SQL 2016 unresponsive during VSS snapshots

James Barrett 1 Reputation point
2022-03-25T16:49:13.65+00:00

Server 2016
SQL 2016
Beast of a box, 128GB memory, Dual Xeon E5-2630 (20 CPU each or something like that)Dell Perc H730P, two volumes C and F, Raid 10, etc, etc
We are failing to get backups as the system seems to deadlock during the snapshots. I can get a backup/snapshot of C (OS) but deadlocks on F (SQL). Seeing the same thing happen when I test the VSS Writers *see below). List writers shows no errors. One of the databases of 500GB and I've given the 3rd part backup and diskshadow backup 30 minutes to create a snapshot but it never finishes. During this time SQL databases become unresponsive which considering it drives multiple websites and services I have limited windows for doing this type of testing. Windows and SQL updates all applied, SP3 on SQL.
DISKSHADOW> set context persistent

DISKSHADOW> set verbose on

DISKSHADOW> begin backup

DISKSHADOW> add volume C: alias VolumeC

DISKSHADOW> add volume F: alias VolumeF

DISKSHADOW> writer verify {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

DISKSHADOW> create
Excluding writer "Shadow Copy Optimization Writer", because all of its components have been excluded.
Excluding writer "MSSearch Service Writer", because all of its components have been excluded.
Component "\BCD\BCD" from writer "ASR Writer" is excluded from backup,
because it requires volume which is not in the shadow copy set.
The writer "ASR Writer" is now entirely excluded from the backup because the top-level
non selectable component "\BCD\BCD" is excluded.
All components from writer "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}" are selected.

Including writer "Task Scheduler Writer":

  • Adding component: \TasksStore

Including writer "VSS Metadata Store Writer":

  • Adding component: \WriterMetadataStore

Including writer "Performance Counters Writer":

  • Adding component: \PerformanceCounters

Including writer "System Writer":

  • Adding component: \System Files
  • Adding component: \Win32 Services Files

Including writer "SqlServerWriter":

  • Adding component: \SQL16\master
  • Adding component: \SQL16\model
  • Adding component: \SQL16\msdb
  • Adding component: \SQL16\ReportServer
  • Adding component: \SQL16\ReportServerTempDB
  • Adding component: \SQL16\DK
  • Adding component: \SQL16\CDM
  • Adding component: \SQL16\Web
  • Adding component: \SQL16\JSAuth
  • Adding component: \SQL16\CRM
  • Adding component: \SQL16\Bidlot
  • Adding component: \SQL16\BB
  • Adding component: \SQL16\ASPState
  • Adding component: \SQL16\AutoAnalysis
  • Adding component: \SQL16\UserAccounts
  • Adding component: \SQL16\ReportServer2
  • Adding component: \SQL16\ServiceHistory
  • Adding component: \SQL16\SSISDB
  • Adding component: \SQL16\Inventory
  • Adding component: \SQL16\Braze
  • Adding component: \SQL16\M1
  • Adding component: \SQL16\vAuto
  • Adding component: \SQL16\ThirdPartyData
  • Adding component: \SQL16\ConfigurationManagement
  • Adding component: \SQL16\Assurant
  • Adding component: \SQL16\ImageInventory
  • Adding component: \SQL16\MPI
  • Adding component: \SQL16\DAConfiguration
  • Adding component: \SQL16\DAReporting
  • Adding component: \SQL16\FVS
  • Adding component: \SQL16\aspnetdb
  • Adding component: \SQL16\HelpDesk
  • Adding component: \SQL16\Dashboard
  • Adding component: \SQL16\Referral
  • Adding component: \SQL16\MembershipSecurity
  • Adding component: \SQL16\LotTracker
  • Adding component: \SQL16\EDW
  • Adding component: \SQL16\IHQ
  • Adding component: \SQL16\DoNotCall
  • Adding component: \SQL16\AuditLog
  • Adding component: \SQL16\ADP
  • Adding component: \SQL16\Auto

Including writer "Registry Writer":

  • Adding component: \Registry

Including writer "COM+ REGDB Writer":

  • Adding component: \COM+ REGDB

Including writer "WMI Writer":

  • Adding component: \WMI
Windows Server Backup
Windows Server Backup
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Backup: A duplicate copy of a program, a disk, or data, made either for archiving purposes or for safeguarding valuable files from loss should the active copy be damaged or destroyed.
461 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Stacy Clark 21 Reputation points
    2022-04-18T07:18:09.6+00:00

    Is your SQL database part of your domain or just a local database?

    Try running it with local admin permissions.

    Are people using the database while you are trying to backup? Try off hours and disconnect the server from anyone or anything querying it.

    Last, check the SQL database logs for any errors. It may give you insight into what's going on.

    0 comments No comments