Well for NOM we just do what it says in the manual, to create the internally scheduled exports from Sybase to flat files. We then let the standard backup pick those up. The documented restore process is to restore those flat files and go from there. I did wonder about pre-backup scripting but it easier to follow the NOM documents, and just set the backup 12 hours staggered from the backup window - I think we set it to midday or a little after.
And actually, our NOM server is not backed up by NetBackup...but that's another forum ;-) I've not looked at VBR as planning to move to OpsCenter, but I'd guess it will be the same. William D L Brown -----Original Message----- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of David Stanaway Sent: 06 January 2010 06:53 To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Policies for NOM, VBR, KMS Anyone have policies (Pre/Post command scripts/backup selections) for backing up KMS, NOM and VBR? I am kind of surprised there aren't specially crafted backup types for these. ENV: NBU 6.5.4 Windows _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ----------------------------------------------------------- This e-mail was sent by GlaxoSmithKline Services Unlimited (registered in England and Wales No. 1047315), which is a member of the GlaxoSmithKline group of companies. The registered address of GlaxoSmithKline Services Unlimited is 980 Great West Road, Brentford, Middlesex TW8 9GS. ----------------------------------------------------------- _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
