Job configuration

Based on the procedure for upload type SIMATIC S7, you will be shown an example of a job configuration. For other upload types, there are specific variations in the job configuration. These can be found in the device specific tutorials available: Device-specific tutorials.

Section: Job configuration

Example:

  1. Start the AdminClient and open the Jobs module.
  2. In the Project tree, select the component for which you want to create the job.
  3. In the menu tab, click on Create or drag & drop the components into the Jobs section.
  4. Check in the Job configuration (right side) if the preselected Upload type is the one that you want to use.
  5. When selecting Execute, you need to decide if the job is to be executed according to Scheduled, Not scheduled, Using versiondog BackupClient or Triggered by URL*.

* From versiondog version 8.0, you have the option to trigger a job using a OPC variable. This functionality is an add-on and therefore requires additional licensing. A more detailed description can be found in the tutorial Job trigger via OPC UA.

Section: General

  1. Job name: Give your job a descriptive name (limited to 64 characters).
  2. Components: Under Components, select the path to your component in the Project tree.
  3. Warning when the Backup is older than: Select an age for the backup from the dropdown if required. The default selection is Never warn.
    If a time period has been selected here, jobs, for which the backup is older than the selected time period, are marked with a warning icon. This is located in the column Timestamp backup.

  4. On error: Select from the dropdown list whether and when to retry the job if an error arises.
  5. Execution via: When using parallel servers, select the server on which the upload will be performed.

Section: Notification

The Notification section is displayed only if you have specified in the Upload Type-Specific Configuration window that job-specific or daily emails are to be sent for job execution. For more information, click here.

  1. When you click on the field Who to notify.
  2. The dialogue Who to notify will open.
  3. Select the users and user groups to be notified and click the appropriate checkboxes.
  4. E-mail recipients who are not versiondog users can be entered in the field Additional email addresses. Enter multiple users separately with commas.

Section: Upload and Compare

  1. Save policy: The following options are available to you:
  2. Number of remaining Backups (Rollover): Entered the desired value. After reaching this value, the new Backup will overwrite the oldest. The default is: 5
  3. Upload Agent: If you want to use an upload agent for this job, select it under Upload agent. Click on Check connection: To ensure that the computer on which the agent is installed can be accessed. If no success, the job will fail as well.
    Remember that when you use an agent, all user ID information and paths relate to the computer on which the agent is installed and the not the server. If you later specify a username or a network path, you need to make sure that this user exists on the computer on which the agent is installed or that the network path is accessible from the computer in question.
  4. Comparison strategy: Select a Compare policy from the drop-down list.
    This contains the following options:
    • Server version <-> Backup, Previous backup <-> backup
      The backup of the (online) version on the device is first compared with the last checked-in version of the project, this backup is then compared to the last backup.
      This option can give you more information than any other. It is however important to think carefully when interpreting the results.
      Examples:
      • If the backup is different from the previous backup, but the same as the last checked-in version of the project, this indicates that a version was developed in the project, checked-in then deployed to the device (This is the recommended workflow).
      • If the backup is different from the last checked-in version of the project, but the same as the previous backup, this indicates that a new version of the project has been created and checked-in, but not yet deployed to the device.
      • If the backup is different to both the last checked-in version of the project and the previous backup, this indicates that a new version of the project has been developed and deployed to the device, but not yet versioned and checked-in.
    • Server version <-> Backup
      The program running on the device is compared with the latest checked in version of the project. Job results are not be compared. We recommend using this option if the versiondog system Always detects differences between backup and previous backup (regardless of the compare configuration). In this case, there is no point running the comparison.
    • Previous backup <-> backup
      The program running on the device is compared with the previous backup. It is not compared with the newest version.
      Detecting a difference here could mean one of the following things:
      • A new version of the project has been developed and deployed to the device.
      • Actual or forced values were not ignored during the comparison (through which the backup always differs from the previous backup).
      • The program on the device was changed. You can find out what was changed by using versiondog's compare functionality.
  5. Compare Agent: If you want to use an upload Compare agent for this job, select it under Compare agent. Click on Check connection to ascertain whether it is possible to access the computer on which the agent has been installed. If no success, the job will fail as well.
  6. If you activate the controlbox Enable configuration of job-specific compare, you can adjust the comparison settings for this job by pressing Configure comparison:

Section: Section automatically creating versions after job excution

This section is only displayed if in the window Upload specific configuration

For more information on upload specific configuration, please refer to the section Adding additional job settings.

Create version when: In the drop-down list, you can specify when a new version of the component should be created automatically:

Section: Job information

In this section, you will be find the Job ID and the component ID. These are for example relevant for Scripting.

Section: SIMATIC S7 Settings

Configure the settings for your chosen upload type.

For further information regarding job configuration for individual jobs, please refer to Device specific tutorials in versiondog INFO.

Section: Configure the section Access path details

Select the Access path you want to use for communication with the controller. For more information, see Tutorial SIMATIC S7 > section: Configure access path.

Section: Backup

Reduce network load and exclude defined blocks from comparison. For more information, see Tutorial SIMATIC S7 under 7. Configure the section Backup.

Section: Advanced

Change the TCP/IP port, specify a CPU password, configure retries on failed uploads, and specify waiting times between data packets. For more information, see Tutorial SIMATIC S7 under 8. Configure the section Advanced.

FAQ:: Can I set up the versiondog server to backup one device after the other (never multiple devices at once)?

You can set the backup time so that your devices are backed up with a time delay (to do so, go to AdminClient > Jobs > Job configuration > General > Schedule).

Alternatively, you can set the number of uploads that can be performed simultaneously. Proceed as follows:

  1. Open the AdminClient > INI files.
  2. Open the file AgentStation.ini (Path to the file: <drive>:\vdServerArchive\VD$A\Configuration\Upload)
  3. Search the section [Common] and add it. Enter the key 4900 with the value 1 (only 1 comparison may be carried out simultaneously).
  4. Under [Common], enter the upload class and enter the key 4900 with the value 1
    Example:
  	[Common]
        4900=1
	[FTP]
        4900=1

The values in the example mean that never more than one backup is created at a time.

The number of comparisons that may be executed in parallel can be configured as follows:

  1. Open the AdminClient and then go to INI files.
  2. Open the file AgentStation.ini (Path to the file: <drive>:\vdServerArchive\VD$A\Configuration\Compare).
  3. Search for the section [Common]. If this section is not present, insert it. Write the key 4930 and the value 2.
  4. In this section, add the upload class together with the key 4930 with the corresponding value for the parallel comparison, for example:
	[Common]
	4930=2
	[FTP]
	4930=2

The values in the example mean that never more than two comparisons are carried out simultaneously.

Important Information

  • The [Common] section can be followed by several sections of the type upload class. Possible upload classes are for example UNC, FTP and SimaticS7.
  • The value set in the [Common] section is the maximum value. If a higher value for 4900 is assigned in one of the following sections, the maximum value defined in [Common] applies.
  • Possible values: Minimum value = 1, maimum value = 1024; default value = 5

To FAQ list

FAQ: Why does a job fail to run successfully and end in an error even though an agent is installed and an upload job is properly configured?

Possible cause

This problem could be occurring because the agent do not have the administrative rights required for an application that needs to be opened for the job to run.

Solution

To ensure that the log-on account for the agent is correctly set, proceed as follows:

  1. Open the Windows Services console (Windows > Start > services.msc).
  2. Double-click on the agent service (VDog UploadAgent or VDog CompareAgent).
  3. Go to the tab Log on.
  4. The option This account should be selected. If not, select it and enter the username and password of an account which has the appropriate administrative rights.

To FAQ list

FAQ: Where do I find a 32 character job ID (and how can I copy it into a clipboard)?

To find the Job ID, proceed as follows:

  1. Then go to the Jobs section.
  2. Activate the column Job ID.
  3. The job ID will be visible if the job has been run at least once.

Proceed as follows to copy the job ID to the clipboard:

  1. Click anywhere on the Job ID number and copy with CTRL + C.
  2. Paste into a text editor such as Notepad. The Job ID will be included among all the other information.
  3. You need the 32-digit job ID. For all application possibilities of the job ID it is necessary that it is complete and correct.

To FAQ list

For more information on Job configuration for the General upload types, see the following sections.