Active IQ Unified Manager Discussions

WFA - Command updating reservation works but not in workflow

LFueyo
5,007 Views

Hello, 

 

I've been working on a workflow used for Disaster Recovery Plans since a few days ago, and I must say that I'm stuck on something that I just can't understand. 

 

In this workflow, I'm using the "Reverse Resync SnapMirror" two times. Unfortunately this puts two rows of reservation entries and the first one is never cleared even on cache acquisition, which is a little bit problematic if the workflow has to run again before the reservation expires. (and I wouldn't want a customer to have to clean specific reservations, let's keep it simple).

 

The solution I thought about was to force an acquisition on OCUM, right after the first "Reverse Resync" workflow, using the great commands from sinhaa . They work just fine if I execute them alone, or from a CLI, and they return no error in a workflow (in fact, I can even see that the data acquisition occurred in the data sources tab and on OCUM). 

 

The thing is : the reservation tab is updated when I use them from a CLI or "test" them, but it's not if I used the commands from a workflow.

 

 I checked that the inputs were the same, tried after clearing the Reservations and I always get the same result : the acquisition on OCUM and WFA happened (they are listed in the GUI and the rows from the cache database are updated) but didn't update the reservations.

 

(If it's a known problem for a few versions, I'm using WFA 3.0 with OCUM 6.2 and a CDOT 8.3)

 

Regards, 

Lucas Fueyo.

1 ACCEPTED SOLUTION

LFueyo
3,824 Views

Here is an update for all of those that are in the same kind of situation.

 

We solved the problem a few weeks ago (well, the problem being in WFA's core we couldn't solve it but at least we bypassed it). 

Our solution being a little bit heavy as it requires an acquisition with OnCommand Unified Manager as well as the data sources, it isn't really suited for short / small workflows that need to go fast and are often executed. 

 

Here is what we did : 

- Invoke a rediscover on the concerned clusters via REST from the main workflow

- Schedule another workflow from the main worflow and wait for approval

 

This other workflow will force the data acquisition, and as it is scheduled and then executed in another workflow, the main workflow's reservation will be updated (the main workflow will be waiting for approval). Then, we just continue the execution of the main workflow.

 

I hope it'll help some of you, we unfortunately couldn't find any simpler way that was imperceptible to the end users.

View solution in original post

10 REPLIES 10
Public