March 6, 2017 at 7:08 am
Quick question for you all. Does the secondary database in Database Mirroring require direct access to the primary database's transaction log backups for synchronization?
We're having a space issue on our backup NAS (which is locked and doesn't allow us to remove backups until a certain date) and someone suggested moving the log backups to the local server where we could manage them more proactively. My concern is that the secondary server may need access to the backups, like in log shipping, but I'm not sure if that's the case and I can't seem to find that information on Google.
March 6, 2017 at 7:29 am
Brandie Tarvin - Monday, March 6, 2017 7:08 AMQuick question for you all. Does the secondary database in Database Mirroring require direct access to the primary database's transaction log backups for synchronization?
We're having a space issue on our backup NAS (which is locked and doesn't allow us to remove backups until a certain date) and someone suggested moving the log backups to the local server where we could manage them more proactively. My concern is that the secondary server may need access to the backups, like in log shipping, but I'm not sure if that's the case and I can't seem to find that information on Google.
No. Synchronization is done via log reader thread sending tlog contents over to secondary.
HOWEVER!!! Putting log backups on the SQL Server box itself is a STUPID STUPID IDEA, and I am (virtually) slapping the person that recommended that upside the head!!! What happens when the disk system evaporates with those tlogs on it??
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
March 6, 2017 at 7:36 am
TheSQLGuru - Monday, March 6, 2017 7:29 AMBrandie Tarvin - Monday, March 6, 2017 7:08 AMQuick question for you all. Does the secondary database in Database Mirroring require direct access to the primary database's transaction log backups for synchronization?
We're having a space issue on our backup NAS (which is locked and doesn't allow us to remove backups until a certain date) and someone suggested moving the log backups to the local server where we could manage them more proactively. My concern is that the secondary server may need access to the backups, like in log shipping, but I'm not sure if that's the case and I can't seem to find that information on Google.
No. Synchronization is done via log reader thread sending tlog contents over to secondary.
HOWEVER!!! Putting log backups on the SQL Server box itself is a STUPID STUPID IDEA, and I am (virtually) slapping the person that recommended that upside the head!!! What happens when the disk system evaporates with those tlogs on it??
I know. I know. I need to talk to this person about it. Unfortunately, I'm outranked in this matter and if I can't convince him...
March 6, 2017 at 7:46 am
Brandie Tarvin - Monday, March 6, 2017 7:36 AMTheSQLGuru - Monday, March 6, 2017 7:29 AMBrandie Tarvin - Monday, March 6, 2017 7:08 AMQuick question for you all. Does the secondary database in Database Mirroring require direct access to the primary database's transaction log backups for synchronization?
We're having a space issue on our backup NAS (which is locked and doesn't allow us to remove backups until a certain date) and someone suggested moving the log backups to the local server where we could manage them more proactively. My concern is that the secondary server may need access to the backups, like in log shipping, but I'm not sure if that's the case and I can't seem to find that information on Google.
No. Synchronization is done via log reader thread sending tlog contents over to secondary.
HOWEVER!!! Putting log backups on the SQL Server box itself is a STUPID STUPID IDEA, and I am (virtually) slapping the person that recommended that upside the head!!! What happens when the disk system evaporates with those tlogs on it??
I know. I know. I need to talk to this person about it. Unfortunately, I'm outranked in this matter and if I can't convince him...
I knew YOU knew better Brandie, which is why I was smacking the other person. 😉 I know that you understand that the very viability of the company is at risk with that move. I have been involved with incidents where that very thing happened, and know of others too. It is really sad to see a company fold, and people put out of work, because of stupid/uninformed/CHEAP decisions such as storing SQL Server tlogs on the same box the SQL Server files are stored on.
Good luck with it. BTW, if you need someone to back you up on this one I will do it for free. And since I don't have to worry about politics, repercussions, etc. I can and will be straight up honest - just like I am even when there is an invoice on the line
Oh, funny thing: you are the second person today that has asked this very same question.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply