GuardianOS™, RAINcloud™, SnapDisk™, SnapEDR™, Snap Enterprise Data Replicator™, SnapExpansion™, SnapSAN™, SnapScale™,
SnapServer DX Series™, SnapServer Manager™, SnapWrite™, and SnapServer Manager™ are trademarks of Overland Storage, Inc.
All other brand names or trademarks are the property of their respective owners.
The names of companies and individuals used in examples are fictitious and intended to illustrate the use of the software. Any resemblance to
actual companies or individuals, whether past or present, is coincidental.
PROPRIETARY NOTICE
All information contained in or disclosed by this document is considered proprietary by Overland Storage. By accepting this material the recipient
agrees that this material and the information contained therein are held in confidence and in trust and will not be used, reproduced in whole or
in part, nor its contents revealed to others, except to meet the purpose for which it was delivered. It is understood that no right is conveyed to
reproduce or have reproduced any item herein disclosed without express permission from Overland Storage.
Overland Storage provides this manual as is, without warranty of any kind, either expressed or implied, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose. Overland Storage may make improvements or changes in the product(s) or
programs described in this manual at any time. These changes will be incorporated in new editions of this publication.
Overland Storage assumes no responsibility for the accuracy, completeness, sufficiency, or usefulness of this manual, nor for any problem that
might arise from the use of the information in this manual.
, VR2®, and XchangeNOW® are registered trademarks of Overland Storage, Inc.
Overland Storage, Inc.
9112 Spectrum Center Blvd.
San Diego, CA 92123
U.S.A.
This user guide explains how to install, setup, and use the SnapSAN VSS Provider software.
VSS Provider is software that facilitates business backup operations by linking the Volume Shadow Copy
Service (VSS) of Microsoft® Windows Server® 2003 or Microsoft® Windows Server® 2008 with data
replication (VSS Storage Volume Cloning or VSS Provider Replication and Mirroring) and a snapshot
function (VSS Provider Snapshots).
This guide assumes that you are familiar with computer hardware, data storage, and network
administration terminology and tasks. It also assumes you have basic knowledge of Internet SCSI (iSCSI),
Serial-attached SCSI (SAS), Serial ATA (SATA), Storage Area Network (SAN), and Redundant Array of
Independent Disks (RAID) technology.
This guide is intended for those who have basic knowledge of backup and recovery using Microsoft Windows
Server 2003 or Microsoft Windows Server 2008 and the VSS Provider snapshot function or data replication
function.
This manual explains functions implemented by the following program products:
•VSS Provider Manager and VSS Provider base product
•VSS Provider Control Command
This manual is applicable to the program products of the following versions:
•VSS Provider Manager Ver4.2 or later
•VSS Provider Base Product Ver4.2 or later
•VSS Provider Control Command Ver4.2 or later
The VSS Provider series disk array subsystems is referred to as a disk array in this manual unless clearly
specified.
Product Documentation and Firmware Updates
Overland Storage SnapSAN product documentation and additional literature are available online, along
with the latest release of the SnapSAN VSS software.
Point your browser to:
http://docs.overlandstorage.com/snapsan
Follow the appropriate link to download the latest software file or document. For additional assistance,
search at http://support.overlandstorage.com
This document exercises several alerts and typographical conventions.
Alerts
ConventionDescription & Usage
IMPORTANTAn Important note is a type of note that provides information essential to
the completion of a task or that can impact the product and its function.
CAUTIONA Caution contains information that the user needs to know to avoid
damaging or permanently deleting data or causing physical damage to
the hardware or system.
WARNING A Warning contains information concerning personal safety. Failure to
follow directions in the warning could result in bodily harm or death.
Typographical Conventions
ConventionDescription & Usage
Button_name
Ctrl-Alt-rThis type of format details the keys you press simultaneously. In this
NOTEA Note indicates neutral or positive information that emphasizes or
Menu Flow
Indicator (>)
Courier ItalicA variable for which you must substitute a value
Courier Bold
Words in this special boldface font indicate command buttons found in
the Web Management Interface.
example, hold down the Ctrl and Alt keys and press the r key.
supplements important points of the main text. A note supplies
information that may apply only in special cases, for example, memory
limitations or details that apply to specific program versions.
Words with a greater than sign between them indicate the flow of actions
to accomplish a task. For example, Setup > Passwords > User indicates
that you should press the
finally the
Commands you enter in a command-line interface (CLI)
User button to accomplish a task.
Setup button, then the Passwords button, and
Information contained in this guide has been reviewed for accuracy, but not for product warranty
because of the various environments, operating systems, or settings involved. Information and
specifications may change without notice.
A discharge of static electricity can damage static-sensitive devices. Proper packaging and grounding
techniques are necessary precautions to prevent damage. To prevent electrostatic damage, observe
the following precautions:
•Transport products in static-safe containers such as conductive tubes, bags, or boxes.
•Cover the appliance with approved static-dissipating material.
•Use a wrist strap connected to the work surface and properly-grounded tools and equipment.
•Keep the work area free of non-conductive materials such as foam packing materials.
•Make sure you are always properly grounded when touching a static-sensitive component or
Snapshot or Data Replication ............................................................................................................................. 3-3
Data Replication Installation ......................................................................................................................... 3-3
Initial Setup of Volumes .................................................................................................................................. 3-4
Backup Server Connected to Data Replication Volume (RV) .................................................................. 3-5
Backup and Restore Procedures .................................................................................................................. 3-5
Contents
Chapter 4 - Error Management
Actions When Error Occurs .................................................................................................................................. 4-1
When Backup has Errors ................................................................................................................................. 4-1
When VSS must be Restarted ........................................................................................................................ 4-1
When Returning Volume to Initial State ....................................................................................................... 4-1
Backup Server Connected to Snapshot LV .................................................................................................4-1
Backup Server Connected to Data Replication RV ................................................................................... 4-2
Collecting Information of Unclear Failure .................................................................................................... 4-3
Chapter 5 - Troubleshooting
About Snapshot or Data Replication ........................................................................................................... 5-1
This chapter provides an overview of the Volume Shadow Copy Service (VSS) and explains
system configuration and other fundamentals.VSS was implemented in Microsoft Windows
Server 2003 and Microsoft Windows Server 2008, as a new function for performing storage
management. The graphic shows a basic VSS Configuration made up of backup software
(requestor), business applications (writers), and software that performs disk array shadow
copy (replication) instructions (VSS provider).
Backup using VSS is performed by taking a request from the requestor as a trigger. When
VSS receives a backup request from the requestor, it performs coordinating operations with
the writers and provider, and it instructs the provider to create a replication. This series of
operations is performed entirely under the control of VSS. Accordingly, a user can easily
carry out non-interrupting backup without becoming involved with complicated scripts for
each application, just by executing the requestor.
A hardware provider is software exclusively for the in-house manufactured disk arrays
(supplied by the storage vendor), makes it possible to create shadow copies using hardwarespecific replication functions. VSS Provider is a hardware provider.
A software provider is software that a software vendor supplies for creating shadow copies.
The system provider that is supplied by Microsoft Corporation is also a software provider.
Software Required
The following software is needed on each server or disk array:
Application Server
•Job management software (Example: JobCenter)
•Requestor (Example: Protection Manager)
•Exchange Server 2003
•VSS Provider
•Control Command
Backup Server
•Job management software (Example: JobCenter)
•Requestor (Example: Protection Manager)
•Backup software (Example: NetBackup)
•VSS Provider
•Control Command
Management
•SnapSAN Manager
Disk Array
•Snapshots, Volume Cloning, or Replication and Mirroring
•Access Control
Volume Types
VSS Provider handles volumes that are subject to snapshot or replication operations by a
disk array’s logical disk.
Requestors
Server
VSS Provider supports Protection Manager and other software as requestors. For
introductions about each requestor, refer to the product-specific manual.
VSS Provider Installation and Operation Procedures
This example shows the system installation procedure by taking a tape backup system in
which the D series is used as an example. For the snapshot environment installation
procedure, refer to
Windows)”. For the data replication environment installation procedure, refer to the “Data
Replication User's Manual (Installation and Operation Guide for Windows)”. For hardware
configurations and software configurations, refer to the configurations in this manual. For
requestor installation procedures and operating procedures, refer to the manuals of the
selected requestor. Highlighted portions below are procedures to perform by
other manuals
the “Snapshot
User’s Manual (Installation and Operation Guide for
The configuration example shows: hardware components, performance requirements, and disk
capacity.
Figure 3-1: Hardware Configuration Example
To utilize the snapshot or data replication function more efficiently, separate the application
servers, which process tasks from the backup servers. Accordingly, the tape backup
operation gives no additional load to application servers.
Though the application or backup server may also be used as a management server, using a
specific management server is recommended. Use of LAN connection is strongly
recommended for connection with the disk array.
Connect the path of individual servers, to be connected to the disk array, to the port of
different directors of the disk array, limiting the servers to be accessed by AccessControl.
The example shows a software configuration. Select the software to use from the business
equipment and operations mode. The software configuration varies according to the
requestor selected.
Figure 3-2: Software Configuration Example
Hardware Required
To install and use VSS Provider, the following hardware is needed:
Disk Array – This is a disk array in which the snapshot function (Snapshots) or data
replication function (Volume Cloning or Replication and Mirroring) is loaded.
Application Server – This performs snapshot or data replication operations.
Backup Server – This is arranged to perform backup of data from a replication to tape or
other media.
Magnetic Tape Unit – This is used if tape backup is needed. Use a tape unit that is
supported by the backup software.
Management Server – This performs a disk array management. It can also serve as the
backup server or application server.
•Snapshots, Volume Cloning, or Replication and Mirroring
•AccessControl
er
Snapshot or Data Replication
Snapsho
Data Replicat
t Installation
Refer to the “Snapshot User’s Manual (Installation and Operation Guide for Windows)” for
system configuration determination and subsequent installation procedures and concerns
when performing operations. Perform through “Installation Procedure” there to prepare for
backup operations in which the snapshot function is used.
ion Installati
Refer to the “Data Replication User's Manual (Installation and Operation Guide for
Windows)” for system configuration determination and subsequent installation procedures
and concerns when performing operations. Perform through “Installation Procedure” there
to prepare for backup operations in which the data replication function is used.
Requestor Installation
For concerns when installing a requestor, refer to the manuals of the selected requestor.
Volume Types
VSS Provider handles volumes that are subject to snapshot or replication operations by a
disk array’s logical disk. When there are multiple partitions or logical volumes on one logical
disk, depending on the operation, it may not be possible to guarantee data consistency if a
replication operation is executed for a volume made up of multiple partitions or logical
volumes or for a dynamic disk volume. The table below shows the function range for each
disk.
When performing backup operations in which the snapshot function is used, the initial
setup below is necessary. Execute identical operations for target volumes used in backup
operations. The
“Snapshot User’s Manual (Installation and Operation Guide for Windows) ended, are
assumed to be “active” for the SV state and “unlink” for the LV link state.
rver Connected to Snapshot Logical Volume (
volume states
√
Primary partition (GPT format)
Logical volume on expanded partition
Simple volume
Spanned volume
Striped volume
Mirror volume
RAID5 volume
LV)
, which are the states in which “Installation Procedure” in the
√
-
-
-
-
-
-
1. Start a command prompt on the backup server.
2. Confirm that volumes used in backup operations have been registered in the volume
list created in (Installation and Operation Guide for Windows)” and re-create the
volume list.
> iSMvollist -a
3. In order to change the LV access restriction to Not Available (NA), stop the volume
beforehand.
Here, the setting is made for logical disk name lv001.
> iSMvss -devmode disable -vol lv001 -volflg ld
4. Change the LV access restriction to Not Available (NA). Here, settings are made for
When performing backup operations in which the data replication function is used, the
initial setup below is necessary. Execute identical operations for target volumes used in
backup operations.
1. Start a command prompt on the backup server.
2. Confirm that volumes used in backup operations have been registered in the volume
list created in “Data Replication Installation”.
a. If they are not registered, refer to the “Data Replication User’s Manual
(Installation and Operation Guide for Windows)” and re-create the volume list.
> iSMvollist -a
b. If the RV is replicate state, execute Separate to separate the Master Volume (MV)
and RV and make the RV available. Here, execute using the settings below. If the
RV is separated, the command below need not be executed.
•Access restriction for RV after separated: rw (Read/Write) (Default value)
This chapter explains how to address errors that occur during backup when VSS Provider is
used.
When Backup has Errors
When an error has occurred during backup, investigate the cause of the error using the
procedure below and re-execute the backup after eliminating the cause of the error.
1. Verify if the error was output in the application’s event log.
2. If you were able to confirm the error number and error message, check Appendix A
“Error Messages at Time of Failure”.
3.
Refer to the explanation in (Measure) and eliminate the cause of the error.
If there are unformatted partitions, a warning may be output to the (application) event log
when executing VSS backup.
“Event Log Warning Message.
Error Management
This does not affect backup processing. For details, refer to
When VSS must be Restarted
When the VSS must be restarted, follow the instructions:
1. From the Windows (Start) button, select (Administrative Tools) > (Services).
2. Select (VSS Provider) and restart it.
3. Confirm that the service was started.
When Returning Volume to Initial State
Sometimes, an LV or RV for performing VSS backup enters a state in which backup is not
possible because of an error during backup. To initialize the state of the LV or RV to a state
in which re-execution is possible, different operations are needed for operation in which the
snapshot function is used and operation in which the data replication function is used.
Execute the operations for LV or RV for which backup failed.
If Protection Manager is selected as a requester, troubleshoot by referring to the “CLI
Command Reference Guide”.
Backup Se
rver Connected to Snapshot L
This section describes the procedure that returns a volume to its initial state when an error
occurred during operation using the snapshot function. Execute the procedure below for all
volumes subject to backup.
a. If the target volume is already canceled, the message below is output.
iSMsc_svguard:Info: iSM19127: Request has already completed.
The above is the end of the volume initialization procedure for operation using the snapshot
function.
rver Connected to Data Replication
RV
This section describes the procedure that returns a volume to its initial state when an error
occurred during operation using the data replication function. Execute the procedure below
for all volumes subject to backup.
Start a command prompt on the backup server.
1. Check the RV state. Here, the state of logical disk name rv001 is checked.
The above is the end of the volume initialization procedure for operation using the data
replication function.
Collecting Information of Unclear Failure
Even when performing the procedures above, if an error occurs during backup, execute the
commands in the procedure below to gather an operation trace and other fault information.
Login as Administrator.
1. Click the Windows [Start] button, and select and execute [All Programs] →
[ControlCommand] →[SnapSAN Manager Volume List] → [Difficulty Information
Gather]. When changing the directory of the storage destination and executing,
specify a directory on the appropriate server and do not specify a directory on a
separate server connected by a network.
2. Confirm that the iSMvolgather directory is created under the installation directory
when the storage destination directory is not changed or under the specified directory
when it is changed, and obtain the files under that directory.
Moreover, since VSS Provider utilizes the snapshot or data replication function, if a failure
occurs, also refer to the measures for errors described in the “Snapshot User’s Manual
(Installation and Operation Guide for Windows)” or the “Data Replication User’s Manual
(Installation and Operation Guide for Windows)”.
For problems that occur when operating the snapshot or data replication function, refer to
the notes described in the “Snapshot User’s Manual (Installation and Operation Guide for
Windows)” or the “Data Replication User’s Manual (Installation and Operation Guide for
Windows)”.
NOTE: The concerns in snapshot and data consistency described in the “Snapshot User’s Manual
(Installation and Operation Guide for Windows)” and the concerns in data replication and
data consistency described in the “Data Replication User’s Manual (Installation and
operation Guide for Windows)” are resolved by using VSS.
Event Log Warning Message
If there is even one unformatted partition on the server that executes VSS backup
(including volumes not subject to backup), the (sample) warning below may be output to the
(application) event log. This applies to SnapSAN Manager cluster partitions and others.
For Windows Server 2008, if there is a volume on the backup server whose state is Not
Ready, such as an RV being replicated or LV being unlinked, the (example) error below may
be output to an event log of the backup server by performing a VSS backup.
Table 5-1: Output Example
Variable Output
Log name System
Typ eEr ror
Source: Virtual Disk Service
Event ID:1
Explanation An unexpected error occurred
Error code 13@02000018
Log name: Application
Typ eEr ror
Source:VSS
Event ID 12289
Explanation Volume shadow copy service error: Unexpected error
IOCTL_DISK_GET_DRIVE_LAYOUT_EX
This error does not affect the operation.
Stopping Service
To stop the (VSS Provider) service of during regular operation, follow the procedure
below.
1. Stop the (Volume Shadow Copy) service.
2. Stop the (VSS Provider) service.
Path Manager Warning Message
The Path Manager version to be used must be V3.3 or later.If Path Manager has been
installed, the warning below may be output in the (application) event log.
Type:
Warning
Source:spsdsm
Event ID:530
Description:A path is lost.
To replace this warning message with an information message, follow the procedure below.
1. Start a command prompt on the backup server.
2. Execute the following: command:
> spscmd -seteventmode 1
The above is the end of the setting of Path Manager.
The “Message List” provides explanations of the error messages that are output to the event
log in message ID order. An explanation of each message is given in the format below.
iSMxxxxx: AAAAA<aaa>,<bbb...b>
Message ID (iSMxxxxx) and message body (AAAAA<aaa>,<bbb...b>) are
described
Descriptions using angle brackets such as <aaa> and <bbb...b> indicate that parameter
values are not fixed. (The angle brackets “<” and “>” are not displayed in the actual
message.)
For details on parameter values, refer to Explanation
TermDescription
Typ e Message classification (ERROR,
WARNING, or INFO) is described.
ExplanationThis field describes the causes of
the message output, etc.
Parameters in the message are
also described in this field.
iSM13852: Specified volume does not exist in a vollist file.
Ter mDescription
Typ e
Explanation
ERROR
Shows that VSS Provider was called by a process that does not have Administrator
SerialNumber=<aaa...a>,
privileges.
Measure
Re-execute following login to the Windows OS by a user who has Administrator
privileges.
ldn=<bbb... b>.
TermDescription
Typ e ERROR
ExplanationShows that the specified volume does not exist in the volume list. aaa...a: Unit serial
number
bbb...b: Logical disk number
MeasureRe-create the volume list by referring to the “Snapshot User’s
Operation Guide for Windows)” or the “Data Replication User’s Manual (Installation and
Operation Guide for Windows)”.
Manual (Installation
iSM13853: Specified volume <aaa...a> is not paired.
and
Ter mDescription
Type ERROR
ExplanationShows that the logical disk indicated by aaa...a was not paired or was forcibly unpaired.
aaa...a: Logical disk name
MeasureAfter checking messages output by ControlCommand, check whether there is a
mistake in setup by referring to the “Data Replication User’s Manual (Installation and
Operation Guide for Windows)” or 2.6.2 “For Backup Server Connected to Data
Replication RV”.
iSM13854: No suitable RV was found for MV <aaa...a>.
Ter mDescription
Type ERROR
ExplanationShows that the logical disk indicated by aaa...a was not paired or was forcibly unpaired.
aaa...a: Logical disk name
MeasureAfter checking messages output by ControlCommand, check whether there is a mistake
in setup by referring to the “Data Replication User’s Manual (Installation and Operation
Guide for Windows)” or 2.6.2 “For Backup Server Connected to Data Replication RV”.
iSM13858: Memory allocation (malloc) error.
Ter mDescription
Typ e ERROR
ExplanationAllocation of a memory area failed.
MeasureIt is possible that the memory area is insufficient. To use this program, secure free
iSM13859: Failed to replicate. MV=<aaa...a>, RV=<bbb...b>.
iSM13860: Parameter error. (Invalid Snapshot Set ID
TermDescription
Typ e ERROR
ExplanationReplication failed.
MeasureAfter checking messages output by ControlCommand, check whether there is a mistake
<aaa...a>)
Ter mDescription
Typ e ERROR
ExplanationA parameter error occurred. The Snapshot Set ID is invalid. aaa...a: Snapshot Set ID
MeasureAfter saving the information below, restart the VSS Provider service by referring to
aaa...a: MV logical disk name bbb...b: RV logical disk name
in setup by referring to the “Data Replication User’s Manual (Installation and Operation
Guide for Windows)” or 2.6.2 “For Backup Server Connected to Data Replication RV”.
Chapter 3 “Actions When Error Occurs”.
• ControlCommand operation log (iSMrpl.log)
•Event log
iSM13861: Failed in waiting for the synchronized state. MV=<aaa...a>, RV=<bbb...b>.
Ter mDescription
Typ e ERROR
ExplanationA wait for completion of replication failed. aaa...a: MV logical disk name
bbb...b: RV logical disk name
MeasureAfter checking messages output by ControlCommand, check whether there is a
mistake in setup by referring to the “Data Replication User’s Manual (Installation and
Operation Guide for Windows)” or 2.6.2 “For Backup Server Connected to Data
Replication RV”.
iSM13862: Failed to separate. MV=<aaa...a>, RV=<bbb...b>.
Ter mDescription
Typ e ERROR
ExplanationSeparation failed.
aaa...a: MV logical disk name bbb...b: RV logical disk name
MeasureAfter checking messages output by ControlCommand, check whether there is a mistake
in setup by referring to the “Data Replication User’s Manual (Installation and Operation
Guide for Windows)” or 2.6.2 “For Backup Server Connected to Data Replication RV”.
iSM13863: Failed in waiting for the separated state. MV=<aaa...a>, RV=<bbb...b>.
ExplanationA wait for completion of separation failed. aaa...a: MV logical disk name
MeasureAfter checking messages output by ControlCommand, check whether there is a mistake
bbb...b: RV logical disk name
in setup by referring to the “Data Replication User’s Manual (Installation and Operation
Guide for Windows)” or 2.6.2 “For Backup Server Connected to Data Replication RV”.
ExplanationA parameter error occurred. The LUN information is invalid.
MeasureAfter saving the information below, restart the VSS Provider service by referring to
iSM13865: Failed to change LUN <aaa...a> to data-valid state.
Ter mDescription
Typ e ERROR
ExplanationShows that a snapshot attribute change failed.aaa...a: Logical disk name of operation
MeasureIf you select Protection Manager as a requester, after checking the state and pairing of
Chapter 3 “Actions When Error Occurs”.
• ControlCommand operation log (iSMrpl.log)
•Event log
target (RV)
the logical disk, set the volume to its initial state by referring to the “Protection Manager
CLI User’s Guide”. If you select a different requester, set the volume to its initial state by
referring to Chapter 3 “Actions When Error Occurs”.
iSM13866: Failed to change LUN <aaa...a> from
NotAvailable state.
Ter mDescription
Typ e ERROR
ExplanationShows that snapshot volume unmasking failed. aaa...a: Logical disk name of
operation target (RV or LV)
MeasureIf you select Protection Manager as a requester, after checking the state and pairing of
the logical disk, set the volume to its initial state by referring to the “Protection Manager
CLI User’s Guide”. If you select a different requester, set the volume to its initial state by
referring to Chapter 3 “Actions When Error Occurs”.
iSM13872: Failed to change LUN <aaa...a> to data-invalid state.
Ter mDescription
Typ e ERROR
ExplanationShows that a snapshot attribute change failed.
MeasureIf you select Protection Manager as a requester, after checking the state and pairing of
the logical disk, set the volume to its initial state by referring to the “Protection Manager
CLI User’s Guide”. If you select a different requester, set the volume to its initial state by
referring to Chapter 3 “Actions When Error Occurs”.
iSM13874: No suitable SV was found for BV <aaa...a>.
Ter mDescription
Typ e ERROR
ExplanationShows that no SV suitable for VSS backup was found for the logical disk name indicated
Measure After checking messages output by ControlCommand, check whether there is a
iSM13875: Failed to create. BV=<aaa...a>, SV=<bbb...b>.
TermDescription
Typ e ERROR
ExplanationShows that snapshot creation failed. aaa...a: BV logical disk name bbb...b: SV logical
MeasureAfter checking messages output by ControlCommand, check whether there is a mistake
by aaa...a.
aaa...a: Logical disk name
mistake in setup by referring to the “Snapshot User’s Manual (Installation and
Operation Guide for Windows)” or 2.6.1 “For Backup Server Connected to Snapshot LV”.
disk name
in setup by referring to the “Snapshot User’s Manual (Installation and Operation Guide
for Windows)” or 2.6.1 “For Backup Server Connected to Snapshot LV”.
iSM13876: Failed in waiting for the active state. BV=<aaa...a>, SV=<bbb...b>.
Ter mDescription
Typ e ERROR
ExplanationShows that a wait for snapshot completion failed. aaa...a: BV logical disk name
bbb...b: SV logical disk name
MeasureAfter checking messages output by ControlCommand, check whether there is a mistake
in setup by referring to the “Snapshot User’s Manual (Installation and Operation Guide
for Windows)” or 2.6.1 “For Backup Server Connected to Snapshot LV”
iSM13877: Failed to import. LDNAME=<aaa…a>.
TermDescription
Typ e ERROR
ExplanationShows that importing of a snapshot failed
aaa...a: Logical disk name of import target (RV or LV)
MeasureIf you select Protection Manager as a requester, after checking the state and pairing of
the logical disk, set the volume to its initial state by referring to the “Protection Manager
CLI User’s Guide”. If you select a different requester, set the volume to its initial state by
referring to Chapter 3 “Actions When Error Occurs”.
It is also possible that the control volume was not set. Check the control volume setting.
iSM13880: Environment variable 'iSMrpl' not defined.
TermDescription
Typ e ERROR
ExplanationThe environment variable iSMrpl is not defined. [Measure] Confirm that
MeasureIf ControlCommand is installed, restart the server.
iSM13881: Environment variable 'iSMvol' not defined.
Ter mDescription
Typ e ERROR
ExplanationThe environment variable iSMvol is not defined. [Measure] Confirm that
MeasureIf ControlCommand is installed, restart the server.
iSM13882: LD attribute is neither MV nor BV. (ldattr=<a>)
ControlCommand has been installed.
ControlCommand has been installed.
iSM13883: The specified pair is in the restore state. MV=<aaa...a>, RV=<bbb...b>.
Ter mDescription
Typ e ERROR
Explanation[Explanation] The logical disk to be backed up is not the MV or BV. a:Internal number
showing type of logical disk
0: IV
4: RV
8: LV
16: SV
Measure[Measure] If you select Protection Manager as a requester, after checking the state and
pairing of the logical disk, set the volume to its initial state by referring to the “Protection
Manager CLI User’s Guide”. If you select a different requester, set the volume to its
initial state by referring to Chapter 3 “Actions When Error Occurs”.
Ter mDescription
Typ e ERROR
ExplanationThe specified pair is in a restore state. aaa...a: MV logical disk name bbb...b: RV
logical disk name
MeasureCheck the activity state of the specified pair and change it to separated or replicate
iSM13884: Failed to change copy control state. MV=<aaa...a>, RV=<bbb...b>.
TermDescription
Typ e ERROR
ExplanationA copy control state change failed. aaa...a: MV logical disk name bbb...b: RV logical
MeasureAfter checking messages output by ControlCommand, check whether there is a mistake
iSM13885: The parameter control file analysis error. (<aaa...a>=<bbb...b>)
TermDescription
Typ e ERROR
Explanation[Explanation] Parameter control file analysis failed. aaa...a: Parameter control file key
Measure[Measure] After saving the information below, restart the VSS Provider service by
disk name
in setup by referring to the “Data Replication User’s Manual (Installation and Operation
Guide for Windows)” or 2.6.2 “For Backup Server Connected to Data Replication RV”.
name bbb...b: Value corresponding to key name
referring to Chapter 3 “Actions When Error Occurs”.
y ControlCommand operation log (iSMrpl.log)
y Event log
iSM20502: Illegal control option.
TermDescription
Typ e ERROR
ExplanationThe iSMvss command syntax is invalid.
MeasureSpecify parameters correctly.
iSM20503: Environment variable ‘iSMrpl’ is not defined.
Ter mDescription
Typ e ERROR
ExplanationControlCommand is not correctly installed.
MeasureInstall ControlCommand correctly.
iSM20504: Insufficient option. (<aaa…a>)
Ter mDescription
Type ERROR
ExplanationA required iSMvss command option is not specified. aaa…a: Unspecified option
This parameter must be specified together with -vol. The vol_flg that can be specified here is
limited to ld.
[USAGE]
(1) Change the state of OS recognition for a LV to stop state (disable).
A message is not output if the command succeeds.
C:\> iSMvss-devmode disable-vollv001-volflgld
C:\>
(2) If the state of OS recognition for a LV could not be changed to stop state (disable)
C:\> iSMvss-devmode disable-vollv001-volflgld iSMvss: Err:iSM20519: Specified disk
cannot be disabled. C:\>
[NOTES]
•
iSMvss cannot be executed if the access restriction of the LV or RV subject to the
operation is
“na”.
•
iSMvss cannot be executed if the state of OS recognition for the LV or RV subject to the
operation is the same as the specified state.
•
iSMvss cannot be executed if the disk array in which the LV or RV subject to the
operation is stored is in a frozen state.
[RETURN VALUE]
0: Change of state of OS recognition of LV or RV terminated normally.
1: Change of state of OS recognition of LV or RV terminated abnormally. iSMvss
terminates abnormally in the following cases.
- A parameter is invalid.
- A condition for operation is not satisfied.
- An attempt to operate a disk array fails.
iSMvss_clear
[NAME]
iSMvss - Initializes device entry information.
[SYNOPSIS]
iSMvss_clear iSMvss_clear delete
[DESCRIPTION]
The iSMvss_clear command changes all the volumes that were set to the disable state
(which prevents volumes from being recognized by the OS) by the iSMvss command to the
enable state (which allows volumes to be recognized by the OS).
This command also deletes unnecessary device entry information from the registry.
The iSMvss_clear command recognizes the following options:
NoneChanges all the volumes to the enable state (which allows volumes to be recognized by
the OS).
deleteDeletes unnecessary device entry information from the registry.
[USAGE]
(1) Change all the volumes that were set to the disable state (which prevents volumes from
being recognized by the OS) by the iSMvss command to the enable state (which allows
volumes to be recognized by the OS).
Use this command by registering it to the task scheduler so that it is executed at computer
startup.
C:\> iSMvss_clear
C:\>
(2) Delete unnecessary device entry information from the
regi
stry.
Execute this command after performing a backup using VSS.
C:\> iSMvss_clear delete
C:\>
•
If a computer is restarted when a device is in the disable state (which prevents the device
from being recognized by the OS), a backup using VSS after computer startup may fail.
Register the iSMvss_clear command (with no option) to the task scheduler so that it is
executed at computer startup.
•
Unnecessary device entry information accumulates when a backup using VSS is
repeated.
If the amount of such information increases, the OS may fail to recognize Plug and Play
devices. Execute the iSMvss_clear delete command after performing a backup using VSS.