well, having a small database (500MB) and a large tape (400GB) it's at least a waste of tapes.. Regards, Lucian goc <goran.k AT VIP DOT HR> Gesendet von: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIS
Hi Hoa, now this sounds interesting: I suppose I willhave to define a "FileDrive" device, since I belive that only device classes are allowed targets to the dbbackup command. And then set up a nice s
Author: "Johnson, Milton" <milton.johnson AT CITIGROUP DOT COM>
Date: Wed, 15 Sep 2004 10:54:04 -0400
OK, I just have to jump in. If I understand Hoa he: 1) Backs up the TSM database to a disk file 2) backs up that disk file to a TSM disk storage pool using DSM 3) moves that db backup to onsite/offsi
Author: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG>
Date: Wed, 15 Sep 2004 07:55:38 -0700
It's Ok to backup your database to disk, but you can't use the backup/archive client to protect that file. If your database is corrupted, you won't be able to restore any files until you first restor
Author: Henrik Wahlstedt <shwl AT STATOIL DOT COM>
Date: Wed, 15 Sep 2004 16:57:42 +0200
Ok, I agree itīs a nice workaround.. But in Hoaīs case with a buch of 3592 drives it seems like you have a .... small budgett if you cant afford ~7 more tapes... And keep in mind that you should be a
You only have to pay for the 1's you write on the tape. The unused portion is free. In the case of the DB tape, however, the information is more valuable than the data on primary or copy storage pool
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 dat
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)
Author: Otto Schakenbos <otto.schakenbos AT TELEFLEX DOT COM>
Date: Thu, 16 Sep 2004 09:49:23 +0200
Although this does cover you in case of a disk failure, it doesn't save you in case if a bigger disaster where you loose the both servers. And therefore only doing this is not a good idea. At least r
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
Author: "Purdon, James R" <james_purdon AT MERCK DOT COM>
Date: Mon, 18 Oct 2004 17:28:58 -0400
Hi, The resume issue goes away if the tape backup of the database backup flat files is a non-TSM backup. The probably of managing the non-TSM tapes is left as an exercise for the reader - but it can
well, having a small database (500MB) and a large tape (400GB) it's at least a waste of tapes.. Regards, Lucian goc <goran.k AT VIP DOT HR> Gesendet von: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIS
Hi Hoa, now this sounds interesting: I suppose I willhave to define a "FileDrive" device, since I belive that only device classes are allowed targets to the dbbackup command. And then set up a nice s
Author: "Johnson, Milton" <milton.johnson AT CITIGROUP DOT COM>
Date: Wed, 15 Sep 2004 10:54:04 -0400
OK, I just have to jump in. If I understand Hoa he: 1) Backs up the TSM database to a disk file 2) backs up that disk file to a TSM disk storage pool using DSM 3) moves that db backup to onsite/offsi
Author: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG>
Date: Wed, 15 Sep 2004 07:55:38 -0700
It's Ok to backup your database to disk, but you can't use the backup/archive client to protect that file. If your database is corrupted, you won't be able to restore any files until you first restor
Author: Henrik Wahlstedt <shwl AT STATOIL DOT COM>
Date: Wed, 15 Sep 2004 16:57:42 +0200
Ok, I agree itīs a nice workaround.. But in Hoaīs case with a buch of 3592 drives it seems like you have a .... small budgett if you cant afford ~7 more tapes... And keep in mind that you should be a
You only have to pay for the 1's you write on the tape. The unused portion is free. In the case of the DB tape, however, the information is more valuable than the data on primary or copy storage pool