Veritas Desktop and Laptop Option 9.2. High Availability (HA) with DLO

Transcription

1 Veritas Desktop and Laptop Option 9.2 High Availability (HA) with DLO

2 2 Veritas Desktop and Laptop Option The software described in this document is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Legal Notice Copyright (c) 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Veritas product may contain third party software for which Veritas is required to provide attribution to the third party ( Third Party Programs ). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Veritas product for more information on the Third Party Programs. This Veritas product may contain open source and other third party materials that are subject to a separate license. Please see the applicable Third Party Notice at The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement. Veritas Technologies LLC 500 East Middlefield Road Mountain View, CA

3 3 Technical Support Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within the company to answer your questions in a timely fashion. Our support offerings include the following: A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services For information about our support offerings, you can visit our website at the following URL: All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy. Contacting Technical Support Customers with a current support agreement may access Technical Support information at the following URL: Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available: Product release level Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Router, gateway, and IP address information Problem description: Error messages and log files Troubleshooting that was performed before contacting Technical Support Recent software configuration changes and network changes

4 4 Licensing and registration If your product requires registration or a license key, access our technical support Web page at the following URL: Customer Service Customer service information is available at the following URL: Customer Service is available to assist with non-technical questions, such as the following types of issues: Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Advice about technical support options Nontechnical presales questions Issues that are related to CD-ROMs, DVDs, or manuals Support Agreement Resources If you want to contact us regarding an existing support agreement, please contact the support agreement administration team for your region as follows: Worldwide (except Japan) Japan CustomerCare@veritas.com CustomerCare_Japan@veritas.com

5 Contents Contents Technical Support... 3 Contacting Technical Support... 3 Licensing and registration... 4 Customer Service... 4 Support Agreement Resources... 4 High Availability with DLO... 6 Assumptions for HA... 6 DLO SERVER MACHINES... 6 DLO Administration Server Machine... 6 SQL Server Machine... 8 Dedupe Server Machine... 8 DLO IO Server Machine... 8 DLO Edge Server Machine... 9 Storage Location (DLO and Dedupe)... 9 DLO Maintenance Server Machine... 9 Server Sequence for High Availability Configuration... 9

6 6 High Availability with DLO DLO can protect data on machines connected to the DLO Servers that are part of High Availability environment. Assumptions for HA The following are the assumptions: 1. DLO Server machines are configured for HA. 2. Shared disk is available for sharing the data between nodes. 3. Changes done on one node should reflect the changes on another node. DLO SERVER MACHINES DLO Administration Server Machine 1. Update the "DEFAULTMEDIASERVER" information in the setup.ini file which is present in the install path of server <Server install path\dloagent folder> to the DLO Administrator service cluster name, through which both servers are recognized. Example: DEFAULTMEDIASERVER="Cluster1" 2. Update "DEFAULTDATABASESERVER" information in the setup.ini file which is present in the install path of server <Server install path\dloagent folder> to the SQL cluster name. Example: DEFAULTDATABASESERVER="SQLCluster1" 3. Update the below registries entries on DLO Administrator server machine. [HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Veritas DLO\AdminService] "DataPath": This key value should contain the shared disk path where DLO database files are stored. "DBServer"= This key value should contain the SQL cluster name. [HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Veritas DLO\DB] "DBServer"= This key value should contain the SQL cluster name. Note: In case of remote database update the below entries in DLO administrator server machine:

7 7 [HKEY_LOCAL_MACHINE\SOFTWARE\ Veritas\Veritas DLO\RemoteDB] "Remotemdfpath": This key value should contain the shared disk path where DLO database file (DLO.mdf) is stored. "RemoteComputerName": This key value should contain the SQL cluster name. 4. Update the SERVERNAME in the edge server.ini file present in the server install path to the cluster name for the edge server. <Server install path\dloagent folder> <Server install path>\dloagent\certificates> Note: If you are planning to use any other domain specific\ca certificate for edge server communication then refer the section "To change the Server certificate in Edge server" in DLO Administrator Guide. 5. Extract the DLOAgent.zip file present in server install path <Server install path\dloagent folder> and update the below details: Update the "DEFAULTMEDIASERVER" information in the setup.ini file which is present in the install path of server <Server install path\dloagent folder> to the DLO Administrator service cluster name, through which both servers are recognized. Example: DEFAULTMEDIASERVER="Cluster1" Update "DEFAULTDATABASESERVER" information in the setup.ini file which is present in the install path of server <Server install path\dloagent folder> to the SQL cluster name. Example: DEFAULTDATABASESERVER=" SQLCluster1" Update the SERVERNAME in the edge server.ini file present in the server install path to the cluster name for the edge server. <Server install path\dloagent folder> <Server install path>\dloagent\certificates> Note: If you are planning to use any other domain specific\ca certificate for edge server communication then refer the section "To change the Server certificate in Edge server" in DLO Administrator Guide. 6. After updating the above details, zip the DLOAgent folder which is extracted and place it in the DLO Server install path: <Server install path\dloagent folder>

8 8 SQL Server Machine 1. Detach the DLO and Dedupe databases from the SQL instance. 2. Place the DLO (DLO.mdf, DLO_log.ldf) and Dedupe (dedupedb.mdf, dedupedb_log.ldf) database files in the shared disk. 3. Attach the database files(dlo and Dedupe) by running the below commands: osql.exe -E -S SQLCLUSTERNAME\INSTANCENAME -Q "sp_attach_db 'DLO', '<<DLO MDF file path on the shared location>>, <<DLO LDF file path on the shared location>>'" osql.exe -E -S SQLCLUSTERNAME\INSTANCENAME -Q "sp_attach_db 'dedupedb', '<<DedupeDB MDF file path on the shared location>>, <<DedupeDB LDF file path on the shared location>>'" -o "%TEMP%\DedupeDBAttach.log 4. Now restart the DLO Administration Service, Mindtree StoreSmart Dedupe Server Service, and DLO Web Server Service. Dedupe Server Machine 1. Change the ServerName to SQL cluster name in context.xml file in the dedupe server install path: C:\Program Files\Veritas\Veritas DLO\Dedupe Server \Tomcat\ webapps\ DedupeServer\ META- INF\context.xml ServerName = SQL Cluster Name 2. Delete the dedupe server on both the nodes on the dedupe server machines. 3. Add the dedupe server with the cluster name for the dedupe server. DLO IO Server Machine 1. Change the "ServerName" to SQL cluster name in context.xml file in the IO server install path: C:\Program Files\Veritas\Veritas DLO\IOServer\Tomcat\webapps\DLOServer\META- INF\context.xml ServerName = SQL Cluster Name 2. Delete the IO server on both the nodes on the DLO Administrator Console machine. 3. Add the IO server with the cluster name for the IO server.

9 9 DLO Edge Server Machine 1. Delete the Edge server on the DLO Administrator Console machine. 2. Add the Edge server with the cluster name for the edge server. Storage Location (DLO and Dedupe) Create the storage location used for DLO (both DLO and dedupe) in the shared disk. DLO Maintenance Server Machine 1. Add the new maintenance server with the cluster name for the Maintenance Server on the DLO Administrator Console machine. Refer section "Adding a New Maintenance Server" in the DLO Administrator Guide. 2. Now assign the storage location to the new configured maintenance server. Refer section "Reassigning a File Server" in the DLO Administrator Guide. Server Sequence for High Availability Configuration Below is the order for the Servers to be configured for High Availability: 1. Database Server 2. DLO Administration Server 3. Dedupe Server 4. DLO IO Server 5. DLO Edge Server 6. DLO Maintenance Server 7. DLO Administration Server Console