Sorry to be a bother but I have tried searching the forum and cannot find a similar post.
I have been successfully backing up all my clients and server with only a couple warnings/errors.
the main one I want to fix is the error on my Urbackup Server.
Environment: Windows Server 2019.
Client: Itself (extra redundant backups) - Change Block Tracking purchased, installed & running.
Other clients: Windows 10 (no issues or errors).
“Default Directories to Backup C:;D:”
"Excluded Files added to end D:\UrBackup*;D:\UrBackup;c:\Users*\OneDrive*; "
On the urbackup client application, In “add remove backup paths” I have the following.
I have only 2 Volumes on the server C: and D:
I use D: for mass storage and low speed files (such as backups and file sync’s)
My Urbackupserver is setup to store into D:\Urbackup\ and I have setup an exclude on that folder for file backups (Image backups are of C: only).
When doing incremental file backups If I include volume D: indexing takes upwards of an Hour (even with CBT) and I find it’s throwing error “code: 3” every time.
Cannot open file \?\GLOBALROOT\Device\HarddiskVolumeShadowCopy446\urbackup\ae-4\220117-0331\c to read the FRN. The system cannot find the path specified. (code: 3)
the amount of these Errors per run can be up to 3000 lines. All similar to the above.
I do not get this error on Full File Backups.
What I do notice is that it is looking for the other clients Volume Shadow Copies, which I wouldn’t think it would be trying to access (since it does not relate to the Server backup itself up).
Has anyone else had this issue with the UrbackupServer backing itself up?