About Backup Data and Configuration Data in schedules

Two device properties are critical in setting up backup schedules and backup and compare schedules:

Backup Data

and

Configuration Data

.

Some devices use both properties and some devices use only Configuration Data or Backup Data. The following list shows which devices use which properties and the following sections explain how the backup and compare schedules work for the two cases. Any asset types not listed cannot be used in backup and compare schedules.

For devices that use both Backup Data and Configuration Data

In the case of certain devices, such as Siemens S7 Controllers (STEP7), Custom Devices, and Allen-Bradley PowerFlex Drive devices, files in the device are very different from the files used with the editing software, so both Backup Data and Configuration Data are needed.

When setting up the device, you place user data, for example, the files created with the editing software for a Siemens S7 (STEP7) device in Configuration Data.

During the first backup operation, files from the device are stored in Backup Data. (Alternatively you can place a binder with an empty folder in Backup Data when adding the device asset and device files are placed in that binder during the first backup operation.) During subsequent backup-only operations, data from the physical device is uploaded and a new version is placed in Backup Data.

When setting up a schedule for the device you select a version of the Backup Data and, if desired, Configuration Data, to use for comparisons.

During a backup and compare operation, data from the physical device is uploaded and compared to the designated version of the Backup Data and, if specified, Configuration Data. The uploaded data is stored as a new Backup Data version depending on the result of the compare and on the

Create New Backup Version

setting in the schedule properties.

When differences are detected in the Configuration Data:

As has been stated, the data from the processor stored in Backup Data is different from the data from the editing software stored in Configuration Data. So what happens when changes have been made online on the processor so that the Configuration Data is now different from the processor data and the Backup Data? You can do one of two things to update the Configuration Data:

For devices that use Configuration Data only

When setting up the device, you place a master copy of the device files in Configuration Data in the device properties. This data is stored in Archive for version control. When setting up a schedule for the device, you specify which version of the Configuration Data to use as the Master for comparisons.

During a backup-only operation, data from the physical device is uploaded and a new version is placed in Configuration Data.

During a backup and compare operation, data from the physical device is uploaded and compared to the designated master version in Configuration Data. A new version is placed in Configuration Data depending on the result of the compare and the Promote New Upload to Master setting in the schedule properties.

For assets that use Backup Data only

When setting up an asset that uses Backup Data only, a backup binder or file does not exist yet in most cases. You may specify the Backup Data or run a backup schedule to automatically create one. This data is stored in Archive for version control. When setting up a Backup and Compare schedule for the asset, you specify which version of the Backup Data to use as the backup compare partner to compare with the new file version.

Siemens S7 Controller (STEP7) password issue with backups

If the password in the Siemens S7 Controller (STEP7) is different than the password in the Configuration Data binder, the backup operation cannot complete. To avoid this, when you change the password in your S7 editor, be sure to download it to the controller and check the Configuration Data binder back in.