HPE EVA Storage
1849970 Members
2314 Online
104049 Solutions
New Discussion

Problem with RSM Script

 
Paul Hall_1
Occasional Contributor

Problem with RSM Script

I'm trying to use one of the provided RSM templates to freeze an app, snap the lun, mount it to a host, start legato then after legato finishes tear it all down. Everything works up until it hands off it to legato, its saying the command to launch legato fails (even though it doesn't it does launch it) and then its not waiting until legato returns a completion time line which is what I put as the success value, in the line that does this I told it to wait. and it starts tearing it down before legato finishes. Anyone have any ideas as to what I'm missing? I took screenshots of the script they're viewable at: http://chia.csumb.edu/rsm.

Thanks in advance for any help,

-paul
IT@CSUMB
4 REPLIES 4
Ken Grabowski
Respected Contributor

Re: Problem with RSM Script

Hi Paul,

This may be an obvious question but; if you run the legato command at the dos prompt does it wait until it is done, or does it run in the background?
CSUMB Network Operation
Occasional Advisor

Re: Problem with RSM Script

it runs in the dos window in the foreground until its done. I came up with a somewhat hackish fix to my problem basically just inserted a "wait 4 hours" line into the rsm script which should fix legato plenty of time to finish before the cleanup parts start.
chris barnett_2
Frequent Advisor

Re: Problem with RSM Script

It's a "feature" introduced in RSM 2.0, when HP removed the host agent dependancy on SAM agents. The problem is present when trying to launch any program external to RSM. The workaround is to configure the wait for activity to complete field to "NOWAIT" and the success value to empty. then add a script flow control statement WAIT ("x:x:x") to allow sufficient time for the backup to complete. Alternativly you could try scripting using the RSM clui using perl or back to good old SSSU
LSt_1
Occasional Advisor

Re: Problem with RSM Script

Hi,

I have the same problem, but on the HP web-site is a new fix for the windows HA. The new timeout is now 6h.
I try this in production on W2K3, this will fix the problem

Please have a look at
"
VERSION: HP Replication Solutions Manager host agent software 2.0.2 for Windows"

DESCRIPTION:
You should install the 2.0.2 patch if you are currently running HP Replication Solutions Manager host agent software for Windows version 2.0.


UPDATE RECOMMENDATION: Recommended


FIXES:

-Jobs including the DeleteHostVolume command were intermittently reporting failures because the server software was still detecting the volume. The software has been updated to allow a number of rescans to ensure the device has been removed and eliminate failures.

-If the time it takes to execute a command exceeds the default time out, the command would fail. The default time out has been increased to six hours to avoid command failures.

-After a device presentation, the host agent software performs a scan to detect the device. Even with multiple scans being performed until the device is detected, the device detection fails intermittently. The software code has been updated with an additional file to ensure device detection is successful.

-The host agent logging functionality now works correctly on Japanese versions of the Windows operating system.

Regards Lutz