Restore of SQL server replicated DB in v10 & v11

[jamespbarrett3]

Hi All:

We are currently using Veeam 9.5U4 as our bkup/restore system for non-DB servers. We were testing bkup/restore on replicated SQL Server DB. We ran into a problem where we could not restore the DB to it's normal location without dropping replication. Some research showed this was the case in another forum topic. I'm curious if this has changed in v10 or v11.

Our support contract has expired and we need to either renew or upgrade. We are already thinking of upgrading to V11 because you can now copy trans-log files with "Backup Copy" jobs. (One of the other items testing revealed).

Thanks

[HannesK]

Hello,
and welcome to the forums.

Can you please give more information which kind of replication you use? SQL has so many replication options (including legacy ones), that guessing makes little sense to me.

And can you also please also link the other topic that we can merge the questions together?

Thanks,
Hannes

[jamespbarrett3]

Link: vmware-vsphere-f24/error-restoring-obje ... 33235.html

I use both transactional and snapshot replication on SQL Server 2017 Enterprise. I could ignore the snapshot and just configure a job in SSIS or stored procs to handle the data refresh. I use transaction replication to populate a real-time reporting environment. It is "1 publisher/1 subscriber" and subscriber DB is read-only.

Thanks,
Jim

[PetrM]

Hi Jim,

It's expected that replication is broken after restore as from SQL perspective we always create a new database with settings identical to the original one.

Thanks!