Skip to main content

Upgrade from AB 12 to AB 12.5

Thread needs solution

Hi all,

just mine 2 cents to recently released AB 12.5:

I was advised by support to update our AB 12.3689 installation to latest 12.5 in order to resolve issues that we had with AB 12. Installation of core was quite fast without any problems and we have deployed new appliances for our ESX 5.5. environment. After upgrade only ~30% of servers were able to backup ... rest was failing with few different error messages.

1. "The password for the protected backup is incorrect." We are using encryption on all of our backup archives. The fact was that we have only few backup jobs (up to 10) where we are backing up to 40 servers in a single job. Only part of servers were not able to back up .... some of them were working fine. Also in existing job there is no option to re enter password for backup archive ..... and last thing; when we tried to backup the server manually, the backup was successfull.

2. The backup didn't run for unknown reason - this is not the exact error message as i can't find it in the logs ... however servers were not backed up because the backup just didn't start ...... again sometimes manual backup run fine.

And the best as last. We have found out that for the servers that were backed up successfully we are not able to do any kind of restore. Full restore of VM to new VM failed with error message "Message: Resizing is unavailable." despite the fact that we didn't change any VM parameters. When we tried to do the run from backup we received VM with corrupted file system ... we have tried both unix and windows VM. We didn't try to do the direct restore to existing VM but i guess it would fail/create unusable VM as well.

I've contacted support for the 1st point and they advised only option that i was already aware of and this is to create new job thus new archive .. etc. It looks that this is running fine so far and producing backups that can be used for restore (wheee :) )

Summary of update:

1. We have lost all the backup archives that were touched by the new AB12.5 - they are unusable.So we need to do the full backups (dozens of TB) and prey that for next 2 weeks there will be no request for restore from more than we have new backups.

2. We have re created all backup jobs manually.

3. There are still some issues like backups of some servers are run randomly outside schedule, backup notes for VM are filled with bad time of backup, next backup field is showed not correctly (date from past) .... etc

So for everyone that want to upgrade AB 12 to 12.5 or already done the upgrade i strongly recommend:

1. Try to restore several servers - check if the backup is usable

2. Re create the jobs manually

3. If possible didn't do the upgrade ... better way is to setup backups as new installation with new archive .

BR,

Lubos

0 Users found this helpful

Soooo sad!