Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Negative fragment numbers

Updated: 21 May 2010 | 8 comments
rjrumfelt's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

A did some searching around and couldnt really find anything.

I was just curious, does anyone know what a negative fragment # represents?

Thanks

discussion Filed Under:

Comments

Andy Welburn's picture
04
Nov
2009
0 Votes 0
Login to vote

Are you looking at bpimmedia -l command?

If so, from the Help pages:

Fields for the -l format are as follows:

Line 1
IMAGE - Identifies the start of an image entry
Client - Client for the backup that produced this image
Version - Image-version level
Backup-ID - Unique identifier for the backup that produced this image
Policy - Policy name
Policy type - 0 denotes Standard, etc. Run bpimmedia -L or refer to bpbackup(1M) to interpret the policy-type value as a policy-type name.
Schedule - Schedule name
Type - Schedule type (full, etc.)
RL - Retention level (0-24)
Files - Number of files
Expiration date or time - The expiration date of the first copy to expire. It appears in the Expires field of the fragment, which is described later (system time). 0 denotes an image in progress or failed.
C - Compression; 1 (yes) or 0 (no)
E - Encryption; 1 (yes) or 0 (no)

Line 2_n+1
FRAG - Identifies a fragment line in an image entry
Copy - Copy number of this fragment
Frag - Fragment number, or -1 for a TIR fragment
KB - Size of the fragment in kilobytes
MPX - Flag that indicates whether this copy is multiplexed, 1(yes) or 0(no) (applies only when fragment number is 1)
Expires - The expiration date of this copy in system time (applies only when fragment number is 1)
Disk type - BasicDisk (1), NearStore (2), SAN Disk (4)
Disk pool name - Only applies to SAN Disk. All other disk types show *NULL*.
Media ID - volume path if NearStore, path if BasicDisk, or volume name if SAN Disk
Density - Density value (applies only to removable media). Run bpimmedia -L or bpmedialist -mlist -L -m mediaid to interpret the density value as a density label
Fnum - File number; the n-th backup on this medium (applies only to removable media)
MediaID - Media ID or absolute path where the image is stored
Host - Server whose catalog contains this image
Block size - Number of kilobytes per block for this medium
Off - Offset
Media date - Time this medium was allocated (system time)
DWO - Device Written On (applies only to removable media)

Regards Andy

"It's not too late to panic ..."

rjrumfelt's picture
04
Nov
2009
0 Votes 0
Login to vote

That is interesting

I did not realize we had TIR set up for our environment.

You learn something every day

Andy Welburn's picture
04
Nov
2009
0 Votes 0
Login to vote

Must be set up on one or two of your policies,

or we're looking at two totally different things!! :D

Regards Andy

"It's not too late to panic ..."

rjrumfelt's picture
04
Nov
2009
0 Votes 0
Login to vote

No, you're right

I'm just getting my info from an "Images on Tape" report from the GUI.  I'm actually seeing them for my catalog backup.

Andy Welburn's picture
04
Nov
2009
0 Votes 0
Login to vote

You do learn something new everyday then!

Didn't realise TIR (with move detection) is on by default for Catalog Backups

Regards Andy

"It's not too late to panic ..."

rjrumfelt's picture
04
Nov
2009
0 Votes 0
Login to vote
Andy Welburn's picture
04
Nov
2009
0 Votes 0
Login to vote

Not counting.

 

 

 

 

 
 

 
 
 (yeah, 2 ;) ) (in 7 minutes)

Regards Andy

"It's not too late to panic ..."

Andy Welburn's picture
04
Nov
2009
0 Votes 0
Login to vote

But on a more serious note:

just checked our "Images on Tape" report (Windows GUI, 6.5.4), for one of our Catalog tapes, & the entries for fragment number are either 1 or TIR (no negatives anywhere)

Regards Andy

"It's not too late to panic ..."