Getting Started with VSS Hardware Provider

This section provides information and setup guidance when using the VSS Hardware Provider software. VSS Hardware Provider works with DiskShadow or any other third party VSS requester software that is supported by the Windows Volume Shadow Copy Service.

The instructions documented here assume that the user has a working knowledge of DataCore Windows Integration Kit. Information and examples use DiskShadow commands as a point of reference. If using a different VSS requester, please adapt the instructions.

Pre-Requisites

  • A VSS requester software is required on VSS clients.
  • Volume Shadow Copy Service must be started.
  • DiskShadow commands must be run at an elevated command prompt.
  • If using User Account Control, disable Run all administrators in Admin Approval Mode. This setting is located under Security Settings>Local Policies>Security Options.
  • VSS Hardware Provider software is supported for use with any virtual machine when LUNS are directly served to the virtual machine. However, for instance, when going through an ESXi server using Raw Device Mapping (RDM), all VSS clients that need access to the shadow copies are required to be configured in the DataCore Server and must have a valid iSCSI or Fibre Channel initiator port. Shadow copies will be served directly to the virtual machine that imports them, regardless of the fact that the source volume is served through the ESXi server.

Procedural Overview

Follow the steps in order and click the hyperlinks for additional instructions.

Steps Procedures

1

Install the VSS Hardware Provider software on hosts acting as VSS clients Hosts (also known as application servers) that are running VSS. Read the VSS Hardware Provider Release Notes.

2

Review About VSS Hardware Provider and other introductory topics to plan the implementation.

Refer to DiskShadow Interactions with DataCore SANsymphony for a description of the effects that certain DiskShadow commands will have on virtual disks.

Refer to DiskShadow Commands Example for examples of commands.

3

VSS clients must be registered as hosts in the same server group as the DataCore Servers used to create the snapshots. Ports should be configured. (When DataCore Servers in the server group are acting as VSS clients, do not register the DataCore Servers as hosts.)

The host name registered in DataCore SANsymphony must be identical to the computer name of the VSS client. The host name can be changed in the DataCore Management Console if necessary. If using the Windows operating system Hosts file, the host name must also be identical. For instance, a mismatch will occur if the computer name of the VSS client is "Host1" and the host name in the Hosts file is "Host1.domain.local".

4

Ensure virtual disks are prepared:

  • If using replication, virtual disk replications should be configured between local and remote DataCore Servers.

  • If using CDP, it must be enabled on the virtual disks before using VSS.

  • Virtual disks should be served to VSS clients, discovered as volumes, and be in use as storage resources for applications. Shadow copy commands will be performed on these volumes.

5

On VSS clients, create and manage shadow copies using the installed VSS requester software.