meditech emc networker module for...introduction to the networker module for meditech the emc®...

EMC® NetWorker® Module forMEDITECHVersion 8.2 SP1

Installation and Administration Guide302-001-192

REV 01

Copyright © 2007-2015 EMC Corporation. All rights reserved. Published in USA.

Published January, 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

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

2 EMC NetWorker Module for MEDITECH 8.2 SP1 Installation and Administration Guide

5

7

9

Overview 11

Introduction to the NetWorker Module for MEDITECH..................................... 12The NetWorker Module for MEDITECH architecture............................12

Installation and Upgrade 17

Installation prerequisites.............................................................................. 18Host requirements.........................................................................................18

MEDITECH requirements...................................................................18Operating system requirements....................................................... 18Array hardware requirements........................................................... 19VNX requirements............................................................................ 19Symmetrix VMAX requirements........................................................ 20RecoverPoint requirements.............................................................. 20VPLEX requirements......................................................................... 20

Installing the NetWorker Module for MEDITECH..............................................21Uninstalling the NetWorker Module for MEDITECH......................................... 21Upgrading the NetWorker Module for MEDITECH............................................21

Upgrading from 8.2 to 8.2 SP1......................................................... 22Upgrading from 3.0 or earlier to 8.2 SP1...........................................22Reverting to the previous version of the NetWorker Module forMEDITECH........................................................................................ 22

Licensing 25

Licensing NetWorker..................................................................................... 26Evaluating the software....................................................................26Licensing the software..................................................................... 27

Licensing the supporting features................................................................. 28Managing the licenses.................................................................................. 29

Interface Overview 31

The NetWorker Module for MEDITECH interface overview............................... 32Configure view................................................................................. 32Recover view.................................................................................... 34Monitor view.................................................................................... 34Log files........................................................................................... 35

Configuration 37

Figures

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

CONTENTS

EMC NetWorker Module for MEDITECH 8.2 SP1 Installation and Administration Guide 3

Configuration prerequisites........................................................................... 38General requirements.......................................................................38VNX configuration requirements.......................................................38Symmetrix VMAX configuration requirements................................... 40RecoverPoint configuration requirements.........................................41VPLEX configuration requirements....................................................42

Configuring backups and recoveries..............................................................42Configuration roadmap.................................................................... 43Configuration tasks..........................................................................43

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

Backups 53

Scheduling backups......................................................................................54ISB...................................................................................................54IDR In-Frame.....................................................................................55IDR...................................................................................................56Configuring the scheduled backups................................................. 57Checking the backups status........................................................... 59

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

Recoveries 63

Recovering the ISB data................................................................................ 64Recovering the IDR In-Frame data.................................................................. 67Recovering the IDR data................................................................................ 67

Troubleshooting 69

Troubleshooting the NetWorker Module for MEDITECH issues........................70

The NetWorker Module for MEDITECH Commands 71

Overview of the NetWorker Module for MEDITECH commands........................72nsrmedisv..................................................................................................... 72

Command syntax............................................................................. 72Command options............................................................................74

nsrmedirc......................................................................................................75Command syntax............................................................................. 75Command options............................................................................75

nwmedi.........................................................................................................76Command syntax............................................................................. 76Command options............................................................................76

77

81

Chapter 6

Chapter 7

Chapter 8

Appendix A

Glossary

Index

CONTENTS


The NetWorker Module for MEDITECH general architecture.............................................13The NetWorker Module for MEDITECH ISB architecture................................................... 13The NetWorker Module for MEDITECH IDR - local replication architecture........................14The NetWorker Module for MEDITECH IDR - remote replication architecture.................... 14The NetWorker Module for MEDITECH IDR In-Fame architecture...................................... 15Configure view...............................................................................................................33Select NetWorker server ................................................................................................33Recover view..................................................................................................................34Monitor view..................................................................................................................35Add Coherency Group.................................................................................................... 44Edit Coherency Group.................................................................................................... 46Add VNX storage array................................................................................................... 47Add VMAX storage array.................................................................................................48Edit VNX storage array................................................................................................... 49Edit VMAX storage array.................................................................................................49Add storage device........................................................................................................ 50Edit storage device........................................................................................................ 51Status of the backups....................................................................................................60Notifications..................................................................................................................61Configure reports...........................................................................................................62Change time.................................................................................................................. 64ISB backed up segments............................................................................................... 65Select target LUN........................................................................................................... 66Change time.................................................................................................................. 68IDR backed up segments............................................................................................... 68

12345678910111213141516171819202122232425

FIGURES


FIGURES


Revision history............................................................................................................... 9Supported snapshot and clone methods....................................................................... 19Backup requirements of the records department'...........................................................57nsrmedisv command options.........................................................................................74nsrmedirc command options......................................................................................... 75nwmedi command options............................................................................................ 76

123456

TABLES


TABLES


Preface

As part of an effort to improve its product lines, EMC periodically releases revisions of itssoftware and hardware. Therefore, some functions described in this document might notbe supported by all versions of the software or hardware currently in use. The productrelease notes provide the most up-to-date information on product features.

Contact your EMC technical support professional if a product does not function properlyor does not function as described in this document.

Note

This document was accurate at publication time. Go to EMC Online Support (https://support.emc.com) to ensure that you are using the latest version of this document.

PurposeThis document describes installation, configuration, backup, and recovery processes forEMC® NetWorker® Module for MEDITECH.

AudienceThis guide is part of the EMC NetWorker Module for MEDITECH documentation set. It isintended for use by system administrators during installation and setup of the product.Operators who schedule and monitor backups may also find this guide helpful.

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

l EMC NetWorker client 8.2 SP1

l EMC VNX® and VNX management software

l EMC Symmetrix® VMAX® and Symmetrix VMAX management software

l EMC RecoverPoint

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

Table 1 Revision history

Revision Date Description

01 January 28, 2015 First release of this document for the NetWorker Modulefor MEDITECH release 8.2 SP1.

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

l EMC NetWorker Module for MEDITECH Release Notes

l EMC NetWorker Module for MEDITECH Installation and Administration Guide

l EMC VNX product documentation

l EMC Symmetrix VMAX product documentation

l EMC RecoverPoint product documentation

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


https://support.emc.com/

https://support.emc.com/

NOTICE

Addresses practices not related to personal injury.

Note

Presents information that is important, but not hazard-related.

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

Italic Use for full titles of publications referenced in text

Monospace Use 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 Use for variables

Monospace bold Use 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 or z

... Ellipses indicate non-essential information omitted from the example

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

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

Technical supportGo to EMC Online Support and click Service Center. You will see several options forcontacting EMC Technical Support. Note that to open a service request, you must have avalid support agreement. Contact your EMC sales representative for details aboutobtaining a valid support agreement or with questions about your account.

Online communitiesVisit EMC Community Network at https://community.emc.com for peer contacts,conversations, and content on product support and solutions. Interactively engage onlinewith customers, partners, and certified professionals for all EMC products.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overallquality of the user publications. Send your opinions of this document to [email protected]

Preface


https://support.emc.com

https://community.emc.com

mailto:[email protected]

CHAPTER 1

Overview

This chapter includes the following section:

l Introduction to the NetWorker Module for MEDITECH............................................. 12

Overview 11

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

l Schedule, create, and manage local replicas of the MEDITECH volumes when you usethe product with the EMC VNX® and EMC Symmetrix® VMAX® storage systems

l Schedule, create, and manage local and remote replicas of the MEDITECH volumeswhen you use the product with the EMC RecoverPoint storage system

l Schedule, create, and manage local and remote replicas of the MEDITECH volumeswhen you use the product with EMC VPLEX® along with the RecoverPoint storagesystem

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 or arraypoint-in-time snapshots to back up the MEDITECH data to the NetWorker devices

l Perform Integrated Serverless Backups (ISBs) of the LUNs that VNX, Symmetrix VMAX,and RecoverPoint support to a NetWorker device, such as tape, Data Domain, anddisk

l Perform Integrated Disaster Recovery (IDR) backups to create bookmarks at regularintervals according to the user-defined schedule on a RecoverPoint appliance, andvalidate the bookmarks in the NMMEDI GUI

l Perform in-frame point-in-time IDRs by using the VNX's VNX-SNAP and SymmetrixVMAX's VPSNAP snapshot features

l Perform backups and recoveries in a quick and predictable timeframe

l View the backup and recovery information

The NetWorker Module for MEDITECH architectureThe NetWorker Module for MEDITECH along with the NetWorker client on the proxy hostcommunicates with the MEDITECH Backup Intermediary (MBI) servers and the VNX,Symmetrix VMAX, and RecoverPoint systems to perform backups. The NetWorker Modulefor MEDITECH proxy host is a Windows server.

The following figures illustrate the general, ISB, and IDR architectures of the NetWorkerModule 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 13

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 15

Overview


CHAPTER 2

Installation and Upgrade

This chapter includes the following sections:

l Installation prerequisites...................................................................................... 18l Host requirements.................................................................................................18l Installing the NetWorker Module for MEDITECH......................................................21l Uninstalling the NetWorker Module for MEDITECH................................................. 21l Upgrading the NetWorker Module for MEDITECH....................................................21

Installation and Upgrade 17

Installation prerequisitesInstall the third-party software according to your requirements. Refer to each product’sdocumentation for information about how to install the software.

Ensure that you meet the following requirements before you install the NetWorker Modulefor MEDITECH:

l You contacted the EMC technical support professional to help you install theNetWorker Module for MEDITECH and the supported software.

l You installed and configured the MEDITECH Backup Facility (MBF) on the MEDITECHservers. Contact your MEDITECH representative for directions and support to installand configure the MBF utility.

l You created the C:\Program Files\Meditech folder on the NetWorker Modulefor MEDITECH proxy host and copied the MBF64.exe file that you obtained fromMEDITECH to this folder.

l You installed and configured EMC NetWorker 8.0.x, 8.1.x, or 8.2.x server. Eachversion's installation and administration guides provide information.

l You installed and configured EMC NetWorker 8.2 SP1 client. The EMC NetWorkerRelease 8.2 SP1 Installation Guide and the EMC NetWorker Release 8.2 SP1Administration Guide provide information.

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

The NetWorker Module for MEDITECH client communicates with MEDITECH hosts andEMC storage systems from the NetWorker Module for MEDITECH proxy host.

l You exposed the target LUN for the source volume to the host on which you install theNetWorker Module for MEDITECH.

Host requirementsThe following sections describe host requirements.

MEDITECH requirementsThe NetWorker Module for MEDITECH supports the following MEDITECH versions andconfigurations:

l C/S NPR 5.x, 5.66 pp10 or later, or 5.67 or later

l MAGIC OS P9.1.33 or later, P9.2.16 or later, or P10.0.6 or later

l MBI server 7.0 for NPR

l MBI 6.07 PP5 or later, or 6.13 PP27 or later for M-AT

l MEDITECH must have at least one MBI server and one file server with one segmentunder the MBI for the backups to succeed.

Operating system requirementsThe NetWorker Module for MEDITECH supports the following operating systems:

l Windows Server 2012 R2 (x64)



l Windows Server 2012 (x64)

l Windows Server 2008 R2 SP1 or later (x64)

l Windows Server 2008 R2 (x64)

Array hardware requirementsThe NetWorker Module for MEDITECH supports the following array hardware:

l EMC VNX with Code 05.33.000.5.015 or later

l EMC VNX with Code 05.32.000.5.206 or later

l EMC VNX with Code 05.31.000.5.726 or later (without VNX-SNAP support)

l EMC Symmetrix VMAX with Enginuity 5876 or later

l EMC RecoverPoint 3.5 or later

l EMC RecoverPoint 4.0

l EMC RecoverPoint 4.1

l EMC RecoverPoint 4.1.1

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

Table 2 Supported snapshot and clone methods

Backup source (MBF) Point in time (MBF)

Local arraysupported

Remote arraysupported

Local arraysupported

Remote arraysupported

VNX VNX

Clone Yes No SanCopy No No

VNX-SNAP Yes No VNX-SNAP Yes No

RecoverPoint Yes Yes RecoverPoint Yes Yes

Symmetrix VMAX Symmetrix VMAX

BCV No No BCV/RDF/Clone

No No

Clone Yes No

VPSNAP Yes No VPSNAP Yes No


VPLEX VPLEX


VNX requirementsThe NetWorker Module for MEDITECH supports the following VNX software installationrequirements:

l EMC NetWorker 8.2 SP1 client


Array hardware requirements 19

l EMC Solutions Enabler 7.6 or later

Note

The NetWorker Module for MEDITECH 8.2 SP1 does not support Solutions Enabler 8.0.

l EMC Unisphere™ Host Agent

l EMC Navisphere®

CLI

l EMC SnapCLI

l EMC Unisphere admsnap

l Windows .NET Framework 4.0

Symmetrix VMAX requirementsThe NetWorker Module for MEDITECH supports the following Symmetrix VMAX softwareinstallation requirements:


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


Note



RecoverPoint requirementsThe NetWorker Module for MEDITECH supports the following RecoverPoint softwareinstallation requirements:



Note



VPLEX requirementsThe NetWorker Module for MEDITECH supports the following VPLEX software installationrequirements:



Note





Installing the NetWorker Module for MEDITECHYou must install both the NetWorker client software and the NetWorker Module forMEDITECH software on the proxy host. EMC recommends that the NetWorker serversoftware reside on a separate host. After you install the NetWorker Module for MEDITECHsoftware, you must configure the NetWorker Module for MEDITECH proxy host as a clienton 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 requirements onpage 18 section lists.

3. Download the NetWorker Module for MEDITECH 8.2 SP1 software package from EMCOnline Support (https://support.emc.com) to a folder on the host.

4. Open the folder that contains the NetWorker Module for MEDITECH 8.2 SP1 softwarepackage.

5. In the ...\nmmedi821_win_64\win_x64 folder, double-click the setup.exe file.

6. On the Welcome to the InstallShield Setup Wizard for NetWorker Module forMEDITECH page, click Next.

7. On the License Agreement page, select I accept the terms in the license agreementand click Next.

8. On the Ready to Install the Program page, click Install.

9. On the Completed the InstallShield Setup Wizard page, click Finish.

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 for MEDITECHsoftware without re-creating the configuration file.

Procedure

1. On the Windows desktop, select Start > Control > Control Panel > Programs > Uninstall aprogram.

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

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

l Double-click EMC NetWorker Module for MEDITECH.

A confirmation message to uninstall the NetWorker Module for MEDITECH appears.

3. Click Yes.

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

l Upgrading from 8.2 to 8.2 SP1

l Upgrading from 3.0 or earlier to 8.2 SP1


Installing the NetWorker Module for MEDITECH 21


Upgrading from 8.2 to 8.2 SP1

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 requirements onpage 18 section lists.

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

4. Upgrade the NetWorker client to 8.2 SP1.

5. Download the NetWorker Module for MEDITECH 8.2 SP1 software package from EMCOnline Support (https://support.emc.com) to a folder on the host.

6. Open the folder that contains the NetWorker Module for MEDITECH 8.2 SP1 softwarepackage.

7. In the ...\nmmedi821_win_64\win_x64 folder, double-click the setup.exe file.

8. On the Welcome to the Upgrade for NetWorker Module for MEDITECH page, clickUpgrade.

9. On the Ready to Upgrade the Program page, click Install.

10.On the InstallShield Wizard Completed page, click Finish.

Upgrading from 3.0 or earlier to 8.2 SP1

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 8.2 SP1.

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 8.2 SP1 client.

The NetWorker Release 8.2 SP1 Administration Guide provides information.

6. Install the NetWorker Module for MEDITECH 8.2 SP1.

Installing the NetWorker Module for MEDITECH on page 21 provides information.

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

Configuration tasks on page 43 provides information.

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

The NetWorker Release 8.2 SP1 Administration Guide provides information.

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 the NetWorker

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 NetWorker Module forMEDITECH, you must uninstall the NetWorker client, and then install the relevant previousversion of the NetWorker client.

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


Reverting to the previous version of the NetWorker Module for MEDITECH 23

CHAPTER 3

Licensing


l Licensing NetWorker............................................................................................. 26l Licensing the supporting features......................................................................... 28l Managing the licenses.......................................................................................... 29

Licensing 25

Licensing NetWorkerYou must install the NetWorker software and the NetWorker Module for MEDITECH in theevaluation mode and enable all the features. You must specify the enabler andauthorization codes on the server to license the product. NetWorker and the NetWorkerModule for MEDITECH do not work beyond the 30-day evaluation period without theenabler and authorization codes.

You must license each installation of the NetWorker server software with a base enablercode. The base enabler code is the license that enables the edition that you purchased.The base enabler codes are available for various editions of the software. The baseenabler code enables you to use NetWorker features such as a specified number ofclients and devices. The add-on enabler code enables you to use additional features. Youmust specify the licenses on the server. The server enforces the licensing and saves theinformation.

You must purchase a NetWorker client license and a NetWorker Module for MEDITECHlicense for each MEDITECH host and NetWorker proxy host.

For example, you must meet the following licensing requirements to support fiveMEDITECH hosts and one proxy host:

l Five MEDITECH hosts require the following licenses:

n Five NetWorker client licenses

n Five NetWorker Module for MEDITECH licenses

l One NetWorker Module for MEDITECH proxy host requires the following licenses:

n One NetWorker client license

n One NetWorker Module for MEDITECH license

Evaluating the softwareYou can evaluate a new installation of the software on a server or evaluate more featuresin an existing installation.

Evaluating a new installationWhen you install the software, you can evaluate the software with all the modules andfeatures for 30 days without entering any codes.

By the end of the evaluation period, you must purchase, specify, and authorize a baseenabler code to use the software.

After the evaluation period, you must purchase the add-on enabler codes that depend onthe edition of the purchased base enabler code to continue to use some of the modulesand features of the evaluation version.

Evaluating features in an existing installationTo evaluate one or more NetWorker modules or features in the software that is installedand enabled, specify a temporary enabler code for each module or feature. The temporaryenabler code is valid for 45 days.

By the end of the evaluation period, you must purchase, install, and authorize thecorresponding license enabler codes to continue to use these modules or features.

Licensing the software on page 27 provides information about how to license thesoftware.

Licensing


Licensing the supporting features on page 28 provides information about licensing thesupporting features.

Specifying the temporary enabler codeThe temporary enabler code is valid on only one host in a network. If you specify thesame code on more than one host in a network, a copy protection violation error occursdisabling the server software on all the servers with duplicate enabler codes.

Procedure

1. In the NMC, click Enterprise.

2. In the Enterprise list in the left panel, right-click the relevant server and select LaunchApplication.

3. In the NetWorker Administration window, click Configuration.

4. In the left panel, right-click Registrations and select New.

5. In the Create Registration dialog box, perform the following steps:

a. In the Enabler Code field, type the temporary enabler code.

b. In the Comment field, type a description for the enabler code.

c. Click OK.

Licensing the softwareThe license enabler code that you purchase is valid for 45 days, which is the registrationperiod. You must purchase, specify, and authorize a license enabler code during theregistration period to permanently use the software. The licensing process is the same forall editions of the software, the modules, and the features.

The following sections explain how to specify and authorize the license enabler code.

Specifying the license enabler codeWhen you specify multiple licenses, specify the base enabler code at the end to savetime. When you add a base enabler code for the NetWorker client, all other hosts in theconfiguration are disabled. You must re-enable the disabled hosts after adding licenses.

Procedure




4. In the left panel, right-click Registrations and select New.

5. In the Create Registration dialog box, perform the following steps:

a. In the Enabler Code field, type the enabler code.

b. In the Comment field, type a description for the enabler code.

c. Click OK.

6. Repeat the procedure to add the additional enabler codes.

Results

The procedure adds the licenses to the NMC. The licenses appear in the right panel of theNMC.

Licensing

Licensing the software 27

You have 45 days during the registration period to authorize the software.

Obtaining the authorization codeYou must authorize the software or the features by the end of the 45-day registrationperiod. Otherwise, you cannot perform backups. However, you can recover the data thatyou backed up during the registration period from the local devices.

Contact the EMC sales representative to obtain the authorization code.

Specifying the authorization codeTo complete the licensing process, you must specify the unique authorization code onthe server within 45 days after you specify the license enabler code.

Procedure




4. In the left panel, select Registration.

5. In the right panel, right-click a license and select Properties.

6. In the Registration Properties - Enterprise License dialog box, perform the followingsteps:

a. In the Auth code field, type the authorization code for the software.

The authorization code pertains to the permanent enabler code or the updateenabler code.

b. In the Comment field, describe the authorization code.

c. Click OK.

Results

If the authorization succeeds, Authorized - No expiration date appears in theExpiration date field in the Registration Properties - Enterprise License dialog box.

After you finish

Perform one of the following steps to avoid interrupting the scheduled backups if youmoved the software from one host to another, or changed the network address of thehost after you installed the software:

l Obtain a new authorization code. You need the host IDs of the old and new servers.The host ID appears in the server’s registration window.

l Install and configure the NetWorker License Manager software. Managing thelicenses on page 29 provides information about the NetWorker License Manager.

Licensing the supporting featuresThe following sections provide information about licensing the features that NetWorkerand NetWorker Module for MEDITECH support.

Multiplatform licensingYou can use the client connections of a server for the server platform only. For example,you can use the client connections of a NetWorker server for Microsoft Windows forWindows client hosts only.

Licensing


A ClientPak®

license allows a server to back up clients of different platforms.

The ClientPak license for UNIX enables a Solaris server to use other UNIX platforms andclients that a UNIX or Windows server backed up.

Update enabler codeYou require a one-year update agreement when you purchase the software for the firsttime. After a year, you must purchase an update agreement to obtain an update enablercode to update the software to a major release.

Additional licensesYou require the following additional licenses to use features in the software:

l Client connection licenses

Every host that you back up in a datazone and the server require a client connectionlicense. You can purchase the client connection license either separately or alongwith the base enabler code. A cluster client and a Network Data ManagementProtocol (NDMP) data server require a special type of client connection license.

l Storage node licenses

Each storage node requires a storage node license in addition to the clientconnection license. A storage node that enables you to back up only itself requires aseparate license.

l NetWorker Module for MEDITECH licenses

NetWorker Module for MEDITECH licensing requires one enabler code per databasetype host. For example, to back up the MEDITECH database on two hosts even if thesame server backs up the two hosts requires two NetWorker Module for MEDITECHenabler codes. However, to back up a host that has multiple instances of thedatabase requires only one NetWorker Module for MEDITECH enabler code.

l Cluster client licenses

You must purchase a cluster client connection, that is, one standard clientconnection for each physical node in a cluster.

l NDMP license

NDMP licensing requires one NDMP client connection for each NDMP data server. TheNDMP client connection applies to any supported NDMP data server. The NDMP dataserver does not require a standard client connection.

Managing the licensesThe NetWorker License Manager provides centralized license management from one hostfor all the licenses in an enterprise configuration. The NetWorker License Managerenables you to move the software from one host to another, or change the IP address onan existing server without reauthorizing the software. You can install the NetWorkerLicense Manager as an option during NetWorker installation.

The latest NetWorker License Manager Installation and Administration Guide providesinformation about how to install and use the NetWorker License Manager.

Procedure

1. Obtain bulk enabler codes.

2. Install the NetWorker License Manager software.

3. Configure the NetWorker License Manager software.

Licensing

Managing the licenses 29

4. Configure the NetWorker servers to access the NetWorker License Manager to managethe licenses of the servers.

Licensing


CHAPTER 4

Interface Overview


l The NetWorker Module for MEDITECH interface overview....................................... 32

Interface Overview 31

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 the configurationfile mediconfig.xml does not exist, a message that states that you have not yet

created the configuration information appears. Click OK in the message box to create theconfiguration file, and continue to use the NetWorker Module for MEDITECH.

The Recover and Monitor views rely on the selection of a NetWorker server. The followingsections provide you an overview of the views and the tasks that you can perform.

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 and Symmetrix VMAX arrays that the hosts use to store data

l The RecoverPoint appliance that the hosts use to store data

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

Configuration tasks on page 43 provides information about how to perform the tasks.

Interface Overview


Figure 6 Configure view

Selecting a NetWorker serverSelect a NetWorker server to perform recoveries, and view the backup and recover jobs inthe Monitor view.

Procedure

1. Click the NetWorker server icon in the NetWorker Module for MEDITECH GUI. TheChange NetWorker Server dialog box appears.

Figure 7 Select 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.

Interface Overview

Configure view 33

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 34 provides moreinformation.

You can view the segments that the selected NetWorker server backed up in the Recoverview. Recover view on page 34 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 67provides information about how to recover the IDR data.

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 aNetWorker server on page 33 provides information about how to change the server.

Note

The NetWorker Module for MEDITECH does not support redirected recovery.

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 segment names,hostnames, and the start and end times of a job. The job details section providesattributes and values of each job. The Monitor page updates the job summary every 30seconds.

Interface Overview


Figure 9 Monitor view

You can view the NetWorker Module for MEDITECH backup and recover jobs that wereperformed on the selected NetWorker server. You can change the server to monitor thecorresponding NetWorker Module for MEDITECH backup and recover jobs. Selecting aNetWorker server on page 33 provides information about how to change 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 error messages inthe following files:

l nsrmedisv.rawThis log file enables you to review the backup information. The default location of thensrmedisv.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 log files,create the NSR_MAXLOGVERS environment variable with a necessary value. If youspecify a value n, the total number of log files in the C:\Program Files\EMCNetWorker\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 a single file,create the NSR_MAXLOGSIZE environment variable with a necessary value in terms ofmegabytes. The default value is 1 MB. After the size of the log file exceeds the limitthat you have set, each backup creates one log file by default. However, you can resetthe NSR_MAXLOGSIZE environment variable before performing backups. You mustrestart the host for the change to be effective from the next backup.

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

l nwmedi.log

Interface Overview

Log files 35

This 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 does notcontain 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 5

Configuration


l Configuration prerequisites................................................................................... 38l Configuring backups and recoveries......................................................................42l Backing up and recovering the configuration file................................................... 51

Configuration 37

Configuration prerequisitesConfigure third-party software according to your requirements. Refer to each product'sdocumentation for information about how to configure the software.

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

General requirementsEnsure that you meet the following general configuration requirements:

l In the NMC, you added only system and administrator as the users.

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

n Backup local data

n Monitor NetWorker

n Operate devices and jukeboxes

n Operate NetWorker

n Recover local data

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 on theNetWorker server.

l You as either a SYSTEM user or an Administrator user of the NetWorker Module forMEDITECH proxy host are in the Application Administrators group on the NetWorkerserver.

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

Perform the following steps to create the security file:

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

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

3. 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 the

PSEXEC command from Windows Start > Run....

4. Run the following command to verify whether the command prompt belongs to theSYSTEM user account:

WHOAMI/USER

Configuration


5. Run the following command in the SYSTEM command prompt to set the globalaccount 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 in step 1 on page 38.

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 FRAME_IP

6. 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 created thesecurity 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 proxy host.

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

l You exposed the target LUN to the proxy host.

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

n EMCCLAR_SNAP_SUBTYPE=MIRRORThe EMCCLAR_SNAP_SUBTYPE indicates the type of snapshot that you use toperform backups.

n EMCCLAR_MAX_CLONE=<Number>where <Number> is a value 32 through 64 depending on the model of VNX. Thedefault 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.

The EMCCLAR_MAX_CLONE enables you to limit the number of LUNs that you caninclude in a snapshot in a VNX-SNAP consistency group.

n FRAME_IP=<storage_processor_A_IP_address>:<storage_processor_B_IP_address>

If you configured two or more VNX arrays in the NetWorker Module for MEDITECHGUI, set the FRAME_IP application information variable with the storage processorIP addresses to point to the correct VNX array for successful backups.

Configuration

VNX configuration requirements 39

Note

Consider the following notes when you specify application information variables:

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, the backupsfail.

VNX-SNAP requirements

l You installed VNX with the 05.32.000.5.206 code or later on a physical proxy host.

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, and rebootedthe host.

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

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

l You specified the following application information variables in the Applicationinformation 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 snapshot that youuse to perform backups.

n FRAME_IP=<storage_processor_A_IP_address>:<storage_processor_B_IP_address>

If you configured two or more VNX arrays in the NetWorker Module for MEDITECHGUI, set the FRAME_IP application information variable with the storage processorIP addresses to point to the correct VNX array for successful backups.

Note





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

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 MEDITECH proxyhost.

Configuration


l You configured the proxy host as a client on the NetWorker server.

l You as either a SYSTEM user or an Administrator user of the NetWorker Module forMEDITECH proxy host are in the Application Administrators group on the NetWorkerserver.

l You created the C:\Program Files\EMC NetWorker\nsr\res\symm.resfile.

The file must contain the source and target devices from Symmetrix VMAX in theSymmetrix ID:<Source_Device_ID> <Target_Device_ID> format, wherethe target device is either a clone or a vpsnap. For example, 000192601677:0B790B7.

For the IDR In-Frame backups, ensure that the number of target thin devices in thesymm.res file is equal to IDR number + 1. The ISB backups use the extra LUN. TheISB backups fail if you used all the thin devices in the symm.res for the IDR In-Framebackups.

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 snap

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 use toperform backups.

Note





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

l You installed RecoverPoint 3.5 or later, 4.0, 4.1, or 4.1.1.

l As an user on RecoverPoint 4.0, 4.1, or 4.1.1, you are assigned with the integrationrole.

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

l You configured the proxy host as a client on the NetWorker server.

l As either a SYSTEM user or an Administrator user of the NetWorker Module forMEDITECH proxy host, you are in the Application Administrators group on theNetWorker server.

Configuration

RecoverPoint configuration requirements 41

l You use one consistency group per RecoverPoint appliance for optimal performanceof backups.

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

l (Optional) You specified the following application information variable in theApplication information field in the Client Properties dialog box of the NMC if eitherbackups 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 the NetWorkerModule for MEDITECH must try to check whether the RecoverPoint image isenabled.


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.


Note





NOTICE

The NetWorker Module for MEDITECH supports the following RecoverPoint configurations:

l Continuous Data Protection (CDP)

l Continuous Remote Replication (CRR)

l Concurrent Local and Remote (CLR) data protection

VPLEX configuration requirements

The EMC VPLEX GeoSynchrony Release 5.3 Product Guide provides information about howto configure VPLEX to use with RecoverPoint to perform the NetWorker Module forMEDITECH backups and recoveries.

Configuring backups and recoveriesThe following sections describe the configuration tasks. You must install and configurethe MEDITECH host and the VNX, Symmetrix VMAX, or RecoverPoint before you configurethe NetWorker Module for MEDITECH.

Configuration


Configuration roadmapTo configure the NetWorker Module for MEDITECH, define the MEDITECH MBI server andthe MEDITECH file servers that you want to back up, and identify the VNX, SymmetrixVMAX, or RecoverPoint systems that you want 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 a file on the NetWorker Module forMEDITECH proxy host. Performing a backup backs up the configuration file. If necessary,you can recover the configuration file if you or another user deletes the file. Backing upand recovering the configuration file on page 51 provides information.

Coherency GroupsThe Coherency Groups enable you to back up multiple segments of multiple MEDITECHhosts at the same time. For example, if you want to back up all administrative data at thesame time, you must create a Coherency Group that contains all the MEDITECH MBIservers that contain the information about the administrative data that exists on theMEDITECH hosts.

The NetWorker Snapshot Management (NSM) concurrently takes snapshots of the VNXLUNs or the Symmetrix VMAX LUNs for all the MEDITECH MBI servers in a CoherencyGroup.

The NetWorker Module for MEDITECH creates point-in-time snapshots for all theMEDITECH segments in a Coherency Group and copies the snapshots to a NetWorkerdevice.

Storage arraysYou must configure the storage arrays to enable the NetWorker Module for MEDITECH totake snapshots of the VNX and Symmetrix VMAX LUNs by using the NSM.

The NSM uses the configuration information to take snapshots before backups, andresynchronizes the clone and production LUNs after backups.

Storage devicesYou must configure the storage device which is a RecoverPoint appliance to enable theNetWorker Module for MEDITECH to communicate with, and store the MEDITECH data.

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 in thescheduled backups

l Identifying the VNX or Symmetrix VMAX storage arrays that the MEDITECH hosts useto store the backup data

l Identifying the RecoverPoint appliance storage devices that the MEDITECH hosts useto store the backup data

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

The parallelism settings that you define in NMC when you set or configure the CoherencyGroups can impact the NetWorker Module for MEDITECH backups. NSM splits all the

Configuration

Configuration roadmap 43

clone and production data segments for each host in the Coherency Group at the sametime. The NetWorker Module for MEDITECH backs up the maximum number of hosts at thesame time according to the parallelism setting.

For example, if the NetWorker server parallelism is set to 4, the NetWorker Module forMEDITECH processes three backups at a time.

Note

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

Procedure

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

2. Click Add Group.

The Add Coherency Group dialog box appears.

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 want to backup. 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 the MEDITECHfile servers are configured.

Configuration


l Confirm password: Re-type the password of the MBI server, by using which theMEDITECH file servers are configured.

l SAN Type: Select the storage array or device—RecoverPoint, VNX, or VMAX to usefor 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 SAN type.

4. Perform and repeat the following steps to add the MEDITECH hosts (MBI servers) tothe Coherency Group:

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 the MBIserver.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 the MBI Portfields.

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 IDR images.

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

l VNX: 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 RecoverPoint: The field does not apply; it is disabled.

Configuration

Configuration tasks 45

Note

You must configure RecoverPoint CDP, CRR, and CLR by using either theUnisphere for RecoverPoint GUI or the RecoverPoint CLI before you performbackups.

6. Click OK.

Editing Coherency GroupsProcedure

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

2. Select the Coherency Group that you want to edit and click Edit Group.

The Edit Coherency Group dialog box appears.

Figure 11 Edit Coherency Group

3. 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 and MBI Portfields.

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

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


6. Repeat step 3 on page 46 through step 5 on page 46 to modify the other hosts in thetable.

Configuration


7. 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 user credentialsare correct.

Click OK.

8. Click OK.

Removing Coherency GroupsProcedure


2. Select the coherency group that you want to remove and click Remove Group.

The Remove Coherency Group dialog box appears.

3. Click OK.

Adding storage arraysThe storage arrays include VNX and Symmetrix VMAX with which the NetWorker Modulefor MEDITECH communicates to store the MEDITECH data.

Procedure


2. Click Add Array.

The Add Storage Array dialog box appears.

Figure 12 Add VNX storage array

3. Perform the following steps to add a VNX array:

a. Click the EMC VNX tab.

b. Specify the following fields:

Configuration


l Serial Number: Type the serial number of the VNX array.

l Storage Processor A IP Address: Type the IP address of the storage processorA.

l Storage Processor B IP Address: Type the IP address of the storage processorB.

Note

VNX has two network connections to the two storage processors to overcomefailovers.

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

l Password: Type the password to access the array.

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

l Verify: Click the button to validate the values that you have specified in thefields.

c. 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.

Editing storage arraysProcedure


2. Select the array that you want to edit and click Edit Array.

The Edit Storage Array dialog box appears.

Configuration


3. Perform the following steps to edit a VNX array:

a. Click the EMC VNX tab.

Figure 14 Edit VNX storage array

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

c. Click Verify to validate the values.

d. Click OK.

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

a. Click the EMC VMAX tab.

Figure 15 Edit VMAX storage array

b. Select the serial number of the array that you want to use and click OK.

Removing storage arraysProcedure


2. Select the storage array that you want to remove and click Remove Array.

Configuration


The Remove Storage Array dialog box appears.

3. Click OK.

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

Procedure


2. Click Add Device.

The Add Storage Device dialog box appears.

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. Select the device that you want to edit and click Edit Device.

The Edit Storage Device dialog box appears.

Configuration


Figure 17 Edit storage device

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

4. Click Verify to validate the values.

5. Click OK.

Removing storage devicesProcedure


2. Select the storage device that you want to remove and click Remove Device.

The Remove Storage Device dialog box appears.

3. 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 use thefile if you lose the actual file.

Note

Recovering the backed up mediconfig.xml configuration file results in the NetWorker

Module for MEDITECH configuration settings that are specific to the file that you arerecovering.

Backing up the 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 and selectthe file.

5. Click Start.

Configuration

Backing up and recovering the configuration file 51

Recovering the 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 scheduled backups.

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 and selectthe file.

5. Click Start.

Configuration


CHAPTER 6

Backups


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

Backups 53

Scheduling backupsThe NetWorker Module for MEDITECH software enables you to perform regular backups ofMEDITECH 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 at anytime.

Scheduled backups save the following items from the NetWorker server:

l all data

l client indexes

l bootstrap file

To recover data to MEDITECH host and NetWorker server after the NetWorker server'sconfiguration data is destroyed, requires the client indexes and the bootstrap file.

Scheduling the NetWorker Module for MEDITECH backups is similar to scheduling theNetWorker file system backups. You must specify fields such as Policy, Group, Clientresources, and so on in the Client Properties dialog box. 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 NetWorker devicessuch as tapes, Data Domain, and disks.

l IDR: The NetWorker Module for MEDITECH retains the point-in-time snapshot on thestorage array while indexing the snapshot details in the NetWorker database. You canuse the snapshot information when you perform IDR recoveries.

ISBThe NetWorker Module for MEDITECH backs up the MEDITECH data to the NetWorkerdevices. The source and target LUNs must exist on VNX, Symmetrix VMAX, orRecoverPoint.

Using VNX or Symmetrix VMAXThe NetWorker Module for MEDITECH uses the MEDITECH MBF utility to communicate withthe MEDITECH to obtain a list of the source LUNs and quiesce and unquiesce theMEDITECH databases, and the NSM to fracture the source LUNs.

Each backup of MEDITECH is a full backup of a MEDITECH data LUN. The backup processincludes the following steps:

1. When you start a backup, the NetWorker Module for MEDITECH uses the MEDITECHMBF utility to get a list of the LUNs in the MEDITECH databases.

2. You perform a pre-configuration check to ensure that all the source LUNs have thecorresponding target LUNs for the backup.

3. The NetWorker Module for MEDITECH uses the MBF quiesce command to quiesce theMEDITECH servers to ensure that you take a consistent snapshot.

4. The NetWorker Module for MEDITECH fractures the LUNs and takes a point-in-timesnapshot.

5. The NetWorker Module for MEDITECH uses the MBF quiesce command to unquiescethe MEDITECH databases or servers.

Backups


Note

If the quiesce operation fails, you must run the MBF reset command before youperform the next backup.

6. The NetWorker Module for MEDITECH performs the backup.

The backup process saves the point-in-time image to a NetWorker device that isconfigured on a NetWorker storage node, and resynchronizes the clone with theprimary LUN.

Note

Multiple independent backups that involve the same host fail when you concurrentlyperform the backups.

You can view the successfully backed up MEDITECH segments in the NetWorker Modulefor MEDITECH GUI and recover these MEDITECH segments.

Using RecoverPointRecoverPoint creates bookmarks of snapshots and stores the bookmarks at the CDP,CRR, and CLR sites. The NetWorker Module for MEDITECH communicates withRecoverPoint to get the bookmarked data and backs up the data to a NetWorker device.

RecoverPoint bookmark eliminates the need to create an array clone for the MEDITECHISB.

The NetWorker Module for MEDITECH communicates with MEDITECH by using theMEDITECH MBF utility to obtain the source LUNs, and RecoverPoint to create bookmarksfor the MEDITECH segments.

IDR In-FrameAn IDR In-Frame backup is a point-in-time snapshot of the MEDITECH segments that existon VNX and Symmetrix VMAX. The IDR In-Frame backups support only the LUNs—bothsource and target that exist on either the same VNX or the same Symmetrix VMAX.

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 IDR In-Frame backups.

l The NetWorker Module for MEDITECH does not support backing up the same sourceLUNs by using different technologies. However, if you use VNX, you can back up thesame source LUNs by using VNX-SNAP and CLONE.

l You must set the following application information variables in the Client Propertiesdialog box:

n EMCCLAR_SNAP_SUBTYPE=VNX-SNAP for VNXThe VNX snap requirements section in VNX configuration requirements on page 38provides information.

n SYMM_SNAP_TECH=VPSNAP for Symmetrix VMAXSymmetrix VMAX configuration requirements on page 40 provides information.

l The IDR number is the maximum number of the point-in-time snapshots that can existfor a Meditech segment at any point of time. The IDR number indicates the point fromwhich recycling of target LUNs must start.For example, if there are 6 target LUNs and the IDR number is 4, after four IDR In-Frame backups, the next IDR In-Frame backup deletes the first backup and uses thefirst LUN that the first point-in-time backup used.

Backups

IDR In-Frame 55

If you want to perform both the ISB and IDR In-Frame backups of the same SymmetrixVMAX source LUN, ensure that the total number of target LUNs are greater than orequal to IDR number + 1.

Adding Coherency Groups on page 43 provides information about how to specify thenumber of IDR images to be created for the SAN that you use.

The IDR In-Frame backup process includes the following steps:

1. When you start the backup, the NetWorker Module for MEDITECH reads the IDRnumber that you specified, from the mediconfig.xml file.

2. Depending on the save set that you specified, the NetWorker Module for MEDITECHqueries for the number of IDR In-Frame snapshots of the save set in the mediadatabase.

3. If there are no snapshots in the media database, or the number of IDR In-Framesnapshots in the media database is less than the IDR number, the NetWorker Modulefor MEDITECH proceeds with step 5.

4. If the number of IDR In-Frame snapshots in the media database is equal to the IDRnumber, the NetWorker Module for MEDITECH deletes the oldest snapshot and thecorresponding logical objects from the media database and proceeds with step 5.

5. The NetWorker Module for MEDITECH uses the MEDITECH MBF utility to get a list ofthe LUNs in the MEDITECH databases.

6. The NetWorker Module for MEDITECH quiesces the MEDITECH servers to ensure thatyou take a consistent snapshot.

Note

You cannot abort the backup from this stage. If you abort the backup, though theNMC reports the group as aborted, the backup succeeds. The NMC and the NetWorkerModule for MEDITECH log files display the following message:NOTE :Abort received: Backup is not aborted.

7. The NetWorker Module for MEDITECH takes a point-in-time snapshot.

8. The NetWorker Module for MEDITECH unquiesces the MEDITECH databases or servers.

9. The NetWorker Module for MEDITECH performs the backup.The backup process creates logical objects for each segment, in the media database.

IDR

NOTICE

This IDR backup process applies to the VPLEX with RecoverPoint configuration also.

The IDR backup enables you to register bookmarks by using RecoverPoint. The backupdoes not save the data to a NetWorker device. The backup process includes the followingsteps:

1. When you start a backup, the NetWorker Module for MEDITECH uses the MEDITECHMBF utility to get a list of the LUNs in the MEDITECH databases.

2. You perform a pre-configuration check to ensure that all the source LUNs have thecorresponding target LUNs for the backup.

3. The NetWorker Module for MEDITECH uses the MBF quiesce command to quiesce theMEDITECH servers to ensure that you take a consistent snapshot.

4. RecoverPoint creates bookmarks of snapshots and stores the bookmarks at the CDP,CRR, and CLR sites.

Backups


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

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

Scheduled backup exampleA healthcare company XYZ wants to ensure that the company backs up all the computersin the Records department according to the requirements listed in the following table.

The table maps each requirement to a specific field in the NMC.

Table 3 Backup requirements of the records department'

Requirement NMC field Task to perform

Backups occur at the same time. Backup ScheduleBackup Group

Set up a schedule to perform backups.Set up a group for each client entry.

Record system backups for the past3 months are immediatelyavailable.

Browse Policy Set up policies for quick access andlong-term storage.

Record system backups for the past7 years are available.

Retention Policy Set up policies for quick access andlong-term storage.

Perform backups to volumes. Pools Set up a pool to sort backup data.

The backup operation backs up aset of MEDITECH hosts of aCoherency Group at the same time.

Client resource Create a backup client resource for eachCoherency Group that you created in theNetWorker Module for MEDITECH GUI.

Recoverable 1 year non-recordsystem data.

Browse PolicyRetention Policy

Client resource

Set up policies for quick access andlong-term storage.Create a backup client resource.

The EMC NetWorker 8.2 SP1 Administration Guide provides information about how toperform the tasks that the table lists.

After you complete the tasks, you can perform the scheduled backups of the MEDITECHdata.

Perform the following steps if you want to perform the ISB and IDR backups on the sameMEDITECH 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.

The EMC NetWorker 8.2 SP1 Administration Guide provides information.

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

Backups

Configuring the scheduled backups 57

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, if you use RecoverPoint, you can start anIDR backup when an ISB is in progress.

Scheduling backups

Before you begin

Ensure that you configured the backup devices before scheduling a backup.

The EMC NetWorker 8.2 SP1 Administration Guide provides information.

Procedure

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 Configuration.

4. Define groups, clients, and schedules specifically for the MEDITECH hosts:

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 dialog box.

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

d. Create a save set to identify each Coherency Group for the MEDITECH hosts thatyou created in the NetWorker Module for MEDITECH GUI.

The syntax of the save set is MEDI:<Coherency_Group>.

e. Schedule the backup.

Note

Ensure that you specify 0 in the Client retries field on the Advanced tab in the GroupProperties dialog box.

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:

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

l Three file servers FS01, FS02, and FS03.

Backups


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 following tasks:

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,FILESERVERDRIVE

For example, MEDI:<Coherency_Group>/MBISERVER/FS01*,FS02 E,FS03 G

Use the NSR_DATA_VOLUME_POOL environment variable to perform backups to a specificmedia pool. Add the environment variable to the system environment and assign thename of the media pool to the environment variable.

For example, NSR_DATA_VOLUME_POOL = meditechpool

If you perform a backup by using the CLI and you want to back up the data to a specificpool, use the -b <media_pool_name> option.

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

Set the debug level to 5 to get more information about backups.

l Run the following command to perform a manual backup:

nsrmedisv -s <server_name> -g <save_group> -m<proxy_server_name> -N MEDI:<Coherency_Group> -D5

l Specify nsrmedisv -D5 in the Backup command field in Client Properties dialogbox of the NMC to perform a scheduled backup.

Checking the backups statusAfter you start a backup in the NMC, you can check the status of the backup by using thefollowing 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 is Runningin the Windows Task Manager window.

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.

Backups

Checking the backups status 59

Note

Use the nsr_render_log.exe utility to render the log messages for the

nsrmedisv.raw file. The EMC Support team provides more information about this

utility.

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

After the ISBs complete, the NetWorker Module for MEDITECH resynchronizes the cloneand 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 Groups and Policies panel in theNetWorker Administration window.

Figure 18 Status of the backups

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

Note

EMC recommends that you configure NetWorker to email a notification only when abackup fails.

Backups


Figure 19 Notifications

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

n Use the default notification:


2. In the left panel, select Notifications.

3. In the Notifications panel, right-click Savegroup Failure and select Properties.

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

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

b. Click OK.

n Create a custom notification:


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.

– Priority: Specify the priority of the notification.

– Action: Typesmtpmail -h mailhost -s <"message"> <user>

Backups

Viewing the backups status and reports 61

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 NetWorker Backup Status folder and select a status.

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

Figure 20 Configure reports

4. Click View Report.

Backups


CHAPTER 7

Recoveries


l Recovering the ISB data........................................................................................ 64l Recovering the IDR In-Frame data.......................................................................... 67l Recovering the IDR data........................................................................................ 67

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 accessibleand is in the ready state.

l To perform the recovery to the original target LUN instead of another disk:

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.

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 33 provides information.

3. Click the Browse time icon.

The Change Time dialog box appears.

Figure 21 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 latest backupand click OK.

5. On the Recover page, select the Coherency Group that has the required backed upsegments to recover.

The backed up segments appear in the right panel.

Recoveries


Figure 22 ISB backed up segments

You can perform the following optional steps:

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

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 the segment andselect Versions.

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

l To retrieve information about the NetWorker volume that contains the backed upMEDITECH segments, right-click the segment and select Required Volumes.

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

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 to selectthe destination for the recovery data.

The Select Target LUN dialog box appears.

Recoveries

Recovering the ISB data 65

Figure 23 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 to recover theselected 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 on page 65 and step 8 on page 66 for all the segments in the Recoverpanel.

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 the followingtasks:

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.

Recoveries


Recovering the IDR In-Frame data

Note

To view the backed up information by using the CLI, run the following command on theNetWorker server:nsrmedirc -s <NetWorker_server> -xThe recovery saves a .csv file with the backup information in the C:\Program Files\EMC NetWorker\nsr\applogs folder.

Recovering the IDR In-Frame data corresponds to the SAN type that you are using.

For VNX, use either the Unisphere for VNX GUI or the Navisphere CLI to recover the image.The VNX documents provide information.

For Symmetrix VMAX, use the relevant Symcli commands. The Symmetrix VMAXdocuments provide information.

Recovering the IDR data

NOTICE

This IDR process applies to the VPLEX with RecoverPoint configuration also.

The NetWorker Module for MEDITECH provides the administrative information thatrecovering the IDR data requires. To recover IDR data, you must contact the MEDITECHSystems Support Group for assistance. Always contact your MEDITECH HCIS coordinatoror the MEDITECH Systems Support Group if you have a problem that necessitates a datarecovery. You must involve MEDITECH to perform recoveries.

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

Note

To view the backed up information by using the CLI, run the following command on theNetWorker server:nsrmedirc -s <NetWorker_server> -xThe recovery saves a .csv file with the backup information in the C:\Program Files\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 33 provides information.

3. Click the Browse time icon.

The Change Time dialog box appears.

Recoveries

Recovering the IDR In-Frame data 67

Figure 24 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 backups thatyou want to view and click OK.

5. On the Recover page, select the Coherency Group that has the required backed upsegments to recover.

The backed up segments appear in the right panel.

Figure 25 IDR backed up segments

You can perform the following optional steps:

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

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 the segment andselect Versions.

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

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

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

The RecoverPoint documents provide information.

Recoveries


CHAPTER 8

Troubleshooting


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

Troubleshooting 69

Troubleshooting the NetWorker Module for MEDITECH issuesThis 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 7.6 or later.

Note


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

Troubleshooting


APPENDIX A

The NetWorker Module for MEDITECH Commands

This appendix includes the following sections:

l Overview of the NetWorker Module for MEDITECH commands................................72l nsrmedisv............................................................................................................. 72l nsrmedirc..............................................................................................................75l nwmedi.................................................................................................................76

The NetWorker Module for MEDITECH Commands 71

Overview of the NetWorker Module for MEDITECH commandsNetWorker Module for MEDITECH commands perform the following functions:

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

l nsrmedirc recovers the specified NetWorker Module for MEDITECH data objects. nsrmedirc on page 75 provides information.

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

The nsrmedisv and nsrmedirc commands generate the application logs and save thelogs in the nsr\applogs folder on the proxy server host. The logs are cumulative. Thecommands 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 a command.Do not include brackets when you type the command to perform a backup or arecovery.

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 in theClient Properties dialog box of NMC, or the CLI depending on the method that you use toperform the backup.

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


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]



To run the preprocessing and postprocessing scripts, you must be either one or all of thefollowing users. The security permission for the preprocessing and postprocessing scriptsmust 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 perform byusing 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, thesave 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 perform backupsto VNX by using the CLI. VNX configuration requirements on page 38 provides informationabout how to create the security file.

Use the nsrmedisv command with the preprocessing and postprocessing script optionsto 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 73

Command optionsThe following table lists the nsrmedisv command options:

Table 4 nsrmedisv command options

Command options Descriptions

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

-q Displays nsrmedisv messages in quiet mode. Only summary information

and error messages appear.

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

detailed information about the progress of the backup.

-b Specifies the device pool.

-c Specifies the NetWorker client to use to perform 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 the backup starts.

-g Specifies the savegroup. The NetWorker server and the savegrpcommand use the group parameter to select the media pool.

-m Specifies the NetWorker Module for MEDITECH proxy server.

-N Specifies the NetWorker save set name.Use the following similar value with the -N option:

MEDI:medi1/feni4/feni1 E,feni1 Fwhere:

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 command must run after the backupcompletes.

-R Generates the backup completion report.

-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 the NetWorkerhost. Specify nsrmedirc and the necessary command options in the CLI to perform therecovery.

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 the recovery.Only minimal information, including error messages, is written to the 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 is similarto 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>.

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

-L Specifies the drive number of an alternate recovery destination. You must usethis 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.


nsrmedirc 75

Table 5 nsrmedirc command options (continued)

Commandoptions

Description

-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 -z command

output lists.

nwmediThe nwmedi command starts the NetWorker Module for MEDITECH GUI.

Command syntaxThe nwmedi command has the following syntax:

nwmedi [-s NetWorker_server] [-c NetWorker_client]

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.



GLOSSARY

This glossary contains terms used in this manual.

A

administrator Person who installs, configures, and maintains the NetWorker software.

B

backup Operation that saves data to a volume.

backup cycle The period of time from one level full backup to the next level full backup.

backup volume A volume used to store backup data.

bookmark A label of a point-in-time image that enables you to explicitly identify the image when youperform a recovery, for example, while you access image. You must create the bookmarkseither manually or by using either the RecoverPoint CLI or the RecoverPoint ManagementApplication.

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 the datathat you save, and enables you to back up data to any point in time.

client A computer, workstation, or file server whose data can be backed up or recovered.

clone A reliable copy of backed up data. Unlike volumes created with a simple copy command,clone volumes can be used in exactly the same way as the original backup volume. Singlesave sets or entire volumes can be cloned.

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 disaster recovery.

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 interface andare referenced when creating a NetWorker save set. See save set.

Console server NetWorker servers and clients are managed from the NetWorker Console server. TheConsole server also provides reporting and monitoring capabilities for all NetWorkerprocesses.


CRR Continuous Remote Replication (CRR) is a RecoverPoint configuration where data istransferred between two sites over Fibre Channel or a WAN. In this configuration, the RPAs,storage, and splitters exist at both the local and the remote site. This type of configurationprovides crash consistent protection based on the applications write activity and enablesrecovery to specific points in time.

D

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

device 1. A storage unit that reads from and writes to backup volumes. A storage unit can be atape device, optical drive, autochanger, or file connected to the NetWorker Server orstorage node.

2. When dynamic drive sharing (DDS) is enabled, refers to the access path to the physicaldrive.

F

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

full backup See level.

G

group A client or group of clients configured to back up files to the NetWorker server at adesignated time of day.

H

host ID A serial number that uniquely identifies a computer.

I

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

L

label A NetWorker assigned label that uniquely identifies a volume. Templates can be used todefine label parameters.

level A measurement that determines how much data is saved during a scheduled or manualbackup.

A full (f) backup backs up all files, regardless of whether they have changed. Levels onethrough nine [1-9] back up files that have changed since the last lower numbered backuplevel. An incremental (incr) backup backs up only files that have changed since the lastbackup.

Glossary


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 A backup that a user requests from the client. The user specifies the files, file systems, anddirectories to backup.

MBF The MEDITECH Backup Facilitator (MBF) is a utility that you use as part of a pre-backupscript. The MBF ensures that all the MEDITECH segments are in a consistent and quiescestate before you start the backup.

media The physical storage medium, such as magnetic tape, optical disk, or file system to whichbackup data is written.

N

NetWorker administrator A user who can add to or change the configuration of the NetWorker server, media devices,and libraries. NetWorker administrators must have their usernames included in theNetWorker server Administrator list.

NetWorker Console server See Console server.

NetWorker server The computer running the NetWorker server software which contains the clientconfiguration information, and provides backup and recovery services to the clients on thesame network.

NetWorker storage node See storage node.

R

recover To restore files from a backup volume to a client disk.

remote device A storage device that is attached to a storage node.

remote procedure call(RPC)

The protocol that the NetWorker server uses to perform client requests over a network.

resource A component that describes the NetWorker server or its clients. Clients, devices,schedules, groups, and policies are all NetWorker resources. Each resource has attributesthat define its properties.

retry mechanism The action NetWorker software performs when client operations fail. This situation mightoccur when the rate of transmission is either low or non-existent.

S

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

Glossary


save The command that backs up client files and makes entries in the online index.

save set A group of files or a file system that is backed up on storage media.

snapshot A point-in-time copy of data created during an instant backup.

storage array A configuration element in the NetWorker Module for MEDITECH interface that enables theproxy server to communicate with the VNX and Symmetrix VMAX systems that storeMEDITECH data.

storage node A storage device physically attached to another computer whose backup operations arecontrolled by the NetWorker server.

V

volume 1. The physical storage medium, such as magnetic tape, optical disk, or file system towhich backup data is written.

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

Glossary


INDEX

Aarray hardware requirements 19audience 9

Bbacking up

configuration file 51IDR 56IDR In-Frame 55ISB 54

backupchecking status 59scheduling 54, 58viewing status and reports 60

Ccoherency groups

adding 43editing 46overview 43removing 47

Command Line Interfacensrmedirc 75nsrmedisv 72nwmedi 76overview 72

comments 9configuration file

backing up, recovering 51configuring

general requirements 38prerequisites 38roadmap 43scheduled backups 57tasks 43

conventions for publication 9

EError Log 35

Iinterface view

configure 32monitor 34recover 34

ISBusing RecoverPoint 55using VNX and Symmetrix VMAX 54

Llicensing

existing installation 26

managing 29NetWorker 26new installation 26obtaining the authorization code 28specifying the authorization code 28specifying the license enabler code 27specifying the temporary enabler code 27supporting features 28

MMEDITECH requirements 18

NNetWorker

selecting server 33NetWorker Module for MEDITECH

architecture 12host requirements 18installation prerequisites 18installing 21interface overview 32introduction 12reverting to previous version 22uninstalling 21upgrading

from 3.0 or earlier to 8.2 SP1 22from 8.2 to 8.2 SP1 22

nsrmedirccommand options 75command syntax 75

nsrmedisvcommand options 74command syntax 72

nwmedicommand options 76command syntax 76

Ooperating system requirements 18

Ppreface 9

Rrecovering

configuration file 52IDR 67IDR In-Frame 67ISB 64

RecoverPointconfiguration requirements 41installation requirements 20


related documentation 9

Sscheduled backups

configuring 57example 57

storage arraysadding 47editing 48overview 43removing 49

storage devicesadding 50editing 50overview 43

removing 51support information 9Symmetrix VMAX

configuration requirements 40installation requirements 20

Ttroubleshooting issues 70

VVNX

configuration requirements 38installation requirements 19

VPLEXconfiguration requirements 42installation requirements 20

Index


meditech emc networker module for...introduction to the networker module for meditech the emc®...

Documents