Netbackup to disk solution query

[Aidan_Jordan]

Hi,

New to Netbackup but i have a query on backup to disk and protection against failure on the disk

We are deduping our data (Vmware backups) to a NetApps Fas2020. This works well and runs quickly for both the diff and full. However, this disk solution is in our data center so we are paranoid about disk failure and believe that we need to send each nights backup to tape. Unfortunately, the tape solution takes forever as it has to dupe the data.

Example for 1 machine of 150GB data - backup to dedupe store takes 1hr , backup directly to take can take 5 hours, but using the lifecycle policy can take 10 hrs + for this one VM.

It obviously works okay for the differential but my concern is that with 70 VMs been backed up eventually, i won't have time for all the weekend backups

What do other people do, i can't figure out how best to protect your disks but also have a time window for other backups as you can't seem to control the Life Cycle policy. Is there an option, just to copy the deduped data to another disk manually or rather then duping to tape, stop the life cycle policy and have a manual back to tape when required.

Thanks

[mph999]

The problem with disk - disk duplication, is you have no protection against corruption.  If something corrupts, and this is 'copied' over to the other side, you've potentially lost everything.

Martin

[rizwan84tx]

In SLP, you may use LIFECYCLE_PARAMETERS file to optimize and modify the SLP to work as you prefer.

For more information : http://www.symantec.com/business/support/index?page=content&id=HOWTO33715

[watsons]

According to your example, is the 5 hours backup duration for direct backup to tape, up to your expectation?

If it is, you probably fall into one of the known issue Netbackup is still trying to address:

http://www.symantec.com/docs/TECH154166

If the 5 hours is considered too slow, you need to check further if the tape device or disk I/O is causing the delay. Collect bptm logs on media server to see if it falls into the situation as described in: http://www.symantec.com/docs/TECH18422.

You may also want to tune by setting buffer size in: http://www.symantec.com/docs/TECH1724