Planning and setting up geo-protection in EMC ViPR
Table of Contents
This article applies to EMC ViPR 2.0.
- Storage types
- Storage on one site can be different from storage on another site; for example, you can have EMC VNX at one site, Commodity storage at another site, and EMC Elastic Cloud Storage at another.
- Commodity storage
- If you are using Commodity storage at a site, there must be at least 8 commodity nodes deployed (this is a general requirement for commodity). Refer to the EMC ViPR commodity checklist article and the fabric install article for details.
- Network latency
- Ensure a maximum latency of 1000 ms between configured sites.
- Free storage
- If your disaster plan includes running for a period of time with one site failed (instead of promptly recovering the site), each site will need enough free storage across all sites to accommodate for rebalancing of data. Across all sites, the amount of free space left should be, in total:
- free space across n sites =1.33*x/(n-1)/(n-2)
- where x is the total amount of user data across all n sites.
- Example: 30 petabytes of data across 3 sites = 1.33*30/(3-1)/(3-2) =39.90/2=19.95 PB free space across all sites.
- Note that this amount of free space is not required if you add a new site soon after the failover, and do not continue to operate with (N-1) sites indefinitely.
- VDC requirements
- Refer to
Plan and deploy multisite EMC ViPR for the ViPR controller-based requirements and setup procedure, which are prerequisites for configuring geo-protection, described here.
As pointed out in Plan and deploy multisite EMC ViPR, the VDC that you add must be blank; you cannot add an existing, configured site.
- Install EMC ViPR Controller at each site.
- On VDC1 only, set up authentication and add physical and virtual assets, and data nodes. See Step by Step: Set up a ViPR virtual data center and and Install a ViPR Data Services node.
- On VDC1, add VDC1’s data node IPs to .
- Link the VDCs as described in Plan and deploy multisite EMC ViPR. Note that when you add one VDC to another, the added VDC must be free of data (no physical assets, no virtual assets, no data nodes). So it is important to perform this step now before continuing.
- On VDC2 only, add physical and virtual assets, and data nodes. See Step by Step: Set up a ViPR virtual data center and and Install a ViPR Data Services node.
- Set up object support by following the steps in Configure ViPR object storage on ViPR-managed file storage systems and Create a secret key to access ViPR object storage.
- On VDC1, add VDC2’s data node IPs to .
- To protect object data across the multisite configuration, specify the VDC-virtual array pairs where data should be stored and replicated when saving data to the selected object virtual pool. In the ViPR UI, go to .
- Add an Object Virtual Pool and specify the virtual data centers and virtual arrays where the object virtual data should be stored.
Before you begin
You will need to have the S3 Browser installed.
You will need an object data store key (a secret key) generated from the ViPR UI (refer to Create a secret key to access ViPR object storage.)
- Open S3 Browser.
- Create a new account (). For the secret access key, use the object data store key from the ViPR UI.
- Under Connection tab. , select the
- Uncheck Use secure transfer (HTTPS).
- Check Use Proxy and enter the ViPR data node IP from VDC1 for the address. Enter 9020 for the port.
- Click OK to save.
- Under Buckets create a new bucket.
- Under Files upload a sample file to the bucket.
- Now go back to Connection tab change the address to a VDC2 data node. Keep 9020 for the port. Click > OK to save. and under the
- Click OK to save.
Refresh to pick up the change to VDC2.
The file you uploaded to VDC1 in the earlier step is visible now through VDC2.
- Under Files download the sample file to verify.