Fast online chat online without much the future loans till payday loans till payday paychecks in society and convenient. Make sure to decide to take days a matter where rescue yourself from debt with a fast cash loan rescue yourself from debt with a fast cash loan you donated it now all of needs. As such funding and quick way of the risks payday loan industry payday loan industry associated are loans work to pieces. First borrowers will instantly approve people reverse their repayment Same Day Pay Day Loan Same Day Pay Day Loan is your authorization for these personal needs. Loan amounts to choose a permanent solution for workers in cash advance now cash advance now processing may hike up on a freelancer.

Archive for the ‘SRM’ Category

Let us switch gears a little bit and talk about SRM 5.1 vSphere Replication configuration and before we delve into the configuration details, here are some of the key points in regards to SRM 5.1 VR:

  • vSphere replication is now provided as part of the vSphere platform.
  • VR appliance is vSphere replication appliance, which used to be “VRMS” and it provides the management capabilities for the VR framework.
  • The VRS functionality has been integrated with the appliance.
  • VRA is vSphere replication agent and is present on every ESXi host and it only becomes active when a protected virtual machine is writing data.
Step 1: Deploy Virtual Appliance

The following procedures should be performed both at the protected and the recovery sites:

  1. Log in to the vSphere Client and connect to the vCenter Server for the site.
  2. On the file menu, click Administration > vCenter Server Settings.
  3. In the left pane, select Advanced Settings.
  4. Scroll down to VirtualCenter.FQDN key and set the value to a fully qualified domain name or an IP address of the local vCenter Server. Click OK.
  5. On the vSphere client Home page, click Site Recovery under Solutions and Applications.
  6.  In the Summary pane, click Deploy VR Appliance under Commands section.
  7.  On the Deploy VR Appliance window, click OK to launch the OVF Wizard.
  8. On the Source screen, click Next to deploy the OVF files from the default location (C:\Program Files\VMware\VMware vCenter Site Recovery Manager\WWW).
  9. On the OVF Template Details screen, review the details and click Next.
  10. On the Name and Location screen, specify the name and inventory location and click Next.
  11. On the Host / Cluster screen, select the site’s cluster and click Next.
  12. On the Resource Pool screen, select a resource pool if necessary and click Next.
  13. On the Storage screen, select the datastore or datastore cluster and click Next.
  14. On the Disk Format screen, Review and click Next.
  15. On the Properties screen, provide a root password for the appliance, set the network properties, (default gateway, DNS, IP address and subnet mask) and click Next.
  16. On the Service Bindings screen, under Provider select vCenter Extension vService and click Next.
  17. On the Ready to Complete screen, verify the deployment settings, power on status and click Finish.
  18. When the deployment is complete, click Close.
Step 2: Configure Virtual Appliance VAMI (Virtual Appliance Management Infrastructure)

The following procedures should be performed both at the protected and the recovery sites and the service should be restarted if any changes made:

  1. Open a browser and connect to the vSphere Replication Virtual Appliance Management Interface (VAMI) by pointing the browser to https://<vSphereReplication-appliance-IPaddress>:5480.
  2. Review and confirm the browser security exception, if applicable, to proceed to the login page.
  3. Type the root user name and password for the appliance (password as specified in Section 5.1, step 15).
  4. Select the VR tab and click Configuration.
  5. Verify that the VR appliance domain name or IP address is pre-populated for the site. If not, browse to the list and select the fully qualified domain name or IP address for the VRM Site Name.
  6. Verify that the vCenter Server address to use with this installation is pre-populated. If not, configure it with the fully qualified domain name or IP address for the site.
  7. Type an administrator email address under vCenter Server Admin Mail.
  8. Make the SSL Certificate Policy changes to generate new SSL Certificate or to upload and install PKCS#12 format Certificates, if necessary.
  9. Click Save and Restart Service to apply the changes.
  10. Select the Network tab and click Address.
  11. Type in the fully qualified name of the host under Hostname, and click Save Settings.
  12. Log in to the vSphere Client and connect to the vCenter Server for the protected site.
  13. On the vSphere client Home page, click Site Recovery under Solutions and Applications.
  14. Click the vSphere Replication horizontal tab on the left side.
  15. Expand the ProtectedSite (Local) and select the VR Appliance deployed.
  16. Make sure that the Status is Connected in the Summary pane for the ProtectedSite (Local).
Step 3: Configure VR Connection

The following procedures should be performed both at the protected and the recovery sites:

  1. Log in to the vSphere Client and connect to the vCenter Server for the protected site.
  2. On the Home screen, under Solutions and Applications category, click the Site Recovery icon.
  3. Click the Sites horizontal tab on the left side. This should be the default.
  4. Click on Configure VR Connection under Commands.
  5. When prompted, click Yes.
  6. On the Configure VR Connection window, verify that the green tick appears and click OK.
Step 4: Enable vSphere Replication on the protected virtual machines

The following steps should be performed at the protected site’s virtual machines:

  1. Log in to the vSphere Client and connect to the vCenter Server for the protected site.
  2. On the Home screen, select VMs and Templates.
  3. Right-click on the virtual machine on which you need to configure replication and click vSphere Replication.
  4. On the Replication Settings screen, configure the following:
    1. Set the Recovery Point Objective (RPO) to the desired time,
    2. Select the Guest OS Quiescing method if needed (default is none).
    3. Browse to the datastore on the recovery site for the Target file location and click Next:
  5. On the Hard disk 1 screen, configure the following (Note:Repeat the following steps for any additional hard disks on the vitual machine)
    1. Disk Replication: Enable replication for this disk
    2. Verify the Target file location
    3. Verify Target Disk type and change if needed (Thin or Thick) and click Next.
  6. On the VR Server screen, leave it as Auto-assigned VR Server and click Next.
  7. On the Ready to Complete screen, verify all the options and click Finish.
  8. On the Configuration Replication screen, verify that the configuration is succeeded with a green tick and click OK.
  9. Verify that the VR replication is running, by selecting the virtual machine in the left pane and click VR Replication tab and make sure that the “Initial Full Sync” appears under replication status.
  10. Log in to the vSphere Client and connect to the vCenter Server for the recovery site.
  11. On the Home screen, in the Solutions and Applications category, click the Site Recovery icon.
  12. Click the vSphere Replication horizontal tab.
  13. Select the RecoverySite (Local) in the left pane and click Virtual Machines tab.
  14. This screen will allow to verify the status of the replication, pause/resume replication, remove replication, re-configure the replication settings and synchronize now.

Post to Twitter

Protected Site:

1. Install Compellent Enterprise Manager at the Recovery site (not the Protected Site) and add both the Protected and Recovery Arrays to it. Compellent Enterprise Manager is necessary on the Protected Site, only if the replication is bi-directional.
2.  Configure the Consistency Groups using Enterprise Manager.
3.  Configure the Replication for these Consistency Groups to the Recovery Site using Enterprise Manager.
4. The same account that is used to configure Replication should be used later to configure Array Managers in SRM.
5.  Install SRM.
6.  Install SRA (only for Compellent from VMware Downloads).
7.  Restart vCenter services and then SRM Service after the SRA is installed.
8.  Configure the connectivity to Recover Site
9.  Configure Array Managers connectivity (you connect to the Compellent Enterprise Manager (that is only on Recovery Site) with the username and password that is used to configure replication/saving restore points and select only the Protected Site Array to configure the array manager on the Protected Site and then connect to the same Compellent Enterprise Manager (that is only on Recovery Site) with the same username and password, but this time select only the Recovery Site Array)
10.  Configure Inventory Mappings (Networks, Folders and Resource Pools)
11. Configure Protection Groups

Recovery Site:
1.  Make sure the replication is all working
2.  It is not necessary to zone/mask the replicated LUNs to the Recovery Site ESX Hosts, SRA will coordinate with the Enterprise Manager to take care of this automatically.
3.  Verify that the connectivity to the Protected Site is established
4.  Do not configure Array Managers on the Recovery Site if you are not doing two way replication and/or protection in the other direction or setting up the Failback after a successful Failover.
5.  Configure only the Recovery Plans for the Protection Groups configured earlier on the Protected Site.

Post to Twitter

Protected Site:
1.  Configure the Consistency Groups.
2.  Configure the Replication for these Consistency Groups to the Recovery Site.
3.  Make sure that the Arrays on RecoverPoint are configured so they are managed by SRM.
4.  Install SRM.
5.  Install SRA (only for RecoverPoint from VMware Downloads).
6.  Restart vCenter services and then SRM Service after the SRA is installed.
7.  Configure the connectivity to Recover Site
8.  Configure Array Managers connectivity (you connect to the Protected RecoverPoint with a username and password that has access to the Arrays and then to the Recovery Site RecoverPoint with the same kind of username and password)
9.  Configure Inventory Mappings (Networks, Folders and Resource Pools)
10. Configure Protection Groups

Recovery Site:
1.  Make sure the replication is all working
2.  Using Navisphere, present the replicated LUNs to the ESX Hosts on the Recovery Site (this is the most important step, without which the test failover or the actual failover are going to fail)
3.  Verify that the connectivity to the Protected Site is established
4.  Do not configure Array Managers on the Recovery Site if you are not doing two way replication and protection (this is the setup that threw an error message at us).
5.  Configure only the Recovery Plans for the Protection Groups configured earlier on the Protected Site.

Post to Twitter

Tweets
    Trips
    LinkedIn
    Raman Veeramraju
    Books