emc networker module for meditech 9.1.1 installation ......5 7 9 overview 13 introduction to the...

EMC NetWorker® Module for MEDITECHVersion 9.1.1

Installation and Administration Guide302-003-698

REV 01

Copyright © 2007-2017 Dell Inc. or its subsidiaries. All rights reserved.

Published April, 2017

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND

WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.

Published in the USA.

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC NetWorker Module for MEDITECH 9.1.1 Installation and Administration Guide

5

7

9

Overview 13Introduction to the NetWorker Module for MEDITECH...............................14The NetWorker Module for MEDITECH architecture.................................. 14

Installation and Upgrade 19Installation prerequisites.............................................................................20Host requirements......................................................................................20

Licensing requirements..................................................................20MEDITECH requirements.............................................................. 20Operating system requirements..................................................... 21Array hardware requirements......................................................... 21VNX requirements......................................................................... 22Unity requirements........................................................................ 22Symmetrix VMAX requirements.....................................................22XtremIO requirements................................................................... 23RecoverPoint requirements........................................................... 23

Installing the NetWorker Module for MEDITECH........................................23Uninstalling the NetWorker Module for MEDITECH................................... 24Upgrading the NetWorker Module for MEDITECH..................................... 24

Upgrading from 8.2.x, 9.0.x, or 9.1 to 9.1.1.....................................24Upgrading from 3.0 to 9.1.1............................................................25Reverting to the previous version of the NetWorker Module forMEDITECH.................................................................................... 25

Interface Overview 27The NetWorker Module for MEDITECH interface overview........................28Configure view........................................................................................... 28

Selecting a NetWorker server........................................................29Recover view..............................................................................................30Monitor view............................................................................................... 31Log files......................................................................................................32

Configuration 33Configuration prerequisites........................................................................ 34

General requirements.................................................................... 34VNX configuration requirements....................................................34Unity configuration requirements.................................................. 36Symmetrix VMAX configuration requirements...............................38

Tables

Figures

Preface

Chapter 1

Chapter 2

Chapter 3

Chapter 4

CONTENTS

EMC NetWorker Module for MEDITECH 9.1.1 Installation and Administration Guide 3

RecoverPoint configuration requirements..................................... 38XtremIO configuration requirements............................................. 39

Configuring backups and recoveries........................................................... 40Configuration roadmap.................................................................. 40Configuration tasks........................................................................ 41

Backing up and recovering the configuration file........................................ 52Backing up the configuration file................................................... 52Recovering the configuration file...................................................52

Backups 55Scheduling backups....................................................................................56

ISB................................................................................................ 56IDR................................................................................................ 57IDR In-Frame................................................................................. 57Configuring the scheduled backups............................................... 58Checking the backups status.........................................................59

Viewing the backups status and reports..................................................... 60

Recoveries 63Recovering the ISB data.............................................................................64Recovering the IDR data.............................................................................66Recovering the IDR In-Frame data............................................................. 68Performing redirected recoveries............................................................... 72

Troubleshooting 75Troubleshooting the NetWorker Module for MEDITECH issues..................76

The NetWorker Module for MEDITECH Commands 79Overview of the NetWorker Module for MEDITECH commands.................80nsrmedisv................................................................................................... 80

Command syntax...........................................................................80Command options..........................................................................82

nsrmedirc................................................................................................... 83Command syntax........................................................................... 83Command options..........................................................................83

nwmedi.......................................................................................................84Command syntax........................................................................... 84Command options..........................................................................85

87

91

Chapter 5

Chapter 6

Chapter 7

Appendix A

Glossary

Index

CONTENTS


Revision history............................................................................................................ 9Style conventions........................................................................................................10Supported snapshot and clone methods......................................................................21nsrmedisv command options...................................................................................... 82nsrmedirc command options.......................................................................................83nwmedi command options.......................................................................................... 85

123456

TABLES


TABLES


The NetWorker Module for MEDITECH general architecture......................................15The NetWorker Module for MEDITECH ISB architecture............................................15The NetWorker Module for MEDITECH IDR - local replication architecture................16The NetWorker Module for MEDITECH IDR - remote replication architecture............16The NetWorker Module for MEDITECH IDR In-Fame architecture.............................. 17Configure view........................................................................................................... 29Select the NetWorker server .....................................................................................30Recover view...............................................................................................................31Monitor view............................................................................................................... 31Add Coherency Group................................................................................................ 42Edit Coherency Group................................................................................................ 44Add VNX/Unity storage array.....................................................................................45Add VMAX storage array............................................................................................ 46Edit VNX/Unity storage array.....................................................................................47Edit VMAX storage array............................................................................................ 48Add storage device.....................................................................................................49Edit storage device.....................................................................................................49Add XMS device.........................................................................................................50Edit XMS device......................................................................................................... 51Status of the backups................................................................................................ 60email notification.........................................................................................................61Configure reports....................................................................................................... 62Change time............................................................................................................... 64ISB backed up segments............................................................................................ 65Select target LUN...................................................................................................... 66Change time............................................................................................................... 67IDR backed up segments............................................................................................ 68VNX LUN properties...................................................................................................69Symmetrix VMAX LUN properties.............................................................................. 69Unity LUN properties..................................................................................................70Unisphere - Consistency Group properties................................................................. 70XtremIO LUN properties..............................................................................................71XtremIO Storage Management Application.................................................................72

123456789101112131415161718192021222324252627282930313233

FIGURES


FIGURES


Preface

As part of an effort to improve its product lines, periodic revisions of software andhardware are released. Therefore, all versions of the software or hardware currently inuse might not support some functions that are described in this document. Theproduct release notes provide the most up-to-date information on product features.

If a product does not function correctly or does not function as described in thisdocument, contact a technical support professional.

Note

This document was accurate at publication time. To ensure that you are using thelatest version of this document, go to the Support website at https://support.emc.com.

PurposeThis document describes installation, configuration, backup, and recovery processesfor EMC® NetWorker® Module for MEDITECH.

AudienceThis guide is part of the EMC NetWorker Module for MEDITECH documentation set. Itis intended for use by system administrators during installation and setup of theproduct. Operators who schedule and monitor backups may also find this guidehelpful.

Readers of this guide must be familiar with the following topics:

l EMC NetWorker 9.1.1 client and extended client

l EMC VNX® and VNX management software

l EMC Symmetrix® VMAX® and Symmetrix VMAX management software

l EMC Unity™

l EMC RecoverPoint®

l EMC VPLEX®

l EMC XtremIO® and XtremIO Management System (XMS)

Revision historyThe following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

01 April 28, 2017 First release of this document for the NetWorkerModule for MEDITECH 9.1.1 release.

Related documentationThe NetWorker Module for MEDITECH documentation set includes the followingpublications:

l EMC NetWorker Module for MEDITECH Installation and Administration Guide


https://support.emc.com/

https://support.emc.com/

l EMC NetWorker Module for MEDITECH Release Notes

Special notice conventions that are used in this documentEMC uses the following conventions for special notices:

NOTICE

Identifies content that warns of potential business or data loss.

Note

Contains information that is incidental, but not essential, to the topic.

Typographical conventionsEMC uses the following type style conventions in this document:

Table 2 Style conventions

Bold Used for names of interface elements, such as names of buttons,fields, tab names, and menu paths (what the user specifically selectsor clicks)

Italic Used for full titles of publications that are referenced in text

Monospace Used for:

l System code

l System output, such as an error message or script

l Pathnames, file names, prompts, and syntax

l Commands and options

Monospace italic Used for variables

Monospace bold Used for user input

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces enclose content that the user must specify, such as x or y orz

... Ellipses indicate non-essential information that is omitted from theexample

Where to get helpEMC support, product, and licensing information can be obtained as follows:

Product informationFor documentation, release notes, software updates, or information about EMCproducts, go to EMC Online Support at https://support.emc.com.

Technical supportGo to EMC Online Support and click Service Center. Several options for contactingEMC Technical Support appear on the site. Note that to open a service request, youmust have a valid support agreement. Contact your EMC sales representative fordetails about obtaining a valid support agreement or with questions about youraccount.

Preface


https://support.emc.com

Online communitiesGo to the EMC Community Network at https://community.emc.com for peercontacts, conversations, and content on product support and solutions. Interactivelyengage online with customers, partners, and certified professionals for all EMCproducts.

Your commentsYour suggestions help to improve the accuracy, organization, and overall quality of theuser publications. Send your opinions of this document to [email protected].

Preface


https://community.emc.com

mailto:[email protected]

Preface


CHAPTER 1

Overview

This chapter includes the following section:

l Introduction to the NetWorker Module for MEDITECH...................................... 14l The NetWorker Module for MEDITECH architecture..........................................14

Overview 13

Introduction to the NetWorker Module for MEDITECHThe EMC® NetWorker® Module for MEDITECH 9.1.1 enables you to perform thefollowing tasks:

l Schedule and manage MEDITECH volumes when you use the product with theEMC VNX®, EMC Symmetrix® VMAX®, EMC Unity™, and EMC XtremIO® storagesystems

l Schedule and manage local and remote replicas of MEDITECH volumes when youuse the product with VNX, Symmetrix VMAX, Unity, EMC VPLEX®, XtremIO, andalong with the RecoverPoint storage system

l Integrate NetWorker with the MEDITECH application to perform the scheduledbackups and create disaster recovery replicas of the data without interrupting theapplication

l Integrate the product with MEDITECH Backup Facility (MBF) to take hardware orarray point-in-time snapshots to back up the MEDITECH data to the NetWorkerdevices

l Perform Integrated Serverless Backups (ISBs) of the LUNs that VNX, SymmetrixVMAX, Unity, XtremIO, and RecoverPoint support to a NetWorker device, such astape, Data Domain, and disk

l Perform Integrated Disaster Recovery (IDR) backups to create bookmarks atregular intervals according to the user-defined schedule on a RecoverPointappliance, and validate the bookmarks in the NetWorker Module for MEDITECHGUI

l Perform in-frame point-in-time IDR backups by using the VNX's VNX-SNAP,Symmetrix VMAX's VPSNAP, Unity's VNXe-SNAP, and XtremIO snapshotfeatures

l Perform backups and recoveries in a quick and predictable timeframe

l View the backup and recovery information

l Perform redirected recoveries of ISB data

NOTICE

In this guide, the term XtremIO if not succeeded by the term with RecoverPoint,indicates a native XtremIO array. This guide contains the terms XtremIO and XtermIOwith RecoverPoint according to the context.

The NetWorker Module for MEDITECH architectureThe NetWorker Module for MEDITECH along with the NetWorker client on the proxyhost communicates with the MEDITECH Backup Intermediary (MBI) servers and theVNX, Symmetrix VMAX, Unity, XtremIO, and RecoverPoint systems to performbackups.

The following figures illustrate the general, ISB, IDR, and IDR In-Frame architecturesof the NetWorker Module for MEDITECH respectively.

Overview


Figure 1 The NetWorker Module for MEDITECH general architecture

Figure 2 The NetWorker Module for MEDITECH ISB architecture

Overview

The NetWorker Module for MEDITECH architecture 15

Figure 3 The NetWorker Module for MEDITECH IDR - local replication architecture

Figure 4 The NetWorker Module for MEDITECH IDR - remote replication architecture

Overview


Figure 5 The NetWorker Module for MEDITECH IDR In-Fame architecture

Overview

The NetWorker Module for MEDITECH architecture 17

Overview


CHAPTER 2

Installation and Upgrade

This chapter includes the following sections:

l Installation prerequisites.................................................................................... 20l Host requirements............................................................................................. 20l Installing the NetWorker Module for MEDITECH............................................... 23l Uninstalling the NetWorker Module for MEDITECH........................................... 24l Upgrading the NetWorker Module for MEDITECH............................................. 24

Installation and Upgrade 19

Installation prerequisitesInstall the third-party software according to your requirements. Refer to eachproduct’s documentation for information about how to install the software.

Ensure that you meet the following requirements before you install the NetWorkerModule for MEDITECH:

l You contacted your sales representative to arrange the professional services teamto help you to install the NetWorker Module for MEDITECH and the supportedsoftware.

l You installed and configured the MEDITECH Backup Facility (MBF) on theMEDITECH servers. Contact your MEDITECH representative for directions andsupport to install and configure the MBF utility.

l You created the C:\Program Files\Meditech folder on the NetWorkerModule for MEDITECH proxy host and copied the MBF64.exe file that youobtained from MEDITECH to this folder.

l You installed and configured EMC NetWorker 8.2.x, 9.0.x, or 9.1.x server. Eachversion's installation and administration guides provide information.The latest EMC NetWorker Online Software Compatibility Matrix provides the latestinformation about the supported NetWorker server versions.

l You installed and configured EMC NetWorker 9.1.1 client and EMC NetWorker9.1.1 extended client. The EMC NetWorker Installation Guide and the EMCNetWorker Administration Guide provide information.

l You installed the required software and the EMC storage systems on the proxyhost. See Host requirements on page 20 for the required software. The productdocumentation provides more information.

The NetWorker Module for MEDITECH client communicates with MEDITECHhosts and EMC storage systems from the NetWorker Module for MEDITECHproxy host.

l You exposed the target LUN for the source volume to the proxy host, on whichyou install the NetWorker Module for MEDITECH.In case of XtremIO, for each XtremIO cluster, you configured one initiator group tothe physical proxy host, on which you install the NetWorker Module forMEDITECH.

Host requirementsThe following sections describe host requirements.

Licensing requirementsThe EMC NetWorker Licensing Guide provides detailed information about NetWorkerlicensing.

MEDITECH requirementsThe NetWorker Online Software Compatibility Matrix, which is available at http://compatibilityguide.emc.com:8080/CompGuideApp/, provides the most up-to-dateinformation about supported MEDITECH versions and configurations.



http://compatibilityguide.emc.com:8080/CompGuideApp/


Operating system requirementsThe NetWorker Online Software Compatibility Matrix, which is available at http://compatibilityguide.emc.com:8080/CompGuideApp/, provides the most up-to-dateinformation about supported operating systems and versions.

Array hardware requirementsThe NetWorker Online Software Compatibility Matrix, which is available at http://compatibilityguide.emc.com:8080/CompGuideApp/, provides the most up-to-dateinformation about supported array versions.

The following table lists the array snapshot and clone methods that the NetWorkerModule for MEDITECH supports:

Table 3 Supported snapshot and clone methods

Rollover to a NetWorker device(MBF)

Point-in-time snapshot backup (MBF)

Localarraysupported

Remotearraysupported

Virtualmachinesupported

Localarraysupported



VNX VNX

Clone Yes No Yes SanCopy No No Yes

VNX-SNAP

Yes No No VNX-SNAP

Yes No No

RecoverPoint

Yes Yes Yes RecoverPoint

Yes Yes Yes

Unity Unity

VNXe-SNAP

Yes No Yes VNXe-SNAP

Yes No Yes

RecoverPoint


Yes Yes Yes

Symmetrix VMAX Symmetrix VMAX

Clone Yes No Yes RDF/Clone

No No Yes

VPSNAP Yes No Yes VPSNAP Yes No Yes

RecoverPoint


Yes Yes Yes

VPLEX VPLEX

RecoverPoint


Yes Yes Yes

XtremIO XtremIO


Operating system requirements 21





Table 3 Supported snapshot and clone methods (continued)

Rollover to a NetWorker device(MBF)

Point-in-time snapshot backup (MBF)

Localarraysupported



Localarraysupported



XtremIO Yes N/A Yes XtremIO Yes N/A Yes

RecoverPoint


Yes Yes Yes

VNX requirementsFor the NetWorker Module for MEDITECH to support VNX, install the followingsoftware:

l EMC NetWorker 9.1.1 client

l EMC NetWorker 9.1.1 extended client

l EMC Solutions Enabler 8.2 or later

l EMC Unisphere™ Host Agent

l EMC Navisphere® CLI

l EMC SnapCLI

l EMC Unisphere admsnap

l Windows .NET Framework 4.0

Unity requirementsFor the NetWorker Module for MEDITECH to support Unity, install the followingsoftware:




l EMC Unisphere™ CLI


Symmetrix VMAX requirementsFor the NetWorker Module for MEDITECH to support Symmetrix VMAX, install thefollowing software:



l HBA Adapter and storport Miniport Driver that support EMC Symmetrix VMAX





XtremIO requirementsFor the NetWorker Module for MEDITECH to support XtremIO, install the followingsoftware:





RecoverPoint requirementsFor the NetWorker Module for MEDITECH to support RecoverPoint, install thefollowing software:





Installing the NetWorker Module for MEDITECHYou must install the NetWorker client, NetWorker extended client, and NetWorkerModule for MEDITECH software on the proxy host. EMC recommends that theNetWorker server software reside on a separate host. After you install the NetWorkerModule for MEDITECH software, you must configure the NetWorker Module forMEDITECH proxy host as a client on the NetWorker server.

Procedure

1. Log in as an administrator to the proxy host, on which you want to install theNetWorker Module for MEDITECH.

2. Verify whether the host meets all the requirements that the Host requirementson page 20 section lists.

3. Download the NetWorker Module for MEDITECH 9.1.1 software package fromEMC Online Support (https://support.emc.com) to a folder on the host.

4. Open the folder that contains the NetWorker Module for MEDITECH 9.1.1software package.

5. In the ...\nmmedi911_win_x64\nmmedi folder, double-click the NWMMEDITECH.exe file.

6. On the Welcome to the Setup Wizard page, select I agree to the licenseterm and agreements and click Install.

7. On the Complete the Setup page, click Finish.


XtremIO requirements 23


Uninstalling the NetWorker Module for MEDITECHUninstalling the NetWorker Module for MEDITECH software does not remove theconfiguration file. You can uninstall and reinstall the NetWorker Module forMEDITECH software without re-creating the configuration file.

Procedure

1. On the Windows desktop, select Start > Control Panel > Programs > Uninstalla program.

2. In the Uninstall or change a program window, perform one of the followingsteps:

l Select EMC NetWorker Module for MEDITECH, and then click Uninstall.

l Double-click EMC NetWorker Module for MEDITECH.

3. On the Install Modification page, select Remove and click Remove.


Upgrading the NetWorker Module for MEDITECH

Upgrading the NetWorker Module for MEDITECH includes one of the following tasks:

l Upgrading from 8.2.x, 9.0.x, or 9.1 to 9.1.1

l Upgrading from 3.0 to 9.1.1

Upgrading from 8.2.x, 9.0.x, or 9.1 to 9.1.1

Procedure

1. Log in as an administrator to the proxy host, on which you want to upgrade theNetWorker Module for MEDITECH.

2. Verify whether the host meets all the requirements that the Host requirementson page 20 section lists.

3. Backup the nsr\res\mediconfig.xml file.

4. Upgrade the NetWorker client to 9.1.1, and install the NetWorker extendedclient 9.1.1.

5. Download the NetWorker Module for MEDITECH 9.1.1 software package fromEMC Online Support (https://support.emc.com) to a folder on the host.

6. Open the folder that contains the NetWorker Module for MEDITECH 9.1.1software package.

7. In the ...\nmmedi911_win_x64\nmmedi folder, double-click the NWMMEDITECH.exe file.

8. On the Welcome to the Setup Wizard page, select I agree to the licenseterm and agreements and click Upgrade.





After you finish

If you use EMC Unity, ensure that you respecify the Windows registry setting for theUEMCLI system path. Unity configuration requirements on page 36 providesinformation.

Upgrading from 3.0 to 9.1.1

Procedure

1. Back up the nsr\res\mediconfig.xml file.

You can use the backed up mediconfig.xml file if you revert to the currentNetWorker Module for MEDITECH version from 9.1.1.

2. Either delete or rename the nsr\res\mediconfig.xml file.

3. Uninstall the previous version of the NetWorker Module for MEDITECH.

4. Uninstall the NetWorker client.

5. Install the NetWorker 9.1.1 client and NetWorker 9.1.1 extended client.

The EMC NetWorker Administration Guide provides information.

6. Install the NetWorker Module for MEDITECH 9.1.1.

Installing the NetWorker Module for MEDITECH on page 23 providesinformation.

7. Set up Coherency Group, storage devices, and storage arrays in the NetWorkerModule for MEDITECH Graphical User Interface (GUI).

Configuration tasks on page 41 provides information.

8. Set up the NetWorker client and group in the NetWorker Management Console(NMC).


Reverting to the previous version of the NetWorker Module for MEDITECHProcedure

1. Back up the nsr\res\mediconfig.xml file.

Note

You can use the backed up mediconfig.xml file if you upgrade theNetWorker Module for MEDITECH to the current version.

2. Uninstall the current version of the NetWorker Module for MEDITECH.

3. Install the previous version of the NetWorker Module for MEDITECH.

After you finish

If the NetWorker client does not support the previous version of the NetWorkerModule for MEDITECH, you must uninstall the NetWorker client and the NetWorkerextended client, and then install the relevant previous version of the NetWorker client.


Upgrading from 3.0 to 9.1.1 25

If you revert to a version earlier than 8.2 of the NetWorker Module for MEDITECH,you must use the ISB servers instead of the MBI servers to perform backups andrecoveries.



CHAPTER 3

Interface Overview


l The NetWorker Module for MEDITECH interface overview............................... 28l Configure view................................................................................................... 28l Recover view..................................................................................................... 30l Monitor view.......................................................................................................31l Log files............................................................................................................. 32

Interface Overview 27

The NetWorker Module for MEDITECH interface overviewThe NetWorker Module for MEDITECH user interface contains three views: Configure,Recover, and Monitor.

Note

When you start the NetWorker Module for MEDITECH for the first time, if theconfiguration file mediconfig.xml does not exist, a message that states that youhave not yet created the configuration information appears. To create theconfiguration file, and continue to use the NetWorker Module for MEDITECH, click OKin the message box.

The Recover and Monitor views rely on the selection of a NetWorker server. Thefollowing sections provide you an overview of the views and the tasks that you canperform:

l Configure view

l Recover view

l Monitor view

l Log files

Configure viewUse the Configure view to specify the following features and hardware:

l The Coherency Groups of the MEDITECH MBI servers that you can back up

l The VNX, Symmetrix VMAX, and Unity arrays that the hosts use to store data

l The XMS devices, which are management systems of XtremIO arrays, to enablethe NetWorker Module for MEDITECH to communicate with the XtremIO arrays toperform backups

l The RecoverPoint appliances that the hosts use to store data

Interface Overview


Figure 6 Configure view

Use the Configure view to perform the following tasks:

l Creating (adding) Coherency Groups for MEDITECH hosts

l Editing Coherency Groups

l Removing Coherency Groups

l Adding storage arrays

l Editing storage arrays

l Removing storage arrays

l Adding storage devices

l Editing storage devices

l Removing storage devices

l Adding XMS devices

l Editing XMS devices

l Removing XMS devices

Configuration tasks on page 41 provides information about how to perform thetasks.

Selecting a NetWorker serverSelect a NetWorker server to perform recoveries, and view the backup and recoverjobs in the Monitor view.

Procedure

1. Click the NetWorker server icon in the NetWorker Module for MEDITECH GUI.

The Change NetWorker Server dialog box appears.

Interface Overview

Selecting a NetWorker server 29

Figure 7 Select the NetWorker server

2. Perform one of the following tasks to specify the NetWorker server:

l Specify the NetWorker server in the Server field.

l Click Update Server List.

The process takes a few minutes to update the NetWorker Servers list.

Select the relevant server from the NetWorker Servers list.

3. Click OK.

After you finish

You can view the backup jobs, which you or another user scheduled on the selectedNetWorker server, in the Monitor view. Monitor view on page 31 provides moreinformation.

You can view the segments that the selected NetWorker server backed up in theRecover view. Recover view on page 30 provides more information.

Recover viewUse the Recover view to perform the following tasks:

l Defining a time range to browse the backup segments.

l Selecting a version of the backup segment that you want to recover.

l Selecting a target destination to recover the selected segment.

l Performing the ISB data recovery.

Note

You must manually recover the IDR data. Recovering the IDR data on page 66provides information about how to recover the IDR data.

Interface Overview


Figure 8 Recover view

You can view the segments that the selected NetWorker server backed up. You canchange the server, also to which you or another user backed up the segments. Selecting a NetWorker server on page 29 provides information about how to changethe server.

Monitor viewUse the Monitor view to view the progress of backup and recover jobs.

The job summary includes the unique backup or recover ID, MEDITECH segmentnames, hostnames, and the start and end times of a job. The "Job Details" sectionprovides attributes and values of each job. The Monitor page updates the jobsummary every 30 seconds.

Figure 9 Monitor view

You can view the NetWorker Module for MEDITECH backup and recover jobs thatwere performed on the selected NetWorker server. You can change the server tomonitor the corresponding NetWorker Module for MEDITECH backup and recover

Interface Overview

Monitor view 31

jobs. Selecting a NetWorker server on page 29 provides information about how tochange the server.

The job status icon shows you the status of the job. The job status icons appear to theleft of the job IDs and at the bottom of the window.

Log filesThe NetWorker Module for MEDITECH logs the interface actions and the errormessages in the following files:

l nsrmedisv.rawThis log file enables you to review the backup information. The default location ofthe nsrmedisv.raw log file is C:\Program Files\EMC NetWorker\nsr\applogs.

The NetWorker Module for MEDITECH retains the latest five log files only.

If you want the NetWorker Module for MEDITECH to retain more than five logfiles, create the NSR_MAXLOGVERS environment variable with a necessary value.If you specify a value n, the total number of log files in the C:\Program Files\EMC NetWorker\nsr\applogs folder is n+1. The default value for theNSR_MAXLOGVERS variable is 4. You must restart the host for the change to beeffective from the next backup.

If you want the NetWorker Module for MEDITECH to retain multiple logs in asingle file, create the NSR_MAXLOGSIZE environment variable with a necessaryvalue in terms of megabytes. The default value is 1 MB. After the size of the logfile exceeds the limit that you have set, the subsequent backup creates anotherlog file. However, you can reset the NSR_MAXLOGSIZE environment variablebefore performing backups. You must restart the host for the change to beeffective from the next backup.

l nsrmedirc.rawThis log file enables you to review the recovery information. The default locationof the nsrmedirc.raw log file is C:\Program Files\EMC NetWorker\nsr\applogs.

l nwmedi.logThis log file enables you to review the unresolved error messages. The defaultlocation of the nwmedi.log file is C:\Program Files\EMC NetWorker\nsr\applogs.

There is no limitation on the size of the file. You can delete the file if the file doesnot contain unresolved error messages.

You can set the log level by specifying the following command in the Backupcommand field of the NetWorker Client Properties dialog box:

nsrmedisv -D <log_level>You can set the value of <log_level> to 0 through 9 depending on the amount oflogging you require.

The default value is 0.

Interface Overview


CHAPTER 4

Configuration


l Configuration prerequisites................................................................................ 34l Configuring backups and recoveries...................................................................40l Backing up and recovering the configuration file................................................52

Configuration 33

Configuration prerequisitesConfigure third-party software according to your requirements. Refer to eachproduct's documentation for information about how to configure the software.

Ensure that you meet the requirements in the following sections before you configurethe NetWorker Module for MEDITECH backups and recoveries.

General requirementsEnsure that you meet the following general requirements to perform backups:

l As a system user of the NetWorker Module for MEDITECH proxy host, you are inthe NSR Application Administrators group on the NetWorker server.

l In the NMC, set the following privileges for the system user on the specified host:

n Back up local data

n Monitor NetWorker

n Operate devices and jukeboxes

n Operate NetWorker

n Recover local data

The Application Administrators group typically has these privileges. So, you canadd the system users to the Application Administrators group.

Note

You can add administrator users to the Application Administrators group if youwant to manually perform the operations. Also, you can create an NSR lockbox forthe NetWorker Module for MEDITECH proxy host by using the NetWorkerAdministration GUI to ensure that the backups and recoveries succeed regardlessof the user type—system or administrator. The EMC NetWorker AdministrationGuide provides information about how to create a lockbox.

l When you specify application information variables in the Application informationfield in the Client Properties dialog box of NMC, consider the following steps:

n Include the = symbol between an application information variable name and thevalue of the variable.

n Specify each variable on a separate line.

n Specify the application information variable in uppercase. Otherwise, thebackups fail.

VNX configuration requirementsEnsure that you meet the following VNX requirements to perform backups.

VNX general requirements

l You configured the NetWorker Module for MEDITECH proxy host as a client onthe NetWorker server.

l You created the security file on the proxy host as the Windows SYSTEM user toperform backups by using the NMC:

1. Create a user account, for example, backup or nmmedi on VNX to performbackups.

Configuration


2. Download the PSEXEC.exe file from the Microsoft website.

3. In the path environment variable, specify the path to the PSEXEC.exe file.

4. Run the following command from the command prompt:

PSEXEC -i -s –d CMDThe command starts the SYSTEM command prompt.

Note

If the PSEXEC command does not start the SYSTEM command prompt, run thePSEXEC command from Windows Start > Run....

5. Run the following command to verify whether the command prompt belongs tothe SYSTEM user account:

WHOAMI/USER6. Run the following command in the SYSTEM command prompt to set the global

account for all users on the system:

naviseccli -User <username> -Password <password> -Scope 0 -AddusersecurityUse the username and the password of the account that you created on VNX instep 1.

The command creates the security file.

To set credentials for a specific VNX storage array, run the following command:

naviseccli -User <username> -Password <password> -Scope 0 -Addusersecurity -Address <VNX_IP_address>

7. Run the following command to verify whether you created the security file:

naviseccli -Address <VNX_IP_address> getagentThe VNX information appears which indicates that the procedure has createdthe security file.

Note

You must create the security file as the administrator user to perform backups byusing the CLI.

l You have configured IDR.

VNX CLONE requirements

l You created a storage group for the NetWorker Module for MEDITECH proxyhost.

l You created a clone group for each MEDITECH source LUN (segment) and addedat least one clone LUN to it.

l You exposed the target LUN to the proxy host.

l [Optional] You specified the following application information variables in theApplication information field in the Client Properties dialog box of the NMC:

n EMCCLAR_MAX_CLONE=<Number>where, <Number> is a value 32 through 64 depending on the model of VNX.The default value is 32.

If you specify a value that is less than 32, the value defaults to 32.

If you specify a value that is greater than 64, the value defaults to 64.

Configuration

VNX configuration requirements 35

The EMCCLAR_MAX_CLONE variable enables you to limit the number of LUNsthat you can include in a snapshot in a VNX-SNAP consistency group.

n FRAME_IP=<VNX_IP_address>If you configured multiple VNX arrays in the NetWorker Module for MEDITECHGUI, set the FRAME_IP application information variable with the VNX IPaddress that points to the correct VNX array for successful backups.

VNX-SNAP requirements

l You installed VNX with the 05.32.000.5.206 code or later.

l You copied the snapcli.exe file from C:\Program Files (x86)\EMC\Unisphere Snapcli to C:\Program Files (x86)\EMC\NavisphereCLI.

l You created one consistency group for all MEDITECH source LUNs.

l You manually created only one Snapshot Mount Point (SMP) for each MEDITECHsegment or source LUN, assigned the SMP to the proxy storage group, andrebooted the host.

l You enabled in-band commands from the proxy host to attach snapshots to themount host.

l [Optional] You made the SMP visible and accessible from the proxy host.

l [Optional] You specified the following application information variables in theApplication information field in the Client Properties dialog box of the NMC:

n EMCCLAR_SNAP_SUBTYPE=VNX-SNAPThe EMCCLAR_SNAP_SUBTYPE variable indicates the type of the snapshotthat you use to perform backups.

Note

To perform ISBs by using the VNX-SNAP technology, you must specify thisapplication information variable.

n FRAME_IP=<VNX_IP_address>If you configured multiple VNX arrays in the NetWorker Module for MEDITECHGUI, set the FRAME_IP application information variable with the VNX IPaddress that points to the correct VNX array for successful backups.

Unity configuration requirementsEnsure that you meet the following Unity requirements to perform backups:


l You set the NetWorker Module for MEDITECH proxy host as the snapshot accesshost for all source LUNs.

l You configured Unisphere CLI:In the Configure Optional Settings panel of UEMCLI:

1. Select the Unisphere CLI in the Environment path option.By default, the option is selected.

2. Select the Low (The certificate will not be verified) option to avoid runtimebackup errors.

Configuration


l You created the security file on the proxy host as the Windows SYSTEM user toperform backups by using the NMC:

1. Create a user account, for example, backup or nmmedi on Unity to performbackups.

2. Download the PSEXEC.exe file from the Microsoft website.

3. In the path environment variable, specify the path to the PSEXEC.exe file.

4. Run the following command from the command prompt:

PSEXEC -i -s –d CMDThe command starts the SYSTEM command prompt.

Note

If the PSEXEC command does not start the SYSTEM command prompt, run thePSEXEC command from Windows Start > Run....

5. Run the following command to verify whether the command prompt belongs tothe SYSTEM user account:

WHOAMI/USER6. In the SYSTEM command prompt, run the following command:

uemcli -d <Unity_IP_Address> -u <Unity_Username> -p<Unity_Password> -saveUserUse the username and the password of the account that you created on Unityin step 1.

The command creates the security file.

7. Run the following command to verify whether you created the security file:

uemcli -d <Unity_IP_Address> /prot/snap showThe Unity information appears which indicates that the procedure has createdthe security file. If an error appears, UEMCLI is not correctly set up.

Note

You must create the security file as the administrator user to perform backups byusing the CLI.

l You specified the Windows registry setting for the UEMCLI system path.To ensure that you have a valid path to the Unisphere installation location,manually add a registry entry for NetWorker:

1. From the command prompt or the Windows shell prompt, type regedit.

2. Go to the HKEY_LOCAL_MACHINE\SOFTWARE\Legato\NetWorker folder.

3. Right-click and select New > String Value.

4. Type UEMCLI_directory as the value, and press Enter on the keyboard.

5. Right-click UEMCLI_directory, and select Modify.

6. In the Value data field, type the full path to the Unisphere CLI installationlocation.

Configuration

Unity configuration requirements 37

Symmetrix VMAX configuration requirementsEnsure that you meet the following Symmetrix VMAX requirements to performbackups:

l You have at least one clone or vpsnap LUN per MEDITECH segment.

l You masked the clone or the vpsnap on the NetWorker Module for MEDITECHproxy host.


l You performed one of the following steps:

n You created separate <name>.res files (files with device pairing information),typically in the C:\Program Files\EMC NetWorker\nsr\res\ folder forISB and IDR backups and specified the following application informationvariable in the Application information field in the Client Properties dialogbox of the NMC:SYMM_SNAP_POOL=<Path_to_the_Corresponding_<name>.res_File>This is the recommended step.

n You created the C:\Program Files\EMC NetWorker\nsr\res\<name>.res file.The file must contain the source and target devices from Symmetrix VMAX inthe Symmetrix ID:<Source_Device_ID><Target_Device_ID> format,where the target device is either a clone or a vpsnap. For example,000192601677:0B79 0B7.

For the IDR In-Frame backups, ensure that the number of target thin devices inthe <name>.res file is equal to IDR number + 1. The ISB backups use the extraLUN. The ISB backups fail if you used all the thin devices in the <name>.resfor the IDR In-Frame backups.

l You specified one of the following application information variables in theApplication information field in the Client Properties dialog box of the NMC:

n SYMM_SNAP_TECH=CLONE for clone

n SYMM_SNAP_TECH=VPSNAP for VPSNAP

Note

To perform the IDR In-Frame backups, you must specify theSYMM_SNAP_TECH=VPSNAP application information variable.

The SYMM_SNAP_TECH variable indicates the type of the snapshot that you useto perform backups.

RecoverPoint configuration requirementsEnsure that you meet the following RecoverPoint requirements to perform backups:

l You have the integration role privileges on RecoverPoint 4.0, 4.1, 4.1.1, or 4.1.2.

l You have the admin role privileges on RecoverPoint 4.4, 4.4.1, or 5.0.

l You created the NetWorker Module for MEDITECH Coherency Group thatconsists of all the LUNs that you want to back up as a group.


Configuration


l You use one consistency group per RecoverPoint appliance and add all the LUNsto this consistency group for optimal performance of backups.

l You updated the Windows hosts file with Recover Point IP address.

l [Optional] You specified the following application information variables in theApplication information field in the Client Properties dialog box of the NMC ifeither backups failed or enable image access took a lot of time:

n NSR_NMMEDI_RP_ENABLE_IMAGE_ACCESS_RETRY_COUNT=<value>This application information variable indicates the number of times theNetWorker Module for MEDITECH must try to check whether theRecoverPoint image is enabled.


n NSR_NMMEDI_RP_ENABLE_IMAGE_ACCESS_RETRY_GAP=<value in seconds>This application information variable indicates the time interval that theNetWorker Module for MEDITECH must maintain between two retries to checkwhether the Recoverpoint image is enabled.


n NSR_NMMEDI_RP_RETRIES=<value>This application information variable indicates the number of times theNetWorker Module for MEDITECH must try to check whether theRecoverPoint image is present on the copy, from where rollover is performedduring an ISB.

This application information variable is useful in case of the XtremIO withRecoverPoint workflow because shipping a bookmark can take time thatdepends on the snap replication interval.


The NetWorker Module for MEDITECH supports the following RecoverPointconfigurations:

l Continuous Data Protection (CDP)

l Continuous Remote Replication (CRR)

l Concurrent Local and Remote (CLR) data protection

l Snap-Based Replication (SBR) in case of XtremIO with RecoverPoint

NOTICE

To configure VNX, Symmetrix VMAX, Unity, VPLEX, or XtremIO to use withRecoverPoint to perform the NetWorker Module for MEDITECH backups andrecoveries, refer to the relevant product documentation.

XtremIO configuration requirementsEnsure that you meet the following XtremIO requirements to perform backups:

Proxy on a physical hostIf you installed the NetWorker Module for MEDITECH proxy on a physical host, ensurethat you meet the following requirements:


l You configured only one initiator group per XtremIO cluster.

Configuration

XtremIO configuration requirements 39

To perform ISBs, you must configure the initiator group to the physical proxy. Thisconfiguration enables the NetWorker Module for MEDITECH to map target LUNsduring ISBs. The EMC XtremIO administration guide provides information about howto configure an initiator group to a physical proxy.

Proxy on a virtual machine

If you installed the NetWorker Module for MEDITECH proxy on a virtual machine, youperformed the following steps:

Procedure

1. Identify the source volumes on the XMS device.

2. Create one or multiple consistency groups, as required.

3. Add the source volumes to the consistency group.

4. Take a snapshot of the consistency group, and specify a snap set tag name forthe snapshot.

You can use the snap set tag name as the target.

5. Configure an initiator group on the ESXi server, on which the proxy virtualmachine is present.

6. Map the snapshot volumes to the initiator group.

7. Create a Raw Device Mapping (RDM) of the snapshot volumes to the proxyvirtual machine.

8. Specify the cluster, consistency group, and snapshot information as anapplication information variable in the following format:

SNAPSHOT_REASSIGN=<XMS_IP_address>:<Cluster_Name_1>:<Consistency_Group_Name_1>:<Target_Snap_Set_Tag_Name_1>,<XMS_IP_address>:<Cluster_Name_2>:<Consistency_Group_Name_2>:<Target_Snap_Set_Tag_Name_2>, [...]For example,SNAPSHOT_REASSIGN=10.63.28.51:DPAD_XIO_31_1_C1:NMMEDI_ESX_10.63.97.15_XIO_VM_Proxy:NMMEDI_tag

Configuring backups and recoveriesBefore you configure the NetWorker Module for MEDITECH, install and configure theMEDITECH host and the storage arrays and devices. The following sections describethe configuration tasks.

Configuration roadmapDefine the MEDITECH MBI server and the MEDITECH file servers that you want toback up, and identify the VNX, Symmetrix VMAX, XtremIO, or RecoverPoint systemsthat you want to use to back up the MEDITECH MBI servers.

The NetWorker Module for MEDITECH saves the configuration information of storagearrays, storage devices, and Coherency Groups in the<product_installation_folder>\nsr\res\mediconfig.xml file on theNetWorker Module for MEDITECH proxy host. Performing a backup backs up themediconfig.xml configuration file. If necessary, you can recover the configuration

Configuration


file if either you or another user deletes the file. Backing up and recovering theconfiguration file on page 52 provides information.

Coherency GroupsCoherency Groups are logical groupings of the MEDITECH hosts that you back up atthe same time. NetWorker uses the Coherency Groups for the scheduled backups.

The Coherency Groups enable you to back up multiple segments of multipleMEDITECH hosts at the same time. For example, if you want to back up alladministrative data at the same time, you must create a Coherency Group thatcontains all the MEDITECH MBI servers that contain the information about theadministrative data that exists on the MEDITECH hosts.

The NetWorker Module for MEDITECH creates point-in-time snapshots for all theMEDITECH segments in a Coherency Group, and backs up the snapshots to asecondary device such as, a tape, in case of an ISB.

Storage arraysYou must configure the storage arrays to enable the NetWorker Module forMEDITECH to take snapshots of the VNX, Symmetrix VMAX, and Unity LUNs by usingthe NSM.

NSM uses the configuration information to take snapshots before the ISB backups.After the ISB backups in case of Symmetrix VMAX, NSM resynchronizes the cloneand production LUNs.

Storage devicesYou must configure the storage device, which is a RecoverPoint appliance, to enablethe NetWorker Module for MEDITECH to communicate with it to perform backups.

XMS devicesYou must configure the XMS device, which is a management system of an XtremIOarray, to enable the NetWorker Module for MEDITECH to communicate with theXtremIO array to perform backups.

Configuration tasksConfiguring the NetWorker Module for MEDITECH to perform backups and recoveriesincludes the following tasks:

l Creating a Coherency Group to identify the MEDITECH hosts that participate inthe scheduled backups

l Identifying and configuring the VNX, Symmetrix VMAX, Unity, or XtremIO storagearrays that the MEDITECH hosts use to store the source data

l Identifying and configuring the RecoverPoint appliance storage devices that theMEDITECH hosts use to store the source data

Adding Coherency GroupsProcedure

1. In the NetWorker Module for MEDITECH window, click Configure.

2. Click Add Group.

The Add Coherency Group dialog box appears.

Configuration

Configuration tasks 41

Figure 10 Add Coherency Group

3. Specify the following fields under Coherency Group common parameters:

l Group Name: Type a name for the group of MEDITECH hosts that you wantto back up. The group name can contain up to 64 alphanumeric characters,spaces, underscores (_), and hyphens (-).

l MBI User Name: Type the username of the MBI server, by using which theMEDITECH file servers are configured.

l MBI Password: Type the password of the MBI server, by using which theMEDITECH file servers are configured.

l Confirm password: Re-type the password of the MBI server, by usingwhich the MEDITECH file servers are configured.

l SAN Type: Select the storage array or device—RecoverPoint, VNX, Unity,VMAX, or XtremIO to use for the backup.

The default value is RecoverPoint.

Note

All the hosts in the coherency group must have the same MBI server accountusername and password, and LUNs from same type of storage array becauseSAN type is a common selection for the whole coherency group.

4. Perform and repeat the following steps to add the MEDITECH hosts (MBIservers) to the coherency group:

Configuration


a. Specify the following fields under MEDITECH Hosts:

l MBI Host Name: Type the name of the MBI server.Click Clear to clear the host name.

l MBI Port: Type the port number that you use to communicate with theMBI server.The default port number is 2987.

b. Click the right arrow to add the host to the coherency group.

The hostname and the port number appear in the table.

c. To modify the information of a host:

a. Select the hostname in the table and click the left arrow.

b. Edit the hostname and the port number in the MBI Host Name and theMBI Port fields.

c. Click the right arrow to add the host to the coherency group.


d. Click Verify.

The NetWorker Module for MEDITECH performs the following tasks:

a. Validates the user credentials.

b. Checks whether the MBI server works for all the MEDITECH file servers.

c. Writes the information to the nsr\applogs\nwmedi.log file.

d. Displays a validation message that states whether the specified usercredentials are correct.

Click OK.

e. Click Remove below the table to remove a host from the coherency group.

5. Under Disaster Recovery Options:

a. Select Create Integrated Disaster Recovery Images to back up the IDRimages.

b. In the Number of IDR images to create field, specify the number of IDRimages to be created for the SAN type that you have selected.

l VNX: Specify a value 2 through 48. The default value is 2.

l Unity: Specify a value 2 through 48. The default value is 2.

l VMAX: Specify a value 2 through 32. The default value is 2.

l XtremIO: Specify a value 2 through 120. The default value is 2.

l RecoverPoint: The field does not apply; it is disabled.

Note

You must configure RecoverPoint CDP, CRR, CLR, and SBR by usingeither the Unisphere for RecoverPoint GUI or the RecoverPoint CLIbefore you perform backups.

6. Click OK.

Configuration


Editing Coherency GroupsProcedure


2. In the middle panel, select Coherency Groups.

3. In the right panel, select the Coherency Group that you want to edit and clickEdit Group.

The Edit Coherency Group dialog box appears.

Figure 11 Edit Coherency Group

4. Select a host (MBI server) from the table and click the left arrow.

The information about the selected host appears in the MBI Host Name andMBI Port fields.

5. Edit the values in the fields, as necessary.

6. Click the right arrow to add the modified host to the Coherency Group.


7. Repeat step 3 through step 5 to modify the other hosts in the table.

8. Click Verify.

The NetWorker Module for MEDITECH performs the following tasks:

Configuration


a. Validates the user credentials.

b. Checks whether the MBI server works for all the MEDITECH file servers.

c. Writes the information to the nsr\applogs\nwmedi.log file.

d. Displays a validation message that states whether the specified usercredentials are correct.

Click OK.

9. Click OK.

Removing Coherency GroupsProcedure


2. In the middle panel, select Coherency Groups.

3. In the right panel, select the Coherency Group that you want to remove andclick Remove Group.

The Remove Coherency Group dialog box appears.

4. Click OK.

Adding storage arraysThe storage arrays include VNX, Unity, and Symmetrix VMAX with which theNetWorker Module for MEDITECH communicates to store the MEDITECH data.

Procedure


2. Click Add Array.

The Add Storage Array dialog box appears.

Figure 12 Add VNX/Unity storage array

3. Perform the following steps to add VNX and Unity arrays:

Configuration


Note

Ensure that you have specified the NetWorker server in the NetWorkerModule for MEDITECH window. Selecting a NetWorker server on page 29provides information.

a. Click the EMC VNX/Unity tab.

b. To add a VNX array:

a. Under Storage Type, select VNX.

b. In the VNX/Unity IP Address field, type the IP address of the VNXarray.

c. Click Verify to validate the IP address and the user credentials.

c. To add an Unity array:

a. Under Storage Type, select Unity.

b. In the VNX/Unity IP Address field, type the IP address of the Unityarray.

c. Click Verify to validate the IP address and the user credentials.

d. Click OK.

4. Perform the following steps to add a VMAX array:

a. Click the EMC VMAX tab.

Figure 13 Add VMAX storage array

b. Perform one of the following tasks:

l In the Serial Number field, type the ID of the Symmetrix VMAX array.

l Click Discover to select the required Symmetrix VMAX array.

The process requires a few minutes to complete.

c. Click OK.

Configuration


Editing storage arraysProcedure


2. In the middle panel, select Storage Arrays.

3. In the right panel, select the array that you want to edit and click Edit Array.

The Edit Storage Array dialog box appears.

4. Perform the following steps to edit the VNX and Unity arrays:

a. Click the EMC VNX/Unity tab.

Figure 14 Edit VNX/Unity storage array

b. Edit the values in the fields, as necessary.

c. Click Verify to validate the values.

d. Click OK.

5. Perform the following steps to edit the VMAX array:

a. Click the EMC VMAX tab.

Configuration


Figure 15 Edit VMAX storage array

b. From the Serial Number drop-down list, select the serial number of thearray that you want to use, and click OK.

Removing storage arraysProcedure


2. In the middle panel, select Storage Arrays.

3. In the right panel, select the storage array that you want to remove and clickRemove Array.

The Remove Storage Array dialog box appears.

4. Click OK.

Adding storage devicesThe storage device includes a RecoverPoint appliance with which the NetWorkerModule for MEDITECH communicates to store the MEDITECH data.

Procedure


2. Click Add Device.

The Add Storage Device dialog box appears.

Configuration


Figure 16 Add storage device

3. Specify the following fields:

l Cluster ID: Type the cluster ID of the RecoverPoint appliance.

The cluster ID is either a name or an IP address of a host.

l User Name: Type the username to access the device.

l Password: Type the password to access the device.

l Confirm Password: Re-type the password to access the device.

4. Click Verify to validate the values in the fields.

5. Click OK.

Editing storage devicesProcedure


2. In the middle panel, select Storage Devices.

3. In the right panel, select the device that you want to edit and click Edit Device.

The Edit Storage Device dialog box appears.

Figure 17 Edit storage device

4. Edit the values in the fields, as necessary.

5. Click Verify to validate the values.

Configuration


6. Click OK.

Removing storage devicesProcedure


2. In the middle panel, select Storage Devices.

3. In the right panel, select the storage device that you want to remove and clickRemove Device.

The Remove Storage Device dialog box appears.

4. Click OK.

Adding XMS devicesThe XMS device, which is a management system of an XtremIO array, enables theNetWorker Module for MEDITECH to communicate with the XtremIO array to performbackups.

Procedure


2. In the middle panel, right-click XMS Devices and select Add XMS.

The Add XMS Device dialog box appears.

Figure 18 Add XMS device

3. Specify the following fields:

l IP Address: Type the IP address of the XMS device.

l Username: Type the username that has the administrator role on the XMSdevice.

Configuration


l Password: Type the password of the XMS device.

4. Click Get Initiator Groups to validate the XMS credentials and list the initiatorgroups.

5. From the Select Initiator Group list, select the relevant cluster name andinitiator group, to which the XtremIO array belongs.

Note

The NetWorker Module for MEDITECH supports only one initiator group perXtremIO cluster.

6. Click OK.

Editing XMS devicesProcedure


2. In the middle panel, select XMS Devices.

3. In the right panel, select the device that you want to edit and click Edit XMS.

The Edit XMS Device dialog box appears.

Figure 19 Edit XMS device

4. Edit the XMS credentials.

5. Click Get Initiator Groups to validate the XMS credentials and list the initiatorgroups.

6. From the Select Initiator Group list, select the relevant cluster name andinitiator group, to which the XtremIO array belongs.

Configuration


Note

The NetWorker Module for MEDITECH supports only one initiator group perXtremIO cluster.

7. Click OK.

Removing XMS devicesProcedure


2. In the middle panel, select XMS Devices.

3. In the right panel, right-click the XMS device that you want to remove andselect Remove XMS.

The Remove XMS Device dialog box appears.

4. Click OK.

Backing up and recovering the configuration fileEach NetWorker Module for MEDITECH backup backs up the mediconfig.xmlconfiguration file. Alternatively, you can back up the configuration file by using theNetWorker User program. You can recover the backed up configuration file and usethe file if you lose the actual file.

Note

Recovering the backed up mediconfig.xml configuration file results in theNetWorker Module for MEDITECH configuration settings that are specific to the filethat you are recovering.

Backing up the configuration fileProcedure

1. On the proxy host, select Start > All Programs > EMC NetWorker >NetWorker User.

2. Connect to the NetWorker server that you use to perform scheduled backups.

3. Click the Backup icon.

4. In the left panel, navigate to the folder that contains the configuration file andselect the file.

5. Click Start.

Recovering the configuration fileProcedure

1. On the proxy host, select Start > All Programs > EMC NetWorker >NetWorker User.

2. Connect to the NetWorker server that you use to perform the scheduledbackups.

Configuration


3. Click the Recover icon to browse the files that you or another user backed up.

4. In the left panel, navigate to the folder that contains the configuration file andselect the file.

5. Click Start.

Configuration

Recovering the configuration file 53

Configuration


CHAPTER 5

Backups


l Scheduling backups........................................................................................... 56l Viewing the backups status and reports.............................................................60

Backups 55

Scheduling backupsThe NetWorker Module for MEDITECH software enables you to perform regularbackups of MEDITECH segments. Use the NMC to configure and schedule backups.

The most reliable way to protect the MEDITECH data is to schedule backups of theMEDITECH hosts at regular intervals. You can configure scheduled backups to run atany time.

Scheduled backups save the following items from the NetWorker server:

l Data

l Client indexes

l Bootstrap file

To recover data to MEDITECH host and NetWorker server after the NetWorkerserver's configuration data is destroyed, requires the client indexes and the bootstrapfile.

Scheduling the NetWorker Module for MEDITECH backups is similar to scheduling theNetWorker file system backups. You must define groups, clients, policies, andschedules for the MEDITECH hosts. Always perform a full backup.

Use the following methods to back up the MEDITECH data:

l ISB: The NetWorker Module for MEDITECH backs up the data to the NetWorkerdevices such as tapes, Data Domain, and disks.

l IDR: The NetWorker Module for MEDITECH retains the point-in-time snapshot onthe storage array while indexing the snapshot details in the NetWorker database.You can use the snapshot information when you perform IDR recoveries.

ISBEach backup of MEDITECH is a full backup of a MEDITECH data LUN. The ISBprocess saves the point-in-time images of MEDITECH data to a NetWorker devicethat is configured on a NetWorker storage node. According to the workflow, the ISBprocess resynchronizes the clone with the primary LUN or deletes the snapshots. Thesource and target LUNs must exist on the same type of array.

The NetWorker Module for MEDITECH supports ISBs by using the VNX, Unity,Symmetrix VMAX, XtremIO, and RecoverPoint arrays.

The NetWorker Module for MEDITECH uses the MEDITECH MBF utility to obtain alist of the source LUNs, and quiesce and unquiesce the MEDITECH databases. Youcan see the status of the operations in the NetWorker Module for MEDITECH logs. Ifthe quiesce operation fails, you must run the MBF reset command before you performthe next backup.

Ensure that you meet the following prerequisites to perform an ISB by usingRecoverPoint:

l For RecoverPoint consistency groups in a Snap-Based Replication (SBR)configuration, to ensure better performance of a backup, the shipping time of asnapshot must be less.On the Link Policy tab of the Unisphere for RecoverPoint GUI, you can set theshipping time.

l The image access (consistency group) is not enabled.If the image access is manually enabled, performing an ISB aborts any operationthat is in progress.

Backups


RecoverPoint creates bookmarks in the NMMedi_yyyymmddhhMMss_<GUID> formatand stores the bookmarks at the CDP, CRR, CLR, and SBR sites. You can sortbookmarks by name (timestamp).NMMedi_20151228035612_186c8db1-0000000e-0000103c-5681235c-00020c00-651df529 is an example for a bookmark. The NetWorker Module for MEDITECHcommunicates with RecoverPoint to get the bookmarked data and backs up the datato a NetWorker device.

Note

Multiple independent backups that involve the same MBI host fail when youconcurrently perform the backups. However, this limitation does not apply to XtremIO.

You can view the successfully backed up MEDITECH segments in the NetWorkerModule for MEDITECH GUI and recover these MEDITECH segments.

IDRThe IDR backup enables you to register bookmarks by using RecoverPoint. Thebackup does not save data to a NetWorker device.

RecoverPoint creates bookmarks in the NMMedi_yyyymmddhhMMss_<GUID> formatand stores the bookmarks at the CDP, CRR, CLR, and SBR sites. You can sortbookmarks by name (timestamp).NMMedi_20151228035612_186c8db1-0000000e-0000103c-5681235c-00020c00-651df529 is an example for a bookmark.

The cataloged bookmarks along with the MEDITECH hostname associations appear inthe NetWorker Module for MEDITECH GUI, which provides an option to validate thebookmarks.

The NetWorker Module for MEDITECH supports IDR backups by using theRecoverPoint, VPLEX with RecoverPoint, Unity with RecoverPoint, and XtremIO withRecoverPoint arrays.

IDR In-FrameAn IDR In-Frame backup is a point-in-time snapshot of the MEDITECH segments thatexist on an array. For the backups to succeed, both the source and target LUNs mustexist on the same array. The NetWorker Module for MEDITECH supports IDR In-Frame backups by using the VNX, Unity, Symmetrix VMAX, Compellent, and XtremIOarrays.

Consider the following notes before you perform the IDR In-Frame backups:

l The NetWorker Module for MEDITECH does not support overlap of ISB and IDRIn-Frame backups. However, this limitation does not apply to the backups that useXtremIO.

l In case of Symmetrix VMAX, set the following application information variables inthe Client Properties dialog box:SYMM_SNAP_TECH=VPSNAPSymmetrix VMAX configuration requirements on page 38 provides information.

Backups

IDR 57

Configuring the scheduled backupsUse NMC to configure the MEDITECH data backups and perform the backups. If youwant to perform a file system backup of the proxy host, you must create a clientresource for the host and schedule the backup at a different time.

Perform the following steps if you want to perform the ISB and IDR backups on thesame MEDITECH host and segments:

1. Create a separate Coherency Group for each type of backup on the proxy host.

2. Create separate schedules for each Coherency Group on the NetWorker server.


For example, you can schedule backups every 4 hours, where a backup at midnight isan ISB, and the others are the IDR backups.

Note

Ensure that the ISB and IDR backups do not overlap. If both the backups use the sameMBI server, one of the backups fails. However, this limitation does not apply to thebackups that use XtremIO and RecoverPoint.

Scheduling backupsEnsure that you configured the backup devices before scheduling a backup.


Perform the following steps to schedule a backup:

1. In the NMC, select Enterprise and add NetWorker servers.

2. Right-click a server and select Launch Application.

3. In the NetWorker Administration window, select Protection.

4. Define groups, clients, policies, and schedules specifically for the MEDITECHhosts:

a. Create a group that includes the NetWorker Module for MEDITECH proxy hostconnection information. If you perform both the ISB and IDR backups, create agroup for each backup.

b. Create a client for the proxy server and specify nsrmedisv.exe in the Backupcommand field on the Apps & Modules tab in the Client Properties dialogbox.

c. Update the application information variables in the Application informationfield.

d. Create a save set to identify each Coherency Group for the MEDITECH hoststhat you created in the NetWorker Module for MEDITECH GUI.The syntax of the save set is MEDI:<Coherency_Group>.

Use the following save set to perform a single host backup:

<Coherency_Group>/<Host>For example, medi1/feni4

Use the following save set to perform a single segment backup:

<Coherency_Group>/<Host>/<Segment>For example, medi1/feni4/feni1 E

Assume that you have the following setup:

Backups


l A client/server setup with MBISERVER as the MEDITECH host.

l Three file servers FS01, FS02, and FS03.

l Each file server has two segments each on E and G Drives.

With the specified setup, you can use the save set to perform the followingtasks:

l Back up all the file servers with all the segments.

MEDI:<Coherency_Group> or MEDI:<Coherency_Group>/MBISERVERl Back up only one file server and both the segments.

MEDI:<Coherency_Group>/MBISERVER/FILESERVER*For example, MEDI:<Coherency_Group>/MBISERVER/FS01*

l Back up only one file server and a specific segment.

MEDI:<Coherency_Group>/MBISERVER/FILESERVER DRIVEFor example, MEDI:<Coherency_Group>/MBISERVER/FS02 G

l Back up multiple file servers and multiple segments:

MEDI:<Coherency_Group>/MBISERVER/FILESERVER DRIVE,FILESERVERDRIVEFor example, MEDI:<Coherency_Group>/MBISERVER/FS01*,FS02 E,FS03G

e. Ensure that you specify 0 in the Retries field on the Advanced Options page inthe Policy Action Wizard.

f. Schedule the backup.

NOTICE

If you selected the Concurrent cloning option in the Policy Action Wizard in theNetWorker Administration GUI, the concurrent or immediate cloning starts only afterall the MEDITECH segments of the selected save set are backed up. The concurrentor immediate cloning applies only to the ISB backups.

To view more information about backups, set the debug level to 5 by using one of thefollowing methods:

l In case of a scheduled backup, specify nsrmedisv -D5 in the Backup commandfield in Client Properties dialog box of NMC.

l In case of a manual backup, run the following command:nsrmedisv -s <server_name> -g <save_group> -m <proxy_server_name> -N MEDI:<Coherency_Group> -D5

To back up data to a specific pool by using CLI, run the following command:

nsrmedisv -s <server_name> -g <save_group> -m <proxy_server_name> -b<media_pool_name> -N <save_set_name>

Checking the backups statusAfter you start a backup in the NMC, you can check the status of the backup by usingthe following methods:

l In the NetWorker Module for MEDITECH window, use the Monitor view.

l On the proxy host, check whether the status of the nsrmedisv.exe job isRunning in the Windows Task Manager window.

Backups

Checking the backups status 59

l On the proxy host, open the nsrmedisv.raw file to review the information aboutthe backup job. The default location of the log file is C:\Program Files\EMCNetWorker\nsr\applogs.

Note

Use the nsr_render_log.exe utility to render the log messages for thensrmedisv.raw file. The EMC Support team provides more information aboutthis utility.

l On the NetWorker server, review the logs in either nsr\tmp\policy\<policy_name> or nsr\logs\policy\<policy_name>

After the ISBs complete, the NetWorker Module for MEDITECH resynchronizes theclone and production LUNs regardless of the status of the backups.

Viewing the backups status and reportsUse one of the following methods to view the status of the backups:

l View the status of the NetWorker group in the Policies panel in the NetWorkerAdministration window.

Figure 20 Status of the backups

l Configure NetWorker to email a notification about the status of each completedbackup to the administrators.

Backups


Note

EMC recommends that you configure NetWorker to email a notification only whena backup fails.

Figure 21 email notification

Use one of the following methods to configure NetWorker to email thenotification:

n Use the default notification:

1. In the NetWorker Administration window, click Server.

2. In the left panel, select Notifications.

3. In the Notifications panel, right-click Protection Policy Failure and selectProperties.

4. In the Notification Properties dialog box, perform the following steps:

a. On the General tab, in the Action field, type smtpmail -h mailhost -s <"message"> <user>.

b. Click OK.

n Create a custom notification:

1. In the NetWorker Administration window, click Server.

2. In the left panel, right-click Notifications and select New.

3. In the Notification Properties dialog box, perform the following steps:

a. On the General tab, specify the following fields:

– Name: Type a name for the notification.

– Comments: Type comments that pertain to notification.

– Event: Select the events for the notification.

Backups

Viewing the backups status and reports 61

– Priority: Specify the priority of the notification.

– Action: Type smtpmail -h mailhost -s <"message"> <user>b. Click OK.

Use the NMC to view the MEDITECH groups, clients, and servers reports.

1. In the NMC, click Reports.

2. In the left panel, expand the Policy Statistics folder and select an option to viewthe statistics.

3. In the right panel, on the Configure tab, configure the parameters to include in thereport.

Figure 22 Configure reports

4. Click View Report.

Backups


CHAPTER 6

Recoveries


l Recovering the ISB data.................................................................................... 64l Recovering the IDR data.................................................................................... 66l Recovering the IDR In-Frame data..................................................................... 68l Performing redirected recoveries.......................................................................72

Recoveries 63

Recovering the ISB dataYou can perform only the ISB data recoveries by using the NetWorker Module forMEDITECH GUI. Always contact your MEDITECH HCIS coordinator or the MEDITECHSystems Support Group if you have a problem that necessitates a data recovery. Youmust involve MEDITECH to perform recoveries.

Before you begin

Ensure that you meet the following requirements before you perform a recovery:

l The LUN is a raw disk, that is, the LUN does not have a file system, but is online(accessible and is in the ready state).

l To perform the recovery to the original target LUN instead of another disk, whichdoes not apply to the backups that used either XtremIO or VNX-SNAP:

n You broke the relationship between the source and target LUNs.

n The target LUN is not in a Read Only state.

n The target LUN is a raw disk, that is, the LUN does not have a file system.

l In case of XtremIO and VNX-SNAP, you must use a new LUN to perform therecovery.

Procedure

1. In the NetWorker Module for MEDITECH window, click Recover.

2. Select the NetWorker server that you used to back up data.

Selecting a NetWorker server on page 29 provides information.

3. Click the Browse time icon.

The Change Time dialog box appears.

Figure 23 Change time

The default values are the current date and the current time.

4. Select the date and time either on or before which you performed the latestbackup and click OK.

5. On the Recover page, select the Coherency Group that has the requiredbacked up segments to recover.

The backed up segments appear in the right panel.

Recoveries


Figure 24 ISB backed up segments

You can perform the following optional steps:

l To view the properties of a segment, right-click the segment and selectProperties.

In the LUN Properties dialog box, review the information and click OK.

l To select the specific versions of a segment to recover, right-click thesegment and select Versions.

In the Versions dialog box, select the versions of the required backed upsegments to recover and click OK.

l To retrieve information about the NetWorker volume that contains thebacked up MEDITECH segments, right-click the segment and selectRequired Volumes.

In the Required NetWorker Volumes dialog box, review the details and clickOK.

6. Select the segments to recover.

The selected segments appear in the Recover panel.

7. Right-click the segment in the Recover panel and select Target Destination toselect the destination for the recovery data.

The Select Target LUN dialog box appears.

Recoveries

Recovering the ISB data 65

Figure 25 Select target LUN

8. Perform the following steps in the dialog box:

a. From the Array list, select the array that contains the target LUNs torecover the selected segment.

b. Click Refresh to update the list of LUNs for the selected array.

c. Select the LUNs.

d. Click OK.

9. Repeat step 7 and step 8 for all the segments in the Recover panel.

10. Click Start.

After you finish

l Restart the proxy host.

l Use one of the following methods to view the status of the recoveries:

n In the NetWorker Module for MEDITECH window, use the Monitor view.

n On the proxy host, open the nsrmedirc.raw file to review the informationabout the recovery job. The default location of the log file is C:\ProgramFiles\EMC NetWorker\nsr\applogs.

l If the target LUN is not mounted with the recovered data, perform one of thefollowing tasks:

n Restart the proxy host.

n Check for stale volume GUIDs by using the mountvol /p command, and thenrestart the proxy host.

n Perform recovery to the same LUN.

Recovering the IDR data

NOTICE

This IDR process applies to the VPLEX with RecoverPoint, Unity with RecoverPoint,and XtremIO with RecoverPoint configurations also.

Recoveries


The NetWorker Module for MEDITECH provides the administrative information thatrecovering the IDR data requires. To recover IDR data, you must contact theMEDITECH Systems Support Group for assistance. Always contact your MEDITECHHCIS coordinator or the MEDITECH Systems Support Group if you have a problemthat necessitates a data recovery. You must involve MEDITECH to performrecoveries.

For IDR data recoveries, the NetWorker Module for MEDITECH GUI enables you toonly view the backed up segments and the associated bookmarks.

To view the backed up information by using the CLI, run the following command onthe NetWorker server:

nsrmedirc -s <NetWorker_server> -xThe recovery saves a .csv file with the backup information in the C:\ProgramFiles\EMC NetWorker\nsr\applogs folder.

Procedure

1. In the NetWorker Module for MEDITECH window, click Recover.

2. Select the NetWorker server that you used to back up data.

Selecting a NetWorker server on page 29 provides information.

3. Click the Browse time icon.

The Change Time dialog box appears.

Figure 26 Change time

The default values are the current date and the current time.

4. Select the date and time either on or before which you performed the backupsthat you want to view and click OK.

5. On the Recover page, select the Coherency Group that has the requiredbacked up segments to recover.

The backed up segments appear in the right panel.

Recoveries

Recovering the IDR data 67

Figure 27 IDR backed up segments

6. [Optional] You can perform the following steps:

l To view the properties of a segment, right-click the segment and selectProperties.

In the LUN Properties dialog box, review the information and click OK.

l To select the specific versions of a segment to recover, right-click thesegment and select Versions.

In the Versions dialog box, select the versions of the required backed upsegments to recover and click OK.

7. Right-click the segment and select Validate Bookmarks.

8. Use either the RecoverPoint GUI or the RecoverPoint CLI to recover the image.

The RecoverPoint documents provide information.

Recovering the IDR In-Frame dataTo view the backed up information by using the CLI, run the following command onthe NetWorker server:

nsrmedirc -s <NetWorker_server> -xThe recovery saves a .csv file with the backup information in the C:\ProgramFiles\EMC NetWorker\nsr\applogs folder.

If you are using VNX:

1. Perform steps 1 through 5 that the Recovering the IDR data on page 66 sectiondescribes.

2. Right-click the segment to restore and select Properties.The LUN Properties - IDR In-Frame dialog box appears.

Recoveries


Figure 28 VNX LUN properties

3. From the Snapshot Name field, note down the value.

4. Use either the Unisphere for VNX GUI or the Navisphere CLI to recover the imageby using the snapshot value that you have noted down.The VNX documents provide information.

If you are using Symmetrix VMAX:



Figure 29 Symmetrix VMAX LUN properties

3. From the Clone LUN field, note down the value.

4. Use the relevant Symcli commands to recover the image by using the clone LUNvalue that you have noted down.The Symmetrix VMAX documents provide information.

If you are using Unity:


Recoveries

Recovering the IDR In-Frame data 69


Figure 30 Unity LUN properties

3. From the Snapshot Name field, note down the value.

4. Use one of the following methods to recover the image by using the snapshotvalue that you have noted down.

l Unisphere GUI:

a. In the EMC2 Unisphere GUI, in the left panel, select Block.

b. In the right panel, on the Consistency Groups tab, double-click theconsistency group that contains the LUNs to recover.The <Consistency_Group> Properties dialog box appears.

Figure 31 Unisphere - Consistency Group properties

Recoveries


c. On the Snapshots tab:

a. Select the snapshot to recover.

b. From the More Actions drop-down list, select Restore.

l Unisphere CLI:Run the following command:

uemcli -d <Unity_IP_Address> -u <Unity_Username> -p<Unity_Password> /prot/snap -name <Snapshot_Name> restore

If you are using XtremIO:



Figure 32 XtremIO LUN properties

3. From the Snapshot Name field, copy or note down the volume name and thecluster name.The value in this field is in the following format:

<volume_name>.NMMEDI_snapshot_<cluster_name>_<timestamp_in_ISO_format>

4. Log in to the XMS device and start XtremIO Storage Management Application.

Recoveries

Recovering the IDR In-Frame data 71

Figure 33 XtremIO Storage Management Application

Note

This XtremIO Storage Management Application GUI pertains to XtremIO 4.0.1. TheGUI can vary in different versions.

5. Click the Configuration tab.

6. From the drop-down list, select the same cluster that you have copied or noteddown in step 3.

7. In the left panel, select Volumes.

8. In the right panel, in the text box, paste or type the volume name that you havecopied or noted down in step 3 and click the search button.The volume name and the point-in-time IDR In-Frame snapshots of the volumeappear in the table.

9. In the table, right-click the volume name and select Refresh this volume.The Refresh dialog box appears.

10. On the Select Snapshot page, from the list of snapshots, select the snapshot torecover.

11. Click Finish.

Performing redirected recoveriesYou can perform redirected recoveries of only the ISB data. The following proceduredescribes how to recover the old_client (example client name) data to thenew_client (example client name).

Recoveries


Procedure

1. On the new_client, update the etc\hosts file by using the details of theold_client.

2. On old_server, the server on which old_client is configured, configurenew_client.

3. On old_server, add new_client to the Remote Access list on the Globals (2 of2) tab in the Client Properties dialog box of old_client.

4. On new_client, start the NetWorker Module for MEDITECH by running thefollowing command:

nwmedi -s old_server -c old_client

5. Perform the steps that Recovering the ISB data on page 64 describes.

Recoveries

Performing redirected recoveries 73

Recoveries


CHAPTER 7

Troubleshooting


l Troubleshooting the NetWorker Module for MEDITECH issues......................... 76

Troubleshooting 75

Troubleshooting the NetWorker Module for MEDITECHissues

This section lists the common issues with the NetWorker Module for MEDITECH andprovides workarounds for these issues:

l After you install the NetWorker Module for MEDITECH and start the GUI, an errorscreen appears if you have not installed Solutions Enabler.

Workaround:

Install EMC Solutions Enabler 8.2 or later.

l Unable to find the physical drive information on VNX.

Workaround:

n Check whether the clone LUN is surfaced on the proxy host.

n Check whether the location of the Solutions Enabler bin is in the system path.

n For a detailed error information, review the following Solutions Enabler log file.\Program Files\EMC\SYMAPI\log\symapi-<current_date>.log

l During ISBs, physical drives are not rescanned even after a minute.Workaround:

Increase the rescan waiting period to ideally 120 seconds by specifying thefollowing application information variable in the Application information field inthe Client Properties dialog box of the NMC:

NSR_NMMEDI_DEVICE_REFRESH_WAIT_SECS_VAR=120l The IDR In-Frame backups sometimes fail and report the Error creating

media database entries error in the log file.Workaround:

Ignore the error message because though the IDR In-Frame point-in-timesnapshots do not appear in the NetWorker Module for MEDITECH GUI, theyappear in the array.

l Taking snapshots on an XtremIO array fails and displays the following error:

“ERROR: Snapshot of the cluster <cluster_name> has failed. Snapshot threshold has reached the maximum value. Delete unwanted snapshots to take a successful snapshot.”

Workaround:

1. By using either the show-clusters command on the XMS device or RESTAPI get clusters command, check the total number of volumes (snapshots)and internal volumes (snapshots) that are created by using RecoverPoint. Theinternal volumes are invisible unless you use one of these commands.

2. Delete the unwanted snapshots.

l Sometimes ISBs and IDR backups fail, and the nsrmedisv.log file contains thefollowing message:

Path to uemcli executable not found. Windows Registry entry "UEMCLI_directory" not set.

Workaround:

Troubleshooting


Specify the Windows registry setting for the UEMCLI system path as Unityconfiguration requirements on page 36 describes.

l While adding a Unity array by using the Add Storage Array dialog box, when youclick Verify to validate the IP address and the user credentials, sometimes thefollowing message appears:

You do not have access to perform the requested operation. (Error Code:0x6000001)

Workaround:

Create the user account with necessary privileges as Unity configurationrequirements on page 36 describes.

Troubleshooting

Troubleshooting the NetWorker Module for MEDITECH issues 77

Troubleshooting


APPENDIX A

The NetWorker Module for MEDITECHCommands

This appendix includes the following sections:

l Overview of the NetWorker Module for MEDITECH commands........................ 80l nsrmedisv...........................................................................................................80l nsrmedirc........................................................................................................... 83l nwmedi.............................................................................................................. 84

The NetWorker Module for MEDITECH Commands 79

Overview of the NetWorker Module for MEDITECHcommands

NetWorker Module for MEDITECH commands perform the following functions:

l nsrmedisv backs up the specified MEDITECH data. nsrmedisv on page 80provides information.

l nsrmedirc recovers the specified NetWorker Module for MEDITECH dataobjects. nsrmedirc on page 83 provides information.

l nwmedi starts the NetWorker Module for MEDITECH GUI. nwmedi on page 84provides information.

The nsrmedisv and nsrmedirc commands generate the application logs and savethe logs in the nsr\applogs folder on the proxy server host. The logs arecumulative. The commands append the logs whenever you run the commands.

Review the following list before you run the commands:

l Command options can be either lowercase or uppercase. Many commands includeoptions with both cases.

l Brackets ([ ]) denote optional options and the corresponding values of acommand. Do not include brackets when you type the command to perform abackup or a recovery.

l Data items must follow other command options and parameters in the CLI.

nsrmedisvThe nsrmedisv command backs up the MEDITECH data.

Specify nsrmedisv and the command options in either the Backup command field inthe Client Properties dialog box of NMC, or the CLI depending on the method thatyou use to perform the backup.

Perform the following steps to specify nsrmedisv in the Backup command field:

1. In the NetWorker Administration window, click Configuration.

2. In the left panel, click Clients.

3. In the right panel, right-click the client for the backup and select Properties.

4. In the Client Properties dialog box, perform the following steps:

a. On the General tab, specify the Save set field.

b. On the Apps & Modules tab, specify nsrmedisv and the necessary commandoptions in the Backup command field.

c. Click OK.

Command syntaxThe nsrmedisv command has the following syntax:

nsrmedisv -s server [-qv ] [-b pool] [-c client] [-e date] [-gsave_group] [-m proxy_server_name] [-E pre_processing_script][-N save_set_name] [-P post_processing_script] [-Rbackup_completion_report_file] [-y date]

The NetWorker Module for MEDITECH Commands


To run the preprocessing and postprocessing scripts, you must be either one or all ofthe following users. The security permission for the preprocessing and postprocessingscripts must be any of the following users:

l Backup Operators Group

l Administrators Group

l SYSTEM

Note

The backup succeeds even if the preprocessing script fails.

The -b and -e command options are valid only for manual backups that you performby using the Windows command prompt on a client host. Do not use options when youperform a scheduled backup by using the NetWorker Administration window.

The -e option specifies an expiration date of a save set. If you set the expiration date,the save set is browsable and non-recyclable till the expiration date.

The -e option supports the following types of dates:

l Absolute Date: The format of this date is mm/dd/yy hour:min:sec AM/PM.The default time is 12:00:00 AM.

l Relative Date: The format of this date is [number] unit.where unit is decade, year, quarter, month, fortnight, week, day, hour, minute, orsecond.

You must render the nsrmedisv.raw file by using the nsr_render_log utility.

If you set parallelism to 1, the backup does not start regardless of the priority you set.

You must create the security file as an administrator user if you want to performbackups to VNX by using the CLI. VNX configuration requirements on page 34provides information about how to create the security file.

Use the nsrmedisv command with the preprocessing and postprocessing scriptoptions to perform the following tasks:

l Run the batch files, for example, C:\pre_batch.bat and C:\post_batch.bat.nsrmedisv -s server -g group -m masquerade -b pool -E C:\pre_batch.bat -N save_set_name -P C:\post_batch.bat

l Run the VB scripts as part of the batch file.nsrmedisv -s server -g group -m masquerade -b pool -E C:\pre_vbscript.bat -N save_set_name -P C:\post_vbscript.batwhere the pre_vbscript.bat and post_vbscript.bat files include thecscript <vb_script_name>.vbs entry.

l Run the perl files as part of the batch file.nsrmedisv -s server -g group -m masquerade -b pool -E C:\pre_perlfile.bat -N save_set_name -P C:\post_perlfile.batwhere the pre_perlfile.bat and post_perlfile.bat include the<path_to_perl_interpreter> perl <perl_script_name>.pl entry.


Command syntax 81

Command optionsThe following table lists the nsrmedisv command options:

Table 4 nsrmedisv command options

Command options Descriptions

-s Specifies the NetWorker server to use toperform the backup.

-q Displays nsrmedisv messages in quiet mode.

Only summary information and errormessages appear.

-v Displays nsrmedisv messages in verbose

mode. Verbose mode provides detailedinformation about the progress of the backup.

-b Specifies the device pool.

-c Specifies the NetWorker client to use toperform the backup.

-e Specifies the expiration date of the save set.

Note

Do not use the -e option with the -y option.

Otherwise, the backup fails.

-E Specifies the custom script to run before thebackup starts.

-g Specifies the savegroup. The NetWorkerserver and the savegrp command use the

group parameter to select the media pool.

-m Specifies the NetWorker Module forMEDITECH proxy server.

-N Specifies the NetWorker save set name.

Use the following similar value with the -Noption:

MEDI:medi1/feni4/feni1 E,feni1 F

where:

l medi1 is the name of the group

l feni4 is the name of the MBI server

l feni1 E is the name of the first segment

l feni1 F is the name of the second segment

-P Specifies the custom script that the commandmust run after the backup completes.

-R Generates the backup completion report.



Table 4 nsrmedisv command options (continued)

Command options Descriptions

-y Specifies the retention policy of a backup.

Note

Do not use the -y option with the -e option.

Otherwise, the backup fails.

nsrmedircThe nsrmedirc command recovers the specified MEDITECH data from theNetWorker host. Specify nsrmedirc and the necessary command options in the CLIto perform the recovery.

Command syntaxThe nsrmedirc command has the following syntax.

nsrmedirc [-nqVvxz] [-i {nNyYrR}] [-d destination_directory] [-C storage_array_controller] [-L logical_unit_number] [-Ssave_set_ID or clone_ID] [-s server] [-c client] [-t date] [-ycount] MAGICNAME

Command optionsThe following table lists the nsrmedirc command options:

Table 5 nsrmedirc command options

Commandoptions

Description

-n Disables the recovery to either write or create any files and directories.

-q Specifies quiet mode for logging messages about the progress of therecovery. Only minimal information, including error messages, is written tothe log.

-V Specifies the version number of the NetWorker Module for MEDITECH.

-v Displays nsrmedirc messages in verbose mode. Verbose mode provides

detailed information about the progress of the recovery.

-x Generates a .csv file in the nsr\applogs folder of the NetWorker Module

for MEDITECH IDR save sets. You can import the information in the file to aspreadsheet.

-z Prints a list of the NetWorker Module for MEDITECH save sets. This list issimilar to the output of the NetWorker nsrinfo command.

-i {nNyYrR} Overwrites a response.

-d Specifies a Windows Server physical drive to use as an alternate recoverylocation. The format is -d \\.\<physical_drive_name>.


nsrmedirc 83

Table 5 nsrmedirc command options (continued)

Commandoptions

Description

-C Specifies the storage array name of an alternate recovery destination. Youmust use this option along with the -L option.

-L Specifies the drive number of an alternate recovery destination. You mustuse this option along with the -C option.

If you do not specify any destination options, the command recovers theoriginal data segment. If you use the -d option along with the -C and -Loptions, nsrmedirc ensures that the destinations agree.

-S Specifies the save set ID (SSID) or the clone ID (CLONEID).

You cannot use SSID along with the -C and -L options.

-s Specifies the NetWorker server that was used to perform the backup.

-c Specifies the proxy server client name to use to recover the data.

-t Recovers data according to the specified date. The specified date must begreater than or equal to the backup date. Use the nsr_getdate command

syntax guidelines when you format the date.

-y Specifies the number of save sets that the nsrmedirc -x -z command

output lists.

MAGICNAME Specifies the name of the MAGIC save set in the following format:

MEDI:/<Coherency_Group>/<Logical_Object>

where, the logical objects are the save sets that the nsrmedirc -zcommand output lists.

nwmediThe nwmedi command starts the NetWorker Module for MEDITECH GUI.

Command syntaxThe nwmedi command has the following syntaxes:

l nwmedi [-s NetWorker_server] in case of a general recovery, where a clientname is automatically detected

l nwmedi [-s NetWorker_server] [-c NetWorker_client] in case of aredirected recovery



Command optionsThe following table lists the nwmedi command options:

Table 6 nwmedi command options

Command options Description

-s Specifies the NetWorker server.

-c Specifies the NetWorker client.


Command options 85

GLOSSARY

This glossary contains terms used in this manual.

A

administrator Person who normally installs, configures, and maintains software on networkcomputers, and who adds users and defines user privileges.

B

backup 1. Duplicate of database or application data, or an entire computer system, storedseparately from the original, which can be used to recover the original if it is lost ordamaged.

2. Operation that saves data to a volume for use as a backup.

backup cycle Full or level 0 backup and all the subsequent incremental backups that are dependenton that backup.

backup volume A volume used to store backup data. NetWorker backup data cannot be stored on anarchive volume or a clone volume.

bookmark A label of a point-in-time image that enables you to explicitly identify the image whenyou perform a recovery, for example, while you access image. You must create thebookmarks either manually or by using either the RecoverPoint CLI or the RecoverPointManagement Application.

C

CDP Continuous data protection (CDP) is also known as a continuous backup or a real-timebackup. CDP saves every change you make to the data, captures every version of thedata that you save, and enables you to back up data to any point in time.

client Host on a network, such as a computer, workstation, or application server whose datacan be backed up and restored with the backup server software.

clone 1. Duplicate copy of backed-up data, which is indexed and tracked by the NetWorkerserver. Single save sets or entire volumes can be cloned.

2. Type of mirror that is specific to a storage array.

CLR A RecoverPoint configuration that includes both a CDP and a CRR copy, providingconcurrent local and remote data protection. In RecoverPoint, the CDP copy is normallyused for operational recovery, while the CRR copy is normally used for disasterrecovery.


Coherency Group A user-defined grouping of MEDITECH hosts that will be backed up at the same time.Coherency Groups are defined within the NetWorker Module for MEDITECH interfaceand are referenced when creating a NetWorker save set. See save set.

CRR Continuous Remote Replication (CRR) is a RecoverPoint configuration where data istransferred between two sites over Fibre Channel or a WAN. In this configuration, theRPAs, storage, and splitters exist at both the local and the remote site. This type ofconfiguration provides crash-consistent protection based on the applications writeactivity and enables recovery to specific points in time.

D

data segment A unit of data that can be backed up and recovered. For VNX or Symmetrix VMAXsystems, this is called a Logical Unit Number (LUN).

device 1. Storage folder or storage unit that can contain a backup volume. A device can be atape device, optical drive, autochanger, or disk connected to the server or storagenode.

2. General term that refers to storage hardware.

3. Access path to the physical drive, when dynamic drive sharing (DDS) is enabled.

F

fracture The operation of severing the connection between a production and clone datasegment.

full backup Type of backup that backs up all data objects or files, including the transaction logscontained in databases, regardless of when they last changed. See level.

G

group One or more client computers that are configured to perform a backup together,according to a single designated schedule or set of conditions.

H

host ID Eight-character alphanumeric number that uniquely identifies a computer.

I

I/O device An addressable input/output unit, such as a disk device.

L

label Electronic header on a volume used for identification by a backup application.

Glossary


level Backup configuration option that specifies how much data is saved during a scheduledor manual backup:

l A full backup backs up all data objects or files, regardless of when they lastchanged.

l An incremental backup backs up only data objects or files that have changed sincethe previous backup.

license enabler A code that is required to run a feature or product.

Logical Unit Number(LUN)

A logical unit of storage on either a VNX system or a Symmetrix VMAX system.

M

manual backup Backup that a user performs from the client, also known as an unscheduled, on-demand, or ad hoc backup.

MBF The MEDITECH Backup Facilitator (MBF) is a utility that you use as part of a pre-backup script. The MBF ensures that all the MEDITECH segments are in a consistentand quiesce state before you start the backup.

media Physical storage, such as a disk file system or magnetic tape, to which backup data iswritten. See volume.

N

NetWorker administrator NetWorker server user who may add, change, or delete NetWorker server users.

NetWorker ManagementConsole (NMC)

Software program that is used to manage NetWorker servers and clients. The NMCserver also provides reporting and monitoring capabilities for all NetWorker processes.

NetWorker server Computer on a network that runs the NetWorker server software, contains the onlineindexes, and provides backup and restore services to the clients and storage nodes onthe same network.

NetWorker storage node See storage node.

R

recover To restore data files from backup storage to a client and apply transaction (redo) logsto the data to make it consistent with a given point-in-time.

remote device 1. Storage device that is attached to a storage node that is separate from theNetWorker server.

2. Storage device at an offsite location that stores a copy of data from a primarystorage device for disaster recovery.

remote procedure call(RPC)

Protocol used by the backup server to perform client requests over a network.

Glossary


resource Software component whose configurable attributes define the operational properties ofthe NetWorker server or its clients. Clients, devices, schedules, groups, and policies areall NetWorker resources.

retry mechanism Action that NetWorker software performs when client operations fail. This situationmight occur because the rate of transmission is either low or undetectable.

S

SAN Copy An EMC software feature that enables the copying of data from one location toanother.

save NetWorker command that backs up client files to backup media volumes and makesdata entries in the online index.

save set 1. Group of tiles or a file system copied to storage media by a backup or snapshotrollover operation.

2. NetWorker media database record for a specific backup or rollover.

snapshot Point-in-time, read-only copy of specific data files, volumes, or file systems on anapplication host. Operations on the application host are momentarily suspended whilethe snapshot is created on a proxy host. Also called a PiT copy, image, or shadow copy.

storage array A configuration element in the NetWorker Module for MEDITECH interface that enablesthe proxy server to communicate with the VNX, Symmetrix VMAX, and Unity systemsthat store MEDITECH data.

storage node Computer that manages physically attached storage devices or libraries, whose backupoperations are administered from the controlling NetWorker server. Typically a“remote” storage node that resides on a host other than the NetWorker server.

V

volume 1. Unit of physical storage medium, such as a disk or magnetic tape, to which backupdata is written.

2. Identifiable unit of data storage that may reside on one or more computer disks.

Glossary


INDEX

Aarray hardware requirements 21audience 9

Bbacking up:configuration file 52backing up:IDR 57backing up:IDR In-Frame 57backing up:ISB 56backup:checking status 59backup:scheduling 56, 58backup:viewing status and reports 60

Ccoherency groups:adding 41coherency groups:editing 44coherency groups:overview 41coherency groups:removing 45Command Line Interface:nsrmedirc 83Command Line Interface:nsrmedisv 80Command Line Interface:nwmedi 84Command Line Interface:overview 80comments 9configuration file:backing up, recovering 52configuring:general requirements 34configuring:prerequisites 34configuring:roadmap 40configuring:scheduled backups 58configuring:tasks 41conventions for publication 9

EError Log 32

Iinterface view:configure 28interface view:monitor 31interface view:recover 30

Llicensing requirements 20

MMEDITECH requirements 20

NNetWorker Module for MEDITECH:architecture 14NetWorker Module for MEDITECH:host requirements

20NetWorker Module for MEDITECH:installation

prerequisites 20

NetWorker Module for MEDITECH:installing 23NetWorker Module for MEDITECH:interface overview

28NetWorker Module for MEDITECH:introduction 14NetWorker Module for MEDITECH:reverting to previous

version 25NetWorker Module for MEDITECH:uninstalling 24NetWorker Module for MEDITECH:upgrading: 24NetWorker Module for MEDITECH:upgrading:from 3.0

to 9.1.1 25NetWorker Module for MEDITECH:upgrading:from

8.2.x, 9.0.x, or 9.1 to 9.1.1 24NetWorker: selecting server 29nsrmedirc:command options 83nsrmedirc:command syntax 83nsrmedisv:command options 82nsrmedisv:command syntax 80nwmedi:command options 85nwmedi:command syntax 84

Ooperating system requirements 21

Ppreface 9

Rrecovering: redirected recovery 72recovering:configuration file 52recovering:IDR 66recovering:IDR In-Frame 68recovering:ISB 64RecoverPoint:configuration requirements 38RecoverPoint:installation requirements 23related documentation 9

Sscheduled backups:configuring 58storage arrays:adding 45storage arrays:editing 47storage arrays:overview 41storage arrays:removing 48storage devices:adding 48storage devices:editing 49storage devices:overview 41storage devices:removing 50support information 9Symmetrix VMAX:configuration requirements 38Symmetrix VMAX:installation requirements 22

Ttroubleshooting issues 76


UUnity:configuration requirements 36Unity:installation requirements 22

VVNX:configuration requirements 34VNX:installation requirements 22

Xxms devices:adding 50xms devices:editing 51xms devices:overview 41xms devices:removing 52XtremIO:configuration requirements 39XtremIO:configuring to work with proxy on a physical

host 39XtremIO:configuring to work with proxy on a virtual

machine 40XtremIO:installation requirements 23

Index


emc networker module for meditech 9.1.1 installation ......5 7 9 overview 13 introduction to the...

Documents