March 16, 2009 at 10:18 am
We have a datawarehouse server (DW) acting as a subscriber/distributor and a production server (PROD) acting as the publisher. Also, the network folder that the publisher is writing to is actually on DW.
We need to bring down the DW server for hardware upgrades. How will this affect the publication and the PROD server? Do I need to move the network folder? Will I need a new snapshot? Or don't worry, the publication will sync with the subscriber once the DW server comes back on line?
Alan
March 16, 2009 at 11:25 am
Alan Vogan (3/16/2009)
We have a datawarehouse server (DW) acting as a subscriber/distributor and a production server (PROD) acting as the publisher. Also, the network folder that the publisher is writing to is actually on DW.We need to bring down the DW server for hardware upgrades. How will this affect the publication and the PROD server? Do I need to move the network folder? Will I need a new snapshot? Or don't worry, the publication will sync with the subscriber once the DW server comes back on line?
Alan
I am assuming you are using "Transactional" Replication.
- The network folder is only used at snapshot time so as long as you don't trigger snapshots you should be OK.
- If the downtime is longer than the expiration period you will have to snapshot but if it is not you should be fine.
- It will though make your Transaction log on the Publisher "grow" because backups won't be able to clear entries
that are still marked for replication. So if there is a lot of activity in the publisher be ready to accommodate extra space for the Transaction Log.
Good Luck!
* Noel
March 16, 2009 at 11:45 am
Thanks Noel,
Yes, we are using transactional replication. I've got plenty of log space and downtime will be no more than 30 minutes. Just wanted to confirm that this was going to work and check if anyone had experienced any problems.
Thanks again for the response,
Alan
March 16, 2009 at 11:47 am
you should be fine then!
* Noel
March 16, 2009 at 12:02 pm
One more note - I left the distributor transaction retention at the default 0-72 hours and history at 48 hours. How do you determine what the best setting for this would be? Looking at my log files for 72 hours, I see about 1GB of log files.
March 16, 2009 at 12:12 pm
Alan Vogan (3/16/2009)
One more note - I left the distributor transaction retention at the default 0-72 hours and history at 48 hours. How do you determine what the best setting for this would be? Looking at my log files for 72 hours, I see about 1GB of log files.
I actually see it more as a functionality setting. For example if I know that my subscriber (which is not the same as the distributor) could be disconnected for up to 3 days that's the number I would use so that no Transaction is lost even if the subscriber is out for a while. What is even more interesting is that you can even restore a backup of the db "within" the minimum-retention period and replication picks up from the correct LSN.
I have in many occasions set up distribution db in simple recovery mode and forget about Tlog on it. Now if consistency is a priority you may want to look at the "synch-with-backup" option but It is a lot of hassle to recover when you lose distrib anyway.
Just my $0.02
* Noel
March 16, 2009 at 1:26 pm
Thanks again. I worry too much and second guess myself alot. Guess it comes with the territory...
Have good day,
Alan
March 17, 2009 at 9:03 am
I worry too much and second guess myself alot. Guess it comes with the territory...
Good qualities for a DBA 😉
* Noel
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply