UPDATE FILESPACE (Update file-space node-replication rules)

Use this command to update file-space replication rules. You can also enable or disable replication of data to which a file space rule applies.

Issue this command on the server that acts as a source for replicated data.

Privilege class

To issue this command, you must have system privilege, unrestricted policy privilege, or restricted policy privilege for the policy domain to which the client node with the file space to be updated belongs.

Syntax


>>-UPDate FIlespace--node_name--file_space_name----------------->

   .-NAMEType--=--SERVER-------.   
>--+---------------------------+-------------------------------->
   '-NAMEType--=--+-SERVER---+-'   
                  +-UNIcode--+     
                  |      (1) |     
                  '-FSID-----'     

   .-CODEType--=--BOTH-----------.   
>--+-----------------------------+------------------------------>
   '-CODEType--=--+-UNIcode----+-'   
                  +-NONUNIcode-+     
                  '-BOTH-------'     

                .-,------------------------.   
                V                    (2)   |   
>--DATAType--=------+-BACKup-------+-------+-------------------->
                    +-ARCHive------+           
                    '-SPACEManaged-'           

>--+--------------------------------------------------------+--->
   |             (3)                                        |   
   '-REPLRule--=--------+-ALL_DATA----------------------+---'   
                        |             (4)               |       
                        +-ACTIVE_DATA-------------------+       
                        +-ALL_DATA_HIGH_PRIORITY--------+       
                        |                           (4) |       
                        +-ACTIVE_DATA_HIGH_PRIORITY-----+       
                        +-DEFAULT-----------------------+       
                        '-NONE--------------------------'       

>--+-------------------------------------+---------------------><
   |                               (3)   |   
   '-REPLState--=----+-ENabled---+-------'   
                     +-DISabled--+           
                     '-PURGEdata-'

Notes:

You cannot specify a file space identifier (FSID) if you use wildcard characters for the client node name.
You can specify each rule only once.
You must specify either the REPLRULE or the REPLSTATE parameter on this command.
The ACTIVE_DATA and ACTIVE_DATA_HIGH_PRIORITY rules are valid only if you specify DATATYPE=BACKUP.

Parameters

node_name (Required)

Specifies the client node to which the file space belongs. You can use wildcard characters to specify this name. However, file space identifiers can be different among client nodes for the same file space. Therefore, you cannot specify wildcard characters for the client node name and FSID as the value for the NAMETYPE parameter.

file_space_name (Required)

Specifies the name of the file space to be updated. You can use wildcard characters or a comma-delineated list to specify names.

For a server that has clients with Unicode-enabled file spaces, you might have to make the server convert the file space name that you enter. For example, you might have to make the server convert a name from the server code page to Unicode. For details, see the NAMETYPE parameter. 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.

File space names are case-sensitive. To determine the correct capitalization for the file space to be updated, use the QUERY FILESPACE command.

NAMEType

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 Unicode-enabled and that have Windows, Macintosh OS X, or NetWare operating systems.

Use this parameter only when you enter a partly-qualified or fully-qualified file space name. The default value is SERVER. You can specify one of the following values:

SERVER: The server uses the server code page to interpret file space names.
UNIcode: The server converts file space names from the server code page to the UTF-8 code page. The success of the conversion depends on the operating system, on the characters in the name, and the server code page. Conversion can fail 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 fails, the name can contain question marks, blanks, or ellipses (...).
FSID: The server interprets file space names as file space identifiers.

CODEType

Specifies the type of file spaces to be included in node replication processing. The default value is BOTH, meaning that file spaces are included regardless of code page type. Use this parameter only when you enter a single wildcard character for the file space name. You can specify one of the following values:

UNIcode: Specifies only file spaces that are in Unicode.
NONUNIcode: Specifies only file spaces that are not in Unicode.
BOTH: Specifies all file spaces regardless of code page type.

DATAType (Required)

Specifies the data type to which a replication rule applies. To specify multiple data types, separate the names with commas and no intervening spaces. You can specify the following values:

BACKup: Specifies the backup data type.
ARCHive: Specifies the archive data type.
SPACEManaged: Specifies the space-managed data type.

REPLRule

Specifies the replication rule that applies to a data type. You cannot use wildcards. If you specify multiple data types, the replication rule applies to each data type. For example, if you specify DATATYPE=BACKUP,ARCHIVE, the replication rule applies to backup data and to archive data.

Restriction: The REPLRULE parameter is optional. However, if you do not specify it, you must specify the REPLSTATE parameter.

You can specify normal-priority replication or high-priority replication rules. In a replication process that includes both normal and high-priority data, high-priority data is replicated first. Before you specify a rule, consider the order in which you want the data to be replicated.

For example, suppose that a file space contains active backup data and archive data. Replication of the active backup data is a higher priority than the archive data. To prioritize the active backup data, specify DATATYPE=BACKUP REPLRULE=ACTIVE_DATA_HIGH_PRIORITY. To assign a normal priority to archive data, issue the UPDATE FILESPACE command again, and specify DATATYPE=ARCHIVE REPLRULE=ALL_DATA.

You can specify the following rules:

ALL_DATA

Replicates backup, archive, or space-managed data. The data is replicated with a normal priority.

ACTIVE_DATA

Replicates only the active backup data in a file space. The data is replicated with a normal priority.

Attention: If you specify ACTIVE_DATA and one or more of the following conditions are true, inactive backup data on the target replication server is deleted, and inactive backup data on the source replication server is not replicated.

When a Tivoli Storage Manager version earlier than Version 7.1.1 is installed on either the source or target replication servers.
When you are using the REPLICATE NODE command with the FORCERECONCILE=YES parameter.
When you are running the initial replication of a file space after you configure replication, restore the database, or upgrade both the source and target replication servers from a Tivoli Storage Manager version earlier than V7.1.1.

If the previous conditions are not true, all new and changed files since the last replication are replicated, including inactive files, and files are deleted when they expire.

ALL_DATA_HIGH_PRIORITY

Replicates backup, archive, or space-managed data. The data is replicated with a high priority.

ACTIVE_DATA_HIGH_PRIORITY

This rule is the same as the ACTIVE_DATA replication rule except data is replicated with a high priority.

DEFAULT

Data is replicated according to the client node rule for the data type.

For example, suppose that you want to replicate the archive data in all the file spaces that belong to a client node. Replication of the archive data is a high priority. One method to accomplish this task is to specify DATATYPE=ARCHIVE REPLRULE=DEFAULT for each file space. Ensure that the client replication rule for archive data is set to ALL_DATA_HIGH_PRIORITY or to DEFAULT. If the client replication rule is DEFAULT, the server replication rule for archive data must be set to ALL_DATA_HIGH_PRIORITY.

NONE

Data is not replicated. For example, if you do not want to replicate the space-managed data in a file space, specify DATATYPE=SPACEMANAGED REPLRULE=NONE.

REPLState

Specifies the replication state for a data type. If you specified multiple data types, the state applies to all the data types. For example, if you specified DATATYPE=BACKUP,ARCHIVE, the state applies to backup data and archive data.

The REPLSTATE parameter is optional. However, if you do not specify it, you must specify the REPLRULE parameter. You can specify one of the following values for the REPLSTATE parameter:

ENabled: Specifies that the data type is ready for replication.
DISabled: Specifies that replication does not occur until you enable it.
PURGEdata: Specifies that data is deleted from the target replication server. The type of data deleted is the type of data specified by the DATATYPE parameter. For example, if you specify DATATYPE=BACKUP,ARCHIVE and REPLSTATE=PURGEDATA, backup data and archive data are deleted from the file space on the target replication server.
After the data is deleted, the REPLSTATE parameter is set to DISABLED, preventing future replication of the data type or types. The replication rule for the data type is set to DEFAULT.

Remember: PURGEDATA processing does not delete file spaces. Only data is deleted. The file space shows as empty in the output of the QUERY OCCUPANCY command.

Example: Update replication rules for two data types

NODE1 has three file spaces: /a, /b, and /c. The replication rules for all file spaces are set to ALL_DATA. However, you want to replicate the backup and archive data in file space /a before the data in other file spaces is replicated.

update filespace node1 /a datatype=backup,archive replrule=
       all_data_high_priority

Example: Update replication rules for two data types

NODE2 has two file spaces: /a and /b. You want to temporarily suspend replication of all data in file space /b.

update filespace node2 /b datatype=backup,archive,spacemanaged
 replstate=disabled

Related commands

Table 1. Commands related to UPDATE FILESPACE
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 STATUS	Displays the settings of server parameters, such as those selected by the SET commands.
REPLICATE NODE	Replicates data in file spaces that belong to a client node.
SET REPLRETENTION	Specifies the retention period for replication history records.
UPDATE NODE	Changes the attributes associated with a client node.
UPDATE REPLRULE	Enables or disables replication rules.
VALIDATE REPLICATION	Verifies replication for file spaces and data types.