RSM Rant/Question

[Stevan Beara]

Hi Guys,
I am trying to write 2 RSM jobs which will:

1st job

1. snapshot the VDisks that belong to the VG
2. mount them to the server (create VGs, etc.)



2nd job

1. unmount the VG
2. delete the VG
3. delete the snaphots

The problem is the following:
1. RSM is incapable of passing variables from one job to another (as far as I know)
2. Although it's smart enough to see which LUNs comprise the VG (as shown by the capacity to snapshot those exact LUNs), I am unable to get the RSM to recognize the LUNs in the VG for the purpose of deleting them later on in the job
3. RSM does not allow me to DeleteStorageVolume(s) by passing the VG variable

Due to these 3 limitations (if I could do either one I would be fine), I cannot perform job 2, step 3 (the rest I've done), which means that I run my 2 scripts and have to manually delete the snapshots created.

I understand the following:
1. HP has a single script that does all this by pausing the job for backup to take place - can't do this because backups are spawned by a different tool - a customer requirement + how would I know exactly how long to wait before continuing the script

Please let me know if I am mistaking in any of RSM limitations.

Any help is greatly appreciated,

Stevan

[Stevan Beara]

After reading the CLUI reference again (this time paying more attention to the return codes), I found out that when script flow control "Pause ()" is issued, there is a return value to the system. Later a command "job - continue" from CLUI can be issued to continue the same job and pass another return value to the system, in fact treating the single script as two separate scripts.

That solved my problems,

Stevan

[Stevan Beara]

.