NetApp AltaVault Cloud Integrated Storage Administration Guide 165
CHAPTER 12 Migrating data to a new cloud
This chapter describes how to migrate data to from an existing cloud to a new cloud. It includes the following sections:
“Cloud migration overview” on page 165
“Cloud-to-cloud migration” on page 166
“Canceling cloud-to-cloud migration” on page 167
“Amazon S3 or S3-IA to Glacier migration” on page 167
“Amazon S3 to S3-IA or Amazon S3-IA to S3 migration” on page 168
Cloud migration overview
It might be necessary to move AltaVault protected cloud data from one cloud to another some time after the original
deployment. For example, there may be a strategy shift to move from a public cloud to a private cloud in order to keep
data on premise rather than online.
AltaVault offers cloud migration to address this requirement.
For general cloud-to-cloud migration, AltaVault acts as a data replicator during the migration. As the data flows from
the existing cloud, through AltaVault, and then on to the new cloud, AltaVault does not reprocess the data. Therefore,
no data is evicted from the AltaVault cache during this process; the data simply flows through the networking
components of the appliance. AltaVault also continues to accept data from backup applications, so no interruption to
backup schedules occurs during migration. Upon completion, AltaVault automatically resumes replication of any
pending data that was queued during the migration process.
Be aware that replication is suspended during cloud migration. Therefore, if the AltaVault cache becomes full (since
data from the cache cannot be evicted if it is not replicated yet), then backup application attempts to write to the
AltaVault cache will fail, leading to failure of backup applications.
To Next Page
Loading...
