I asked "you" not to ask! (business reasons for not upgrading the old database, and the DBAs, although they do their best to support an unsupported database, have no desire to inject yet another unsupported process in the mix.
Michael correctly asked - what about the archive logs that are created during the backup? That's a great question which we found was a real problem when we did our first test restore. So we made some alterations. Now I have a policy that just has for selection, the database data files. I have another that just does the archive logs. Only the data-file policy calls the pre-and post scripts to put the database into and out of backup mode. It turns out that we can call bpbackup from the master server, so although I can't set up a policy dependencies using the netbackup scheduler, I can call both bpbackups in the correct order in a little shellscript that is called by cron on the master scheduler. Although we have not tried to do a restore yet using this backup technique, I have hopes that it will work correctly. We'll be trying the restore this week. +---------------------------------------------------------------------- |This was sent by [email protected] via Backup Central. |Forward SPAM to [email protected]. +---------------------------------------------------------------------- _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
