Srm58

Unfortunately, not all software is perfect and from time to time I’ve run into issues with SRM as well. This post is a list of items I often see during SRM deployments and some information to troubleshoot issues. Log File Locations SRM Logs: c:programDataVMwareVMware vCenter Site Recovery ManagerLogs Installation logs: %USERPROFILE%Application DataVMwareVMware Site Recovery ManagerLogs Storage Replication Adapater Logs: This depends on the SRA Vendor, but try program filesSRANAME to start with ...

SRM version 5.8 now is now extensible with vRealize Orchestrator (formerly vCenter Orchestrator). This new functionality was expected since the vRealize Suite is all about automation and disaster recovery certainly needs to be taken into consideration. One pain point I’ve seen with SRM has been the ongoing administration of protection groups. Every time a virtual machine is deployed to a protected datastore, the VM also has to be configured for protection. This usually only consists of right clicking the virtual machine and choosing “configure protection” but is also another thing that administrators have too keep track of. ...

If you’ve got SRM 5.5 installed and you want to get the new SRM 5.8 code into your environment, don’t worry. The upgrade process is pretty easy to manage. The important thing to note is the upgrade order and of course your compatibility matrix. Remember that you need vCenter 5.5 U2 or higher to get SRM 5.8 working. Upgrade Order Ensure your vCenter Server and Web Client are on 5.5 U2 or higher in the protected site. If not, upgrade them! Upgrade vSphere Replication on the protected site to 5.8 if you’re using one. Upgrade SRM on the protected site to 5.8 Upgrade your SRA on the protected site if you’re using one. Ensure your vCenter Server and Web Client are on 5.5 U2 or higher in the recovery site. If not, upgrade them! Upgrade vSphere Replication on the recovery site to 5.8 if you’re using one. Upgrade SRM on the recovery site. Upgrade your SRA on the recovery site if you’re using one. Verify the conneciton between your sites is valid, protection groups still exist and recovery plans are in tact. Upgrade ESXi servers on the recovery site Upgrade ESXi servers on the protected site Upgrade VMware Tools. Install Run the installer on the SRM servers. The installer should detect that SRM is already installed an that an upgrade will be performed. ...

A customized recovery plan means the difference between hoursdays of reconfiguration of your environment in the event of a failure. VMware SRM allows for lots of opportunity to customize your recovery plans with scripts and modifications along the way to ease the management of your disaster recovery plans. Run Scripts from SRM Server If we open any given recovery plan we can click on a step we’d like to modify and then right-click to “Add Step…” ...

Setting up some alerting is a good idea once you’ve setup your disaster recovery solution. Let’s face it once you’ve tested your DR solution, you might not look at it again until your next test, which in some cases is yearly! To setup alarms for SRM in version 5.8 navigate to the vCenter object and click the Manage tab. From there click the Alarm Definitions sub-tab. Click the add (green plus sign) to add a new alarm. ...

“Your disaster recovery plan is only as good as it’s last test.” “If you haven’t tested your DR plan, then you don’t have a DR plan.” These are all statements I’ve heard in the industry from CIOs and directors, and lucky for us VMware Site Recovery Manager has a test functionality built in for us to leverage without fear of affecting our production workloads. Run a Test Open up one of your recovery plans and click the monitor tab. Here you’ll have several buttons to choose from as well as seeing the list of recovery steps. To run a “Test” recovery click the green arrow button. ...

A terrible thing has happened and it’s time to failover your datacenter to your disaster recovery site. Well, maybe you’re just migrating your datacenter to a new one, but this is always a bit of a tense situation. Luckily we’ve had the opportunity to test the failovers many, many times before so we can be confident in our process. Go to the Recovery Plan and click the monitor tab. Click the “BIG RED BUTTON” (yeah, it’s not that big, but it has big consequences). ...

Some companies have built out their disaster recovery site with a stretched layer 2 network or even a disjoint layer 2 network that shares the same IP addresses with their production sites. This is great because VMs don’t need to change IP Addresses if there is a failover event. This post goes over what options we have if you need to change IP Addresses during your failover. Network mappings SRM 5.8 has a wonderful new way to manage IP Addresses between datacenters. Prior to SRM 5.8 each VM needed to be manually updated with a new IP Address or done in bulk with a CSV template (show later in this post) if you had to re-IP your VMs. Now with SRM 5.8 we can do a network mapping to make our lives much easier. This is one of the best new features of SRM 5.8 in my opinion. ...

A recovery plan is the orchestration piece of Site Recovery Manager and likely the main reason for purchasing the product. All of the setup that’s been done prior to creating the recovery plans is necessary but the recovery plan is where magic happens. When we go to the Recovery Plans menu in Site Recovery, we’ll see the option to click the notepad with the “+” sign on it to create a new recovery plan. ...

SRM Sites and resource mappings are all done. It’s time to create some Protection Groups for our new VMware Site Recovery Manager deployment. A protection group is a collection of virtual machines that should be failed over together. For instance, you may want all of your Microsoft Exchange servers to fail over together, or you may want a Web, App, Database Tier to all failover at the same time. It is also possible that your main goal for SRM is to protect you in the event of a catastrophic loss of your datacenter and you’re concerned with every VM. It still a good idea to create multiple protection groups so that you can fail over certain apps in the event of an unforeseen issue. Think about it, if your mail servers crashed but the rest of your datacenter is fine, would it make sense to just fail over the mail servers, or the entire datacenter? Just failing over the mail servers would make sense if they are in their own protection group. ...