James and Zoltan,
To run expiration for one node use the following undocumented
parameters:
expire inventory beginnode= endnode=
To get the node numbers, use the following case-sensitive commands from
a dsmadmc session:
create sqltable Nodes Mynodes
select c0,c1 from Mynodes order by c1
drop sqlt
copy a domain and change the management class retention and versioning to no
limit and bind the node to that domain.
>>> "Lepre, James" <[EMAIL PROTECTED]> 08/15/08 11:49 AM >>>
Hello Everyone,
Is there a way to stop expiration from happening on a certain Node?
Thank you
James Lepre
No.
But even if you could, it doesn't do what you think.
If you are retaining 5 versions of a file, when you run the 6th backup, the
1st version is gone/expired/inaccessible. Whether expiration has run or
not, you can't get that 1st version back (unless you restore your TSM DB to
a prior date).
Thanks for the suggestions.
I realize the test wont be that accurate. However, these servers are
dedicated to TSM so there shouldn't be anything else running.
I would settle for a 50% difference.
Nicholas Cassimatis <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
08/15/2008 11:41 AM
Pl
I would like the reverse...to run expiration AGAINST one specific
node. I hope V6 adds this.
"Lepre, James" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
08/15/2008 11:50 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] Expiration
Hello Everyone,
Is there a way to stop expiration from happening on a certain Node?
Thank you
James Lepre
---
Confidentiality Notice: The information in this e-mail and any attachments
thereto is intended for the named recipie
I did not interview much. The install date is in the status tren reoport file.
-Original Message-
From: Kauffman, Tom <[EMAIL PROTECTED]>
Sent: Friday, August 15, 2008 11:34 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Expiration on a Test server
FWIW, we use multiple networks for T
Unzone the library and drives on the test machine, so the OS doesn't see
them (then the TSM Server won't, either). Add the "disable sessions" line
to the DSMSERV.OPT file. Now you're isolated. Fire up TSM, and do a DB
Backup to a file (you're doing to want to do this more than once, right?),
the
FWIW, we use multiple networks for TSM backups/archives - and we use DNS.
My TSM server is columbia; it also answers to columbia-pri (our 'private'
network for SAP only); columbia-adm (administrative); columbia-bu1,
columbia-bu2, columbia-bu3, and columbia-bu4 (gigabit dedicated backup
networks
Ah - A light dawns.
You have a TSM server, 'A', on host 'A' that has connections to a library,
disk, and other such. You are now building a new copy of the TSM server 'A' on
host 'B'. If host 'B' does not have physical contact with the library AND your
new server 'A' does not have a server defi
We don't use DNS references. We use specific IP addresses to force
communications onto a private connection/subnet between the servers.
Sounds like I need to go with the "unplug from the network" method before
I start the server up and run the expire.
Thanks for all the feedback. I am glad I ask
This is exactly what I do when testing a new TSM upgrade. I restore a DB
to our test server, but before
starting it I put bogus entries in the /etc/hosts file for each of our
production tsm instances and AIX servers, including
the library manager (we have dns aliases for each TSM instance). That
Zoltan -
I wouldn't touch this configuration with someone else's sharp stick.
For one thing, to run expiration in a realistic manner you'll be limited to one
run per day unless you change the date on the test server.
I'd break the testing into at least two stages -- one as a stand-alone, runnin
One time when we wanted to find out what a change to RETONLY would
accomplish, I restored
a TSM db to a test server, changed the policy, ran expiration, then checked
the occupancy. I don't
know if this was right, but it provided some numbers to play with.
Rick
"ADSM: Dist Stor Manager" wrote o
This is one of the reasons I haven't brought it up after the reload, yet.
The test server isn't going to use/do anything but test things like EXPIRE
INVENTORY. We will be eraseing/reloading it numerous times.
So, how do I avoid these possible complication? Disconnect the ethernet
cable and work
When we did our upgrade testing we did not allow the test server to talk
to the production server by creating a false entry in the hosts file.
We also did not allow our test server to connect to the libraries. This
may be the paranoid approach, but we did not break anything.
Andy Huebner
-Ori
Anyone familiar with tsm/gresham and acsls?
I checked in some scratch tapes via acsls
Set scratch
Pool #
Range #
However,
Tsm is not recognizing the newly checked in tapes, any ideas?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Dre
thanksalot
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Drew
Sent: 2008, August, 14 11:36 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Total amount of data migrated
Here is a hairy unix command that gets the information from the actlog an
On Aug 15, 2008, at 10:10 AM, Zoltan Forray/AC/VCU wrote:
Will doing this effect the actual, live data on the production server,
since they see each other? I was concerned it would try to release
tapes
and such.
By covertly sharing the real tape library inventory, you're playing
with fire, as
Such files are marked Inactive (not Deleted), and can be seen in scans
of the Backups and Archives tables (STATE='INACTIVE_VERSION') - which
is expensive, and can't report actual client file sizes.
Richard Sims
We are going to start billing folks for TSM resources usage/occupancy.
One issue that came up was how to identify those node objects/files that
are marked as DELETED and thus remain in inventory due to the RETONLY
duration of the management class. If we are to start billing for
occupancy, we woul
We have purchased a new, even beefier server then our last one.
To make sure it is configured optimally, we want to test how long an
expire inventory runs. Our biggest server is up to 190G DB and expires
run 40-48hours.
I installed and configured the new server, connecting it to the main, tape
l
Shawn,
in the dsm.opt the syntax is, I think
testflag DISABLEATTRIBUPDATE
i.e. no '='
Ian Smith
On Thursday 14 Aug 2008 7:53 pm, Shawn Drew wrote:
> Unfortunately that didn't work when I tried a backup. Anyone else with
> an idea on how to get a testflag into a client option set?
>
> "Invali
23 matches
Mail list logo
