Shadow copy warnings

client
1

Hello,

My incremental file backups complete but I keep getting the list of warnings in the log below every time a backup is initiated. I would like to understand why this is happening and potentially get rid of them.

Client OS: Windows 2012
Urbackup client version: 2.2.5
Urbackup server OS: CentOS 7
Urbackup server version: 2.2.8

2018-04-15 04:24:14(info): Starting scheduled incremental file backup…
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server
2018-04-15 04:30:17(warning): Removing reference because shadowcopy could not be openend
2018-04-15 04:30:17(warning): Restarting shadow copy of c:\ because it was started by this server

Thanks.

2

Hi @milos

Did you ever get a solution to this? I’m seeing it as well and just curious if you ever made an progress on any solutions? I’ve already enabled debug logging and not seeing much in the logs than was already in them.

The only anomaly I noticed potentially was on the URBackup client (Windows 10 in this case) when I go to update the Configure components to backup, it appears to take the settings as none are checked, but then after checking all or even just some one by one and then applying , when I go back into that setting, there are none selected.

In my case for this particular PC client, I really only need the file level backups but just curious if you ever determined anything, etc.

Thanks~

3

@milos

I just wanted to give you an update on this for a fix that resolved this problem I just confirmed today. Use the latest URBackup client 2.2.6 and that should solve this problem. I looked over the change log and they did seem to patch a meta data issue so maybe that’s what was going on but in any case, I downloaded the executable file for the client 2.2.6 and ran that as administrator, and then kicked off the incremental file backup that has been failing on my and that resolved the problem.

4

Hi Team,
i am using UrBackup Client 2.4.11.exe version , still i am getting this alert
what should i do to resolve this , frequently i am getting this alert mail from client

WARNING: Restarting shadow copy of C:\ because it was started by this server
ERROR: Creating symlink at “/home/backup/urbackup/SEICHE-LAP-169/210102-1531/Users/Admin/Documents/My Music” to “” failed. Operation not supported (errorcode=95)
ERROR: Fatal error during backup. Backup not completed

THANKS
IQBAL.A