DOCUMENTATION: What are the different fields in "bpimagelist -l" output?

Article:TECH5584

Created: 2000-01-15

Updated: 2012-08-23

Article URL http://www.symantec.com/docs/TECH5584

Article Type
Technical Solution

Product(s)

Show all

Environment

Show all

Subject

Show all

Languages

Show all

Problem

DOCUMENTATION: What are the different fields in "bpimagelist -l" output?

Solution

Manuals:
NetBackup™ 5.0 Commands for UNIX, pages 106-112
NetBackup™ 5.0 Commands for Windows, pages 103-109
NetBackup™ 5.1 Commands for UNIX, pages 106-112
NetBackup™ 5.1 Commands for Windows, pages 103-109
NetBackup™ 6.0 Commands for UNIX and Linux, pages 132-138
NetBackup™ 6.0 Commands for Windows, pages 125-131
NetBackup™ 6.5 Commands for UNIX and Linux, pages 137-144
NetBackup™ 6.5 Commands for Windows, pages 131-137
Symantec NetBackup™ 7.0 Commands for UNIX, Windows and Linux, pages 148-155
Symantec NetBackup™ 7.1 Commands Reference Guide for UNIX, Windows and Linux, pages 160-167
Symantec NetBackup™ 7.5 Commands Reference Guide for UNIX, Windows and Linux, pages 166-173

Modification type: Supplement

Modification:
The following entries appear in the output of the bpimagelist -l command. The entries for the IMAGE and FRAG lines are in the charts below. The HISTO line should always be -1 for all values.

# /usr/openv/netbackup/bin/admincmd/bpimagelist -l

IMAGE client_name, date1, date2, version, backupid, policy_name, client_type, proxy_client, creator, sched_label, sched_type, retention, backup_time, elapsed, expiration, compression, encryption, kbytes, num_files, copies, num_fragments, files_compressed, files_file, version, name1, options, primary, image_type, tir_info, tir_expiration, keywords, mpx, ext_security, raw, dump_lvl, fs_only, prev_BItime, BIfull_time, obj_desc, requestID, backup_stat, backup_copy, prev_image, jobid, num_resumes, resume_expr, ff_size, pfi_type, image_attrib[, ss_classification_id, ss_name, ss_completed, snap_time[, slp_version[, remoteExpiration, origin_master_server, origin_master_guid[, ir_enabled, client_charset, hold, indexing_status]]]]

HISTO -1 -1 -1 -1 -1 -1 -1 -1 -1 -1

FRAG copy_num, frag_num, KB, remainder, media_type, density, file_num, id/path, host, block_size, offset, media_date, dev_written, f_flags, media_desc/f_unused1, expiration, mpx, ret_level, checkpoint, resume_nbr, media_seq_no, media_subtype/unused4, ss_try_to_keep_date/unused3, copy_date/unused2, unused1[, kms_key_tag[, slp_dest_tag]]

The different fields in the IMAGE entry are:

Field	Field Header	Example	Description
1	Record Header	IMAGE
2	Client Name	myclient	The name of client being backed up.
3	Date1	0
4	Date2	0
5	Version	7	The version of the software 7 = 5.1
6	Backup ID	myclient_1115034756	The Backup ID recorded in the Database
7	Class Name	mypolicy	The name of the policy associated with this backup.
8	Client Type	13	The type of client: 0 = STANDARD, 1 = PROXY, 2 = NONSTANDARD, 3 = APOLLO_WBAK, 4 = ORACLE, 6 = INFORMIX, 7 = SYBASE, 8 = MAC, 9 = WINDOWS, 10 = NETWARE, 11 = BACKTRACK, 12 = AUSPEX_FASTBACKUP, 13 = WINDOWS_NT, 14 = OS2, 15 = SQL_SERVER, 16 = EXCHANGE, 17 = SAP, 18 = DB2, 19 = NDMP, 20 = FLASHBACKUP, 21 = SPLIT-MIRROR, 22 = AFS, 23 = DFS, 25 = LOTUS_NOTES, 26 = NCR_TERADATA, 27 = VAX_VMS, 28 = HP3000_MPE.
9	Proxy Client	NULL
10	Creator	root	The user who did the backup.
11	Schedule Label	Incr_bkup	The name of the schedule being used.
12	Schedule Type	4	The type of schedule: 0 = FULL, OBACKUP, INFORMIX ON-BAR, SYBASE, SQL_SERVER, NCR_TERRADATA, EXCHANGE, LOTUS_NOTES, BACKTRACK, SAP, DB2, NDMP, 1 = INCR - differentail Incremental, IINFORMIX ON-BAR INCREMENTAL, 2 = UBACKUP, UOBACKUP, UINFORMIX, USYBASE, USQL_SERVER, UNCR_TERADATA, UEXCHANGE, ULOTUS_NOTES, UBACKTRACK, USAP, UDB2, UNDMP, 3 = UARCHIVE, 4 = CINC or Cumulative Incremental
13	Retention Level	3	The retention level : 0 - 9 See Change NetBackup Configuration, under Retention Levels for the retention level.
14	Backup Time (Image Directory Name)	1115034756	The time the backup started. Use bpdbm -ctime 949042968 to get date and time.
15	Elapsed Time in Seconds	46	How long the backup took to run to completion.
16	Expiration (Image)	1116244356	When the images will expire use bpdbm -ctime 951721368 to get date and time.
17	Compression	0	0 = NO Software Compression not used, 1 = YES Software Compression used.
18	Encryption	0	0 = NO Encryption not used, 1 = YES Encryption used.
19	Kbytes Written	5612	The number of Kbytes backed up.
20	Number of Files	15	The number of files backed up.
21	Copies	1	The number of Copies 1 is 1 copy, 2 means the images has been duplicated.
22	Number of Fragments	1	The number of fragments.
23	Files File Compressed	0	0 = NO Files File not Compressed, 1 = YES Files files Compressed.
24	Files File	myclient_1115034756.INCR.f	The name of the files file in the image database.
25	Software Version	NULL
26	Name1	NULL
27	bpimagelist Input Options	0
28	Primary Copy	1	1 = Primary Copy, 2 = Duplicated Copy.
29	Image Type	0	0 = REGULAR or Normal Backup, 1 = PRE_IMPORT or Phase 1 import of this image is completed, 2 = IT_IMPORTED or Phase 2 import of this image is completed, this also means that an imported image was backed up.
30	True Image Recovery Info	0	0 = NO, True image recovery was not used, 1 = YES, True image recovery was used.
31	True Image Recovery Expiration	0	The expiration date for True image recovery use bpdbm -ctime to get the date and time, 0 here since True image recovery was not used.
32	Keywords	NULL	The keyword associated with the policy, NULL = no keyword used.
33	MPX	0	0 = no MPX used, else number of MPX per drive.
34	Extended Security Info	0	0 = NO Extended security info used, 1 = YES Extended security info used.
35	Individual File Restore from Raw	0	0 = Not used, this only applies to Auspex FastBackup and Flashbackup type classes.
36	Image Dump Level	0	For NDMP Incrementals.
37	File System Only	0	This is a flag used for restores.
38	Previous Block Incremental Time	0	Used for BLIB, 0 = NOT used, else previous BLIB backup time.
39	Block Incremental Full Time	0	Used for BLIB, 0 = NOT used, else current BLIB backup time.
40	Object Description	NULL
41	Request ID	0
42	Backup Status	0	0 = Succesful, etc taken from Job Monitor = Status Codes.
43	Backup Copy	0
44	Prev Backup Image	NULL
45	Job ID	703	The job ID.
46	Number of Resumes	0
47	Resume Expiration	0
48	Files File Size	348	The files file size in bytes.
49	PFI Type	0
50	Image Attribute	0

In NetBackup 6.5, storage lifecycles were introduced. Additional fields were added to bpimagelist output:

Field	Field Header	Example	Description
51	Data Classification ID	(a long hexadecimal value)	ID value corresponding to Data Classification selected (for example, "Platinum")
52	Storage Lifecycle Policy	my_stl_policy_name	If a STL policy was used, its name
53	STL_Completed	3	The numerical value of the status of storage lifecycle service completion
54	Snap Time	0	The creation date of the snapshot (if applicable).

In NetBackup 6.5.5, one more field was added:

Field	Field Header	Example	Description
55	SLP Version	1	"Version" of the SLP policy

In NetBackup 7.1, Automatic Image Replication was introduced, necessitating three more new fields:

Field	Field Header	Example	Description
56	Remote Expiration	1299000000	Remote copy expiration (Use bpdbm -ctime to convert to date)
57	Origin Master Server	mymaster	Hostname of the original master server
58	Origin Master GUID	(long id string)

These fields were added in NetBackup 7.5:

Field	Field Header	Example	Description
59	IR Enabled	1	0 = NO, 1 = YES Catalog this snapshot for later use in Instant Recovery or a SLP
60	Client Character Set	1	integer representation of the charset used when the client calls bpcd
61	Image on Hold	0	0 = No copies on hold, nonzero = Binary representation of which copy/copies are marked for legal hold
62	Indexing Status	0	File system metadata associated with the backup image may be indexed for NetBackup Search. 0 = NOT_ENABLED, 1 = ENABLED, 2 = COMPLETED, 3 = FAILED

The different fields in the FRAG entry are:

Field	Field Header	Example	Description
1	Record Header	FRAG
2	Copy Number	1	The copy number. Default: 1 for the first copy, 2 for the second copy, etc.
3	Fragment Number	1	The fragment number. Default: 1 for the first copy, 2 for the second copy, etc. A fragment of -1 indicates a TIR backup.
4	Kilobytes	32	The size in kilobytes of the fragment.
5	Remainder	0	The remainder. This will be a numeric value.
6	Media Type	2	The media type of the fragment. This will be a numeric value that indicates the type of media used.
7	Density	13	The density of the fragment. This will be a numeric value that indicates the density of the media used.
8	File Number	48	The file number. This will be a numeric value that indicates the file number on the media. This number will be displayed in the Activity Monitor under the Job Detailed Status as "positioning to file ".
9	ID/Path	A00001	The Media ID or BasicDisk disk path the backup was written to. All disk types other than BasicDisk will display a Media ID of the form "@xxxxx"
10	Host	server1	The media server that did the backup. This will appear as the hostname of the media server.
11	Block Size	65536	The block size used when writing the backup. This will appear as a number. Ex. 32768
12	Offset	155	The offset on the media. This will appear as a numeric value.
13	Media Date	1112641625	The media date. This is the "Assign Time" of this media when the image was written. This will appear as a UNIX time value.
14	Device Written On	2	The device written on. This will appear as the drive index, or -1 for disk based backups.
15	f_flags	0	This is a internal flag. This should always be 0.
16	Media Descriptor	NULL	In 6.x, disk based backup location information; In 5.x, "f_unused1" should always be 0
17	Expiration	1116244356	The expiration time of the image. This will appear as a UNIX time value.
18	MPX	0	The value for multiplexing. A value of 0 indicates multiplexing was not used. A value of 1 indicates multiplexing was used.
19	Retention Level	655357
20	Checkpoint	0
21	Resume NBR	0
22	Media Seq #	0
23	Media Subtype	1	In 6.x, type of Disk Storage Unit; In 5.x, "Unused4" should always be 0
24	Try to Keep Date	0	In 6.5 and above, for the first fragment of each copy - expiration date for capacity-managed copies written using a Lifecycle policy, otherwise 0; In 5.x and 6.0; "Unused3" should always be 0.
25	Copy Creation Time	1201888951	In 6.5 and above, for the first fragment of each copy - the time that the copy was written, otherwise 0; In 5.x and 6.0; "Unused2" should always be 0.
26	Unused1	0	This is unused and should always be 0.