This would be SmWaitForDevice in the global configuration file. Restart DP services to have the new values become active. Another solution would be to use post backup instead of scheduled object copies.
# default: 60 minutes # This timeout is used by the Backup Session Manager. The # Backup Session Manager first tries to get a lock for all # devices that will be used for backup. If a lock can not be # obtained for the desired devices, the BSM will wait for the # specified time-out. If it can not get a lock for the devices, # the backup session will fail. If dynamic is used then the # Backup Session Manager tries to get a lock for the minimum # number of devices used for backup. In general, # SmWaitForDevice is used as a time-out for different kinds of # queuing (queuing for lock, license etc.).
--- Please assign a KUDO to this post, if you find it useful.
All you have to do is the specify which backups you want to be copied, what device(s) and what pool they will be written to and whether you want to change the protection of the original disk backup on completion.
As each backup completes Data Protector starts the copy of that backup.
I summarize: I create a new job -post backup- then: - First tab : i select all backups - Second tab : nothing to do - Third tab : nothing to do - Fourth tab: check the 2 boxes - Fifth tab : nothing to do - Sixth tab : nothing to do - Seventh tab: i select my tape drive - Eighth tab: i modify if needed
Thus at the end of each backup disk it will be copied to tape. That although there are several backups on disks at the same time.
There are thirty backups between 09:00am to 05:30am D+1.