Veeam Deployment Kit

[jcofin13]

about 2 months ago after our upgrade from 12 to 13 we had lots of issues with VMS not backing up due to the VBR server not being able to install the agent and "stuff" on the vms so they could do application aware backups. This thread is here: veeam-backup-replication-f2/veeam-13-is ... 02486.html I started a new thread here because that one went off the rails quickly with other replies from other users that may or may not have been related.

The issue in summary was i needed to manually install the deployment kit for some reason to allow those vms to backup after the upgrade.

Anyway a couple nights ago i noticed that one of our vms failed. Veeam couldnt talk to it.

I took the same deployment kit folder and bat file and attempted the install of it on this vm. It installed fine with no errors via elevated command prompt.

I restarted/reset the services.

Oddly under the windows services i only see the veeam installer service.
Under add/rem programs i see the installer service as well and i also see a Veeam SSL FIPS service.

Anyway i try the job and now it fails with a certificate error.


On all prior vms from 2 months ago when i had to install the deployment kit batch file i got 3 windows services:
Veeam Installer Service
Veeam Guest Agent
Veeam Transaction Log Service

I also see those 3 in add/rem programs as well.

Im not sure how or why i didnt get all 3 services this time. Same installer from the same folder.
IM also not sure why im now getting a cert error on this vm.

I dont know if i needed to run the "deployment kit" to export a new one on the VBR server then try to deploy it on this vm? DO they expire? I dont want to export a new deployment kit from the VBR server if it does anything to the server and cause those other 26 to start having issues. I wouldnt think it would but i cant get a clear answer via the documentation and support seems to be good for 1 response per day recently. I have a case going if that ticket number is helpful.

[Mildur]

Hello jcofin13,

The certificate created with the deployment kit has an expiration date. The default validity period is 720 hours (30 days). This period can be extended during creation via PowerShell or the REST API. Creating a new deployment kit will not affect existing configuration. The certificate in the deployment kit is used to enable initial communication.

Regarding the error you’re seeing, please continue working with Customer Support so we can investigate properly. Could you also share your case number here for our reference?

Best,
Fabian

[matteu]

Hello,

You can try with a new generated deployment kit to get a new generated certificate (not expired).

Keep us informed

[jcofin13]

Can i generate another "new" deployment kit without disrupting the ~20 vms we manually installed with the initial deployment key after our v13 upgrade?

This is unclear. I assume its fine to do but i dont want to go from bad to worse and cause those vms to start having issues again due to cert changes in running the deplopyment kit creation again to troubleshoot this 1 recently failing vm.

[Mildur]

I answered that question above.

Best,
Fabian

[jcofin13]

lol...sorry. I only saw the last post. Its been a long week. Thank you for the clarification on this. I will keep working with support. Next steps per the ticket is to regenerate the deployment kit and install on this problem vm. Thank you for the response.

[jcofin13]

That did work. I was able to generate a new deployment kit and then run it on the failing vm. I issued a "retry" on the job and it did backup. It threw a warning about creds for application aware processing which was odd since this vm is excluded from that but maybe on a manual retry thats normal. Ill watch it as the job runs the next few days.

Thank you for the help / clarity!

[matteu]

Thanks to keep us informed

The solution here seems logical based on what you described

When you do a retry it should not be different than when the job execute itself based on the schedule.
Are you sure you correctly excluded the vm from application aware processing ?
You can do it like this :
vmware-vsphere-f24/disable-application- ... 89020.html