2017-05-02 10:04 AM
Solved! SEE THE SOLUTION
2017-05-02 10:19 AM
AltaVault saves the cloud connection details of the cloud you connected to when you set the appliance up for the first time - this is then stored in the configuration you export and import. In this case, the US GCP location. Even though you've moved the data to the Asia GCP bucket location, AltaVault or the AltaVault you set up for DR will be attempting to connect to the US GCP location. It does not support connecting to a different location once it is initially set up. This likely means that there is a problem accessing the US GCP data location from the AltaVault you're using (in Asia?).
Unfortunately there is not a mechanism (via community support) to change the cloud target details once set. However, supported AltaVaults can engage f ormal NetApp support to address a cloud change mechanism like this depending on the setup (although it's highly unusual and considered on a case by case basis). Since you're doing this as a test, it's likely they won't support it. And in general, you should not have to move your data across geographies from a cloud provider perspective since your AltaVault can do that for you.
2017-05-02 10:32 AM
Thanks Chris ,
Realy appriciate your response , yes you are right , however my intention was to provide an GEO DR Solution useing an single Altavault .
As I understood correctly What you are suggestiong is , Use two diffrent altavault applience and try to create two diffrent replication ?
2017-05-02 01:54 PM
The intent of my comments was that your data is in the cloud. It shouldn't need to be replicated anywhere for geographical DR, and at this time AltaVault doesn't formally support that type of functional activity (accessing the data from a geo-replicated target, such as AP vs. US).
Data availability will be provided for by the cloud provider, so as long as you have a network link to the internet, you should be able to access it from anywhere. Given that, you then only need to bring the AltaVault to the DR location (geographically independent) to move the data back for restore.