"Invalid Usage" error causing backups to fail
I have a few backups that suddenly started failing with an error saying "invalid usage" and "the specified file does not exist". This happens on both GFS scheme and Simple backup plans that have been running a month or so without problems. I have tried to reinstall the agents on the target machines, but they still failed after that. One of the machines will succeed in one backup plan it is scheduled to run and fail another, same result every time.
Anybody else running into this issue?
Here is an excerpt from the log.
--------------------
Error code: 11
Module: 23
LineInfo: 639cc48216fa4c1f
Fields: IsReturnCode : 1, $module : disk_bundle_vs
Message:
--------------------
Error code: 11
Module: 23
LineInfo: 639cc48216fa4c1f
Fields: $module : disk_bundle_vs
Message:
--------------------
Error code: 12
Module: 23
LineInfo: 639cc48216fa4d2d
Fields: Path : C:/.rnd, $module : disk_bundle_vs
Message:
--------------------
Error code: 31
Module: 4
LineInfo: 35f34aff8801b59c
Fields: $module : disk_bundle_vs
Message: Invalid usage.
--------------------
Error code: 1
Module: 4
LineInfo: c847b314771c6034
Fields: $module : disk_bundle_vs
Message: Error occurred while reading the file.
--------------------
Error code: 17
Module: 4
LineInfo: 6517e0ecf4e10261
Fields: $module : disk_bundle_vs
Message: The specified file does not exist.
--------------------

- Log in to post comments

Agata,
1. Backing up to a NAS as an unmanaged vault, other machines (on the same backup plan) are able to successfully back up to it.
2. Yes, edited task and saved, no luck.
Any other suggestions are welcome.
Thanks
- Log in to post comments

The error (The specified file does not exist.) occurs when backup engine reads information from existing archive (set of .tib files) and fails to recognize them as a valid backups set.
In case of 'GFS' scheme, if you run a full backup manually, does it fix the situation?
- Log in to post comments

I will try to run a full backup on the GFS scheme that is failing to find out, but the error occurs also on a simple backup that is taking full backups daily.
- Log in to post comments