# Export failed startindex cannot be less than zero – Veeam Restore

Posted by paris on Apr 12, 2017 in Random

Just tried to restore a veeam SQL backup , however got the error message

Export failed startindex cannot be less than zero

Changed the location of the MDF/LDF files to local instead of a network path , and this fixed the issues

VN:F [1.9.22_1171]
VN:F [1.9.22_1171]

# Vmware : Cannot create snapshot. Operation not allowed in current state

Posted by paris on Jun 30, 2016 in Random

1. Login to the host where the virtual machine lies and try and do a snapshot via here instead of VCentre
2. If Take Snapshot is greyed out on the host , then check the settings of the device for :
• Does it have an PCI Devices cards mapped to it? E.g. for Use of Tape Drives. If so these will need to be removed as Vmware doesn’t support snapshotting these.
• Does it have any physical mapped Drives to it instead of virtual , again is not supported for snapshotting
1. Try shutting down the VM to see if you can snapshot it shutdown insteaf of powered off
1. Restart the Management Agents on the hosts
VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)
VN:F [1.9.22_1171]

# IBM Ultirium-ULT3580-HH6 SCSI Sequential Device Drives 2008

Posted by paris on May 3, 2016 in Random

Trying to install a Dell 124T Autoloader to work with Veeam. We have this installed on a server with Backup Exec and the driver seemed to be interfering. Moving the tape drive to another server I had the reinstall the drivers

http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=P48C1

Worked for the autoloader , however no drivers found for the LT0 6 Drive

### * Use Windows inbox driver

However a search to update drivers didn’t install anything

Turns out you need this windows update!

https://support.microsoft.com/en-gb/kb/2619836

VN:F [1.9.22_1171]
VN:F [1.9.22_1171]

# “This computer does not meet system requirements” veeam

Posted by paris on May 3, 2016 in Random

Trying to install Veeam on a server 2008 and got greeted with the above message

“This computer does not meet system requirements”

However nothing staying why – relating to CPU/Memory or OS

Turns out the server had not been updated to SP1 for 2008 R2

VN:F [1.9.22_1171]
VN:F [1.9.22_1171]
Rating: -1 (from 1 vote)

# Veeam Storage version [3701403] is not supported for read-only access.

Posted by paris on Feb 7, 2016 in Random

After copying a VBK and VBM file from one server to another , after a test restore the following error showed up in the logs and in Gui

 Source code
Storage version [3701403] is not supported for read-only access.
--tr:Failed to open storage for read access. Storage: [\\path\to\file.vbk].
--tr:Cannot apply patches stored in folder [HostFS://\\path\to\file.vb[41e6829d-533e-480f-8b38-3726d3fa47a2 (vm-4628)]]
--tr:Failed to build restore point.

After my own research ( Trying to copy it locally ) and contacting Veeam support , it turns out the VBK file was corrupt some how. Recopying the file resolved this issue

VN:F [1.9.22_1171]
Rating: 8.0/10 (1 vote cast)
VN:F [1.9.22_1171]

# Cannot login to Veeam One Reporter ( Veeam One Business Reporter works )

Posted by paris on Feb 5, 2016 in Research

After installing Veeam One , login to Veeam One Business View worked , however Veeam One Reporter with the same login details came back with

The specified username or password is not correct. Provide new credentials and try again.

After Checking the C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe and what the service was started as these where all correct.

I was using firefox to login , so I tried with Internet Explorer with the same details and it worked straight away!

***Update if this still doesn’t work

Log onto the server where Veeam ONE is installed.

Open Local Users and groups, ensure that the user in question is added only to the Veeam ONE administrators group.

Log off then log back on and attempt opening the monitor console.

VN:F [1.9.22_1171]
VN:F [1.9.22_1171]

# No Windows PowerShell snap-ins matching the pattern ‘VeeamPSSnapIn’ were found.

Posted by paris on Jan 20, 2016 in Random

Trying to get the Solarwinds Veeam Backup and Recovery Template working, After installing the powershell plugin via BPS_x64.msi, when trying to run Powershell commands , I could not include to the Veeam VeeamPSSnapIn.

Turns out it hadn’t installed and referenced the .dll properly , below can be saved as .reg files and run , depending where your Veeam.Backup.PowerShell.dll is located

 Source code
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\VeeamPSSnapIn]
"PowerShellVersion"="2.0"
"Vendor"="Veeam"
"Description"="This is a PowerShell snap-in that includes the Veeam's cmdlet."
"VendorIndirect"="VeeamPSSnapIn, Veeam"
"DescriptionIndirect"="VeeamPSSnapIn,This is a PowerShell snap-in that includes the Veeam's cmdlet."
"Version"="8.0.0.0"
"ApplicationBase"="C:\\Program Files\\Veeam\\Backup and Replication\\Backup"
"AssemblyName"="Veeam.Backup.PowerShell, Version=8.0.0.0, Culture=neutral, PublicKeyToken=bfd684de2276783a"
"ModuleName"="C:\\Program Files\\Veeam\\Backup and Replication\\Backup\\Veeam.Backup.PowerShell.dll"

 Source code
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\VeeamPSSnapIn]
"PowerShellVersion"="2.0"
"Vendor"="Veeam"
"Description"="This is a PowerShell snap-in that includes the Veeam's cmdlet."
"VendorIndirect"="VeeamPSSnapIn, Veeam"
"DescriptionIndirect"="VeeamPSSnapIn,This is a PowerShell snap-in that includes the Veeam's cmdlet."
"Version"="8.0.0.0"
"ApplicationBase"="C:\\Program Files\\Veeam\\Backup and Replication\"
"AssemblyName"="Veeam.Backup.PowerShell, Version=8.0.0.0, Culture=neutral, PublicKeyToken=bfd684de2276783a"
"ModuleName"="C:\\Program Files\\Veeam\\Backup and Replication\\Veeam.Backup.PowerShell.dll"
VN:F [1.9.22_1171]
VN:F [1.9.22_1171]

# HA unsuccessfully failed over VM on HOST in cluster vSphere HA will retry if the maximum number of attempts has not been exceeded. Reason: Operation timed out.

Posted by paris on Jul 8, 2015 in Research

Recently during a Veeam backup HA kicked in due to a problem with VCenter and marked two machines as Invalid

•  Veeam started backup and created snapshot on affected VMs
• HA kicked in after VCenter Server failure
• Vcenter tried to move the machines after the HA event but they were locked by the snapshot Veeam had (the hypervisor has a lock because of the snapshot)
• Machine couldn’t move but Vmware removed them from inventory and tried to register them to another host, without success
• Machines marked as Invalid, Removing machines from Inventory and registering the machines manually did not work
• The machines are locked however still powered on and response

Fix to get VM’s registered on VCenter

• Stop any tasks (i.e. Veeam) that might trigger a snapshot on affected machines
• Temporarily disable DRS in the cluster (when we power up the machine we don’t want Vsphere to power it up on another host otherwise the lock will persists)
• Power affected VMs off gracefully from within the OS.
• Login to vcenter and select Host which failed and . Unregister “unkown” VM’s listed (these should be the actual Vms). Unregistering should remove the lock.
• Register the virtual machines using the vmx files in the datastore
• Check no snapshots are present, if yes delete or consolidate
• Power on Vm
• Re-enable DRS
VN:F [1.9.22_1171]
VN:F [1.9.22_1171]

# Veeam Backup Job “finished with error” after password change

Posted by paris on May 5, 2014 in Fixes

After going in to each of the servers it displays the error “Cannot complete login due to incorrect username or password”

After a recent password change our Veam jobs would start for a few seconds then fail.

In Veam, go to File , then Manage Credentials