We have about 20 databases, with no DR config yet. Most of them are SQL Server 2016 with Failover cluster Availability group

What's the best method for a log shipping?

  1. Log shipping directly between DC site to DR site
  2. Log shipping through a fileshare server

Imo, 2 is much more risks in case of file share server are accessed by someone else.

  • Welcome to dba.se - please provide the version of SQL Server you are using and please add more detail dba.stackexchange.com/help/minimal-reproducible-example
    – user212533
    Mar 4, 2021 at 4:35
  • Hi, I already updated the details
    – Nike
    Mar 4, 2021 at 5:21
  • Are you planning to use fileshare server as monitoring server? Mar 4, 2021 at 6:09
  • I meant a directory to store a redo log for log shipping. Which one are more secure between store redo log on primary server and secondary take it to apply or store redo log on network share server. and thanks for mentioned about monitoring server. does it necessary to have it one? or it just an optional?
    – Nike
    Mar 4, 2021 at 6:59
  • When you say failover cluster is it windows cluster or SQL failover cluster you are talking about ?
    – Shanky
    Mar 4, 2021 at 8:23

1 Answer 1


I supposing you are using Alwayson AG with a SQL server enterprise edition (because you are in a business critical production environment). Why don't you add the DR instance as a node of the alwayson AG cluster? It's free and included in the license you already own.

Instead if you are using basic availability group, you are limited to one copy. So you have to look up for something like log shipping.

Log shipping is based on a share that plays as a repository for tlog backup between primary and distare recovery site.

After saying that, you have to evaluate that the source environment is composed by two nodes that have to use the same repository for LS tlog backups. So a network path is more friendly and reliable.

The risk of having someone to disrupt the share you created is something you have to handle with security and rights in your environment; it should not prevent smart architectural choises.

Not the answer you're looking for? Browse other questions tagged or ask your own question.