I agree that having more than 1 IDENTICAL copies of a TSM DB backup is a good thing and these copies needs to be integrated into the framework of DRM. This needs to be added to the TSM wish list. I'm aware that I can backup the TSM DB to disk and then use a non-TSM method of creating a copy of the backup to tape, however the management of that tape is outside of TSM's DRM module. It would be nice if the "BACKUP DB" command would create 2 identical copies of the backup, one to tape and one to disk. DRM could manage the tape copy and the TSM Administrator could manage the disk copy.
H. Milton Johnson Voice: (210) 677-6728 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 16, 2004 3:27 PM To: [EMAIL PROTECTED] Subject: Re: each dbbackup to new tape? ==> In article <[EMAIL PROTECTED]>, "Johnson, Milton" <[EMAIL PROTECTED]> writes: > An interesting paper on an obviously VERY large TSM system, involving > upwards to 40 TSM servers. Mild correction: I started off thinking I'd have that many server instances; That was one of the blind alleys. I now have only 9, and may be able to reduce that. But the principal advantage, from my perspective, of the "backup database to remote server" scheme is that it permits you to keep a copy of your DB backup onsite, and send a copy offsite. If you're not using a separate TSM server to accomplish this, you have to generate multiple DB backups, some snapshots, and each of these is in fact -different-. My offsite copies are the same as my onsite. Perhaps a bit compulsive, but I like it. - Allen S. Rout
