cancel
Showing results for 
Search instead for 
Did you mean: 

Help configuring Dedup and duplicating images to tape using SLP

jpichardo
Level 4

We are running Netbackup 7.5.0.6 on both our master and media servers, Windows Server 2008 R2 is the operating system on both systems. We have a mixed bag of virtual and physical servers mostly Windows based with a handful of Linux boxes thrown in the mix.  Currently we use a disk to tape strategy using the disk staging scheduler to duplicate the images to tape.  I want to configure deduplication and the supporting storage units on my media server then use SLP to duplicate images to tape, we are required to send tapes offsite on a daily basis. Although I am fairly certain how to configure the storage server and storage unit disk pool I have some general questions.

Is client or server side dedup the best option to back up the VMware VM’s? How do I configure the SLP to copy all images backed up that night to duplicate to tape, will one SLP accomplish this task?

1 ACCEPTED SOLUTION

Accepted Solutions

Mark_Solutions
Level 6
Partner Accredited Certified

If your VMware backup host is your Media Server then it makes no difference whether you use server or client side as it is the same place

If you use another client as the VMWare backup host then use client side to reduce the data crossing the network.

If you do Daily, Weekly, Monthly and Annual backups with different retention periods then you will need an SLP for each in order to set the appropriate retention periods

In your policy you would then set the Policy Attributes to use say the Weekly SLP and then override the Daily, Monthly and Annual Schedules to use the appropriate SLP

Each SLP will have just 2 steps

1. Backup - this selects the de-dupe disk storage unit taht you back up to - set the retention carefully as unlike disk staging it is not capacity managed so dont have this too long or your disk will fill up and everything will stop!

2. Duplication - here you select the tape storage unit and tape pool plus the tape retention (this is why you need a different SLP for every tape retention you need.

You then back up to the SLP rather than a storage unit and NetBackup does the rest for you automatically

Hope this helps

View solution in original post

3 REPLIES 3

V4
Level 6
Partner Accredited

single slp can work to duplicate those images, Default replication time are 30 mins specified in slp configuration touch file, however it can be changed based on your requirement.

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

For Deduplication setup. All you need is netbackup media server on x64 architecture. Storage for DeDupe. Deduplication license installed on master/media

From master Server admin console, click on master server name.(above activity monitor)

on right pane you will find list of wizards. Choose configure storage server

Follow wizard for storage server -> Disk pool -> STU

Just make sure for specifying dedupe path. provide directory path instead of Drive.

 e.g. instead of F:\ provide F:\MSDP1 or F:\DeDupe1 anything you name.

Credentials prompted are not your local system or domain creds. Those are for NBU MSDP internal. Hence make a note of those creds used as it would be required during troubleshooting cases especially for recovery in case required.

You should be fine through it.

let us know if above clarifies 

Mark_Solutions
Level 6
Partner Accredited Certified

If your VMware backup host is your Media Server then it makes no difference whether you use server or client side as it is the same place

If you use another client as the VMWare backup host then use client side to reduce the data crossing the network.

If you do Daily, Weekly, Monthly and Annual backups with different retention periods then you will need an SLP for each in order to set the appropriate retention periods

In your policy you would then set the Policy Attributes to use say the Weekly SLP and then override the Daily, Monthly and Annual Schedules to use the appropriate SLP

Each SLP will have just 2 steps

1. Backup - this selects the de-dupe disk storage unit taht you back up to - set the retention carefully as unlike disk staging it is not capacity managed so dont have this too long or your disk will fill up and everything will stop!

2. Duplication - here you select the tape storage unit and tape pool plus the tape retention (this is why you need a different SLP for every tape retention you need.

You then back up to the SLP rather than a storage unit and NetBackup does the rest for you automatically

Hope this helps

View solution in original post

jpichardo
Level 4

I successfully created the dedup disk pool and storage unit then created three SLP's with the proper retention times for Diff, Full and Monthly backups.  I configured all of my existing backups policies to use one of the SLPs according to backup type and data classification. I conducted some test backups and realized size savings of up to 99% but my backup times did not improve at all. Perhaps disk tuning is in order? 

Below are some job details

 

9/6/2013 11:35:57 AM - Info nbjm(pid=5112) starting backup job (jobid=2795) for client Webdev, policy Webdev, schedule Full 
9/6/2013 11:35:57 AM - Info nbjm(pid=5112) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2795, request id:{58C2D492-CDA7-4187-9671-76F0B3055D31}) 
9/6/2013 11:35:57 AM - requesting resource mediasvr_msdp_stu
9/6/2013 11:35:57 AM - requesting resource netbackup.magnacare.com.NBU_CLIENT.MAXJOBS.Webdev
9/6/2013 11:35:57 AM - requesting resource netbackup.magnacare.com.NBU_POLICY.MAXJOBS.Webdev
9/6/2013 11:35:57 AM - granted resource netbackup.magnacare.com.NBU_CLIENT.MAXJOBS.Webdev
9/6/2013 11:35:57 AM - granted resource netbackup.magnacare.com.NBU_POLICY.MAXJOBS.Webdev
9/6/2013 11:35:57 AM - granted resource MediaID=@aaaai;DiskVolume=PureDiskVolume;DiskPool=mediasvr_msdp_dpool;Path=PureDiskVolume;StorageSer...
9/6/2013 11:35:57 AM - granted resource mediasvr_msdp_stu
9/6/2013 11:35:57 AM - estimated 6629634 Kbytes needed
9/6/2013 11:35:57 AM - Info nbjm(pid=5112) started backup (backupid=Webdev_1378481756) job for client Webdev, policy Webdev, schedule Full on storage unit mediasvr_msdp_stu
9/6/2013 11:35:57 AM - started
9/6/2013 11:35:59 AM - started process bpbrm (4704)
9/6/2013 11:36:04 AM - connecting
9/6/2013 11:36:05 AM - Info bpbrm(pid=4704) Webdev is the host to backup data from    
9/6/2013 11:36:05 AM - Info bpbrm(pid=4704) reading file list from client       
9/6/2013 11:36:07 AM - connected; connect time: 00:00:03
9/6/2013 11:36:08 AM - Info bpbrm(pid=4704) starting bpbkar32 on client        
9/6/2013 11:36:08 AM - Info bpbkar32(pid=0) Backup started          
9/6/2013 11:36:08 AM - Info bptm(pid=5168) start           
9/6/2013 11:36:08 AM - Info bptm(pid=5168) using 262144 data buffer size       
9/6/2013 11:36:08 AM - Info bptm(pid=5168) setting receive network buffer to 1049600 bytes     
9/6/2013 11:36:08 AM - Info bptm(pid=5168) using 30 data buffers        
9/6/2013 11:36:10 AM - Info bptm(pid=5168) start backup          
9/6/2013 11:36:11 AM - Info bptm(pid=5168) backup child process is pid 5672.2884      
9/6/2013 11:36:11 AM - begin writing
9/6/2013 11:36:12 AM - Info bptm(pid=5672) start           
9/6/2013 12:15:19 PM - Info bptm(pid=5168) waited for full buffer 10090 times, delayed 147953 times   
9/6/2013 12:15:20 PM - Info bptm(pid=5168) EXITING with status 0 <----------       
9/6/2013 12:15:20 PM - Info mcwb-mediasvr.magnacare.com(pid=5168) StorageServer=PureDisk:mcwb-mediasvr.magnacare.com; Report=PDDO Stats for (mcwb-mediasvr.magnacare.com): scanned: 5552201 KB, CR sent: 34620 KB, CR sent over FC: 0 KB, dedup: 99.4%
9/6/2013 12:15:20 PM - Info bpbrm(pid=4704) validating image for client Webdev       
9/6/2013 12:15:24 PM - Info bpbkar32(pid=0) done. status: 0: the requested operation was successfully completed   
9/6/2013 12:15:24 PM - end writing; write time: 00:39:13
the requested operation was successfully completed(0)