Log shipping through firewall

I attempted to set up log shipping where the standby server is in the DMZ
and the master server is on the internal network. Both are MSSQL 2000 servers.
I used the Maintenance Plan Wizard in order to set it up.
My problem is that the standby server does not appear in the list of servers
available to choose from when choosing a destination server. I would expect
that list to contain all servers found via broadcast on the local network,
as well as servers registered in EM, but the latter does not seem to be the
case.
The standby server is registered in the master servers EM, and port 1433
is open through the firewall, so the server can be managed. However, the
server still does not appear in the list of "destination servers" to choose
from.
What are the requirements for a server to appear in that list? Would opening
the RPC ports make a difference? (that is what's next on the agenda - as
file transfer uses the RPC).
Hi
Have your read
http://support.microsoft.com/default...b;en-us;287932
For most locations where you require to name a server, even if the server
does not appear you can usually type in the name.
John
"Inge" <inge@.norway.net> wrote in message
news:36b19dde6ba838c7d29534d97760@.news.microsoft.c om...
>I attempted to set up log shipping where the standby server is in the DMZ
>and the master server is on the internal network. Both are MSSQL 2000
>servers. I used the Maintenance Plan Wizard in order to set it up.
> My problem is that the standby server does not appear in the list of
> servers available to choose from when choosing a destination server. I
> would expect that list to contain all servers found via broadcast on the
> local network, as well as servers registered in EM, but the latter does
> not seem to be the case.
> The standby server is registered in the master servers EM, and port 1433
> is open through the firewall, so the server can be managed. However, the
> server still does not appear in the list of "destination servers" to
> choose from.
> What are the requirements for a server to appear in that list? Would
> opening the RPC ports make a difference? (that is what's next on the
> agenda - as file transfer uses the RPC).
>
|||Thank you for your quick reply!
I can successfully communicate through the port 1433 as per the article.
with EM on one side of the firewall, I can administer the server on the other
side, no problem.
Unfortunately, the dialog box with regards to Log Shipping does not allow
me to type in the name - I can only choose from the list. I would believe
that the servers in that list should include those registered in Enterprise
Manager on that server, but that does not appear to be the case.
[vbcol=seagreen]
> Hi
> Have your read
> http://support.microsoft.com/default...b;en-us;287932
> For most locations where you require to name a server, even if the
> server does not appear you can usually type in the name.
> John
> "Inge" <inge@.norway.net> wrote in message
> news:36b19dde6ba838c7d29534d97760@.news.microsoft.c om...
|||You have two issues to deal with in this scenario.
1. To get the list of servers you will need to open up UDP port 1434.
2. MS Logshipping requires that the account running running your SQL Agent
service be able to map a drive (open a UNC) to the destination server. This
means that AD must be available on both sides and that SMB traffic must be
allowed through the firewall. Most firewall admins don't like to open up
SMB taffic because of the exposures it causes. Since this is to the DMZ
perhaps thats not an issue.
An alternative would be write your own custom version of Log shipping. I
wrote one that uses FTP to send the log files. On the destination, a
routine is called to pick the sent files, check for contigous LSN and apply
them to standby mode.
Also bear in mind that every timie a log is being applied the database goes
offline during the restore.
"Inge" <inge@.norway.net> wrote in message
news:36b19dde6ba838c7d29534d97760@.news.microsoft.c om...
>I attempted to set up log shipping where the standby server is in the DMZ
>and the master server is on the internal network. Both are MSSQL 2000
>servers. I used the Maintenance Plan Wizard in order to set it up.
> My problem is that the standby server does not appear in the list of
> servers available to choose from when choosing a destination server. I
> would expect that list to contain all servers found via broadcast on the
> local network, as well as servers registered in EM, but the latter does
> not seem to be the case.
> The standby server is registered in the master servers EM, and port 1433
> is open through the firewall, so the server can be managed. However, the
> server still does not appear in the list of "destination servers" to
> choose from.
> What are the requirements for a server to appear in that list? Would
> opening the RPC ports make a difference? (that is what's next on the
> agenda - as file transfer uses the RPC).
>
|||The issue was that the DMZ server was std. edition, not Enterprise edition...
As long as the server is registered in the Log Shipping source EM, I don't
think the UDP port is necessary. The file share is still an issue, but we
can deal with it.
Thanks for the input
[vbcol=seagreen]
> You have two issues to deal with in this scenario.
> 1. To get the list of servers you will need to open up UDP port 1434.
> 2. MS Logshipping requires that the account running running your SQL
> Agent
> service be able to map a drive (open a UNC) to the destination server.
> This
> means that AD must be available on both sides and that SMB traffic
> must be
> allowed through the firewall. Most firewall admins don't like to open
> up
> SMB taffic because of the exposures it causes. Since this is to the
> DMZ
> perhaps thats not an issue.
> An alternative would be write your own custom version of Log shipping.
> I wrote one that uses FTP to send the log files. On the destination,
> a routine is called to pick the sent files, check for contigous LSN
> and apply them to standby mode.
> Also bear in mind that every timie a log is being applied the database
> goes offline during the restore.
> "Inge" <inge@.norway.net> wrote in message
> news:36b19dde6ba838c7d29534d97760@.news.microsoft.c om...
sql

Log shipping through firewall

I attempted to set up log shipping where the standby server is in the DMZ
and the master server is on the internal network. Both are MSSQL 2000 servers.
I used the Maintenance Plan Wizard in order to set it up.
My problem is that the standby server does not appear in the list of servers
available to choose from when choosing a destination server. I would expect
that list to contain all servers found via broadcast on the local network,
as well as servers registered in EM, but the latter does not seem to be the
case.
The standby server is registered in the master servers EM, and port 1433
is open through the firewall, so the server can be managed. However, the
server still does not appear in the list of "destination servers" to choose
from.
What are the requirements for a server to appear in that list? Would opening
the RPC ports make a difference? (that is what's next on the agenda - as
file transfer uses the RPC).Hi
Have your read
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
For most locations where you require to name a server, even if the server
does not appear you can usually type in the name.
John
"Inge" <inge@.norway.net> wrote in message
news:36b19dde6ba838c7d29534d97760@.news.microsoft.com...
>I attempted to set up log shipping where the standby server is in the DMZ
>and the master server is on the internal network. Both are MSSQL 2000
>servers. I used the Maintenance Plan Wizard in order to set it up.
> My problem is that the standby server does not appear in the list of
> servers available to choose from when choosing a destination server. I
> would expect that list to contain all servers found via broadcast on the
> local network, as well as servers registered in EM, but the latter does
> not seem to be the case.
> The standby server is registered in the master servers EM, and port 1433
> is open through the firewall, so the server can be managed. However, the
> server still does not appear in the list of "destination servers" to
> choose from.
> What are the requirements for a server to appear in that list? Would
> opening the RPC ports make a difference? (that is what's next on the
> agenda - as file transfer uses the RPC).
>|||You have two issues to deal with in this scenario.
1. To get the list of servers you will need to open up UDP port 1434.
2. MS Logshipping requires that the account running running your SQL Agent
service be able to map a drive (open a UNC) to the destination server. This
means that AD must be available on both sides and that SMB traffic must be
allowed through the firewall. Most firewall admins don't like to open up
SMB taffic because of the exposures it causes. Since this is to the DMZ
perhaps thats not an issue.
An alternative would be write your own custom version of Log shipping. I
wrote one that uses FTP to send the log files. On the destination, a
routine is called to pick the sent files, check for contigous LSN and apply
them to standby mode.
Also bear in mind that every timie a log is being applied the database goes
offline during the restore.
"Inge" <inge@.norway.net> wrote in message
news:36b19dde6ba838c7d29534d97760@.news.microsoft.com...
>I attempted to set up log shipping where the standby server is in the DMZ
>and the master server is on the internal network. Both are MSSQL 2000
>servers. I used the Maintenance Plan Wizard in order to set it up.
> My problem is that the standby server does not appear in the list of
> servers available to choose from when choosing a destination server. I
> would expect that list to contain all servers found via broadcast on the
> local network, as well as servers registered in EM, but the latter does
> not seem to be the case.
> The standby server is registered in the master servers EM, and port 1433
> is open through the firewall, so the server can be managed. However, the
> server still does not appear in the list of "destination servers" to
> choose from.
> What are the requirements for a server to appear in that list? Would
> opening the RPC ports make a difference? (that is what's next on the
> agenda - as file transfer uses the RPC).
>

Log shipping through firewall

I attempted to set up log shipping where the standby server is in the DMZ
and the master server is on the internal network. Both are MSSQL 2000 server
s.
I used the Maintenance Plan Wizard in order to set it up.
My problem is that the standby server does not appear in the list of servers
available to choose from when choosing a destination server. I would expect
that list to contain all servers found via broadcast on the local network,
as well as servers registered in EM, but the latter does not seem to be the
case.
The standby server is registered in the master servers EM, and port 1433
is open through the firewall, so the server can be managed. However, the
server still does not appear in the list of "destination servers" to choose
from.
What are the requirements for a server to appear in that list? Would opening
the RPC ports make a difference? (that is what's next on the agenda - as
file transfer uses the RPC).Hi
Have your read
http://support.microsoft.com/defaul...kb;en-us;287932
For most locations where you require to name a server, even if the server
does not appear you can usually type in the name.
John
"Inge" <inge@.norway.net> wrote in message
news:36b19dde6ba838c7d29534d97760@.news.microsoft.com...
>I attempted to set up log shipping where the standby server is in the DMZ
>and the master server is on the internal network. Both are MSSQL 2000
>servers. I used the Maintenance Plan Wizard in order to set it up.
> My problem is that the standby server does not appear in the list of
> servers available to choose from when choosing a destination server. I
> would expect that list to contain all servers found via broadcast on the
> local network, as well as servers registered in EM, but the latter does
> not seem to be the case.
> The standby server is registered in the master servers EM, and port 1433
> is open through the firewall, so the server can be managed. However, the
> server still does not appear in the list of "destination servers" to
> choose from.
> What are the requirements for a server to appear in that list? Would
> opening the RPC ports make a difference? (that is what's next on the
> agenda - as file transfer uses the RPC).
>|||Thank you for your quick reply!
I can successfully communicate through the port 1433 as per the article.
with EM on one side of the firewall, I can administer the server on the othe
r
side, no problem.
Unfortunately, the dialog box with regards to Log Shipping does not allow
me to type in the name - I can only choose from the list. I would believe
that the servers in that list should include those registered in Enterprise
Manager on that server, but that does not appear to be the case.
[vbcol=seagreen]
> Hi
> Have your read
> http://support.microsoft.com/defaul...kb;en-us;287932
> For most locations where you require to name a server, even if the
> server does not appear you can usually type in the name.
> John
> "Inge" <inge@.norway.net> wrote in message
> news:36b19dde6ba838c7d29534d97760@.news.microsoft.com...
>|||You have two issues to deal with in this scenario.
1. To get the list of servers you will need to open up UDP port 1434.
2. MS Logshipping requires that the account running running your SQL Agent
service be able to map a drive (open a UNC) to the destination server. This
means that AD must be available on both sides and that SMB traffic must be
allowed through the firewall. Most firewall admins don't like to open up
SMB taffic because of the exposures it causes. Since this is to the DMZ
perhaps thats not an issue.
An alternative would be write your own custom version of Log shipping. I
wrote one that uses FTP to send the log files. On the destination, a
routine is called to pick the sent files, check for contigous LSN and apply
them to standby mode.
Also bear in mind that every timie a log is being applied the database goes
offline during the restore.
"Inge" <inge@.norway.net> wrote in message
news:36b19dde6ba838c7d29534d97760@.news.microsoft.com...
>I attempted to set up log shipping where the standby server is in the DMZ
>and the master server is on the internal network. Both are MSSQL 2000
>servers. I used the Maintenance Plan Wizard in order to set it up.
> My problem is that the standby server does not appear in the list of
> servers available to choose from when choosing a destination server. I
> would expect that list to contain all servers found via broadcast on the
> local network, as well as servers registered in EM, but the latter does
> not seem to be the case.
> The standby server is registered in the master servers EM, and port 1433
> is open through the firewall, so the server can be managed. However, the
> server still does not appear in the list of "destination servers" to
> choose from.
> What are the requirements for a server to appear in that list? Would
> opening the RPC ports make a difference? (that is what's next on the
> agenda - as file transfer uses the RPC).
>|||The issue was that the DMZ server was std. edition, not Enterprise edition..
.
As long as the server is registered in the Log Shipping source EM, I don't
think the UDP port is necessary. The file share is still an issue, but we
can deal with it.
Thanks for the input
[vbcol=seagreen]
> You have two issues to deal with in this scenario.
> 1. To get the list of servers you will need to open up UDP port 1434.
> 2. MS Logshipping requires that the account running running your SQL
> Agent
> service be able to map a drive (open a UNC) to the destination server.
> This
> means that AD must be available on both sides and that SMB traffic
> must be
> allowed through the firewall. Most firewall admins don't like to open
> up
> SMB taffic because of the exposures it causes. Since this is to the
> DMZ
> perhaps thats not an issue.
> An alternative would be write your own custom version of Log shipping.
> I wrote one that uses FTP to send the log files. On the destination,
> a routine is called to pick the sent files, check for contigous LSN
> and apply them to standby mode.
> Also bear in mind that every timie a log is being applied the database
> goes offline during the restore.
> "Inge" <inge@.norway.net> wrote in message
> news:36b19dde6ba838c7d29534d97760@.news.microsoft.com...
>

Log Shipping Problem

Hi there,

I am currently trying to set-up log shipping for one of my databases. In order to set this up I am trying to backup the master database on the primary server and restore it on the secondary server. When I try and restore it I get a message saying that the master database has been restored successfully but then the database crashes and I can't get it to restart unless I use the rebuildm utility.

Any ideas what could be causing this? The servers are both SP4 and use the same collation types.

I've spent hours on this so any help would be appreciated.

ThanksForgive me, but why are you trying to restore the master database on the secondary server? To my knowledge, that's not part of the setup process. Restoring the master database is an entirely different process and needs to be handled totally outside the context of log shipping.

Regards,

hmscott|||Hi there,

Sorry for the delay in replying. I'm following a document that a collegue put together. One of the steps he has listed is to restore the master db from the Primary Server to the Secondary Server. The Secondary Server will be used as a failover server so I pressume this is to make sure that the ss can take over the trole of the ps in event of failure?? Is this not the case? I'm not using the wizard to set this up.|||Okay, it's been a while (about two years), but at one time I managed a log shipping pair. Here are the things that I remember:

1. I remember nothing about having to restore the master db to the secondary. The master db handles information about databases, files, devices, logins and server-wide info. When you set up log shipping, the database and file placement information carries forward with the log shipping process. [edit: this is not entirely correct; you specify the placement of files for the destination database when you create the destination database. There is no requirement that the destination file locations match source file locations, although this would be a prudent measure. Sorry for the misleading comment.]

I do remember that the SQL Server Login information DOES NOT carry forward. Thus, you will need to set up a manual process to copy logins from the primary server to the secondary. Do a google on sp_resolve_logins.

Also, please check this link (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_1_013_9t0p.asp).

2. The log shipping process pretty much handles the remaining processes (transferring data, copying over schema changes and even permissions). You have to remember to set up individual log shipping processes for each database on the primary server.

3. There is nothing automatic about the failover process. Applications (or users) will need to update IP addresses and the secondary server will have to be placed into the primary role.

Finally, you might want to check out this link (http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx) as well.

Regards,

hmscott|||Thanks, I'll look into it and let you know how I get on.|||Just to say thanks for your help. I managed to set it up by:

1) Making sure that all sql services were running under an account with network permissions.

2) Transfering the logins from the primary server to the secondary server using the Transfer Logins Task within DTS. (not restoring the master database as i was instructed by a colleague)

Matt

Log shipping and Manual backups

I have set up a log shipping on my master and backup database, where a full
backup of the master database is done each day at midnight and restored to
the backup database. The master databases transaction logs are then backed
up and restored to the backup database every 10 minutes.
My users want to also have the ability to do manual full database backups as
well. However I am unsure whether or not this will have the affect that the
log shipping operations.
Will this cause the master and backup databases to get out of synch until
the full backup and restore is performed at midnight?
Thanks in advance
No worries. Database backup does not break the log backup chain.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Parks" <treatyourselfnow@.hotmail.com> wrote in message
news:%23OJ4KyGHGHA.3120@.TK2MSFTNGP10.phx.gbl...
>I have set up a log shipping on my master and backup database, where a full backup of the master
>database is done each day at midnight and restored to the backup database. The master databases
>transaction logs are then backed up and restored to the backup database every 10 minutes.
> My users want to also have the ability to do manual full database backups as well. However I am
> unsure whether or not this will have the affect that the log shipping operations.
> Will this cause the master and backup databases to get out of synch until the full backup and
> restore is performed at midnight?
> Thanks in advance
>

Log shipping and Manual backups

I have set up a log shipping on my master and backup database, where a full
backup of the master database is done each day at midnight and restored to
the backup database. The master databases transaction logs are then backed
up and restored to the backup database every 10 minutes.
My users want to also have the ability to do manual full database backups as
well. However I am unsure whether or not this will have the affect that the
log shipping operations.
Will this cause the master and backup databases to get out of synch until
the full backup and restore is performed at midnight?
Thanks in advanceNo worries. Database backup does not break the log backup chain.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Parks" <treatyourselfnow@.hotmail.com> wrote in message
news:%23OJ4KyGHGHA.3120@.TK2MSFTNGP10.phx.gbl...
>I have set up a log shipping on my master and backup database, where a full backup of the master
>database is done each day at midnight and restored to the backup database. The master databases
>transaction logs are then backed up and restored to the backup database every 10 minutes.
> My users want to also have the ability to do manual full database backups as well. However I am
> unsure whether or not this will have the affect that the log shipping operations.
> Will this cause the master and backup databases to get out of synch until the full backup and
> restore is performed at midnight?
> Thanks in advance
>

Log shipping and Manual backups

I have set up a log shipping on my master and backup database, where a full
backup of the master database is done each day at midnight and restored to
the backup database. The master databases transaction logs are then backed
up and restored to the backup database every 10 minutes.
My users want to also have the ability to do manual full database backups as
well. However I am unsure whether or not this will have the affect that the
log shipping operations.
Will this cause the master and backup databases to get out of synch until
the full backup and restore is performed at midnight?
Thanks in advanceNo worries. Database backup does not break the log backup chain.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Parks" <treatyourselfnow@.hotmail.com> wrote in message
news:%23OJ4KyGHGHA.3120@.TK2MSFTNGP10.phx.gbl...
>I have set up a log shipping on my master and backup database, where a full
backup of the master
>database is done each day at midnight and restored to the backup database.
The master databases
>transaction logs are then backed up and restored to the backup database eve
ry 10 minutes.
> My users want to also have the ability to do manual full database backups
as well. However I am
> unsure whether or not this will have the affect that the log shipping oper
ations.
> Will this cause the master and backup databases to get out of synch until
the full backup and
> restore is performed at midnight?
> Thanks in advance
>