For the default tenant, the replication service works on one or more selected directories directly under fcfs_data in the default namespace. The service replicates the entire directory hierarchy under each selected directory.
Default namespace properties
Directories in the default namespace on one system involved in a replication link can be replicated only to the default namespace on the other system involved in the link. They cannot be replicated to HCP namespaces. Additionally:
•Before you can include any default-namespace directories in a replication link, the default namespace must exist on both systems involved in the link.
•The default namespaces in the two systems must have the same cryptographic hash algorithm and retention mode.
•If the default namespace on one system supports appendable objects, the default namespace on the other system should, too. For an active/active link, this ensures that users and applications can add data to replicated appendable objects on either system. For an active/passive link, this ensures that, in case of failover, users and applications can continue to add data to the replicated appendable objects on the replica. For information on failover, see Failover and failback.
![]() |
Note: For an active/passive link, regardless of whether the default namespace on the replica supports appendable objects, when these objects are recovered to the primary system, they are still appendable. |
The default namespace can be configured to prevent writes and/or deletes. This configuration can differ between the default namespace in the two systems involved in a link. However, even if the system receiving data is configured to prevent these actions, changes to namespace content on the sending system are replicated.
Replicated directories
You select directories for replication when you create the replication link. You can select additional directories or deselect directories by modifying the link at a later time. A replication link can include at most 256 directories.
![]() |
Note: In releases of HCP earlier than 6.0, a replication link could include more than 256 directories. In a system that was originally upgraded from a release earlier than 6.0, the maximum number of directories that can be included in a preexisting link in which the system participates is equal to either 256 or the number of directories included in the link at the time of the upgrade to release 7.0, whichever is greater. |
Directories can be created in the default namespace in both of the systems involved in a replication link, so the two systems can have directories with the same name. You cannot, however, replicate a directory created in one of the systems if a locally created directory with the same name already exists in the other system.
The one exception to this is the directory used for email archiving through SMTP. You can replicate the email directory if the email directory name is the same on both systems.
Replicated changes
With an active/active link, replicated directories are read-write on both systems involved in the link. All changes made to the content of those directories on either system are replicated to the other system.
With an active/passive link, the replicated directories are read-write on the primary system and read-only on the replica. Users and applications cannot make any changes to the content of the replicated directories on the replica. However, all changes made on the primary system are replicated to the replica.
Other replicated items
In addition to object creations, object deletions, and metadata changes, the replication service replicates:
•Retention class creations, modifications, and deletions for the default namespace
•Content class and content property creations, modifications, and deletions
•All log messages relating to retention classes and privileged delete operations
© 2017 Hitachi Data Systems Corporation. All rights reserved.