Configure the advanced options for an IBM i File System subclient.
Target release for backup data
Specify the operating system version that runs on the restore destination when it is different than the source client.
The format is as follows:
VxRxMx
where:
V - The operating system version
R - The operating system release
M - The operating system modification level
Example
Use the following to specify Version6, Release 1, Modification 0.
V6R1M0
The valid values for this parameter change in every new release.
Save access path
Specify whether to save the logical file paths that are dependent of the physical files that are being saved.
-
*SYSVAL
Have the QSAVACCPTH system value determine whether to save the logical file access paths that are dependent on the physical files that are being saved.
-
*NO
Only save the objects that are specified on the command line. This option does not save the logical file access paths.
-
*YES
Save the specified physical files, and all the eligible logical file access paths that are above them
Note
If the based-on physical files and the logical files are in different libraries, then the access paths are saved. However, if the logical files, and the based-on physical files are in different libraries, and the logical files or physical files do not exist at at the time that you perform the restore (such as during disaster recovery or the files were deleted), then the software rebuilds the access paths instead of restoring them. For the fastest possible restore operation for logical files, the logical files and the based-on physical files must be in the same library and must be saved at the same time.
Update history (UPDHST)
Specifies whether the save history information of each saved object is changed with the date, time during the backup operation.
-
*YES
The software updates the last save date, and time for each saved object.
-
*NO
The software does not save history information contained in the description of each object saved during the backup operation.
Compression
Specifies the client-level software data compression that the software uses. Use a higher level of compression if you need to reduce the data through the network between the IBM i client and the proxy.
-
*NO
The software does not perform any data compression.
-
*LOW
The software performs the data compression using the SNA algorithm. Low compression is usually faster than medium and high compression and the data is usually larger than medium and high compression data.
-
*MEDIUM
The software performs the data compression using the TERSE algorithm. Medium compression is usually slower than low compression but faster than high compression. The data is usually smaller than low compressed data and larger than high compressed data.
-
*HIGH
The software performs the data compression using the LZ1 algorithm. High compression is usually slower than medium and low compression and the data is usually smaller than medium or low compressed data.
Note
If the save is running while other jobs on the system are active and software compression is used, the overall system performance may be affected.
Use Optimized Scan
Select this check box to have the software use optimized scan for the backup operation.
When you select this option, the scan duration for full, incremental and differential backups is reduced because the software runs the backup operations without scanning each object that is part of the content.
Optimized scan applies to the following backup types:
-
Library file system data backups
-
UNIX type file system data backups
Optimized scan applies to the Library file system data backup and the UNIX type file system data backups.
Optimized scan only supports subclient content with the OS "*" wildcard. You cannot use other wildcards for optimized scan.
Examples of allowed wildcards in subclient content
“/QSYS.LIB/APP1*.LIB"
"/DIR1/SUB_DIR/A*”
Examples of wildcards that are not allowed in subclient content
“/QSYS.LIB/A?.LIB”
“/DIR4/[!AEIOU]*”
Notes
-
Do not use exceptions under filters.
-
The software does not mark deleted items in the next incremental backup.
-
You can not select the Backup library content(s) as objects check box for subclients if you want to use the optimized scan feature (Subclient Properties dialog box, Content tab).
-
You can only add 300 or fewer object level paths per library as filters. You can use the "*" in the filter paths.
-
You can only select, omit or clear 300 or fewer objects per library for a restore operation.
-
You can use optimized scan with pre-defined subclients, but the “*ALLDLO” subclient or a subclient that contains custom content with a path that starts with “/QDLS” is not supported.
Backup library objects
Select each check box to include the objects in the backup.
Note: These are only applicable for a library file system.
-
Save file data(SAVFDATA)
Save the file contents and file description.
-
Spooled file data(SPLFDATA)
Save the output queue and all the spooled file data on the output queue.
-
Queue data (QDATA)
Save the queue contents and queue description.
-
Private authority(PVTAUT)
Save the private authority of all saved objects.