As per the first post in this series, this article documents a demo that we did at MMS last week.
In this demo, I showed how we could automatically add a newly deployed server into the DPM protection cycle. This is a very simple demo, with only 4 activities!
The complete runbook looks like this.
As per all the other demos we do, we are showcasing one segment of a greater process, so we are using a Custom Start to pipe in the information that would typically come from an in-flight process such as a change control. Also, again, this is a demo runbook, and does not contain all the fail paths and best practices we recommend for production runbooks.
So now we have the input we require, which is the server that we want to add into the protection group of DPM. We do this in 2 steps. Firstly we need to get the Server information using the Server Name that was entered to start the runbook.
And then once we have the DPM information back, we can use that to get the further information required to add the Server into the Protection Group.
In our demo we hard coded that we would add the server into the “System Protection” group, however as per previous commentary this would typically be a dynamic entry. We specify a manual replica method, as the next activity will trigger the first Recovery Point creation.
And here in the last activity, using the newly created Data Source, we trigger the creation of the first recovery point.
And that’s it! A short, but very powerful demo of how we can automatically add new resources into protection cycles.