QUERY REPLNODE (Display information about replication status for a client node)

Use this command to display the number of files that are stored for each replicated file space. Information is displayed about file spaces for every client node that is configured for replication.

A client node is configured for replication if it is enabled or disabled.

Privilege class

Any administrator can issue this command.

Syntax


                   .-,-----------------.   
                   V                   |   
>>-Query REPLNode--------node_name-----+------------------------>

>--+--------------------+--------------------------------------><
   '-target_server_name-'

Parameters

node_name (Required)

Specifies the client node that owns the files about which you want information. You can specify one or more names. If you specify multiple names, separate the names with commas. Do not use intervening spaces. You can use wildcard characters to specify multiple names.

Information about client nodes that match the file criteria, but that are not configured for replication, is not displayed.

target_server_name

Specifies the name of the replication server to query for replication information. This parameter is optional. If you do not specify a value for this parameter, the server that is the default target for replicated data is queried.

As the value for this parameter, you can also specify a server that was formerly a target for replicated data.

The client nodes that are defined to a replication server can be the source or the target of replicated data. To determine whether a particular client node is sending or receiving data, issue the QUERY NODE command. Look for the value Send or Receive in the Replication Mode field of the output.

To display the name of the active target replication server, issue the QUERY STATUS command, and look for the name in the Target Replication Server field.

Example: List client node files on a source and a target replication server

The name of the client node is NODE1.

query replnode *

Node   Type   Filespace  FSID   Files on   Replication   Files on
Name            Name             Server     Server (1)   Server (1)
-------------------------------------------------------------—-----
NODE1  SpMg    /hmsmfs    1      1                        	  
NODE1  Bkup    /lspace2   2      27                           
NODE1  Arch    /lspace2   2      22        TGTSRV     22      
NODE1  Bkup    /lspace    3      18,096                       
NODE1  Arch    /lspace    3      61,150    TGTSRV     61,150  
NODE2

The number of files that are displayed for the replication servers might be different for the following reasons:

The output of the QUERY REPLNODE command displays the number of files obtained from the occupancy table. The occupancy table contains only files that have a length greater than zero. Files that have a length of 0 and have been replicated are not reflected in this output.
If only active data is replicated to the target server, the number of files that are displayed for the source server will be larger than the number of files that are displayed on the target server. The reason for the difference is that the source replication server has both active and inactive data, and the target server has only active data.
A client node might have data that was exported from the source replication server and imported to the target replication server. If that data was synchronized and if the client node also stored data to the target replication server, then the number of files on the target replication server will be greater than the number of files stored as a result of export-and-import operations and replication.
When you replicate node data from a source server prior to version 7.1, to a target server at version 7.1 or later, files that are larger than 10 GB are split in to smaller files if the SPLITLARGEOBJECTS parameter for the node definition is set to Yes. Each of these split files are counted on the target server.

Field descriptions

Node Name

The name of the client node that owns the files.

Type

The type of data. If this field is blank, the client node is configured for replication, but it does not have data on the replication server. In the example output, NODE2 is configured for replication, but it does not have backup, archive, or space-managed data.

The following values are possible:

Arch: Archive data
Bkup: Backup data
SpMg: Data that was migrated by IBM® Tivoli® Storage Manager for Space Management clients

Filespace Name

The name of the file space that belongs to the node.

If this field is blank, the client node is configured for replication, but it does not have data on the replication server.

File space names can be in a different code page or locale than the server. If they are, the names in the Operations Center and the administrative command-line interface might not be displayed correctly. Data is backed up and can be restored normally, but the file space name or file name might be displayed with a combination of invalid characters or blank spaces.

If the file space name is Unicode-enabled, Tivoli Storage Manager converts the name to the server code page for display. The success of the conversion depends on the operating system, the characters in the name, and the server code page. Conversion can be incomplete if the string includes characters that are not available in the server code page or if the server cannot access system conversion routines. If the conversion is incomplete, the name might contain question marks, blanks, unprintable characters, or ellipses (...).

FSID

The file space identifier for the file space. The server assigns a unique FSID when a file space is initially stored on the server. If this field is blank, the client node is configured for replication, but it does not have data on the replication server.

Files on Server

The number of backup, archive, and space-managed files on the server on which this command is issued. If this field is blank, the client node is configured for replication, but it does not have data on the replication server.

Replication Server (1)

The name of the replication server that is being queried for information. If this field is blank, one or more of the following conditions might exist:

The file space of the node on the replication server where the command was issued does not have any data.
The client node is not defined on replication server (1).
The client node is defined on replication server (1), but the node is not configured for replication.
The corresponding file space on replication server (1) does not have data or the file space is not defined.

Files on Server (1)

The number of files for the data type that are stored on the target replication server. This field can be blank. If it is, one or more of the following conditions might exist:

Replication server (1) does not have any data.
The client node is not defined on replication server (1).
The client node is defined on replication server (1), but the node is not configured for replication.
The corresponding file space on replication server (1) does not have data or the file space is not defined.

Related commands

Table 1. Commands related to QUERY REPLNODE
Command	Description
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 REPLICATION	Displays information about node replication processes.
QUERY REPLRULE	Displays information about node replication rules.
REPLICATE NODE	Replicates data in file spaces that belong to a client node.
UPDATE REPLRULE	Enables or disables replication rules.