Title Page. Guide. to Migrating a NetVault Smart Client to a Backup Server

Transcription

1 Title Page Guide to Migrating a NetVault Smart Client to a Backup Server

2 Copyrights Guide to Migrating a NetVault Smart Client to a Backup Server Software Copyright 2008 BakBone Software Documentation Copyright 2008 BakBone Software This documentation and its associated software product are copyrighted and all rights are reserved. The distribution and sale of this product are intended for the use of the original purchaser only per the terms of the License Agreement. All other product trademarks are the property of their respective owners. This document may not, in whole or part, be copied, photocopied, reproduced, translated, reduced or transferred to any electronic medium or machine-readable form without prior consent in writing from BakBone Software. THIS PUBLICATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED INTO NEW EDITIONS OF THE PUBLICATION. BAKBONE SOFTWARE MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME. BakBone Software 9540 Towne Centre Drive, Suite 100 San Diego, California

3 3 MIGRATING A NETVAULT SMART CLIENT TO A BACKUP SERVER As part of your disaster preparedness plan you should include the ability to recover your NetVault Server in the event of a major disaster at your primary site. The documented process below will explain the steps necessary to change an offsite Smart Client into a NetVault Server. This NetVault Server may then be used to perform critical restores as needed and get major systems functional. This process requires access to a current NetVault database backup and assumes the group label NVDB. This is not intended as a fail-over or warm standby. The basis for this process is an existing NetVault backup environment where the customer is using VTL as their primary backup storage. With the addition of an offsite Smart Client with an equivalent sized VTL, all backups are duplicated to the off-site Smart Client VTL including the NetVault Database backup. This allows for rapid recovery of the NetVault Server by turning the off-site Smart Client into a temporary NetVault Server. The process requires that the NetVault Server and NetVault Smart Client be running on the same operating system. The same version of the NetVault software is highly recommended and a copy of the current software in use should be available at the off-site location. Additional licensing will be required for the Smart Client and required VTL capacity. The replacement NetVault server will be using an evaluation license as its use will be limited to the amount of time necessary to bring the original NetVault Server back online. The steps outlined below require the current NetVault Server to be nonoperational. If you are running a test simulation you must Stop the NetVault Service before proceeding. The steps necessary to add the off-site Smart Client and VTL are not defined within this document. For assistance in reconfiguring your backup environment to include this functionality please contact your local Bakbone Software sales office. Bakbone Software Customer Support.

4 4 1. Stop the NetVault services on the Smart Client and then copy the diskdevices.cfg file from the NetVault\config directory out to one side (not in the NetVault directory). 2. Then uninstall NetVault using the 'uninstall' script in the NetVault\util directory or add/remove programs for Windows. 3. Install NetVault selecting 'server' during the install. Ensure that the NetVault paths are the same and the NetVault name is the same as the original server. 4. Once the install is completed stop the NetVault services on the newly installed server. You will not need to license the server as it will be running on the 45 day evaluation license. 5. Copy the diskdevices.cfg file from step 1 into the NetVault\config directory (overwriting the existing one). 6. Restart NetVault services and open the main GUI and go to device management. A window will pop up as NetVault will recognize the VTL connected to the server. 7. Once that has been added scan in the tape from the NVDB group (NVDB backups are written to its own media group for ease of knowing which tape to scan). 8. Then go to the restore window and expand the latest NVDB saveset. Select everything except cluster and license keys and then submit the job. 9. When the job is done you will get "plugin died unexpectedly" message. This is normal it's just NetVault shutting down after it's restored itself. 10.Stop the NetVault services and do the following: Rename the newly restored diskdevices.cfg file to diskdevices.server (for user when bringing back online the original NetVault Server). Copy the diskdevices.cfg file back into the NetVault\config directory (as during the restore the old one will have been restored) and also go into the NetVault\db\MediaDatabase\Indexes directory and the NetVault\db\MediaDatabase\Records directory and delete the 'devicetree' file located in both locations. 11.Stop and Restart the NetVault service and re-add the VTL again in device management. At that point all the jobs and users and notification etc should be back. 12.All restores will use the available duplicated media. If backups jobs need to be run the target will need to be changed to the current VTL and the duplication phase will need to be removed.

5 5 Upon recovery of the original or replacement system to be the NetVault server do the following steps. a. Stop the NetVault services on the Smart Client and then copy the diskdevices.cfg file from the NetVault\config directory out to one side (not in the NetVault directory). b. Install NetVault software selecting 'server' during the install. Ensure that the NetVault paths are the same and the NetVault name is the same as the original server. c. Once the install is completed stop the NetVault services on the newly installed server. d. Copy the diskdevices.server file from step 10 above into the NetVault\config directory (overwriting the existing one). (this file will be on the Smart Client Machine) e. Restart NetVault services and open the main GUI and go to device management. A window will pop up as NetVault will recognize the VTL connected to the server. f. Once that has been added scan in the tape containing the NetVault database backup (NVDB). g. Then go to the restore window and expand the latest NVDB saveset. Select everything except cluster and license keys and then submit the job. h. When the job is done you will get "plugin died unexpectedly" message. This is normal it s just NetVault shutting down after it s restored itself. i. Then uninstall the NetVault software on the off-site NetVault Server using the 'uninstall' script in the NetVault\util directory or add/remove programs for Windows. j. Install the NetVault software selecting 'client' during the install. Ensure that the NetVault paths are the same and the NetVault name is the same as the original smart client. k. Once the install is completed stop the NetVault services on the newly installed client. l. Copy the diskdevices.cfg file from step 1(on page1) above into the NetVault\config directory (overwriting the existing one). m. Restart NetVault services on both the newly installed smart client and the original NetVault server. At that point all the jobs and users and notification etc should be back and both the server and smart client should be back to their original state. n. Any backup jobs done on the standby server will need to be scanned in to the NetVault MediaDatabase by scanning the VTL connected to the smart client.

6 6 Migrating a NetVault Smart Client to a Backup Server Important: 1. SVTL is not supported in the above scenario. 2. The evaluation license is valid for 45 days and the time starts when you first install the NetVault Backup Server 3. This process is not to be utilized for migrating to a new NetVault Backup Server. See the following kb article.