Yesterday my TSM server crashed and lost the db.
Our TSM DB is approx. 1.5 TB on a windows system. I started a TSM DB RESTORE
last night around midnight and it's still running this morning.
Is there any way to know how long it will run or follow the progress other than
the scrolling console?
R
There is a 3rd -party product called Autovault that will manage the vaulting of
a primary pool.
(very well supported product, by the way)
OTOH, best practice requires you still have a 2nd copy of the data.
Vaulted tapes can get lost, get eaten by a drive, etc...
W
-Original Message-
Fr
Thanks for the suggestion. As SOP, we update all firmware, every few
months, so this box is up-to-date.
The Dell diagnostics finally finished, CLEAN. No issues found.
I have some of the FODC logs when the first error occurred (was moving them
to another filespace as fast as I could when the dis
TSMManager has a vaulting management option to select "Primary pools to
vault". Go to http://www.tsmmanager.com. From my sig, I do not work for
them (other than as a beta tester). Just a satisfied customer.
On Wed, Mar 12, 2014 at 8:56 AM, Prather, Wanda wrote:
> There is a 3rd -party product
George,
Sounds like you found yourself in a bowl of spaghetti with just a spoon
to eat your way out.
Some general recommendations:
1. Check all of your tapes for different generations of media. There may
be a mix of JA, JB and JC media.
2. Assuming that you have both onsite and offsite tape
Cheers back to you Neil!
- They are all JA volumes. I have to wait for them to fail to ID them.
- There are copypools so a second virtual library is a good option.
- I was able to determine that all of the scratch made private were
formatted for E06 drives. I took the E06 drives/paths offli
Hi George,
I've had mixed drives in a library from before. What I've had to do
set the devc format to the lesser drive format. I know this does not
utilize the features of the new drives. But administratively when you
no choice, it is much easier than splitting the library.
http://publib.boulder.
If I wanting to keep two weeks of database backups I'm a little confused on how
to run the delete volhist command. Usually I would run the following command:
delete volhist type=dbb todate=today-14
With running only type=dbb I'm noticing a lot of volumes that no longer exist
in the volhist fil
Hello. We include parms: force and devc
DELETE VOLHISTORY type=dbb todate=today-7 force=yes devc=xxxclass
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Maness, Eric
Sent: Wednesday, March 12, 2014 5:06 PM
To: ADSM-L@VM.MARIST.EDU
Subject
Also...
on source server do:
RECONCILE VOLUMES xxxCLASS (where xxxCLASS is the device classthis will
tell you if any volumes are invalid)
Output Example: Volume TSMNBG.DSS.372056474 not valid, source server missing
corresponding entry for
target server.
RECONCILE VOLUMES xxxCLASS fix=y
Nick, the catch here is that I already have media in Generation 3
format..
After setting the Gen 3 drives to write in Gen 2 density, they are also
restricted to reading at Gen2. I would still have to remediate the Gen3
media.
Hi George,
I've had mixed drives in a library from before. What I've
Op 12 mrt. 2014, om 22:05 heeft Maness, Eric het
volgende geschreven:
> If I wanting to keep two weeks of database backups I'm a little confused on
> how to run the delete volhist command. Usually I would run the following
> command:
>
> delete volhist type=dbb todate=today-14
>
> With runn
12 matches
Mail list logo
