Field Description
Write Throughput The write throughput speed, expressed in MB/s, is the logical bandwidth. The %
bandwidth saving depends upon whether the store has been configured for
source-side deduplication with a low-bandwidth transfer policy, or target-side
deduplication with a high-bandwidth transfer policy. See Viewing the store
details on page 91.
Data Read The amount of user data that was read.
Read Throughput The read throughput speed. This only has one value because read throughput is
always high throughput without any % saving.
Client Identifier The client that initiated the data job, as defined on the backup application. The
IP address in the brackets is for information and not part of the client name. It is
best practice to ensure that a meaningful name is given to the client within the
backup application. If no client was defined on the backup application, only the
IP address is shown.
Start Time The time the job started.
End Time The time the job ended.
4. Click on an item within a list to display further details about it in the lower part of the page.
Table 33: Data job details
Field Description
Item Name The name of the item within data job. This name is created by the backup
application. Each data job may have multiple items.
Status The status of the data job item, as described in the previous table.
NOTE: The backup application must be configured to tidy up any incomplete or
orphaned items before retrying the job.
Status Information Status information, which explains the reason for the Status reported.
Start Time The time the job started.
End Time The time the job ended.
Client Identifier A name that identifies the client user who created the item.
Client Address Displays the IP address if the job was over Ethernet or the World Wide Port
Name/World Wide Node Name if the job was over Fibre Channel of the server
that created the item.
Application
Identifier
The name of the application that created the item.
Table Continued
StoreOnce Catalyst functions 107
To Next Page
Loading...
