BFS Data

System Programmer Reference › Summary and Detail Reports › Restore Job Detail Report › Minidisk, File Space, Directory, or Abstract Domain Detail › BFS Data

BFS Data

For each directory in a BFS file space, the report includes the following information for each object:

For regular files, this field shows the number of bytes in the file. For other BFS objects, this field shows a code that indicates the object type. The code can be one of the following:

Code	Object Type
C	Character special file
E	External link
L	Symbolic link
P	Named pipe

Character special files and external links can have a secondary code.
For character special files the secondary code indicates the device number associated with the file. It can be one of the following:

Secondary code	Device number
3	/dev/tty
4	/dev/null

For external links the secondary code indicates the type of external link associated with the file. It can be one of the following:

Secondary code	Type of external link
1	CMSEXEC
2	CMSDATA
3	MOUNT
nnn	CODE (where nnn is a user-defined code with a value of 100-200)

Date and time the object was last updated
Attributes assigned to the file by CA VM:Backup when the file was backed up; this field contains an M if the file was migrated, or a hyphen if it was not
Number of links to an object (applies to regular files only)
Inode, which is the hexadecimal number that uniquely identifies the data portion of the object
Name of the object
Whether the object was to be created, erased, or replaced; this field contains SCANNED if the job specified NEWFILE and the file already existed
If the object was renamed when restored, the new name of the object

Note: For BFS file spaces, the detail section lists objects to be restored. This list is not a list of objects that were restored. To determine whether all listed objects were restored, you must check the Summary of All File Spaces report to determine whether CA VM:Backup encountered errors restoring these objects.