I am trying to build an ndmpcopy based restore job in WFA due to functionality issues within OCUM. The job works without issue, however as I have to call Invoke-NcSSH the command waits for the restore to finish. Without the command going into a success status and moving on, the monitoring command I have put together is not called until after the restore command completes.
Does anyone know of a way to have WFA accept that a command has been run, ignore output and drop out to move to the next command?
Thank you for the reply, but that isn't the issue. An ndmpcpoy invoke by nature of the command is a verbose out, there is no background or quiet option available.
This means when I use "Invoke-NcSSH ndmpcopy -sa -da path path", the command doesn't show completion until the entire restore completes or fails. This would be the same if it were run on the CLI, what I need is a way to Invoke-NcSSH in non-interactive mode so that I can allow the command to timeout but continue running. I actually somehow had this work one time and then after a log out and back in the job didn't work the same way...I cannot figure out how to replicate what happened in that single run.
I think this is likely an issue with the ndmp command and Invoke-NcSSH cmdlet as in 7mode we had start-nandmpcopy which would return as soon as the command was submitted.
Unfortunately there are not in cDOT, they have been removed.... I am stuck right now with the fact that OCUM does not do what the customer needs of it and scripting it has turned out to be nearly impossible because things were laid out with the idea that OCUM would be managing these backups and the complexity of the layout would be irrelevant.
That leaves me with the only option of re-designing the snapvault implementations to remove vaults from DR desitnations and pull them from the sources thus increasing the bandwith required of snapvaults between datacenters. Doing this will at least allow me to control the restore process somewhat and provide a viable solution to the customer.