EMC Recoverpoint: Automating Cluster Configuration backups

An important (but often neglected) part of any Recoverpoint deployment is to ensure you have regular backups of your cluster configuration.

Important for DR, it also serves as a useful reference point for configuration forensics (What changed and when)

There are multiple ways to do this, however my preference is to utilize an existing scripting host and Powershell. This allows for ‘set & forget’ scheduling.

Firstly, you’ll need to download the putty ssh companion ‘plink’ from here and save it out into a working directory.

I’m going to use plink to open up a connection to the cluster hostname “PRODRP” pipe the output through out-file and save it into the c:\files folder. The filename will be called PRODRP_xxxxxx.backup, where xxxxxx will the current date in ddmmyy format. So if run today it would create a backup file PRODRP_160914.backup

 

17-09-2014 9-36-11 PM

[default admin user/pass is used as an example only !]

Scheduled to run weekly (or your preference), you’ll end up with a nice config repository like this;

rpb2

But this one liner only backs up a single cluster, and every Recoverpoint CRR deployment will have 2 clusters so here’s a script to back the config of both Clusters (or more if req) in your environment.

To configure for your own setup, replace the names in the $clusters variable with your own cluster names. Format the date to your preference, enter your user/pass and alter the save location as appropriate.

Save to a PS1 file and create a scheduled task. The filename will be made up of your cluster names, the current date .backup.

Your results will look like;

rpb4

Easy, fast, clean & reliable. Enjoy

5 thoughts on “EMC Recoverpoint: Automating Cluster Configuration backups

    1. Hi Les, and thanks for reading. There’s always more than one way to achieve a result. If you send me the link to the emc batch file, I’ll add it here.

    1. The file is readable from a text editor and you’ll see it’s basically commands used to recreate the cluster.

      Note that it doesn’t include security (account) settings which can be exported/imported similarly by using save_account_settings

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: