Use this command to display information about running and ended node-replication processes.
Issue this command on the server that acts as a source for replicated data.
By default, records about completed node-replication processes are retained for 30 calendar days. A calendar day consists of 24-hours, from midnight to midnight.
To display the retention period, issue the QUERY STATUS command. Check the value in the Replication Record Retention Period field. To change the retention period, issue the SET REPLRETENTION command.
Any administrator can issue this command.
>>-Query REPLIcation--node_name---------------------------------> .-*--------------------------. >--+----------------------------+-------------------------------> | (1) | '-----+-+-filespace_name-+-+-' | '-,--------------' | '-+-FSID--+----------' | (2) | '-,-----' .-NAMEType--=--SERVER-------. >--+---------------------------+--------------------------------> '-NAMEType--=--+-SERVER---+-' +-UNIcode--+ | (2) | '-FSID-----' .-CODEType--=--BOTH-----------. >--+-----------------------------+------------------------------> '-CODEType--=--+-BOTH-------+-' +-UNIcode----+ '-NONUNIcode-' .-DISplay--=--1--------------. >--+----------------------------+-------------------------------> '-DISplay--=--number_of_days-' >--+----------------------------------+-------------------------> '-PROCessid--=--process_identifier-' .-STatus--=--ALl---------. .-Format--=--Standard-----. >--+------------------------+--+-------------------------+----->< '-STatus--=--+-ALl-----+-' '-Format--=--+-Standard-+-' +-RUnning-+ '-Detailed-' +-ENded---+ '-FAiled--'
Specifies the name of the client node to be queried. You can use wildcard characters when you specify this name, with one exception. If the value of the NAMETYPE parameter is FSID, do not specify wildcard characters for the client node name. The FSID value indicates the file space identifier. File spaces with identical names can have different identifiers in different client nodes.
Specifies the name of the file space or the file space identifier (FSID) to be queried. A name or FSID is optional. If you do not specify a name or an FSID, all file spaces are queried.
A server that has clients with Unicode-enabled file spaces might have to convert the file space name. For example, the server might have to convert a name from the server code page to Unicode. For details, see the NAMETYPE parameter. If you do not specify a file space name, or if you specify only a single wildcard character for the name, you can use the CODETYPE parameter to limit the operation to Unicode file spaces or to non-Unicode file spaces.
Specifies how you want the server to interpret the file space names that you enter. You can use this parameter for Tivoli® Storage Manager clients that are Unicode-enabled and that have Windows, Macintosh OS X, or NetWare operating systems.
Specifies the type of file spaces to be included in the query. The default value is BOTH, which means that file spaces are included regardless of code page type. Use this parameter only if you enter a single wildcard character for the file space name. You can specify one of the following values:
Specifies the number of days of node replication history to display. The default value is 1, which displays information about running node replication processes and about processes that completed during the current calendar day. The maximum value is 9999.
You can specify a number that is the same as or less than the number of days that are specified as the retention period for the replication history records. If you specify a value that is more than the value of the replication retention period or more than the number of days that replication records have been collected, the server displays only the number of replication history records that are available. For example, suppose that the replication retention period is 30 days and that the replication process has been running for only 10 days. If you specify DISPLAY=20, only 10 days of replication history are displayed.
Restarting the server can cause the server to reuse process IDs. Reuse of process IDs can result in duplicate process IDs for separate processes.
query replication ironman
NodeName Filespace FSID Start Time End Time Status Phase
Name
---------------------------------—---------------–----–----–-------
IRONMAN /space 2 02/08/11 02/08/11 Ended None
21:44:19 21:48:14
query replication ironman format=detailed
Node Name: IRONMAN
Filespace Name: /space
FSID: 2
Start Time: 02/08/11 21:44:19
End Time: 02/08/11 21:48:14
Status: Ended
Process Number: 4
Command: replicate node ironman
Phase: None
Process Running Time: 0 Day(s) 0 Hour(s)
4 Minute(s)
Completion State: Complete
Reason For Incompletion: None
Backup Last Update Date/Time:
Backup Target Server:
Backup Files Needing No Action: 0
Backup Files To Replicate: 0
Backup Files Replicated: 0
Backup Files Not Replicated Due to Errors: 0
Backup Files Not Yet Replicated: 0
Backup Files To Delete: 0
Backup Files Deleted: 0
Backup Files Not Deleted Due To Errors: 0
Backup Files To Update: 0
Backup Files Updated: 0
Backup Files Not Updated Due To Errors: 0
Backup Bytes To Replicate (MB): 0
Backup Bytes Replicated (MB): 0
Backup Bytes Transferred (MB): 0
Backup Bytes Not Replicated Due
To Errors (MB): 0
Backup Bytes Not Yet Replicated (MB): 0
Archive Last Update Date/Time: 02/08/11 21:48:14
Archive Target Server: NIGLINA
Archive Files Needing No Action: 0
Archive Files To Replicate: 39,416
Archive Files Replicated: 39,206
Archive Files Not Replicated Due to Errors: 210
Archive Files Not Yet Replicated: 0
Archive Files To Delete: 0
Archive Files Deleted: 0
Archive Files Not Deleted Due To Errors: 0
Archive Files To Update: 0
Archive Files Updated: 0
Archive Files Not Updated Due To Errors: 0
Archive Bytes To Replicate (MB): 4,335
Archive Bytes Replicated (MB): 4,335
Archive Bytes Transferred (MB): 0
Archive Bytes Not Replicated
Due To Errors (MB): 0
Archive Bytes Not Yet Replicated (MB): 0
Space Managed Last Update Date/Time:
Space Management Target Server:
Space Managed Files Needing No Action: 0
Space Managed Files To Replicate: 0
Space Managed Files Replicated: 0
Space Managed Files Not Replicated
Due to Errors: 0
Space Managed Files Not Yet Replicated: 0
Space Managed Files To Delete: 0
Space Managed Files Deleted: 0
Space Managed Files Not Deleted
Due To Errors: 0
Space Managed Files To Update: 0
Space Managed Files Updated: 0
Space Managed Files Not Updated
Due To Errors: 0
Space Managed Bytes To Replicate (MB): 0
Space Managed Bytes Replicated (MB): 0
Space Managed Bytes Transferred (MB): 0
Space Managed Bytes Not Replicated
Due To Errors (MB): 0
Space Managed Bytes Not Yet Replicated (MB): 0
Total Files Needing No Action: 0
Total Files To Replicate: 39,416
Total Files Replicated: 39,206
Total Files Not Replicated Due To Errors: 210
Total Files Not Yet Replicated: 0
Total Files To Delete: 0
Total Files Deleted: 0
Total Files Not Deleted Due To Errors: 0
Total Files To Update: 0
Total Files Updated: 0
Total Files Not Updated Due To Errors: 0
Total Bytes To Replicate (MB): 4,335
Total Bytes Replicated (MB): 4,335
Total Bytes Transferred (MB):
Total Bytes Not Replicated
Due to Errors (MB):
Total Bytes Not Yet Replicated (MB):
Estimated Percentage Complete: 100
Estimated Time Remaining:
Estimated Time of Completion:
The same process number can have different start times. If a replication process starts and the server is restarted, the server begins assigning process numbers that begin with the number 1. Replication processes that start after a server restart can obtain process numbers that are already assigned to other replication processes in the replication history. To identify unique replication processes, use the start time.
If a file was stored in a deduplicated storage pool, the number of bytes in the stored file might be less than the number of bytes in the original file. This field represents the number of physical bytes in the original file.
The value in this field represents the actual number of file bytes sent to the target replication server. This value is calculated by subtracting the number of bytes not sent because of deduplication from the number of bytes to replicate.
If a file was stored in a deduplicated storage pool, the number of bytes in the stored file might be less than the number of bytes in the original file. This field represents the number of physical bytes in the original file.
For files stored in a deduplicated storage pool, the value in this field includes the number of bytes in the original file before duplicate extents were removed. If duplicate extents were already on the target replication server, the number of bytes in the original file is more than the number of bytes transferred.
Command | Description |
---|---|
CANCEL REPLICATION | Cancels node replication processes. |
QUERY ACTLOG | Displays messages from the server activity log. |
QUERY FILESPACE | Displays information about data in file spaces that belong to a client. |
QUERY NODE | Displays partial or complete information about one or more clients. |
QUERY PROCESS | Displays information about background processes. |
QUERY REPLNODE | Displays information about the replication status of a client node. |
QUERY REPLRULE | Displays information about node replication rules. |
REPLICATE NODE | Replicates data in file spaces that belong to a client node. |
SET REPLRETENTION | Specifies the retention period for replication history records. |