Creating and configuring backups - Data360_Analyze - 3 - 3.12

Data360 Analyze Server Help

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 Analyze
Version
3.12
Language
English
Product name
Data360 Analyze
Title
Data360 Analyze Server Help
Copyright
2023
First publish date
2016

By default, a backup is performed daily at 12 p.m 2:00 a.m, and the twenty most recent backups are saved. Additionally, if you are an administrator, you can start a system backup at any time from the Settings page in the Directory.

Note: Backup files can only be created while Data360 Analyze is running. If the application is not running when a backup is scheduled, the backup will not be created until the next scheduled time after restart.

During installation, you can select a backup file to restore your system to an earlier state, as described in the installation guide.

Note: The backup / restore facility can only be used to restore your system to a previously known state on the same version. For example, if you are installing Data360 Analyze 3.6.2, you can only restore to a backup file that was created on a 3.6.2 installation.

Running a backup on demand

  1. From the Directory, select Settings > Backup.
  2. To create a backup of your system, select Create Backup Now.
  3. In the Create Backup Now dialog, click Backup.
  4. Wait for the system backup to complete, then click Close.

Editing backup settings

If needed, you can modify the default backup settings, for example, you can change the location of saved backup files, or you can increase the number of most recent files that are saved.

  1. Navigate to the "cust.prop" file located at:

    %LOCALAPPDATA%/Data360Analyze/site/conf/cust.prop if you selected Local User during installation.

    C:/ProgramData/Data360Analyze/site/conf/cust.prop if you selected All Users during installation.

    <Data360Analyze site configuration directory>/conf/cust.prop

    For example: C:/Users/<username>/Data360Analyze/site-7731/conf/cust.prop

  2. Open the cust.prop file. The default backup settings are shown in the following table. To edit any of the backup settings, you can replace the default property values (shown in red below) with new values in the same format.
    CAUTION:
    If you upgraded from 3.0.5, backups are not created by default. In this case, you will need to manually add the below properties to your cust.prop file if you want backup files to be created.

    Property Description

    ls.lae.system.backup.backupFileLocation="%LOCALAPPDATA%/Data360Analyze/site/data"

    ls.lae.system.backup.backupFileLocation="C:/ProgramData/Data360Analyze/site/data"

    ls.lae.system.backup.backupFileLocation="<Data360Analyze data directory>/data-7731"

    For example: ls.lae.system.backup.backupFileLocation=" C:/Users/<username>/Data360Analyze/data-7731"

    The directory where the backup files are stored.

    The default location depends on the option that you selected during installation.

    Note: If you have upgraded from a release prior to 3.6.0, the backups may be in the original default directory /Data3SixtyAnalye/site/data
    Note: If you have upgraded from a release prior to 3.6.0, the backups may be in the original default directory: <Data3SixtyAnalye data directory>/data-7731
    ls.lae.system.backup.maxBackupFiles= 20 The number of most recent files that are saved.
    ls.lae.system.backup.scheduledBackupsEnabled=true

    Enable or disable the creation of backup files.

    Set this property to false if you do not want to create backup files.

    ls.lae.system.backup.scheduledBackupsCronExpr="0 0 2 1/1 * ? *"

    The time when the backup file is created. The time must be specified as a Cron expression, using the Quartz Job Scheduler format. For more details and formatting examples, see:

    http://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html

    and

    https://www.freeformatter.com/cron-expression-generator-quartz.html

    ls.lae.system.backup.backupErrorThreshold=1000

    The number of errors that can occur during backup before the backup aborts. Setting the value to 0 will guarantee that the backup has no errors, but may also cause the backup to never be taken successfully. Setting the value to a negative value will guarantee that a backup is taken successfully, but the backup might contain errors.

  3. Restart Data360 Analyze for the changes to take effect.
Tip: The Data360 Analyze "site" and "data" directories can be any location and are set during installation. The examples above show default locations for these directories.

What's included in a Data360 Analyze backup?

A Data360 Analyze backup contains the latest user-specific and system information which can be used during a future installation to restore your system to an earlier state, including:

  • Users and user preferences
  • Data flows and library nodes, including node run statuses
  • Schedules
  • System configuration
  • Directory structure

Note: The site folder (%LOCALAPPDATA%/Data360Analyze/site) is not currently included as part of a Data360 Analyze backup. We recommend that you make a copy of the following files and folders which you can then use if needed to replace the default files in the same location of a future installation:• The site/data/securityStore.jks file, as this contains your encryption and decryption keys.• The site/lib and site/conf folders, as these contain custom information such as JAR files and the cust.prop file.It is also worth considering whether you want to back up the temporary data produced by data flow runs. If so, you should also make a copy of the site/data/executions folder.
Note: The site directory (e.g. C:\Users\<username>\Data360Analyze\site-7731) and the data directory (e.g. C:\Users\<username>\Data360Analyze\data-7731) are not currently included as part of a Data360 Analyze backup. We recommend that you make a copy of the following files and folders which you can then use if needed to replace the default files in the same location of a future installation:• The securityStore.jks file found in the data directory, as this contains your encryption and decryption keys. • The conf and lib folders found in the site directory, as these contain custom information such as JAR files and the cust.prop file.It is also worth considering whether you want to back up the temporary data produced by data flow runs. If so, you should also make a copy of the executions folder found in the data directory.

See also Stopping the scheduler.