Hi Lucian, We do very simple: Through TSM schedule to backup DB with flat file to Disk beginning of hour. 45' later a script to archive the file to other site. If somethings happen we can get data fr
Author: "Mark D. Rodriguez" <mark AT MDRCONSULT DOT COM>
Date: Wed, 15 Sep 2004 11:08:53 -0500
I have to agree with Milton on this one. It seems the system that you describe has some issues that would make me want to have an updated resume! Here is what I have been doing for many years. There
Author: Nicholas Cassimatis <nickpc AT US.IBM DOT COM>
Date: Wed, 15 Sep 2004 18:53:53 -0400
Are you doing OS level backups (sysback/mksysb on AIX, similar tool on other OS platforms) of your TSM Server for DR? If you are, you can "cheat" one of two ways: 1. Do your TSM DBBackup to disk, the
The procedure for doing this is documented in the Tivoli manuals. The answer is: run two copies of TSM server, and have them back up their databases to each other. It would be better if they ran on s
Author: Henk ten Have <hthta AT NCSA.UIUC DOT EDU>
Date: Thu, 16 Sep 2004 01:37:20 -0500
If you have two copies of TSM server, fine. If not, you have to pay for your second copy. I bet it's much cheaper to buy some tapes and send them offline. Cheers, Henk ten Have (back after one year)
Storing a TSM server's database backup inside another TSM server strikes me as a very bad idea. Fundamental recovery such as that of a TSM server calls for rudimentary, uncomplicated data preservati