11-21-2016 03:39 AM
11-21-2016 04:29 AM
Duplication jobs will go on till they complete. If there are no drives, they will wait till they get a drive or till you kill the duplication job.
You can schedule duplication jobs. You also need to fine tune the backups and jobs so they complete on time and do not competer or clash over drives. If you have large backups, you might want to think about inline duplication and getting more drives. Perhaps even stagger your duplications.
11-21-2016 04:30 AM
* compete for drives.
11-21-2016 04:42 AM
11-21-2016 07:24 AM
Check out the Link Marianne provided.
There is a file ( unix) /usr/openv/var/global/nbcl.conf that contains the non-standard SLP parameters.
I find that by having several options, I can set up simple aliases or shell scripts to update them using commands like:
/usr/openv/netbackup/bin/admincmd/bpsetconfig /usr/openv/var/global/nbcl.conf.small
cat /usr/openv/var/global/nbcl.conf.small
SLP.MIN_SIZE_PER_DUPLICATION_JOB = 32 GB
SLP.MAX_SIZE_PER_DUPLICATION_JOB = 64 GB
SLP.JOB_SUBMISSION_INTERVAL = 5 minutes
SLP.IMAGE_PROCESSING_INTERVAL = 5 minutes
SLP.IMAGE_EXTENDED_RETRY_PERIOD = 10 minutes
SLP.MAX_TIME_TIL_FORCE_SMALL_DUPLICATION_JOB = 2 minutes
OR
cat /usr/openv/var/global/nbcl.conf.big
SLP.MIN_SIZE_PER_DUPLICATION_JOB = 64 GB
SLP.MAX_SIZE_PER_DUPLICATION_JOB = 256 GB
SLP.JOB_SUBMISSION_INTERVAL = 20 minutes
SLP.IMAGE_PROCESSING_INTERVAL = 20 minutes
SLP.IMAGE_EXTENDED_RETRY_PERIOD = 1 hour
SLP.MAX_TIME_TIL_FORCE_SMALL_DUPLICATION_JOB = 20 minutes
There are efficiencies you can achive with grouping duplications into larger ones, or making smaller ones if you need to free up a drive.