Application consistent Snapshots with Microsoft VSS

Application consistent snapshots can be taken by the StorONE array for Microsoft hos application servers.  The application consistent snapshots are taken using Microsoft Volume Shadow Copy Service (VSS).  Microsoft VSS enables application-consistentthe snapshotsapplication onserver to temporarily quiesce IO for designated application volumes and specific applications used by Microsoft Windows. To enable VSS snapshots with the StorONE system, the StorONE VSS module must be installed on all Windows hosts or cluster members that use the volume.servers

InStorONE orderapplication forconsistent Microsoftsnapshot VSS snapshots to be enabled:requirements:

• The StorONEvolume volumeon the Microsoft host application server must be block-basedseen as a "block device", and not a network attached drive.  This is possible in one of two ways:
  • directly mappedconnecting the StorONE array to your application host via iSCSI or Fibre Channel for application and formattedlog fromvolumes
    
  • Directly connecting a hypervisor via iSCSI or Fibre Channel, and then presenting the volumes to the host (notapplication through a hypervisor), or a virtual disk mountedserver as a driveblock letterdevices. on theBlock host.devices Volumeswhich usedare asback virtualby disksfile canbased be block(NFS) or filesystem-based volumes (NFS). Network mappedSMB shares cannotare benot usedsupported for MicrosoftApplication VSSconsistent snapshots with StorONE at this time.
• The Microsoft application must be VSS capable (Microsoft SQL, Exchange, Sharepoint, and so on).
• The StorONE VSS application must be installed on each Microsoft host where application consistent snapshots are required.  For Microsoft clusters, the StorONE VSS application must be installed on each individual cluster member.

Connectivity

Installingbetween the StorONE VSSarray pluginmanagement onIP Microsoftaddresses Windows

Pre-requisites

You must installand the Application host server(s) via TCP port 18222

The latest Microsoft Visual C++ Redistributable Version package before installing the StorONE VSS plugin. It can be downloaded from Microsoft.

Download the relevant version for your Windows platform (x86 or x64).

If the StorONE VSS module was installed before installing the Microsoft Visual C++ Redistributable Version, remove the module, install the Microsoft Visual C++ Redistributable Version, and then reinstall the StorONE VSS module.

Installing the StorONE VSS plugin on Microsoft Windows

Downloading the StorONE VSS module

Download the latest VSS installer .MSI file from the StorONE landing page. In a browser, go to the DNS name or IP address of either of the StorONE controller nodes, and click the VSS Installer link.

Installing the StorONE VSS module

After the download completes, run the installer. Make sure to download and run it on all Windows machines (physical or virtual) that use the StorONE volume that you want to enable VSS snapshots on.

After the installation finishes, two services are added to the Windows host: S1VssHardwareProvider and S1VssService:

TheNOTE: hardwarewhen providerverifying servicethe installation of the VSS services, the S1VssHardwareProvider should be set tofor manualManual start,startup astype.  If the startup type is Automatic it onlyneeds runsto whenbe Microsoftchanged VSSto snapshotsManual. are being taken.

When aan Microsoftapplication VSSconsistent snapshot is initiated by the StorONE system, the appliancearray contacts the Microsoft VSS provider on the Windowshost machinesapplication onserver via TCP port 18222.  In order for application consistent snapshots to work properly, make sure that this port is openavailable for requests from the management IP on both StorONE controller nodes.  VSSApplication consistent snapshots can be scheduled or manually initiated via the StorONE UI.

StorONE system configuration

Step 1: Create Application and log volumes in StorONE

Configure volumes and consistency groups in StorONE.  It is recommended to create a specific application to contain the applicaiton and log volumes for each host applicaiton server.  In cases where the application server is a cluster, only one StorONE application and set of volumes need to be created for the cluster.

(fill in steps)

We may want to recommend log volumes be on SSD becaise they are small and this will make it easier to snapshot from a performance perspective.  log volumes are usually 100G or less, and can be as little as 10G

Step 2: Mask volumes to host or Hypervisor

Create host groups and mask LUNs as needed

(fill in steps)

In the StorONE admin web interface, there are two steps required to enable Microsoft VSS snapshots:

1. Enable VSS for the required volume
2. Configure a snapshot schedule

Step 1:3: Enable VSS for the consistency Group

Inneed to change instructions and photo to a consistency group and slightly alter the GUI,text gofor to Applications 🡪 Snapshots, and then click the VSS button.this

Specify the application and volume that you want to enable VSS snapshots for, and add the IP addresses of all Windows machines using the volume.

If the volume is a block volume (iSCSI or Fibre Channel) directly mapped to the Windows hosts, make sure to check the Direct Mapping checkbox.

If the volume is anbeing NFShosted filesystem volume orthrough a blockHypervisor volume used as a datastore hostingpresenting virtual disks for the Windows hosts, do not check the Direct Mapping checkbox.

Step 2: Configure snapshot schedule

On the Applications 🡪 Snapshots page, you can manually take a one-time snapshot by clicking the Take button, or by clicking Schedule to schedule recurring snapshots. In both cases, check the Enable Vss box.

When a VSS-enabled snapshot is initiated, the StorONE system will communicate with the VSS services on the Windows machines to coordinate an application-consistent snapshot.

Using the CLI

To manually take a Microsoft Application consistent snapshot using the CLI, use the --vss argument:

Troubleshooting

In some cases, the VSS backupsnapshots fails with error 8194: Access Denied. This is caused when the Windows NETWORK SERVICE predefined local user does not have sufficient access permissions.

To fix this issue, add the relevant permissions:

1. Open the Windows Start Menu, then search for and run the dcomcnfg tool.
2. Expand the path Console Root 🡪 Component Services 🡪 Computers.
3. Right click on My Computer, then select Properties.
4. In the My Computer Properties dialog box, select the COM Security tab
5. In the Access Permission dialog box, click Add and enter NETWORK SERVICE.
   
6. To make sure the spelling is correct, click the Check Names button.
   
7. After adding NETWORK SERVICE make sure the Local Access permission is allowed.
   
   
8. Click OK to save the configuration.