cancel
Showing results for 
Search instead for 
Did you mean: 

Best practice for backing up multiple Sybase databases?

bitandbytes
Level 2

We have been testing the Netbackup 7.1 sybase solution over the past couple weeks;  we have had success in backing up one single instance database with the template script provided at path  "/usr/openv/netbackup/ext/db_ext/sybase/scripts/sybase_mydb_backup" replacing the variables with our very own.

The logistics questions that have come up for us are that we have hundreds of Sybase servers with each instance having several databases behind them with completely different names.

1.  What is the best way to manage all these database backups from an Netbackup administor's point of view; do we have to have several hundred different scripts with server and database entries that would match those of our sybase customers.. that would seem like like a lot of scripts to manage under one policy or more policies.  Has anyone been able to come up with a better solution?  The only alternative we saw to ease Netbackup administrative management was to give the Sybase administrators user init rights to the policy so they can inititate and manage the sybase back scripts themselves as they move database in and out of production.

 

 

0 REPLIES 0