You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ensure you are able to reproduce it on the latest released version (we release often)
Verified this bug is not already reported in an issue
Verified errors are not related to permissions
Can reproduce in a clean PowerShell session (clean = powershell -NoProfile)
Describe the bug
The "DatabaseTimestamp" metadata field is only filled in when a fresh backup is taken, not when using existing backup files to generate an image.
We can use the global output variable feature of Restore-DbaDatabase to capture this field more robustly.
Before submitting the bug
powershell -NoProfile)Describe the bug
The "DatabaseTimestamp" metadata field is only filled in when a fresh backup is taken, not when using existing backup files to generate an image.
We can use the global output variable feature of
Restore-DbaDatabaseto capture this field more robustly.This also introduces necessary data for #172
To Reproduce
Create an image from an existing backup file, then check the database/json files to see a "null" DatabaseTimestamp value for the image.
Expected behavior
The DatabaseTimestamp field reflects when the backup was taken, regardless of how the image is generated.
Screenshots
Before and after fix:
The text was updated successfully, but these errors were encountered: