-
Notifications
You must be signed in to change notification settings - Fork 343
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
VSSTester: Allow specifying volumes to back up
In previous versions of VSSTester, the user had to specify a database when testing a DiskShadow backup. This would cause VSSTester to look up the volumes that stored the database and log files, and then it would snap those volumes. This approach works for most cases, but it makes it hard to compare with backup software that only allows specifying volumes, not databases. This change allows running a DiskShadow backup of specified volumes. To get a list of acceptable volume names, the user can specify one that is invalid. For example: ``` [PS] C:\>.\VSSTester.ps1 -DiskShadow -VolumesToBackup foo C:\VSSTester.ps1 : Cannot validate argument on parameter 'VolumesToBackup'. Invalid volume specified. Please specify one of the following values: C:\ C:\Databases\DB1\ At line:1 char:70 + ... code\CSS-Exchange\dist\VSSTester.ps1 -DiskShadow -VolumesToBackup foo ``` One or two volumes can be specified. As usual, drive letters must be provided. For this syntax, the number of provided drive letters must match the number of specified volumes. Example: ``` VSSTester.ps1 -DiskShadow -VolumesToBackup C:\Databases\DB1\ -ExposeSnapshotsOnDriveLetters X ``` This PR includes several other changes: * Get-WmiObject has been replaced with Get-CimInstance. * Drive letters are now specified with -ExposeSnapshotsOnDriveLetters, which more clearly communicates the intent and allows specifying one or more drive letters with a single parameter.
- Loading branch information
Showing
6 changed files
with
177 additions
and
194 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.