When using the Database Maintenance Plan WIzard to setup log shipping I have
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.com
Easy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
Showing posts with label destination. Show all posts
Showing posts with label destination. Show all posts
Wednesday, March 28, 2012
Log Shipping Setup Problem
When using the Database Maintenance Plan WIzard to setup log shipping I have
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
Log Shipping Setup Problem
When using the Database Maintenance Plan WIzard to setup log shipping I have
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I ha
ve
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is n
ot
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I ha
ve
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is n
ot
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
Friday, March 23, 2012
Log Shipping Question
Using Log shipping via SQL Ent Edition, do all your users have to be disconnected from the destination server the logs are being pushed to?
Say, user x is pulling a report from the server, and it takes 2 minutes, after 1 minutes the scedualed log ship needs to take place, will the log ship fail? will the user get kicked off? or will the logs be applied like nothing happend since its read only?
Anyones that used log shipping alot let me know! Thanks
ChrisI believe because you leave the destination database in recoverable mode, users can not query it - see links for more details
http://support.microsoft.com/default.aspx?scid=kb;en-us;314515
http://www.sql-server-performance.com/sql_server_log_shipping.asp
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
HTH|||And also this Q&A - http://www.sql-server-performance.com/q&a37.asp|||With Log Shipping, the destination db's are read only. Your users can query them as much as they like - the only stipulation is that they can't have an active connection to a database while it's logs are being restored - I simply have a process that kills any connections to the db before I restore the logs - and that takes care of the issue. Hope this helps.
Nick DeAngelo|||Refer to the link provided by me to kill those SPIDs before restoring the log.|||Thanks for pointing that out Nick, I forgot about that
Say, user x is pulling a report from the server, and it takes 2 minutes, after 1 minutes the scedualed log ship needs to take place, will the log ship fail? will the user get kicked off? or will the logs be applied like nothing happend since its read only?
Anyones that used log shipping alot let me know! Thanks
ChrisI believe because you leave the destination database in recoverable mode, users can not query it - see links for more details
http://support.microsoft.com/default.aspx?scid=kb;en-us;314515
http://www.sql-server-performance.com/sql_server_log_shipping.asp
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
HTH|||And also this Q&A - http://www.sql-server-performance.com/q&a37.asp|||With Log Shipping, the destination db's are read only. Your users can query them as much as they like - the only stipulation is that they can't have an active connection to a database while it's logs are being restored - I simply have a process that kills any connections to the db before I restore the logs - and that takes care of the issue. Hope this helps.
Nick DeAngelo|||Refer to the link provided by me to kill those SPIDs before restoring the log.|||Thanks for pointing that out Nick, I forgot about that
Wednesday, March 21, 2012
log shipping not working
hello, on the destination server he says the restore job has failed
and my log shipping databases are then out of sync. where do i begin
to find out why my log shipping is no longer working? my two servers
are in differnet locations but i can ping and returns are under 50ms.
help?
thanks
APAP
Is it one log it has failed to apply or several? Sometimes
one log may fail to apply for a number of reasons. Next
time the target server tries to apply the logs it should
try to apply all logs since it last applied one. Quite
often it can catch up.
One common reason for log shipping failure is having the
restore on the target run too soon after the backup on the
source. Occasionally the restore tries to run before the
backup finishes. This may be because a big work load on
the source has caused a larger than normal log. It may be
the servers have got out of sync time wise.
Hope this helps
John|||thanks you john, it looks to me that the log shipping has never worked
since the backup was restored in the destincation server. these is a
small database like 63 mb so backup times is quick. each site has a
t1 or faster.
how do i get them back to sync?
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0ec801c3aa02$82d32cc0$a401280a@.phx.gbl>...
> AP
> Is it one log it has failed to apply or several? Sometimes
> one log may fail to apply for a number of reasons. Next
> time the target server tries to apply the logs it should
> try to apply all logs since it last applied one. Quite
> often it can catch up.
> One common reason for log shipping failure is having the
> restore on the target run too soon after the backup on the
> source. Occasionally the restore tries to run before the
> backup finishes. This may be because a big work load on
> the source has caused a larger than normal log. It may be
> the servers have got out of sync time wise.
> Hope this helps
> John|||Antonio
You will need to copy a recent full backup to your standby
server, to re-establish the log shipping.
I don't have a copy of Enterprise edition that I can look
at at the moment to see exactly how you do it. There
should be an option somewhere to re-establish it.
The fact that it has never worked suggests there is a
problem anyway. Permissions on the share on the target
server is quite a common problem. Use 'xp_cmdshell' on
your source database to check the permissions work. (Do
a 'dir' on it).
Also worth having a look at this link.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;323135
Hope this helps
John|||thank you again. i did check permissions. i see on teh source and
destination server where the transaction logs are that all are on both
servers so i see this to mean that the logs are baccking up on the
source server good and they are being transmisssion to the destination
server good. it looks to me that the logs are shipping ok but not
being replayed on the destination server.
this probably changes your recommentations.
what do you think about it now?
thanks
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0adc01c3aac4$4e192ad0$a501280a@.phx.gbl>...
> Antonio
> You will need to copy a recent full backup to your standby
> server, to re-establish the log shipping.
> I don't have a copy of Enterprise edition that I can look
> at at the moment to see exactly how you do it. There
> should be an option somewhere to re-establish it.
> The fact that it has never worked suggests there is a
> problem anyway. Permissions on the share on the target
> server is quite a common problem. Use 'xp_cmdshell' on
> your source database to check the permissions work. (Do
> a 'dir' on it).
> Also worth having a look at this link.
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;323135
> Hope this helps
> John|||Antonio
Last thing I can think of suggesting is to try running the
SQL Server agent as a local domain account with the same
name and password on both servers.
I have seen this work.
Regards
John
and my log shipping databases are then out of sync. where do i begin
to find out why my log shipping is no longer working? my two servers
are in differnet locations but i can ping and returns are under 50ms.
help?
thanks
APAP
Is it one log it has failed to apply or several? Sometimes
one log may fail to apply for a number of reasons. Next
time the target server tries to apply the logs it should
try to apply all logs since it last applied one. Quite
often it can catch up.
One common reason for log shipping failure is having the
restore on the target run too soon after the backup on the
source. Occasionally the restore tries to run before the
backup finishes. This may be because a big work load on
the source has caused a larger than normal log. It may be
the servers have got out of sync time wise.
Hope this helps
John|||thanks you john, it looks to me that the log shipping has never worked
since the backup was restored in the destincation server. these is a
small database like 63 mb so backup times is quick. each site has a
t1 or faster.
how do i get them back to sync?
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0ec801c3aa02$82d32cc0$a401280a@.phx.gbl>...
> AP
> Is it one log it has failed to apply or several? Sometimes
> one log may fail to apply for a number of reasons. Next
> time the target server tries to apply the logs it should
> try to apply all logs since it last applied one. Quite
> often it can catch up.
> One common reason for log shipping failure is having the
> restore on the target run too soon after the backup on the
> source. Occasionally the restore tries to run before the
> backup finishes. This may be because a big work load on
> the source has caused a larger than normal log. It may be
> the servers have got out of sync time wise.
> Hope this helps
> John|||Antonio
You will need to copy a recent full backup to your standby
server, to re-establish the log shipping.
I don't have a copy of Enterprise edition that I can look
at at the moment to see exactly how you do it. There
should be an option somewhere to re-establish it.
The fact that it has never worked suggests there is a
problem anyway. Permissions on the share on the target
server is quite a common problem. Use 'xp_cmdshell' on
your source database to check the permissions work. (Do
a 'dir' on it).
Also worth having a look at this link.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;323135
Hope this helps
John|||thank you again. i did check permissions. i see on teh source and
destination server where the transaction logs are that all are on both
servers so i see this to mean that the logs are baccking up on the
source server good and they are being transmisssion to the destination
server good. it looks to me that the logs are shipping ok but not
being replayed on the destination server.
this probably changes your recommentations.
what do you think about it now?
thanks
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0adc01c3aac4$4e192ad0$a501280a@.phx.gbl>...
> Antonio
> You will need to copy a recent full backup to your standby
> server, to re-establish the log shipping.
> I don't have a copy of Enterprise edition that I can look
> at at the moment to see exactly how you do it. There
> should be an option somewhere to re-establish it.
> The fact that it has never worked suggests there is a
> problem anyway. Permissions on the share on the target
> server is quite a common problem. Use 'xp_cmdshell' on
> your source database to check the permissions work. (Do
> a 'dir' on it).
> Also worth having a look at this link.
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;323135
> Hope this helps
> John|||Antonio
Last thing I can think of suggesting is to try running the
SQL Server agent as a local domain account with the same
name and password on both servers.
I have seen this work.
Regards
John
Log Shipping Monitor Shows Problems when there aren't any
I Have setup a pair of server with log shipping, it works perfectly, logs are
backed up every 2 mins and restored succesfully to the destination server. My
only problem is that the monitor (running on the backup server) thinks that
things are not working correctly. It shows the correct times for the copy and
load jobs but the backup job time never gets updated. I have read the MS KB
article 292586 which states that this could be a permissions issue that the
source server does not have permissions to update the msdb database on the
destination server, however I have tried changing things in this area by
having the sql account running with full admin privs (both domain admin and
sql admin) this didnt work, I also tried running sql in mixed auth mode and
then configurung log shipping to use SQL authentication, it correctly created
the new log_shipping_monitor account, but still the log shipping monitor
refuses to work. Can somebody help me before I pull all my hair out.
Brett
Hello Brett,
My suggestion is that you reset password for log_shipping_monitor_probe
account on all shipping databases (both secondary and primary) and removed
and
reapplied permissions to the log shipping tables on both primary and
secondary servers. If log_shipping_monitor_prob does not exist, create the
login, set the default
database to msdb, and grant it access to msdb.
On both Primary / Secondary server, right click the log shipping database,
select properties. In the general tab, click the details button for log
shipping. Select "Use SQL Server Authentication" and change the password
to log_shipping_monitor_prob account.
More related information:
321247 How To Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Log Shipping Monitor Shows Problems when there aren't any
>thread-index: AcX4xD/DRKnfVG7nSZmLj/7UPPi8Vg==
>X-WBNR-Posting-Host: 194.109.239.116
>From: "=?Utf-8?B?QnJldHQgQ2Fycg==?=" <brettcarr@.news.postalias>
>Subject: Log Shipping Monitor Shows Problems when there aren't any
>Date: Sun, 4 Dec 2005 03:17:01 -0800
>Lines: 15
>Message-ID: <0E563B60-3095-4635-BC0A-3153BEB87CDB@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:67206
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>I Have setup a pair of server with log shipping, it works perfectly, logs
are
>backed up every 2 mins and restored succesfully to the destination server.
My
>only problem is that the monitor (running on the backup server) thinks
that
>things are not working correctly. It shows the correct times for the copy
and
>load jobs but the backup job time never gets updated. I have read the MS
KB
>article 292586 which states that this could be a permissions issue that
the
>source server does not have permissions to update the msdb database on the
>destination server, however I have tried changing things in this area by
>having the sql account running with full admin privs (both domain admin
and
>sql admin) this didnt work, I also tried running sql in mixed auth mode
and
>then configurung log shipping to use SQL authentication, it correctly
created
>the new log_shipping_monitor account, but still the log shipping monitor
>refuses to work. Can somebody help me before I pull all my hair out.
>Brett
>
|||"Peter Yang [MSFT]" wrote:
> Hello Brett,
> My suggestion is that you reset password for log_shipping_monitor_probe
> account on all shipping databases (both secondary and primary) and removed
> and
> reapplied permissions to the log shipping tables on both primary and
> secondary servers. If log_shipping_monitor_prob does not exist, create the
> login, set the default
> database to msdb, and grant it access to msdb.
> On both Primary / Secondary server, right click the log shipping database,
> select properties. In the general tab, click the details button for log
> shipping. Select "Use SQL Server Authentication" and change the password
> to log_shipping_monitor_prob account.
>
Ok. I've done the following:
1. log_shipping_monitor_prob did not exist on the primary server so I
created it.
2. I reset the password for log_shipping_monitor_prob on both primary and
secondary.
3. On both primary and secondary servers I have set
log_shipping_monitor_prob to have select,insert,update and delete permissions
on all tables starting with log_shipping in the msdb database.
However I'm afraid the 'Last Backup' date and time listed in the monitor is
still the date and time I set it up originally. The Last copy and Last
restore dates are still being updated correctly.
Brett..
|||Hello Brett,
Going forward, I'd like to confirm if Windows Authentication option is
selected on the Specify The Log Shipping Monitor Server Information screen
during log shipping setup.
If so, you may want to check if the SQL Server Service startup account on
the primary server of a log shipping pair does not have sufficient
privileges to update table msdb..log_shipping_primaries on the monitor
server.
Also, please check if the value in primary_server_name column in
log_shipping_primaries does not match the <@.@.servername> of the primary
server.
If the issue persists, please use SQL profiler on the monitor server to see
if the update operation on log_shipping_primaries occurs or if there is any
related errors in error log.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Log Shipping Monitor Shows Problems when there aren't any
>thread-index: AcX5iaV+Rf+MfqKZTvqVdLuPrgGVlw==
>X-WBNR-Posting-Host: 193.0.2.180
>From: "=?Utf-8?B?QnJldHQgQ2Fycg==?=" <brettcarr@.news.postalias>
>References: <0E563B60-3095-4635-BC0A-3153BEB87CDB@.microsoft.com>
<VAQE#gX#FHA.1236@.TK2MSFTNGXA02.phx.gbl>[vbcol=seagreen]
>Subject: RE: Log Shipping Monitor Shows Problems when there aren't any
>Date: Mon, 5 Dec 2005 02:50:03 -0800
>Lines: 35
>Message-ID: <33C3B088-9CA3-4C3E-98B1-86E784833DDC@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:67231
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>"Peter Yang [MSFT]" wrote:
removed[vbcol=seagreen]
the[vbcol=seagreen]
database,[vbcol=seagreen]
password
>Ok. I've done the following:
>1. log_shipping_monitor_prob did not exist on the primary server so I
>created it.
>2. I reset the password for log_shipping_monitor_prob on both primary and
>secondary.
>3. On both primary and secondary servers I have set
>log_shipping_monitor_prob to have select,insert,update and delete
permissions
>on all tables starting with log_shipping in the msdb database.
>However I'm afraid the 'Last Backup' date and time listed in the monitor
is
>still the date and time I set it up originally. The Last copy and Last
>restore dates are still being updated correctly.
>Brett..
>
>
backed up every 2 mins and restored succesfully to the destination server. My
only problem is that the monitor (running on the backup server) thinks that
things are not working correctly. It shows the correct times for the copy and
load jobs but the backup job time never gets updated. I have read the MS KB
article 292586 which states that this could be a permissions issue that the
source server does not have permissions to update the msdb database on the
destination server, however I have tried changing things in this area by
having the sql account running with full admin privs (both domain admin and
sql admin) this didnt work, I also tried running sql in mixed auth mode and
then configurung log shipping to use SQL authentication, it correctly created
the new log_shipping_monitor account, but still the log shipping monitor
refuses to work. Can somebody help me before I pull all my hair out.
Brett
Hello Brett,
My suggestion is that you reset password for log_shipping_monitor_probe
account on all shipping databases (both secondary and primary) and removed
and
reapplied permissions to the log shipping tables on both primary and
secondary servers. If log_shipping_monitor_prob does not exist, create the
login, set the default
database to msdb, and grant it access to msdb.
On both Primary / Secondary server, right click the log shipping database,
select properties. In the general tab, click the details button for log
shipping. Select "Use SQL Server Authentication" and change the password
to log_shipping_monitor_prob account.
More related information:
321247 How To Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Log Shipping Monitor Shows Problems when there aren't any
>thread-index: AcX4xD/DRKnfVG7nSZmLj/7UPPi8Vg==
>X-WBNR-Posting-Host: 194.109.239.116
>From: "=?Utf-8?B?QnJldHQgQ2Fycg==?=" <brettcarr@.news.postalias>
>Subject: Log Shipping Monitor Shows Problems when there aren't any
>Date: Sun, 4 Dec 2005 03:17:01 -0800
>Lines: 15
>Message-ID: <0E563B60-3095-4635-BC0A-3153BEB87CDB@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:67206
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>I Have setup a pair of server with log shipping, it works perfectly, logs
are
>backed up every 2 mins and restored succesfully to the destination server.
My
>only problem is that the monitor (running on the backup server) thinks
that
>things are not working correctly. It shows the correct times for the copy
and
>load jobs but the backup job time never gets updated. I have read the MS
KB
>article 292586 which states that this could be a permissions issue that
the
>source server does not have permissions to update the msdb database on the
>destination server, however I have tried changing things in this area by
>having the sql account running with full admin privs (both domain admin
and
>sql admin) this didnt work, I also tried running sql in mixed auth mode
and
>then configurung log shipping to use SQL authentication, it correctly
created
>the new log_shipping_monitor account, but still the log shipping monitor
>refuses to work. Can somebody help me before I pull all my hair out.
>Brett
>
|||"Peter Yang [MSFT]" wrote:
> Hello Brett,
> My suggestion is that you reset password for log_shipping_monitor_probe
> account on all shipping databases (both secondary and primary) and removed
> and
> reapplied permissions to the log shipping tables on both primary and
> secondary servers. If log_shipping_monitor_prob does not exist, create the
> login, set the default
> database to msdb, and grant it access to msdb.
> On both Primary / Secondary server, right click the log shipping database,
> select properties. In the general tab, click the details button for log
> shipping. Select "Use SQL Server Authentication" and change the password
> to log_shipping_monitor_prob account.
>
Ok. I've done the following:
1. log_shipping_monitor_prob did not exist on the primary server so I
created it.
2. I reset the password for log_shipping_monitor_prob on both primary and
secondary.
3. On both primary and secondary servers I have set
log_shipping_monitor_prob to have select,insert,update and delete permissions
on all tables starting with log_shipping in the msdb database.
However I'm afraid the 'Last Backup' date and time listed in the monitor is
still the date and time I set it up originally. The Last copy and Last
restore dates are still being updated correctly.
Brett..
|||Hello Brett,
Going forward, I'd like to confirm if Windows Authentication option is
selected on the Specify The Log Shipping Monitor Server Information screen
during log shipping setup.
If so, you may want to check if the SQL Server Service startup account on
the primary server of a log shipping pair does not have sufficient
privileges to update table msdb..log_shipping_primaries on the monitor
server.
Also, please check if the value in primary_server_name column in
log_shipping_primaries does not match the <@.@.servername> of the primary
server.
If the issue persists, please use SQL profiler on the monitor server to see
if the update operation on log_shipping_primaries occurs or if there is any
related errors in error log.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Log Shipping Monitor Shows Problems when there aren't any
>thread-index: AcX5iaV+Rf+MfqKZTvqVdLuPrgGVlw==
>X-WBNR-Posting-Host: 193.0.2.180
>From: "=?Utf-8?B?QnJldHQgQ2Fycg==?=" <brettcarr@.news.postalias>
>References: <0E563B60-3095-4635-BC0A-3153BEB87CDB@.microsoft.com>
<VAQE#gX#FHA.1236@.TK2MSFTNGXA02.phx.gbl>[vbcol=seagreen]
>Subject: RE: Log Shipping Monitor Shows Problems when there aren't any
>Date: Mon, 5 Dec 2005 02:50:03 -0800
>Lines: 35
>Message-ID: <33C3B088-9CA3-4C3E-98B1-86E784833DDC@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:67231
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>"Peter Yang [MSFT]" wrote:
removed[vbcol=seagreen]
the[vbcol=seagreen]
database,[vbcol=seagreen]
password
>Ok. I've done the following:
>1. log_shipping_monitor_prob did not exist on the primary server so I
>created it.
>2. I reset the password for log_shipping_monitor_prob on both primary and
>secondary.
>3. On both primary and secondary servers I have set
>log_shipping_monitor_prob to have select,insert,update and delete
permissions
>on all tables starting with log_shipping in the msdb database.
>However I'm afraid the 'Last Backup' date and time listed in the monitor
is
>still the date and time I set it up originally. The Last copy and Last
>restore dates are still being updated correctly.
>Brett..
>
>
Monday, March 19, 2012
Log Shipping in multiple databases
I am trying to configure Log_Shipping in multiple databases on different
servers.
I tried to add it but it has to use the same destination copy folder, is
that true ?
i am using SQL2005.I haven't used the 2005 log shipping. Log shipping in general works under
the following model. There are two virtual jobs that run consecutively; the
first virtual job would be to create a log for a given time frame on the
source server and write it to the local disk and subsequently send a copy of
that log file to the destination server. The second virtual job is to read
the log file sent from the source server and when it reads the log file, it
can either delete it or more commonly, the file is saved for a given time to
another folder that consists of logs that have been read.
Example:
Write log to \\mysourceserver\backup\mylog_date_time.log
Copy mylog_date_time.log from \\mysourceserver\backup to
\\mysdestserver\backup
Read log \\mysourceserver\backup\mylog_date_time.log
Store log by moving \\mysourceserver\backup\mylog_date_time.log to
\\mysourceserver\storage\mylog_date_time.log
Finally there may be a purge time set to delete logs older than a set time.
--
Regards,
Jamie
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>|||Thanks Jamie for help,
I am already running Log Shipping from one server to another one, but i am
going to buy a new server with a highly configuration and want this new one
to be the main database and the old one be another log shipping database ( 1
main db and 2 log shipping db).
I tried it on a test server but any adding new server, has to change the
copy folder into the old server by force.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:786DB259-3386-4E4E-9A0A-FFE03BC5557B@.microsoft.com...
>I haven't used the 2005 log shipping. Log shipping in general works under
> the following model. There are two virtual jobs that run consecutively;
> the
> first virtual job would be to create a log for a given time frame on the
> source server and write it to the local disk and subsequently send a copy
> of
> that log file to the destination server. The second virtual job is to
> read
> the log file sent from the source server and when it reads the log file,
> it
> can either delete it or more commonly, the file is saved for a given time
> to
> another folder that consists of logs that have been read.
> Example:
> Write log to \\mysourceserver\backup\mylog_date_time.log
> Copy mylog_date_time.log from \\mysourceserver\backup to
> \\mysdestserver\backup
> Read log \\mysourceserver\backup\mylog_date_time.log
> Store log by moving \\mysourceserver\backup\mylog_date_time.log to
> \\mysourceserver\storage\mylog_date_time.log
> Finally there may be a purge time set to delete logs older than a set
> time.
> --
> Regards,
> Jamie
>
> "Mahmoud Amin" wrote:
>> I am trying to configure Log_Shipping in multiple databases on different
>> servers.
>> I tried to add it but it has to use the same destination copy folder, is
>> that true ?
>> i am using SQL2005.
>>|||Hi Amin,
You have 1 server which has primary db and you configure it
for log shipping to 2 different secondary servers....i guess this is what
you want....
but i think you are trying to configure log shipping from 1 st primary to 1
st secondary
and from the 1st primary to the same secondary server...so you'll have 2
copies of your log shipped db in your secoindary server......but that will
not server the purpose of log shipping as in case the seconday server is down
you won't have backup of primary server.......
but you can configure like that but you'll have only 1 shared folder which
conains both the logs from primary server
refer the below link for configuring log shipping just a sample
http://deepakinsql.blogspot.com/2007/06/how-to-configure-log-shipping-in-sql.html
Thanxx
Deepak
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>
servers.
I tried to add it but it has to use the same destination copy folder, is
that true ?
i am using SQL2005.I haven't used the 2005 log shipping. Log shipping in general works under
the following model. There are two virtual jobs that run consecutively; the
first virtual job would be to create a log for a given time frame on the
source server and write it to the local disk and subsequently send a copy of
that log file to the destination server. The second virtual job is to read
the log file sent from the source server and when it reads the log file, it
can either delete it or more commonly, the file is saved for a given time to
another folder that consists of logs that have been read.
Example:
Write log to \\mysourceserver\backup\mylog_date_time.log
Copy mylog_date_time.log from \\mysourceserver\backup to
\\mysdestserver\backup
Read log \\mysourceserver\backup\mylog_date_time.log
Store log by moving \\mysourceserver\backup\mylog_date_time.log to
\\mysourceserver\storage\mylog_date_time.log
Finally there may be a purge time set to delete logs older than a set time.
--
Regards,
Jamie
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>|||Thanks Jamie for help,
I am already running Log Shipping from one server to another one, but i am
going to buy a new server with a highly configuration and want this new one
to be the main database and the old one be another log shipping database ( 1
main db and 2 log shipping db).
I tried it on a test server but any adding new server, has to change the
copy folder into the old server by force.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:786DB259-3386-4E4E-9A0A-FFE03BC5557B@.microsoft.com...
>I haven't used the 2005 log shipping. Log shipping in general works under
> the following model. There are two virtual jobs that run consecutively;
> the
> first virtual job would be to create a log for a given time frame on the
> source server and write it to the local disk and subsequently send a copy
> of
> that log file to the destination server. The second virtual job is to
> read
> the log file sent from the source server and when it reads the log file,
> it
> can either delete it or more commonly, the file is saved for a given time
> to
> another folder that consists of logs that have been read.
> Example:
> Write log to \\mysourceserver\backup\mylog_date_time.log
> Copy mylog_date_time.log from \\mysourceserver\backup to
> \\mysdestserver\backup
> Read log \\mysourceserver\backup\mylog_date_time.log
> Store log by moving \\mysourceserver\backup\mylog_date_time.log to
> \\mysourceserver\storage\mylog_date_time.log
> Finally there may be a purge time set to delete logs older than a set
> time.
> --
> Regards,
> Jamie
>
> "Mahmoud Amin" wrote:
>> I am trying to configure Log_Shipping in multiple databases on different
>> servers.
>> I tried to add it but it has to use the same destination copy folder, is
>> that true ?
>> i am using SQL2005.
>>|||Hi Amin,
You have 1 server which has primary db and you configure it
for log shipping to 2 different secondary servers....i guess this is what
you want....
but i think you are trying to configure log shipping from 1 st primary to 1
st secondary
and from the 1st primary to the same secondary server...so you'll have 2
copies of your log shipped db in your secoindary server......but that will
not server the purpose of log shipping as in case the seconday server is down
you won't have backup of primary server.......
but you can configure like that but you'll have only 1 shared folder which
conains both the logs from primary server
refer the below link for configuring log shipping just a sample
http://deepakinsql.blogspot.com/2007/06/how-to-configure-log-shipping-in-sql.html
Thanxx
Deepak
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>
Log shipping in mssql 2000
Hi,
I am now trying to configure Log Shipping in my compeny but I have encountered some difficulties. The destination site and the source site are far from each other and the transaction logs are too big, this situation causes an huge overload on our private network (we use WAN which is complitly disconnected from the internet). Is there any way to compress the transacion logs with zip or rar and combine it in the log shipping mechanizem?
Is there another way for making this files smaller?
I would be greatful for any ideas in this matter.
Thanks in advance,
Zvi GilinskyThe only way I think is to increase time of Log shipping and meanwhile use compress software and ftp to transfer the file, then unzip it at desired location where LS can acces to restore.
BTW, any chance of hosting another standby server on the network and copy the files to this remote location as contingency.|||Dear Satya,
Correct me if I wrong.
As far as I know LS uses 3 primary jobs: one job on the source and two on the destinaion.
The job on the source creates the transaction logs, one job on the destination copy this files to the destination and the other job applies them on the destination DB.
If I will stop the job that copy the files and replace it by another job that compress these files, transfer them and then extract them won't it demage the LS mechanizem (wrong data in log shipping tables in msdb database)?
I also try to understand what the job that copy the files does but when I I see that it does the following line : EXECUTE master.dbo.xp_sqlmaint'-LSCopyPlainID "plan id"...
but when I query the msdb database : exec sp_help_maintenance_plan
this plan id isn't there. Where else can I see this plan id and it's details?
thanks,
zvi gilinsky|||Try to get dedicated link between primary & secondary servers to ensure no issues on network.
If you've such network problems in complying the log shipping to complete then better to think of contingency solution on a local network and use this remote server as seperate server.
Try to query against master database and see.
I am now trying to configure Log Shipping in my compeny but I have encountered some difficulties. The destination site and the source site are far from each other and the transaction logs are too big, this situation causes an huge overload on our private network (we use WAN which is complitly disconnected from the internet). Is there any way to compress the transacion logs with zip or rar and combine it in the log shipping mechanizem?
Is there another way for making this files smaller?
I would be greatful for any ideas in this matter.
Thanks in advance,
Zvi GilinskyThe only way I think is to increase time of Log shipping and meanwhile use compress software and ftp to transfer the file, then unzip it at desired location where LS can acces to restore.
BTW, any chance of hosting another standby server on the network and copy the files to this remote location as contingency.|||Dear Satya,
Correct me if I wrong.
As far as I know LS uses 3 primary jobs: one job on the source and two on the destinaion.
The job on the source creates the transaction logs, one job on the destination copy this files to the destination and the other job applies them on the destination DB.
If I will stop the job that copy the files and replace it by another job that compress these files, transfer them and then extract them won't it demage the LS mechanizem (wrong data in log shipping tables in msdb database)?
I also try to understand what the job that copy the files does but when I I see that it does the following line : EXECUTE master.dbo.xp_sqlmaint'-LSCopyPlainID "plan id"...
but when I query the msdb database : exec sp_help_maintenance_plan
this plan id isn't there. Where else can I see this plan id and it's details?
thanks,
zvi gilinsky|||Try to get dedicated link between primary & secondary servers to ensure no issues on network.
If you've such network problems in complying the log shipping to complete then better to think of contingency solution on a local network and use this remote server as seperate server.
Try to query against master database and see.
Monday, February 20, 2012
Log Shipping - log shipping transaction log destination directory
I am trying to set up log shipping between two servers. Secondary server is
going to be a stand-by and light reporting server. My question is 'can I
point log shipping transaction log destination directory to network share
folder?'. Database backup file is pretty big and I'd like to store them on
network. Is it possible?
Thanks in advance,
Jay
yes you can. make sure that you give the accounts running sqlserver and
sqlserveragent read/write permission.
Thanks
Yunwen
"Jay Lee" wrote:
> I am trying to set up log shipping between two servers. Secondary server is
> going to be a stand-by and light reporting server. My question is 'can I
> point log shipping transaction log destination directory to network share
> folder?'. Database backup file is pretty big and I'd like to store them on
> network. Is it possible?
> Thanks in advance,
> Jay
going to be a stand-by and light reporting server. My question is 'can I
point log shipping transaction log destination directory to network share
folder?'. Database backup file is pretty big and I'd like to store them on
network. Is it possible?
Thanks in advance,
Jay
yes you can. make sure that you give the accounts running sqlserver and
sqlserveragent read/write permission.
Thanks
Yunwen
"Jay Lee" wrote:
> I am trying to set up log shipping between two servers. Secondary server is
> going to be a stand-by and light reporting server. My question is 'can I
> point log shipping transaction log destination directory to network share
> folder?'. Database backup file is pretty big and I'd like to store them on
> network. Is it possible?
> Thanks in advance,
> Jay
Subscribe to:
Posts (Atom)