Replication compatibility

Similar Questions

• Replication with Ultra4 compatibility?

  I have a ReadyNas Ultra4 (strandard not pro or something special). Looking to buy an another ReadyNas to save the exisiting Ultra4. RN31441E-100EUS looks like a nice, but both would be compatible to run replication?

  Hello gazzaroo,

  ReadyNAS Ultra 4 is an OS4 which does not come with free ReadyNAS Replicate. Please see http://kb.netgear.com/app/answers/detail/a_id/20841/~/readynas-replicate-faq for ReadyNAS Replicate info and license needed.

  Here is a user manual that you may want to check before you buy: http://www.downloads.netgear.com/files/GDC/READYNAS-COMMON/ReadyNAS%20Replicate%20UM_10Jul2013.pdf

  I hope this helps.

  Kind regards

• VSphere 6.0 backward compatible with vCenter 5.5 replication is?

  At one point, the vSphere replication 6.0 compatibility matrix said that it is compatible with vCenter 5.5.  I think it was around mid-March.  Now, he seems to have changed and says vSphere 6.0 replication is only compatible with vCenter 6.0.  Is this true?  Are there plans to make vSphere replication 6.0 backward compatible with vCenter 5.5?

  Bill,

  A decision was made not to support backward compatibility between replication 6.0 vSphere and vCenter Server 5.5 going forward.  This is the result extended and careful considerations affecting the provision of quality and consistent user experience for our customers using vSphere 6.0 replication.

  Thus, vSphere 6.0 replication is officially supported with vCenter Server 6.0 only (SSO 6.0, 6.0 PC, Web Client 6.0).  This resulted therefore in the interoperability of public VMware product matrix.

• vSphere replication device 5.5.1.2 Build 1999430 to 5.5.8 upgrade?

  I have vCenter Server 5.5 U2 both protected and DR Sites, vSphere replication device 5.5.1.2 build 1999430

  I'm not able to move the unit to 5.5.8 version or by using update manager, nor page VAMI (Update Section)

  Any ideas, please.

  Kind regards.

  Ndiaye.

  Unfortunately, upgrade is possible between minor versions... 5.5.x to 5.5.x etc.

  The replication of vSphere upgrade

  The downloadable ISO image is the only way to upgrade to vSphere replication 5.1.x 5.5.x or 5.6 to 5.8 Replication vSphere. You cannot pass vSphere replication version 5.5.x or 5.6 5.1.x version 5.8 using vSphere Update Manager or the official repository of update of VMware since the unit of replication vSphere VAMI. See the compatibility matrix for more information on versions supported.
  See Upgrading vSphere replication upgrade to vSphere 5.8 replication.

  See:

  

• vSphere replication and RDM

  Hello

  I have a site that I put in place which has Windows 2012 R2 invited with RDM in physical compatibility mode.  When I go through the wizard of replication vSphere for these servers I can configure replication for the comments and as expected I can not set up for the RDM (which is fine, I have those covered by the SRA) but on the last stage it errors with the following:

  Configure a virtual machine for replication

  VRM Server runtime error. Please check the

  documentation for troubleshooting information. The

  detailed exception: "HMS can't put disc UUID for"

  VM disks: ManagedObjectReference: type =

  VirtualMachine, vm-34 = value, serverGuid is C5ABE757 -.

  9697-4C6A-A36B-F98F72EFB5GG'.

  Contoso\tdaley

  VC1.contoso.com

  02/09/2014 14:49:40

  02/09/2014 14:49:40

  02/09/2014 14:49:41

  Is it not possible to ignore the RDM or is not my problem?

  Thank you

  Thom

  Physical RDM mode is not supported by vSphere replication and there is a known issue, you cannot configure replication for VM with RDM physical mode even if you exclude this record of replication.

  Check the release notes: VMware vSphere replication 5.5.1 Release Notes

  Cannot configure a virtual machine with disc RDM in physical mode even if the disk is excluded from replication.

  If you configure a replication of a virtual machine with the physical mode, the following error message may appear:

  VRM Server generic error. Check the documentation for any troubleshooting information. The detailed exception is: HMS can not set disk UUID for disks of VM : MoRef: type = VirtualMachine, value = , serverGuid = null'.
  

  Workaround: No.

• Compatibility Matrix vs Release Notes - who 'wins '?

  We run vCenter 5.1 U1 with ESXi 5.1 U1 hosts and at one point, I thought would be so deploy vShere replication 5.1.1 for match/being compatible.

  The compatibility matrix has green checkmarks when selecting vSphere replication 5.1.2 with the foregoing.  I know I can't use vSphere replication 5.5.x and that's fine.

  However, the Release Notes for vSphere replication 5.1.2 States the following: "before that vSphere replication upgrade to version 5.1.2 make sure that you have upgraded to vCenter Server 5.1u2.

  So who 'wins '?  Can I go ahead and use my other purely 5.1U1 vCenter and ESXi environment vSphere replication 5.1.2?  The '' correction '' in 5.1.2 to 5.1.1 is minor, so I doubt I give much to just settle for 5.1.1 for my tests/POC, but I wanted to be sure and prefer to use the more recent/more great if I can.  Thank you.

  had it checked. the release notes are NOT correct and will be changed. Go by the matrix of compat. hope that helps.

• SAN only for VM Disaster Recovery replication

  I am part of the talks for a recovery site that will not be replicated SAN data warehouses. So, we have an essentially empty ESXi environment with LUNS replicated data store. In the case of a DR, the plan would be to start the import of virtual machines in the DR ESX environment. I've never seen replication strict SAN has offered as a solution of Dr. ignore the logistics around IP, naming, etc. I want to focus on the consistency of the VMs who grew up and which have been replicated like that.

  1. My hypothesis is that the system VMs would probably upward in a consistent state of failure. Is that correct or could I do not affirm the VM would be healthy at all.
  2. If the virtual machine is running, I guess that the integrity of any application or DB data on these virtual machines would be suspect.

  As I said, I never considered this scenerio. Most of the solutions I've seen using an application layer to maintain compatibility in different time intervals. Just curious if anyone has had experience with this kind of recovery.

  vmproteau wrote:

  Just curious if anyone has had experience with this kind of recovery.

  Hi vmproteau,

  This works perfectly.  I made thousands of these movements of the virtual machine in a uniform way down with a success rate of 100%.  The portability that we all talk about is real.  He works for me very well since 2005 when I started with EMC SRDF.  I also had great success with SnapMirror of NetApp.  If you have any kind of enterprise storage, you should be fine.  In addition, modern guest operating systems are extremely resistant to crash-compatible power (i.e. 2008 R2 is a dream come true).  In addition, I have never had a problem with NT 4.0, 2000 or 2003 in my data center migrations or exercises of DR.

  Nowadays, most DBAs use something like SQL LiteSpeed and Idera to create local backups on of additional vmdk attached to the virtual machine.  If a recovery of a painting is necessary for example, they can obtain this granular coverage using these products.  Yet once again, I never had a problem with SQL put online following a crash-consistent (i.e. test DR, moving to DC or power event HA).  Of course, YMMV and you must test for your specific environment.

  With respect to the RPO, it is to you to determine how often the table performs the replication.  More often = more money, of course.  You can also get more granular on the SQL backup points.  For many, a backup per day is fine.  Others take Idera SQL backups every 15 minutes for example (a slight exaggeration!).

  On OTN... The biggest risk for your RTO is the lack of organization and preparation (update document and books run scripts!).  In addition, having good PMs to manage the application mapping and interdependencies is essential.  You'd be surprised to know how many tests application fails due to host files, order DNS or boot of VMS (i.e. Ideally you should show AD/DNS, then SQL, then App, then Web).  Practice makes perfect.  PowerCLI is your friend here.

  Unless the plan is to re - ip, this place DR must be built as totally isolated with dedicated physical Firewall (or many sessions of sniffer and excellent ACL).  If you choose SRM (as it should!), a large part of this risk is avoided since you can test in the bubble.  Many companies bit on correct insulation and end up hurting prod during the test.  Don't, don't.  Physical Citrix is particularly vulnerable to this and is often required for DR since many apps is published exclusively via Citrix.  Often, the Citrix server will eventually be multihomed (so the company doesn't have to pay for additional SQL and Citrix license servers, etc.) and will be riding the Prod and isolated environments.  The default behavior is that the Citrix user will get the same routing as the underlying Citrix server so the risk is that they can connect by mistake for prod.  You must study it well.

  Not to mention that Citrix, other considerations ensure good VPN and other mechanisms on the DR site (which will be used for actual testing of isolated app and DR).  Have several new hubs according to the needs and requirements of the network.  This, along with time, often being saved at the end, but are important to your success and should be reviewed as soon as possible.  In addition, to maintain the volumes that you both own (i.e. no laggard vmdk who are orphans, etc.).  Use scripts to check RVTools or Vsante to remain vigilant on this.  What get is replicated on the other side should be clean.  Only what you need.  Each vmx that is there should be one that gets recorded.

  Anyway, with the replication table, this project should be a slam dunk.  Don't worry so much the market crash-compliant of your guests.  It works.

• Compatibility of EVA from HP and VMware SRM

  Hello

  I'm on the side of VMware VMware vCenter 5.1 Update1 with MRS 5.1 installed Update1.

  HP, side I have the hardware/software on both sites:

  -HP EVA 6350 with XCS 11001100

  -HP. view Comand 10.1

  -HP P6000 EVA SRA 5.01.0

  -HP continuous access

  I had a problem with the State of replication group DR get suspended trying Reprotect in the restore process. Gives me the following error"

  «Error - cannot reverse the replication for the consistency group «...»» ». SRA command 'prepareReplication' failed for the consistency group. The fault of server 'ExtendedFault' was no message'

  I searched through the VMware/HP compatibility matrix in the VMware and HP sites, but could not find a clear answer for compatibility issues.

  I check the next page:

  VMware Compatibility Guide: sra

  Anyone who has experienced such a problem with process Reprotection?

  I found the solution to my problem!

  When I went through of the HP Command View and found the path of I/O replication is passed to suspend

  and when I turned it to RESUME a full copy has begun and everything went well.

  NetRock,

• With 2008 r2 Compatibility Modes supported

  Hello-
  I'll set up a cluster of Server 2008 R2 (on hosts) and I would like to use the compatibility mode virtual (not pass-through) for the RDM if in the "Setup for Failover Clustering and Microsoft Cluster Service" for 4.0 and 5.0, it says "Failover clustering with Windows Server 2008 is not supported with virtual compatibility (not pass-through) RDM mode.» And in the "vSphere MSCS Installation Checklist" he says: "Device type must be defined in virtual compatibility mode of cluster across boxes, but not for the standby cluster host or a cluster across boxes on Windows Server 2008." Under the "Clustered disks, virtual compatibility mode (no-pass-through ROW).
  Here's my question, when they say 2008 mean 2008 and 2008 and 2008 r2?  If they mean just 2008 and I can use virtual compatibility mode, where can I find the backup information that I can use virtual compatibility mode?
  I would use the virtual compatibility for several reasons, is most important without doubt so that I can use replication SRM and vSphere virtual machine protection. If I understand correctly, if I use virtual compatibility I'll be able to do this.
  Thanks for your help
  vSphere MSCS Installation Checklist
  http://pubs.VMware.com/vSphere-50/index.jsp?topic=%2Fcom.VMware.vSphere.MSCS.doc_50%2FGUID-E794B860-E9AB-43B9-A6D0-F7DE222695A1.html
  Setup for Microsoft Cluster Service 5.0 and Failover Clustering
  http://pubs.VMware.com/vSphere-50/topic/com.VMware.ICbase/PDF/vSphere-ESXi-vCenter-Server-50-MSCS-Guide.PDF
  Setup for Microsoft Cluster Service 4.0 and Failover Clustering
  http://www.VMware.com/PDF/vSphere4/R40/vsp_40_mscs.PDF
  Setup for Failover Clustering and the Microsoft Cluster Service 4.1
  https://www.VMware.com/PDF/vSphere4/R41/vsp_41_mscs.PDF
  All versions
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1004617

  Almost all clusters require RDM.

  The reason is that some commands (more precisely, orders usually locking like SCSI2, locks SCSI3) to have crossed the the device and RDM virtual mode do not allow the commands to pass through.

• RS 5 + VC 5 + ESXi 4.1, replication?

  I have a client who wants to use the new features of replication of RS 5. I know that it requires VCenter 5 and the compatibility matrix indicates that ESXi 4.1 is supported, however I can not find no confirm that SRM 5 replication will work with a combination of 5 VC and ESXi 4.1. Knowledge for sure?

  -Adam

  Hello

  vSphere replication only works with 5.0 ESXi hosts.

  You will find confirmation in SRM 5.0 release notes:

  
  

  vSphere replication. When it is used in conjunction with VMware vSphere 5.0, Site Recovery Manager 5.0 introduces a new ability to use the 5.0 vSphere host to perform the replication of the slot voltage of the virtual machines on the network to another host vSphere 5.0, without requirement of the storage array-based replication. As virtual machines change with use, the changed blocks are replicated on a snapshot of the virtual machine reside on the recovering site, in line with a goal of recovery Point defined as a property of the virtual machine.

  and

  SRM 5.0 can work with previous versions (4.0, 4.1) vSphere and Virtual Infrastructure (3.5) only if you are using replication based on the Bay. If vSphere replication must be used (alone or in conjunction with the replication on Bay) then VMware ESX must be upgraded to version 5.0 as part of the upgrade process.

  Rym.

• SRM FC SAN compatibility

  I currently have an EMC CX3 - 10 c to each of my spots and I use MirrorView/s for replication between the primary and secondary site. SRM 4.1 is located at the top of this infrastructure and everything works well in terms of VM failover and failback between the two locations.

  If I upgrade the CX3 - 10 c to my main site to a VNX 5300 will be there at the RS level compatibility issues? Should I just move to a CX4 and stick to the Clariion range?

  Thank you

  PJ

  If you can ensure that both material can perform mirrorview/s then it should be no problem that SRM automates all of the current process.

• software compatibility

  Before I dive and upgrade to Sierra, I'm looking for a reliable source check the compatibility of the applications, I currently rely on.  Many are a bit dated.  Any suggestions?

  Main applications:

  Microsoft Office for Mac 2011 v 14.6.8

  Quicken for Mac 2007 v 16.2.4

  Photoshop CS5 x 64 new v12.0

  Roxio Toast 10 Titanium v 10.0

  Apple Pages, Numbers and Keynote ' 09

  Running OS X Lion mountain.

  Click here.

  (145086)

• I have to stay with OS10.7.5 due to software compatibility, but is it possible to update Safari to latest version during your stay on OS10.7.5

  I have to stay with OS10.7.5 due to software compatibility, but is it possible to update Safari to latest version during your stay on OS10.7.5. How this is done. Thank you very much.

  It is not possible to update Safari past 6.1.6 on Lion.

  (144969)

• How to: Crush 3/iMac 5 k (compatibility mode)

  Hello friends,

  I see quite a few new features on the market with Thunderbolt 3. According to the FAQ of TB3 Intel, TB1 and TB2 was designed with future upgrades in mind. This means that you can connect, once a solution is available, on a host of TB2 TB3 system using compatibility mode. It will only work to 20Gbps TB2, but work remains. The same is true of peripheral TB2 TB3 host computer (will work but at slower speed)

  This would be similar to the connection of a USB 3 device on a USB 2 or 1 USB host but only get speeds over slow or vice versa.

  
  

  The question I have is that if someone came out with these fittings/adapters? What I've seen online seems to go using a device of TB2 and TB3 host and each of these adapters is Windows only. I have spent too many hours searching so I'm curious to know if someone has yet to fall on an adapter or converter that connect DisplayPort TB2 host and have the device USB-C/TB3 (USB - C not only) in compatibility mode.

  The reason? Peripheral TB3 are already less expensive than TB2 devices. I don't know who will get the most expensive. I don't care 40Gbps if he gives me a simple way to add multiple devices USB 3.0, exhibitions and maybe the eSata device. I know there are hubs, but I would prefer something that is the test of the future TB3 would be cheaper and future proof for NeXTGen computers.

  (Sorry for the TL; DR but it is always a person who does not read or "assume" it is a noob question and gives an answer "Captain Obvious". Don't BE this guy here...)
  

  Sincere greetings,

  Jorge Uptown

  JLopez. Chicago wrote:

  The question I have is that if someone came out with these fittings/adapters?

  bolt-adapter https://www.StarTech.com/cables/Thunderbolt-3-cables/Thunderbolt-3-USB-c-Thunder ~ TBT3TBTADAP

  

• DIGITAL CAMERA RAW COMPATIBILITY UPDATE 6.21

  ***? How many times I have to do? I'm FED UP! I don't care ABOUT RAW! Update your program... I have

  NEVER USE!  NOT my computer!

  You're not talking Apple here.  It is a moderated forum for Apple to discuss features and troubleshooting. Apple-> system-> software update Preferences menu contains options to disable automatic downloads, although the Mac App Store update itself for Snow Leopard activates the automatic notifications of updates.  While a nuisance, you have just to tell more later, only choose to update once you have read the documentation to verify that its good operation with what you have.  Always back up your data before allowing updates.

  For direct feedback to Apple, who may have only one impact of future operating systems, http://www.apple.com/feedback

  If you find that a specific update has compatibility issues, we invite you to sign up for a free developer online account on http://developer.apple.com and submit a bug report to http://bugreporter.apple.com where you can know at least that if it's something reported before.  But this will not use or disclose this information here because of a confidentiality agreement.