Contact & Subscribe RSS

LinkedIn
RSS

Posts tagged "veeam-backup-and-replication"

VEEAM Task failed Error: Exception of type ‘System.OutOfMemoryException’ was thrown

Last week I had the following error when starting a Veeam backup job. I thought my proxy servers where out of memory, so I rebooted them. Then I started the backup jobs again, with no result.

Solution:
To solve this issue you must logoff all the other RDP sessions, which have a disconnected session with the Veeam console open. Alternatively, give the Veeam backup server more resources so there is more memory available.

VEEAM Change disk exclusion (disk filter) with PowerShell

When you have multiple jobs with many VMs it’s a boring task to change all the disk exclusions by hand. That’s why VEEAM have made a nice PowerShell module to automate this boring tasks.

Excluded disks are displayed with numbers, the numbers in Hyper-V are different (because of the IDE disks) then how the numbers are showed in VMWare.
This scripts are tested with VEEAM Backup and Replication V8.

See the current excluded disks and the numbers with this script (Run as Administrator):

Change the disks exclusions with PowerShell (Run as Administrator):

Comments are welcome.

Task failed. Failed to expand object. Error: Object was not found

Task failed. Failed to expand object. Error: Object was not found

Change VM ID VEEAM database.
In my case I had to replace the old VM id with the new one.

There are multiple reasons why the VMID is changed. This can be caused by exporting and importing the VM for example. When this situation occurred you get the following error in VEEAM:
“Task failed. Failed to expand object. Error: Object was not found”

If you don’t want to add the new object and creating a new full back-up of the VM. You can change the VM ID in the database.

When this is done the forward incremental runs as before.

First we need to determine the OLD id where VEEAM is looking for.
This can be done with the following lines SQL Query against your VEEAM DB:

Get old object ID before Veeam version 9.5

Get old object ID Veeam 9.5

The following step is to get the new VMID from Hyper-V or VMWare.
With Hyper-V Virtual Machines Manager (SCVMM) PowerShell Module.

Run PowerShell as Administrator:

With VMWare can this be done with PowerCLI on the ESX host.
Excuse me when I’m wrong, but I think:

SQL Query:

Put the new ID by SET.
Put the old ID by WHERE.

*Tested with VEEAM Backup & Replication 8

 

Error: Failed to determine SCVMM Server version. The credentials provided have insufficient privileges on NO_PARAM.

VEEAM communicates with the VMM Console to get the Hyper-v topology and other VM information. After installing UR6 on our VMM Management servers VEEEAM could not enumerate the VM information from VMM.

The jobs fails with the following error: Task failed. Failed to expand object. Error: Failed to determine SCVMM Server version: You cannot contact the VMM management server. The credentials provided have insufficient privileges on NO_PARAM. You cannot contact the VMM management server. The credentials provided have insufficient privileges on. Ensure that your account has access to the VMM management server, and then try the operation again.

In our case we solve this with the following steps:

– Download / install all available Windows Updates.
– Upgrade the VMM Console on your VEEAM management server to the same version as your VMM management server.
– Create a new SA account with the same rights and VMM Rights as the old account.
– Change SA account in VEEAM Console (Backup Infrastructure -> Right click on your VMM Server -> Properties -> Credentials -> Change -> Finish.

The weird thing is, AFTER changing the SA account with the same rights etc the stuff worked again -_-‘
If someone can explain this don’t hesitate to comment 🙂