252
NetApp AltaVault Cloud Integrated Storage Administration Guide
Best practices for Amazon Glacier
Recovering data from Amazon Glacier
AltaVault can also be configured to delay the migration of data from Amazon S3 to Amazon Glacier. By default, data
is typically migrated within a 24 hour window once it arrives on Amazon S3. Using the AltaVault CLI command,
replication migration-delay
, Amazon S3 can be instructed to maintain the data for a longer period of time (set in
days), until the data is moved to Amazon Glacier. However, it is important to understand that while this can extend the
retention on Amazon S3 for new data segments, iterations of the same data segments sent to AltaVault (such as during
subsequent full backups) will not result in the migration delay being extended for that deduplicated data segment
already residing on Amazon S3. It is likely that over time, only a subset of a backup will reside on Amazon S3 awaiting
migration, but a majority of the data will reside in Amazon Glacier since it hasn't changed. Refer to the
NetApp
AltaVault Cloud Integrated Storage Command-Line Interface Reference Guide
for more details.
Recovering data from Amazon Glacier
When you use Amazon Glacier as the cloud storage provider, you can select from one of several retrieval modes:
Expedited, Standard (default), or Bulk. Data retrieval speeds for these modes are 5 minutes, 5 hours, and 12 hours,
respectively. For the data transfer pricing available with each method, see Amazon Web Services. Faster retrieval times
will result in higher costs.
The retrieval speed is the time it takes to make the data available for download after you send the initial request to the
cloud. Due to this delay, if data is not available on the local cache, it cannot be paged back from the cloud on demand.
In such cases, you must first manually restore the files to be read from the cloud to the local cache on AltaVault using
either the prepopulation GUI or CLI commands. After the data is restored from the cloud, it can be read from the local
cache.
When recovering data from Amazon Glacier, NetApp requires that all the data segments related to a restore or retrieve
by the backup application be present on the AltaVault cache first. This avoids error or retry conditions by the backup
or archive application while it waits on Amazon Glacier to send the data to the AltaVault cache. To recover the data
segments associated with the files to the AltaVault cache, use the AltaVault prepopulation feature. This limits the time
penalty for data retrieval to the waiting period associated your selected retrieval mode. If several, separate retrieve
requests are made for individual data segments (for example, when a backup application restores files sequentially,
where each file is not in the AltaVault cache), this can slow down the overall retrieval process from Amazon Glacier
and the overall recovery.
Data prepopulation is described in the following sections:
“Restoring data from the cloud using the prepopulation page” on page 252
“Restoring data from the cloud using the command-line interface” on page 254
“Automatic prepopulation” on page 258
Restoring data from the cloud using the prepopulation page
The Prepopulation page provides a granular status of its tasks that were started using the Management Console or the
command-line interface. For each task, you can also view the list of files that are being restored by the task.
To restore data from the cloud using the prepopulation page
1.
Prepopulation requires the specific Prepopulation Settings user permissions in order to access.
2.
Choose Configure > Prepopulation.
3.
Click the
Select File
tab to display the Prepopulation File Browser that contains a list of files that can be
prepopulated.
Summary of Contents for AltaVault AVA400
Page 2: ...Beta Draft ...
Page 10: ...Beta Draft Contents ...
