Release #1901
Merged
Release #1901
Conversation
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
Queue viewer crash
Update Emerging-Issues.md
Update VSSTester.md
Fixing formatting with URL
Update VSSTester.md
Add High Performance (ConfigMgr) power plan detection to HC
Adding logic for Publishing Format tables Output cmdlet calls
Adding logic for Publishing Format tables Output cmdlet calls Skip checks if they are not using modern sharing Output Sharing specifically at bottom
Code standards
Adding Output of Sharing Type specifically
Update Summary output
Output changes and parameter for waiting time in Test-ExchAVExclusions
Save RBA Log, RBA Logs summary, Better coverage of known issues
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.
VSSTester: Allow specifying volumes to back up
bill-long
requested review from
Batre-MSFT,
tweekerz,
ninobb,
Nasir1786 and
a team
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.