Forum Discussion

Yet's avatar
Yet
Level 5
12 years ago

Method of backing up remote sites

Hi! I have Netbackup 7.5 environment with Appliance 5220 media server. Everything is OK however, my dilema is backing up rmeote sites. Link on those sites is not that good. I thought of enabling cl...
Backing Up
Backup and Recovery
NetBackup
Windows Server (2003-2008)
  • Nicolai's avatar
    Nicolai
    12 years ago

    Client side de-dupe is a very good choice. However if the link is bad Netbackup will always fail.

    Try setting up a ping test from the 5220 to one of the remote client. If you see a large amount of failed pings the line is defect and network should be notified

    This command will ping 999 ping with a size of 8K per ping to the host srv1

    ping -n 999 -l 8192 srv1.acme.com

bak's avatar
bak
Level 4
12 years ago
I know this post has already been marked as solved, but I thought I would add a couple of points from my experience with a couple of slow links to remote sites where we are using client-side deduplication. We have some sites that have fractional T1 links, and they are so small and remote no one wants to fund the bandwidth. You can "Jump-Start" client-side deduplication IF you have a copy of some of the files that you would find at the remote site. For example, say you have 20 Windows 2008R2 servers at the remote site, you could backup a vanilla 2008R2 server that has a fast link, and thereby adding all of those Windows objects into the dedup pool so they do not have to be re-sent for the remote jobs. Also, I ended up tanking a remote site link with an appliance swap out, ended up having to seed the new appliances with backup images from the previous appliances (via bpduplicate). Once you have a FULL of everything, your daily jobs will probably run fine as long as the change rate is relatively low. Consider getting a full of your clients one-at-a-time, then once you do, you can turn them all on.