The EMC NetWorker Module for MEDITECH Backup · PDF fileThe EMC NetWorker Module for MEDITECH Backup Solution for MEDITECH Databases on EMC Symmetrix and EMC CLARiiON Applied Technology

The EMC NetWorker Module for MEDITECH Backup Solution for MEDITECH Databases on

EMC Symmetrix and EMC CLARiiON Applied Technology

Abstract

The EMC® NetWorker® Module for MEDITECH is used in conjunction with NetWorker to schedule, create, and manage either tape backup or disaster recovery disk-based replicas of MEDITECH databases residing on EMC CLARiiON® and EMC Symmetrix®.

August 2009

Copyright © 2009 EMC Corporation. All rights reserved.

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

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com

All other trademarks used herein are the property of their respective owners.

Part Number h6532

The EMC NetWorker Module for MEDITECH Backup Solution for MEDITECH Databases on EMC Symmetrix and EMC CLARiiON Applied Technology 2

Table of Contents Executive summary ............................................................................................4 Introduction.........................................................................................................4

Audience ...................................................................................................................................... 4 Terminology ................................................................................................................................. 4

Overview..............................................................................................................5 NetWorker Module for MEDITECH integration with MEDITECH ISB APIs......6 NetWorker Module for MEDITECH tape backups for OSAL ISB backups......7 NetWorker Module for MEDITECH tape backups for CS ISB backups...........8 NetWorker Module for MEDITECH disk backups for IDR backups.................9 NetWorker Module for MEDITECH proxy host and EMC storage array configuration for MEDITECH backups ............................................................10

ISB tape backups for MEDITECH segments on EMC CLARiiON ............................................. 10 NMMEDI proxy host and EMC CLARiiON configuration........................................................ 11

IDR disk-based backups for MEDITECH segments on EMC CLARiiON .................................. 13 NMMEDI proxy host and EMC CLARiiON configuration........................................................ 14

ISB tape backups for MEDITECH segments on EMC Symmetrix............................................. 20 NMMEDI proxy host and EMC Symmetrix configuration ....................................................... 20

IDR disk-based backups for MEDITECH segments on EMC Symmetrix.................................. 23 NMMEDI proxy host and EMC Symmetrix configuration for IDR backups ............................ 23

Conclusion ........................................................................................................27


Executive summary MEDITECH is a leading software vendor in the Health Care Information System (HCIS) industry. It offers a full range of software applications for today's health care facilities across two platforms, MAGIC OSAL and MAGIC CS.

The EMC® NetWorker® Module for MEDITECH (NMMEDI) is a solution used by health care organizations to improve their backup and recovery performance by using a wide variety of tape libraries and disk-based disaster recovery replicas for their enterprise Healthcare Operational Continuance strategies.

The EMC NetWorker family of products is used to protect data by simplifying and centralizing backup and recovery operations. NetWorker, with its record-breaking performance, is the ideal backup software for small offices and large data centers. NetWorker supports leading applications such as Oracle, Microsoft SQL Server, and SAP DB, and advanced backup/recovery technologies such as snapshot management and data deduplication. With this support, customers can realize the highest levels of flexibility, management, and cost control over their data protection operations, while protecting their overall investments in these technologies.

EMC Symmetrix® and EMC CLARiiON® are industry-proven storage arrays that maintain a high degree of robustness and availability. An organization can centralize and simplify its data protection strategies with local continuous data protection or remote replication, which protect an organization from data loss due to server failures, data corruption, software errors, viruses, end-user errors, and catastrophic events.

The EMC NetWorker Module for MEDITECH allows MEDITECH customers to utilize centralized backup and recovery management of their databases residing on EMC storage arrays, for performing tape-based backups and point-in-time (PIT) copies for disaster recovery. NMMEDI is integrated with MEDITECH by using its Integrated Serverless Backup (ISB) API and EMC storage array APIs to perform tape-based backups and PIT copies for disaster recovery. NMMEDI allows browsing backups and reduces time for recovery.

Introduction This white paper provides information on a NetWorker Module for MEDITECH solution for effective backups and recoveries of MEDITECH databases residing on EMC CLARiiON and EMC Symmetrix storage arrays.

Audience The intended audiences of this white paper are health care organization management and business decision-makers including storage, server, and database administrators, IT managers, application engineers, storage integrators, consultants, and distributors.

Terminology • BJP – Also known as a Background Job Processor in a MEDITECH CS environment. • Coherency group – A user-defined grouping of MEDITECH hosts that are simultaneously backed up. • EMC CLARiiON SAN Copy™ – EMC CLARiiON technology to create disk-based replicas on a

local or remote CLARiiON array. • EMC Symmetrix SRDF® – The SRDF family of software is the most powerful suite of remote

storage replication solutions available for disaster recovery and business continuity. It leverages the high-end Symmetrix storage architecture to offer unmatched deployment flexibility and massive scalability. It also provides cross volume and storage system consistency, tight integration with industry-leading applications, and automated management for simplified usage.


• EMC Symmetrix TimeFinder®/Mirror – A business continuance solution that allows usage of

special business continuance volume (BCV) Symmetrix devices. Copies of data from a standard Symmetrix device (which are online for regular I/O operations from the host) are sent to, and stored on, BCV devices to mirror the primary data. Each BCV has its own host address and is configured as a standalone Symmetrix device.

• EMR – Also known as an Enterprise Medical Record in a MEDITECH CS environment. • Integrated Disaster Recovery (IDR) – Enables backup vendors to utilize the replicas created by ISB,

to create remote copies for disaster recovery. • Integrated Serverless Backup (ISB) – An API provided by MEDITECH for backup vendors to

initiate backup of MEDITECH databases. • MAGICNAME – A MEDITECH term that encompasses both “OSAL SEGMENT” and “CS Server-

Drive”. • MAGIC CS – MEDITECH's client/server platform, which also runs on top of Microsoft Windows

Server 2000/2003. MAGIC CS uses standard NTFS files, Winsock, TCP/IP stack, and so on, and acts like any other Windows application in its use of Windows APIs.

• MEDITECH OSAL and C/S – Has a built-in Database Management System (DBMS) that provides database services for the MEDITECH application suite.

• MEDITECH SEGMENT – A range of blocks that contains MAGIC data that corresponds to an individual MEDITECH database.

• Proxy host – A host that runs the NetWorker Module for MEDITECH, and is connected to EMC storage arrays.

Overview EMC NetWorker Module for MEDITECH is designed to provide SAN-based backup and recovery of MEDITECH databases that are located on EMC Symmetrix and EMC CLARiiON storage arrays.

NMMEDI uses MEDITECH provided ISB APIs to:

• Communicate with MEDITECH OSAL and MEDITECH CS environments • Freeze the MEDITECH databases and prepare them for backup NMMEDI uses EMC Solutions Enabler APIs to:

• Communicate with EMC storage arrays to get storage array information such as LUN IDs of the MEDITECH databases residing on EMC storage arrays

• Perform remote replication of MEDITECH databases by using SAN Copy operation on EMC CLARiiON and SRDF/S operation on EMC Symmetrix for disaster recovery

NMMEDI uses the NetWorker interface to schedule and manage the backups of MEDITECH databases. NMMEDI writes backup metadata to the NetWorker server, which is used to restore and browse the backups.


Figure 1. The NetWorker Module for MEDITECH architecture

EMC NetWorker Module for MEDITECH is used in conjunction with NetWorker to schedule, create, and manage either local or remote replicas of MEDITECH data segments. NetWorker can be fully integrated with the MEDITECH application to enable the system administrator to perform normal scheduled NetWorker save set backups, and create disaster recovery replicas of the data without interrupting the application. NMMEDI can perform the following operations for MEDITECH databases:

• Create disk-based local or remote replicas of MEDITECH databases for disaster recovery • Create tape-based backups for MEDITECH databases • View backup and restore process information • Recover to the main host from any generation of data NMMEDI supports MEDITECH installations on EMC CLARiiON and EMC Symmetrix storage systems. Because the backup and mirroring processes have been moved to the backup server and the SAN, the resource demands of full database copying, complete resynchronizations, and multiple sequential writes have been lifted from the MEDITECH servers.

NetWorker Module for MEDITECH integration with MEDITECH ISB APIs NMMEDI incorporates MEDITECH Integrated Serverless Backup (ISB) into the NetWorker information protection strategy. MEDITECH ISB provides a system backup process to support local logical unit number (LUN) replication technologies for EMC CLARiiON and EMC Symmetrix systems. The MEDITECH ISB API enables NMMEDI to request a freeze and split of MEDITECH segments for MEDITECH hosts.

When a backup is requested, NMMEDI calls the MEDITECH ISB APIs to prepare the backup list. After receiving the request, MEDITECH prepares the backup list.


If MEDITECH databases reside on:

• EMC CLARiiON, then MEDITECH sends a fracture command to split the source LUN and the clone LUN relationship

• EMC Symmetrix, then MEDITECH sends a split command to split the STD and the BCV relationship After the operation is completed, MEDITECH sends the backup list to NMMEDI for ISB or IDR backups. NMMEDI then performs ISB or IDR backup based on the backup type and schedule.

NetWorker Module for MEDITECH tape backups for OSAL ISB backups The NetWorker Module for MEDITECH tape-based backup is referred to as ISB backup. NMMEDI ISB backups are initiated from the NetWorker server. The NMMEDI backup host sends the backup request to MEDITECH hosts to freeze the MEDITECH databases and split the relationship between source and mirrored devices. The MEDITECH host sends back the backup list to the NMMEDI backup host. The backup list contains the storage array name, the device ID where the MEDITECH database resides, and the MEDITECH MAGIC segment name. A MAGIC segment is the database for a MEDITECH host.

NMMEDI parses the backup list sent by the MEDITECH host and derives the physical drive name of the MAGIC segment device ID from the EMC storage array; the physical drive is visible to the NMMEDI backup host after the split operation. NMMEDI starts the backup of the physical drive and sends the data to the NetWorker storage node.

After the backup is completed, the NMMEDI host sends backup completion status to the MEDITECH host and asks the MEDITECH host to resynchronize the source and the mirrored devices. MEDITECH resynchronizes the devices and sends the backup completion status. The NMMEDI host records the metadata information on the NetWorker server. The metadata information is used for restoring and browsing the backup.


Figure 2. NetWorker Module for MEDITECH: ISB backup with MEDITECH OSAL

NetWorker Module for MEDITECH tape backups for CS ISB backups The NetWorker Module for MEDITECH supports tape-based backups for a MEDITECH CS environment. The NMMEDI host communicates with the MEDITECH CS BJP server to freeze all the MEDITECH databases, and get the backup list for all the MEDITECH hosts in the MEDITECH CS environment. After receiving the backup list for all MEDITECH CS hosts, NMMEDI performs the backup and stores the metadata information on the NetWorker server for recovery.


Figure 3. NetWorker Module for MEDITECH: ISB backup with MEDITECH CS

NetWorker Module for MEDITECH disk backups for IDR backups NMMEDI disk-based backups are performed for disaster recovery and quick recovery and are called Integrated Disaster Recovery (IDR) backups. To perform the IDR backups, EMC storage arrays are configured such that clone/BCV devices of MEDITECH database segments are replicated to the remote storage arrays by using the EMC CLARiiON SAN Copy operation or the EMC Symmetrix TimeFinder operation.

NMMEDI communicates with MEDITECH hosts in the OSAL and the CS environment similar to NMMEDI ISB backups. For IDR backups, NMMEDI initiates the preconfigured remote copy sessions on EMC storage arrays by using EMC Solutions Enabler APIs. After the successful initiation of remote replication, NMMEDI sends a request to MEDITECH hosts to resynchronize the data. After the remote replication is completed, NMMEDI records the metadata information, which contains the MEDITECH host name, segment name, remote copy session name, storage array type, and so on. The metadata information is used to browse the IDR backups.


Figure 4. NetWorker Module for MEDITECH: IDR backup

NetWorker Module for MEDITECH proxy host and EMC storage array configuration for MEDITECH backups MEDITECH database segments reside on external storage, for example, EMC Symmetrix, EMC CLARiiON, or any other storage array. NMMEDI provides support for CLARiiON and Symmetrix.

To configure with an EMC storage array, the NMMEDI proxy host should be configured with:

• A CLARiiON/Symmetrix-supported HBA Fibre Channel host adapter • HBA card-compatible Storport miniport driver on the host • EMC PowerPath® 4.5 or later • NMMEDI proxy host having SAN connections with a CLARiiON or Symmetrix storage array

ISB tape backups for MEDITECH segments on EMC CLARiiON Assumptions are the following:

• The CLARiiON has a storage group for a MEDITECH host, and production LUNs for each MEDITECH segment.


Figure 5. MEDITECH host MAGIC segments configured with EMC CLARiiON

• Each MEDITECH segment LUN is configured with a clone LUN.

Figure 6. Clone LUNs configured with EMC CLARiiON for MAGIC segments

NMMEDI proxy host and EMC CLARiiON configuration

1. Install EMC Solutions Enabler 6.4.2 or later.

2. Install EMC Navisphere® Host Agent and Navisphere CLI.

The Navisphere CLI version should be the same as the FLARE version. For example, if the FLARE version is 19, the Navisphere CLI version should be 2.19xx.

Using Navisphere Manager, mask the MEDITECH clone LUNs with the NMMEDI proxy host:

1. Create a storage group for the NMMEDI proxy host on CLARiiON.

2. Add the NMMEDI proxy host to the newly created storage group.


3. Add clone LUNs of all MEDITECH segments to the newly created storage group.

Navisphere Manager will generate a warning message that says that the selected clone LUNs are already configured with another host and storage group. Ignore the warning, and continue adding the clone LUNs to the storage group. CLARiiON throws the warning so that multiple hosts should not overstep each other while writing data to the disk. In this case, the NMMEDI proxy does not write any data on the clone LUN; it only reads the data for backup.

Figure 7. Storage groups configuration on EMC CLARiiON

4. Open the Device Manager on the NMMEDI proxy host and rescan the disk. You can see all the clone LUNs.

Figure 8. Device Manager on the NMMEDI proxy host

Note: Do not initialize the physical disks on the proxy host that belongs to the clone LUN.


5. Install the NetWorker client software on the NMMEDI proxy host.

6. Install the NMMEDI software on the NMMEDI proxy host.

7. Using the NMMEDI GUI, configure CLARiiON with NMMEDI for backup.

Figure 9. Configuring EMC CLARiiON with NMMEDI

IDR disk-based backups for MEDITECH segments on EMC CLARiiON Assumptions are the following: • The CLARiiON has a storage group for a MEDITECH host and production LUNs for each

MEDITECH segment. • Each MEDITECH segment LUN is configured with a clone LUN.


Figure 10. EMC CLARiiON remote site replication using SAN Copy

NMMEDI proxy host and EMC CLARiiON configuration


2. Install EMC Navisphere Host Agent and Navisphere CLI.

The Navisphere CLI version should be the same as the FLARE version. For example, if the FLARE version is 19, the Navisphere CLI version should be 2.19xx.

Using Navisphere Manager, mask the MEDITECH clone LUNs with the NMMEDI proxy host:

1. Create a storage group for the NMMEDI proxy host on EMC CLARiiON.

2. Add the NMMEDI proxy host to the newly created storage group.

3. Add clone LUNs of all MEDITECH segments to the newly created storage group.

4. Provision at least two LUNs to create the same number of SAN Copy sessions for each clone LUN.

5. Make sure that the SAN Copy LUNs reside on the same storage processor where clone LUNs reside.

6. Make sure that the SAN Copy license is applied on the CLARiiON array.


Figure 11. EMC CLARiiON properties for installed software

7. Right-click the SAN Copy Sessions node and select Create Session from the context menu. The SAN Copy Create Session Wizard is displayed.

Figure 12. Welcome page for the SAN Copy Session Configuration Wizard

8. Click Next after reading the instructions. The Select Session Type page is displayed.


Figure 13. Wizard page to select a Full or Incremental session

9. Select Incremental. During SAN Copy session operation, CLARiiON initially performs Full copy and then Incremental copy.

Click Next. The Select Storage Sources page is displayed.

Figure 14. Wizard page to select the source storage array and source LUN

10. Select the source storage array and the source LUN. In this case, the clone LUN is the source LUN for the SAN Copy session.

Click Next. The Select Storage Destinations for Storage Sources page is displayed.


Figure 15. Wizard page to open the Destination Storage dialog box

Right-click the source LUN for the SAN Copy session. A dialog box for Destination Storage is displayed.

Figure 16. Wizard page to select the destination storage array and LUN

Select the destination EMC CLARiiON storage array from the drop-down list, select the destination LUN for the SAN Copy session, and click OK.


11. Click Next. The Link Utilization page is displayed.

Figure 17. Wizard page for Link Bandwidth

12. Select the bandwidth for the link between source and destination EMC CLARiiON storage arrays. You can also proceed with the default value.

Click Next. The Session Names page with the default SAN Copy session name is displayed.

Figure 18. Wizard page and dialog box for the SAN Copy session name


If you want to change the default name, right-click the default name. A dialog box is displayed. Specify the SAN Copy session name in the Name field and click OK.

13. Click Next. The Summary page is displayed.

Figure 19. Summary wizard page for the SAN Copy session

Click Back if you want to change the settings that you have made in the previous pages. Otherwise, click Finish to create the SAN Copy session.

14. Under SAN Copy Sessions, you can see two Incremental SAN Copy sessions are created with Storage Processor A. Ignore Initial Copy Required because it is initiated through NMMEDI on the first run of IDR backups.

Figure 20. EMC CLARiiON view for SAN Copy sessions

15. Install NetWorker client software on the NMMEDI proxy host.

16. Install NMMEDI software on the NMMEDI proxy host.

17. By using the NMMEDI GUI, configure CLARiiON with NMMEDI for backup.


18. By using the NMMEDI GUI, create a coherency group that contains MEDITECH hostnames.

Figure 21. NMMEDI GUI view for configuring IDR backups

19. In the Disaster Recovery Options field:

Select the checkbox Create Integrated Disaster Recovery Images. Select the number of IDR images to be created. The number should be less than or equal to the

number of SAN Copy sessions configured for the MEDITECH host.

ISB tape backups for MEDITECH segments on EMC Symmetrix Assumptions are as follows: • MEDITECH hosts have a SAN connection with the EMC Symmetrix storage array. • MEDITECH hosts are configured with Symmetrix STD devices to host MAGIC segments. • STD devices on the MEDITECH host are configured with BCV devices and are in sync state. • The NMMEDI proxy host has a SAN connection with the same Symmetrix storage array as for

MEDITECH hosts.

NMMEDI proxy host and EMC Symmetrix configuration


2. Procure the following licenses from EMC licensing and apply them to Symmetrix CLI (symcli):

SYMAPI Feature: BASE / Symmetrix SYMAPI Feature: SRDF / Symmetrix SYMAPI Feature: SRDFA / Symmetrix SYMAPI Feature: SRDF/AR / Symmetrix SYMAPI Feature: SRDF/CG / Symmetrix


SYMAPI Feature: TimeFinder / Symmetrix SYMAPI Feature: Snap / Symmetrix SYMAPI Feature: TF/CG / Symmetrix SYMAPI Feature: SERVER / Symmetrix SYMAPI Feature: DevMasking / Symmetrix SYMAPI Feature: SOLUTION_4 / Symmetrix SYMAPI Feature: TF-Clone / Symmetrix

3. Mask the BCV devices that are configured with the MEDITECH MAGIC segment production STD devices with the NMMEDI proxy host. Use the following sequence of commands to mask the BCV devices:

a. symcfg discover SYMCLI - To discover the Symmetrix array attached to your host

b. symmask –sid <symmetrix id> list hba - To list the configured HBAs and their World Wide Names

c. symmask –sid <symmetrix id> -wwn <HBA wwn> -dir <Symm director> -p <Symm port number> add bcv bcv1, bcv2…

wwn should be followed by the port WWN of the host that you want to give LUNs to, on a particular channel.

-dir is the director number assigned by the storage administrator -p is the port number where 0=port A and 1=port B, assigned by storage admin bcv – BCV devices’ names attached to the MEDITECH MAGIC segment STD devices

d. symmask –sid <symmetrix id> refresh

4. Open the Device Manager on the NMMEDI proxy host and rescan the disk. You can see all the BCV devices. If you cannot see any device, reboot the system and recheck the Device Manager.


Figure 22. Device Manager on the NMMEDI proxy host

5. Install the NetWorker client software on the NMMEDI proxy host.

6. Install the NMMEDI software on the NMMEDI proxy host.

7. By using the NMMEDI GUI, configure Symmetrix with NMMEDI for backup. Click Discover. It searches all Symmetrix arrays that have a SAN connection with the NMMEDI proxy host. Select the appropriate array.


Figure 23. Configure the Symmetrix array with NMMEDI GUI

IDR disk-based backups for MEDITECH segments on EMC Symmetrix Assumptions are as follows:

• MEDITECH hosts have a SAN connection with an EMC Symmetrix storage array. • MEDITECH hosts are configured with EMC Symmetrix STD devices to host MAGIC segments. • STD devices on the MEDITECH host are configured with BCV devices and are in the sync state. • The NMMEDI proxy host has a SAN connection with the same Symmetrix storage array as for the

MEDITECH hosts.

NMMEDI proxy host and EMC Symmetrix configuration for IDR backups You require at least two Symmetrix arrays for IDR backups. The first Symmetrix array, which is called the R1 array, is a primary array deployed on the production site. The second Symmetrix array, which is called the R2 array, is deployed on a remote site for disaster recovery.

The NMMEDI proxy host is configured with an R1 Symmetrix array. Perform the following steps to configure Symmetrix for a single segment or multiple segments:

Note: The R1-BCV that is paired with a STD device on the MEDITECH host should be masked on the NMMEDI proxy host.


Figure 24. EMC Symmetrix remote site replication

1. Establish a SRDF link between R1-BCVs and R2-STD devices of the same size.

2. Configure at least two clone devices with an R2-STD device on the R2 array. The number of clone devices should be greater than or equal to the number of IDR images selected in the NMMEDI GUI and according to EMC Symmetrix limitations.


Figure 25. EMC Symmetrix remote site replication architecture

3. Make sure that the R1 array has the R2 array link, by using the following command:

symdev show –sid <r2 array id> <r2 array device name> The command displays the R2 device information. If the r2 device information is not displayed, check the R1 and R2 array link.

4. Check the RDF information for R1-BCV by using the following command:

symdev show –sid <r1 array id> <r1 bcv device name> The command displays the R2-STD device name and R2 array name in the RDF information section. Note: Masking the R2 device on the proxy host is not required.

5. Create a device group of type RDF1 by using the following command:

symdg create <device group name> -type rdf1

6. Add the R1-BCV device that resides on the NMMEDI proxy host to the newly created device group.


7. Repeat steps 1 through 5 for R1-BCV devices in case of multiple segments on the MEDITECH host.

Each R1-BCV device should reside in a separate device group of type rdf1.

8. Configure at least two clone devices on R2-Symmetrix with each R2-STD device by using the following command:

symclone –sid <R2 Symmetrix ID> -file <file name> -differential create

Example: symclone -sid 276 -file C:\bcv_pair_598_59A.txt -differential create

9. Move all R2-Clone devices to the COPIED state. R2-STD and R2-Clone devices should always be in COPIED state before running IDR backups through the NMMEDI. Otherwise, the NMMEDI fails to perform IDR backup for the MAGIC segment.

Some of the other symcli commands and their examples for configuring and verifying IDR setup are follows:

symdg list — Lists all the device groups. sympd list — Lists all STD devices. symbcv list — Lists all BCV devices. symdg show <device group name> — Displays information about device group. An

example is: symdg show mediidr symclone -sid <R2 Symmetrix ID> -file <file name> RECREATE set mode precopy — Re-creates the clone device relationship and change mode to precopy. An example is: symclone -sid 276 -file C:\bcv_pair_598_59A.txt RECREATE set mode precopy

symclone –sid <R2 Symmetrix ID> –file <file name> activate -Activates the copy operation with clone device. An example is: symclone -sid 276 -file C:\bcv_pair_599_5A6.txt activate

symclone -sid <R2 Symmetrix ID> -file<file name> query — Queries the clone device operation status. An example is: symclone -sid 276 -file C:\bcv_pair_599_5A5.txt query

symmir -g <rdf1 group name> establish –incr — Establishes the sync operation between STD and BCV devices in a device group. An example is: symmir -g mediidr establish –incr

symdev show -sid <R1 Symmetrix id> <device name> — Displays a device’s information. An example is: symdev show -sid 273 FBD

symclone -sid <R2 Symmetrix ID> -file<file name> terminate — Terminates the clone relationship between R2-STD and clone devices. An example is: symclone -sid 276 -file C:\bcv_pair_599_5A6.txt terminate

symmir –g <RDF1 group name> -sid <R2-Symmetrix ID> est -full DEV001 BCV002 — Establishes a relationship between STD and devices in a device group. An example is: symmir -g meditest -sid 276 est -full DEV001 BCV002

symbcv -g <RDF1 group name> remove dev <device name> 5A6 –force — Removes a BCV device from a device group. An example is: symbcv -g meditest remove dev 5A6 -force


symld -g <RDF1 group name> remove DEV001 –force - Removes a STD device from a group. An example is: symld -g meditest remove DEV001 -force

symrdf -g <RDF1 group name> query –bcv — Queries the bcv state in a device

group. An example is: symrdf -g mediidr query -bcv

symrdf -g <RDF1 group name> -bcv est –full — Establishes a relationship between R1-BCV and R2-STD. An example is: symrdf -g mediidr -bcv est -full

Conclusion The EMC NetWorker Module for MEDITECH extends support to the MEDITECH software solution, and is available to health care providers using MEDITECH MAGIC with EMC CLARiiON and EMC Symmetrix storage. The module can be deployed in conjunction with NetWorker to schedule, create, and manage local and remote replicas of the MEDITECH databases. System administrators are enabled to perform normally scheduled NetWorker backups, and create disaster recovery replicas of the data without interrupting the application. By using MEDITEC APIs, two data protections schemes can be implemented:

• ISB (Integrated Serverless Backup) – Performs a backup of the database mirror copy, for example, NetWorker backup to disk or tape.

• IDR (Integrated Disaster Recovery) – Creates a SAN Copy-based or SRDF-based copy of the database mirror copy, for example, EMC CLARiiON SAN Copy and EMC Symmetrix SRDF.

With EMC NetWorker Module for MEDITECH, health care organizations are no longer limited to native host-based mirroring solutions because they can now incorporate their MEDITECH system into their enterprise Healthcare Operational Continuance strategies, providing more flexible choices of tape libraries, improved backups, and better recovery performance.


Documents

The EMC NetWorker Module for MEDITECH Backup · PDF fileThe EMC NetWorker Module for MEDITECH Backup Solution for MEDITECH Databases on EMC Symmetrix and EMC CLARiiON Applied Technology