How to interpret the fields in the bpcatlist output

Article: 100016710
Last Published: 2012-09-20
Ratings: 0 0
Product(s): NetBackup & Alta Data Protection

Description

The bpcatlist output shows the catalog archiving related information for images within the NetBackup image database.  Depending on the command line arguments, it may show images that have been archived, or those that have never been archived, or those that have been archived and restored.

The following is an example of the bpcatlist output for a client called mybox. Most of the fields are self-explanatory, but some can be confusing. 

# cd /usr/openv/netbackup/bin/admincmd
# ./bpcatlist -client mybox

Backupid         Backup Date  Files  Size  Sched  Policy  Catarcid   S C Files file
mybox_1102660477 <date>       2180   370M  FULL   policy  1103729447 2 1 policy_1102660477_FULL.f
mybox_1102631905 <date>       6      200k  UBAK   policy  1103729447 2 0 policy_1102631905_UBAK.f

Here is an explanation of each of the fields:

Backupid - The backup ID.
Backup Date - The date of the backup.
Files - The number of files backed up under the backup ID.
Size - The amount of data backed up under the backup ID.
Sched - The Schedule used for the backup.
Policy - The Policy used for the backup.
Catarcid - The Catalog Archive ID.  The value is 0 if the backup image either has not been archived or has been archived but then restored.  If non-zero, it is the UNIX ctime from the backup ID of the catalog archiving job that was started by bpcatarc . 
S - Indicates whether the files file is currently present on disk;  1 = present  2 = not present.  If bpcatarc is run without bpcatrm the value is typically 1, if bpcatrm is run the value is typically 2.  Other operations that remove or restore the *.f file will affect this value.
C - Indicates whether the files file was compressed or was not compressed before archiving; 0 = not compressed, 2 = compressed
Files file - The name that the files file for the backup ID should have.

Consider the following example which focuses on the Catarcid and S columns.

Backupid         ..   Catarcid   S C Files File
server1_1159166059 .. 1164408549 2 1 FS_1159166059_INCR.f
server1_1048917731 .. 1148328124 1 1 FS_1048917731_INCR.f
server1_1147238391 ..          0 1 0 FS_1147238391_INCR.f
server1_1158992617 ..          0 2 0 FS_1158992617_INCR.f


These four images demonstrate various states:


The first image (server1_1159166059) has a catarcid of 1164408549 which indicates the image was archived on November 24th 2006.  The S value of 2 indicates the .f file is no longer present on the disk.  The C value of 1 indicates the .f file was compressed.

The second image (server1_1048917731) has catarcid of 1148328124, which indicates the image was archived.  The S value of 1 however, indicates the .f file is present on disk and the C value of 1 indicates the .f file is compressed.

The third image (server1_1147238391) has a catarcid of 0, which means that either it has not be archived, or if previously archived then it has been restored.  The S value of 1 confirms that the files file is present on disk and the C value of 0 shows the .f file is not compressed.
 
The fourth image (server1_1158992617) has a catarcid of 0 and a S value of 2 indicating that the files file is missing and not associate with a catalog archive image.  The C value of 0 shows that the file, although now missing, was not compressed.

 

 

Was this content helpful?