vRanger tasks failing with "The database transaction was rolled back" message. (315807)

vRanger tasks failing with "The database transaction was rolled back" message.

Backup tasks fail with the following message: 

"The database transaction was rolled back"

• The disk where the DB resides is full. 
• The database maximum size limit has been reached.
• The vRangerPro database has been modified to restrict or disable the auto-growth property 

• If the disk where the vRangerPro database (MDF and/or LDF) resides is full, please add more space to the disk or relocate the MDF/LDF files to a drive that has enough space. In order to relocate the vRangerPro database, the database must be taken offline prior to any relocation process. 

• The database maximum size limit has been reached:
  1. SQL 2005 and 2008 Express Edition have a maximum database size of 4GB.
  2. SQL 2008R2, 2012 Express Edition and above have a maximum database size of 10GB. 
  3. In order to reduce the size of the vRangerPro database, a script has been created and attached to this solution in order to delete old and unused entries from the database. 

• The vRangerPro database has been modified to restrict or disable the auto-growth property:
  1. Within SQL Management Studio, locate the vRangerPro database.
  2. Right-click the database and select properties.
  3. Select the Files page. 
  4. If vRangerPro and vRangerPro_Log have an auto-growth property of none, modify it to reflect "By 1MB, unrestricted growth" for the vRangerPro DB and "By 10 percent, restricted growth" for the vRangerPro_Log file.  

   

SQL SCRIPT DISCLAIMER

The information in the script(s) provided is known to work successfully; however, they have not been officially tested by Quest Software Quality Control. If any of these instructions are changed and/or incorrectly used, intentionally or unintentionally, this solution becomes unsupported by Quest Software Support and Development. Quest Software Support and Development recommend to always make a backup of the current database prior to execution of any script(s) that may modify it. For customization of the SQL script, please contact our Professional Services Organization.

 

In order to take a backup of the vRangerPro database, please follow these steps:

1. Within SQL Management Studio, locate the vRangerPro database.
2. Right-click the database and select "Tasks".
3. Select the "Backup..." option. 
4. Keep the default values.
   • Backup Type: Full
   • Copy-Only backup: Unchecked
   • Backup component: Database
   • Destination: Backup to Disk
5. Click "Add..." to add a location for the backup file.
6. Click "..." in order to browse the location where the backup should be stored and the file name. The file extension should be ".bak" 
7. Once done, click OK to close the "Select Backup Destination" window.
8. Click OK to perform the backup.

The PurgeDB SQL script attached to the solution only clears removed jobs, backup history, and failed tasks if needed. Before running the script, you will need to modify the following lines:

• USE vRangerPro (The default name of the DB is vRangerPro, but this may be changed by a SQL administrator)
• SET @test_run = 1 (Default is 1 and will show how much data can be purged. Change to 0 to allow the script to clean the database)

purgeDB03c

This is a "Quick Share" article provided by Quest Support. All content included in this article is unverified and provided “as is” for information purposes only. Although reasonable efforts have been made to present complete, current and accurate content, no guarantees for the completeness, currency or accuracy of this content is made. Accordingly, Quest makes no representation, warranty or endorsement of any kind regarding this content, whether express or implied, including but not limited to the implied warranties of satisfactory quality, fitness for a particular purpose, non-infringement, compatibility, security, accuracy or completeness.