Part 2 – Site Recovery Manager Installation

  • Log onto the SRM application server
  • Locate and start up the SRM installation program
  • Select your language and then click ‘OK’
  • After a short while the installation wizard will begin… click ‘Next’.
  • On the ‘Patents’ screen, click ‘Next’
  • Accept the license agreement and click ‘Next’
  • Change the installation directory to the D: drive as shown below and click ‘Next’:
    part2 - 1
  • As we will be utilising XIV replication, you should now select ‘Do not install vSphere Replication’ (this can be modified at a later date by going through the installation utilising repair mode)
    part2 - 2
  • Now enter the ‘vCenter Server Address’ and the ‘vCenter Server Username’ and ‘Password’, then click ‘Next’:
  • You will now be shown the vCenter Certificate, click ‘Yes’ to accept it.
  • On the ‘Certificate Type Selection’ screen, select the ‘Automatically generate a certificate’ option (the certificates can be changed at a later date), and then click ‘Next’
  • Enter the Organization and Organization Unit, then click ‘Next’
  • Enter a name for the Local Site, administrator email addresses and also how the Local Host should be seen, then click ‘Next’:
  • You are now requested to enter in the database information.  The ‘Database Client’ should be ‘SQL Server’ and then enter the DSN name, username and password created earlier, then click ‘Next’
  • Finally click ‘Install’ to begin the installation
  • You should now be able to go into the ‘Plug-ins’ section of the vSphere client and install the new Site Recovery Manager plug-in.

This ends Part 2 of our instructions… please click here to continue to Part 3 or here to return to the 10-part Site Recovery Manager menu.

About the Author


I have been in IT for the past 15 years and using virtualisation technologies for around the past 8 years. I started, as quite a lot of people do, working with PCs after playing with such iconic systems like the ZX81, ZX Spectrum and then progressing through 386s, 486s, Pentiums etc. After being headhunted at sixth form to work for a small company based around Hertfordshire, UK. I began working with small businesses and gaining a lot of hardware experience. Three years later, after helping to increase the size of the business, I needed to gain exposure to a larger environment to progress my own career. I joined a large manufacturing company around Electronic Test and Measurement which progressed my skills onto more PC work, hardware work and then onto Server Operating Systems. I progressed again onto a consultancy company based in Reading, UK. Initially working as an engineer performing hardware / software installations for larger companies contracted out to the consultancy company, I moved up into a Consultant position continuing my travel across the UK assisting and providing solutions to companies. I finally moved on again to my current position, working back in Hertfordshire, UK. Again working for a large manufacturing company, this time with over 50,000 users worldwide. I am responsible for the datacenter hardware, the storage environment, the vmware environment and also implementing their new Citrix XenApp farm. My days are busy but also productive, its a friendly environment and in my four years of being with the company, I have seen many changes in technology and infrastructure in use within the company. About the site I started this site as I had been thinking of having more of a presence on the web for a while. On a daily basis, I perform tasks and use tools that others may not use or may not think to do and therefore I thought that I would share some of these experiences and tips with others to help with their day to day work. Currently, my main focus of work is around VMware and Veeam Backup & Replication but hopefully as my tasks progress, I’ll be able to share useful bits of information about other areas of IT as well.

Leave a Reply

Your e-mail address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.