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 wizard. Show all posts
Showing posts with label wizard. 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
Wednesday, March 21, 2012
Log shipping not work, but jobs say successful
I have a pretty standard log shipping arrangement created with the Log
Shipping wizard against an existing database on the standby server. All the
jobs were created successfully and run on the correct schedule. However,
the copy job on the standby server doesn't work. It shows that it ran
successfully, but the files just aren't copied to the standby server's
directory, and so are not restored. After manually copying the transaction
log files to the standby server, the restore job will work. However, the
next log in sequence will not copy over.
The maintenance plan history shows no errors.
Both servers are running Windows 2000 servers and SQL Server 2000 Enterprise
SP3a. The link is a 45 Mbit leased line.
What could be the problem?
Thanks,
RS
RS,
usually this is a problem with the paths - the wizard is not very intuitive
and it's quite easy to set them incorrectly. On the screen that says
'Specify the Transaction Log Share', you must identify the file share on the
primary server and when setting up the destination, the name is a local
pathname, not a file share. If this is incorrect, there will be no errors
and the monitor will show continually the first setup file as being
transferred. So, initially check that you have a share on the primary server
and the logs are getting there.
HTH,
Paul Ibison
sql
Shipping wizard against an existing database on the standby server. All the
jobs were created successfully and run on the correct schedule. However,
the copy job on the standby server doesn't work. It shows that it ran
successfully, but the files just aren't copied to the standby server's
directory, and so are not restored. After manually copying the transaction
log files to the standby server, the restore job will work. However, the
next log in sequence will not copy over.
The maintenance plan history shows no errors.
Both servers are running Windows 2000 servers and SQL Server 2000 Enterprise
SP3a. The link is a 45 Mbit leased line.
What could be the problem?
Thanks,
RS
RS,
usually this is a problem with the paths - the wizard is not very intuitive
and it's quite easy to set them incorrectly. On the screen that says
'Specify the Transaction Log Share', you must identify the file share on the
primary server and when setting up the destination, the name is a local
pathname, not a file share. If this is incorrect, there will be no errors
and the monitor will show continually the first setup file as being
transferred. So, initially check that you have a share on the primary server
and the logs are getting there.
HTH,
Paul Ibison
sql
Monday, March 19, 2012
Log Shipping Monitor
Hello,
I have configured a SQL Server for Log Shipping using the Database Maintenan
ce Planner Wizard. Now a Log Shipping Monitor object appears below the Manag
ement folder. How do I reverse this process, and make the Log Shipping Monit
or disappear? In other word
s I want to revert back to the state SQL Server was in before I ran the Data
base Maintenance Planner.
Thanks,
Jerome SmithHello all,
I'll answer my own question for everybody's benefit. Eliminating the Log Shi
pping Monitor is equivalent to eliminating all Log Shipping pairs from the L
og Shipping system database. This is done with the stored procedure:
sp_delete_log_shipping_primary
located in the msdb system database.
Following is the help article.
Cheers,
Jerome
sp_delete_log_shipping_primary
Deletes the primary server from the log_shipping_primaries table.
Syntax
sp_delete_log_shipping_primary
[ @.primary_server_name = ] 'primary_server_name' ,
[ @.primary_database_name = ] 'primary_database_name' ,
{ [ @.delete_secondaries = ] delete_secondaries }
Arguments
[@.primary_server_name =] 'primary_server_name'
Is the name of the primary server. primary_server_name is sysname.
[@.primary_database_name =] 'primary_database_name'
Is the name of the secondary server. primary_database_name is sysname.
[@.delete_secondaries =] delete_secondaries
Specifies that the delete action is also applied to log_shipping_secondaries
table. delete_secondaries is bit, with a default of zero (0).
Return Code Values
0 (success) or 1 (failure)
Remarks
This stored procedure only removes the primary and secondary server from the
monitor. Log shipping still has to be removed from the primary and secondar
y servers.
sp_delete_log_shipping_primary deletes a log shipping primary table. If ther
e are corresponding rows in the log_shipping_databases table, delete_seconda
ries must be set to one (1) or the stored procedure will fail.
Permissions
Only members of the sysadmin fixed server role can execute sp_delete_log_shi
pping_primaries.
Examples
This example deletes the source database "pubs" from the server "source". Th
ere are no corresponding rows in log_shipping_secondaries table.
EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source', @.pri
mary_database_name = N'pubs'
?1988-2000 Microsoft Corporation. All Rights Reserved.|||Actually, when nothing has gone wrong, the easiest way is in Enterprise
Manager:
Management->Database Maintenance Plans->Right-Click->Properties->Log
Shipping->Remove Log Shipping.
Then delete Plan.
Jerome
"Jerome Smith" <jerosmith@.hotmail.com> escribi en el mensaje
news:3B6447C3-7819-4F31-983B-7BDD84D2311F@.microsoft.com...
> Hello all,
> I'll answer my own question for everybody's benefit. Eliminating the Log
Shipping Monitor is equivalent to eliminating all Log Shipping pairs from
the Log Shipping system database. This is done with the stored procedure:
> sp_delete_log_shipping_primary
> located in the msdb system database.
> Following is the help article.
> Cheers,
> Jerome
> sp_delete_log_shipping_primary
> Deletes the primary server from the log_shipping_primaries table.
> Syntax
> sp_delete_log_shipping_primary
> [ @.primary_server_name = ] 'primary_server_name' ,
> [ @.primary_database_name = ] 'primary_database_name' ,
> { [ @.delete_secondaries = ] delete_secondaries }
> Arguments
> [@.primary_server_name =] 'primary_server_name'
> Is the name of the primary server. primary_server_name is sysname.
> [@.primary_database_name =] 'primary_database_name'
> Is the name of the secondary server. primary_database_name is sysname.
> [@.delete_secondaries =] delete_secondaries
> Specifies that the delete action is also applied to
log_shipping_secondaries table. delete_secondaries is bit, with a default of
zero (0).
> Return Code Values
> 0 (success) or 1 (failure)
> Remarks
> This stored procedure only removes the primary and secondary server from
the monitor. Log shipping still has to be removed from the primary and
secondary servers.
> sp_delete_log_shipping_primary deletes a log shipping primary table. If
there are corresponding rows in the log_shipping_databases table,
delete_secondaries must be set to one (1) or the stored procedure will fail.
> Permissions
> Only members of the sysadmin fixed server role can execute
sp_delete_log_shipping_primaries.
> Examples
> This example deletes the source database "pubs" from the server "source".
There are no corresponding rows in log_shipping_secondaries table.
> EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source',
@.primary_database_name = N'pubs'
> 1988-2000 Microsoft Corporation. All Rights Reserved.
>
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.629 / Virus Database: 403 - Release Date: 17-03-2004
I have configured a SQL Server for Log Shipping using the Database Maintenan
ce Planner Wizard. Now a Log Shipping Monitor object appears below the Manag
ement folder. How do I reverse this process, and make the Log Shipping Monit
or disappear? In other word
s I want to revert back to the state SQL Server was in before I ran the Data
base Maintenance Planner.
Thanks,
Jerome SmithHello all,
I'll answer my own question for everybody's benefit. Eliminating the Log Shi
pping Monitor is equivalent to eliminating all Log Shipping pairs from the L
og Shipping system database. This is done with the stored procedure:
sp_delete_log_shipping_primary
located in the msdb system database.
Following is the help article.
Cheers,
Jerome
sp_delete_log_shipping_primary
Deletes the primary server from the log_shipping_primaries table.
Syntax
sp_delete_log_shipping_primary
[ @.primary_server_name = ] 'primary_server_name' ,
[ @.primary_database_name = ] 'primary_database_name' ,
{ [ @.delete_secondaries = ] delete_secondaries }
Arguments
[@.primary_server_name =] 'primary_server_name'
Is the name of the primary server. primary_server_name is sysname.
[@.primary_database_name =] 'primary_database_name'
Is the name of the secondary server. primary_database_name is sysname.
[@.delete_secondaries =] delete_secondaries
Specifies that the delete action is also applied to log_shipping_secondaries
table. delete_secondaries is bit, with a default of zero (0).
Return Code Values
0 (success) or 1 (failure)
Remarks
This stored procedure only removes the primary and secondary server from the
monitor. Log shipping still has to be removed from the primary and secondar
y servers.
sp_delete_log_shipping_primary deletes a log shipping primary table. If ther
e are corresponding rows in the log_shipping_databases table, delete_seconda
ries must be set to one (1) or the stored procedure will fail.
Permissions
Only members of the sysadmin fixed server role can execute sp_delete_log_shi
pping_primaries.
Examples
This example deletes the source database "pubs" from the server "source". Th
ere are no corresponding rows in log_shipping_secondaries table.
EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source', @.pri
mary_database_name = N'pubs'
?1988-2000 Microsoft Corporation. All Rights Reserved.|||Actually, when nothing has gone wrong, the easiest way is in Enterprise
Manager:
Management->Database Maintenance Plans->Right-Click->Properties->Log
Shipping->Remove Log Shipping.
Then delete Plan.
Jerome
"Jerome Smith" <jerosmith@.hotmail.com> escribi en el mensaje
news:3B6447C3-7819-4F31-983B-7BDD84D2311F@.microsoft.com...
> Hello all,
> I'll answer my own question for everybody's benefit. Eliminating the Log
Shipping Monitor is equivalent to eliminating all Log Shipping pairs from
the Log Shipping system database. This is done with the stored procedure:
> sp_delete_log_shipping_primary
> located in the msdb system database.
> Following is the help article.
> Cheers,
> Jerome
> sp_delete_log_shipping_primary
> Deletes the primary server from the log_shipping_primaries table.
> Syntax
> sp_delete_log_shipping_primary
> [ @.primary_server_name = ] 'primary_server_name' ,
> [ @.primary_database_name = ] 'primary_database_name' ,
> { [ @.delete_secondaries = ] delete_secondaries }
> Arguments
> [@.primary_server_name =] 'primary_server_name'
> Is the name of the primary server. primary_server_name is sysname.
> [@.primary_database_name =] 'primary_database_name'
> Is the name of the secondary server. primary_database_name is sysname.
> [@.delete_secondaries =] delete_secondaries
> Specifies that the delete action is also applied to
log_shipping_secondaries table. delete_secondaries is bit, with a default of
zero (0).
> Return Code Values
> 0 (success) or 1 (failure)
> Remarks
> This stored procedure only removes the primary and secondary server from
the monitor. Log shipping still has to be removed from the primary and
secondary servers.
> sp_delete_log_shipping_primary deletes a log shipping primary table. If
there are corresponding rows in the log_shipping_databases table,
delete_secondaries must be set to one (1) or the stored procedure will fail.
> Permissions
> Only members of the sysadmin fixed server role can execute
sp_delete_log_shipping_primaries.
> Examples
> This example deletes the source database "pubs" from the server "source".
There are no corresponding rows in log_shipping_secondaries table.
> EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source',
@.primary_database_name = N'pubs'
> 1988-2000 Microsoft Corporation. All Rights Reserved.
>
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.629 / Virus Database: 403 - Release Date: 17-03-2004
Log Shipping Issue
Hello All,
I am trying to set up Log Shipping, but, in the second screen of Database Maintenence wizard, when I select any database, the log shipping option gets grayed out. I am not able to select both. But in the step by step guide, it mentions to select both. I could have provided a screenshot of what's happening, but I could not locate a place for the same. Please let me know about this at the earliest. I'll be very grateful. Thanks a lot.
Mannu.
What is the recovery model for the databases you are want to include in the log shipping?
What is the edition of SQL you are using?
|||That is corrrect. It was in Simple mode. Changing it to Full Mode, gave me what I want.
Thanks a lot.
Monday, March 12, 2012
Log shipping from SQL 2000 to SQL 2005
I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQL
2K5) with norecovery.
Now i want to use the maintenance plan wizard in 2000 to set up log shipping
but since i cannot register the destination i.e the SQL 2K5 box in 2000
Enterprise Manager, I cannot seem to complete it.
How do you all set it up ? Please help.Hi Hassan
Have you looked at manually setting up log shipping as in the topic "How to
set up a Log Shipping Monitor (Transact-SQL)" in Books online?
John
"Hassan" wrote:
> I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQL
> 2K5) with norecovery.
> Now i want to use the maintenance plan wizard in 2000 to set up log shipping
> but since i cannot register the destination i.e the SQL 2K5 box in 2000
> Enterprise Manager, I cannot seem to complete it.
> How do you all set it up ? Please help.
>
>|||I know how to setup log shipping, but what i dont know is how to setup log
shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans wont let
me.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D95FCA9-03A5-4082-83BD-1DD974E09D69@.microsoft.com...
> Hi Hassan
> Have you looked at manually setting up log shipping as in the topic "How
> to
> set up a Log Shipping Monitor (Transact-SQL)" in Books online?
> John
> "Hassan" wrote:
>> I have a DB on Server A ( SQL 2K) and just restored the DB on Server B(
>> SQL
>> 2K5) with norecovery.
>> Now i want to use the maintenance plan wizard in 2000 to set up log
>> shipping
>> but since i cannot register the destination i.e the SQL 2K5 box in 2000
>> Enterprise Manager, I cannot seem to complete it.
>> How do you all set it up ? Please help.
>>|||Hassan wrote:
> I know how to setup log shipping, but what i dont know is how to setup log
> shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans wont let
> me.
>
So don't use the maintenance plans!! Log shipping is nothing more than
restoring transaction log backups from one database to another, with a
control wrapper to keep track of which logs have not been restored.
Very easy to roll your own process, and you can make it work the way YOU
want it to, not the way MS wants it to.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I assume that the SSMS / EM GUIs don't allow this, but it's really easy to
script a couple of SQL Agent jobs to perform the LogShipping - on the prod
side, a Maintenance Plan job to backup the log to a shared directory every n
minutes, then a second on the Standby server which polls that directory &
restores the log backups.
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
"Hassan" <Hassan@.hotmail.com> wrote in message
news:uTHS4lM%23GHA.3480@.TK2MSFTNGP04.phx.gbl...
>I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQL
>2K5) with norecovery.
> Now i want to use the maintenance plan wizard in 2000 to set up log
> shipping but since i cannot register the destination i.e the SQL 2K5 box
> in 2000 Enterprise Manager, I cannot seem to complete it.
> How do you all set it up ? Please help.
>|||Tracy,
So right now we have log shipping set up between a source SQL 2K server and
a standby SQL 2K server using the maintenance plan. What I want to
accomplish is to add the SQL 2K5 standby server to it which means I need to
somehow copy the log files and restore the log files on the SQL 2K5 server
through a script.
I dont know how to write that script. Can you help ?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4540E47C.7060908@.realsqlguy.com...
> Hassan wrote:
>> I know how to setup log shipping, but what i dont know is how to setup
>> log shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans
>> wont let me.
> So don't use the maintenance plans!! Log shipping is nothing more than
> restoring transaction log backups from one database to another, with a
> control wrapper to keep track of which logs have not been restored. Very
> easy to roll your own process, and you can make it work the way YOU want
> it to, not the way MS wants it to.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Scripting is not my forte Greg. Do you know how you can help me out here ?
"Greg Linwood" <g_linwood@.hotmail.com> wrote in message
news:ONGl$WV%23GHA.4464@.TK2MSFTNGP02.phx.gbl...
>I assume that the SSMS / EM GUIs don't allow this, but it's really easy to
>script a couple of SQL Agent jobs to perform the LogShipping - on the prod
>side, a Maintenance Plan job to backup the log to a shared directory every
>n minutes, then a second on the Standby server which polls that directory &
>restores the log backups.
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uTHS4lM%23GHA.3480@.TK2MSFTNGP04.phx.gbl...
>>I have a DB on Server A ( SQL 2K) and just restored the DB on Server B(
>>SQL 2K5) with norecovery.
>> Now i want to use the maintenance plan wizard in 2000 to set up log
>> shipping but since i cannot register the destination i.e the SQL 2K5 box
>> in 2000 Enterprise Manager, I cannot seem to complete it.
>> How do you all set it up ? Please help.
>|||Hi Hassan,
Those are the Simple Backup and Restore commands you have to use in the
script and schedule in Jobs.
You can take BOL Reference and start writing it....
Thanks
Ajay Rengunthwar
"Hassan" <Hassan@.hotmail.com> wrote in message
news:OkQiuLW%23GHA.1752@.TK2MSFTNGP02.phx.gbl...
> Tracy,
> So right now we have log shipping set up between a source SQL 2K server
> and a standby SQL 2K server using the maintenance plan. What I want to
> accomplish is to add the SQL 2K5 standby server to it which means I need
> to somehow copy the log files and restore the log files on the SQL 2K5
> server through a script.
> I dont know how to write that script. Can you help ?
> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
> news:4540E47C.7060908@.realsqlguy.com...
>> Hassan wrote:
>> I know how to setup log shipping, but what i dont know is how to setup
>> log shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans
>> wont let me.
>>
>> So don't use the maintenance plans!! Log shipping is nothing more than
>> restoring transaction log backups from one database to another, with a
>> control wrapper to keep track of which logs have not been restored. Very
>> easy to roll your own process, and you can make it work the way YOU want
>> it to, not the way MS wants it to.
>>
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com
>
2K5) with norecovery.
Now i want to use the maintenance plan wizard in 2000 to set up log shipping
but since i cannot register the destination i.e the SQL 2K5 box in 2000
Enterprise Manager, I cannot seem to complete it.
How do you all set it up ? Please help.Hi Hassan
Have you looked at manually setting up log shipping as in the topic "How to
set up a Log Shipping Monitor (Transact-SQL)" in Books online?
John
"Hassan" wrote:
> I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQL
> 2K5) with norecovery.
> Now i want to use the maintenance plan wizard in 2000 to set up log shipping
> but since i cannot register the destination i.e the SQL 2K5 box in 2000
> Enterprise Manager, I cannot seem to complete it.
> How do you all set it up ? Please help.
>
>|||I know how to setup log shipping, but what i dont know is how to setup log
shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans wont let
me.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D95FCA9-03A5-4082-83BD-1DD974E09D69@.microsoft.com...
> Hi Hassan
> Have you looked at manually setting up log shipping as in the topic "How
> to
> set up a Log Shipping Monitor (Transact-SQL)" in Books online?
> John
> "Hassan" wrote:
>> I have a DB on Server A ( SQL 2K) and just restored the DB on Server B(
>> SQL
>> 2K5) with norecovery.
>> Now i want to use the maintenance plan wizard in 2000 to set up log
>> shipping
>> but since i cannot register the destination i.e the SQL 2K5 box in 2000
>> Enterprise Manager, I cannot seem to complete it.
>> How do you all set it up ? Please help.
>>|||Hassan wrote:
> I know how to setup log shipping, but what i dont know is how to setup log
> shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans wont let
> me.
>
So don't use the maintenance plans!! Log shipping is nothing more than
restoring transaction log backups from one database to another, with a
control wrapper to keep track of which logs have not been restored.
Very easy to roll your own process, and you can make it work the way YOU
want it to, not the way MS wants it to.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I assume that the SSMS / EM GUIs don't allow this, but it's really easy to
script a couple of SQL Agent jobs to perform the LogShipping - on the prod
side, a Maintenance Plan job to backup the log to a shared directory every n
minutes, then a second on the Standby server which polls that directory &
restores the log backups.
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
"Hassan" <Hassan@.hotmail.com> wrote in message
news:uTHS4lM%23GHA.3480@.TK2MSFTNGP04.phx.gbl...
>I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQL
>2K5) with norecovery.
> Now i want to use the maintenance plan wizard in 2000 to set up log
> shipping but since i cannot register the destination i.e the SQL 2K5 box
> in 2000 Enterprise Manager, I cannot seem to complete it.
> How do you all set it up ? Please help.
>|||Tracy,
So right now we have log shipping set up between a source SQL 2K server and
a standby SQL 2K server using the maintenance plan. What I want to
accomplish is to add the SQL 2K5 standby server to it which means I need to
somehow copy the log files and restore the log files on the SQL 2K5 server
through a script.
I dont know how to write that script. Can you help ?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4540E47C.7060908@.realsqlguy.com...
> Hassan wrote:
>> I know how to setup log shipping, but what i dont know is how to setup
>> log shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans
>> wont let me.
> So don't use the maintenance plans!! Log shipping is nothing more than
> restoring transaction log backups from one database to another, with a
> control wrapper to keep track of which logs have not been restored. Very
> easy to roll your own process, and you can make it work the way YOU want
> it to, not the way MS wants it to.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Scripting is not my forte Greg. Do you know how you can help me out here ?
"Greg Linwood" <g_linwood@.hotmail.com> wrote in message
news:ONGl$WV%23GHA.4464@.TK2MSFTNGP02.phx.gbl...
>I assume that the SSMS / EM GUIs don't allow this, but it's really easy to
>script a couple of SQL Agent jobs to perform the LogShipping - on the prod
>side, a Maintenance Plan job to backup the log to a shared directory every
>n minutes, then a second on the Standby server which polls that directory &
>restores the log backups.
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uTHS4lM%23GHA.3480@.TK2MSFTNGP04.phx.gbl...
>>I have a DB on Server A ( SQL 2K) and just restored the DB on Server B(
>>SQL 2K5) with norecovery.
>> Now i want to use the maintenance plan wizard in 2000 to set up log
>> shipping but since i cannot register the destination i.e the SQL 2K5 box
>> in 2000 Enterprise Manager, I cannot seem to complete it.
>> How do you all set it up ? Please help.
>|||Hi Hassan,
Those are the Simple Backup and Restore commands you have to use in the
script and schedule in Jobs.
You can take BOL Reference and start writing it....
Thanks
Ajay Rengunthwar
"Hassan" <Hassan@.hotmail.com> wrote in message
news:OkQiuLW%23GHA.1752@.TK2MSFTNGP02.phx.gbl...
> Tracy,
> So right now we have log shipping set up between a source SQL 2K server
> and a standby SQL 2K server using the maintenance plan. What I want to
> accomplish is to add the SQL 2K5 standby server to it which means I need
> to somehow copy the log files and restore the log files on the SQL 2K5
> server through a script.
> I dont know how to write that script. Can you help ?
> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
> news:4540E47C.7060908@.realsqlguy.com...
>> Hassan wrote:
>> I know how to setup log shipping, but what i dont know is how to setup
>> log shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans
>> wont let me.
>>
>> So don't use the maintenance plans!! Log shipping is nothing more than
>> restoring transaction log backups from one database to another, with a
>> control wrapper to keep track of which logs have not been restored. Very
>> easy to roll your own process, and you can make it work the way YOU want
>> it to, not the way MS wants it to.
>>
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com
>
Log shipping from SQL 2000 to SQL 2005
I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQL
2K5) with norecovery.
Now i want to use the maintenance plan wizard in 2000 to set up log shipping
but since i cannot register the destination i.e the SQL 2K5 box in 2000
Enterprise Manager, I cannot seem to complete it.
How do you all set it up ? Please help.Hi Hassan
Have you looked at manually setting up log shipping as in the topic "How to
set up a Log Shipping Monitor (Transact-SQL)" in Books online?
John
"Hassan" wrote:
> I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQ
L
> 2K5) with norecovery.
> Now i want to use the maintenance plan wizard in 2000 to set up log shippi
ng
> but since i cannot register the destination i.e the SQL 2K5 box in 2000
> Enterprise Manager, I cannot seem to complete it.
> How do you all set it up ? Please help.
>
>|||I know how to setup log shipping, but what i dont know is how to setup log
shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans wont let
me.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D95FCA9-03A5-4082-83BD-1DD974E09D69@.microsoft.com...[vbcol=seagreen]
> Hi Hassan
> Have you looked at manually setting up log shipping as in the topic "How
> to
> set up a Log Shipping Monitor (Transact-SQL)" in Books online?
> John
> "Hassan" wrote:
>|||Hassan wrote:
> I know how to setup log shipping, but what i dont know is how to setup log
> shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans wont let
> me.
>
So don't use the maintenance plans!! Log shipping is nothing more than
restoring transaction log backups from one database to another, with a
control wrapper to keep track of which logs have not been restored.
Very easy to roll your own process, and you can make it work the way YOU
want it to, not the way MS wants it to.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I assume that the SSMS / EM GUIs don't allow this, but it's really easy to
script a couple of SQL Agent jobs to perform the LogShipping - on the prod
side, a Maintenance Plan job to backup the log to a shared directory every n
minutes, then a second on the Standby server which polls that directory &
restores the log backups.
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
"Hassan" <Hassan@.hotmail.com> wrote in message
news:uTHS4lM%23GHA.3480@.TK2MSFTNGP04.phx.gbl...
>I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQL
>2K5) with norecovery.
> Now i want to use the maintenance plan wizard in 2000 to set up log
> shipping but since i cannot register the destination i.e the SQL 2K5 box
> in 2000 Enterprise Manager, I cannot seem to complete it.
> How do you all set it up ? Please help.
>|||Tracy,
So right now we have log shipping set up between a source SQL 2K server and
a standby SQL 2K server using the maintenance plan. What I want to
accomplish is to add the SQL 2K5 standby server to it which means I need to
somehow copy the log files and restore the log files on the SQL 2K5 server
through a script.
I dont know how to write that script. Can you help ?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4540E47C.7060908@.realsqlguy.com...
> Hassan wrote:
> So don't use the maintenance plans!! Log shipping is nothing more than
> restoring transaction log backups from one database to another, with a
> control wrapper to keep track of which logs have not been restored. Very
> easy to roll your own process, and you can make it work the way YOU want
> it to, not the way MS wants it to.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Scripting is not my forte Greg. Do you know how you can help me out here ?
"Greg Linwood" <g_linwood@.hotmail.com> wrote in message
news:ONGl$WV%23GHA.4464@.TK2MSFTNGP02.phx.gbl...
>I assume that the SSMS / EM GUIs don't allow this, but it's really easy to
>script a couple of SQL Agent jobs to perform the LogShipping - on the prod
>side, a Maintenance Plan job to backup the log to a shared directory every
>n minutes, then a second on the Standby server which polls that directory &
>restores the log backups.
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uTHS4lM%23GHA.3480@.TK2MSFTNGP04.phx.gbl...
>|||Hi Hassan,
Those are the Simple Backup and Restore commands you have to use in the
script and schedule in Jobs.
You can take BOL Reference and start writing it....
Thanks
Ajay Rengunthwar
"Hassan" <Hassan@.hotmail.com> wrote in message
news:OkQiuLW%23GHA.1752@.TK2MSFTNGP02.phx.gbl...
> Tracy,
> So right now we have log shipping set up between a source SQL 2K server
> and a standby SQL 2K server using the maintenance plan. What I want to
> accomplish is to add the SQL 2K5 standby server to it which means I need
> to somehow copy the log files and restore the log files on the SQL 2K5
> server through a script.
> I dont know how to write that script. Can you help ?
> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
> news:4540E47C.7060908@.realsqlguy.com...
>
2K5) with norecovery.
Now i want to use the maintenance plan wizard in 2000 to set up log shipping
but since i cannot register the destination i.e the SQL 2K5 box in 2000
Enterprise Manager, I cannot seem to complete it.
How do you all set it up ? Please help.Hi Hassan
Have you looked at manually setting up log shipping as in the topic "How to
set up a Log Shipping Monitor (Transact-SQL)" in Books online?
John
"Hassan" wrote:
> I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQ
L
> 2K5) with norecovery.
> Now i want to use the maintenance plan wizard in 2000 to set up log shippi
ng
> but since i cannot register the destination i.e the SQL 2K5 box in 2000
> Enterprise Manager, I cannot seem to complete it.
> How do you all set it up ? Please help.
>
>|||I know how to setup log shipping, but what i dont know is how to setup log
shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans wont let
me.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D95FCA9-03A5-4082-83BD-1DD974E09D69@.microsoft.com...[vbcol=seagreen]
> Hi Hassan
> Have you looked at manually setting up log shipping as in the topic "How
> to
> set up a Log Shipping Monitor (Transact-SQL)" in Books online?
> John
> "Hassan" wrote:
>|||Hassan wrote:
> I know how to setup log shipping, but what i dont know is how to setup log
> shipping from SQL 2000 EE to SQL 2005 EE as the maintenance plans wont let
> me.
>
So don't use the maintenance plans!! Log shipping is nothing more than
restoring transaction log backups from one database to another, with a
control wrapper to keep track of which logs have not been restored.
Very easy to roll your own process, and you can make it work the way YOU
want it to, not the way MS wants it to.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I assume that the SSMS / EM GUIs don't allow this, but it's really easy to
script a couple of SQL Agent jobs to perform the LogShipping - on the prod
side, a Maintenance Plan job to backup the log to a shared directory every n
minutes, then a second on the Standby server which polls that directory &
restores the log backups.
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
"Hassan" <Hassan@.hotmail.com> wrote in message
news:uTHS4lM%23GHA.3480@.TK2MSFTNGP04.phx.gbl...
>I have a DB on Server A ( SQL 2K) and just restored the DB on Server B( SQL
>2K5) with norecovery.
> Now i want to use the maintenance plan wizard in 2000 to set up log
> shipping but since i cannot register the destination i.e the SQL 2K5 box
> in 2000 Enterprise Manager, I cannot seem to complete it.
> How do you all set it up ? Please help.
>|||Tracy,
So right now we have log shipping set up between a source SQL 2K server and
a standby SQL 2K server using the maintenance plan. What I want to
accomplish is to add the SQL 2K5 standby server to it which means I need to
somehow copy the log files and restore the log files on the SQL 2K5 server
through a script.
I dont know how to write that script. Can you help ?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4540E47C.7060908@.realsqlguy.com...
> Hassan wrote:
> So don't use the maintenance plans!! Log shipping is nothing more than
> restoring transaction log backups from one database to another, with a
> control wrapper to keep track of which logs have not been restored. Very
> easy to roll your own process, and you can make it work the way YOU want
> it to, not the way MS wants it to.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Scripting is not my forte Greg. Do you know how you can help me out here ?
"Greg Linwood" <g_linwood@.hotmail.com> wrote in message
news:ONGl$WV%23GHA.4464@.TK2MSFTNGP02.phx.gbl...
>I assume that the SSMS / EM GUIs don't allow this, but it's really easy to
>script a couple of SQL Agent jobs to perform the LogShipping - on the prod
>side, a Maintenance Plan job to backup the log to a shared directory every
>n minutes, then a second on the Standby server which polls that directory &
>restores the log backups.
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uTHS4lM%23GHA.3480@.TK2MSFTNGP04.phx.gbl...
>|||Hi Hassan,
Those are the Simple Backup and Restore commands you have to use in the
script and schedule in Jobs.
You can take BOL Reference and start writing it....
Thanks
Ajay Rengunthwar
"Hassan" <Hassan@.hotmail.com> wrote in message
news:OkQiuLW%23GHA.1752@.TK2MSFTNGP02.phx.gbl...
> Tracy,
> So right now we have log shipping set up between a source SQL 2K server
> and a standby SQL 2K server using the maintenance plan. What I want to
> accomplish is to add the SQL 2K5 standby server to it which means I need
> to somehow copy the log files and restore the log files on the SQL 2K5
> server through a script.
> I dont know how to write that script. Can you help ?
> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
> news:4540E47C.7060908@.realsqlguy.com...
>
Friday, March 9, 2012
Log Shipping Error - Failing to save Secondary Server Configurations Err # 14262
I set up Log Shipping with just 2 servers primary and secondary. When I run from the Wizard for the very first time keeps failing at the stage of saving Secondary Server Configuration info. When i instead run the generated script this problem disappears but then restoring of transactions fails - the process can backup transactions from the Primary server , copy them accross to the secondary and fails on the restore. Any ideas why.
Hi Jonathan
When you use the SSMS UI to configure log shipping and it fails, can you give me the error message that should be available in the error dialog?
When you use the generated script to configure log shipping, but the restore fails, have you had a look at the log_shipping_monitor_error_detail tables on both the primary and seconary servers? These tables are in msdb (see BOL for more information) and should provide detailed error information.
Thanks, Mark
|||Also its good to check whether both the instances have the same MDAC level & service pack, as this will happen if there is such mismatch.
http://www.sql-server-performance.com/sql_server_log_shipping.asp fyi.
|||Hi Satya
Greetings to you. I managed to resolve the problem of failing to save Secondary Server configuration. I reinstalled SQL Server and the problem disappeared. My next challenge is I want to automate my backup strategy where I have Log Shipping between 6am to 8pm backing up transactions at 20 minute interval. Then Log Shipping between 8pm to 10pm at 1 hour interval then Full database backup daily , once a week , once a month etc. in which case I need to disable Log Shipping .
|||Hi there Mark!
Thanks for your interest in my problem. I managed to go over the problem. I reinstalled SQL Server and the problem disappeared. However I have a new challenge. I need to automatically setup Log Shipping between 6am to 8pm backing up transactions at 20 minute intervals then Log shipping between 8pm to 10pm at 1hr intervals then automatically disable Log shipping and do Full Database backup at night like midnight per day ,week etc
|||Hi Jonathan
Glad the problem disappeared.
Do you really need to have two different interval periods for the backups? It is obviously simpler if you only have the one configuration. If you do need the two schedules, then you should be able add a schedule to the backup job that is created. Using the log shipping UI, go to the "Transaction Log Backup Settings" dialog then the "Edit Job" button to pull up the job properties.
Regarding the full backup you do not need to disable log shipping for you to be able to do a full backup. See the topic in BOL titled "Creating Transaction Log Backups" for a description of the log sequence and how transaction log backups are independent of the full backup.
Subscribe to:
Posts (Atom)