Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsTroubleshooting - Enterprise Workloads
Backup fails with Phoenix encountered incorrect folder path error
Backup fails with Phoenix encountered incorrect folder path error
Updated over 3 months ago

This article applies to:

  • Product edition: On-Premise

Problem description

Backup fails with "Phoenix encountered incorrect folder path" error message.

Cause

The backup job fails with the above error when the drive or drives mentioned in the policy for the File Server is not present on the Server and cannot be backed up.


πŸ’‘ Tip

This issue also occurs when incorrect Drive or a Drive letter which once existed but is no longer present on the Server and the error is thrown even if one drive is missing.


Traceback

level=info ts=2024-09-13T00:01:07.3209705+05:30 filename=backup_agent.go:866 message="Misconfigured folder found" folder=E:level=info ts=2024-09-13T00:01:07.3209705+05:30 filename=backup_agent.go:957 message="Sending log to Phoenix server with message: Misconfigured folder found: 'E:'."level=info ts=2024-09-13T00:01:07.8037934+05:30 filename=backup_agent.go:882 message="Some folders configured for backup are not found on the share"level=info ts=2024-09-13T00:01:07.8037934+05:30 filename=backup_agent.go:957 message="Sending log to Phoenix server with message: Some folders configured for backup are not found on the share"

Resolution

Verify whether all the drives configured for backup are present on the server. If a drive is not present on the server, remove the drive from backup using one of the following options:

  • If the server is assigned a custom content rule, you can directly exclude the drive from the content rule to resolve the issue.​
    ​

  • If the content rule assigned to the File Server is also mapped to multiple servers, excluding the drive from the rule will impact all the servers mapped to the content rule. Hence, create a custom content rule and assign it to the File Server and ensure all the drives configured in the custom content rule are present on the server.

See also

Did this answer your question?