10-29-2013 12:39 PM
Any ideas what the following is complaining about? This is an EV 10.0.4 FSA targetting EMC Celera filer. All the pre-reqs were done successfully, server added. I am able to archive (can see the items when I search the archive) but it is failing to create the shortcuts. It is complaining about:
*** Error *** - Error making file NO_MATCHING_CONNECTION
------------------------------------------------------------------------------------
Archive mode run started at 10/24/2013 9:09:46 AM for task File System Archiving Task for NASPFS01
Task run: 3
Time File Size (bytes) Policy name Rule name Rule type Archive status Shortcut type Shortcut status Filter Modifications
--------------------------------------------------------------------------------------------------------------------------------------------------
10/24/2013 9:09:52 AM \\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\Copy of VM Guesst Capacity list 4 29 2011 (4).xls 116224 Bond Compliance Folder Policy Archive All Files ARCHIVE *** Error *** - Error making file: \\?\UNC\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\Copy of VM Guesst Capacity list 4 29 2011 (4).xls a placeholder file. NO_MATCHING_CONNECTION
10/24/2013 9:09:53 AM \\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\Copy of VM Guesst Capacity list 4 29 2011 (5).xls 116224 Bond Compliance Folder Policy Archive All Files ARCHIVE *** Error *** - Error making file: \\?\UNC\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\Copy of VM Guesst Capacity list 4 29 2011 (5).xls a placeholder file. NO_MATCHING_CONNECTION
10/24/2013 9:09:54 AM \\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\testarchive.txt 15 Bond Compliance Folder Policy Archive All Files ARCHIVE *** Error *** - Error making file: \\?\UNC\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\testarchive.txt a placeholder file. NO_MATCHING_CONNECTION
10/24/2013 9:09:54 AM \\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\Expense_Report01.xls 40448 Bond Compliance Folder Policy Archive All Files ARCHIVE *** Error *** - Error making file: \\?\UNC\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\Expense_Report01.xls a placeholder file. NO_MATCHING_CONNECTION
10/24/2013 9:09:56 AM \\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\Copy of servers tiers.xls 171520 Bond Compliance Folder Policy Archive All Files ARCHIVE *** Error *** - Error making file: \\?\UNC\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test\Copy of servers tiers.xls a placeholder file. NO_MATCHING_CONNECTION
Summary by volume
\\naspfs01.abc.org\Accounting_FSA
Estimated space saved after shortcut creation and file deletion (MB): 0.00
No items were matched by any rule. Some files may have been ignored because of policy permission settings.
Archive Point Summary
---------------------
ArchivePointPath VaultStoreName RemoveSafetyCopies
-----------------------------------------------------------------------------------------
\\naspfs01.abc.org\Accounting_FSA\Finance Administration\Finance\test FSAVaultStore Immediately
Retention Folders Summary
--------------------------
No folders created.
Total volumes processed: 1
Total folders processed: 1
Total number of files matching an archive rule: 5
Total number of files matching an archive and copy rule: 0
Total number of files matching a do not archive rule: 0
Total number of files matching a delete rule: 0
Total files that matched a rule and were processed successfully: 0 (0.00 MB)
Total files archived by File System Archiving TASK : 0 (0.00 MB)
Total files excluded by a do not archive rule: 0 (0.00 MB)
Total files successfully archived by File System Archiving API: 0 (0.00 MB)
Shortcut Creation
Total number of files matching a 'Create Shortcuts Immediately' rule: 5
Total number of files matching a 'Create Shortcuts Later' rule: 0
Total number of files matching a 'None. Archive and Delete File' rule: 0
******** Total errors reported: 5
Processing of all volumes is complete.
Start time: 10/24/2013 9:09:46 AM
End time: 10/24/2013 9:09:56 AM
Elapsed Time: 00:00:10
Solved! Go to Solution.
10-29-2013 01:35 PM
http://www.symantec.com/business/support/index?page=content&id=TECH52430
According to that, it states
fs_dhsm -connection <fs_name> -create -type http -secondary <ev_url> -user <user> -password <user_password> -cgi n
<ev_url> is the URL of the Web Access application. The Celerra is case-sensitive, so this URL must use the correct case. If this is incorrect, data will not be reverted to placeholders and the error "NO_MATCHING_CONNECTION" will appear in the FSA Reports. To ensure this is correct open the EV Directory database in SQL and the SiteEntry table. This will contain the correct URL (only if single Enterprise Vault Server is in use) in the correct case that is required for the EV_URL. In the ComputerEntry table you will find the ComputerName that forms the first (hostname) portion of the URL. If you use any other name for this server, you'll get the same NO_MATCHING_CONNECTION error. For example, if the ComputerName field reads "EVFSAServer" (the DNS alias (CNAME Record) for the EV server in question), then the proper URL will be http://EVFSAServer/EnterpriseVault.
10-29-2013 01:35 PM
http://www.symantec.com/business/support/index?page=content&id=TECH52430
According to that, it states
fs_dhsm -connection <fs_name> -create -type http -secondary <ev_url> -user <user> -password <user_password> -cgi n
<ev_url> is the URL of the Web Access application. The Celerra is case-sensitive, so this URL must use the correct case. If this is incorrect, data will not be reverted to placeholders and the error "NO_MATCHING_CONNECTION" will appear in the FSA Reports. To ensure this is correct open the EV Directory database in SQL and the SiteEntry table. This will contain the correct URL (only if single Enterprise Vault Server is in use) in the correct case that is required for the EV_URL. In the ComputerEntry table you will find the ComputerName that forms the first (hostname) portion of the URL. If you use any other name for this server, you'll get the same NO_MATCHING_CONNECTION error. For example, if the ComputerName field reads "EVFSAServer" (the DNS alias (CNAME Record) for the EV server in question), then the proper URL will be http://EVFSAServer/EnterpriseVault.
10-29-2013 02:25 PM
Thanks JW3 for the quick answer. Good catch. I will try this with the client next week and will update your post as solution then.
11-05-2013 06:21 AM
Thanks again JW3. It did the trick.