XenServer 6. Arcserve Support. Search For Articles.. Preferred Language. Arcserve RHA. Arcserve RHA -
|Published (Last):||14 August 2018|
|PDF File Size:||14.33 Mb|
|ePub File Size:||7.12 Mb|
|Price:||Free* [*Free Regsitration Required]|
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in i a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or ii a separate confidentiality agreement between you and CA.
Notwithstanding the foregoing, if you are a licensed user of the software product s addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Copyright CA. All rights reserved.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. At arcserve. This document contains the following information relating to use of the CA ARCserve RHA family of products: New and discontinued features, as well information about how the enhancements made to existing features might affect you Issues discovered after publication that you should know before you use this product A list of the fixes included in this release For similar information about previous releases, see the corresponding Release Summaries located on the Support site.
Go to support. Click Product Documentation from the Get Support box. Select the current version from the Select a Release list. Click Go. A list of document titles is displayed. Download the Release Notes for the desired service pack. Chapter 1: Welcome 7. When you have multiple alias names, you can select either a few or all alias names for switchover. Then after switchover, the network adapter of the newly created virtual machine fails to map to the correct NIC. The failure to start is caused by a system exception related to winhv.
The workaround is to remove the Hyper-V role on the master server and synchronize again. If you do not see a specific fix listed in this section, please contact CA Support for more information.
You can select the backup host and its virtual machines. You can create any topology for a Full System scenario to make it flexible even if the appliance hosts are at different virtual platforms. Each appliance host has its own virtual platform and virtual machine settings and you can specify these settings separately. For manual switchover, you can choose which replica to be switched over to.
The engine discovers and replicates even if the BOLB data is stored in locations other than the database files. The root directory also adjusts automatically according to the BLOB data path. You can now select Hyper-V 3.
Make sure that the virtual platform also supports the UEFI firmware. Both the master and replica support dynamic disks. RHA supports 4K sector size hard disk on the following operating systems. RHA engine now monitors all the services for each oracle database instance. You can now select multiple instances on the "Select Oracle Instances for Replication" screen while creating a scenario. RHA also lets you specify "sys as sysdba" to log in to the database.
You can also set network adapters using the GUI. Full System Scenario Template with Predefined Replica Details: The Full System scenario template is enhanced to let you include replica details while creating the template.
This created template has the predefined replica details that you can use multiple times to create scenarios. When you create the scenario, just specify the master server details and reuse the predefined replica details.
Any newly created VM backup folders are also replicated. Only the folders of the unchecked virtual machines are excluded. Those folders are marked as excluded folders. If you do not select this option, only the selected backup folders are replicated.
Improved Scenario Authentication and Multitenancy Support: The scenario authentication is improved and is more secure. This allows you to have a very secure multitenancy replication. ARCserve RHA verifies the following conditions at the beginning and stops the scenario when these conditions fail. Scenario level credentials for each host. Host level credentials for each host. The host level credentials override scenario level credentials.
If the host level credential is blank or is not set, then RHA automatically uses scenario level credentials. User has Full Control Permission to the specified parent folder. This option lets you log on to the CS Control Service using the current account you logged in with. You can set mail server, submission port, user credential, and proxy settings. This behavior occurs during the process of upgrading the Engine.
The upgrade process should stop running scenarios and then restart the running scenarios after the upgrade process completes. However, the upgrade process interprets the running scenarios as having new user name and passwords in error , which prevents the upgrade process from restarting the scenario automatically.
To correct this problem, manually start the scenarios that were running before the upgrade started using Run, after the upgrade process completes. Use the Run control from the user interface. Close the interface.
Relaunch the interface. The interface arrangement is returned to the default layout. To avoid this, use a Domain Admin account to access the Control Service. When you use the Switch Computer Name redirection method on computers running Windows Server R2, manually rejoin the Master server to the domain after failover. After 72 hours, the bare metal machine will reboot automatically applicable for full system scenarios.
When you boot the bare metal machine after recovery, some drivers may be missing. Manually install these drivers. When you upgrade the RHA engine, all existing bookmarks and rewind points are lost.
During replication, the target files may fail to open on the Replica server, causing errors. This is because: The Replica local admin account is overwritten by the Master local admin account in the Master database. To avoid this problem, use SQL authentication or switch computer name redirection method.
Depending on your Windows license type, you may need to reactivate your virtual machines after Full System Assured Recovery or switchover. Visit the Microsoft website for more information about reactivation policies. In "mixed environments" in which supported and unsupported versions of ESX are managed by a vcenter Server, full system scenarios may fail because VMDK cannot be mounted on the appliance specified.
To avoid this situation, verify all versions of ESX in your environment are supported. When performing a restore process for a Full System scenario, manually stop the application services on the Master or that application may become corrupt after restore.
If the application is corrupted after a restore, stop the application services, restore to the same bookmark again to solve the problem. While synchronizing a Full System scenario if you get the "Access is denied" message, then consider the following points: Use the Volume synchronization instead of the File or Block synchronization. Set engine service logon account to Local System. The error could be because the master engine service logon account is local or domain administrator. The address of the license server is not in the proxy bypass list.
The proxy requires authentication to access the website. The Windows account does not have the required privileges to access the proxy, which means the current MMC user is not authorized to use the proxy. Authorize the current user to access the HTTP proxy server. Note that the MMC connects to the Control Service with Windows Internet Configuration automatically; this setting can be changed by third-party applications. For applications that require data integrity between data sets, all data must be hosted on a single volume.
Linux For any file operations on the root directory of the master, you must either disable SeLinux or change the SeLinux security context. Microsoft Windows When a Replica server is Windows and the Master server is Windows or higher, you can get the following error. Otherwise, the machine fails to boot. You can find the detailed steps in engine logs of each hosts. For Hyper-V HA Scenarios When the protected VM has multiple network adapters connected to different virtual switches and you choose to customize the IP address using network mapping, the following problem may occur after switchover.
The network adapters in the VM are connected to wrong virtual switches at the Hyper-V replica and the network of the VM may not work properly. To resolve this issue, manually change the virtual switch for each network adapter in the virtual machine setting using the Hyper-V Manager. Otherwise, the r Note: This Service Pack does not support upgrade from r This feature not only restores data but also builds the bare metal machine by installing the operating system, applications, and other necessary components.
For example, you can have a setup where the Master is behind a NAT device whereas the Control Service and Replica are on a public domain.
Arcserve RHA - 16.5 - Software Compatibility Matrix
Arcserve Replication and High Availability r16.5 General Availability Announcement
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in i a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or ii a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product s addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.
Replication r16 Product Brief Eng:Layout 1 - ARCserve
CA ARCserve Replication and High Availability. r16.5 Release Notes