Veeam is the best backup solution for virtual workloads unless you're running a weird hypervisor.

General Information

This page will contain helpful scripts, and fixes. Some of these will be undocumented scripts or options that have been provided by Veeam Support while troubleshooting an issue.

Checklist

• If in doubt, contact Veeam Support, they're awesome.
• Options will be described as well as possible, but, again, refer to previous.

Section 1 content.

Example Code:

GrantUserAuthorAllCalendars.ps1

$Example powershell code that will be presented as an attachment in the wiki, while also showing syntax highlighting.

See https://www.dokuwiki.org/wiki:syntax#syntax_highlighting for supported syntax highlighting.

Section 1, sub-content.

-This occurred on upgrade, and required uninstalling the VAC Communication Agent, and reinstalling it manually from elevated cmd prompt:

msiexec.exe /i VAC.CommunicationAgent.x64.msi VAC_MANAGEMENT_AGENT_TYPE=3 VAC_CC_COMMUNICATION_PORT=9999 VAC_SERVER_NAME=VACserver VAC_CONNECTION_ACCOUNT=m\administrator VAC_CONNECTION_ACCOUNT_PASSWORD=123qweASD /l*v C:\ProgramData\Veeam\Setup\Temp\AgentSetupmsi.txt

MSI location C:\ProgramData\Veeam\Veeam Availability Console or C:\Program Files\Veeam\Availability Console\ApplicationServer\AgentPackage

VAC_SERVER_NAME= This needs to be the IP address, or FQDN of the VAC server.

VAC_CONNECTION_ACCOUNT= This will be an account is authorized to connect to VAC (I believe this is local administrator, or Backup Operators groups)

VAC_CONNECTION_ACCOUNT_PASSWORD= This will be the password to the above account, the password will only be plain text in the cmd prompt.

/l*v path: This enable verbose logging to the specified path.