Unsolved
This post is more than 5 years old
5 Posts
0
2156
September 25th, 2014 11:00
Replication/duplication initial starting
Currently using Netbackup 7.6.0.2 with Data Domain units for replication to remote central storage.
Know it is best to seed the target unit because it allows better replication times. If seeding is not possible which way is better.?
1.Using SLP create a full backup job for backup and replication and let this job completely finish before starting another job. This may take a while.
2. Using SLP create the backup job and allow multiple weekly jobs to run.
Tried the second method and ended up with lots of jobs running. Seemed to me that the many jobs were interfering with each other.
One of my group cancelled the earlier jobs. This seems to be counterproductive as the data transferred is probably not usable.
My understanding of the way DD Boost works with the SLP replication is that the source machine works with the target machine to send only new data. Since this is the original set of data this will take a while. Is there a better way to do the seeding across the network? Would just doing a backup to the target device be better than using SLP.
We actually do a monthly (long term storage) and weekly-full (short term storage) and am considering only doing the monthly backup because of the time it is taking to complete the replication/duplication process.
tks
ed



ed_smith
5 Posts
0
September 29th, 2014 14:00
1. Target is DD640 Origin DD2500, DD640, DD160
2 5.4.2.1-423209
3 depends on location 512 to 5 mb Limited during working hours. Varies from location
4 all over the place
standard slp
Think am making this too complicated. Know that prestaging data is the best way to go. However; in places where this is not possible should I let the first full replication (each server) job finish before starting more? All other questions follow from that.
tks
ed