June 30, 2009 at 10:00 am
Hi,
We are ready to configure log shipping in SQL Server 2005.
Couple of questions:
1.Can we use a Virtual server for Monitoring Log shipping of Production databases?
2. Which location is the best palce to keep monitoring server? Primary location or the Secondary DRT location?
3. Can we use developer edition of sql server 2005 for monitoring purpose?
thanks
June 30, 2009 at 10:10 am
Hi
I am not sure what exactly you mean by monitoring, are you going to install a 3rd party software for monitoring, which requires a separate server?
Yes you can use Virtual machine for monitoring, providing that machine is accessible by your production server
Not sure about the developer edition for monitoring.
June 30, 2009 at 10:15 am
I am not sure what exactly you mean by monitoring, are you going to install a 3rd party software for monitoring, which requires a separate server?
Its not a 3rd party tool. I'm talking about the Monitor Server Instance, that we mention in the Log shipping wizard.
Is it legal to use developer edition of sql server 2005 for monitoring purpose?
June 30, 2009 at 10:56 am
rambilla4 (6/30/2009)
Hi,We are ready to configure log shipping in SQL Server 2005.
Couple of questions:
1.Can we use a Virtual server for Monitoring Log shipping of Production databases?
If you mean wmware yes you could
2. Which location is the best palce to keep monitoring server? Primary location or the Secondary DRT location?
DR location, more likely to be available in case of failure. Not havin g the monitor is not the end of the world though and will not prevent recovery.
3. Can we use developer edition of sql server 2005 for monitoring purpose?
Yes. In fact probably best solution in terms of cost.
---------------------------------------------------------------------
June 30, 2009 at 1:10 pm
I may be missing the point but isn't this overkill! We have logshipping with email notification when the secondary server gets no update within a set time over a set duration. What is this additional instance doing that this doesn't accomplish? It costs also costs nothing! If you use a VM you still have to buy the OS license plus other Virus scan etc that your company insist on.
June 30, 2009 at 1:35 pm
Because if we use either primary or secondary server instance as Monitor server, the performance will be Degraded. I do not know much this will impact on the performance. So We decided to go for 3rd server as a Monitor server?
please advice...
June 30, 2009 at 2:44 pm
Well I do survive without a monitor server myself and I don't think I would ever bother with one.
Microsoft would say that as log-shipping is controlled via SQLAgent jobs all the information about the job runs and log shipping history is local to the server, and therefore if you lose the server you lose that information as well so might not be aware of the state of the secondary. Having a monitor server forces the information to be written to the monitor as well as locally. I would have to agree it does not give you much as there are plenty of sources of information on what state the logshipping is in, including the local msdb, the errorlog and contents of the shares for the transaction logs. I cannot think of a situation where I could not work it out.
Its just belt and braces. What a monitor does give you is it can act as a monitor for multiple log shipping set ups and therefore could centralise your monitoring of logshipping, I can see a use for that.
---------------------------------------------------------------------
June 30, 2009 at 2:47 pm
p.s. logshipping monitoring locally has no performance hit. very small amount of activity in msdb but that's on a seperate drive right? 🙂
---------------------------------------------------------------------
June 30, 2009 at 3:25 pm
We have system database's mdf, ldf and user databases mdf files on one drive and user databases ldf files on other drive.
The reason for going to a have a separate Monitor server is, we 15 databases and we want to Log ship all the databases. In this case for each database log shipping configuration creates
2 jobs on Primary and 3 jobs on Secondary. So total 5 jobs for each databases. So on Primary 15*2=30 jobs and on Secondary 15*3=45 jobs. If we create a separate Monitor server, then at least I can have these alert jobs on that and the no.of jobs on Primary and secondary will be reduced.
On Primary:
LSAlert_SQL1\INS1
LSBackup_DB_Name
On Secondary:
LSAlert_SQL2
LSCopy_SQL1\INS1_DB_Name
LSRestore_SQL1\INS1_DB_Name
We just building a Virtual machine with only one drive i.e OS drive C and install sql server 2005 developer edition and use it as a Log shipping Monitor server. There will be no databases on this, so just OS drive is fine.
Advice if I need to make any changes..
June 30, 2009 at 3:35 pm
rambilla4 (6/30/2009)
We have system database's mdf, ldf and user databases mdf files on one drive and user databases ldf files on other drive.We just building a Virtual machine with only one drive i.e OS drive C and install sql server 2005 developer edition and use it as a Log shipping Monitor server. There will be no databases on this, so just OS drive is fine.
Advice if I need to make any changes..
that should suffice as a monitoring server.
---------------------------------------------------------------------
July 1, 2009 at 12:11 am
1.Is it legal to use developer edition of sql server 2005 for monitoring purpose in production environment?
2.Can we use the same Monitor server, for monitoring log shipping of the sql instances that are in different domain?
I mean lets say
Primary Server Location: Secondary Server(DR)Location:
Server A is in abc.com domain Server B is in abc.com domain
Server C is in xyz.com Server D is in xyz.com
Now Monitor Server is in abc.com and used to Monitor Log shipping in Server A(which is in abc.com).
Now Can we use the same Monitor server to Monitor log shipping in Server C(which is in xyz.com)
thanks
July 1, 2009 at 3:35 am
rambilla4 (7/1/2009)
1.Is it legal to use developer edition of sql server 2005 for monitoring purpose in production environment?
yes, because its not supporting a production application itself.
2.Can we use the same Monitor server, for monitoring log shipping of the sql instances that are in different domain?
I mean lets say
Primary Server Location: Secondary Server(DR)Location:
Server A is in abc.com domain Server B is in abc.com domain
Server C is in xyz.com Server D is in xyz.com
Now Monitor Server is in abc.com and used to Monitor Log shipping in Server A(which is in abc.com).
Now Can we use the same Monitor server to Monitor log shipping in Server C(which is in xyz.com)
thanks
Not tried it but I would imagine a trust between the domains would do it. The service account used for servers C and D would have to be added to the monitor with enough rights to update msdb.
If you have a number of log shipping set ups in each domain how about a monitor in both domains?
the monitor will monitor both primary and secondary.
---------------------------------------------------------------------
July 1, 2009 at 9:31 am
Is it legal to use developer edition of sql server 2005 for monitoring purpose in production environment?
yes, because its not supporting a production application itself.
Can you point me to BOL, where it says that we can use Developer edition of SQL Server 2005 as Monitor Server to Monitor Log shipping Of a Production Server??
thanks a lot...
July 1, 2009 at 9:44 am
rambilla4 (7/1/2009)
Is it legal to use developer edition of sql server 2005 for monitoring purpose in production environment?
yes, because its not supporting a production application itself.
Can you point me to BOL, where it says that we can use Developer edition of SQL Server 2005 as Monitor Server to Monitor Log shipping Of a Production Server??
thanks a lot...
You cant use developer edition to monitor log shipping of a production server.
July 1, 2009 at 10:04 am
AlexSQLForums (7/1/2009)
rambilla4 (7/1/2009)
Is it legal to use developer edition of sql server 2005 for monitoring purpose in production environment?
yes, because its not supporting a production application itself.
Can you point me to BOL, where it says that we can use Developer edition of SQL Server 2005 as Monitor Server to Monitor Log shipping Of a Production Server??
thanks a lot...
You cant use developer edition to monitor log shipping of a production server.
As its not supporting a production database I don't see why not. They allow express edition as a mirroring witness server, what's the difference.?
I don't think you will find it in writing, but try googling it or searching on log shipping in BOL. Only final proof is to check with microsoft.
---------------------------------------------------------------------
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply