ShadowCopyProviderforMicrosoftVSSInstallGde RD1660

Hitachi RAID Manager Shadow Copy Provider
for
Microsoft Volume Shadow Copy Service (VSS)
Installation Guide
2004 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED

Notice: No part of this publication may be reproduced or transmitted in any form or by any
means, electronic or mechanical, including photocopying and recording, or stored in a
database or retrieval system for any purpose without the express written permission of
Hitachi Data Systems Corporation.
Hitachi Data Systems reserves the right to make changes to this document at any time
without notice and assumes no responsibility for its use. Hitachi Data Systems products and
services can only be ordered under the terms and conditions of Hitachi Data Systems
applicable agreements. All of the features described in this document may not be currently
available. Refer to the most recent product announcement or contact your local Hitachi
Data Systems sales office for information on feature and product availability.
This document contains the most current information available at the time of publication.
When new and/or revised information becomes available, this entire document will be
updated and distributed to all registered users.
Trademarks
Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., and the
Hitachi Data Systems design mark is a trademark and service mark of Hitachi, Ltd.
Tagmastore USP, HiCommand, Hitachi Freedom Storage, Lightning 9900, Thunder 9200, and
Thunder 9500 are trademarks of Hitachi Data Systems Corporation in the United States and
other countries.
Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation in
the United States and other countries.
Java, Java2, Java Runtime Environment, Java Web Start, Solaris, StorEdge, and Sun are
registered trademarks or trademarks of Sun Microsystems in the United States and other
countries.
All other brand or product names are or may be trademarks or service marks of and are used
to identify products or services of their respective owners.
Notice of Export Controls

Export of technical data contained in this document may require an export license from the
United States government and/or the government of Japan. Please contact the Hitachi Data
Systems Legal Department for any export compliance questions.
Hitachi RAID Manager for VSS Installation Guide
iii
Document Revision Level

Revision
Date
Description
MK-94RD166-00
October 2004
Initial Release
Source Documents for this Revision
RM Shadow Copy Provider Basic Specifications (RMVSS4), version 01-02-03/02
RM Shadow Copy Provider Basic Specifications (RMVSS5), version 01-02-03/02
RAID Manager Basic Specifications (RMHORC52), version 52
MK-94RD166-Pa(RSD-1)
MK-94RD166-Pc(RSD)
MK-94RD166-Pc_AD
MK-94RD166-Pd(RSD)
MK-94RD166-Pe(RSD)
Related Documentation
iv
Microsoft, Developing Volume Shadow Copy Service Hardware Providers for Windows
.NET, version 6
Microsoft, Storage Management Using Windows Server 2003 and Windows Storage
Server 2003 Virtual Disk Service and Volume Shadow Copy Service, August 2003
Preface
Preface
This document describes and provides instructions for installing RAID Manager VSS Provider.
This document assumes that the user has a background in data processing and understands
peripheral storage device subsystems and their basic functions.
Notes:
The term TagmaStore USP refers to the entire Hitachi TagmaStore Universal
Storage Platform Series subsystem family, unless otherwise noted.
The term 9900V refers to the entire Lightning 9900 V Series subsystem family (e.g.,
9980V, 9970V), unless otherwise noted. The term 9900 refers to the entire Lightning
9900 subsystem family (e.g., 9960, 9910), unless otherwise noted. The term 9500V
refers to the entire Thunder 9500V subsystem family (e.g., 9570V, 9580V), unless
otherwise noted.
The use of all other Hitachi Data Systems products is governed by the terms of your
agreement(s) with Hitachi Data Systems.
Software Version
This document revision applies to RAID Manager VSS Hardware Provider version 01-02-03/02.
Comments
Please send us your comments on this document. Make sure to include the document title,
number, and revision. Please refer to specific section(s) and paragraph(s) whenever possible.
E-mail: doc.comments@hds.com
Fax: 858-695-1186
Mail:
Technical Writing, M/S 35-50
Hitachi Data Systems
10277 Scripps Ranch Blvd.
San Diego, CA 92131
Thank you! (All comments become the property of Hitachi Data Systems Corporation.)
vi
Preface
Contents
Chapter 1
Introducing RAID Manager Shadow Copy Provider ............................................................1

1.1
1.2
1.3
1.4
1.5
Chapter 2
Installing RAID Manager Shadow Copy Provider ..............................................................15

2.1
2.2
2.3
Chapter 3
Reviewing the Prerequisites ..................................................................

Completing the Installation Procedures.....................................................
2.2.1 Procedure for New Installation......................................................
2.2.2 Procedure for Update Installation ..................................................
2.2.3 Version Confirmation after Installation ............................................
Uninstalling RAID Manager Shadow Copy Provider ........................................
16
17
17
18
18
19
Performing VSS Operations ................................................................................................21

3.1
3.2
3.3
Chapter 4
Overview ........................................................................................... 2
Reviewing the Three VSS Configurations...................................................... 3
1.2.1 Single Host Configuration .............................................................. 3
1.2.2 Export and Import Host Configuration ............................................... 4
1.2.3 Transportable Configuration........................................................... 5
1.2.4 Reviewing the Processes that Coordinate to Create a Shadow Copy............ 6
Reviewing the Restrictions for VSS Configurations .......................................... 7
Reviewing the Implementation Configuration for RM Shadow Copy Provider........... 9
1.4.1 About System Environment Variables ................................................ 9
1.4.2 About Separated Control Flows ..................................................... 10
1.4.3 About Multiple SVOLs on a PVOL .................................................... 12
1.4.4 About Identical Mirror Unit (MU) Numbers ........................................ 12
1.4.5 About the Execution of Multiple SnapShotSetIDs ................................. 12
Understanding the Relationship Between Backup Software and Each Configuration 13
VSS Start-up Procedures on a Single Host ..................................................

3.1.1 Setting the System Environment Variables ........................................
3.1.2 Setting the RAID Manager Environment ............................................
3.1.3 Executing the Backup Program......................................................
VSS Start-up procedures on a Transportable (Export/Import) Host ....................
3.2.1 Setting the System Environment Variables on the Export Host ................
3.2.2 Setting the RAID Manager Environment on the Export Host ....................
3.2.3 Setting the System Environment Variables on the Import Host ................
3.2.4 Setting the RAID Manager Environment on the Import Host ....................
Reviewing the Notes for VSS Operation .....................................................
3.3.1 Starting HORCM as a Service on Windows 2000/2003............................
22
22
24
27
28
28
29
30
31
35
36
Troubleshooting ...................................................................................................................37
4.1
4.2
4.3
4.4
4.5
4.6
General Troubleshooting ......................................................................

Reviewing the Error Messages ................................................................
Checking Volume Settings .....................................................................
Collecting Additional Information............................................................
Recovering from a Failed Import.............................................................
Calling the Support Center....................................................................
38
39
40
41
42
44
vii
Appendix A: Examples of Complex Configurations ..............................................................................45

A.1
A.2
A.3
Example of a Transportable Host Configuration Using Multiple Volumes .............. 45

Example of a Mixed Configuration (Single Host and Transportable Host) .............. 46
Example of a Two-Node Cluster Configuration on a Backup Server..................... 47
A.3.1 Example of RM Configurations for Two-Node Cluster Using Virtual IP on MSCS48
A.3.2 Example of RM Configurations for Two-Node Cluster Using Static IP on MSCS49
Acronyms and Abbreviations ...................................................................................................................51
List of Figures
Figure 1.1
Figure 1.2
Figure 1.3
Single-Host Configuration for VSS Provider ............................................ 3

Export and Import Host Configuration for VSS Provider ............................. 4
Transportable Configuration for VSS Provider......................................... 5
Figure 3.1
System Environment Variables.......................................................... 22
Figure A.1
Figure A.2
Figure A.3
Figure A.4
Figure A.5
Example of Environment Variables for a Transportable Host Configuration .... 45

Example of a Mixed Configuration ..................................................... 46
Two-Node Cluster Configuration on a Backup Server ............................... 47
Example of RM Configurations for Two-Node Cluster Using Virtual IP on MSCS. 48
Example of RM Configurations for Two-Node Cluster Using Static IP on MSCS .. 49
List of Tables
viii
Table 1.1
Table 1.2
Table 1.3
Table 1.4
Table 1.5
Hidden Property of SVOL and Performance Characteristic.......................... 7

System Environment Variables........................................................... 9
Export Control Flow ...................................................................... 10
Import Control Flow ...................................................................... 11
Backup Software Confirmed with RM Shadow Copy Provider ...................... 13
Table 2.1
Table 2.2
Table 2.3
Table 2.4
Table 2.5
Windows 2003 Enterprise Server and RM Shadow Copy Provider Requirements 16

Files Provided During Installation ...................................................... 17
Setting System Environment Variables on a Single Host ............................ 23
Setting System Environment Variables on a Transportable Host .................. 28
Notes for VSS Operation ................................................................. 35
Table 3.1
Table 3.2
General Troubleshooting for VSS Provider ............................................ 38

Error Messages............................................................................. 39
Contents
Chapter 1
Introducing RAID Manager Shadow Copy Provider
This chapter provides an overview of the RAID Manager Shadow Copy Provider:
Overview (see section 1.1)
Reviewing the VSS Provider Configurations (see section 1.2)
Reviewing the Restrictions for VSS Configurations (see section 1.3)
Reviewing the Implementation Configuration for RM Shadow Copy Provider

(see section 1.4)
1.1
Overview
The Windows 2003 Server platform supports the Volume Shadow Copy Service (VSS), which
provides an infrastructure for creating point-in-time images known as shadow copies. VSS
can produce high-fidelity shadow copies by coordinating with business applications, backup
applications (called requestors), database applications (called writers), and hardware
(such as HDS Storage, and generally called providers) to provide vendor-unique shadow
copy functions. The VSS service is also called the VSS coordinator.
Additionally, the RAID Manager (RM) shadow copy provider component creates a shadow
copy volume by controlling the array via VSS. A shadow copy volume is a copy of a volume
that is used by an application at a specific point in time.
This guide provides an overview of VSS Provider and it contains instructions to help system
administrators install and configure VSS Provider.
Chapter 1 Introducing RAID Manager Shadow Copy Provider
1.2
Reviewing the Three VSS Configurations

RAID Manager (hereafter abbreviated as RM) provides the RM shadow copy provider as a
Hardware Provider for VSS. RM shadow copy provider supports any disks that are defined in
RM configuration files. If any disks for a backup application are not defined in RM
configuration files, then the VSS coordinator will select the provider using the following
default hierarchy and will create a snapshot volume by using the default system software
provider:
Hardware provider (RM shadow copy provider) Software provider System software
provider
There are three possible VSS configurations:
1.2.1
Single Host
Export and Import Host
Transportable
Single Host Configuration

Figure 1.1 shows an example of a single-host configuration for VSS Provider.
Host A
DB
writer
VSS
requestor
VSS
coordinator
VSS
provider
CCI
(RAID Mgr)
CCI
(RAID Mgr)
Command
device
SVOL
PVOL
Lightning 9900V
Figure 1.1
Single-Host Configuration for VSS Provider
1.2.2
Export and Import Host Configuration

Figure 1.2 shows an example of an export and import host configuration for VSS Provider.
Host A for Export
DB
writer
VSS
coordinator
XML
VSS
requestor
Host B for Import
VSS
coordinator
VSS
provider
VSS
provider
CCI
(RAID Mgr)
CCI
(RAID Mgr)
VSS
requestor
Command
device
SVOL
PVOL
Lightning 9900V
Figure 1.2
Export and Import Host Configuration for VSS Provider
1.2.3
Transportable Configuration
Figure 1.3 shows an example of a transportable configuration for VSS Provider. Note that
when importing the SVOL, the requestor imports the designated disk using the VSS
coordinators direct interaction with VDS.
DB
writer
Host A
transportable
VSS
coordinator
Host B
VSS
requestor
SVOL informations
VSS
provider
VSS
requestor
RAID
Manager
RAID
Manager
Command
device
VDS
Mask / Unmask
SVOL
PVOL
RAID
Figure 1.3
Transportable Configuration for VSS Provider
The requestor can choose to import the SVOL using either of the following two methods:
OFFHOST configuration import option (steps 10-13 in section 1.2.4)
RAID Manager Command Line Interface

Use the following command to unmask (mount for LU) the SVOL:
C:\HORCM\etc> raidvchkset d Ser# LDEV# -vg
Use the following command to mask (unmount for LU) the SVOL:
C:\HORCM\etc> raidvchkset d Ser# LDEV# -vg idb
Use the following command to release (empty for LU) the SVOL:
C:\HORCM\etc> pairresync d Ser# LDEV# -l
1.2.4
Reviewing the Processes that Coordinate to Create a Shadow Copy

This section describes the roles of the requestor, writer, and provider and lists the steps to
create a shadow copy. The VSS coordinator maintains overall control of the requestor,
writer, and provider.
1. A backup application (requestor) notifies the VSS coordinator service to prepare a
volume for back up.
2. The VSS coordinator notifies the application-specific writer to prepare its data for
making a shadow copy.
3. The VSS coordinator relays the message to the requestor, and the requestor initiates the
commit snapshot phase. The VSS coordinator temporarily halts (quiesces) application
I/O write requests (I/O read requests are still possible) for the several seconds required
to create the shadow copy of the volume or volumes.
4. The VSS coordinator chooses a provider that matches the volume. For any disks that are
not defined in CCI configuration files, VSS will select the provider using the default
hierarchy (Software provider System software provider).
5. The writer prepares the data in whatever way is appropriate for that application, such
as completing all open transactions, rolling transaction logs, and flushing caches. When
the data is ready for shadow copy creation, the writer notifies the VSS coordinator.
6. RM Shadow Copy Provider splits the designated disk and snapshot disk pair in order to
create the shadow copy (a maximum of 10 seconds).
7. After the shadow copy is created, the VSS coordinator releases the writer from its
temporary quiescent phase. VSS queries the writers to confirm that write I/Os were
successfully held during shadow copy creation. If the writes were not successfully held
(meaning the shadow copy data is potentially inconsistent), the shadow copy is deleted
and the requestor is notified. The requestor can retry the process (loop back to step 1)
or notify the administrator to retry at a later time.
8. RM Shadow Copy Provider notifies the VSS coordinator of the snapshot disks that match a
designated disk.
9. The VSS coordinator creates the XML document file describing the snapshot set in order
to export the transportable snapshot volume.
10. The RM Shadow Copy Provider maps (unmasks) to the VSS coordinator.
11. The VSS coordinator discovers the new LUN, and notifies a backup application of the
snapshot volume mapped to a LUN.
12. The requestor (backup application) starts the backup of the disks that are mounted by
VSS coordinator.
13. When the requestor indicates the completion of the backup, RM Shadow Copy Provider
maps (unmasks) and disables the disk that is designated by the VSS coordinator.
Note: In export and import configuration, steps 10 through 13 above will be performed on
the import host, but this configuration should be supported by a backup requestor.
1.3
Reviewing the Restrictions for VSS Configurations

The following VSS and RM shadow copy provider restrictions apply:
Property of the Shadow Copy volume
Snapshots containing dynamic disks
Hardware snapshots not supported on MSCS
Using VSS under the I/O path manager
I/O during RM shadow copy provider
Property of the Shadow Copy volume

The Shadow Copy volume (SVOL) must be created with the hidden and read-only properties
when detected by the Windows 2003 OS. Drive letters and/or mount points are not
automatically assigned.
VSS requires that the INVISIBLE attribute be set on the SVOL. Because this hidden attribute
is supported only for the 9900V subsystem and not for 9900, the 9900 subsystem uses the
NOREAD attribute to disable SCSI Read command as an alternative for the INVISIBLE
attribute.
Table 1.1 shows the difference in performance characteristics for the INVISIBLE and
NOREAD attributes of SVOL. Note that for each subsystem, connectivity with Windows
2003 is supported.
Table 1.1
Hidden Property of SVOL and Performance Characteristic

Performance Characteristic
Subsystem
SVOL Hidden Property
Import Time
Method of Recognition
See Note 1
9900
NO READ
2-3 minutes
Reboot
9900V, TagmaStore USP,
INVISIBLE
20-30 seconds
Rescan
DF600,
See Note 2
DF600H
Notes 1: In 9900, only one reboot is required on the SVOL host after pair-creation.
Note 2: In 9900v, Open LDEV must be installed when using microcode 21-08-XX.
Snapshots Containing Dynamic Disks

The native support for dynamic disks cannot accommodate LUNs with duplicate signatures
and configuration database contents. The snapshot LUNs must be transported to a different
host.
Because the Logical Disk Manager (LDM) exports the copied dynamic disks regardless of VSS,
only the Import/Export configuration can use dynamic Disks.
When transporting dynamic disk LUNs to a new host, we recommend that at least one
dynamic disk already exist on the receiving host. This ensures that the disk group identifiers
will be unique to both machines.
Hardware Snapshots not Supported on MSCS
MSCS cannot accommodate LUNs with duplicate signatures and partition layout. The
snapshot LUNs must be transported to a host outside the cluster. Therefore, the Basic disks
used for MSCS can only be used on the Export/Import configuration.
Using VSS under the I/O Path Manager
I/O Path Manager must support the Shadow Copy volume as the PnP device, and must
support all DeviceIocontrol functions used on the Shadow Copy volume.
Note: For HDLM, VSS will not be protected from the path failure, since HDLM does not
support all of the DeviceIocontrol functions that will be in use by VSS.
I/O During RM shadow copy provider
During the Commit Snapshot phase, the VSS (coordinator) uses the "Lovelace" driver to
block I/Os sent to the drive that is a backup object. If the backup drive is used for the CCI
(RAID Mgr) Log directory, the snapshot commit process will become deadlocked. If this
situation occurs, either RAID Manager must be installed on a drive that is not a backup
object or the default HORCM log directory must be changed:
To reinstall to another Drive:
1. Uninstall RAID Manager from a drive which is a backup object.
2. Delete \HORCM directory from the drive which is a backup object.
3. Install RAID Manager on a drive which is NOT a backup object.
To change the Log directory for HORCM:
You can change the default Log directory by setting the environment variables for HORCM.
For example:
Set HORCMINST=X
Set HORCM_LOG= Drive: \DIR\logX\curlog
Set HORCM_LOGS= Drive: \DIR\logX\tmplog
horcmstart
[ where X is an instance number ]

[ where Drive is the specified drive such as C: ]
[ where DIR is the specified directory ]
[ must be specified without an argument ]
1.4
Reviewing the Implementation Configuration for RM Shadow Copy Provider

When RM shadow copy provider is set up, it will have the following characteristics:
1.4.1
System environment variables
Separated control flows
Multiple SVOLs on a PVOL
Identical MU numbers
Execution of multiple SnapShotSetIDs
About System Environment Variables

RM Shadow Copy Provider uses two RAID Manager instances for exporting and importing. As
such, RM Shadow Copy Provider must define the instance numbers of RAID Manager and a
mirror unit number (MUN) for getting snapshots using the system environment variables.
Table 1.2
System Environment Variables
Variables
Value
VSHTCHORCMINST_LOCAL
Specifies the RAID Manager Instance number for PVOL
VSHTCHORCMINST_REMOTE
Specifies the RAID Manager Instance number for SVOL
VSHTCHOMRCF_MUN
Specifies any allowable MU number as VSS. If you allow all MU numbers which
were written in the configuration file, then specify them. For example:
VSHTCHOMRCF_MUN=0 1 2
1.4.2
About Separated Control Flows

RM shadow copy provider supports two control flows: Export and Import.
Export flow: The export flow is used to make and identify a SnapShotSet volume using a
SnapShotSetID.
Import flow: The import flow is used to map and discover the SnapShotSet volumes.
Usually, these two control flow are executed as a sequence of backups by VSS Coordinator
and requestor, as described in Table 1.3 and Table 1.4.
Table 1.3
Export Control Flow
Sequence
Coordinator Method
Query Phase for PVOL
Executing RM commands
Pairdisplay d Ser# LDEV# Mun#....
SVOL state
Inquiry
Read
Write
Invisible
Disable
Disable
Invisible
Enable
Enable
by VDS_Lun_Info
Queries whether PVOL is mapped to RM

configuration file or not.
2
Begin Prepare SnapShot

Phase
Pairdisplay d Ser# LDEV# Mun#
by VDS_Lun_Info
Discovers the PVOL of PAIR or COPY state

from specified any MUs.
and SnapShotSetID
Registers the PVOLs as SnapShotSetID.

3
End Prepare SnapShot

Phase
Pairevtwait d Ser# LDEV# -s pair t
by SnapShotSetID
Waits for splitting until PVOL become PAIR

state.
Commit SnapShot Phase
Pairsplit d[g ]Ser# LDEV# Mun#
by SnapShotSetID
Splits PVOLs at time with group, creates the

SVOL
5
Query Phase for getting

SVOL
Pairdisplay d Ser# LDEV# Mun#
by VDS_Lun_Info
Sets the LUN information for SVOL
VSS requestor will be able to get the SnapShotSet volumes into an XML document.
10
Table 1.4
Sequence
Import Control Flow

Coordinator Method
Executing RM commands
Locate LUN Phase for

SVOL
Raidvchkset d Ser# LDEV# -vg
by VDS_Lun_Info(from
XML)
Unmasks the SVOL to an LUN
Query LUN Phase for

SVOL
Pairdisplay d Ser# LDEV#
by VDS_Lun_Info
Gets the mapped an LUN information
SVOL state
Inquiry
Read
Write
Visible
Enable
Enable
Invisible
Disable
Disable
VSS requestor will be able to execute a backup on the SVOL_SSUS or SVOL_COPY state.
8
Free LUN Phase

by VDS_Lun_Info
Raidvchkset d Ser# LDEV# -vg idb

See Note
Pairresync d Ser# LDEV#
Releases the SVOL, and masks an LUN
Notes: The Raidvchkset command will be used if the array can set the SVOL INVISIBLE
attribute. However, the export flow is terminated by VSS Coordinator if VSS requestor
specifies the XML document context as transportable. This enables to make only the
SnapShotSet volumes by specifying the transportable attribute.
The VSS requestor must specify the context as transportable if it wants to perform the
following:
VSS requestor wants to support OFF HOST backup.
VSS requestor wants to make multiple SnapShotSet volumes on the same PVOL.
11
1.4.3
About Multiple SVOLs on a PVOL

RM shadow copy provider determines whether or not VSS can use all SVOLs on the same
PVOL by checking the VSHTCHOMRCF_MUN variable and MU# described in the horcm.conf
file. In other words, RM shadow copy provider finds and registers MU# of PVOL as
SnapShotSetID which VSHTCHOMRCF_MUN matches the MUN described in the horcm.conf
file.
So, if VSHTCHOMRCF_MUN=0 1 2 and horcm.conf file are specified as shown in the following
example, then two SnapShotSetIDs that correspond to MU#1 and #2 are used.
HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
SQL
db1
CL2-C
25
1
1
SQL
HORCM_DEV
#dev_group
SQLS
SQLS
tlog1
CL2-C
25
dev_name port# TargetID LU# MU#

dbs1
CL2-C
25
1
2
tlogs1
CL2-C
25
2
2
If you want to use MU# on the same PVOL based on the horcm.conf file, then you can specify
VSHTCHOMRCF_MUN=0 1 2 3 4 5 6 7 8 9 10 11 12 13
1.4.4
About Identical Mirror Unit (MU) Numbers

RM shadow copy provider checks whether all volumes associated by SnapShotSetID have
identical MU numbers (MU#). If the PVOLs for the application server are the Shadow Image
volumes specified with paircreate m grp as at time split, then during time split, the
PVOLs execute all volumes associated by SnapShotSetID as a group. For this reason, SVOLs
must have identical MU numbers of the PVOLs.
1.4.5
About the Execution of Multiple SnapShotSetIDs

RM shadow copy provider allows multiple SnapShotSetIDs to be a multithreaded component
so that several different requestors can execute the backup at the same time.
Note: VSS coordinator cannot accept multiple SnapShotSetIDs at the same time. To avoid
terminating with an error, VSS requestor must wait for a backup while the following error
message is returned: VSS_E_SNAPSHOT_SET_IN_PROGRESS.
12
1.5
Understanding the Relationship Between Backup Software and Each Configuration

Table 1.5 shows the related support between the backup software and applicable
configurations. The RM shadow copy provider must be used within the scope of the following
supported backup software. For information on future support for additional backup
software applications, please contact your Hitachi Data Systems account team.
Table 1.5
Backup Software Confirmed with RM Shadow Copy Provider
VSS
Component
Applicable Configurations
component
Name
Single Host
Export/Import Host
Transportable
Provider
RM Shadow Copy provider
Supported
Supported
Supported
Unused
Unused
Unsupported
Basic Disk
Available
Available
Available
Basic Disk on MSCS
Not applicable
Available
Available
Dynamic Disk
Not applicable
Available
Available
SI (normal )
Available
Available
Available
SI (quick )
Available
Available
Available
SI (at time split )
Available
Available
Available
TC
Not applicable
Available
Available
See Note
See Note
Hitachi
Hi-command/VDS
Hitachi
LDM
Array
RAID
DF
Hi-Copy
Not applicable
Not applicable
Not applicable
SI
Available
Available
Available
Quick Shadow
Available
Available
Available
TC
Not applicable
Available
Available
See Note
See Note
Note: RM shadow copy provider supports True Copy (Sync and Async) for testing with ISV, by
specifying VSHTCHORC_MUN= 0 as MU#. In True Copy Async, RM shadow copy provider
executes at time split without waiting to flush the sidefile for all volumes associated with
SnapShotSetID as the consistency group (CTgroup).
13
For information about the Available applicable configurations and Backup Software, please
contact your Hitachi Data Systems representative.
For 9900:
9900 cannot be used with True Copy since it cannot use the NOREAD option.
For 9900V:
Using the following microcode, 9900V can support True Copy by using INVISIBLE as an
attribute of SVOL:
Microcode version 21-08-XX requires the installation of the OpenLDEV Guard product.
Microcode version 21-09-08 (or later) does not require the installation of the
OpenLDEV Guard product.
For DF600(H):
Using the following microcode, DF600 (H) can support True Copy by using INVISIBLE as
an attribute of SVOL: 0656(1656).
14
Chapter 2
Installing RAID Manager Shadow Copy Provider
This chapter describes the prerequisites and installation procedures for RAID Manager
Shadow Copy Provider:
Reviewing the Prerequisites (see section 2.1)
Completing the Installation Procedures (see section 2.2)
Uninstalling RAID Manager Shadow Copy Provider (see section 2.3)
15
2.1
Reviewing the Prerequisites

In order to use RAID Manager and RAID Manager Shadow Copy Provider, you must install the
necessary command device and Shadow Image and/or the Copy Program products.
RAID Manager Version
RAID Manager version 01-12-03/03 or later is required.
Windows Requirements
You must install Windows 2003 Enterprise Server (Build 3790), based on the information that
is provided in the following table.
Table 2.1
Windows 2003 Enterprise Server and RM Shadow Copy Provider Requirements
RM Shadow Copy
Provider
Windows2003(Build# 3790)
01-01-03/02
Supported
01-02-03/01
Windows2003(Build# 3790)
Windows2003 SP1
+ HotFix# 833167+ (831112)
(Build#1184)
Not applicable
Not applicable
Supported
Untested
Note: Hotfix # 833167 is available free of charge from Microsoft.
16
Chapter 2 Installing RAID Manager Shadow Copy Provider
2.2
Completing the Installation Procedures

This section describes the procedures for a new and update installation. When you install RM
Shadow Copy Provider, the following files are downloaded, as listed in the following table.
Table 2.2
Files Provided During Installation
No.
Title
File name
Installation location
001
RM Shadow Copy Provider
\HORCM\Tool\RMVSSPRV.exe
DIR\HITACHI\VSS Provider\
RMVSSPRV.dll
002
RM Shadow Copy Provider for

IA64
\HORCM\Tool\RMVSSPRV64.exe
DIR\HITACHI\VSS Provider\
RMVSSPRV.dll
Note: DIR indicates an installation directory. The default directory is \Program Files.
2.2.1
Procedure for New Installation

To install to the servers where the RM Shadow Copy Provider will be used:
1. Stop Microsoft Volume Shadow Copy Service by using the following command:
C:\>net STOP Volume Shadow Copy
<In case of starting>
The Volume Shadow Copy service is stopping.
The Volume Shadow Copy service was stopped successfully.
<In case of stopping>
The Volume Shadow Copy service is not started.
2. Change the current directory to \HORCM\Tool\ where CCI is installed.

3. Execute the appropriate setup program:
For a 32-bit system, run the RMVSSPRV.exe.
For an IA64 system, run the RMVSSPRV64.exe.
4. Restart Microsoft Volume Shadow Copy Service by using the following command if VSS
will not be started:
C:\>net START Volume Shadow Copy
The Volume Shadow Copy service is starting.
The Volume Shadow Copy service was started successfully.
17
2.2.2
Procedure for Update Installation

To install to the servers where the RM Shadow Copy Provider will be used:
1. Stop Microsoft Volume Shadow Copy Service by using the following command.
<In case of starting>
The Volume Shadow Copy service is stopping.
The Volume Shadow Copy service was stopped successfully.
< In case of stopping>
The Volume Shadow Copy service is not started.
2. Delete the installed RM Shadow Copy Provider using the Add or Remove Programs
control panel.
3. Change the current directory to '\HORCM\Tool\ where RAID Manager is installed.
4. Execute the appropriate setup program:
For a 32-bit system, run the RMVSSPRV.exe.
For an IA64 system, run the RMVSSPRV64.exe.
5. Restart Microsoft Volume Shadow Copy Service by using the following command if VSS
will not be started.
The Volume Shadow Copy service is starting.
The Volume Shadow Copy service was started successfully.
2.2.3
Version Confirmation after Installation

After a new installation or update, verify the version information (Version) by using the
following command:
C:\>vssadmin list providers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Provider name: 'RM Shadow Copy Provider'
Provider type: Hardware
Provider Id: {748babd3-8c62-4b3d-b6b7-430b5f858c74}
Version: 01-02-03/01
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
18
2.3
Uninstalling RAID Manager Shadow Copy Provider

To uninstall to the servers where the RM Shadow Copy Provider was used:
1. Stop Microsoft Volume Shadow Copy Service by using the following command:
2. Delete the installed RM Shadow Copy Provider using the Add or Remove Programs
control panel.
3. Restart the Microsoft Volume Shadow Copy Service with the following command if VSS
will not be started:
19
20
Chapter 3
Performing VSS Operations
This chapter describes the post-installation start-up procedures and operational notes for
VSS.
VSS Start-up Procedures on a Single Host (see section 3.1)
VSS Start-up Procedures on a Transportable Host (see section 3.2)
Reviewing the Notes for VSS Operation (see section 3.3)
21
3.1
3.1.1
VSS Start-up Procedures on a Single Host

Setting the System Environment Variables
RAID Manager Shadow Copy Provider uses system environment variables to define the
instance numbers for RAID Manager and a mirror unit number (MUN) for getting snapshots.
When you set up the system environment variables, you will add the variables as shown in
Figure 3.1.
Figure 3.1
System Environment Variables
The value that is listed for each system variable in Figure 3.1 is based on the following
assumptions for the Instance Number and the target volume:
22
50 is the RAID Manager Instance number for PVOL
51 is the RAID Manager Instance number for SVOL
0 is the MUN# on PVOL for VSS
The target volume for backups is E: drive on Harddisk1
ntbackup.exe is used as the backup program
Chapter 3 Performing VSS Operations
Table 3.1 describes each of the variables that you will add.
Table 3.1
Setting System Environment Variables on a Single Host
Variable
Value
Specifies the RAID Manager Instance number for PVOL.
Specifies the RAID Manager Instance number for SVOL.
VSHTCHOMRCF_MUN
Specifies the MUN specified to PVOL in the RAID Manager

configuration file.
To set the system environment variables on a Windows System:

1. Define the system environment variables:
a) From the Control Panel, select System Properties.
b) Click the Advanced tab, then click the Environment Variables button.
c) Add the system environment variables as shown in Table 3.1.
2. Reboot. VSS will automatically be started as a service.
23
3.1.2
Setting the RAID Manager Environment

To set the RAID Manager environment:
1. Discover and describe the command device for %windir%\horcm50.conf. RAID Manager
uses the command device, so you need to discover the command device (xxxx-CM).
C:\HORCM\etc>inqraid -CLI $Phy
DEVICE_FILE
PORT
SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
Harddisk0
CL2-C
62496
16
- OPEN-3-CM
Harddisk1
CL2-C
62496
18
- s/s/ss 0004 5:01-04 OPEN-3
Harddisk2
CL2-C
62496
19
- s/s/ss 0004 5:01-04 OPEN-3
Harddisk3
- L040L2
C:\HORCM\etc>inqraid -CLI $LETALL
DEVICE_FILE
PORT
E:\Vol2\Dsk1
CL2-C
62496
18
- s/s/ss 0004 5:01-04 OPEN-3
D:\Vol1\Dsk3
- L040L2
%windir%\horcm50.conf
HORCM_MON
#ip_address
service
poll(10ms)
timeout(10ms)
127.0.0.1
52050
1000
3000
HORCM_CMD
#dev_name
dev_name
\\.\PhysicalDrive0
dev_name
Note: You must start HORCM without a description for HORCM_DEV and HORCM_INST
because the target ID and LUN are Unknown. You can find out about a mapping of a
physical device with a logical name by using the raidscan -find command option.
2. Execute horcmstart 50 as background.
C:\HORCM\etc>horcmstart 50
starting HORCM inst 50
HORCM inst 50 starts successfully.
3. Verify a physical mapping.

C:\HORCM\etc>set HORCMINST=50
b C:\HORCM\etc>raidscan -pi $Phys -find
DEVICE_FILE
UID S/F PORT
TARG
Harddisk0
0
F CL2-C
25
Harddisk1
0
F CL2-C
25
Harddisk2
0
F CL2-C
25
4. Shut down horcmstart 50.

C:\HORCM\etc>horcmshutdown 50
inst 50:
HORCM Shutdown inst 50 !!!
24
LUN
0
1
2
SERIAL
62496
62496
62496
LDEV
16
18
19
PRODUCT_ID
OPEN-3-CM
OPEN-3
OPEN-3
5. Describe the known HORCM_DEV on %windir%\horcm50.conf.

%windir%\horcm50.conf for PVOL
HORCM_MON
#ip_address
service
127.0.0.1
52050
poll(10ms)
1000
HORCM_CMD
#dev_name
dev_name
\\.\PhysicalDrive0
HORCM_DEV
#dev_group
snap
HORCM_INST
#dev_group
snap
dev_name
snapdev1
dev_name
port#
CL2-C
ip_address
127.0.0.1
TargetID
25
poll(10ms)
1000
HORCM_CMD
#dev_name
dev_name
\\.\PhysicalDrive0
HORCM_INST
#dev_group
snap
dev_name
snapdev1
MU#
0
timeout(10ms)
3000
dev_name
port#
CL2-C
ip_address
127.0.0.1
LU#
1
service
52051
%windir%\horcm51.conf for SVOL

HORCM_MON
#ip_address
service
127.0.0.1
52051
HORCM_DEV
#dev_group
snap
timeout(10ms)
3000
TargetID
25
LU#
2
MU#
0
service
52050
6. Start horcmstart 50 51.

C:\HORCM\etc>horcmstart 50 51
C:\HORCM\etc>set HORCC_MRCF=1
C:\HORCM\etc>pairdisplay -g snap -fdc
Group
PairVol(L/R) Device_File
,Seq#,LDEV#.P/S,Status,
% ,P-LDEV# M
snap
snapdev1(L) Harddisk2
62496
19..SMPL ----,----- ---- snap
snapdev1(R) Harddisk1
62496
18..SMPL ----,----- ---- -
7. Proceed to the appropriate step, based on the outcome of the

raidvchkset g snap vg idb command:
If the command completed successfully, go to step 8.
If command did not complete successfully, go to step 9.
25
8. For an INVISIBLE SVOL:

a) Create and hide an Invisible SVOL (-vg idb option hides a LUN from SCSI Inquiry).
Note: Microcode version 21-08-XX is required in order to install OpenLDEV Guard for
RAID450. However, this requirement is not necessary for microcode version 21-09-XX and
later.
C:\HORCM\etc> raidvchkset g snap vg idb (Only valid RAID450 or DF600H)
C:\HORCM\etc> paircreate -g snap vr m noread
C:\HORCM\etc>pairdisplay -g snap
Group
PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M
snap
snapdev1(L) (CL2-C ,25, 2-0)62496
19..S-VOL PAIR,----18 N
snap
snapdev1(R) (CL2-C ,25, 1-0)62496
18..P-VOL PAIR,62496
19 -
b) VSS needs to make the hidden volumes for SVOL, so you must execute the Rescan
disk by using the diskpart command.
C:\HORCM\etc>diskpart
:
DISKPART> rescan
Please wait while DiskPart scans your configuration...
DiskPart has finished scanning your configuration.
9. For a NO READ SVOL:

a) Create and hide SVOL with NO READ.
Group
snap
snapdev1(L) (CL2-C ,25, 2-0)62496
19..S-VOL PAIR,----18 N
snap
snapdev1(R) (CL2-C ,25, 1-0)62496
19 -
b) In order for VSS to make the hidden volumes for SVOL, you must reboot the system:
Only reboot the SVOL host (back-up server), and only once after executing
"paircreate m noread" on the SVOL host.
c) Start horcmstart 50 51.
C:\HORCM\etc>horcmstart 50 51
Important: Repeat steps 1 through 9 whenever the horcm*.conf file changes. VSS
coordinator will automatically activate the RM Shadow Copy provider so that it can perform
RAID Manager commands when the backup program is executed.
26
3.1.3
Executing the Backup Program

You can execute the back-up program by specifying the target volume for backup after
setting the RAID Manager Environment.
1. Run the NT backup program (%SystemRoot%\system32\ntbackup.exe) by specifying E:
drive on the PVOL.
2. (Optional) Verify that RM Shadow Copy Provider is working by looking at the "Status
field" using the RAID Manager command (pairdisplay -g snap).
When NT backup is working, the pairdisplay state will be "PVOL_PSUS and

SVOL_COPY" or "PVOL_PSUS and SVOL_SSUS".
For example:
Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M
snap snapdev1(L) (CL2-C ,25, 2-0)62496 19..S-VOL COPY,----- 18 snap snapdev1(R) (CL2-C ,25, 1-0)62496 18..P-VOL PSUS,62496 19 W
When NT backup has been deleting the snap, the pairdisplay state will be
"PVOL_COPY and SVOL_COPY" or "PVOL_PAIR and SVOL_PAIR".
For example:
Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M
snap snapdev1(L) (CL2-C ,25, 2-0)62496 19..S-VOL COPY,----- 18 N
snap snapdev1(R) (CL2-C ,25, 1-0)62496 18..P-VOL COPY,62496 19 -
27
3.2
3.2.1
VSS Start-up procedures on a Transportable (Export/Import) Host

Setting the System Environment Variables on the Export Host
When you set up system environment variables on the Export host, you will define (add) the
following variables.
Table 3.2
Setting System Environment Variables on a Transportable Host
Variable
Value
Specifies 50 as RAID Manager Instance number for PVOL side.
VSHTCHOMRCF_MUN
Specifies 0 as MUN specified to PVOL on RAID Manager

configuration file.
The value that is listed for each system variable in Table 3.2 is based on the following
assumptions for the Instance Number and the target volume:
50 is the RAID Manager Instance number for PVOL on HOSTA
51 is the RAID Manager Instance number for SVOL on HOSTB
0 is the MUN# on PVOL for VSS
The target volume for backups is E: drive on Harddisk1
To set the system environment variables on an Export host:

c) Add the system environment variables as shown in Table 3.2.
2. Reboot. VSS will automatically be started as a service. VSS coordinator will
automatically activate the RM Shadow Copy provider.
28
3.2.2
Setting the RAID Manager Environment on the Export Host

DEVICE_FILE
PORT
Harddisk0
CL2-C
62496
16
- OPEN-3-CM
Harddisk1
CL2-C
62496
18
- s/s/ss 0004 5:01-04 OPEN-3
Harddisk2
- L040L2
DEVICE_FILE
PORT
E:\Vol2\Dsk1
CL2-C
62496
18
- s/s/ss 0004 5:01-04 OPEN-3
D:\Vol1\Dsk2
- L040L2
HORCM_MON
#ip_address
service
poll(10ms)
timeout(10ms)
127.0.0.1
52050
1000
3000
HORCM_CMD
#dev_name
dev_name
\\.\PhysicalDrive0
dev_name

DEVICE_FILE
UID S/F PORT
TARG
Harddisk0
0
F CL2-C
25
Harddisk1
0
F CL2-C
25
LUN
0
1
SERIAL
62496
62496
LDEV
16
18
PRODUCT_ID
OPEN-3-CM
OPEN-3

inst 50:
29

%windir%\horcm50.conf for PVOL
HORCM_MON
#ip_address
service
HASTA
52050
poll(10ms)
1000
HORCM_CMD
#dev_name
dev_name
\\.\PhysicalDrive0
HORCM_DEV
#dev_group
snap
HORCM_INST
#dev_group
snap
dev_name
snapdev1
dev_name
port#
CL2-C
ip_address
HOSTB
timeout(10ms)
3000
TargetID
25
LU#
1
MU#
0
service
52051
6. Start horcmstart 50.

C C:\HORCM\etc>horcmstart 50
3.2.3
Setting the System Environment Variables on the Import Host

When you set the System Environment variable on the Import Host, you will add the
following variable:
For the variables value, you will specify 51 as the RAID Manager Instance number for
SVOL.
To set the system environment variables on an Import host:
c) Add the VSHTCHORCMINST_REMOTE system environment variable.
2. Reboot. VSS will automatically be started as a service. VSS coordinator will
automatically activate the RM Shadow Copy provider
30
3.2.4
Setting the RAID Manager Environment on the Import Host

DEVICE_FILE
PORT
Harddisk0
CL2-D
62496
16
- OPEN-3-CM
Harddisk1
CL2-D
62496
19
- s/s/ss 0004 5:01-04 OPEN-3
Harddisk2
- L040L2
DEVICE_FILE
PORT
D:\Vol1\Dsk2
HORCM_MON
HORCM_MON
#ip_address
HOSTB
SERIAL
-
LDEV CTG
-
service
52050
HORCM_CMD
#dev_name
dev_name
\\.\PhysicalDrive0
H/M/12
-
poll(10ms)
1000
SSID R:Group PRODUCT_ID

- L040L2
timeout(10ms)
3000
dev_name

DEVICE_FILE
UID S/F PORT
TARG
Harddisk0
0
F CL2-D
25
Harddisk1
0
F CL2-D
25
LUN
0
1
SERIAL
62496
62496
LDEV
16
19
PRODUCT_ID
OPEN-3-CM
OPEN-3

inst 51:
31

HORCM_MON
#ip_address
HASTB
service
52051
poll(10ms)
1000
HORCM_CMD
#dev_name
dev_name
\\.\PhysicalDrive0
HORCM_DEV
#dev_group
snap
HORCM_INST
#dev_group
snap
dev_name
snapdev1
dev_name
port#
CL2-D
ip_address
HOSTA
timeout(10ms)
3000
TargetID
25
LU#
1
MU#
0
service
52050
6. Start horcmstart 51.

C:\HORCM\etc>pairdisplay -g snap -fdc
Group
PairVol(L/R) Device_File
,Seq#,LDEV#.P/S,Status,
% ,P-LDEV# M
snap
snapdev1(L) Harddisk1
62496
19..SMPL ----,----- ---- snap
snapdev1(R) Harddisk1
62496
18..SMPL ----,----- ---- -
Note: When using the raidvchkset g snap vg idb command in a RAID 450 environment,
microcode version 21-08-XX requires that OpenLDEV Guard be installed. This installation
requirement is not applicable in version 21-09-XX (or later).
7. Proceed to the appropriate step, based on the outcome of the
raidvchkset g snap vg idb command:
32
If the command completed successfully, go to step 8.
If command did not complete successfully, go to step 9.
8. For an INVISIBLE SVOL:

a) Create and hide an Invisible SVOL (-vg idb option hides a LUN from SCSI Inquiry).
C:\HORCM\etc> raidvchkset g snap vg idb (Only valid RAID450 or DF600H)
Group
snap
snapdev1(L) (CL2-D ,25, 1-0)62496
19..S-VOL PAIR,----18 N
snap
snapdev1(R) (CL2-C ,25, 1-0)62496
19 -
b) VSS needs to make the hidden volumes for SVOL, so you must execute the Rescan
disk by using the diskpart command.
:
DISKPART> rescan
DiskPart has finished scanning your configuration.
9. For a NO READ SVOL:

a) Create and hide SVOL with NO READ.
Group
snap
snapdev1(L) (CL2-C ,25, 2-0)62496
19..S-VOL PAIR,----18 N
snap
snapdev1(R) (CL2-C ,25, 1-0)62496
19 -
b) In order for VSS to make the hidden volumes for SVOL, you must reboot the system:
Only reboot the SVOL host (back-up server), and only once after "paircreate m
noread" on SVOL host.
c) Start horcmstart 51.
Important: Repeat steps 1 through 9 whenever the horcm*.conf file changes. VSS
coordinator will automatically activate the RM Shadow Copy provider so that it can
perform RAID Manager commands when the backup program is executed.
33
10. Confirm LU mapping on both hosts: If Windows 2003 identifies that there is an identical
signature copied from PVOL to SVOL, it will cause problems with the signature.
The export host must be connected to PVOLs. Verify that the export host does not see
the SVOL (LDEV#19), as shown in the following example:
DEVICE_FILE
PORT
SERIAL
Harddisk0
CL2-C
62496
Harddisk1
CL2-C
62496
Harddisk2
-
LDEV CTG
16
18
-
H/M/12
s/P/ss
-

- OPEN-3-CM
0004 5:01-04 OPEN-3
- L040L2
The import host must be connected to SVOLs. Verify that the import host does not see
the SVOL (LDEV#18), as shown in the following example:
DEVICE_FILE
PORT
SERIAL
Harddisk0
CL2-D
62496
Harddisk1
CL2-D
62496
Harddisk2
-
LDEV CTG
16
19
-
H/M/12
s/S/ss
-

- OPEN-3-CM
0004 5:01-04 OPEN-3
- L040L2
11. Execute the back-up program, according to the manufacturers instructions.
34
3.3
Reviewing the Notes for VSS Operation

Table 3.3 and section 3.3.1 contains information relating to the operation of VSS Hardware
Provider. Please review these items once you have completed the VSS Hardware Provider
installation.
Table 3.3
Notes for VSS Operation
Item
Notes
Starting RAID Manager
RAID Manager can only be started as a service by an Administrator. Otherwise, if RAID Manager
is started with the System privilege, RAID Manager commands (via the DOS prompt) cannot
attach to RAID Manager.
Independent VDS
RM shadow copy provider and RAID Manager do not use the VDS interface.
RM shadow copy provider and RAID Manager can support two server configurations for the OFF
HOST Backup (one is export server, another is import server ). However, these configurations
must be supported via the back-up requestor by transporting the XML file between the export and
import server.
Required LUN
VSS inquires about whether or not the VSS provider is supporting the LUN using the SCSI Inquiry
Standard Page, Page0x80, and Page0x83. Also, VSS checks all hardware properties of a LUN of
SVOL which the provider reported. Therefore, the following is required as SCSI Inquiries of a LUN:
SCSI Inquiry Standard Page

-- The Vendor Identification must be set as HITACHI.
-- The Product Identification must be set as the effective character string (NOT all
space strings).
-- The Product Revision Level must be set as the effective character string (NOT all space
strings).
-- The Product Revision Level must be identical between PVOL and SVOL.
SCSI Inquiry Page0x80

-- The Product Serial Number must be set as the effective character string (NOT all space
strings).
-- The Product Serial Number must be identical between PVOL and SVOL.
SCSI Inquiry Page0x83

The Device Identification must include the serial number and LDEV number
Time split Volume
If the PVOLs for the application server are the Shadow Image volumes specified with paircreate
m grp as at time split, then all volumes associated with SnapShotSetID are executed as a group
at time split. For this reason, SVOLs must have identical MU numbers of PVOLs.
The volumes of a group that are described in the configuration files must be specified as Backup
volumes.
35
3.3.1
Starting HORCM as a Service on Windows 2000/2003

Usually, RAID Manager (HORCM) will be started using a start-up script that is executed from
the service. However, in the VSS environment, there is no interface to start RAID Manager
(HORCM) automatically when VSS is started as a service. As such, RAID Manager provides an
svcexe.exe command and a sample script (HORCM0_run.txt) file so that it can be started
automatically from the service.
The following example assumes that a service name for HORCM instance#0 is HORCM0.
C:\HORCM\tool\>svcexe
Usage for adding
[HORCM_START_SVC] : svcexe /A=command_path
for deleting [HORCM_START_SVC] : svcexe /D
for specifying a service: svcexe /S=service_name
for dependent services : svcexe /C=service_name,service_name,
Example for adding
[HORCM0] : svcexe /S=HORCM0 "/A=C:\HORCM\tool\svcexe.exe"
for deleting [HORCM0] : svcexe /S=HORCM0 /D
For starting [HORCM0] :[1] make a C:\HORCM\tool\HORCM0_run.txt file.
:[2] set a user account to this service.
:[3] confirm to start by 'horcmstart 0'.
:[4] confirm to stop by 'horcmshutdown 0'.
:[5] start from a service by 'net start HORCM0'.
1. Registering HORCM instance as a service

The system administrator needs to add the HORCM instance. An example for registering
as the service name for HORCM instance#0 is HORCM0.
C:\HORCM\tool\>svcexe /S=HORCM0 "/A=C:\HORCM\tool\svcexe.exe"
2. Customize the sample script file (HORCM0_run.txt) according to the HORCM instance,
and using the descriptions in the text file.
3. Set the user account for the RAID Manager administrator:
a) From the Control Panel, select Administrative Tools.
b) Select Computer Management and open Services and Applications.
c) Select Services.
4. To start the HORCM instance from the service, use the following command:
C:\HORCM\tool\>net start HORCM0
Afterward, confirm that HORCM0 started automatically from REBOOT.
5. To stop the HORCM instance from the service, use the following command:
C:\HORCM\tool\>net stop HORCM0
(If horcmshutdown 0 is used, the script written into HORCM0_run.txt will restart
HORCM0 automatically.)
36
Chapter 4
Troubleshooting
This chapter helps you locate solutions to issues that may occur with the operation of VSS
Hardware Provider.
General Troubleshooting (see section 4.1)
Reviewing the Error Messages (see section 0)
Checking Volume Settings (see section 4.3)
Collecting Additional Information (see section 4.4)
Recovering from a Failed Import (see section 4.5)
Calling the Hitachi Data Systems Support Center (see section 4.6)
37
4.1
General Troubleshooting
If you are having trouble installing or running VSS Provider, please refer to Table 4.1 for
general troubleshooting information.
Table 4.1
38
General Troubleshooting for VSS Provider
Problem
Description
NTBackup cannot cancel a snapshot
After clicking Cancel, NTbackup does not cancel. To correct, install Windows 2003,
service pack 1.
VSS does not work with the Disk

Manager tool (LDM)
Because VSS depends on PnP, we recommend that you do not use the LDM tool
while VSS is running.
Event log increases at every backup
A warning message is recorded to the event log at time every backup, because
VSS uses PnP for mounting the copied SVOL that has the same signature to
PVOL . Therefore, we recommend that the administrator regularly clears the Event
log.
LUN#0 cannot use as SVOL
Some HBA drivers do not scan all LUNs on a port when LUN#0 is hidden as SVOL.
Therefore, we recommend that the user does not LUN#0 as SVOL for all HBA
drivers.
Chapter 4 Troubleshooting
4.2
Reviewing the Error Messages

When an error condition occurs, a detailed error message is generated. The error message
includes an error code and the steps that the administrator should take to resolve the issue.
Two categories of error messages are output to the application event log:
RM Shadow Copy Provider (RMVSSPRV)
Microsoft Volume Shadow Copy Service (VSS)
Table 4.2 lists the RMVSSPRV and VSS error messages.

Table 4.2
Error Messages
Error Message
Error Cause
Corrective Action
[EV_ERPERM]
Permission denied with the VSS
hardware provider
RM Shadow Copy Provider is

activated except for the Local
System account.
Confirm the RM Shadow Copy Provider

start up account.
[EV_ENOMEM]
The memory is insufficient
The memory for executing a RM

Shadow Copy Provider could not be
retained.
Increase the virtual memory capacity of the

whole system, or terminate unnecessary
programs or daemon processes that are
running simultaneously.
[EV_INVSTP]
Invalid pair status
The pair status of a target volume

isn't appropriate.
Use the pairdisplay command to confirm

volume status.
[EV_CMDERR]
VSS caught a RAID Manager command
error
A RAID Manager command returned

an error
Refer to the RAID Manager system error

code for information about resolving the
issue.
[EV_EGETEV]
An error occurred in
GetEnvironmentVariable()
The system environment variable

could not be obtained from
GetEnvironmentVariable() system
call.
Verify whether the system environment

variable is defined, then refer to the RAID
Manager system error code for information
about resolving the issue.
[EV_ENOSUP]
No supported device
The specified device is a command

device or unsupported disk.
Verify whether a target disk is the

supported disk.
[EV_ENOOBJ]
Not found object
The SnapshotSetID that is specified

by the Provider is invalid.
Verify whether an error about Shadow

Copy Service is written in the event log.
Use the error data to resolve the issue.
[EV_ENOSER]
No such serial number
A Serial number could not be

acquired from the specified device
information
Verify whether an error is written in the

event log. Use the error data to resolve the
issue.
[EV_EXCEPT]
An exception occurred
An Exception occurred during a

process of RM Shadow Copy
Provider
Verify whether an error about system

instability is written in the event log. Use
the error data to resolve the issue.
[EV_INVARG]
Invalid argument
The argument which a coordinator

specified is invalid

[EV_INVSEQ]
Invalid sequence
The order specified from a

coordinator is invalid

[EV_INCMUN]
Inconsistent MUN in a Snapshot Set
The Mun of a volume within a

Snapshot Set isn't identical to the
others in the Snapshot Set.
Use the pairdisplay command to confirm

the Mun that is used in the Snapshot Set
39
4.3
Checking Volume Settings

If the cause of an error cannot be identified by any of the messages that are contained in
the application event log, verify the volume settings, as described in this section.
Check the SVOL attribute
Verify whether SVOL has NO READ attribute. For example:
C:\HORCM\etc> set HORCC_MRCF=1

C:\HORCM\etc> set HORCMINST=%VSHTCHORCMINST_REMOTE%
Group
snap
snapdev1(L) (CL2-D ,25, 1-0)62496
19..S-VOL PAIR,----18 N
snap
snapdev1(R) (CL2-C ,25, 1-0)62496
19 -
If SVOL does not have the NO READ attribute, recreate it. For example:
C:\HORCM\etc> pairsplit -g snap S

snap
snapdev1
Check the LUN map for Export/Import

If Windows 2003 has identified identical Signatures copied from PVOL to SVOL, then the
signature will be confused when it notices that the drive letter has disappeared.
Check if the export host has been connected to PVOLs, only. For example:
DEVICE_FILE
PORT
SERIAL
Harddisk0
CL2-C
62496
Harddisk1
CL2-C
62496
Harddisk2
-
H/M/12
s/P/ss
-

- OPEN-3-CM
0004 5:01-04 OPEN-3
- L040L2
Check if the import host has been connected to SVOLs, only. For example:
DEVICE_FILE
PORT
SERIAL
Harddisk0
CL2-D
62496
Harddisk1
CL2-D
62496
Harddisk2
-
40
LDEV CTG
16
18
-
LDEV CTG
16
19
-
H/M/12
s/S/ss
-

- OPEN-3-CM
0004 5:01-04 OPEN-3
- L040L2
4.4
Collecting Additional Information

If your efforts to resolve an issue by checking the application event log and verifying volume
settings have not been successful, please request an investigation into the issue by
contacting the Hitachi Data Systems Support Center. Before requesting an investigation,
please collect the following information:
Command outputs:
set
inqraid CLI fg $Phys
raidscan pi $Phys findg
pairdisplay g ??? CLI fd (where ??? is a group name)
The RMVSSPRV and VSS error in application event log.
Log files:
All of the files under /HORCM/log* (where * is RAID Manager instance number)
%windir%\horcm*.conf
41
4.5
Recovering from a Failed Import

The VSS coordinator creates an XML document file that describes a snapshot set in order to
export the transportable snapshot volume. Following is a summary of the sequence of events
for when the volume is imported:
1. The RM Shadow Copy Provider maps (Unmasks) the designated disk of the VSS
coordinator to the LUN, using LocateLun().
2. The VSS coordinator discovers the new LUN by re-scanning used PnP, and compares the
volumes describing to XML to the new LUN (New Device Object).
If the import succeeds, the snapshotted volume is mapped to an LUN using a backup
application:
a) The requestor (backup application) starts backing up the disks mounted by VSS
coordinator.
b) When the requestor indicates the completion of the backup, RM Shadow Copy
Provider unmaps (masks) and resynchronizes the designated disk using
OnLunEmpty().
c) The VSS coordinator hides or makes Unknown the designated disk by rescanning used PnP.
If the import fails, then the VSS coordinator sends an error notification to the
backup application: VSS_E_NO_SNAPSHOTS_IMPORTED(0x80042320)
In this case, the VSS coordinator or the backup application deletes the located
volumes, then RM Shadow Copy Provider unmaps (masks) and resynchronizes the
designated disk using OnLunEmpty().
If the backup operation is terminated with an error without calling OnLunEmpty(),
then an administrator must perform one of the following recovery procedures:
If INVISIBLE SVOL is used
a)
Unmap (mask) and resynchronize all target SVOLs using the following
command:
C:\HORCM\etc>set HORCMINST=X
C:\HORCM\etc> raidvchkset g GRP vg idb
[ where GRP is a group name ]
C:\HORCM\etc> pairresync -g GRP
b)
Use the rescan command to hide the SVOLs:
:
DISKPART> rescan
DiskPart has finished scanning your configuration
c)
42
Re-execute the back-up operation.
If NO READ SVOL is used

a)
Resynchronize all target SVOLs using the following command:
C:\HORCM\etc> pairresync -g GRP

[ where GRP is a group name ]

b)
Use the rescan command to hide the SVOLs:
:
DISKPART> rescan
DiskPart has finished scanning your configuration
c)
Re-execute the back-up operation.
43
4.6
Calling the Support Center

If you need to call the Hitachi Data Systems Support Center, make sure to provide as much
information about the problem as possible, including the circumstances surrounding the
error or failure (see section 4.4).
The worldwide Hitachi Data Systems Support Centers are:
44
Hitachi Data Systems North America/Latin America

San Diego, California, USA
1-800-348-4357
Hitachi Data Systems Europe

Contact Hitachi Data Systems Local Support
Hitachi Data Systems Asia Pacific

North Ryde, Australia
61-2-9325-3300
Appendix A Examples of Complex Configurations

A.1
Example of a Transportable Host Configuration Using Multiple Volumes

To add volumes (offdev2 and offdev3) for the current application, you only need to add the
target volumes (offdev2 and offdev3) to the current configuration files, as shown below.
After you change the configuration files on both servers, then restart the HORCM instances,
the pair-volume is created.
horcm50.conf on HOST A
horcm51.conf on HOST B
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
HSTA
52050
1000
3000
HORCM_MON
#ip_address service poll(10ms)
timeout(10ms)
HSTB
52051
1000
HORCM_CMD
#dev_name
\\.\PhysicalDrive0
HORCM_DEV
#dev_group
offhost
offhost
offhost
HORCM_INST
#dev_group
offhost
3000
HORCM_CMD
#dev_name
\\.\PhysicalDrive1
dev_name
offdev1
offdev2
offdev3
port# TargetID LU# MU#

CL2-C
25
1
2
CL2-C
25
3
2
CL2-C
25
5
2
ip_address
HSTB
service
52051
Host A for Export
DB
writer
VSS
coordinator
VSHTCHOMRCF
_MUN=2
VSHTCHORCMINST
_LOCAL =50
HORCMINST=50
CL2-C
HORCM_DEV
#dev_group
offhost
offhost
offhost
HORCM_INST
#dev_group
offhost
dev_name
offdev1
offdev2
offdev3

CL2-D
25
2
0
CL2-D
25
4
0
CL2-D
25
6
0
ip_address
HSTA
service
52050
Host B for Import
XML
VSS
requestor
VSS
coordinator
VSS
provider
VSS
provider
RAID
Manager
RAID
Manager
VSS
requestor
VSHTCHORCMINST
_REMOTE =51
HORCMINST=51
CL2-D
Command
device
PVOLs
2
2
Offhost offdev1
SVOLs
Offhost offdev2
Offhost offdev3
RAID
Figure A.1
Example of Environment Variables for a Transportable Host Configuration
45
A.2
Example of a Mixed Configuration (Single Host and Transportable Host)

To create pair-volumes (snap) for another application on the HOST A server, you only need
to add a group (snap) for the target volumes in the current configuration files, and add
HORCMINST 51 on the HOST A server. After you change and add the configuration files on the
HOST A server, then restart HORCM 50 and HORCM 51, the pair-volume is created.
horcm51.conf on HOST A
HORCM_MON
HSTA
52051
1000
3000
HORCM_CMD
#dev_name
\\.\PhysicalDrive0
HORCM_DEV
snap
snapdev1 CL2-C
25
2
0
HORCM_INST
#dev_group
snap
ip_address
HSTA
service
52050
Horcm50.conf on HOST A
horcm51.conf on HOST B
HORCM_MON
HSTA
52050
1000
3000
HORCM_MON
timeout(10ms)
HSTB
52051
1000
HORCM_CMD
#dev_name
\\.\PhysicalDrive0
HORCM_CMD
#dev_name
\\.\PhysicalDrive1
HORCM_DEV
snap
snapdev1 CL2-C
25
1
2
offhost
offdev1 CL2-C
25
3
2
HORCM_DEV
offhost
offdev1 CL2-D
25
1
0
HORCM_INST
#dev_group
snap
offhost
HORCM_INST
#dev_group
offhost
ip_address
HSTA
HSTB
service
52051
52051
Host A for Export

DB
DB
writer
writer
VSS
coordinator
VSHTCHOMRCF
_MUN=2
VSS
VSHTCHORCMINST
provider
_LOCAL =50
VSHTCHORCMINST
REMOTE =51
RAID
Manager
HORCMINST=50
VSS
VSS
requestor
requestor
HORCMINST=51
RAID
Manager
Command
device
PVOL
LU1
PVOL
LU3
Figure A.2
snap
ip_address
HSTA
service
52050
Host B for Import
XML
CL2-C
46
3000
VSS
coordinator
VSS
requestor
VSS
provider
VSHTCHORCMINST
REMOTE =51
RAID
Manager
HORCMINST=51
CL2-D
SVOL
LU2
offhost
RAID
Example of a Mixed Configuration
SVOL
LU1
A.3
Example of a Two-Node Cluster Configuration on a Backup Server

The MSCS volume does not accommodate LUNs with duplicate signatures and a partition
layout. To prevent problems associated with signature corruption, the back-up server must
use the following configuration.
Node 1
Node 2
Node 3
MSCS + VSS
MSCS + VSS
VSS (Backup)
Sig
P-VOL
Figure A.3
Shadow Copy
Sig
S-VOL
Two-Node Cluster Configuration on a Backup Server
47
A.3.1
Example of RM Configurations for Two-Node Cluster Using Virtual IP on MSCS

RAID Manager supports a configuration where the export machine is in a cluster and the
import machine is either in a different cluster or not in the cluster. In the following
example, clusServer is the MSCS virtual IP (virtual host) of the export machine (NODE1 &
NODE2) in a cluster. Pae2 is a back-up server (NODE3) that is outside the cluster.
As the virtual host, clusServer is always available on the active machine in the cluster, and is
transportableregardless of which machine in the cluster is active.
horcm50.conf on NODE1
HORCM_MON
NONE
5000
1000
3000
HORCM_MON
NONE
5000
1000
3000
HORCM_CMD
#dev_name
\\.\PhysicalDrive4
HORCM_CMD
#dev_name
\\.\PhysicalDrive4
HORCM_DEV
#dev_group
snap
offhost
offhost
HORCM_INST
#dev_group
snap
offhost
dev_name
dev1
dev2
dev3

CL2-B-1
1
1
0
CL2-B-1
1
2
0
CL2-B-1
1
3
0
ip_address
pae2
pae2
HORCM_DEV
#dev_group
snap
offhost
offhost
HORCM_INST
#dev_group
snap
offhost
service
5001
5001
dev_name
dev1
dev2
dev3

CL2-B-1
1
1
0
CL2-B-1
1
2
0
CL2-B-1
1
3
0
ip_address
pae2
pae2
VSHTCHOMRCF_MUN=0
VSHTCHORCMINST_LOCAL =50
HORCMINST=50
service
5001
5001
VSHTCHOMRCF_MUN=0
HORCMINST=50
HORCM_MON
timeout(10ms)
pae2
5001
1000
3000
HORCM_CMD
#dev_name
\\.\PhysicalDrive4
HORCM_DEV
#dev_group
snap
offhost
offhost
HORCM_INST
#dev_group
snap
ffh t
dev_name
dev1
dev2
dev3

CL1-C-1
1
1
0
CL1-C-1
1
2
0
CL1-C-1
1
3
0
ip_address service
ClusServer 5000
Cl S
5000
VSHTCHORCMINST_REMOTE =51
HORCMINST=51
Figure A.4
48
Example of RM Configurations for Two-Node Cluster Using Virtual IP on MSCS
A.3.2
Example of RM Configurations for Two-Node Cluster Using Static IP on MSCS

RAID Manager supports a configuration where the export machine is in a cluster and the
import machine is either in a different cluster or not in the cluster. In the following
example, the static IP is used instead of the MSCS virtual IP (virtual host) of the export
machine ( NODE1 & NODE2 ), in a cluster. Pae2 is a back-up server (NODE3) outside of the
cluster.
Note that this configuration does not depend on the MSCS virtual host; an alternate IP (host)
function is executed by RAID Manager.
HORCM_MON
pae3
5000
1000
3000
HORCM_MON
pae4
5000
1000
3000
HORCM_CMD
#dev_name
\\.\PhysicalDrive4
HORCM_CMD
#dev_name
\\.\PhysicalDrive4
HORCM_DEV
#dev_group
snap
offhost
offhost
HORCM_INST
#dev_group
snap
offhost
dev_name
dev1
dev2
dev3
HORCM_DEV
#dev_group
snap
offhost
offhost

CL2-B-1
1
1
0
CL2-B-1
1
2
0
CL2-B-1
1
3
0
ip_address
pae2
pae2
HORCM_INST
#dev_group
snap
offhost
service
5001
5001
dev_name
dev1
dev2
dev3

CL2-B-1
1
1
0
CL2-B-1
1
2
0
CL2-B-1
1
3
0
ip_address
pae2
pae2
VSHTCHOMRCF_MUN=0
HORCMINST=50
service
5001
5001
VSHTCHOMRCF_MUN=0
HORCMINST=50
HORCM_MON
timeout(10ms)
pae2
5001
1000
3000
HORCM_CMD
#dev_name
\\.\PhysicalDrive4
HORCM_DEV
#dev_group
snap
offhost
offhost
HORCM_INST
#dev_group
snap
snap
offhost
offhost
dev_name
dev1
dev2
dev3

CL1-C-1
1
1
0
CL1-C-1
1
2
0
CL1-C-1
1
3
0
ip_address
pae3
pae4
pae3
pae4
service
5000
5000
5000
5000
VSHTCHORCMINST_REMOTE =51
HORCMINST=51
Figure A.5
Example of RM Configurations for Two-Node Cluster Using Static IP on MSCS

49
50
Acronyms and Abbreviations

CCI
CLI
Command Control Interface

command line interface
GUI
graphical user interface
HBA
HDLM
HORC
HORCM
host bus adapter

Hitachi Dynamic Link Manager
Hitachi Open Remote Copy (another term for TrueCopy)
Hitachi Open Remote Copy Manager (name of CCI executable)
IP
internet protocol
KB
kilobyte (1024 bytes)
LAN
LDM
LCP
LDEV
LU
LUN
LUSE
local-area network
logical disk manager
local control port
logical device
logical unit
logical unit number, logical unit
LUN Expansion, LU Size Expansion
MB
MRCF
MU
MUN
megabyte (1024 KB)

Multiple RAID Coupling Feature (another term for ShadowImage)
mirror unit
mirror unit number
NAS
network-attached storage
OS
operating system
PNP
P-VOL
plug-and-play
primary volume (for TrueCopy or ShadowImage)
RAID
redundant array of independent disks
SAN
SCSI
SI
S-VOL
storage-area network
small computer systems interface
ShadowImage
secondary volume (for TrueCopy or ShadowImage)
TC
TID
TrueCopy
target ID
VSS
volume shadow copy service
XML
extensible markup language
51
52
Acronyms and Abbreviations

ShadowCopyProviderforMicrosoftVSSInstallGde RD1660

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ShadowCopyProviderforMicrosoftVSSInstallGde RD1660

Enviado por

Direitos autorais:

Formatos disponíveis

Hitachi RAID Manager Shadow Copy Provider

2004 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED

Notice of Export Controls

Hitachi RAID Manager for VSS Installation Guide

Document Revision Level

Source Documents for this Revision

RM Shadow Copy Provider Basic Specifications (RMVSS4), version 01-02-03/02

RM Shadow Copy Provider Basic Specifications (RMVSS5), version 01-02-03/02

RAID Manager Basic Specifications (RMHORC52), version 52

Hitachi RAID Manager for VSS Installation Guide

Introducing RAID Manager Shadow Copy Provider ............................................................1

Installing RAID Manager Shadow Copy Provider ..............................................................15

Reviewing the Prerequisites ..................................................................

Performing VSS Operations ................................................................................................21

VSS Start-up Procedures on a Single Host ..................................................

General Troubleshooting ......................................................................

Hitachi RAID Manager for VSS Installation Guide

Appendix A: Examples of Complex Configurations ..............................................................................45

Example of a Transportable Host Configuration Using Multiple Volumes .............. 45

Acronyms and Abbreviations ...................................................................................................................51

Single-Host Configuration for VSS Provider ............................................ 3

System Environment Variables.......................................................... 22

Example of Environment Variables for a Transportable Host Configuration .... 45

Hidden Property of SVOL and Performance Characteristic.......................... 7

Windows 2003 Enterprise Server and RM Shadow Copy Provider Requirements 16

General Troubleshooting for VSS Provider ............................................ 38

Introducing RAID Manager Shadow Copy Provider

Overview (see section 1.1)

Reviewing the VSS Provider Configurations (see section 1.2)

Reviewing the Restrictions for VSS Configurations (see section 1.3)

Reviewing the Implementation Configuration for RM Shadow Copy Provider

Hitachi RAID Manager for VSS Installation Guide

Chapter 1 Introducing RAID Manager Shadow Copy Provider

Reviewing the Three VSS Configurations

Export and Import Host

Single Host Configuration

Single-Host Configuration for VSS Provider

Hitachi RAID Manager for VSS Installation Guide

Export and Import Host Configuration

Host A for Export

Host B for Import

Export and Import Host Configuration for VSS Provider

Chapter 1 Introducing RAID Manager Shadow Copy Provider

Transportable Configuration for VSS Provider

OFFHOST configuration import option (steps 10-13 in section 1.2.4)

RAID Manager Command Line Interface

Hitachi RAID Manager for VSS Installation Guide

Reviewing the Processes that Coordinate to Create a Shadow Copy

Chapter 1 Introducing RAID Manager Shadow Copy Provider

Reviewing the Restrictions for VSS Configurations

Property of the Shadow Copy volume

Snapshots containing dynamic disks

Hardware snapshots not supported on MSCS

Using VSS under the I/O path manager

I/O during RM shadow copy provider

Property of the Shadow Copy volume

Hidden Property of SVOL and Performance Characteristic

SVOL Hidden Property

9900V, TagmaStore USP,

Hitachi RAID Manager for VSS Installation Guide

Snapshots Containing Dynamic Disks

[ where X is an instance number ]

Chapter 1 Introducing RAID Manager Shadow Copy Provider