The procedure for upgrading the AVA-c8 between versions is discussed in the documentation (specifically, the AltaVault cloud install guide). Please refer to Chapter 4 Performing AltaVault AMI and AVM upgrades for procedures on how to upgrade the AltaVault AVA-c8 instance version.
we have followed the same document and we have built a New AVA-C8 AMI with the version of 4.2.2 AVA-c8 with the attatching of AWS s3.
The backup application we are using currently Veritas Netbackup. We have mounted our new AVA-c8(SACNPAWS008) to Same media server and created one more Storage unit to New one also. Initiated the backup to new appliance SACNPAWS008.
Please find the below mounted details.
Currently in the production 3.2v AVA-c8(SACNPAWS002) and all the data is available in that.
We seen the procedure like detatching the EBS volumes and need to attatch it to new AMI SACNPAWS008 with the configuration file.
1. While attatching the EBS volumes any data or volumes will lost any thing? In SACNPAWS002 cloud data presents shows "Estimated Cloud Space is : 39 TB"
2. The same S3 bucket connected our new AVA-c8. Here Cloud Data its Shows "Estimated Cloud Space is : 25gb ( 40Tb empty space )". When attatching cloud data where will go ?
3. If possible please contact us through call or mail to success this upgradation with out any data loses.?
We will have Web-ex session to complete this activity,
Sorry, but it doesn't seem that you followed the directions appropriately as discussed in my previous post (Cloud install guide, Ch4). If followed correctly, this procedure should have lead you to perform a manually created (vs. a 1-click created) version of the AVA AMI, for which you would have connected the original 3.2 AMI's data store disks. If done this way, you would have actually moved your original data store disks to this new instance for use, and you'd only have one instance after all is said and done (with the same hostname and configuration as the original). The screenshot you're showing indicates you've created a separate instance running side by side along your original 3.2 instance, which isn't correct.
With that said, please hold on before doing anything.
Engineering wants to validate the procedure will work from that older 3.2 version to the current 4.2.2 version of AltaVault AMI. The procedure was intended for 4.0+ to 4.2.2.
I will let you know as soon as I hear back from them.