Dell PowerStore 1200T EMC PowerStore Protecting Your Data - Page 7

NOTE: If you cannot see these columns, you can add them, using the Show/Hide Table Columns option. Mapping snapshots to hosts is not supported in PowerStore. To allow a connected host to access a snapshot, you can create a thin clone - a writable, space efficient copy of the snapshot - and map it to a host. You can update the thin clone from different snapshots using the refresh operation. For details on the possible snapshot-related operations you can perform, using the PowerStore Manager, refer to the Snapshots chapter. Replication Data replication is a process in which storage data is duplicated to a remote system, which provides an enhanced level of redundancy in case the main production system fails. Replication minimizes the downtime-associated costs of a system failure and simplifies recovery following a natural disaster or human error. PowerStore supports asynchronous remote replication for volumes and volume groups, NAS servers and virtual volumes. To configure replication for volumes and volume groups: 1. Create a remote connection between the source and destination systems 2. Create a protection policy with a replication rule that best meets your business needs. 3. Assign a protection policy to the volume or volume groups. To configure replication for Nas servers: 1. Configure and map the file mobility network. For details see the Networking Guide for PowerStore X models on the PowerStore Documentation page at https://www.dell.com/powerstoredocs. 2. Create a remote connection between the source and destination systems. 3. Create a protection policy with a replication rule that best meets your business needs. 4. Assign a protection policy to the NAS server. To configure replication for virtual volumes: 1. Create a remote connection between the source and destination systems. 2. Creating protection policies and assigning them to virtual volumes is done on vSphere. See Virtual volumes replication. For volume and file replication, PowerStore enables you to failover control to the remote system and reverse the direction of a remote protection session. Failover may be required in the following cases: ● If you want to migrate data to a new system and then switch to working from it without losing data. In this case, failover can be performed with no data loss. ● When there is no access to the data in the source system, you can switch to the remote system and continue to work, using the latest point-in-time remote protection copy. In such a case there may be some data loss, since the latest copy in the remote system does not include data changes made between the time this copy was created and the time the data in the system became inaccessible. ● When the data in the source system is accessible but its integrity may be compromised. In such a case, you should revert to the latest point-in-time protection copy created before the data was compromised. You can perform a failover test on the destination storage resource to test the system disaster recovery readiness. For detailed information on replication-related procedures you can perform, see the Replication chapter. Protection policies A protection policy consists of snapshot rules, replication rules, or both, that you can create to establish consistent data protection across storage resources. After configuring a protection policy, you can assign it to new or existing storage resources. Each protection policy can only include one replication rule, and up to four snapshot rules. A replication/snapshot rule can be included in multiple policies. Protection policies manage snapshot creation and replication sessions, based on the rules included in them. You can create policies with various rules that provide different levels of protection to meet your local and remote protection needs, and assign a policy to multiple storage resources to provide identical protection to those resources. Based on your user privileges, you can create or modify relevant rules and policies. Introduction 7