Disk Enclosures
cancel
Showing results for 
Search instead for 
Did you mean: 

Mount issue with RSM / BC

SOLVED
Go to solution
Del_3
Trusted Contributor

Mount issue with RSM / BC

Can anyone provide help with the "MountVolume" command in BC? I have a script that works fine from the ValidateHostVolume through the PresentStorageVolume command, but I cannot get the MountVolume to mount the snap as a different drive letter in Windows.

I have tried all sorts of UNC paths in the command and also selected the path/letter from the "..." elipsis selection box, but the mount fails each time.

I am using RSM 1.2.

Thanks in advance.
3 REPLIES
Vic Pratt
Advisor
Solution

Re: Mount issue with RSM / BC

I've had a lot of problems with RSM mounts also. I have had the most success since uninstalling RSM Server and Host Agents, upgrading to RSM 2.0, and installing 2.0.2 patch for the host agent (the patch adds some additional hardware scan loops to give a better chance for success in finding the new volume before attempting to mount it). My hunch is this will fix the problem.

There used to be a restriction about mounting a snapshot to the same host the parent volume is attached to. I don't know if that restriction still exists, though.

I'm not sure if you use SecurePath, but it was causing problems until I installed SecurePathv40c_SP2.

It usually works ok now, but still fails about 10% of the time on "DeleteHostVolume". For some reason that seems more prone to failure than the commands to creat and mount the snapshot.

I've also had problems calling the RSM script to delete all the snapshots from a Data Protector post-exec command via the RSM CLUI command in a batch file. I use windows scheduler via similar batch file to create the snap and it works fine.
Del_3
Trusted Contributor

Re: Mount issue with RSM / BC

Thanks Vic. I did install RSM 2.0 but I havent had the chance to install the patch yet.

Thanks for the DP pre-exec info as well. That is how we were planning to execute the jobs.

Re: Mount issue with RSM / BC

Do install the 2.03 patch. It solves the unmount problem.