Jeff,
If you don´t want to stop TSM, the other alternative is to delete paths,
drives and library.
Make the necessary library changes and redefine the library. Checkin
scratch tapes and checkin private next.
If you have library clients, run an audit on the library client next. All
should be fine n
Well, the saga is coming to a conclusion and I am going to active
encryption of offsite tapes, via AME/TSM.
Is there anything more I need to do besides update the DEVCLASS to
DRIVEENCRYPTION=ALLOW on all of my TSM servers?
When I check the drive details via the TS3500 interface, is says encryptio
Just another item of info server is at level , we have plans to go to 6.3.3,
now maybe sooner.
Would that be first option before PMR .
Session established with server TSM_SERVER1: Windows
Server Version 6, Release 3, Level 1.15
Server date/time: 08/20/2013 12:02:00 Last access: 08/20/2013 1
No orphaned filespaces
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Sheridan, Peter T.
Sent: Tuesday, 20 August, 2013 11:57 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Move node to new domain
Another wild guess and doubt it will matter b
Another wild guess and doubt it will matter but if you do q filespace on the
node do u see orphaned filespaces that you might be able to delete and clean
things up ?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Tim
Brown
Sent: Tuesday, Aug
Yes still seeing orphaned references
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Ehresman,David E.
Sent: Tuesday, 20 August, 2013 11:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Move node to new domain
Tim,
Have you done an "audit vol
Tim,
Have you done an "audit vol XXX fix=yes" on the volumes in question? That
should fix discrepancies between TSM tables
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nick
Laflamme
Sent: Tuesday, August 20, 2013 11:07 AM
To: ADS
The most alarming thing I see about Tim's question is the discrepancy
between Q NODEDATA and Q CONTENT. Q NODEDATA says that there's data for
that user in that volume; Q CONTENT contradicts that. He doesn't show the
full output of the Q CONTENT command, but if what he says is true, I'd
suggest he o
I am having difficulty sending to adsm-l so if you already got this please
ignore!
We recently moved a node from domain dm1 to domain dm2 but are still seeing
nodedata references in dm1 that we cant remove.
If we issue Q CONTENT D:\DM1_PRIM1\0001EAD4.BFS >0001EAD4.TXT theres
I am having difficulty sending to adsm-l so if you already got this please
ignore!
We recently moved a node from domain dm1 to domain dm2 but are still seeing
nodedata references in dm1 that we cant remove.
If we issue Q CONTENT D:\DM1_PRIM1\0001EAD4.BFS > 0001EAD4.TXT
theres n
need to test access to adsnm-l
Tim
Hi Jeff
All SCSI Libraries are basically the same. I've just been through a ton
of pain during a two site TS3500 upgrade (TSM 5.5.6 under AIX). My
advice is shut down the TSM server, make your changes and bring it back
up. The library layout that TSM internalizes will be rebuilt by the
restart
Hi Allen,
why so complicated? Why not 'move nodedata'?
Op 20 aug. 2013, om 02:52 heeft "Allen S. Rout" het volgende
geschreven:
> On 08/19/2013 12:26 PM, Tim Brown wrote:
>> We recently moved a node from domain dm1 to domain dm2 but are still
>> seeing nodedata references in dm1 that we can
13 matches
Mail list logo
