0

Veeam File Copy – Error: The filename, directory name, or volume label syntax is incorrect

Posted by paris on Aug 28, 2017 in Random

Recently an Veeam Backup and Replication Software was upgraded from v8 to 9.5 , to fix an issue with Internal Database

Failed to copy item ‘\\network\Location’ Error: The filename, directory name, or volume label syntax is incorrect

this feature is not supported since version 9, so this might work but the product does not guarrantee this feature would work properly, and unfortunately we do not support features that does not supported by the version you are using.

please see this guide: https://helpcenter.veeam.com/docs/backup/hyperv/file_copy_source.html?ver=95

it says “You cannot use deduplicating storage appliances, shared folder backup repositories and shared folders as a source for the file copy job.”

This is annoying as it did work with Older Versions , in the end , I have to add \\network\Location\Folder ( extra folder on the end ) for the source folder instead of \\network\Location

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Tags: , , , , , , ,

 
0

Unable to truncate Microsoft SQL Server transaction logs. Details: RPC function call failed. Function name: [BlobCall]. Target machine: []. RPC error:The remote procedure call failed. Code: 1726

Posted by paris on Aug 3, 2017 in Random

A veeam backup showed a warning with the following error

Unable to truncate Microsoft SQL Server transaction logs. Details: RPC function call failed. Function name: [BlobCall]. Target machine: []. RPC error:The remote procedure call failed. Code: 1726

Leaving this to run the following day proved a success so must of been SQL Issue

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Tags: , , , ,

 
0

Cannot delete Credentials in Veeam due to Shared Folder

Posted by paris on Jul 12, 2017 in Fixes

For some reason I couldn’t delete credentials from Veeam due to them being used on a Shared Folder that did not existing in a backup repository or Tape to Folder. In the end I had to use SQL remove this.

  1. Verify the record to be deleted by running the following query against the configuration database (VeeamBackup by default);

    SELECT * FROM [backup.model.mrulist]
  2. Run the following query, changing <share path> to match the record to be deleted.

    DELETE FROM [backup.model.mrulist] WHERE url = ‘<share path>’
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Tags: , , ,

 
0

Veeam created _1 Folders for existing jobs

Posted by paris on Jun 7, 2017 in Random

On Restore of a Configuration backup , all the jobs started running Full backups in Veeam in folders with _1 in the same directory

Per this

“If a new backup set is created, but the folder containing the original backup set is not moved, deleted, or renamed, new backup files will be stored in a folder named <job name>_1.”

For some reason the backups were ignoring their existing backup sets and starting new ones filling up the drives and creating new VBK Files to resolve this

 

  1. Stop all the backups running
  2. Delete all the new folders on your Backup Location that were created with _1 , important : ( Check the Created Date as some of the _1 might be old backups )
  3. Go to Backup Infrastructure  , Backup Respositories , and run a rescan on all the repository that will clear these in ( Disk Imported ) 
  4. Now go to each job , edit the properties, Go to Storage , Backup Repository , and click Map Backup and choose the correct Repository for each job

Run a backup again and make sure it’s creating a file into the existing folder

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Tags: , , , ,

 
0

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]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Tags: , ,

 
0

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

Posted by paris on Jun 30, 2016 in Random

vmware_view_pilot-5132020[1]

  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]
Rating: 0 (from 0 votes)

Tags: , , , , ,

 
0

IBM Ultirium-ULT3580-HH6 SCSI Sequential Device Drives 2008

Posted by paris on May 3, 2016 in Random

PV124T[1]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

The Autoloader 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

The Readme file states : 

LT06 SAS

LT0-6

* 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]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Tags: , , ,

 
0

“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]
Rating: 3.8/10 (4 votes cast)
VN:F [1.9.22_1171]
Rating: -1 (from 1 vote)

Tags: ,

 
0

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

Posted by paris on Feb 7, 2016 in Random

Veeam[1]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

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]
Rating: 0 (from 0 votes)

Tags: , , , , , ,

 
0

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

Posted by paris on Feb 5, 2016 in Research

veeam_box_ONE[1]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]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Tags: , , ,

Copyright © 2017 Welcome to Pariswells.com All rights reserved. Theme by Laptop Geek. Privacy Policy