2017-01-31 08:15 PM
We are Currently using NetApp 3.2(AVA-c8) which is replicate in to S3 Bucket. we need to upgrade this version to latest 4.x(AVA-c8).
So, here we need to launch a new AMI built?
Kindly give us the proper guide for follow this procedure with out effecting production environment backups and previous data.
FYI. we are using the Netbackup 7.6.1 as a backing up software. Backups we will take care at the point of upgrade.
2017-02-02 11:42 AM
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.
2017-02-09 01:49 PM
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.
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,
2017-02-09 02:09 PM
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.
2017-02-09 02:34 PM
Chapter 4 Performing AltaVault AMI and AVM upgrades
Please conform following
If we follow the same procedure for what ever new AMI and old AMI it will not work out?
Now if we follow Procedure like ? :
1.Deleting the New AMI 8 - EBS volumes and detatching the old AVA - c8 8 volumes to attatch new AVA-c8. Is it not possible?
2.Downloading the configuration file from old AMI and configures To new AMI is it not possible?
Please reach me Through call 2127906947