Common issues

This article describes the common issues due to Workstations and Servers

PreviousDevice removal NextUse cases

Last updated 8 months ago

The device did not connect to the Management Service

If, after the installation, the device is not connected to the Management Service:

Make sure, that you used the proper Xopero ONE Agent Installer - keep in mind, that the installers for Windows Server 2008R2, 2012 and 2012+ are different!
Make sure, that the Management Service address is configured properly. You can reinstall the Xopero ONE Agent or use the following article to get the information about Agent's configuration:

Make sure, that the communication between the Agent and Management Service is not blocked on the previously configured port (in case of on-premise installation) or between the agent and cloud-based Management Service (in case of SaaS deployment model).

Check the local firewall settings as well.

Make sure, that the device is not connected to the Management Service as a worker - check the Workers tab in Settings:

The file-level backup did not protect all the selected files

If all the selected files are not backed up using the File-level backup, make sure, that the files are able to copy by the Xopero ONE Agent service.

The Storage Initialization failed issue occurred

Make sure, that the storage configuration is correct (e.g. storage access data, the path to the share)
Make sure, that your device has connectivity with the specified storage

The image level-backup of the device with the Linux operating system doesn't work

Xopero ONE allows performing the image-level backup only from the Windows OS. The Linux operating systems are not supported with this kind of copy.

The VSS Diff failed(An error occurred during fast difference check. Slower method will be used instead) issue occurred

This issue is usually caused when the shadow storage size is too small.

Use commandline and perform the following command to resize the shadowstorage:

vssadmin resize shadowstorage /for=X: /on=X: /maxsize=320MB

X -the disk letter (best practice is to perform the operation for all the accessible disks).

vssadmin resize shadowstorage /for=X: /on=X: /maxsize=30%

After the changes, perform the backup task again. If that won't help, then try to delete all the shadow copies using two additional commands in the commandline:

diskshadow

And after that:

delete shadows all

Perform the backup once again, if it still fails, then contact our technical support by submitting a request: HERE

The backup ends with a warning "DW1010"

This warning means that not all query items found (Not all items defined in the query found). In other words, a folder was specified that doesn't exist on the device.

For example, the Export folder on the D: drive was indicated for backup.

But for some reason the folder was deleted (or moved to another location). However, the backup task remembers the indicated location. You can switch from "Select from device" to "Select path or variable".

Because it is not enough now to indicate its new location. You have to:

Edit the old path,
Or delete the old one and add a new one,

The backup of databases ends with a warning DV0249 - Unable to read backup data

If your database backup ends with such an error, it may indicate problems with the stability of your Internet connection. Try to locate and eliminate all possible problems on the local network side. If this is not possible, you can try to eliminate the problem by increasing the number of retry attempts through the agent configuration. Detailed information on how to do this can be found in the article on agent configuration.

VSS service is unavailable

Open the services.msc and make sure, that the VSS service is enabled.