Posts Tagged ‘veeam’

A Server 2012 R2 started getting VSS Writer Errors randomly in Veeam backup job. The server is running AADconnect which is set to autoupdate

A restart of the VSS SQL Writer which usually fixes this did not resolve the issue.

A look in the event log shows

A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:
PrepareForSnapshot Event

Context:
Execution Context: Writer
Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Name: SqlServerWriter
Writer Instance Name: SQL Server Code-Named ‘Denali’ CTP2:SQLWriter
Writer Instance ID: {6c73bfe9-f82f-4854-bec4-4382c314a583}
Command Line: “C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe”
Process ID: 4292

With some

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=4292. Thread=3940. Client. Instance=LOCALDB#SHDA41B2. VD=Global\{9C831400-DE4D-4364-BA22-A8299CF545FC}4_SQLVDIMemoryName_0.

Looks like you need to download the SQL Fix from here : https://support.microsoft.com/en-us/help/2983175/cumulative-update-package-2-for-sql-server-2012-sp2

Mirror Here : https://mega.nz/#!3AZ3gK7I!kDPhnAlur4XtslKxGXwmbnLitJiwN9R6rK-z4Rh0N-s

 

**Update , fix does not seem to work

A repair on the SQL database and then run the below script

Looks like this might be an issue with AADcoonect

https://github.com/pariswells/pariswells.com/blob/master/fixaadconnectvsswriter.ps1

 

**Update

 ADSync launches an SQL Server Local DB under it’s own user account
– The User Profile Service thinks ADSync is no longer logged on, and unloads the registry
– SQL Server though still has handles to the registry, but they’re invalid now

Detailed explanation:
https://support.microsoft.com/en-us/help/2287297/a-com-application-may-stop-working-on-windows-server-2008-when-a-user

In short: Computer Configuration->Administrative Templates->System->User Profiles->Do not forcefully unload the user registry at user logoff

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

 Error: Unfreeze error: [Backup job failed.
Cannot create a shadow copy of the volumes containing writer’s data.
A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{60e3e5dd-73fc-46d6-ab6b-6b8723df09e3}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]

I restarted the SQL Server VSS Writer ( Can be done during production as only used for backups ) and a retry still errored.

In the end I needed to reboot the server

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

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)

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)

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)

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)

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)

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)

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)

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)