Attix5 Pro FAQ
Search:     Advanced search

Configuring MS SQL database maintenance settings for each database

Article ID: 200
Last updated: 08 Jul, 2015

Symptom

When backing up MS SQL databases you may encounter errors such as the following:

Message: 20:00:13 [MS SQL Server Plugin] Truncating log file for database master
Warning: 20:00:13 [MS SQL Server Plugin] Unable to export database localhost:1433.master: Cannot back up the log of the master database. Use BACKUP DATABASE instead.
Message: 20:00:14 [MS SQL Server Plugin] Exporting database longcat
Message: 20:00:16 [MS SQL Server Plugin] Truncating log file for database longcat
Warning: 20:00:16 [MS SQL Server Plugin] Unable to export database localhost:1433.longcat: The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.

Cause

These errors occur when the SQL plug-in maintenance mode does not match the maintenance mode of the database.

In V5 of the Attix5 Pro Backup Client, it is possible to configure database maintenance for each individual database.

In V6 and V7, per database maintenance is not supported in the Backup Client GUI. Maintenance can only be set at the plug-in top level, and any existing database maintenance settings cannot be modified using the GUI.

This is due to a legacy compatibility issue within the Backup Client. The issue is categorised as non-critical, and a workaround is possible, so is scheduled to be addressed in a later V7 release.

Solution

The workaround for the maintenance setting is as follows:

  1. Close the GUI and stop the Attix5 Pro service in the Windows Services menu.
  2. Navigate to the Attix5 Pro Backup Client SE installation folder (by default C:\Program Files\Attix5 Pro\Backup Client SE\)
  3. Make a copy of the backupset.xml (or appropriate other backupset_n.xml if configuring another backup set) in case you make a mistake.
  4. Open backupset.xml in notepad.
  5. Search through the XML for the appropriate plug-in and instance tags.
  6. The instance can be identified by the "name" field within the opening instance tag.
  7. Locate the database tag by the name field, and change the "logmaint" setting to either "NONE" for no log maintenance or "TRUNCATE" for log maintenance. Both values should be in upper case.
  8. In the example below, maintenance is set at the top level, at the instance and on the databases to "TRUNCATE".
    <plugin dumpFolder="C:\Program Files\Attix5 Pro\Backup Client SE\SQLDump" id="7" logmaint="TRUNCATE" name="MS SQL Server" version="3.9">
      <instance logmaint="TRUNCATE" name="localhost:1433" password="0123456789" port="1433" server="localhost" username="0987654321">
        <database logmaint="TRUNCATE" name="longcat" select="include"/>
        <database logmaint="TRUNCATE" name="tacgnol" select="include"/>
        <database logmaint="TRUNCATE" name="monorail" select="include"/>
        <database logmaint="TRUNCATE" name="allyourbase" select="include"/>
      </instance>
    </plugin>
  1. To change all the databases except "allyourbase" to not run maintenance, change the settings as follows:
    <plugin dumpFolder="C:\Program Files\Attix5 Pro\Backup Client SE\SQLDump" id="7" logmaint="TRUNCATE" name="MS SQL Server" version="3.9">
      <instance logmaint="TRUNCATE" name="localhost:1433" password="0123456789" port="1433" server="localhost" username="0987654321"> <database logmaint="NONE" name="longcat" select="include"/>
        <database logmaint="NONE" name="tacgnol" select="include"/>
        <database logmaint="NONE" name="monorail" select="include"/>
        <database logmaint="TRUNCATE" name="allyourbase" select="include"/>
      </instance>
    </plugin>
    Note: Changing the top level or instance level maintenance setting may not propagate changes to existing databases. In this scenario, any newly added databases will inherit the setting from the instance, so in this case would be set to "TRUNCATE". Should the problem occur, to set new databases to have no log maintenance, change the instance setting to "NONE". For example:
    <plugin dumpFolder="C:\Program Files\Attix5 Pro\Backup Client SE\SQLDump" id="7" logmaint="TRUNCATE" name="MS SQL Server" version="3.9">
      <instance logmaint="NONE" name="localhost:1433" password="0123456789" port="1433" server="localhost" username="0987654321">
        <database logmaint="NONE" name="longcat" select="include"/>
        <database logmaint="NONE" name="tacgnol" select="include"/>
        <database logmaint="NONE" name="monorail" select="include"/>
        <database logmaint="TRUNCATE" name="allyourbase" select="include"/>
      </instance>
    </plugin>
  1. Save and close the backupset.xml file.
  2. Restart the service and open the GUI. You will not see any change to individual database settings within the GUI as these are not displayed.
  3. Run a backup and confirm that no log maintenance errors are seen.
Article ID: 200
Last updated: 08 Jul, 2015
Revision: 6
Views: 4723
Comments: 0
Posted: 12 Nov, 2012 by Flood A.
Updated: 08 Jul, 2015 by Du Plessis S.
This article was:  
Prev   Next
Article 194 - GUI fails to load with the error "Java Virtual Machine Launcher"     Article 203 - Invalid encryption key for file error when restoring