Our data center is eliminating an STK tape silo and
implementing STK's Virtual Tape product. They tell me that there is no
interface from VM for STK Virtual Tape. The data center manager wants to
know if we could take DB2/VM backups from MVS (shared dasd environment).
Our DBA has suggested the alternate solution (below) for DB2/VM
backups.
Has anyone got experience with doing DB2/VM backups in such an environment or care to comment on either proposed solution?
Terry A. Moore
Proj Mgr - IT Infrastructure
Terry,Here is the problem. We have several VM for DB2 database servers. Currently they use vmbackup to take database and log backups using the tape silo. The tape silo is being replaced by a virtual tape machine(from STK). VM cannot talk to the virtual tape machine so utilizing that is not an option. My thoughts currently are to take a weekly backup of all the DB2 for VM database machines data disk utilizing a FAT tape(s) and throughout the week take log backups for the database machines that do online updating. I am still trying to test this scenario to make sure it will work.Currently, we use a product called VM:DBA from CA that allows us to automate all the backups so no operator intervention is required. In order to use FAT tape(s) to backup all the databases at one time, I will create a vmbackup template that will have all the databases data disks and then it will be submitted via an exec by VM:DBA after all the databases have been brought down. The problem here is VM:DBA will not be able to track when the backups are done and keep track of the volume serial numbers use in the backup process so the restore process will now have to a more manual process outside of the VM:DBA product. Also, a routine to bring the databases back online after the backup is done will need to created.
This message and any attachments are intended for the individual or
entity named above. If you are not the intended recipient, please
do not forward, copy, print, use or disclose this communication to
others; also please notify the sender by replying to this message,
and then delete it from your system. The Timken Company / The
Timken Corporation
