Posts

Showing posts from November, 2017

Veeam Guest Agent is not started

Backup Technology: - Veeam Issue: - Veeam job failed with below error message. ------------------- VMware Tools are not running. Guest processing skipped. Failed to prepare guest for hot backup. Error: Veeam Guest Agent is not started ------------------- Cause :- -        VM might be rebooted or down during backup job running. -        Veeam run time agent service stuck on VM server. -        VSS writers might be in failed status. Solution :- 1. Login to the effected VM and verity the uptime. If the VM is rebooted during backup job running then it will completed successfully in next retry attempt or next run. or 2. If you found any VSS writers are in failed status then reboot the server to resolve VSS writers issue. or 3. If Veeam run time agent service “VeeamVssSupport” stuck or not deleted after the veeam job completed then you need to delete the service manually or reboot the server.

How to pull reports in Veeam ONE server

Image
1.        Login to the Veeam server 2.        Start à all Programs à Veeam à click on “ Veeam ONE Reporter”. 3.        Veeam ONE Reporter will open in IE and give the credentials. 4.        After login, click on workspace and select “Veeam Backup & Replication”. Below screenshot for your reference. 5.        After clicking “Veeam Backup & Replication”. Below dialog box will open. 6.        Click on the option listed in the Right side and select appropriate options and run the report.

No connection could be made because the target machine actively refused it -vCenter server IP

Backup Technology:- VEEAM Error:- Multiple jobs failed with the error message “” Task failed Error: No connection could be made because the target machine actively refused it <ip_address>.44:443 (vCenter Server IP). Cause:- Backup jobs failed due to vCenter server not reachable during that time. Workaround:- 1.     Try to login to the vCenter server. 2.     Verify, is vCenter server rebooted during the backup’s running. If so wait for next schedule. 3.     Verify vCenter service is running or not. 4.     If you face any problem with accessing the VM then work with Virtualization team and resolve the issue.

Error :- Not enough licenses. Please contact Veeam Customer Support at support@veeam.com

Image
"Error: Not enough licenses. Please contact Veeam Customer Support at support@veeam.com ." Cause: This is typically caused by a host being rebuilt and given a new IP address or net name. Solution: 1. Go to Help -> License       2. Click Licensed Hosts    3. Select each of your hosts and press "Revoke"

How to schedule automatic report delivery for Veeam jobs

Image
You can schedule automatic report delivery for one report or for a number of reports included in a report folder. You can choose to receive ready reports by email, save reports to a folder on a hard drive or to a network share. Note that you can only schedule delivery for saved reports (that is, reports in the My Reports folder and its subfolders). You need to login “VEEAM ONE REPORT” to configure automatic reports To schedule automatic report delivery: 1. Open the Workspace section. 2. Select the necessary folder under My reports on the left. 3. In the displayed list of reports, click a saved report for which you want to set scheduled delivery. 4. Click Scheduling in the Actions pane on the right. 5. In the Scheduling Report Administration window, click Add . 6. In the Scheduling window, configure the scheduling options:

VeeamVssSupport Service not found

Backup Technology:- VEEAM Issue: - Backup job failed with below error message. Error: Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [x.x.x.x]. The specified service has been marked for deletion. Code:1072 Cannot create service. Win32 error:The specified service has been marked for deletion. Code: 1072. Error: Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [x.x.x.x]. The specified service has been marked for deletion. Code:1072 Cannot create service. Win32 error:The specified service has been marked for deletion. Code: 1072. Vvv Cause: - The VeeamVssSupport service cannot be installed because it was never uninstalled. It was marked for deletion instead of being deleted. It cannot be removed, but will be removed automatically when the guest OS reboots. Typically this is due to one of the following programs being open at the time the deletion command w

Veem job Failed to prepare guest for freeze, wait timeout 900 sec

Backup Technology: Veeam Sometimes Veeam backup jobs failed on VM with below error message continuously. Failed to prepare guest for host backup. Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec We need to follow the below steps to resolve the issue. Cause: This issue typically involves a very active transactional application running in the virtual machine, and it is taking longer than expected per the default timeout to freeze the I/O for this application/VM Solution You can change this timeout by modifying the value in the registry of the server where Veeam Backup & Replication is installed as follows: 1.        Go to Veeam registry path HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication. 2.        Add a DWORD (32-bit) value named VssPreparationTimeout. The value is in milliseconds (decimal), the default timeout is 900000, which equa

Object VM name not found

Image
Backup Technology : VEEAM ISSUE: Job fails with the following error message, “Task failed Error: Object <vmname> not found” Check the log file for the following entries: Error    Failed to expand object added to the job. Object: 'Object, id: , name: <vmname>, type: VM, vi type: VirtualMachine, host name: ’. Error    Object <vmname> not found. (System.Exception) The most direct resolution can be verified by editing the job, selecting the “Virtual Machines” tab, then selecting recalculate. Below is the screenshot for the same. If any VM whose size comes back as “Not Available”, one should attempt the below as a resolution . Cause: This error is caused by the VM’s unique inventory reference identification number (MOREF, or Managed Object Reference) changing within the virtual infrastructure, or the VM having been deleted. Veeam is still attempting to find the VM by its old reference ID number based on a “find vm by NAME where REFID =