This document provides details on the Volume Shadow Copy Service (VSS), which allows you to conduct a hot backup of data
(snapshots) without stopping online applications.
Part Number: Z7550-01742R
Published: January 2016
Edition: 2
User edit files......................................................................................................................................37
The Volume Shadow Copy Service (VSS) provides a backup function that generates consistent
point-in-time copies of data known as snapshots.
VSS lets you conduct a hot backup of data without stopping online applications by linking
applications, backup software, and disk array systems that are supported by VSS.
VSS consists of the following components:
•Provider — The provider actually creates snapshots. The provider consists of a software
component that comes with the OS and a hardware component which may be acquired from
some source such as a disk array vender. The VSS provider described in this manual is the
hardware component.
•Writers — The writer quiesces the OS or an application and will flush data as needed in
order to create a consistent state. Only operating systems and applications that include a
VSS writer can work with VSS.
•Requester — This component requests creation, operation, or deletion of snapshots. Usually
backup and recovery software like Microsoft’s Data Protection Manager, or HPE Data
Protection Suite can operate as a VSS requester.
•VSS — This service in the Windows operating system operates as a coordinator for the
provider, the writers, and the requester.
Figure 1 Concept of VSS.png
Overview of the VSS Provider
The VSS Provider is a program that controls a data backup function and works with the Microsoft
Volume Shadow Copy Service (VSS). It uses Business Copy, Snapshot or Fast Snap in Hewlett
10Volume Shadow Copy Service
Packard Enterprise disk array systems such as the XP P9500 and the XP7. This program delivers
backup integration operations with VSS. This program provides the following functions:
•VSS provider — HPE XP Storage Adapter for Microsoft® Volume ShadowCopy Service is
a fully-functional VSS implementation. The provider performs copy control of the Business
Copy or Snapshot pair in the disk array system targeted for a backup.
•GUI tools — With the GUI tools you can confirm and set up the configuration necessary for
the VSS Provider's operation.
Figure 2 Backup image
Overview of the VSS Provider11
2 Environmental Prerequisites
System configuration
The system configuration requirements for VSS Provider are shown below.
•The HPE VSS Hardware provider must be installed on both the backup and recovery
application server (such as the media server in a Symantec NetBackup environment) and
the application server (such as a Microsoft Exchange server) from which a backup will be
taken.
•Table 1 (page 12) shows the connection of I/O path between servers and disk array systems
and the connection that VSS Provider gives an operation direction to the disk array systems
for FC environment support.
•In the case of XP P9500/XP7, the command device must be mapped on an application
server and a backup server.
•IPv6 is not supported.
•Fiber channel switches are not always required. Use them according to your environment
as needed.
•Multiple disk array systems can be connected to both an application server and a backup
server.
•For the application server, a cluster configuration using MSCS (MSFC) is also possible. (For
the backup server, this configuration is impossible.)
•The necessity of using the same operating system on both the backup server and the
application server depends on the backup software.
Table 1 Server and disk array systems connection
Examples of supported system configurations
VSS Provider supports the following system configurations.
Figure 3 (page 13) shows a similar configuration using a XP P9500/XP7 disk array system.
Connection between servers/disk array systems for
FC environment
I/O pathHost portDisk array system
Path for an operation
direction
Must be connected with FCMust be connected with FCFCXP P9500/XP7
12Environmental Prerequisites
Figure 3 Example of a VSS provider system configuration [XP P9500/XP7]
Example of VMware Guest to Guest Backup (FC) function system configuration
VMware Guest to Guest Backup (FC) function is that VSS Provider backups P-VOL connected
to ESXi with FC and VM on ESXi is used as an import server of replicated secondary VOL.
In case of using the VMware Guest to Guest Backup (FC) function, the following system
configurations are supported.
Nontransportable configuration
This is the configuration to backup in the Nontransportable configuration in which the secondary
VOL is imported to the virtual machine to be used as the application server.
System configuration13
Figure 4 Example of VMware Guest to Guest Backup (FC) function system configuration
(Nontransportable configuration)
Transportable configuration (one ESXi)
This is the configuration in which the virtual machines for the application server and backup
server uses are located on the same ESXi.
14Environmental Prerequisites
Figure 5 Example of VMware Guest to Guest Backup (FC) function system configuration
(Transportable configuration (one ESXi))
Transportable configuration (separate ESXi)
This is the configuration in which the virtual machines for the application server and the backup
server uses are located on the separate ESXi.
System configuration15
Figure 6 Example of VMware Guest to Guest Backup (FC) function system configuration
(Transportable configuration (separate ESXi))
16Environmental Prerequisites
Examples of Ext Stor configuration
VSS Provider supports the following Ext Stor configurations.
Figure 7 Example of Ext Stor configuration (Post P9500 migration) (one physical DKC)
System configuration17
Figure 8 Example of Ext Stor configuration (two physical DKCs)
Example of HA configuration
VSS Provider supports the following HA configurations.
18Environmental Prerequisites
Figure 9 Example of HA configuration
Server prerequisites
Prerequisites for application and backup servers:
•CPU — Must be more than or equal to the recommended requirements of the OS.
Windows Server 2008 R2, 2GHz or higher◦
◦Windows Server 2012, 3.1GHz or higher
•Memory — Must be more than or equal to the recommended requirements of the OS.
Windows Server 2008 R2, 2G bytes or higher◦
◦Windows Server 2012, 8G bytes or higher
Server prerequisites19
•Disk drive free space — Disk capacity including log files and setup files are required because
log files and setup files are not included.
NOTE:Depending on the specified log file size and the number of generations, a very
large amount of disk space may be required. Logs cannot be output when a disk has no free
space.
◦4 gigabytes or more if using the default log file size and number of generations
◦152 gigabytes or more if the log file size and the number of generations are set to
maximum
Formula for calculating the required disk size [GB]:
Disk size [GB] = (6 x specified log file size [MB] x (number of generations +1) +1,585 ) ÷
1024
NOTE:The log file size and the number of generations can be specified by using the
maintenance configuration files. For details, see “Maintenance configuration files” (page 42)
and “Generation management of log files” (page 65).
•Display — Required for the GUI tool
Screen resolution – 1024 x 768 pixels or more◦
◦Screen color – 24 bits or more
•Supported HBA — What the OS permits
20Environmental Prerequisites
Software prerequisites
Operating systems
VSS Provider supports the following versions of Microsoft Windows Server:
•Windows 2008 Server, 64-bit versions, including the following (Server Core option can be
specified):
◦Windows Server 2008 R2, Standard Edition
◦Windows Server 2008 R2, Enterprise Edition
◦Windows Server 2008 R2, Datacenter Edition
◦Windows Server 2008 R2, Standard Edition SP1
◦Windows Server 2008 R2, Enterprise Edition SP1
◦Windows Server 2008 R2, Datacenter Edition SP1
•Windows Server 2012, 64-bit versions, including the following (Server Core option can be
specified. Only classic style desktop is supported.):
◦Microsoft Windows Server 2012 Standard Edition
◦Microsoft Windows Server 2012 Datacenter Edition
◦Microsoft Windows Server 2012, R2 Standard Edition
◦Microsoft Windows Server 2012, R2 Datacenter Edition
Virtual environments
VSS Provider supports the following virtual environments:
•Hyper-V and Hyper-V 2.0:
Disk Connection Configuration — Path-through◦
◦Server Configuration:
–Non Transportable — Not Supported
–Transportable Configuration Application Server — Supported
–Transportable Configuration Backup Server — Not Supported
•Hyper-V 3.0
Disk Connection Configuration — Path-through, and Virtual Fibre Channel◦
◦Server Configuration
–Non Transportable — Supported (not supported with Path through connection)
–Transportable Configuration Application Server — Supported
–Transportable Configuration Backup Server — Supported (not supported with Path
through connection)
•ESXi 5.1 update1 and ESXi 5.5
Disk Connection Configuration — Raw Device Mapping (Physical Compatibility)◦
Server Configuration:
Software prerequisites21
Software
Table shows the software that is needed in order to use VSS Provider.
◦
Guest to Guest Backup (FC) function)
Non Transportable — Supported (Raw Device Mapping, corresponding to VMware
–
–Transportable Configuration Application Server — Supported
–Transportable Configuration Backup Server — Supported (Raw Device Mapping,
corresponding to VMware Guest to Guest Backup (FC) function)
VersionUsageStorage/OSSoftware
XP P9500RAID Manager
Business Copy, Snapshot
(SS), and Snapshot (FS)
function.
XP7
Business Copy function or
Snapshot (FS) function.
Virtual DKC(Ext Stor)
Business Copy, Snapshot
(SS), and Snapshot (FS)
function.
v01.32.06 and laterRequired for a backup using
v01.32.06 and laterRequired for a backup using
v01.32.06 and laterRequired for a backup using
Services
To use VSS Provider, start Volume Shadow Copy Service manually or automatically.
The software required to use the VMware Guest to Guest Backup (FC) function
To use the VMware Guest to Guest Backup (FC) function, the software listed is required.
•JRE 1.7(x64) — Required to be installed in the virtual machine in which the secondary VOL
(S-VOL/V-VOL) copied by VSS Provider is imported.
Since JRE is not included in the installer of VSS Provider, JRE installation is required when
implementing VSS Provider.
•VMware vCenter Server — Required to build 5.1 update1 b or 5.5 a.
•VMware Tools — Required to be installed in the virtual machine in which the secondary VOL
(S-VOL/V-VOL) copied by VSS Provider is imported.
Support scope of Ext Stor configuration
This subsection indicates the support scope of Ext Stor configuration.
RSG
Supported configurations
•One RSG in VDKC-Box
•One RSG in respective multiple VDKC-Boxes
•One RSG each in virtual DKC which straddles multiple physical DKCs
NOTE:Two or more RSGs in VDKC-Box is not supported
22Environmental Prerequisites
Figure 10 RSG configurations
RSG assignment of each resource
Table 2 Requirement of assigning resources to meta_resource
Table 3 Support scope of RSG assignment of each resource
P-VOL
RemarksAssignment to meta_resourceResource
RequiredEvery Port
RequiredEvery Parity Group
Do not careEvery LDEV_ID
Do not careEvery Host Group ID
Do not careEvery Pool (THP/Smart/FS)
Do not assign every port and every
parity group to non-meta_resource.
Do not assign every port and every
parity group to non-meta_resource.
SupportPrivilege for RSGRSG AssignmentResource
SupportedWith privilegeSame RSG as P-VOLPhysical LDEV ID
Non-SupportedWithout privilege
Non-SupportedWith privilegeDifferent RSG from
Non-SupportedWithout privilege
SupportedWith privilegeSame RSG as P-VOLVirtual LDEV ID
Non-SupportedWithout privilege
Software prerequisites23
Table 3 Support scope of RSG assignment of each resource (continued)
SupportPrivilege for RSGRSG AssignmentResource
Non-SupportedWith privilegeDifferent RSG from
P-VOL
P-VOL
Non-SupportedWithout privilege
SupportedWith privilegeSame RSG as P-VOLHost group ID
Non-SupportedWithout privilege
Non-SupportedWith privilegeDifferent RSG from
Non-SupportedWithout privilege
1
P-VOL
1
Pool is not managed by RSG. However, a pool created only by LDEV which belongs to specific RSG can only be used
by a user who has RSG privileges.
SupportedWith privilegeSame RSG as P-VOLPool (THP/Smart/FS)
Non-SupportedWithout privilege
SupportedWith privilegeDifferent RSG from
Non-SupportedWithout privilege
NOTE:Even if P-VOL to be operated is assigned in meta_resource, it can be used if a user
has appropriate privileges.
Placement location of command device which is connected to host
Place a command device in each physical DKC when a command device is used in multiple
virtual DKCs.
Table 4 Support scope of placement location of command device which is connected to
host
SupportedOnly command device in physical
DKC
Non-SupportedOnly command device in virtual DKC
RemarksSupportPlacement location
Connecting only command device in
physical DKC to host is required.
and virtual DKC
Support scope of HA configuration
This subsection indicates the support scope of HA configuration.
Adapter function
Table 5 Support scope of adapter function
operations
24Environmental Prerequisites
Same as above.Non-SupportedCommand device in physical DKC
RemarksSupportFunctionTarget
SupportedCreation of secondary VOLPrimary site only
SupportedRemoval of secondary VOL
SupportedSecondary VOL pair
SupportedSecondary VOL mapping
Table 5 Support scope of adapter function (continued)
RemarksSupportFunctionTarget
operations
site at the same time
operations
Supported functions for Primary site:
•Creation of secondary VOL
•Removal of secondary VOL
•Secondary VOL pair operations
•Secondary VOL mapping
Supported functions for Secondary site:
SupportedCreation of secondary VOLSecondary site only
SupportedRemoval of secondary VOL
SupportedSecondary VOL pair
SupportedSecondary VOL mapping
Not SupportedCreation of secondary VOLPrimary site / Secondary
Not SupportedRemoval of secondary VOL
Not SupportedSecondary VOL pair
Not SupportedSecondary VOL mapping
When VOL at the secondary
site is operated, replace
primary volume with
secondary volume of HA
pairs. See the high
availability User Guide.
NOTE:When VOL at the secondary site is operated, replace primary volume with secondary
volume of HA pairs. See the high availability User Guide.
•Creation of secondary VOL
•Removal of secondary VOL
•Secondary VOL pair operations
•Secondary VOL mapping
NOTE:Operation of these functions are not supported on the Primary or Secondary site at
the same time.
Placement location of command device which is connected to host
In the case of the HA configuration, place the command devices in both the storages at the
primary site and the secondary site.
For the support scope of the placement location, see Table 4 (page 24).
Storage requirements
Storage requirements when using VSS Provider.
Storage requirements25
Table 6 Storage requirements
RemarksDescriptionItem
XP P9500Support type
XP7
Storage requirements for XP 9500:
•Microprogram revision — 70-06-20-00/00 or higher
Required for a backup using Business Copy function, Snapshot(SS), or Snapshot(FS)
function
•Host port — FC
Storage requirements for XP7:
•Microprogram revision — 80-02-20-00/00 or higher
•Host port — FC
Restrictions and points of consideration
70-06-20-00/00 or higherXP P9500Microprogram revision
80-02-20-00/00 or higherXP7
FCXP P9500Host port
FCXP7
Required for a backup using
Business Copy function,
Snapshot(SS), or
Snapshot(FS) function
Restrictions and points of consideration related to the environmental configuration
DescriptionItem
(Missing number)(Missing number)
DescriptionItem
(Missing number)(Missing number)
Server Account Authentication
In case of using VSS provider as the general user, server information and disk array system
information cannot be retrieved. Administrative right should be given to the server account.
Also, in case of Windows Server 2008 or later and use VSS Provider with the Windows logon
account having the Administrator rights other than the built-in Administrator, server information
and disk array system information cannot be retrieved.
VSS Provider can be used by disabling UAC though, using VSS Provider with the Windows logon
account having the Administrator right is recommended.
Environmental configuration via remote desktop
Configuration via a remote desktop is supported.
Installation, repair installation, uninstallation and update installation are possible.
26Environmental Prerequisites
Items to confirm during installation
•Disable antivirus processes and other monitoring process services (daemon processes). If
such services (daemon processes) are active, installation may not be possible.
•When using firewall software other than the Windows firewall, disable or remove the software
during installation. In addition, allow settings for communication with TCP port 2000 after
installation.
•Other software must not use TCP port 2000.
Installation drive
Install only on local drives.
Installation on network drives and removable disks is not supported.
Path length of the installation folder
Installation folder of VSS Provider can be specified at the time of installation. Note that the path
length of the VSS Provider installation folder must be less than or equal to 200 bytes
Number of LUs which can be mapped to the host group
Up to 255 LUs per host group are recognizable by Windows (For details, visit
http://support.microsoft.com/kb/310072/en-us ).
Since WWN of the backup server maps S-VOL for a backup to the registered host group, if the
host LUN number is 255 or more, S-VOL cannot be recognized due to Windows specification
mentioned above and backup processing fails.
In addition, the following error is output in the event log. <Event ID 12362>
How to create setup, maintenance configuration, and configuration files
Use the configuration files which are automatically created during VSS HW provider installation.
Files that are made by other means (by text editor or the like) may be overwritten during
installation, repair installation or update installation.
If you delete a file by mistake, restore the file by VSS HW provider repair installation and
reconfigure the necessary information as explained in “User edit files” (page 37).
Hewlett Packard Enterprise shortcut of the Start Menu
When installation/uninstallation is performed by multiple Windows accounts on the equivalent
server, "Hewlett Packard Enterprise" shortcut may be left for the Start Menu of Windows at the
time of uninstallation. You may ignore it, but you can delete it.
To delete the shortcut:
1.Log off in the account except the Windows account that uninstalled VSS Provider.
2.Confirm whether there is Hewlett Packard Enterprise folder for the Start Menu of each
following Windows accounts and delete it if it exists.
Installation of following other VSS Providers at the same time is not supported.
•HPE Storage VSS Hardware Providers
•Hitachi Storage Adapter for Microsoft Volume ShadowCopy Service
Account Authentication
Select Administrator (View and Modify) from the role check box in the Storage Management
Software account addition window.
For the characters and can be used for user name and password as well as the number of
characters can be entered, refer to the RAID Manager command reference.
RAID Manager (HORCM)
•Start RAID Manager (HORCM) prior to starting any RAID Manager commands from VSS
Provider.
See “Preparing configuration files and restarting RAID Manager (HORCM)” (page 43) for
details.
•In the case of the Ext Stor configuration or HA configuration, do not describe HORCM_VCMD
in the HORCM CONF configuration file.
•Do not use the HORCM CONF configuration file used by VSS Provider except for the purpose
of VSS Provider.
Host group creation
Host groups must be created in disk array systems, see Table 7 (page 46).
Creating a user authentication account for storage administration
The disk array system must have the same user name and password when using multiple disk
array systems of the XP P9500/XP7.
For example:
When using disk array system A or B, the same user name (USER01) and password (*****) must
be used.
•Storage A:
User name — USER01◦
◦Password — *****
•Storage B:
User name — USER01◦
◦Password — *****
28Environmental Prerequisites
Assigning LDEV ID
•When configuring Ext Stor, to create secondary VOL (S-VOL/V-VOL) using VSS provider
and GUI, assign the physical LDEV ID to RSG which P-VOL belongs to, in advance.
•Assign virtual LDEV ID to physical LDEV ID as well.
(Do not operate the physical LDEV ID to which the virtual LDEV ID has not been set (Virtual
LDEV ID will be FF:FE) or the physical LDEV ID reserved for HA (Virtual LDEV ID will be
FF:FF))
•In the case of using virtual DKC which straddles multiple physical DKCs, make sure that
virtual LDEV ID is not duplicated in virtual DKC.
Resource Group (Resource Partition)
Do not create Resource Group other than meta_resource in the storage system because Resource
Group is not supported.
Exceptionally, this restriction can be relaxed under H-UVM configuration. See “Support scope
of Ext Stor configuration ” (page 22).
Raw Device Mapping (RDM)
LU which is used as P-VOL must be mapped on the application server in RDM (physical
compatibility mode).
Command device
In case of using XP P9500/XP7 disk array systems, command device must be mapped on the
application server/backup server in RDM (physical compatibility mode)
SCSI controller type
SCSI controller type of the virtual machine supports LSI Logic SAS.
SCSI controller created by VSS Provider
If RDM required sufficient free virtual device node is not available on the import destination virtual
machine during the secondary VOL import process, VSS Provider creates SCSI controller using
the following settings.
•SCSI controller number — Use from not created and smaller controller number
•SCSI controller type — LSI Logic SAS
•Sharing SCSI path — Nil
VMware HA
To use VMware HA, the following conditions must be fulfilled:
•WWN used for the failover of the node participating in VMware HA, write in the configuration
file using the “WWN of ESXi” specified option.
•Register the above WWN in HG which is used for VSS Provider.
•Confirm that the failover operates by using the corresponding HG in advance.
Restrictions and points of consideration29
Operational restrictions and points of consideration
The following table lists the concerning restrictions and points of consideration related to operation
when using VSS Provider.
DescriptionItem
(Missing number)(Missing number)
Multiple instances of the VSS Provider
Multiple instances of the GUI tools tools on one server are not supported.
Unregistering a disk array system
To unregister a disk array system registered by the Add Storage function of the GUI tool, remove
the IP address and the serial number from the setup file.
Number of user accounts that can be registered for a disk array system
Use the Add Storage function of the GUI tool to register user accounts.
Only one account can be registered for a disk array system.
To change a user account, you must re-register the disk array system using the Add Storage
function and specify a new user name and a password.
Changing the configuration file or the maintenance configuration file
The VSS HW provider GUI will need to be restarted when a change to the configuration file or
the maintenance configuration file are made while they are in use.
Restarting a server during a backup
When the server reboots during a backup, depending on the backup software and the timing of
a server reboot, the pair state will be PSUS or PAIR after resynchronization is completed.
When a pair status is suspended, perform the confirmation and recover steps outlined in
“Confirmation and support after a recovery” (page 135).
Log collection during problem occurrence
Because a log may wrap, collect a log and save it during the problem occurrence.
See “Information collected during problem occurrence” (page 137) for the log to collect.
Parallel backup of multiple data on the same volume
When performing a parallel backup of multiple data located on the same volume, the following
operational restrictions exist.
•Backup with Business Copy — Unsupported
•Backup with Snapshot — No restrictions
30Environmental Prerequisites
Loading...
+ 118 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.