Job configuration for upload type UNC (UNC jobs)

Jobs with the upload type Network (UNC) perform data uploads from shared network resources using the UNC (Uniform Naming Convention) protocol.

In the Project tree, select the component.
In the menu tab, click on Create or drag & drop the components into the Jobs section.
Check in the section Job configuration, if the upload type Network (UNC) is being displayed.
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.

Image: Job configuration, sections Network (UNC) Settings and Advanced

Section Network (UNC) settings

In the Username and Password fields, enter the user credentials for the person that will be used to access the network resources. The user will need to have the necessary access rights.
Under Resources, enter the computer name or IP address of the computer you want to access over the network. You can check if the user can access the computer or the entered combination of computer and subfolder by clicking the Check button. If the check is not successful, the job will also fail.
If these details are already saved in the FTP server's subdirectory, enter the subdirectory's path in the field Subdirectory.

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 server: /folder1/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 server: /Directory1/subdirectory1/subdirectory2 and /directory1/subdirectory1/1234

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

Section Additional

You can reduce the network traffic, that caused by the job, by increasing the sleep between packets and reducing the maximum size of data packets.
Higher values for the sleep and lower values for the maximum packet size will result in longer times for job execution.
Activate the Use timestamp check to reduce network traffic 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.
The checkbox Make offline project available to scripting interface enables upload scripts, that were started by the job, to access the latest checked in version.

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 set compare and save behavior.

Activate the Enable custom configuration for this job checkbox and click on Edit. 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 for each upload type separately. To adjust the maximum time for job execution according to the upload type, proceed as follows:

Start the AdminClient and open the Jobs module.
In the menu, click on Global job settings.
The Upload specific configuration window will then open.
Select the upload type in the navigation bar on the left.
Select the Use specific timeout for this upload type checkbox.
In the Maximum time for job execution field, enter the time period in minutes. The maximum possible value is 540 minutes.

If you do not select the Use specific timeout for this upload type checkbox, 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 . (Go to the path in the server or agent archive:..\VD$A\Configuration\Upload\Classes.ini).

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

FAQ: UNC Job: how can I correct the error message: “Error connecting to target system” [ID384]"?

When setting up a UNC job, errors can arise under the following circumstances:

Upload source: PC with operating system WinXP SP3 or older
Resource:..\\OlderXP-PC\Docfile
Upload target: Agent/Server with Windows 10 Version 1709 or Windows Server 2016 and newer

The cause for this is that the operating system WINXP SP3 uses the SMBv1 protocol. The SMBv2 protocol was introduced in Windows Vista and Windows Server 2008. The SMBv3 protocol was introduced in Windows 8 and Windows Server 2012. When you reinstall windows, the SMBv1 protocol will be deactivated as standard for security reasons. Vulnerabilities in SMBv1 allow attacks via the network and the execution of malicious code on machines that can be reached via the network.

Microsoft has discontinued support for SMBv1. For more information, please refer to the microsoft website.

Potential solutions:

Updating the source computers operating system to Windows 7 or newer.
If this should not be doable for technical reason, you have the option to activate the SMBv1 Protocol on the server / agent. This will ensure that the old and insecure SMBv1 protocol will once again be supported and will be able to carry an upload.

Proceed as follows:

1. Open Windows features and functions:

2. Activate SMB1 protocol:

3. Download the necessary files from the internet:

4. Restart is required.

For the UNC Upload, it is recommended that you create a user on the source PC that is the only one who has reader rights to the source folder. This user should not have any further rights on this computer and certainly no administrative rights under any circumstances.

To FAQ list