Skip to main content
NetApp Knowledge Base

How to failback to a physical AltaVault appliance from a virtual AltaVault appliance

  1. Last updated
  2. Save as PDF
Views:
78
Visibility:
Public
Votes:
2
Category:
altavault
Specialty:
legacy
Last Updated:

Applies to

  • NetApp Cloud Backup (formerly AltaVault)
  • AltaVault appliance AVA400 and AVA800
  • Virtual AltaVault AVA-v2, AVA-v8, AVA-v16, and AVA-v32

Description

  • This KB talks about how to revert to the physical AltaVault after it had been failed over to the virtual/cloud AltaVault appliance.
  • The reason for failback could be:
    • DR testing; To revert back to original state after the DR test is complete.
    • The local cache at the virtual AltaVault may not suffice for bulk prepops (if the configured bucket is AWS Glacier) and it could be desired to fail back to the physical appliance to complete the task.
    • The cloud capacity of virtual AltaVault(~160T in case of  AVA-v32) may not suffice for migration or for archiving backups.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.