Forum Discussion
Re-creating log shipping - error message, how to bypass
It seems that the user is experiencing an issue when re-instantiating log shipping between a primary and standby database. The user dropped the database on standby and the jobs on the standby, then went to the primary database properties and attempted to drop the secondary database links and add a connection to the standby database. However, when the user clicked "OK" on the prompt to overwrite the existing configuration, nothing happened.
My suggestion would be to ensure that both the primary and standby databases are properly configured for log shipping and that the required permissions are in place. Additionally, it may be helpful to check the SQL Server error log for any relevant error messages that could provide insight into why the configuration is not being overwritten. [Link removed by admin]
Regarding the issue with the script, it may be necessary to manually adapt the script to include the required folders specified in the backup and restore options. It could also be helpful to review Microsoft's documentation on log shipping for additional guidance and best practices.