DOCUMENTATION: What do entries in the 'bppllist <policy> -l' command indicate?
| Article:TECH42917 | | | Created: 2005-01-29 | | | Updated: 2008-01-20 | | | Article URL http://www.symantec.com/docs/TECH42917 |
Problem
DOCUMENTATION: What do entries in the 'bppllist
Solution
Manual: NetBackup (tm) 5.1 Command Reference
for UNIX, Page: 212
Modification Type: Addition
Modification:
The 'bppllist <policy> -l' command is not meant as a way to view policy information under normal operations. For a human readable output, use the "-L" or "-U" options.
The following is the output from the 'bppllist <policy> -l' command with an explanation of the entries.
The first entry is the CLASS entry. This indicates the start of a policy and includes the policy name.
Modification Type: Addition
Modification:
The 'bppllist <policy> -l' command is not meant as a way to view policy information under normal operations. For a human readable output, use the "-L" or "-U" options.
The following is the output from the 'bppllist <policy> -l' command with an explanation of the entries.
The first entry is the CLASS entry. This indicates the start of a policy and includes the policy name.
CLASS
<policy_name> <name> <options> <protocol> <offset>
<unused1>
The second entry is the NAMES entry. This is not currently used.
NAMES
The third entry is the INFO entry. This contains the policy attributes.
INFO
<client_type> <follow_nfs_mounts> <client_compress>
<priority> <proxy_client> <client_encrypt>
<disaster_recovery> <max_jobs_per_policy> <cross_mount_points>
<max_frag_size> <active> <collect_tir_info> <block_incr>
<ext_sec_info> <i_f_r_f_r> <streaming> <frozen_image>
<backup_copy> <effective_date> <class_id>
<number_of_copies> <checkpoint> <chkpt_interval>
<unused1> <pfi_enabled> <offhost_backup>
<use_alt_client> <use_data_mover>
<data_mover_type>
The fourth entry is the KEY entry. This stores the keyword for the policy.
KEY
keyword
The fifth entry is the BCMD entry. This stores the backup command.
BCMD
*NULL*
The sixth entry is the RCMD entry. This stores the restore command.
RCMD
*NULL*
The seventh entry is the RES entry. This stores the storage unit information required by the policy. A *NULL* entry indicates <Any Available> storage unit. There is an entry for each possible backup copy.
RES
storage_unit *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
The eighth entry is the POOL entry. This stores the volume pool information for the policy. There is an entry for each possible backup copy.
POOL
NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup
NetBackup
The ninth entry is the FOE entry. This stores the fail on error information. There is an entry for each possible backup copy.
FOE
0 0 0 0 0 0 0 0 0 0
The tenth entry is the CLIENT entry. This stores the client information.
CLIENT
hostname hardware OS priority <unused4> <unused3> <unused2>
<unused1>
The eleventh entry is the INCLUDE entry. This stores the backup selections for the policy. Additional INCLUDE lines will appear if more than one directive or pathname is in the policy.
INCLUDE
ALL_LOCAL_DRIVES
INCLUDE
<pathname>
The next entry is the SCHED entry. This contains seven subsections. Additional SCHED entries will appear if more than one schedule is configured for the policy.
SCHED
<label> <type> <max_mpx> <retention_level>
<unused> <incr_type> <incr_depends> *NULL*
<max_fragment> <calendar> <num_copies> <fail_on_error>
<unused>
SCHEDCALENDAR
SCHEDCALIDATES
<calendar> <date>
SCHEDWIN
<day_0_open_secs> <day_0_duration_secs> <day_1_open_secs>
<day_1_duration_secs> ... <day_7_open_secs>
<day_7_duration_secs>
SCHEDRES
<copy_0_stu> <copy_1_stu> ...
<copy_9_stu>
SCHEDPOOL
<copy_0_pool> <copy_1_pool> ...
<copy_9_pool>
SCHEDRL
<copy_0_retlevel> <copy_1_retlevel> ...
<copy_9_retlevel>
SCHEDFOE
<copy_0_failon_error> <copy_1_failon_error> ...
<copy_9_failon_error>
|
|
Legacy ID
278209
Article URL http://www.symantec.com/docs/TECH42917
Terms of use for this information are found in Legal Notices
Thank you.