sort_backup_type device
Specifies that NetBackup create jobs based on a file's device ID. This causes the drives parameter in the intSID.utl file to be ignored.
For example, if 12 files are requested for backup, and they reside on two different devices (X and Y), then two jobs are created. The first job contains all the files that are associated with device X, and the second job contains all the files on device Y.
Note:
The implementation is based on the st_dev value from the stat() function. This value identifies a file partition.
The following UNIX or Linux example shows how jobs are created when device is specified:
Input file list from SAP (brbackup, sapdba):
/oracle/sap/sapdata1/btabd_1/btabd.data1 /oracle/sap/sapdata2/btabi_1/btabi.data1 /oracle/sap/sapdata2/clud_1/clud.data1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 /oracle/sap/sapdata5/ddici_1/ddici.data1 /oracle/sap/sapdata4/el30cd_1/EL30cd.data1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 /oracle/sap/sapdata2/poold_1/poold.data1 /oracle/sap/sapdata1/pooli_1/pooli.data1 /oracle/sap/sapdata4/protd_1/protd.data1 /dev/rdsk/c0t4d0s6 11812864
Backup job 1 (all have the device ID x):
/oracle/sap/sapdata1/btabd_1/btabd.data1 /oracle/sap/sapdata2/btabi_1/btabi.data1 /oracle/sap/sapdata2/clud_1/clud.data1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 /oracle/sap/sapdata5/ddici_1/ddici.data1 /oracle/sap/sapdata4/el30cd_1/EL30cd.data1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 /oracle/sap/sapdata2/poold_1/poold.data1 /oracle/sap/sapdata1/pooli_1/pooli.data1 /oracle/sap/sapdata4/protd_1/protd.data1
Backup job 2 (all have the same device ID y):
/dev/rdsk/c0t4d0s6 11812864
The following Windows example shows how jobs are created when device is specified:
Input file list from SAP (brbackup, sapdba):
Backup job 1 (all have the device ID x):
Backup job 2 (all have the same device ID y):