Using Wildcards or Environment Variables for Policy includes
Description
Backup are not completing successfully. The policy had Locations added using Wildcards or Environment Variables.
How to identify the problem
Wildcards are special characters used to indicate one or more characters in a folder name. As example, an asterisk (*) indicate any number of characters, while a question mark (?) indicate a single character in a folder name.
Envionmental Variables are system wide references to specific folders. As example %windir% will take your to C:\Windows and %programdata% to the hidden c:\programdata folder.
Policies may not include Wildcards or Environment Variables under Locations, and requires a full path and name of the folder, as example: c:\BusinessDocs
Wildcards and Environmental Variables may only be used in the Global Excludes section of the policy. but requires specific folder names and paths for includes under Locations.
As a test scenario, we have created the following include:
If you have a look through the Agent log, you will find the following entries:
Unhandled exception in identifiableRunnable
java.nio.file.InvalidPathException: Illegal char <*> at index 0:*\businessdocs
How do I resolve this problem?
Remove any custom Locations that are using wildcards and add full path names to the folder that needs to be backed up, as example c:\BusinessDocs
If needed, use the well known folders Instead of wildcards, to add as a Location.
Note: Make sure to remove those well known folder from the Global Excludes.
Check if the problem has been fixed
After updating the Policy, a backup is automatically performed by the Agent at the scheduled time, or can be manually started from the Cloud Portal. Make sure that the backup now completes successfully and that a Restore reference the newly added location.