V-79–57344-33932 — Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again. If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.
Agent for Enterprise Vault backup job fails during the ‘index locations’ backup with: 0xe000848c — Unable to attach to a resource.
Cause: When I move indexes from one physical disk to Bigger size SAN LUN (I:\). That drive is not picking default share (I$- system default share). And backup get failed with above error.
Click Start, click Run, type net share
Notice ADMIN$ and C$ shares don’t exists.
Examine the AutoShareServer and AutoShareWks registry values to make sure that they are not set to 0:
Click Start, click Run, type regedit, and then press ENTER.
Locate and then click the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
If the AutoShareServer and AutoShareWks DWORD values in the LanmanServer\Parameters sub-key are configured with a value data of 0, change that value to 1.
Note that, If these values do not exist, you do not have to create them because the default behavior is to automatically create the administrative shares.
Quit Registry Editor and restart the server.
Verify that the administrative shares are by running the net share command from a command prompt.
Notice ADMIN$ and C$ shares are listed. Rerun the backup job.
My Backup job get successfully completed.