Timeline for Database file location change on standby site after restore standby database
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2019 at 22:23 | comment | added | WadeH | In addition, seeing as my answer did help and worked for your initial question, would you mind please marking it as the answer. Thank you | |
| Feb 20, 2019 at 14:21 | comment | added | WadeH | Your plan should work in theory, however i am unsure about the log file history that needs to be kept. normally just a period while it gets applied but i have not attempted this before. I would recommend asking a new question so that you can get the correct answers based on the topic. | |
| Feb 20, 2019 at 6:55 | comment | added | safi qadri | Hence, I have check from this command then it shows last_restored_file correctly but actually not. "select secondary_database,last_copied_file,last_restored_file from msdb..log_shipping_monitor_secondary" It seems that at the time of database open on 2016, it actually applies/restores transaction log files. Please confirm! Would you please show whether there is any way it can apply transaction logs while in this UPGRADE setup as explained above and let older than 2 days transaction log files deleted as per scheduled till we actually upgrade to 2016? | |
| Feb 20, 2019 at 6:55 | comment | added | safi qadri | However, when we check the timestamp of data and log files of the configured databases on 2016, it shows the timestamp when this was configured. It seems transaction logs are not being applied. Also, when we try to open the database on 2016 using Restore -> Database, it reports some transaction log missing (because we configured to delete older than 2 days transaction logs and hence these were deleted after 2 days). | |
| Feb 20, 2019 at 6:55 | comment | added | safi qadri | One more question is: We finally configured 2 test instances using NORECOVERY option with Log Shopping jobs – Backup, Copy and Restore setup to run every hour between following servers: 1. MS SQL Server 2008R2 as a source instance 2. MS SQL Server 2016 as a target instance – as we need our current 2008R2 databases to be upgraded/migrated to 2016 instance Log history of these three jobs shows no error. i.e. Backup executes successfully on 2008R2 instance, Copy and Restore jobs execute fine on 2016 | |
| Feb 19, 2019 at 20:23 | history | edited | LowlyDBA - John M | CC BY-SA 4.0 |
Formatting code
|
| Feb 19, 2019 at 13:42 | history | answered | WadeH | CC BY-SA 4.0 |