Home > Storage > PowerMax and VMAX > Storage Admin > Cloud Mobility for Dell PowerMax > Managing cloud system configuration
Cloud system management options are available by clicking the three-vertical ellipsis as shown in the following figure.
The management options are:
After the initial cloud system setup, networking details can be viewed and changed in the network configuration page.
Each network port can be configured as an individual network interface or can be teamed together providing redundancy. NIC teaming may also be known as link aggregation or Ethernet bonding. On PowerMax 2000 and 8000, the interface names eth1 to eth4 correspond to the I/O module ports 0 to 3, respectively. On PowerMax 2500 and 8500 the lowest physical port number will always have interface name eth2 with the higher port being eth3. In Figure 5, eth2 and eth3 interfaces are not displayed because they are configured as part of a NIC team.
The following are requirements for the cloud system network:
Optional bandwidth limits can be placed on the cloud system network interfaces, as shown in the following figure, by enabling Bandwidth Throttling and defining the maximum Mbps.
The cloud system configuration can be backed up and exported to an encrypted file for use with Cloud Mobility for Dell Storage. Cloud Mobility for Storage is a virtual application in the AWS Marketplace providing access to snapshots that have been shipped from the PowerMax to cloud providers.
The backup operation prompts for a one-time password used to encrypt the configuration backup file. Use of a strong password is recommended and stored in a secure location. The configuration file contains information pertaining to the cloud providers, cloud snapshots, and encryption keys for the data stored on the cloud providers. This password and configuration backup file is required when using Cloud Mobility for Storage.
More details about Cloud Mobility for Storage are in Cloud Mobility for Dell Storage (VMware and AWS) and in the Cloud Mobility for Storage Guide.
Note: We recommend exporting the cloud configuration regularly for site-recovery situations.
Cloud Mobility on PowerMax 2500 and 8500 systems can recover cloud snapshots from another PowerMax. Primarily used if the source PowerMax is no longer available and data from cloud snapshots is required.
The following requirements must be met before restoring a cloud system configuration:
It may take up to 20 minutes after the cloud configuration backup file and password are input until the storage groups cloud snapshots are available to be recovered. Restored cloud snapshots will appear under the Cloud Storage Group section of the Cloud Dashboard. More details on steps to recover cloud snapshots is available in the Recover from cloud snapshot section.
The Advanced Cloud Snapshot Management page displays all the SnapVX snapshots on the PowerMax tagged as Cloud Snapshots as shown in Figure 8. The list details the snapshot ID, name, creation time on the array, if it was taken as part of a cloud snapshot policy, the storage group the snapshot applies to, if the cloud snapshot is protected in the cloud, and if the snapshot is a delete candidate. A delete candidate is any snapshot that has been shipped to the cloud, its retention period has expired, or its cloud provider is now invalid or offline.
Snapshots can be selected to view additional details or deleted if the provider is invalid or offline. The cloud snapshots can also be deleted before the assigned expiry time if no longer required.
Before configuring ECS and PowerScale OneFS S3 cloud providers over a secure SSL connection, a valid certification authority (CA) certificate may need to be imported.
If your organization is not using a public Certificate Authority service, it may be necessary to internally generate a CA certificate in order to enable an SSL connection from the cloud system to the load balancer which handles traffic for the ECS or PowerScale. Usually where an internal CA is being used, it is important to install the *root* CA, not the server certificate installed on the load balancer. Even if using a public CA, it is still likely that installing the root CA is required. For purely private networks, such as offsite DR or test locations which may be isolated from public DNS and CA servers, it is possible to create a self-signed certificate which can be imported into the cloud system for use in building the SSL tunnel.
When a self-signed CA certificate file has been generated in PEM format (x509 with Subject Alternative Name entries), it can be imported into the cloud system as shown in the following figure.
Cloud Mobility can be removed to release the allocated CPU and memory back to the PowerMax for array redistribution. The Unisphere Remove Cloud System operation will unenroll the cloud system but will not release the resources back to the PowerMax. A Dell Technologies Professional Services engagement is required to complete the removal of the Cloud Mobility guest and the associated 10 GbE I/O module on PowerMax 2000 and 8000 or Cloud Mobility guest and the associated 25 GbE ports on PowerMax 2500 and 8500.
Dell Support will be required to reset the Cloud System enrollment if you want to reenroll the Cloud System after running the Remove Cloud System operation and did not have professional services complete the uninstall.
Before running Remove Cloud System, all cloud-related objects (Cloud Snapshots, Cloud Policies, and Cloud Providers) must be deleted from the array.