question

HMK avatar image
HMK asked

SQL 2008 P2P Replication Log Backing Up or Shrinking (If no space left on drive)

Scenario: I have 3 Servers running in different geographical locations. DataBase Log is Full and using P2P Replication to Replicate the DataBases. Everything is fine until log file grows to the limit of the disk size.

What can I do here to make the log file smaller (like truncate / shrink / backup) and if I do that what happened to other 2 Servers? Are they gone down due to log file asymmetry, cause when I do that Main server's transaction log freed a little bit?

Or simply... How can I make log files smaller (due to disk space problem) (in both 3 servers) without breaking the p2p replication and data corruption?

Thanks for your answers...

sql-server-2008replicationtransaction-loglog-backupp2p
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
CirqueDeSQLeil avatar image
CirqueDeSQLeil answered

Typically the changes made to the log on the primary server will replicate to the other servers without breaking replication (including log shipping).

10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.