err, if its not in the manual, I shouldn't say in case it causes any
problems.

basically each day bpdbm will run this in the backgroun. to run it
yourself, stop bprd to no jobs run, and then run bpdbm -consistency 2 >
logfile.

watch the log file for things like missing files or 'error at line xx'. if
you see any errors you will have to look at the actual files.

if your system behaves itself normally and you haven't had any filesystem
fulls on the netbackup db disk, then you shouldn't have any database
problems.

regards
mark


On Mon, 9 Feb 2004, Shafto, Eric wrote:

> Mark,
>  
> I've been searching the web and the Admin guide for anything that might
> conceivably be called a "catalog consistency check" and I have come up
> empty. Is this a manual process (yikes!) or is there a command that does
> this? I'm doing an upgrade this week and a catalog consistency check sounds
> like a good step to add to the plan.
> 
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of mark
> Sent: Saturday, February 07, 2004 6:59 AM
> To: David Thome; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] Best method for moving netbackup server
> 
> 
> If you can afford it, get a veritas consultant. If it goes wrong they may
> well charge you anyway to fix it.
>  
> At a high level:-
>  
> 1. stop all activity on netbackup (stop bprd)
> 2. do a catalog consistency check
> 3. fix any problems with the catalog so its clean
> 4. backup the database to tape
> 5. on client properties add the new server name, so when you switch you
> still have access
> 6. shutdown netbackup
> 7. copy the volume database, the media database and the image database to
> the new machine
> 8. ensure any tuneables or tuneable files such as SIZE_DATA_BUFFERS are
> copied over
> 9. move the access to the robot/drives to the new host
> 10. start netbackup on new master
> 11. change the databases to reflect the new master/media server ( various
> steps within this )
> 12. do some catalog restore queries to see if image access is working.
> 13. do actual restores to see if media/image databases 'work'
> 14. do some local master backups ( use test media, incase media database is
> incorrect )
> 15. do some restores from those test backups
> 16. on client properties, select all and change master name
> 17. run some real backups
> 18. finished
>  
> it at any step beyond 11 you see issues, stop before you get to 17 and you
> can fallback without having overwritten any 'live' tapes.
>  
> regards
> mark
> 
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of David 
> Thome
> Sent: 07 February 2004 05:18
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Best method for moving netbackup server
> 
> 
> 
> I have a SUN V880 server that has both the master and media netbackup server
> on the same machine.  Unfortunately it has other apps on it as well and the
> machines resources are being tapped out.  
> 
> I need to move netbackup off of this machine and on to a new machine.  All
> of the clients will stay the same,  just need to move the master/media
> server to a new machine.  Can I get some suggestions on the best
> practices/methods for doing this.  
> 
> Thank you in advance.
> 
> 
> 
> 
>   _____  
> 
> Plan your next US getaway to  <http://g.msn.com/8HMBENUS/2746??PS=> one of
> the super destinations here. _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 
> 
> 
> 
> If you have received this e-mail in error or wish to read our e-mail 
> disclaimer statement and monitoring policy, please refer to 
> http://www.drkw.com/disc/email/ or contact the sender.
> 
>