Secondary Site Replication

Similar Questions

• PS4100 EQL replication to secondary site

  Hi all

  We need to configure the EQL replication to a DR site. It will probably take 1 x or 2 x PS4100; or 1 x PS4100 and 1 x PS6100 on each site.

  A few Qs for experts:

  (1) the primary site data will pass through the network of a 10 GB switch through 2 sets of x of firewalls and switches on a basis of 1 GB network. The secondary site will be also 2 x fixed firewall and the spine 1 GB. By reading the documentation Dell I understand that we need ICMP and 3260 open over the WAN.

  Is there any kind of questions of data from 9000 MTU at 1500 MTU across the network? Any kind of impact?

  (2) designed to set up the initial seed on site, i.e., configuration of the EQL box replica on the same network and replicate the volumes. Once the initial seed, move the EQL box to secondary site and re - configure replication to point to the new IP address and synchronize the Deltas? Is this the best way? or should I use the manual utility provided by Dell? or something else?

  Comments are much appreciated.

  Hello

  Re: 1 there are also each port iSCSI members on each side of the must be able to reach all the other ports on the side of the partner.   This NAT firewall won't work.

  Re: 9000 vs 1500.  There is no problem.  Each iSCSI session, which is what the replication uses, can be negotiated frameworks standards or Jumbo.

  Re: 2 putting them side by side are the fastest and easiest way.

  Kind regards

• Cannot save an ACS secondary for replication of ACS primary 5.2.

  Hello

  I hope someone can help me.  Currently, I have two devices Cisco ACS and both are classified in the PRIMARY.  The first ACS is running version 5.2.0.26 while the second ACS is running version 5.3.0.40.

  My original thought was to install the first ACS and do serve primary and have it replicate its data on the ACS SECONDARY.  Somehow, after installation, the ACS are now listed as PRIMARY.  When I go into secondary ACS under Deployment Options to try to save it in elementary school, I get the following error message:

  "This failure has occurred.  Failed to authenticate with node.  Your changes have not been saved. »

  Even if I try this GBA primary to save it for the secondary ACS, I get the same error message.  I tried all passwords including the credentials of the admin super user, my credentials for the administrator and the credentials provided to SSH in ' GBA and nothing is helping.

  Reading online, I read there was a way to remove an ACS secondary, but I don't have the ability to add this server in the primary for "bump it down" to a secondary antibody hoping to save it for the primary ACS.

  If anyone can give me some pointers, I would greatly appreciate.

  Thank you, and all have a wonderful day.

  THERE

  Yvonne,

  If the identifier is the same then definitely replication does not work, you will not be able to enroll in primary school if the license is the same. The good side is that you have the other license, you only need to install.

  However I have more bad news, the only way to re - install a license file in ACS 5.x uses the CLI command 'acs reset-config', but it will also delete all of the configuration that you have on this server, except the network configuration (IP, gateway, DNS, etc.)

  After entering this command if you are trying to access the GUI, you should not use the name of user and password acsadmin/default, then you will be asked to locate the license file.

  Here is a document with this information where you need it:

  http://www.Cisco.com/en/us/partner/docs/net_mgmt/cisco_secure_access_control_system/5.3/user/guide/my_wkspc.html#wp1052906

• Cannot save the ACS 5.4 as secondary for replication

  Dear all,

  I am not able to regisrter my ACS in DR 5.4 as secondary to my primary ACS in DC 5.4 for replication.

  Attached is the error I get

  Kind regards

  Ranjit

  Hello

  Enter the IP address of the primary server, not the host name.

  It seems that your DNS has no name, so you have to add the ip address and try.

  HTH

  Amjad

  Rating of useful answers is more useful to say "thank you".

• Requirements for vSphere remote site replication

  I run 3 Enterprise 5.5 x vSphere hosts in A Site with vCenter.   I want to add a new host in a remote site and configure vSphere replication between them.  Issues related to the:

  • Do I need to vCenter in slot 2?
  • If vCenter Site of A is the Site management and hosts of the Site B and Site A goes down, vSphere replicated VMs can be restarted to Site B without problem?
  • Is there a risk to not have a vCenter dedicated to Site B on the changeover plan?

  Thank you

  -Matt

  Hello

  (A) If you have vCenter in slot 2, you will need to deploy device VR and match two VR UI sites.

  In the case where something happens to site A, losing vCenter and/or VR device, you can use vCenter and VR device to site B to perform a recovery after disaster and put in place the VMS to site B, inside of vCenter inventory B.

  (B) If you have no server vCenter in slot 2:

  1. There is no need to deploy handset unit of VR (embedded DB for server VRMS + VR + VRMS) for site B.

  2. you can deploy additional device VR-server only for site B, so that the replication traffic goes directly from the source ESXi to the correct server in VR.

  3. If the disaster arrives at the site, you must have vCenter Server and VRM in the combined unit of VR upward and running order to use the VR UI to perform a disaster recovery. If vCenter Server or VRMS manage warehouses of data target is corrupted/lost, the only way to recover after a disaster is to consolidate recovery replica logs manually rename and replicated configuration files and hope that consolidated records represent a coherent source VM instance. This procedure is subject, not officially supported, and care must be taken when building the redo logs, in order to ensure the consistency of the data in the disks of the virtual machine, not some partial block updates.

  Kind regards

  Martin

• Remote Site Replication

  Hello, I am currently using vSphere 5.1 replication and replication of my production SAN EquilLogic on a little SAN Synology on the same subnet on my local network. I have a data store in my vSphere cluster using iSCSI to Synology for local replication of my VM.

  My company has another office in Seattle that I would use as my recovery site and settle the Synology SAN, so that I do not have the localized replication happening. I am a little confused everything is...

  1. Should I try to keep the connection iSCSI on my WAN link to our Seattle Office that 10mgps on MPLS for the Synology?
     
  2. Or do I need to configure another host of vSphere, tie my Synology and attach it as a remote site in vSphere replication?
     

  Thank you, Eric

  you will probably better use another host using VR because over a 10Mbits/s connection, latency will probably cause the iscsi connection Flake at any given time.

• Secondary base replication error

  I have a problem on one of my client sites that I've not seen before. We are reproducing two Machines protected by one carrot in the other off the coast of the main site. Two checkpoints of the machines create successfully on the nucleus of the host, but a machine falls down during replication. I get a message to halfway through that "an incorrect record was read repository will not be may not be not available." The other machines of replicates correctly. The two shots of machines are stored in the same repository. All have ideas?

  Thank you!

  Hi elspense,

  The best course of action is to open a service request with product support, force a repository check on every deposit on each core and then upload the logs using Aanews to the service request, you have opened.  Support engineer will then reach you on the ticket.  Make sure to note in the service request that newspapers have been downloaded.

  To open a Service request: support.software.dell.com/manage-service-request

  This is how to download the Aanews newspapers: support.software.dell.com/.../117808

  On the core of AppAssure 5:

  Go to C:\Program Files\AppRecovery\Core\CoreService\AAInfo.

  Right-click AAInfo.UI.exe and then click Run as administrator.

  Enter the SR number in the appropriate field, and then click OK.

  Inform the technician of support assigned to your case when the upload is complete.

  Thank you

  Derek

• Unable to see index to display the site replication group

  Hello
  
  I added a few tables and their indexes to a group from the site of master materialized view
  
  I can look in user_repobject to the control of the site and you can see all the tables and indexes
  
  I created and then some views simple fast refresh materialized view site
  
  I do not see the clues that I had added on master site when I am connected to the display of the site
  
  So if I ask materialized views to display the site explain plan does not show that the indexes are available
  
  Is there a process I need to follow to make available on the site to see the main site index?
  
  Any help would be thank you very much
  
  The version of the oracle server is 11.2.0.1
  The customer is 10.2.0.4
  
  Best regards
  
  Patrick

  See http://download.oracle.com/docs/cd/E11882_01/server.112/e10706/reptrouble.htm#i9450
  and
  http://download.Oracle.com/docs/CD/E11882_01/server.112/e10707/rarmanage.htm#i25931

  You should have added the Master_RepObject and call Generate_Replication_Support between the INTERRUPTION / RESUMPTION.
  The actual creation could be pushed through the DBMS_DEFER_SYS.

  You have tasks running in the background? You asked DBA_REPCATALOG to see if the request for creation of the index was pushed and executed?

  (BTW: I did it for the MultiMaster replication.) Not sure if index on MVs are treated in the same way or not really need to be created manually).

  Hemant K Collette

• can we start production on site awaiting replication data at the OS level?

  Hi, I am currently building a backup site. DB version is 11.1.0.7 and aix operating system.
  
  Our team of storage offered to use their replication tool to replicate production on host data watch.
  
  I don't know if it is one another way of RMAN duplicate.
  
  Thank you

  Well then, in the case of the SAN replication you need not to stop your production database as replication will be transparent to the database.

  To test replication works very well and to ensure that the reverse replication product, you will need to stop the database and files etc. systems take it apart before starting the database at the secondary site. Your SAN provider should be able to give details on the procedure.

  However, this kind of strategy DR is more complex than dataguard.

• ACS database does not not after having changed the secondary ip of acs.

  Hello.. Im having 2 ACS 3.1 server. ACS01 (primary) & ACS02 (secondary). We recently moved ACS02 to another site and has changed its ip address.

  When we of database replication from ACS01, we received the error message saying ACS02 has refused the request of replication.

  Any idea what can be the problem?

  Consider these elements when you implement the database replication feature Cisco Secure:

  (1) ACS supports only supported replication of database to other ACS servers. All ACS servers participating in the Cisco Secure database replication must run the same version and patch to FAC level.

  (2) the principal server copy compressed and encrypted the database on the secondary server components. This transmission is done via a connection TCP, Port 2000. The TCP session is authenticated and using an encrypted protocol, Cisco-owners.

  (3) only hosts properly configured, valid ACS can be secondary servers. To add a secondary server, configure it in the AAA servers table in the section of this document Network Configuration. When a server is added to the AAA servers table, the server is displayed for selection as a secondary server in the list of AAA servers as replication partners, on the Cisco Secure database replication page.

  (4) the principal server must be configured as an AAA server and must have a key. The secondary server must have a primary server configured as an AAA server and its key for the primary server must match the key primary servers.

  (5) secondary servers replication takes place sequentially in the order listed in the replication list under replication partners, on the Cisco Secure database replication page. (6) the secondary server that receives the replicated components must be configured to accept replication of database from the primary server. To configure a secondary server for database replication, refer to configuring a secondary Cisco Secure ACS Server of this document section.

  (7) ACS does not support two-way replication of database. The secondary server, which receives the replicated components, check that the primary server is not on its list of replication. If this is not the case, the secondary server accepts replicated components. If so, it rejects the components.

  (8) to replicate the seller of RADIUS defined by the user and the configurations of the specific attribute (VSA) provider successfully, definitions have to be replicated must be identical on the primary and secondary servers. This includes seller RADIUS slots occupy sellers RADIUS defined by the user. For more information on the sellers of the RADIUS and the VSA attributes defined by the user, see section User-Defined RADIUS vendors and VSA sets the document Cisco Secure ACS database command-line Utility.

• vSphere 5.8 and 6 replication

  Hello

  I'm running a vCenter 6 on a site and my secondary site a vCenter 5.5

  I would like to know if I can connect with replication of vSphere. I know vrm 6 is not compatible with vcenter 5.5 and 5.8 vrm is not compatible with vcenter 6

  But vrm vrm-compatible 5.8 6?

  THX in advance for the answer.

  Cyril

  The only support is to upgrade your vcenter seconday to 6.0, and then upgrade your VRM on this site to 6.0/6.1

  * vSphere 5.8 replication only supports vCenter server 5.1 to 5.5

  * vSphere 6.0/6.1 replication support only vCenter Server 6

  * vCenter Server 6.0 Update 1 supports only vSphere 6.1 replication

  I've only seen problems when leaving a VRM on an older version of replication failures, connections between interrupted VRM and so forth, I don't think that same mixed VMware supported versions of VRM.

• Can we use Amazon AWS as VMWare Site Recovery?

  Hello

  I hope I'm asking that this issue will be upset fellows from VMware.  My boss decided to use Amazon AWS as a Cloud Service (it's totally beyond me even if I disagree).

  Is just wonder possible for us to put in place a recovery Site disaster in Amazon AWS?  If not, I can make a proposal to make use of our secondary site as DRS and make use of VMware software and skills.

  Your opinion is requested.

  Thank you

  Zerto using you can use AWS as a disaster recovery site, take a look: http://www.zerto.com/solutions/use-cases/replication-disaster-recovery-solutions-dr-software/

• WebClient problem with application of PSC & VCS on several sites navigation

  Hi all

  I just deployed a VC6 environment nine which consist of two sites. I wanted to set up separate server of VC + PSC external instances on each site where the PSC share a common domain, so actually two PSC replicate information between them and the VC is connected individually to each site of the PSC.

  My main site seems to work quite well when I connect here via the webclient service, but on the second site, I am unable to navigate correctly anything (again via the webclient service). Sometimes I get error messages that http://localhost:10080 / invsvc is not available, and in the "Administration" tab I have no access to anything although I already gave my account permissions. The only thing I get in return is the message "you do not have the permissions to view this object or the object does not exist".

  After some hassles around this question, I tried to redirect the second server of VC to the PSC for the first site which effectively solved the problem, but when I went back the secondary VC to its planned secondary PSC, the problem came back immediately. Now, I also noticed that this occurs only when I sail the second VC with specific accounts. I have no problem while browsing on the environment with the integrated [email protected] or even the domain administrator account from my own internal ad "[email protected]", but if I connect with my own credentials for the administrator, the problem seems to persist. I temporarily assigned my user account AD for the two VC with all permissions and I have had no problem of navigation on both sites.

  Also I don't know if it is a problem related to AD nested groups (I'm delegating access through security usually groups in my VC servers), but I could not navigate the webclient even service correctly after that I assigned my own account directly to instances of VC. Yet once again, this only happens on the secondary site. I gave my has all the necessary permits for the two VC and I have no problem to go them the webclient primary VC, but it is just go right through the second Victoria Cross.

  To me, this seems to be some sort of bug PSC or WebClient. I've tried the individual VC via the regular vSphere navigation c# client and there is no problem with permissions at all, so, actually, that I access granted.

  My environment is based on 100% windows and VMware share consist of several individual components such as PSC and VCS instances deployed on separate VMS on each site (so 4 VM altogether). I have 2 domain controllers in each site with healthy replication and currently I use SQL server databases 2014 hosted directly on instances of the VC.

  Any help would be much appreciated.

  Thank you.

  Update - has worked with support today and they had me spend my Source of the identity of 'Active Directory' (Windows integrated authentication), "Active Directory as an LDAP source ' problems went. Next week, I'll add another remote site to test and see if everything still works.

• Restore with replication of vSphere

  Hello

  We use SRM 5.1 with replication of vSphere.

  I'm trying to get a rough idea of how long a reprotect operation would take after a failover, especially synchronization of storage.

  The manual says that:

  
  "The full synchronization that appears especially in the stages of recovery performs control totals, and only a small amount of data is transferred over the network."

  However in my testing this step still seems to take a long time to complete.  For a person of 50 GB, it takes 40 minutes.  My question is: what is the bottleneck here and I can speed things up?

  In a live scenario, I have much larger comments VMs and I fear that a reprotect could take days to synchronize the storage.

  Thank you

  Steve

  The full synchronization bed basically just for the disk data and checksum data. It also makes requests to read the data and return a set of checksums remotely. He would only send the data if the checksums do not match. Thus, assuming that not many disk changed, there is very little except checksum travel over the network. So you will respect especially how fast you can read files vmdk on both sites and to a lesser extent by the latency of the network between the sites, and, of course, if the link between the sites remains upward.

  Check if the link to the sites is good. Get often ignored or not connections are limited somehow? The latency is extremely high, as hundreds of milliseconds? This can slow things down.

  On the source site, make sure that the storage is not overloaded with other work. In the case of NAS/ISCSI, check also that there is no other work of network hogging bandwidth. Sometimes, there are periodic offers on secondary sites, like backups, and that people often forget this can be a lot of resources.

  On the destination site, carry out similar checks and make sure that the server VR is to get a reasonable amount of network and CPU resources.

• vSphere replication ports

  Hi guys

  We will be deploying vsphere replication between 2 sites that are geographically far apart.

  My question is to confirm if only this 2 ports must be open for replicatio to work?

  Port of 44046 31031

  any other port?

  I found this for Site Recovery manager

  http://pubs.VMware.com/SRM-51/index.jsp?topic=%2Fcom.VMware.SRM.install_config.doc%2FGUID-019985CE-1024-47B0-80AF-B96D1837916A.html

  

  Thank you very much

  Hello

  This is the same topic as part of vSphere documentation Replication - http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.replication_admin.doc/GUID-88B96DAB-8389-40A5-849B-D94ED5A3C4AD.html - in case you are using vSphere replication without SRM.

  The ports listed by you are for replication traffic and the source host must have access to these ports on the secondary site server VR devices to send deltas of the replica.

  VRMS uses the reverse proxy Server vCenter and management traffic to the other VRM through port 80 between the tunnels sites.

  In order to have 31031, 44046 ports and port 80 should be sufficient.

  I have not checked the c# Client UI SRM - I see that direct access to the port remote VRM 8043 was explicitly mentioned. It might be useful to check if it is really necessary in 5.1.

  The plugin of vSphere in vSphere client Web replication does not need to directly access the 8043 remote site port, it uses the vCenter Server proxy port 80.

  Kind regards

  Martin