Archive by category "VEEAM"

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 🙂

Start VEEAM Job Task Scheduler

The VEEAM job scheduler is really basic. It’s not possible to schedule a job on different times in a week for example.
You can create a task schedule job to start the back-up on every possible time.

Start -> Task scheduler -> Create Task

– Name (Job name and Time)
– Check Run whether user is logged on or not
– Check Run with highest privileges
– Configure for: Windows server 2012 R2 (or other late OS)
– Triggers (choose a time)
– Action -> New -> Start a program
– Program script: powershell
– Arguments:

Start job normally:

Start full backup you give the value -fullbackup after start-vbrjob:

 

VEEAM Failed to flush change tracking data. Using full scan incremental run.

Changed block tracking information is no longer being read, causing entire disks to be read instead of just the changed blocks.
This is a very generic error, so it is quite difficult to say what has happened.

Hyper-v Solution:

Run “sc stop veeamfct” and “sc start veeamfct” on the Hyper-V hosts affected to restart the Veeam Change Tracking service, and then see if the errors are resolved afterwards.

VEEAM KB1881

OR

When you run VEEAM V8, you must install patch 1. After this update the Flush change tracking data errors are gone.
This patch can be downloaded from the here:
VEEAM KB1982