During a backup, by default Tivoli® Storage Manager displays the status of each file it attempts to back up.
Tivoli Storage Manager reports the size, path, file name, total number of bytes transferred, and whether the backup attempt was successful for the file. These are also recorded in the dsmsched.log file for scheduled commands.
The Web client and backup-archive
client Java™ GUI provide a Task
List window that displays information about files during
processing. When a task completes, a Backup Report window
displays processing details. Click the Help button
in the Backup Report window for context help.
The Web client and backup-archive client GUI
provide a Task List window that displays information
about files during processing. When a task completes, a Backup
Report window displays processing details. Click the Help button
in the Backup Report window for context help.
On the backup-archive command line, the name of each file is displayed after it is sent to the server. The progress indicator shows overall progress.
| Informational message | Meaning |
|---|---|
| Directory--> | Indicates the directory that you back up. |
| Normal File-->. |
Any file that is not a directory,
symbolic link, or special file. |
| Special File--> |
Special files define devices for
the system or temporary files that are created by processes. There
are three basic types of special files: FIFO (first-in, first-out),
block, and character. FIFO files are also called pipes. Pipes are
created by one process to temporarily allow communication with another
process. These files cease to exist when the first process finishes.
Block and character files define devices. Tivoli Storage Manager processes
only device and named pipe special files. Socket special files are
not processed. |
| Symbolic Link--> |
Indicates that Tivoli Storage Manager backs
up a symbolic link. |
| Updating--> | Indicates that only the file meta data is sent, not the data itself. |
| Expiring--> | Indicates an object (file or directory) on the server that no longer exists on the client is expired and made inactive on the server. |
| Subfile--> |
Indicates that a file is processed
using adaptive subfile backup. The file size that is indicated in
this message is the size of the entire file, not the amount of data
sent. |
| Total number of objects inspected: |
As indicated. When using journal-based
backup (AIX® and Windows only), the number of objects that
are inspected might be less than the number of objects that are backed
up. When you use the snapshot difference incremental backup, the number of objects that are inspected is zero. The number is zero because the client performs an incremental backup of the files that NetApp reported as changed. The client does not scan the volume looking for files that have changed. |
| Total number of objects backed up: | As indicated. |
| Total number of objects encrypted: | This is a count of the objects that were encrypted during backup or archive processing. |
| Data encryption type: | Specifies the encryption algorithm type (e.g 256-bit AES), if one or more objects are encrypted during backup or archive processing. |
| Total number of objects updated: | These are files whose attributes, such as file owner or file permissions, have changed. |
| Total number of objects rebound: | See Bind management classes to files for more information. |
| Total number of objects deleted: | This is a count of the objects that are deleted from the client workstation after being successfully archived on the server. The count is zero for all backup commands. |
| Total number of objects expired: | See the section about full and partial incremental backup for more information. |
| Total number of objects failed: | Objects can fail for several reasons. Check the dsmerror.log for details. |
| Total snapshot difference objects: |
For snapshot difference incremental backups, this represents
the total number of objects backed up and the total number of objects
expired. |
| Total objects deduplicated: | Specifies the number of files that are deduplicated. |
| Total number of bytes inspected: |
Specifies the sum of the sizes of
the files that are selected for the operation. For example, the total
number of bytes that are inspected for this command is the number
of bytes that are used on the volume /Volumes/BUILD: |
| Total bytes before deduplication: | Specifies the number of bytes to send to the Tivoli Storage Manager server if the client does not eliminate redundant data. Compare this amount with Total bytes after deduplication. Includes metadata size and might be greater than bytes inspected. |
| Total bytes after deduplication: | Specifies the number of bytes that are sent to the Tivoli Storage Manager server after deduplication of the files on the client computer. Includes metadata size and might be greater than bytes processed. |
| Total number of bytes inspected: |
Specifies the sum of the sizes of
the files that are selected for the operation. For example, the total
number of bytes inspected for this command is the number of bytes
used in the directory C:\Users |
| Total number of bytes processed: | Specifies the sum of the sizes of the files that are processed for the operation. |
| Total number of subfile objects: |
The number of files processed using
adaptive subfile backup. |
| Data transfer time: | The total time to transfer data across the network. Transfer statistics might not match the file statistics if the operation was retried due to a communications failure or session loss. The transfer statistics display the bytes attempted to be transferred across all command attempts. |
| Network data transfer rate: | The average rate at which the network transfers data between the client and the server. This is calculated by dividing the total number of bytes transferred by the time to transfer the data over the network. The time it takes to process objects is not included in the network transfer rate. Therefore, the network transfer rate is higher than the aggregate transfer rate. |
| Aggregate data transfer rate: | The average rate at which Tivoli Storage Manager and
the network transfer data between the client and the server. This
is calculated by dividing the total number of bytes transferred by
the time that elapses from the beginning to the end of the process.
Both Tivoli Storage Manager processing
and network time are included in the aggregate transfer rate. Therefore,
the aggregate transfer rate is lower than the network transfer rate.
Note: On occasion, the aggregate
data transfer rate might be higher than the network data transfer
rate. This is because the backup-archive client can have multiple
simultaneous sessions with the backup server.
If you set the resourceutilization option, Tivoli Storage Manager attempts
to improve performance and load balancing by using multiple sessions
when it backs up a file space or other set of files. When multiple
sessions are open during backup, the data transfer time represents
the sum of the times reported by all sessions. In this case, aggregate
data transfer time is incorrectly reported as higher. However, when
running with a single session, the aggregate data transfer rate should
always be reported as lower than the network data transfer rate. |
| Objects compressed by: | Specifies the percentage of data sent over the network divided by the original size of the file on disk. For example, if the net data-bytes are 10K and the file is 100K, then Objects compressed by: == (1 - (10240/102400)) x 100 == 90%. |
| Deduplication reduction: |
Specifies the size of the duplicate
extents that were found, divided by the initial file or data size.
For example, if the initial object size is 100 MB, after deduplication
it is 25 MB. The reduction would be: (1 - 25/100) * 100 = 75%. |
| Total data reduction ratio: | Adds incremental and compression effects. For example, if the bytes inspected are 100 MB and the bytes sent are 10 MB, the reduction would be: (1 - 10/100) * 100 = 90% |
| Subfile objects reduced by: |
Expresses the savings achieved by
adaptive subfile backup as a percentage of actual bytes sent versus
actual file sizes. For example, if the actual sizes of the files backed
us is 100 MB, but with adaptive subfile backup, only 25 MB were sent,
then the reduction would be: (1 - (25 MB/100 MB)) x 100 == 75%. Note: The
calculation considers all files that were processed, not only those
files that were processed by adaptive subfile backup. The calculation
does not include the effect of compression.
|
| Elapsed processing time: | The active processing time to complete a command. This is calculated by subtracting the starting time of a command process from the ending time of the completed command process. |
| Total number of bytes transferred: | As indicated. |
| LanFree bytes transferred: |
The total number of data bytes transferred
during a lan-free operation. If the enablelanfree option
is set to no, this line will not appear. |
| Total number of bytes inspected: |
A sum of sizes of files selected
for the operation. |
| Total objects deduplicated: |
The number of files that have been
deduplicated. |