Documentation Center

Changing the automated XML database backup settings

The backup schedule is specified during the initial installation. This procedure shows how to change that schedule after the initial installation.

About this task

Backups occur when they are scheduled. Processes (such as publishing, or loading or upgrading a publication) can potentially collide with a scheduled backup process. Therefore, you can define an allowable time window to delay the process from starting to avoid a collision with the database backup. You define this time window in minutes by specifying a value for the pub.disable.timer config file entry (from the Content Delivery landing page, click Manage Application > Global Config), and ensure that the value reflects a quiet time before the process can start. For example, if the estimated process time is 2 hours, you would enter a value of 120 (the default time of 60 minutes multiplied by the process time of 2 hours in minutes).

Procedure

  1. On the Content Delivery server, edit the ContentDelivery_home/conf.xml file.
  2. Change the cron-trigger value in this element:
    <job type="system" name="check1" class="com.xyenterprise.xquery.lcutil.LCConsistencyCheckTask" cron-trigger="0 0 6 * * ?">
    You may use any standard cron expression string in the value. These are some examples of how to change the cron-trigger value.
    FrequencyDescription
    Every 6 Hours0 0 0/6 * * ?
    Every 12 Hours0 0 0/12 * * ?
    Daily0 0 2 * * ?

    This example performs the backup every day at 2:00 AM.

    Weekly0 0 2 ? * WED

    This example performs the backup on Wednesdays at 2:00 AM.

  3. Determine how many backup files you want to keep on the system by changing the value of this element:
    <parameter name="zip-files-max" value="5" /> 
  4. Save and exit the file.
  5. Restart the application or service.
    1. If you are using a third-party web application server, restart the application server's service. For example, if you are using Apache Tomcat, restart the Apache Tomcat service
    2. If you are using the bundled web application server, restart the Content Delivery database.
      • On Windows, restart the ContentDelivery XML Database service.
      • On Linux, log in as the root user, and type the following at a command prompt:

        /etc/init.d/SDL_LiveContent restart