Replication Removal on a Source Host
The replication removal on the source host is very similar to that on a target host. For simplicity, refer to the corresponding step in a previous section if a step is the same as mentioned before.
On a replication source host, snpolicy-managed directories need a policy assigned directly to them. The policy can be either deduplication only, replication only or replication with deduplication. For directories that have deduplication enabled, the content may have been truncated by the snpolicy daemon. Snpolicy command removepolicy will retrieve the truncated content back before removing the policy from a file if no TSM relation point is associated with it.
The removal of replication/deduplication on host side has 11 steps. It is assumed you have already collected the replication/deduplication configuration described in section Collect and Understand Replication/Deduplication Configurations.
Step | Action | Description |
---|---|---|
1 | Backup Replication/Deduplication Configurations |
This saves the replication/deduplication configurations on the source host. See Replication Removal on a Target Host on how to back up. |
2 | Suspend Replication/Deduplication Actitivities |
This is similar to Replication Removal on a Target Host except that there is no need to change policy “target”. Note: If you have multiple snpolicy-managed file systems, you must stop replication/deduplication activities for each file system. |
3 | Remove Policy from Snpolicy-managed Directories |
For each snpolicy-managed directory obtained from section Obtain Information from the Command Line (from the output of snpolicy command # /usr/cvfs/bin/snpolicy –removepolicy=dir_path
# /usr/cvfs/bin/snpolicy -removepolicy=/stornext/snfs1/test I [0126 09:48:06.955781 28768] Removed policy from /stornext/snfs1/test Note: If you have multiple snpolicy-managed file systems, run this command for every snpolicy-managed directory on each snpolicy-managed file system. After all snpolicy-managed directories have been removed the associated policies, run snpolicy command [root@ylu-rep-src1 ylu]$ snpolicy -listpolicies=/stornext/snfs1
NAME: default NAME: global inherits from: default NAME: target inherits from: global NAME: rep_pol1 inherits from: global |
4 | Remove Replication Targets from StorNext GUI |
In the StorNext GUI, click Configuration > Storage Destinations > Replication Targets, and delete all replication targets defined there. |
5 | Stop Snpolicy Daemon and Blockpool Server |
Stop the snpolicy daemon and blockpool server on the source host. See Replication Removal on a Target Host for details. |
6 | Remove Snpolicy-managed Private Directories |
This step removes the snpolicy-managed private directories. See Remove Snpolicy-managed Private Directories for details. Note: On the source host, no private directory is created under a TSM relation point, so it is not necessary to remove a private directory under a TSM relation point as shown in Remove Snpolicy-managed Private Directories. Also, the private directories for all snpolicy-managed file systems must be removed. |
7 | Remove Replication History Logs |
See Remove Replication History Logs for details. |
8 | Remove Related Event Files |
See Remove Related Event Files for details. |
9 | Remove Blockpool and its Configurations |
See Remove Blockpool and its Configurations for details. |
10 | Turn off “Snpolicy-managed” Attribute in File System Configuration File |
See Turn off the Snpolicy-managed Attribute in File System Configuration File for details. |
11 | Restart StorNext GUI |
See Restart the StorNext GUI for details. |