I've downloaded the most recent installation OVA for Avamar Virtual Edition and deployed it on ESXi 6U2. The OVA deployed correctly. I then added 3 250GB VMDK in order to have 1TB in the avamar pool. As the next step, once I have access to Avamar Installation Manager, I start the installation of ave-config. After filling numerous field, it start creating data partition (task 1 of 65) for a few hours. Then, task 2 proceed without any error. Then, at the "preparing package execution (3 of 65)", it fail with the choice of skipping the current task (tried that one time and it just stop with another failure a few steps later) or to call EMC support. As I got the software through the reseller program, support is not available.
Does anybody got that kind of issue? If so, have you resolved it? I installed the version 7.2 about 6 months ago without that kind of problem. If nobody has any idea of how to fix 7.3, I'll get back to 7.2 for the moment.
Solved! Go to Solution.
I found out why it is not working. I changed the setup to have no encryption and since, it doesn't work (incompatible option). If I activate the encryption at "high", I'm able to do a backup. I looked around to find where I could have a setting for encryption that would be different then "None" but without success.
When we want to use no encryption for the default virtual machine group, where else do I have to select "None" as the encryption method to make it work? I don't remember having this issue with 7.2.x but I may be wrong (or I was just Lucky to have it working as I didn't look for that).
Thank you for any assistance with this.
Unfortunately there's not enough information here to identify the problem. I'd recommend reviewing the workflow.log for more information. This log file is located in the following directory on the Avamar server (where "<package name>" is the name of the AVP package for the installer):
I think I found the problem. I was following the installation guide “Avamar VE 7.3 for VMware System Installation Guide” and, in this guide, they never talk about unlocking the padlock and don't give the password either. As I installed 7.2 about 6 months ago, I tried to unlock it with the previous password without success. I figured this part of the installation may have changed.
About an hour ago, I was looking at the Avamar 7.3 portfolio and found out in the upgrade guide that the password is there. I restarted the 7.3 installation, use that password to unlock the padlock and this time, everything worked as expected.
I’m pretty sure it is the reason of the problem as I did deploy the version 7.3 twice without success and then, a third time after unlocking the padlock and this time, it worked like a charm.
So, hopefully, it may help others that would encounter the problem while EMC update the Installation Guide properly.
Edit by Moderator: Removed confidential password.
Well, I'm having a working AVE 7.3 but can't deploy a proxy. Looking at the log, I'm getting a "javaxnet.ssl.SSLHandshakeException: Unsupported curve: 1.2.840.10045.3.1.7". Anybody knows how to either have this version of curve recognized as a supported version or a way to upgrade/downgrade curve to a supported version?
You do not need the password to install AVE 7.3. The support password for the Avamar Installer is only used when you need to display a "support only" package. Since AVE is now customer installable, the AVE install package is no longer a support only package. If the package is visible when you log into AvInstaller, the support password is not required.
Well, if that's the case and the password is not required, it was not working at all here while everything work perfectly once I used the password. Did you successfully install it without using the password and without hacking behind the scene? If so, which username have you used to connect to the /avi page? I used "root". Is that correct?
I'll try the resolution regarding the unsupported curve issue. Hopefully this will be fixed soon as, per the documentation, the fix is presented as temporary.
I did apply the resolution that is documented and I still get the same error message about curve being unsupported. I did the procedure two times (in case I did a mistake the first time) and get the same result. I tried restarting the service as documented but also rebooted the server and still have the same error which translate in not being able to deploy the proxy. Any suggestions about what I could have missed or something else that could interfere?
Making restricted packages visible is literally the only purpose of that password. Entering it or not entering it will have no effect on the installation of the package itself. When you're initially installing the Avamar software, you do need to use the OS root credentials to log in because the Avamar accounts can't exist yet if the software isn't installed. However, if you've reached the point where the software is actually installing, you've already gone past the point where things like user accounts and passwords matter. The issue is not related. The only way to confirm what went wrong is to review the workflow.log.
What method are you using for deploying the proxy? Are you using proxy deployment manager or deploying the proxy manually using the OVA / OVF?