Well, I guess we will just hijack this thread... sorry.
There are a few things that can help with that. On the warm stand-by TSM server
at the DR site, it has a unique dsmserv.opt file with "DISABLESCHEDS YES" on
the end. When I restore the production TSM database, that setting keeps it from
ru
Jim, my apologies for getting away from your question/subject here, but had a
question for Ben
I have given serious thought to handling my DR site in a similar fashion (warm
stand-by)but have reluctantly decided not to because of the automated tasks
such as Admin schedules and command routi
We are doing the same thing here, although with older versions of TSM: TSM v
5.5.5.0 on AIX6.1.
We dump the TSM DB to a DD690, replicate to a DD580 at a DR site. Then we kick
off a script to restore the DB to a standby TSM server at the DR site.
In testing we did fulls, and fulls+incr and commit
