This concept was considered, but is really last on the list - it's a bit of a mine field.
Running two VM:Backup service machines has potential, though, instead of running two backups serially on the same machine. -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of O'Brien, Dennis L Sent: Thursday, June 05, 2008 1:53 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VM:Backup: Twinning Tapes to Remote Tape Unit If you do a tape-to-tape copy, make sure your local and remote tape volsers match. VM:Backup has the tape volsers in its catalog. If you don't have the correct volsers at your remote site, you have a problem. You could probably get away with different volsers if you code VM:Backup's tape mount user exit to translate the local volser to the remote volser. VM:Backup will probably want to check the tape label, so you'll need to make sure that was copied as part of your tape copy. You'll need to mount the tapes with BLP at the remote site if you do this. Note: I haven't tested any of this. We run a separate backup job, from a separate VM:Backup service machine, for our DR backups. Dennis O'Brien "Don't worry about biting off more than you can chew. Your mouth is bigger than you think." -- CVW-11 chaplain, "Carrier" -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Thursday, June 05, 2008 13:38 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VM:Backup: Twinning Tapes to Remote Tape Unit >>> On Thu, Jun 5, 2008 at 4:12 PM, in message <[EMAIL PROTECTED]>, Mark Llewellyn <[EMAIL PROTECTED]> wrote: -snip- > Our other option is to simply run two backup jobs, one to the local drive > and one to the remote, but that effectively doubles the hit of the backup > jobs. Not if you do the backup to local tape drives, and then do a tape-to-tape copy to the remote drives. Mark Post
