• State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 27 subscribers
  • Views 8347 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SQL Locks

carl.fedak
over 6 years ago

Hello,

 

We are using MSSQL 2014, and RR 6.1.1.137.

Our database server has C (170GB), D (2.2 TB), E (360GB), F (5.6TB).

Currently all databases are set to simple recovery, and our schedule is set to 2 hours.

Unfortunately, at least once a day we have a period where our application (custom built .NET web app) throws a bunch of errors saying it cannot write to the database, we are getting locks.  These are happening only at scheduled backup times, and typically when that happens we have 2-3 retries of the backups.

This is, of course, causing client impact.

Our database is not particularly busy, I feel like maybe we are just doing something wrong or Rapid Recovery would never really work for live databases.  In which case I'm unsure how they could be selling it.

One suspicion, we do have some fairly long running transactions in the application.  These are not changeable at this time.  Could this be causing issues like I've mentioned where DB locks are occurring?

 

Looking for any tips at all.

Parents
  • 0 over 6 years ago
    It is possible your server may be experiencing a volume shadow copy writer issue. Our agent utilizes Microsoft volume shadow copy writers to prepare our snapshots, and it is the job of these writers to provide the "quiescing" of data with live applications (such as SQL) to prepare application-consistent snapshots.

    You could confirm with this via Windows Event Logs, and troubleshoot their status, but I would strongly recommend reaching out on our online help chat or opening a service request for further investigation. Go to - support.quest.com/rapid-recovery.

    Additionally, I suggest for you to upgrade your core and agent to the latest version (6.1.3) and then monitor for the behavior described.
Reply
  • 0 over 6 years ago
    It is possible your server may be experiencing a volume shadow copy writer issue. Our agent utilizes Microsoft volume shadow copy writers to prepare our snapshots, and it is the job of these writers to provide the "quiescing" of data with live applications (such as SQL) to prepare application-consistent snapshots.

    You could confirm with this via Windows Event Logs, and troubleshoot their status, but I would strongly recommend reaching out on our online help chat or opening a service request for further investigation. Go to - support.quest.com/rapid-recovery.

    Additionally, I suggest for you to upgrade your core and agent to the latest version (6.1.3) and then monitor for the behavior described.
Children
No Data