Common Issues
This article describes the common issues due to Workstations and Servers
Last updated
This article describes the common issues due to Workstations and Servers
Last updated
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:
3. 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).
4. 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:
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.
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
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.
This issue is usually caused when the shadowstorage size is too small.
Make 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.
Open the services.msc and make sure, that the VSS service is enabled.
