ProblemPureDisk Export to NetBackup and Restore workflows do not work if the directory or filename contains an apostrophe
Error MessageThe fetched PO-list /Storage/tmp/wf_polist_XxXxX did not contain a valid end-marker. It is probably incomplete
SolutionWhen exporting data from PureDisk to NetBackup, the export job errors out when it encounters a file that contains an apostrophe in the filename or in the foldername. An error is also encountered when trying to download a file that contains an apostrophe using the Find Files action in the PureDisk web GUI.
Review the job details using the PureDisk web GUI - Sample for an export job below.
[2008-Sep-11 13:45:27 UTC] Using MBFind --dirname='*' --basename='*' --completedirstructure --toErrorCode=0
*** Error Message ***
The fetched PO-list /Storage/tmp/wf_polist_ELQ9jI did not contain a valid end-marker. It is probably incomplete.
*** End ***
Reviewing the contents of the file - /Storage/tmp/wf_polist_ELQ9jI shows the following error message
pg_query(): Query failed: ERROR: syntax error at or near "T"
LINE 1: ...stFolderName' AND basename LIKE 'Apos'Trophe' AND ty...
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently being considered by Symantec Corporation to be addressed in a forthcoming Patch or version of the product. The fix for this issue is expected to be released in a future release update for PureDisk. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk. Please refer to the Release Update Readme notes or contact NetBackup Enterprise Support to confirm this issue was included in the maintenance pack.
As future maintenance packs are released, please visit the following link for download and readme information: