NB7.5 Remote Backup Procedure after upgrading & changing Master
Environment: NetBackup 7.5 Media Server with Puredisk and Tape Library attached. I need to backup remote site "ZXY" over a WAN Link. History: Previously we were backing up XYZ using Synthetic Backups to Media Server "B" with Master Server "A" in another location. We then moved to a new Master Server "A1"and media server "B1." Before moving we replicated data using SLP from B to B1. We used the following link to seed: http://www.symantec.com/business/support/index?page=content&id=TECH144437 In particular this section: For example, assume two new remote clients, remote_client1 and remote_client2, are being backed up for the first time.Data for both clients has been copied via a transfer drive and backed up locally to the media server media1, using a policy called “transfer_drive”. Run the following commands on the media server to setup a special seeding directory using the transfer_drive backup images for each client: $ seedutil -seed -sclient media1 -spolicy transfer_drive -dclient remote_client1 $ seedutil -seed -sclient media1 -spolicy transfer_drive -dclient remote_client2 Verify the seeding directory has been populated for each client: $ seedutil –list_images remote_client1 $ seedutil –list_images remote_client2 Run backups for remote_client1 and remote_client2. Clean-up the special seeding directory.: $ seedutil –clear remote_client1 $ seedutil –clear remote_client2 Clearing the special seeding directory is important.The source backup images referenced in the special seeding directory will not be expired until they are no longer referenced.To help with this, the special seeding directory for a client will automatically be cleared whenever an image is expired by NetBackup for that client.That being said, it is good practice to explicitly cleanup the special seeding directory when it is no longer needed Now: We attempted to run backups but continually failed with Error 14. We had the Accelerator unticked. Due to the way our VPN's and WAN links are setup we decided to point the Client to another Media Server C1 which connects to A1 Master Server. How should I progress with backing up the client. Shall I use the Accelerator, have Client Side Dedupe and just run a Full Backup over the link? Or shall I some how replicate from Media Server B to C1 or from B1 to C1, then follow the above link on seeding and then run a full backup? Im a little confused on how remote backups are actually suppose to work and whether the Accelerator works on the first backup. Also whether it will use the dedupe data. Any help is appreciated.
HP StoreOnce OST Plug in for NetBackup on Windows/Linux/Solaris & HPUX
There have been several queries on this forum about downloading the HP StoreOnce OST Plug in for NetBackup, which seem either out of date or don't give the actual information, so here is the latest info. An article from Dec 2012 on HP's Support Center HP D2D/B6000 StoreOnce Backup Systems - OST Software Information with Download Details directs you to: http://www.software.hp.com/kiosk But with the incorrect username and password! Please use the following: User Name: STOREONCE_KIOSK Password: STOREONCEAPPS Once there, the following HP StoreOnce OST Plug ins are available for download: HP StoreOnce Catalyst Plugin for Oracle RMAN Windows v1.0 HP StoreOnce Catalyst Plugin for Oracle RMAN Linux v1.0 HP StoreOnce Enterprise Manager V1.2 for Windows HP StoreOnce D2D OST Plugin v1.2 for Windows/Linux/Solaris & HPUX HP OST Plugin v2.0 for NBU for Solaris Sparc v10/HPUX 11.31i HP OST Plugin v2.0.1 for BE for Windows HP OST Plugin v2.1 for NBU for Windows/Linux Release notes and installation guides are usually included with each plug in's tar/zip file. Please ensure that your environment is compatible with the latest Symantec and HP matrices, including the HP Enterprise BURA Solutions (EBS) Compatibility matrix on SPOCK (requires an HP Passport account creating): http://www.hp.com/storage/spock [It will be updated for OST v2.1 shortly!].
Advice for my SQL backup schemes - what are you doing?
So currently all of my SQL servers have now been moved to VMWare (with most of my other servers). Currently, I have SQL server type backups dumped from every server to a share on my backup server \SQLDumps$\SERVERNAME\DB_NAME Also, since moving to Netbackup 7.5, I have the VMWarev2 type of backup, with no SQL server integration. I believe that I am correct in thinking that as long as I do VMWarev2 style type of backup, it will always pull all files. And because it quieses, I believe that SQL would work, if I restored the entire VM at once. I have tried using the SQL integration before, but it seemed like it was going to be a massive job as many servers were giving me different errors to go chase down, plus I'd still be backing up the files twice. Since I have no need for anything less than a night's backup, the SQLDUMPS are for individual database restores, and the full VMWAREv2 backups are for full emergency restores. I suppose this works, but it feels strange backing up the database files twice every time, (which I believe won't be de-duped well). I think it's about 600GB of databases, so a total of 1.2TB per night for the database files since they essentially back up twice. What do you think, does my plan as is make sense? Are you doing something similar or different?