Data Backup and Recovery

How to modify S3 Bucket Information in Altavault

Argie

 

The Altavault is up and running (only test date on it) but now we were asked to change the AWS configuration. I see a note that states:

 

NOTE: When the datastore is not empty, the cloud provider, region, hostname, bucket name and archival mode cannot be changed.

 

 

What are the needed steps to be bale to modify the AWS S3 bucket configuraton in the Altavault appliance again?

 

 

Thanks,

1 ACCEPTED SOLUTION

chriswong

The prior cloud configuration will be present when you visit the UI after performing the CLI steps, but all the fields should be editable so you can modify the values accordingly (such as the bucket name, endpoint, cloud provider type, etc). If these values are not editable then you may have accidently started the service, which locks these fields down. You need to ensure you do not start the service prior to configuring the cloud settings first after running the CLI commands.

View solution in original post

3 REPLIES 3

chriswong

Hi,

To change the AWS configuration you'll need to wipe the contents of the AltaVault (and cloud) to start over. From CLI issue these commands:

enable

configure terminal

no service enable

datastore format all

(respond 'Y' to wipe cache and cloud contents; this is a permanent action)

stats clear-all

logging files rotation force

 

At this point, you can use th UI Configure -> Cloud Settings Wizard to reconfigure the AWS configuration as needed to your liking. 

 

Regrds,

Christopher

Argie

Unfortunately, I tried these steps 4 times but the cloud config still there after all. What could be preventing the confguration to be deleted?

chriswong

The prior cloud configuration will be present when you visit the UI after performing the CLI steps, but all the fields should be editable so you can modify the values accordingly (such as the bucket name, endpoint, cloud provider type, etc). If these values are not editable then you may have accidently started the service, which locks these fields down. You need to ensure you do not start the service prior to configuring the cloud settings first after running the CLI commands.

View solution in original post

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public