Monthly Archives: May 2014

Creating VBM from scratch

Excellent script posted by “tsightler” on the Veeam forums regarding creating a VBM file from scratch; http://forums.veeam.com/powershell-f26/creating-vbm-from-scratch-t20568.html

Indeed, having a VBM file is not required to be able to restore files or VMs, as a matter of fact, the script referenced above, as well as the one that I post below, use this fact to create VBM files from scratch. For my simple script below you use the Veeam GUI to import the VBK, set the variables in the script (backup name) and the run it. It uses an internal function call to create the VBM XML data, make a minor modification to the JobName and then writes it the data out to the VBM. If you have only the VBK file you must use the “Import” button to browse and locate the VBK file and have it imported into Veeam, but it should work with no problem.

Creating a VBM can sometimes be useful. One common use for me is to create a seed for backup copy jobs from a “normal” backup chain. Normally a backup copy job must be seeded from a single restore points/VBK file which prevents you from using an existing backup chain for a seed since these almost always have multiple chains, however, using this script you can grab just the most recent VBK from an existing backup chain, import it, run the script to create a VBM, and then combine them to use as a seed for a BCJ.

Anyway, just in case it is needed here is the script that I use to create VBM files from scratch. It’s basically a modified version of the script referenced above, but much simpler as I removed the GUI and the automatic import of the VBK, you can just use the Veeam GUI for those steps. The script creates the VBM file on the current users Desktop, but that’s easy to change to any path. After running the script you can place the VBK and the newly created VBM file in any repository. Since it now has an appropriate VBM file a simple rescan of the repo will cause it to show up in the GUI and it can now be used for mapping backup or backup copy jobs.

Copy the below into a Veeam powershell cli

asnp “VeeamPSSnapIn” -ErrorAction SilentlyContinue

$BackupName = “”
$Backup = Get-VBRBackup -Name ($BackupName + “_imported”)
$VBMFile = “$env:UserProfileDesktop” + “$BackupName” + “.vbm”

$Data = [Veeam.Backup.Core.CBackupMetaGenerator]::GenerateMeta($Backup)
$Data.Serialize() | Out-File $VBMFile
$xml = New-Object XML
$xml.Load($VBMFile)
$xml.BackupMeta.JobName = $BackupName
$xml.Save($VBMFile)
Remove-VBRBackup -Backup $Backup -Confirm:$false

Empty Folder(s) in Datastore after Replication job runs?

This behavior is caused when Veeam is configured with a different target datastore then what the replica VM currently resides on. Veeam creates a folder to hold the data on that datastore because it does not see anything there. Once it goes to write the data and work with the replica, it finds the correct location via the reference ID of the replica VM.

The solution to this is to verify the datastore location in VMware, and then edit the replication job to match this. After doing this, you can delete the empty folders, though it is highly advised to check each folder individually before deletion to verify they are in fact all empty.

source: http://www.veeam.com/kb1793

Having trouble importing reverse incremental backups into Veeam?

Are you having trouble trying to import “reverse incremental” backups into Veeam? I recently encountered a problem where no matter how I tried to import the reverse incremental backup it would only show the synthetic full backup, all of the reverse incremental’s were being missed.

Turned out the .vbm file was overwritten and after deleting this file I could manually import the synthetic backup along with all the previous reverse incremental points in time.

vSphere 4.x Support

vSphere 4.x Support

vSphere 4.x moves from the General Support phase into the Technical Guidance phase on May 21, 2014. During Technical Guidance, customers receive support but VMware does not offer new security patches or bug fixes. For information on what is provided during Technical Guidance, see the VMware support lifecycle policy. VMware has developed a vSphere 4.x Extended Support offering for customers who require triage of Severity 1 issues and new security fixes after May 21, 2014.

Veeam Error : Failed to open VDDK disk

I have run into this issue a couple times recently where the proxy has gotten itself into trouble and failing the Veeam backup job.

Its usually springs up out of no where after the backups have been running smoothy for months.

4/05/2014 9:07:51 PM :: Error: Client error: Failed to open VDDK disk [[DS1_Tier1_********_Controller] [1.10] **********/[1.10] *********-BNE_1-000028.vmdk] ( is read-only mode – [true] )
Failed to open VMDK.
Logon attempt with parameters [VC/ESX: [192.168.**.**];Port: 902;Login: [****];VMX Spec: [moref=29];Snapshot mor: [29-snapshot-364];Transports: [nbd];Read Only: [true]] failed because of the following errors:
Failed to process [calcDiskDigestsCli].

If you see this error message, I suggest closely examining each proxy used by Veeam i.e can you log into the server, do you have free space left on the OS boot partition.

Check the disk manager for any additional disks that should not belong there, i.e virtual proxies use Veeam Hot Add.

Using the vSphere Client go into the Virtual Machine Properties, open the hardware tab and  check what disks are virtually attached.

It so happened that the virtual proxy had the virtual drives from virtual machine that was failing to backup. After I removed them the job worked

 

vm hardware