Quantcast
Channel: VMware Communities : All Content - Site Recovery Manager
Viewing all 2572 articles
Browse latest View live
↧

Site Recovery Manager Kickoff Time

June 9, 2014, 6:26 am
$
0
0

We have site Recovery Manager 5.5, build 1315893. We are using vsphere replication.

 

We have set the RPO time to 24 hours. The issue I have is that the time the replication starts drifts. For example if I do the first replication at 7:00 PM, I would like to it consistently start the replication each day at 7:00 PM. It actually seems to start earlier. So within a week after starting the replication it could be starting replication at 4:00 or 5:00 PM instead of 7:00PM.

 

The only way I get it to get close to 7:00 PM again is to log on at 7:00 PM and do another manual replication.

 

Is there a way that I am missing to make it start at a certain time instead of using a 24 Hour RPO? Worst case is there a way to create a script to kick off a manual replication that I could setup to force it closer to my 7:00 PM time like I am doing manually today?

 

Thanks,

 

Brian Sutcliffe  

↧
Search

VM protection at DR site using partial VMDKs

June 10, 2014, 6:20 am
$
0
0

Is it possible to replicate a virtual machine using SRM with only partial disks replicating to DR site ?  or all the Volumes of a VM needs to be replicated to DR site in order to protect VM.

↧
↧

License problem on SRM

June 10, 2014, 8:19 pm
$
0
0

If I only would like protect one site, can I only buy SRM license for the protected site and not need for the DR site?

 

If yes, what license I should use of the SRM on DR site?

↧

SRM 5.0.1 installation woes. ODBC error (42S01)

May 30, 2012, 11:45 pm
$
0
0

I’m trying to install SRM with VR.

I am installing the first SRM server, this is a windows 2008R2 VM.

The Database is an SQL 2008 R2 DB on a remote server using SQL authentication.

 

On installation right as its about to create the database I get the following error;

 

     C:\Users\Administrator\AppData\Local\VMware’ is not a directory – yep it does not exist!

 

I click Retry and I am presented with a lovely dialog with an ODBC error;

-----------Dialog----------------

Failed to create the database tables.

Details:

There was an error creating the sequence: “ODBC error: (42S01) – [Microsoft][SQL Server Native Client 10.0][SQL Server]There is already an object named ‘dr_table_catalog’ in the database.“ is returned when executing SQL statement “create table dr_table_catalog (name varchar(255) PRIMARY KEY NOT NULL)”

Press Retry to try again or press Cancel to exit installation.

-----------Dialog----------------

Ok sounds like I using a database that is already got SRM taking to it, the thing is, this is a new SQL server, New environment and SRM has never been installed previously.

I can delete and recreate the database but to no avail. The same happens.

 

Any suggestions?

↧

SRA Issue

June 15, 2014, 2:07 am
$
0
0

He Team I was having this pb at the first that was solved by doing the manipe here

 

Échec du chargement du SRA depuis 'C:/Program Files (x86)/VMware/VMware vCenter Site Recovery Manager/storage/sra/ONTAP'.

La commande SRA 'queryInfo' n'a pas retourné de réponse.

 

but once i did VMware KB 1027218

Now i have

 

Échec du chargement du SRA depuis 'storage/sra/sampleSra'.

Le chemin d'accès racine des SRA 'storage/sra/sampleSra' n'existe pas ou n'est pas un répertoire.

 

Could you plz help

 

Mercii

↧
↧

SRM 5.1 Replication

June 15, 2014, 3:51 pm
$
0
0

I am using SRM 5.1 with vSphere 5.1. I have 20 vms being protected by SRM. We have one virtual replication appliance at each site. The total disk space for these 20 vms is roughly 6 TB. We have a 200 MB MPLS between the primary and recovery site. The only traffic going over this link is SRM replication.

 

All of my protected vms show success for state and no errors are present under the SRM plugin inside of vCenter. When I run the cli command to get the replication status for my vms, they are all showing 3% or less. This process has been running for 2 full days. When I look at the last sync time its blank. When I look at the recovery site I see the shadow vms, but the amount of disk usage is very small. I selected thick provision when I enabled replication on the vms. What am I missing? Is there a good way to tell for sure if these vms are fully synced? We currently have the RPO set to 24 hours. The goal is to get the down to 30 minutes.

 

 

Thanks,

 

Ed

↧

Planned migration error the vdisk-to-host mapping was not created because this vdisk is already mapped to this host

June 17, 2014, 8:43 am
$
0
0

Hi all,

 

Is there someone encounter the same error below. Co'z when i perform planned migration i received this error . 

i'm using SRM 5.1.2,    SRA 3.2.0,  IBM v7000 storage 7.2 microcode by checking to vmware compatibility matrix this is supported for vshpere version 5.1 update 2. I can successfully perform test migration and disaster recovery without error. thanks in advance for the help..  

planned migration error.jpg

↧

SRM not connecting to recovery site

June 17, 2014, 8:52 pm
$
0
0

Hi All,

 

We are running the latest SRM version 5.5 and we are seeing the below in the SRM logs, any ideas?

 

Line 10810: 2014-06-18T10:44:54.087+10:00 [01224 verbose 'HttpConnectionPool-000000' connID=dr-admin-4f34] [IncConnectionCount] Cannot increment number of connections to <cs p:0000000006aa1050, TCP:servername:80> as max connections (50) already in use

↧
Search

SRM Clarification question - IBM SRA

June 18, 2014, 9:16 pm
$
0
0

Hi,

 

My employer is currently piloting SRM 5.5 and I'm trying to gather some clarification regarding the reprotect option of SRM and in particular what it will and won't do from the IBM SRA 2.1 perspective.

 

Our current scenario is that we have two sites (site A & site B) with vCentre and SRM established in both sites and all of our VMs reside on our IBM N6060 SAN which is replicated to site B and so far each site is paired and the SRAs arrays established.

 

I'm trying to test the following.

 

1.     VM in site A resides on its own SAN based LUN which is replicated to site B.

2.     Protection group and recovery plan for this one VM has been created and the placeholder VM is visible at site B.

3.     I plan on recovering this one individual VM to site B.

 

My question is what is the process for reprotecting this VM back to site A.

 

1. Delete the existing recovery plan and protection group.

2. Does the reprotect revert the snapmirror for this one VM or all snapmirrors.

3. Create the protection group and recovery plan in site A.

4. Perform the recovery.

 

Has anyone had any experience with IBM N series and SRM?

 

Cheers

↧
↧

Error - Failed to recover datastore while rinning SRM test

June 19, 2014, 5:26 am
$
0
0


Hi All

 

Below is my environment details

 

Primary Site

ESX 4.1 update2

Vcenter 5.5 update1a

SRM 5.5.1

SRA version :  IBMSVCSRA_v2.2.0.130422

 

Protected site

Both ESX4.1 update2 & ESXi5.5 update1

Vcenter 5.5 update1a

SRM 5.5.1

SRA version :  IBMSVCSRA_v2.2.0.130422

While running the SRM test am getting below error

Error - Failed to recover datastore 'PROD-DS03'. VMFS volume residing on recovered devices '"2101"' cannot be found. Unable to resignature volume 'PROD-DS03' (53903400-6e651f24-ae41-5ef3fc1eab5b) because there are multiple copies of one or more extents. SRM's attempt to detach duplicate copies ("naa.60050768018105ced8000000000010ff") from ESX host '10.146.211.121' failed.

 

 

If i map the resources only to ESXi5.5 update1 host test is getting successfull

 

 

 

 

 

↧

vSphere Replication | Schedule Sync Time(s)

June 21, 2014, 8:07 am
$
0
0

I can't believe it's on version 5.5 and you still can't set a date/time to sync VMs.  Does no one complain that it's crushing their WAN?  I can understand that the RPO based work around is to kick the jobs off at night but still, what's so hard about having an option for a start time? 

 

Not everyone can do hardware based replication.

↧

SRM 5.0.1 the Recovery Plan test works but Recovery fails

June 22, 2014, 4:42 pm
$
0
0

srm.PNGHello All,

 

I am running SRM 5.0.1 on Vsphere 5.0.1 with Netapp SRAs, the issue is the setup looks all good, the test recovery plan works well. I can see a test machine recovered on the recovery site during the test but when I try and do the real recovery it fails on step 5


5. Prepare Protected Site VMs for Migration  Error - Unable to access file [XXX_SRM_PH] Failed to unregister protected VMs.

 

and then I cam across this article on VMware site VMware Site Recovery Manager 5.0.1 Release Notes and it talks about the placeholder datastore. The protected cluster should have access to the placeholder datastore? I thought the placeholder datastore was accessible to the recovery cluster? Please advice.

↧

How to get the SRM externsion ID in a Shared Recovery Site environment

June 24, 2014, 6:48 pm
$
0
0

I'm setup a new site and I want to get this site be protected and point to the existing Shared recovery site.

I have no idea what is the SRM extension ID that the previous vendor used

Is there anyway to extract the SRM extension ID?

↧
↧

SRM 5.5 w/ MirrorView - Does ReProtect do a full sync?

June 25, 2014, 12:26 pm
$
0
0

We are planning on using MirrorView with SRM 5.5.  After a failover, does the Re-Protect operation perform a full sync again, or does it just copy over the delta blocks?

 

Thanks.

↧

How to know the exisiting SRM installation is using Automatically generate certificate or Using a PKCS #12 certificate file

June 25, 2014, 5:09 pm
↧
Search

EMC Recoverpoint consistency groups question

June 27, 2014, 12:44 pm
$
0
0

I'm looking for anyone who's using the EMC RecoverPoint appliances for the array based replication in a VMWare 5.x environment.

 

Recently we went through an update of our EMC VNX5700 that we use with VSphere 5.1.  As part of the upgrade, we purchased two of the EMC RecoverPoint appliances to replicate the LUNS/datastores to our D/R facility.  Previously, we used the EMC MirrorView product but went with the appliances to reduce the load on the VNX processors.

 

We have about 18 hosts at the primary site, all sharing a group of 19 datastores (each datastore is in its own LUN). 

 

The Recoverpoint appliance groups the luns by consistency groups.  All the luns in a given consistency group are replicated as a unit, and are recovered at the D/R site
together.

 

When the vendor/reseller (not EMC) did the initial configuration, he said that since all the hosts see all 19 datastores, all the LUNS had to be in the same
consistency group.

 

The problem we're seeing with this is that when we need to add a new LUN, when we add it to the consistency group, we basically lose the replicas at the remote site until the new lun is replicated.

 

In almost all cases a given VM is all on the same LUN; we typically don't split VM's over multiple datastores.  I could understand keeping all the VMDK's of a VM in the same consistency group, but do we really need all LUNS that all the VMWare hosts see to be in the same consistency group?

 

Is there a problem if we create a series of smaller consistency groups, as long as we don't have VM's "span" across different groups?

 

We have VMWare SRM for our D/R site, but we're still in the process of setting it up and  hadn't gone live with it, and haven't reconfigured it since we changed from MirrorView to RecoverPoint.

 

Any comments would be appreciated.

↧

SRM Placeholder Datastores

June 28, 2014, 12:41 pm
$
0
0


Hello,

 

I would need an expert opinion on designing the placeholder datastores approach. We have 6 clusters at the protected site & same 6 clusters would be created at the recovery site for the DR.

Can someone please suggest what would be the best approach to decide on the number of placeholder datastores to be created for such decision? Should there be one global placeholder datastore for all the clusters or we should create 1 placeholder datastore for each of the cluster.

 

What are the pros and cons of doing any of these scenarios?

 

Thanks

Rajat

↧
↧

The "correct" way to resize (expand) VMDK protected by vSphere Replication *and* SRM

June 30, 2014, 2:24 pm
$
0
0

Hello,

 

I am trying to figure out which method of resizing/expanding VMDK files is the official VMware-supported method (as of vCenter 5.5U1, ESXi 5.5U1, vSphere Replication 5.5.1, and SRM 5.5.1).  In particular I am looking for the use case where the original replication session was NOT set up using seeds.  There are basically three VMware-published approaches:

 

1) According to the "VMware vSphere Replication Administration" guide, page 62, under "Resize Virtual Machine Disk Files During Replication Without Using Replication Seeds", the procedure is to perform a VM recovery, stop replication, resize the source disk, resize the "recovered" disk at destination, unregister the recovered VM, re-configure replication using the recovered disk as the new seed.  I have used this approach in a "pure" vSphere Replication implementation (no SRM) and it works great, and it's not terribly complex.

 

2) However, the SRM documentation has a different procedure.  The "Site Recovery Manager Administration" document, page 86, under "Resize Virtual Machine Disk Files During Replication Without Using Replication Seeds", the procedure is to run a test recovery of the VM, clone the VM to the same datastore, revert/cleanup the test, stop replication, resize the source disk, resize the "cloned" disk at destination, unregister the cloned VM, re-configure replication using the cloned disk as the new seed.  This procedure won't work if you don't have 2x the amount of disk space needed at the destination.  So if I need to expand a 1.5 TB disk to 1.6 TB, I need at least 1.5 TB of free space at the DR Site in order to clone the recovered VM momentarily.  I also have to wait for the clone operation to complete, as opposed to the above procedure which is much faster.

 

3) Finally, there is a VMware KB article that describes yet a third approach, which is basically the above approach, plus the added complexity of using the CLI to rename disk files, modifying the VMDK descriptor files, replacing the dbb.uuid values:

 

http://kb.vmware.com/kb/2042790

 

My question to the SRM + vSphere Replication community is: which is the above approaches is the "correct" approach for resizing virtual disks when using vSphere Replication 5.5.1 with SRM 5.5.1 (without having used seeds for initial replication)?

 

Thanks,

Bill

↧

SRM Recovery Site and Protection Site

June 30, 2014, 7:24 pm
$
0
0

i'm new srm,

i have one little confusing with srm,

i have a diagram like that

Capture.PNG

 

Can I use site 1 as protection, but it also makes the task of recovery site for site 2, and Site 2 also like that protection site and recovery site for site 1 ?

 

pls have me open mind mine.

 

Thanks,

↧

Unable to add array manager, SRA command 'discoverArrays' failed. SRM 5.5

October 8, 2013, 5:25 pm
$
0
0

Setting up SRM 5.5 using RecoverPoint new install and setup.

 

I have downloaded and installed the recommended SRA Adapter in my SRM server, which is EMC_RecoverPoint_Storage_Replication_Adapter_Version_2.2.0.0. The Unisphere for RecoverPoint I believe has been set up properly too. But I must be missing something.

 

Every time I try and add the array using the either the IP or the FQDN with the user name and password of Unisphere it will not connect. I get the following error: See attachment, any insight what am I missing?

 

Thanks

↧
Viewing all 2572 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>