Job configuration upload type FTP (FTP jobs)

Jobs with the FTP upload type provide access to an FTP server.

  1. In the Project tree, select the component.

  2. In the menu tab, click on Create or drag & drop the components into the Jobs section.
  3. Check in the section Job configuration, if the upload type FTP is being displayed.

  4. Make sure the desired settings are in place for the following sections: General, Notification, Upload and compare, Create a version automatically after job run. The Notification and Create a version automatically after job run sections are only displayed if the necessary settings have been implemented. For more information on configuring the general sections, please refer to Configuring general job settings.

Section FTP Settings

  1. Behind the FTP server, enter the IP address of the server that you want to use to create a connection.
  2. Go to Connection type and select from the drop down list.
  3. Select the port that you want to use for the communication. Port 21 is automatically preselected.
  4. Activate the checkbox Use FTP passive mode when needed.
  5. If required, enter the log-in details (username and/or password) of the user. Depending on the configuration of your FTP server, this step is optional. An upload can also be performed without a username or password.
  1. If these details are already saved in the FTP server's subdirectory, enter the subdirectory's path.
  2. With these login details, you should be able to access the subdirectory. versiondog supports up to 10 sub-directories per job.

    Only when you enter the subdirectory, not only will the entire path on the FTP server in the backup be displayed, but also the most recent directory in the path:

    Example:

    Path on the FTP server: /file1/subdirectory1/*

    Composition of backup: Archive.zip/*

    If you enter multiple subdirectories, the entire directory structure will be included in the backup.

    Example:

    Path on the FTP server: /file1/subdirectory1/subdirectory2 and /file1/subdirectory1/1234

    Composition of backup: Archive.zip/directory1/subdirectory1/subdirectory2 and archive.zip/directory1/subdirectory1/1234

  3. You can check if the login details work by clicking on Check. If no success, the job will fail as well.
    If necessary, you may have to enable the port set in step 3 in your firewall.

Section Additional

Activate the Upload only when timestamp is different (reduces network load) checkbox. The time stamp instead of the content of the files will be checked. This will ensure that only new and edited files are uploaded for the backup; files without changes will be taken over from the previous backup. This will further limit network traffic.

Section file specifications and compare settings

Normally, comparisons are executed using compare settings of the component. Job specific modifications can be made in this section.

The table shows the set compare and save behavior.

  1. Activate the Enable custom configuration for this job checkbox.
  2. Click on Edit.
  3. Set new parameters for the comparison and save process in the new open window.

Configuring a timeout

When uploading large amounts of data, a timeout may occur despite the default time being preset at 30 minutes. This timeout can be adjusted globally for all upload types or each upload type separately. To adjust the maximum time for job execution according to the upload type, proceed as follows:

  1. Start the AdminClient and open the Jobs module.
  2. In the menu, click on Job settings.
  3. The window Upload specific configuration will then open.
  4. Select the upload type in the navigation bar on the left.
  5. Select the checkbox Use specific timeout for this upload type.
  6. In the Maximum time for job execution field, enter the time period in minutes. The maximum possible value is 540 minutes.
  7. If you do not select the checkbox Use specific timeout for this upload type, the next time you change the global timeout, the value set here will be overwritten by the global one.

Alternatively you can adjust the timeout via the INI file Classes.ini (..\<vdArchive>\VD$A\Configuration\Upload\Classes.ini). For more information, see the INI files section, located in the AdminClient tutorial.

The value entered in the Upload type specific configuration window will then be copied into the INI file.

FAQ: When I created a backup using a backup job via the upload class FTP, an error arises. What do I need to change to fix this error?

There are two solutions to solve the problem mentioned above:

  1. Activate passive mode

    Start AdminClient

    1. Start the AdminClient.
    2. Enter your username and password.
    3. Go to the Jobs module.

    Job configuration

    1. Open the Start tab.
    2. In the Project tree, select the component, whose FTP jobs ended in errors.
    3. Select the upload type FTP.
    4. In the Jobs table, select the job in which errors occurred on execution.
    5. Under FTP settings, enable the option Use FTP passive mode.
    6. Save the changes.

    Execute job (for testing purposes) manually

    1. Click on the button Execute selected jobs once in the group Execute.
    2. Wait until the job has been executed.
    3. Not scheduled or Not activated depending on type of job execution.

    If errors continue to reappear when you activate the passive mode, we request that you deactivate this and continue with section b).

  2. Include VDogUpload.exe in firewall exemptions

    The file VDogUpload.exe is (also) executed using FTP during the upload. Timeout errors will occur if the database linked to said file is blocked by the firewall.

    The VDogUpload.exe file needs to be added to the firewall's exemption list to prevent this error from reoccurring.

    Not all customers employ the same firewall. It is therefore not possible for us to provide any information on this topic.

    Please refer to your own product's documentation for more information. The internet is another source of information. Enter of the following searches in your search engine:

    • <product name/name of fire wall> exception
    • <product name/name of fire wall> configure exception
    • <product name/name of fire wall> allow exception
    • <product name/ name of fire wall> insert exception

To FAQ list