Move PiTR-VMFS script into VMFS-VMDK Snapshot folder; combine READMEs; update main README

Author: nocentino

README.md

@@ -43,7 +43,8 @@ Array-based snapshots are used to decouple database operations from the size of
 
 | Demo | Description |  |   |
 | ----------- | ----------- |  ----------- |  ----------- | 
-| **Volume Database Refresh on VMDK Virtual Disks** | Refresh a database from Volume snapshot where all of the databases's files are using a VMware VMDK Virtual Disk type on a single VMFS Datastore on the same Volume on the same FlashArray. | [More Info](./demos-sdk2/VMFS-VMDK%20Snapshot/) | [Sample Code](./demos-sdk2/VMFS-VMDK%20Snapshot/VMFS-VMDK%20Snapshot.ps1) |
+| **Volume Database Refresh on VMDK Virtual Disks** | Refresh a database from a Volume snapshot where all of the databases's files are using a VMware VMDK Virtual Disk type on a single VMFS Datastore on the same Volume on the same FlashArray. | [More Info](./demos-sdk2/VMFS-VMDK%20Snapshot/) | [Sample Code](./demos-sdk2/VMFS-VMDK%20Snapshot/VMFS-VMDK%20Snapshot.ps1) |
+| **Point in Time Recovery on VMDK Virtual Disks** | Combine a FlashArray snapshot with SQL Server 2022 T-SQL Snapshot Backup on a VMFS datastore for application-consistent snapshots and point-in-time recovery. | [More Info](./demos-sdk2/VMFS-VMDK%20Snapshot/) | [Sample Code](./demos-sdk2/VMFS-VMDK%20Snapshot/Point%20in%20Time%20Recovery%20-%20VMFS.ps1) |
 
 
 ## Using Snapshots for Databases on Hyper-V Cluster Shared Volumes (CSV)

demos-sdk2/Point in Time Recovery - VMFS/README.md

@@ -1,40 +1,62 @@
-# Refresh VMFS VMDK(s) with Snapshot Demo
-<!-- wp:separator -->
-<hr class="wp-block-separator"/>
-<!-- /wp:separator -->
-
-# Scenario:
-This example is for a repeatable refresh scenario, such as a nightly refresh of a production database on
-another non-production SQL Server.
-<BR><BR>
-Production SQL Server & database(s) reside on a VMFS datastore.  Non-production SQL Server resides on 
-a different VMFS datastore.  User database(s) data and log files reside on two different VMDK disks 
-in each datastore.  This workflow is intended to only be impact select Windows Disks/VMDKs that contain user 
-databases.  Each datastore also resides on a different FlashArray, to demonstrate use of async snapshot 
-replication.
-<BR><BR>
-This example's workflow takes an on-demand snapshot of the Production datastore and async replicates it to
-the second FlashArray.  Then the snapshot is cloned as a new temporary volume/datastore.  The VMDKs with the
-production database files, residing on the temporary cloned datastore are attached to the target SQL Server,
-replacing the prior VMDKs that stored the database files previously.  Finally Storage vMotion is used to
-migrate the VMDKs to the non-production datastore, then the temporary cloned datastore is discarded.
-<BR><BR>
-
-
-# Disclaimer:
-This example script is provided AS-IS and is meant to be a building block to be adapted to fit an individual organization's  infrastructure.
-<BR><BR>
-_PLEASE_ do not save your passwords in cleartext here. 
-Use NTFS secured, encrypted files or whatever else -- never cleartext!
-<BR><BR>
+# VMFS-VMDK Snapshot Scripts for SQL Server
+
+This folder contains scripts for managing SQL Server databases on VMware VMFS datastores using Pure Storage FlashArray snapshots.
+
+**Files:**
+- `VMFS-VMDK Snapshot.ps1` — repeatable database refresh from a FlashArray snapshot across two VMFS datastores
+- `Point in Time Recovery - VMFS.ps1` — SQL Server 2022 T-SQL Snapshot Backup with point-in-time recovery on VMFS/VMDK
+
+---
+
+## VMFS-VMDK Snapshot.ps1
+
+**Scenario:**
+
+This script is for a repeatable refresh scenario, such as a nightly refresh of a production database onto a non-production SQL Server. Production SQL Server databases reside on a VMFS datastore on one FlashArray. The non-production SQL Server resides on a different VMFS datastore on a second FlashArray.
+
+The workflow takes an on-demand snapshot of the production datastore and async replicates it to the second FlashArray. The snapshot is then cloned as a new temporary volume/datastore. The VMDKs containing the production database files are attached to the target SQL Server, replacing the prior VMDKs. Finally, Storage vMotion migrates the VMDKs to the non-production datastore and the temporary cloned datastore is discarded.
+
+**Prerequisites:**
+
+1. PowerShell Modules: `dbatools` & `PureStoragePowerShellSDK2`
+2. VMware PowerCLI must be installed.
+3. Async replication must be configured between the source and target FlashArrays.
+
+---
+
+## Point in Time Recovery - VMFS.ps1
+
+**Scenario:**
+
+This script performs a point-in-time restore using SQL Server 2022's T-SQL Snapshot Backup feature with a FlashArray snapshot as the base, followed by restoring a native SQL Server log backup.
+
+**Important Note:**
+
+This script is built for a single database spanned across two VMDK files from a single datastore. The granularity of this workflow is a VMDK file and the entirety of its contents — everything in the VMDK, including files for other databases, will be impacted and overwritten. This script will need to be adapted to support multiple databases on the same VMDK(s).
+
+**Prerequisites:**
+
+1. PowerShell Modules: `dbatools` & `PureStoragePowerShellSDK2`
+2. VMware PowerCLI must be installed.
+3. SQL Server 2022 or later is required for T-SQL Snapshot Backup support.
+
+**Usage Notes:**
+
+Each section of the script is meant to be run one after the other. The script is not meant to be executed all at once.
+
+---
+
+## Disclaimer
+
+This example script is provided AS-IS and is meant to be a building block to be adapted to fit an individual organization's infrastructure.
+
 We encourage the modification and expansion of these scripts by the community. Although not necessary, please issue a Pull Request (PR) if you wish to request merging your modified code in to this repository.
 
-<!-- wp:separator -->
-<hr class="wp-block-separator"/>
-<!-- /wp:separator -->
+---
 
 _The contents of the repository are intended as examples only and should be modified to work in your individual environments. No script examples should be used in a production environment without fully testing them in a development or lab environment. There are no expressed or implied warranties or liability for the use of these example scripts and templates presented by Pure Storage and/or their creators._
 
 
 
 
+