RECOVERY OF CA ARCSERVE DATABASE IN A CLUSTER ENVIRONMENT AFTER DISASTER RECOVERY

RECOVERY OF CA ARCSERVE DATABASE IN A CLUSTER ENVIRONMENT AFTER DISASTER RECOVERY

Legal Notice This publication is based on current information and resource allocations as of its date of publication and is subject to change or withdrawal by CA at any time without notice. The information in this publication could include typographical errors or technical inaccuracies. CA may make modifications to any CA product, software program, method or procedure described in this publication at any time without notice. Any reference in this publication to non-ca products and non-ca websites are provided for convenience only and shall not serve as CA s endorsement of such products or websites. Your use of such products, websites, and any information regarding such products or any materials provided with such products or at such websites shall be at your own risk. Notwithstanding anything in this publication to the contrary, this publication shall not (i) constitute product documentation or specifications under any existing or future written license agreement or services agreement relating to any CA software product, or be subject to any warranty set forth in any such written agreement; (ii) serve to affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement relating to any CA software product; or (iii) serve to amend any product documentation or specifications for any CA software product. The development, release and timing of any features or functionality described in this publication remain at CA s sole discretion. The information in this publication is based upon CA s experiences with the referenced software products in a variety of development and customer environments. Past performance of the software products in such development and customer environments is not indicative of the future performance of such software products in identical, similar or different environments. CA does not warrant that the software products will operate as specifically set forth in this publication. CA will support only the referenced products in accordance with (i) the documentation and specifications provided with the referenced product, and (ii) CA s then-current maintenance and support policy for the referenced product. Certain information in this publication may outline CA s general product direction. All information in this publication is for your informational purposes only and may not be incorporated into any contract. CA assumes no responsibility for the accuracy or completeness of the information. To the extent permitted by applicable law, CA provides this document AS IS without warranty of any kind, including, without limitation, any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. In no event will CA be liable for any loss or damage, direct or indirect, from the use of this document, including, without limitation, lost profits, lost investment, business interruption, goodwill or lost data, even if CA is expressly advised of the possibility of such damages. COPYRIGHT LICENSE AND NOTICE: This publication may contain sample application programming code and/or language which illustrate programming techniques on various operating systems. Notwithstanding anything to the contrary contained in this publication, such sample code does not constitute licensed products or software under any CA license or services agreement. You may copy, modify and use this sample code for the purposes of performing the installation methods and routines described in this document. These samples have not been tested. CA does not make, and you may not rely on, any promise, express or implied, of reliability, serviceability or function of the sample code. Copyright 2008 CA. All rights reserved. All trademarks, trade names, service marks and logos referenced herein belong to their respective companies.

Table of Contents Installation of CA ARCserve on cluster... 4 Introduction...4 Backup of CA ARCserve Database in a Cluster... 5 Restore CA ARCserve Database in a Cluster... 7 How to recover SQL Express ASDB after DR and OS reboot on MSCS... 10 How to recover SQL server 2000 or 2005 ASDB after Disaster Recovery and OS reboot on MSCS... 10 How to recover SQL Express ASDB after DR and OS reboot on NEC ClusterPro / ExpressCluster... 10

Installation of CA ARCserve on cluster Introduction This paper presents a detailed explanation of how you can back up and restore data using CA ARCserve in a cluster environment. Installation of CA ARCserve Backup in a cluster environment with job failover capability is supported for the following cluster platforms: Microsoft Cluster Server (MSCS) in X86/AMD64/IA64 Windows Server NEC ClusterPro/ExpressCluster for Windows 8.0 NEC ClusterPro/ExpressCluster X 1.0 for Windows CA ARCserve Backup supports the following databases in a cluster environment: Microsoft SQL Server 2005 Express Edition Microsoft SQL server 2000 Enterprise Edition Microsoft SQL Server 2005 Enterprise Edition For more information about how to install CA ARCserve as cluster aware application, see the CA ARCserve Backup for Windows Administration Guide. Ensure that the database is configured as a cluster database for CA ARCserve, all the nodes in cluster should have same CA ARCserve Backup Domain name. After installing CA ARCserve on a cluster, browse the CA ARCserve manager through the Virtual name specified during installation.

Backup of CA ARCserve Database in a Cluster Back up the CA ARCserve Database (ASDB) through cluster virtual node before you back up the physical machine of the active cluster node. 1. For NEC cluster (only SQL Server 2005 Express is supported), all the cluster resources can be browsed through the virtual node. 2. For MSCS, Quorum, SQL and CA ARCserve are separated in a different group. Backup the ASDB through the SQL virtual node (VSQL2) before you perform a full backup.

3. Perform a full backup on the active cluster node (add the active node physical name using client agent) for DR. 4. For One Button DR case, the physical node name on CA ARCserve Manager GUI must not include the IP address. Remove the IP address from the node name if you want to do OBDR for TEST-NEC-2. Note: Ensure DR session is created for the physical node backed up for DR in Restore by session window.

Restore CA ARCserve Database in a Cluster You can restore CA ARCserve Database in a cluster environment; follow the steps provided below to restore the database. Note: The instructions provided below depict CA ARCserve Disaster Recovery for Windows 2003 environment. To restore CA ARCserve Database (ASDB) in a cluster environment: 1. Start the Disaster Recovery for Windows 2003 or windows 2000. For more information about how to start the Disaster Recovery, see the CA ARCserve Backup for Windows Disaster Recovery Option Guide. 2. Verify the Public IP address of the node in the in Advanced Disaster recovery screen. In cluster DR, the backup server name is CA ARCserve virtual server name. If FAILOVER, the DR will continue and cluster node will be restored through the virtual server (Remote DR) If FAILDOWN (cluster node is unavailable), a message box will prompt user to select Local DR to recover current machine

During FAILOVER, all shared disks currently attached to another cluster node (which is active) will not be restored. Note: As the Failover scenario works as remote DR, it is suggested to disconnect the shared disks from the secondary node. If ASDB is SQL Express 2005, the CA ARCserve Backup SQL DR Element session will be restored; If ASDB is SQL Server (2000 or 2005), the CA ARCserve Backup SQL DR element session will not be restored.

During FAILDOWN, all the shared disks and SQL DR element will be restored as shown in the following screen shot. For Recover_DB on FAILDOWN or OBDR case, ASBD sessions cannot be restored automatically. You have to recover ASDB manually after rebooting the server.

How to recover SQL Express ASDB after DR and OS reboot on MSCS To recover SQL Express ASDB after DR and OS reboot: 1. Set the following three resources to do not restart state from the cluster administrator. ARCserve ASDB ARCserve Registry ARCserve HA 2. Remove "ARCserve ASDB" from the ARCserve Registry resource dependencies. 3. Make sure the SQL Express service instance (ARCSERVE_DB) is running. 4. Make sure all CA ARCserve services, except Database Engine service, are running. (DBENG service is paused or stopped because ASDB is not available yet.) 5. Run ca_recoverdb.exe to restore ASDB sessions. Provide the username and password to browse the ARCserve virtual node and backup ASDB. Usually, the username should be cluster domain administrator which is also local administrator on these two cluster nodes. 6. After ASDB recovery finished, add the dependency "ARCserve ASDB" to resource "ARCserve Registry" again. 7. Reset these resources back to Restart state, and bring all the resources online. How to recover SQL server 2000 or 2005 ASDB after Disaster Recovery and OS reboot on MSCS To recover SQL server 2000 or 2005 ASDB after Disaster Recovery and OS reboot 1. Run ca_recoverdb utility to restore the database from CMD by providing the appropriate Host name and SQL database credentials. NOTE: Master and Model databases are restored during DR. How to recover SQL Express ASDB after DR and OS reboot on NEC ClusterPro / Express Cluster To recover SQL Express ASDB after DR and OS reboot: Run ca_recoverdb utility to restore the database from CMD by providing the appropriate Host name and SQL database credentials.