During the lifetime of a replication session, it is possible that file systems and clone may be added to the source NAS server. When this happens the replication session is supposed to automatically add file systems and clone to the destination NAS server. It is possible, for some unspecified reason, that this may not happen. In this case the replication session is considered inconsistent. The NAS server replication update action is designed to rectify this inconsistency. When the replication session update action is issued the file systems associated with the source NAS server are enumerated. If there is no file system with the same name on the destination NAS server then it will be created, and replication will be established between them. Similarly, if there is a file system with the same name on both NAS servers but there is no replication established, then it will be created. When there are missing file systems or the file systems are not replicated, there will be an alert displayed in the UI SOME_FS_REP_SESSIONS_NOT_CREATED
Example: Some FS replication sessions not created for NAS server replication session 'nas14Async'.
Follow the below steps to update the replication session:
Select
Data Protection.
Select
File Protection.
Click
REPLICATION tab.
Click
REPLICATION SESSION tab.
Select the required NasServer Session from the list view. if update can be performed, the option is enabled.
Click
Update. The Update Replication Session dialogue box opens.
Click
Run Now.
UI screenshot
NOTE:
Adding a filesystem to a nas server under replication would create the corresponding filesystem on the destination.
Cloning a replicated filesystem would follow the same workflow as the above point. Completing the baseline copy would take some time depending on the data on the source side and the session status will be SyncInProg but eventually move to synchronized (synchronous replication) or consistent state (asynchronous replication).
Deleting a filesystem under replication from the source will not delete the corresponding filesystem on the destination.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\