• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 409
  • Last Modified:

transaction log disk issue in replication enviornment

There is an issue with the disk thats hosting the transaction log on publication server.The database is set  for transactional replication.
The system folks wanted to remove the disk and present it back.
How do I bring back the replication when the log disks gets fixed.?
1 Solution
Jim P.Commented:

Which version of SQL Server?

Are they destroying the volume?

Can you shut down the SQL Server?
Here are the steps you can follow:

1. Take a full backup of the database (which is set for replication) and a tail log backup once the application is stopped.
2. Stop the replication on the publication server
3. Once the disk is attached back, check if the database is healthy (you have to run dbcc checkdb for that)
4. If the database is healthy, then proceed with enabling the replication - if everything is fine, this should go or you need to setup the replication again
5. If the database is not accessible/corrupt, restore from the full and tail log backups and enable/reinitiate the replication
Vitor MontalvãoMSSQL Senior EngineerCommented:
Just stop replication before the disk tasks. Then when disk is ready to go, create new snapshot from replication and start replicate after snapshot finnish.

Good luck
venk_rAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now