Backup Options

Backup Options

Check Backup Options to define backup provisions.
Clearing Backup Options indicates that you do not want to set any backup provisions. By default, Backup Options is cleared.

When you select Backup Options, you can choose between two backup modes to be applied before copying any files into the destination directory on the target — Save with suffix or Backup.

Save with suffix

Save a backup of any file that would be overwritten by renaming the original file on the target before copying the new file into the same destination directory. File renaming is done by appending the suffix that you define in the Suffix field to the names of the original files. For example, if you define .bak as your suffix, the original file foo gets saved as foo.bak.

Later, if you need to roll back a File Deploy Job, a custom script can look for all files in the destination directory with a particular suffix and rename them by removing that suffix. For example, foo.bak gets restored as foo.

Backup

Copy the contents of the destination directory (defined on the General panel) to a backup location that you specify, before copying any files into that destination directory. Use the following fields to specify the backup location:

• Directory — The beginning of the path to the backup location. This directory defaults to /backup. You can specify a network location, such as //eastwin2k2/backup. If you do not specify a network location, the backup occurs on the Application Server host.
  If the host for this backup location is running UNIX and the backup directory does not already exist, then you must have root permission to create this directory. If you are not root, an error occurs. If the /backup directory (or any other directory that you specify instead) already exists, you must have read and write permission for that directory.
  Note that additional child directories are appended to this path, as discussed below.
• Name — Another string to uniquely identify the backup. This string is used as the name of a child directory along the path to the final backup location. For example, deploy1.

To ensure a unique backup location for each target server and for each time that you run the File Deploy Job, the final backup location path uses the following format:

<backup directory>/<backup name>/<target server>/<time stamp>/<name of destination directory>