Restoring a shared directory to an alternate path changes the share pointer to the new path after a reboot of the client system.

Article:TECH21801  |  Created: 2002-01-22  |  Updated: 2014-03-05  |  Article URL http://www.symantec.com/docs/TECH21801
Article Type
Technical Solution


Issue



Restoring a shared directory to an alternate path changes the share pointer to the new path after a reboot of the client system.


Solution



This behavior is normal VERITAS NetBackup (tm) functionality.

NetBackup backs up the data and the Access Control Lists (ACLs) of a file or directory of a single glob. Backing up the ACLs allows one to easily do disaster recovery. (Consider the pain involved in having to recreate all the shares found in a company's UserData directory if the restore did not put them back.)  This functionality was added to NetBackup several versions ago.

Note:
All Local system shares are listed in the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\lanmanserver\Shares

The following things contribute to the share pointer moving:
1. Only one share of a particular name can exist on a Windows server.
2. NetBackup backs up files as a single glob which includes ACLs and data. The two cannot be separated.
3. The alternate path restore alters the path to the share in the registry key noted above (because the share name can only exist once on the server).
4. A reboot refreshes this share information.

Thus the share pointer moves.

Note:  A stop/start of the server service on the affected server will refresh new shares, but a reboot is required for the share pointer movement behavior to be observed.

 


Legacy ID



250043


Article URL http://www.symantec.com/docs/TECH21801


Terms of use for this information are found in Legal Notices