Unable to allocate processing resources. Error: No backup proxy is able to backup this VM. Check processing mode settings on proxies.

Hello,
Are you seeing this error when you try to back up your VMs with Veeam Backup & Replication 6.5 in Direct SAN Mode? Does your Proxy Servers sees the VMFS LUNs where you are fetching the VMs Data to the Backup Mode?

This error is generated because the Veeam Configured to backup VMs via Direct SAN Access “Using source proxy VMware Backup Proxy [san] and the Proxy doesn’t have access to the VMFS LUNs.

Solution:

To sort out this issue;
1. Make sure your Proxy Server can see the VMFS LUNs inside the Disk Management of the Windows.
2. Make sure the Proxy configured as Direct SAN Access.
3. Make sure the Direct SAN Access Proxy is selected in the Backup Job Configuration / Storage Section.
4. If you are still getting the error and failing to process the backup further, Open the Proxy Configuration under Backup Infrastructure -> Backup Proxies and select the desire proxy.
Right Click on the Desired Proxy and Select Properties in the Selected DataStores, select the VMFS LUNs which contains the target Backup VMs manually and try..

Hope it helps..

Backing Up Symantec Enterprise Vault with Veeam Backup & Replication

Hello Once Again,

I found the solution to backup Symantec Enterprise Vault 9.0.2.1061 with Veeam Backup and Replication 6.1.0.205.

Every environment is differ to another with regards to the Veeam Setup and Symantec Enterprise Vault Setup and Configuration.

When Symantec Enterprise Vault is configured with the Site and Storage Groups “Vaults”, there is a PowerShell script automatically will generate the Transform Backup Scripts for your environment. The Transform-Backup.PS1 script is located under C:\Program Files (x86)\Enterprise Vault\Reports\Templates.

Once the script runs, it will generate an HTML file which will have all the PowerShell cmdlet to set he Enterprise Vault/Site/Vaults ‘Storage Groups’ into Backup Mode and scripts to Exit/Clear the IndexLocation and Vault ‘Storage Groups’.

Out of this you will have to create two scripts or more, in my environment with my basic knowledge of scripting, I have created four scripts, two PowerShell and two Windows Batch files that calls the powerShell scripts.

Note: You have to install the Enterprise Vault Console on the Veeam Backup & Replication Server in order to invoke and run the scripts.
Note: Permission you will require to run the Veeam Job and the Enterprise Vault Console. If the Veeam Services runs under Service Account, this service account need to be granted permission as Local Administrator on the Enterprise Vault Server and as a Power Administrator “Or create a new Authorization Group under that have definition of;
EVT Manage Index Location Backup Mode
EVT Manage Vault Store Backup Mode
Then add the user to the newly group created. And configure the Task Schduler to run the task under this user which manages the Veeam Services “Veeam”
This KB from Symantec can help you out with the permission: http://www.symantec.com/business/support/index?page=content&id=TECH67812
Note: The PowerShell has to run on the 32bit; c:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
Note: Do not configure the Schduler on Veeam Backup Job, let the Task Scheduler handle this instead.

Pre Script:
This script will include the Power cmdlet which will set the Enterprise Vault in backup Mode and will invoke the Veeam Backup Job to run.

#Pre-job to set the Symantec Enterprise Server and Site into Backup Mode.
#Reset ArchiveBit on the Store Vaults.

DEL “\\EVServer\EVPartition01cc55b2dc699b70$\IgnoreArchiveBitTrigger.old”
DEL “\\EVServer\EVPartition01cc55b2753ddd30$\IgnoreArchiveBitTrigger.old”
DEL “\\EVServer\EVPartition01cc55b34882a450$\IgnoreArchiveBitTrigger.old”
DEL “\\EVServer\EVPartition01cc55b3725ff520$\IgnoreArchiveBitTrigger.old”

#Site: EV Site

#Set backup mode on site
c:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -psconsolefile “C:\Program Files (x86)\Enterprise Vault\EVShell.psc1” -command “& {Set-VaultStoreBackupMode -Name ‘EV Site’ -EVServerName evserver -EVObjectType Site}”

#SiteIndexLocations:  EV Site

#Set backup mode on indexes in site
c:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -psconsolefile “C:\Program Files (x86)\Enterprise Vault\EVShell.psc1” -command “& {Set-IndexLocationBackupMode -EVServerName evserver -EVSiteName ‘EV Site’}”

#Start Veeam Backup Job

Add-PSSnapin VeeamPSSnapin

# Add the name of the backup jobs to be included here. The order in which they are entered is the order in which they will run

$chainedjobs = (“SymantecEV”)

foreach ($jobname in $chainedjobs){
$job = Get-VBRJob -name $jobname
$jobtry = 0
start-VBRJob -job $job

$job.GetLastResult()
if($job.GetLastResult() -eq “Failed”){
do{
Start-Sleep 480
Start-VBRJob -job $job -RetryBackup
$jobtry++
}
while(($jobtry -lt 3) -and ($job.GetLastResult() -eq “Failed”))
}
}

The GetVBR-Job script it will start and it will loop through for 3 times as RetryJob till it gets the result Success/Warning other than Failed.
Call this script in the Task Scheduler either using PowerShell.PS1 or you can create a Windows Batch file to call the script

PowerShell.exe G:\Script\PreJob.ps1

Then in the Veeam Backup Job configuration in the Storage Section -> Advanced Settings you have to put the Post-Job Script under the Post Job Activity Section.

Post-Job Script:
This script will include the Power cmdlet which will clear the Enterprise Vault from backup Mode once the Veeam Job Succeeded.

#Post-job to Clear the Backup Mode on the Enterprise Site and EVServer.

#Create IgnoreArchiveBitTrigger.txtecho “Enterprise Vault Trigger File”> “\\EVServer\EVPartition01cc55b2dc699b70$\IgnoreArchiveBitTrigger.txt”
echo “Enterprise Vault Trigger File”> “\\EVServer\EVPartition01cc55b2753ddd30$\IgnoreArchiveBitTrigger.txt”
echo “Enterprise Vault Trigger File”> “\\EVServer\EVPartition01cc55b34882a450$\IgnoreArchiveBitTrigger.txt”
echo “Enterprise Vault Trigger File”> “\\EVServer\EVPartition01cc55b3725ff520$\IgnoreArchiveBitTrigger.txt”

#Clear backup mode from site

c:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -psconsolefile “C:\Program Files (x86)\Enterprise Vault\EVShell.psc1” -command “& {Clear-VaultStoreBackupMode -Name ‘EV Site’ -EVServerName evserver -EVObjectType Site}”

#Clear backup mode from indexes in sitec:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -psconsolefile “C:\Program Files (x86)\Enterprise Vault\EVShell.psc1” -command “& {Clear-IndexLocationBackupMode -EVServerName evserver -EVSiteName ‘EV Site’}”

When the Pre-Job Script runs, you will notice on the Enterprise Vault Server that an Event IDs will be generated which indicates that the Enterprise Vault Server is Set for Backup Mode and all the Storage Groups;

Successfully set Backup Mode on all the Vault Stores that are managed by the Storage Service on this computer. Event ID 7060
Computer Name: evserver.domain.com


Successfully set Backup Mode on all the Vault Stores in the Vault Store Group that are managed by the Storage Service on this computer.  Event ID 7059

Disabling additions, deletions, and updates to the following index locations because they are in backup mode: Event ID 7319

E:\Index\index1
E:\Index\index2
E:\Index\index3
E:\Index\index4
E:\Index\index5
E:\Index\index6
E:\Index\index7
E:\Index\index8

Status: Success  (0)

Once the Backup Job in Veeam Server finished, the Post-Script will be triggered and will clear out the Backup Mode and Symantec Enterprise Vault will generate an Event IDs
as successful cleared Backup Mode for all the Storage Groups Vault.

Successfully cleared Backup Mode from Vault Store. Event ID 7079


Scheduling Veeam Backup Jobs for Daily Incremental and Weekly Full using PowerShell

As every Veeam Backup & Replication User/Administrator can see that only one schedule can be configured for each job, which will includes First Full backup, Active Full backup and Daily Increments.

Daily incremental takes less time than the full backup and if you have configured the jobs to run each after another with minimum 20 – 30 minutes cap. In the same job there you are restricted to select either Synthetic Backup with Transforming the Backups into one Full Backup *.VBK file chain of all previous incremental or you have to select Active Full.

Synthetic takes less time to finish incremental, but if you don’t have good CPU/Memory resources and Disk I/O, the transformation process could take time or you might end up with full VM freezing.

But if you are in Active Backup and selected Weekly Active Full Backup on Friday let assume, which again if Friday trigger it will run as Full in the same time that the daily incremental runs which will take longer to finish and in the same time the second job will start before the first job finish and will end up having whole jobs running and will slow down the read and write performance of the disks and Veeam server.

Since Friday is the day off and the servers/systems are being utilized very less, I have the whole day to run my backup, but can I can configure the Active Full Backup to run on different day other than the one which is configured in the Job Scheduler of the Backup Job?

Currently there is no way to configure it from the Veeam GUI and it would be very fantastic feature if Veeam.com would consider to add a separate schedule for the Active Full Backup.

The only way to make sure you run your jobs without overlapping with other jobs and will run into performance issue; with very simple Veeam PowerShell script and a Windows batch script to call the PS1 script will make sure all jobs runs as per your needs.
In my environment, I’m backing up 44 VMs those VMs divided into 5 Jobs; I have created 5 scripts for each job and I disabled the Backup Job Schedule;

Critical VMs-1

Critical VMs-2

Critical VMs-3

Critical VMs-4

Critical VMs-5

I have created two scripts for each job as follows;

PowerShell Script “Critical VMs-1.PS1”

Add-PSSnapIn -Name VeeamPSSnapIn -ErrorAction SilentlyContinue
Get-VBRJob -Name "Critical VMs-1" | Start-VBRJob

This Power Shell Script, will find the job name “Critical VMs-1” via the Get-VBRJob command and will start the Backup job via Start-VBRJob.

And another Windows Batch Script to call the Critical VMs-1.PS1 PowerShell script and invoke it into the PowerShell;

Windows Batch Script “RunCritical-1.bat”

PowerShell.exe G:\Scripts\Critical VMs-1.PS1

I have repeated the same scripts for each job. Then in the task Scheduler in windows server 2008 R2, I configured two schedules for each backup job, so one schedule will run the same script RunCritical-1.bat from Sunday to Thursday as daily incremental and the same script will run on Friday on different time than the daily schedule, this will make sure that I have enough time window to run my backup jobs from early morning on Friday.  And since the Veeam Backup Job already configured as Active Full on Friday, it will automatically triggered and run as Full.

Hope it helps;

Get-ADUser – PowerShell & Active Directory

Well, Get-ADUser is a useful PowerShell command to get everything you required from single object in Active Directory. For instance, I have around 2500 objects in Active Directory and these objects are populated with an Employee ID in the Description Filed.

I have a requirement where I want to fetch the Name, Email ID and the Description ‘Employee ID’

Get-ADUser has several approaches to fetch this requirement, but  in here I will talk about the main thing which got my requirement fulfilled.

Get-Content C:\EmployeeID.txt | ForEach-Object { Get-ADUser -Filter {Description -eq $_} -Properties EmailAddress, Description | Select-Object Name, EmailAddress, Description } | Export-Csv C:\ID.csv -NoTypeInformation

All done, this will give a result of a CSV File with Name, Email Address and Description.

Thanks,

Cannot use CBT: Soap fault. Error caused by file

Hello,

I have encountered this warning on Veeam Backup & Replication version 6.1.0.205 on one Exchange Server 2007 VM.

The issue started the backup wants to run, but Veeam was unable to freeze the guest machine to take hot backup, and the snapshot left inside the datastore of the VM and Veeam didn’t remove it. Veeam job was configured to re-try the failed job after 15 minuets. Again, when it’s started, the Veeam created a snapshot and when it failed, Veeam didn’t remove the snapshot. This issue has caused the datastore to be filled up and left without space :)

Manually, I consolidated all the snapshots and deleted all of them. Then when I started the VM, luckily started fine.

But, when I re-run the Veeam Job, it started but very slow and gives the following warning. Cannot use CBT: Soap fault. Error caused by file.

Solution:

Edit the Veeam Backup Job, and in the Virtual Machines section, hit the button Recalculate. This will recalculate the exchange disks and will be re-added veeam/vCenter database. After that, the job started as incremental without warning and full backup without warning and faster :)

Thanks,

Cannot synchronize host : Cannot complete login due to an incorrect user name or password

Hello,

Today I decided to increase the disk space of my vCenter which is currently serving my production vSphere Infrastructure. As you are aware that I cannot increase the disk space due to the vCenter is a Management Operation and vConvertor will not allow me to do so. Even by connecting directly to the host with vConverter, another error message will appear which will not allow me to proceed further.

I have copied the VM with Veeam VM Copy “Thanks to Veeam for this Feature”, and I start re-configure the vCenter VM. I have increased the disk space of the C:\ drive and upload it to a datastore. I registered the VM and booted it up, it booted without any issues. I shutdown the original vCenter and I re-enabled the network interface of the modified vCenter.

I made sure all services are come up without issues, then I logged into the vSphere Client. All hosts are okay, ex one of the host which gives “Cannot synchronize host : Cannot complete login due to an incorrect user name or password” and “Cannot complete login due to an incorrect user name or password”.

Solution:

Disconnect the host and reconnect the host from vCenter will clear these errors.

Thanks,