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.
Type of Change
Purpose
the purpose of this fix is because there is a bug when you want to deploy a log shipping by specifying a backup folder containing the backup full, and an error is thrown. $BackupPath is never initialized when UseExistingBackup is specified, so it throws an error "$Path is null" when trying to execute the Restore database command
Approach
This change only includes a missing line to specify where is the backup folder after validating that the backup folder is working properly
Commands to test
Invoke-DbaLogShipping -SourceSqlInstance source -DestinationSqlInstance destination -Database MyDatabase -FullBackupPath "\path\FULL" -UseExistingFullBackup -BackupNetworkPath "\PATH\LOG" -CopyDestinationFolder "\path\LOG" -CompressBackup -CopyScheduleDisabled -PrimaryThresholdAlertEnabled -RestoreThreshold 15 -SecondaryThresholdAlertEnabled
Screenshots
Learning