CoBMR Windows Run Book · 2020. 11. 12. · Run Book. 1 salescristiecom issued ul Table of Contents Preamble 2 How to download Cristie CoBMR 2 Getting Started with Cristie CoBMR 2

Cristie Software LtdNew Mill, Chestnut Lane, Stroud, Gloucestershire GL5 3EW, UK.+44 (0)1453 847000 | [email protected] | www.cristie.com | issued: February 2021

CoBMR WindowsRun Book

ii

+44 (0)1453 847000 | [email protected] | www.cristie.com | issued: February 2021

Copyright © 2008-2021 Cristie Software Ltd.

All rights reserved.

The software contains proprietary information of Cristie Software Ltd.; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited.

Due to continued product development this information may change without notice. The information and intellectual property contained herein is confidential between Cristie Software Ltd. and the client and remains the exclusive property of Cristie Software Ltd. If you find any problems in the documentation, please report them to us in writing. Cristie Software Ltd. does not warrant that this document is error- free.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise without the prior written permission of Cristie Software Ltd.

IBM Tivoli Storage Manager (TSM), AIX and TIVOLI are trademarks of the IBM Corporation.

IBM Spectrum Protect is a trademark of the IBM Corporation.

IBM Virtual I/O Server (VIOS) is a trademark of the IBM Corporation.

NetWorker and Avamar are trademarks of the Dell EMC Corporation.

vSphere, vCenter and vCloud are trademarks of VMware Inc.

Hyper-V is a trademark of Microsoft Corporation.

Azure is a trademark of Microsoft Corporation.

Amazon Web Services (AWS) and Amazon Elastic Compute Cloud (EC2) are trademarks ofAmazon.com, Inc.

CloneManager® is a registered trademark of Cristie Software Ltd.

PC-BaX, UBax, Cristie P4VM (Protect for VMs), Cristie Storage Manager (CSM), SDB, ABMR (BareMachine Recovery for EMC Avamar), NBMR (Bare Machine Recovery for EMC NetWorker), TBMR(Bare Machine Recovery for Spectrum Protect/TSM), CBMR (Cristie Bare Machine Recovery),Recovery Simulator (RS) and CRISP (Cristie Recovery ISO Producer) are all trademarks of Cristie Software Ltd.

Cristie Software LtdNew MillChestnut LaneStroudGL5 3EWUKTel: +44 (0) 1453 847009Email: [email protected]: https://www.cristie.com

1


Table of Contents

Preamble 2

How to Download Cristie CoBMR 2

Getting Started with Cristie CoBMR 2

Install the Cohesity Agent 2

Protect Your Server with Cohesity DataProtect 5

Licensing for Cristie CoBMR 6

BMR Recovery using Cristie CoBMR - File Based 6

BMR Recovery using Cristie CoBMR - Block Based 6

Appendix A 10

2


PreambleCoBMR, from Cristie Software Limited, provides bare metal recovery of Windows Desktop and Server O/S when registered as Physical Servers on Cohesity DataProtect. It also supports recovery of Virtual Servers provided they are registered as Physical Servers.

The software currently supports Cohesity DataProtect version 6.3.x, 6.4.x, 6.5.1(a,b) and 6.6.0.

.How to download The CoBMR installation media can be downloaded from the following location:

http://source.cristie.com/download/CoBMR

Getting Started with Cristie CoBMRThere are three stages to the deployment of Cristie CoBMR:

� Install the Cohesity Agent

� Install the Cristie CoBMR backup-side software

� Protect your server with your Cohesity DataProtect

Install the Cohesity AgentIf not already done, install the Cohesity Agent software on the server to be protected. This should be done before installing any Cristie software. Please follow Cohesity recommendations regarding the Component installs: Volume CBT (Change Block Tracker) and/or File System CBT (Change Block Tracker).

Step 1 of 4.

Welcome to the Cohesity agent Setup Wizard

Step 2 of 4.

Select Components and Installation Location

3


The Cohesity Agent software can be downloaded from the Cohesity DataProtect web-interface.

� Select the hamburger menu in the top-left hand corner of the page

� Select Sources

� Select the circled plus symbol on the right-hand side of the screen

� Select Download Cohesity Agent

� Select the agent for Windows from the pop-up Download Agents selection options

Install the Cristie CoBMR softwareOnce the Cohesity Agent has been installed, you can install the Cristie CoBMR software through the suite installer. At the end of the installation detailed machine configuration information is recorded which will be required for a successful BMR recovery. This process can take some time.

Step 3 of 4.

Service Account Credentials

Step 4 of 4.

Completing the Cohesity Agent Setup Wizard

Step 1 of 6.

Welcome to the InstallShield Wizard for CoBMR VA Suite 9.1

4


Step 4 of 6.

Install CoBMR

Step 3 of 6.

Select install component

Step 2 of 6.

License Agreement

5


The configuration information is recorded by an executable named CoBMRcfg.exe, which is located in :\Program Files\Cristie\CoBMR on the Windows System drive. The executable must be run before each backup in order to keep the configuration information up to date. This process can be added to a schedule using Cohesity’s pre-script which is found in advanced settings for the protection job. The executable should be run with Administrator privileges.

Protect your server with the Cohesity DataProtectThe server can now be protected from the Cohesity DataProtect. If not already done, register the server as a Physical Server on Cohesity DataProtect. The registered server should be added to a protection job. Until at least one successful run of the protection job, the server is not protected. When your registered server has been added to a protection job, ensure that all the data on the server is being protected, the default protection is usually just the Windows drive (e.g. C:).

To protect files that are open during back including system files it is important to enable Crash Consistent Backups (File Based backups only)

Step 6 of 6.

Final Product Installation Status

Step 5 of 6.

Installing CoBMR

6


Licensing for Cristie CoBMRCristie CoBMR requires a license. When the product is installed, a trial license is automatically included. This allows the product to be used for a period of 30 days from installation. A trial licence extension will need to be obtained, or a full licence from Cristie Software to continue using the software after the trial period.

BMR recovery using Cristie CoBMR File-based backupsTo perform a CoBMR bare metal recovery from a Cohesity file level backup requires the following:

� A suitable file level backup taken after installing CoBMR

� A CoBMR recovery environment on a CD, ISO or USB device - In most circumstances the Windows Preinstallation Environment (WinPE) 10 based recovery media will be appropriate.

� A target physical or virtual machine – The ‘recovery target ‘

Boot the recovery target from the recovery media, (i.e. CD, ISO or USB device). After a short time, the opening page of the Cristie CoBMR recovery environment will be displayed (See Step 1 below). The exact time from boot to the appearance of the welcome screen depends on the speed of the recovery target and the device booting the recovery media. On physical systems, CD devices can be quite slow.

Step 1 of 11.

The opening page of the recovery environment.

7


Step 5 of 11.

This is the opportunity to decide which disks get partitioned and which partitions or volumes are formatted.

Swap target disks around if the disks that have been automatically assigned need reassignment.

Step 3 of 11.

Enter the IPv4 address or name of Cohesity DataProtect, the credentials needed to access it and the IPv4 address or name of the registered source, which must match the address or name used to register the source originally.

Step 4 of 11.

This is a progress screen, there is no user interaction unless an error occurs.

Step 2 of 11.

This is the opportunity to specify where the log files will be copied to at the end of the recovery. It is a recommended step, but is optional.

8


Step 9 of 11.

This is a progress screen, there is no user interaction unless an error occurs. This shows the data being restored from Cohesity DataProtect.

Step 7 of 11.

This is the opportunity to change the computer name, the hostname or the IPv4 address assigned to each network adapter, that will be assigned to the recovered server when it is rebooted at the end of the recovery.

Step 8 of 11.

Note that the “Next >” button has now changed to “Finish”. Until you select “Finish” no changes have been made to the target machine. Selecting “Finish” will start the recovery process.

Step 6 of 11.

This is the opportunity to decide what data gets restored from the backup.

9


Step 11 of 11. This shows the end of the recovery including the dissimilar hardware stage. Selecting “Finish” at this point takes you back to the welcome screen seen at step 1. The recovery CD+ or USB device should be removed or disconnected from the virtual or physical target and “Reboot” should be selected to boot into the recovered server’s operating system.

Step 10 of 11.

This is a progress screen, there is no user interaction unless an error occurs. This shows the progress when processing the hard-links found in the System State.

10


BMR recovery using Cristie CoBMR Block-based backupsCoBMR block based recoveries utilise a VHD or VMDK to access the underlying disks and for this to happen the recovery environment needs NTFS support. ISOs are not supported in block based Cohesity DR recoveries.

Golden ImagesBoth the VHD & VMDK are persistent across reboots and if the same image is used on other systems for recovery. This means that any changes made (Cohesity Server settings, Clone settings etc) will stay when booted again. For this reason, we recommend keeping an ‘untouched’ copy on a file share, make a copy each time a CoBMR DR recovery is required. If the Golden Image is used in a recovery or missing a new one can be downloaded from the Cristie Portal.

Configure Cohesity to allow access to the viewLog into the Cohesity console and create a new user to access the Cohesity shares for data restore, enable SMB Access token for the user then give the user the Admin role. Below is an example, please set your own username and password. To do this run iris_cli and log in with an admin user/password. Finally set magneto flag to enable physical file restore:

# For a new user “testuser” with a password of “P@ssw0rd”

user add user-name=testuser password=P@ssw0rd primary-group-name=Users

user edit user-name=testuser password=P@ssw0rd allow-smb-access-token=true

user edit user-name=testuser roles=Admin

# Following command is all on one line

cluster update-gflag service-name=magneto gflag-name=magneto_physical_file_restore_try_local_user_for_smb gflag-value=true effective-now=true reason=Enable_local_authentication

Create the Target VM and attach the Cristie CoBMR VHD/VMDK as an additional disk to those that will be recovered.

11


Adding the recovery Image Disks

Microsoft Hyper-V

Add the VHD to an empty IDE controller then boot into this disk.

VMWare vSphere

Import the VMDK to a new Hard disk and boot from it.

Boot VHD on Physical Systems using USB device

‘Burn’ the CoBMR VHD image to a USB using software, e.g. Rufus, then boot from the USB. The Filesystem settings should be picked up automatically, otherwise check that the Filesystem is NTFS.

Boot the recovery target from the recovery media, (i.e. the VHD or VMDK device). After a short time, the opening page of the Cristie CoBMR recovery environment will be displayed (See Step 1 below). The exact time from boot to the appearance of the welcome screen depends on the speed of the recovery target and the device booting the recovery media.

12


Step 3 of 11.

Enter the IPv4 address or name of Cohesity DataProtect, the credentials needed to access it and the IPv4 address or name of the registered source, which must match the address or name used to register the source originally.

Step 4 of 11.

This is a progress screen, there is no user interaction unless an error occurs.

Step 2 of 11.

This is the opportunity to specify where the log files will be copied to at the end of the recovery. It is a recommended step, but is optional.

Step 1 of 11.

The opening page of the recovery environment.

13


Step 7 of 11.

This is the opportunity to decide what data gets restored from the backup.

Step 6 of 11.

This is the opportunity to decide which disks get partitioned and which partitions or volumes are formatted.

Swap target disks around if the disks that have been automatically assigned need reassignment.

Step 5 of 11

The recovery will search for backups available with the kSuccess flag suitable for the recovery, there is no user interaction unless an error occurs.

14


At the end of the recovery shut down the recovery environment, remove the recovery disk from the hypervisor, leaving the local disk attached. Choose the recovered local HDD to boot into the recovered OS.

Step 11 of 11.

This shows the end of the recovery including the dissimilar hardware stage. Selecting “Finish” at this point takes you back to the welcome screen seen at step 1

Step 10 of 11.

This is a progress screen, there is no user interaction unless an error occurs. This shows the data being restored from Cohesity DataProtect.

Step 9 of 11.

Note that the “Next >” button has now changed to “Finish”. Until you select “Finish” no changes have been made to the target machine. Selecting “Finish” will start the recovery process.

Step 8 of 11.

This is the opportunity to change the computer name, the hostname or the IPv4 address assigned to each network adapter, that will be assigned to the recovered server when it is rebooted at the end of the recovery.

15


Appendix AIn order for the Cristie CoBMR recovery environment to function correctly, certain ports must be open between the Cristie CoBMR recovery environment and Cohesity DataProtect Server.

The ports required are as follows:

Cristie CoBMR recovery environment Cohesity DataProtect VSE

Details: Allows the Cristie CoBMR recovery environment utilities to contact the Cohesity DataProtect VSE via HTTPS.

Port: TCP 443

Cristie CoBMR recovery environment Cohesity DataProtect VSE

Details: Allows the Cohesity DataProtect VSE utilities to contact the Cristie CoBMR recovery environment via the Cohesity agent.

Ports: TCP 59999 & TCP 50051

16


Cristie Technical SupportIf you have any queries or problems concerning your Bare Machine Recovery for Cohesity DataProtect product, please contact Cristie Technical Support. To assist us in helping with your enquiry, make sure you have the following information available for the person dealing with your call:

� CoBMR Version Number

� Installed OS type and version

� Any error message information (if appropriate)

� Description of when the error occurs

� All Cristie log files relating to the source or recovery machine. This is very important to help us provide a quick diagnosis of your problem

Contact Numbers - Cristie Software (UK) LimitedTechnical Support +44 (0) 1453 847 009

Toll-Free US Number 1-866-TEC-CBMR (1-866-832-2267)

Knowledgebase kb.cristie.com

Forum forum.cristie.com

Sales Enquiries [email protected]

Email [email protected]

Web www.cristie.com

Support Hours05:00 to 17:00 Eastern Standard Time (EST) Monday to Friday

Out-of-Hours support available to customers with a valid Support Agreement - Severity 1 issues* only

UK Bank Holidays** classed as Out-of-Hours - Severity 1 issues only.

*Severity 1 issues are defined as: a production server failure, cannot perform recovery or actual loss of data occurring.

**For details on dates of UK Bank Holidays, please see www.cristie.com/support/

Cristie Software Ltd. are continually expanding their product range in line with the latest technologies. Please contact the Cristie Sales Office for the latest product range.

Documents

CoBMR Windows Run Book · 2020. 11. 12. · Run Book. 1 salescristiecom issued ul Table of Contents Preamble 2 How to download Cristie CoBMR 2 Getting Started with Cristie CoBMR 2