Smarter SLP or Vault process
Idea - improve logical process SLP uses to determine which jobs to run.
I currently use Storage Lifecycle Policies (SLP) extensively. I find they have improved my efficiency tremendously.
However, since many of my policies create backups that do not fill a tape, a later backup can be using that same tape.
When the SLP starts, it requests and reserves the source tape and a destination tape drive. If the source tape is busy with another backup, the SLP queues up (which locks the destination drive) until the source tapes is freed up.
Here is my idea -
When the SLP agent checks to see what SLP are not complete, check the source tape to see if it is in use BEFORE allocating a drive.
Instead of just doing a FIFO (first in first out) process, add in a check so available jobs can be started. Perhaps priority can be taken into account if there are jobs which need to be queued up and run regardless.
I backup to a VTL and then to tape, and can find hundreds of jobs queued waiting for source tapes - behind a log jam of a few jobs hogging the destination drives.
I am also testing backup to
I am also testing backup to VTL then to tape. The duplicate will start right after the backup is finish, maybe can have a parameter to set the delay for the duplicate, for example 30 minutes, to give time to fill up the cartridge in the VTL? or just give smaller size to the VTL?
There are parameters
There are parameters available in /{install path}/netbackup/db/config/LIFECYCLE_PARAMETERS
Here are mine:
# cat LIFECYCLE_PARAMETERS
#MIN_GB_SIZE_PER_DUPLICATION_JOB 256
MIN_KB_SIZE_PER_DUPLICATION_JOB 268435456
MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB 80
DUPLICATION_SESSION_INTERVAL_MINUTES 20
IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS 4
MAX_IMAGES_FETCHED_SESSION 200
Check out this document:
ftp://exftpp.symantec.com/pub/support/products/Net...
Would you like to reply?
Login or Register to post your comment.