Log Shipping with two production servers

I have two SQL Server databases, each with their own server. Is it suitable
to implement log shipping from each server to the other i.e. rather than
having the standard set up with a production server and a standby server, I
will set it up with two production servers 'swapping' logs...?
Hi,
Instead of "swapping logs" you might want to implement merge
replication, however you don't give a case for why you want to
implement log shipping. Is it for a hot standby (you could setup
clustering) or do you plan to utilise one server for reporting
purposes?
Also the official line from MS is that to implement log shipping both
SQL Server Editions should be Enterprise Version, however if you can
get hold of the SQL Server 2000 Resource Kit there is a Simple Log
Shipper Tool (basically two stored procs) on there. However with the
Enterprise methond it does monitor the log shipping for you. The only
disclaimer is that I could get SLS to work in a dev environment but not
in our production setup, so we went with snapshot replication.
Good Luck
Scott
|||Hi
You can't use log shipping for Scale Out as the destination DB can not be
used for write activities.
If you need to impliment something like scale out, look at replication, but
replication could use more resources than what you might gain by off loading
a server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike" wrote:

> I have two SQL Server databases, each with their own server. Is it suitable
> to implement log shipping from each server to the other i.e. rather than
> having the standard set up with a production server and a standby server, I
> will set it up with two production servers 'swapping' logs...?
>
>

Log Shipping with two production servers

I have two SQL Server databases, each with their own server. Is it suitable
to implement log shipping from each server to the other i.e. rather than
having the standard set up with a production server and a standby server, I
will set it up with two production servers 'swapping' logs...?Hi,
Instead of "swapping logs" you might want to implement merge
replication, however you don't give a case for why you want to
implement log shipping. Is it for a hot standby (you could setup
clustering) or do you plan to utilise one server for reporting
purposes?
Also the official line from MS is that to implement log shipping both
SQL Server Editions should be Enterprise Version, however if you can
get hold of the SQL Server 2000 Resource Kit there is a Simple Log
Shipper Tool (basically two stored procs) on there. However with the
Enterprise methond it does monitor the log shipping for you. The only
disclaimer is that I could get SLS to work in a dev environment but not
in our production setup, so we went with snapshot replication.
Good Luck
Scott|||Hi
You can't use log shipping for Scale Out as the destination DB can not be
used for write activities.
If you need to impliment something like scale out, look at replication, but
replication could use more resources than what you might gain by off loading
a server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike" wrote:

> I have two SQL Server databases, each with their own server. Is it suitabl
e
> to implement log shipping from each server to the other i.e. rather than
> having the standard set up with a production server and a standby server,
I
> will set it up with two production servers 'swapping' logs...?
>
>

Log Shipping with two production servers

I have two SQL Server databases, each with their own server. Is it suitable
to implement log shipping from each server to the other i.e. rather than
having the standard set up with a production server and a standby server, I
will set it up with two production servers 'swapping' logs...?Hi,
Instead of "swapping logs" you might want to implement merge
replication, however you don't give a case for why you want to
implement log shipping. Is it for a hot standby (you could setup
clustering) or do you plan to utilise one server for reporting
purposes?
Also the official line from MS is that to implement log shipping both
SQL Server Editions should be Enterprise Version, however if you can
get hold of the SQL Server 2000 Resource Kit there is a Simple Log
Shipper Tool (basically two stored procs) on there. However with the
Enterprise methond it does monitor the log shipping for you. The only
disclaimer is that I could get SLS to work in a dev environment but not
in our production setup, so we went with snapshot replication.
Good Luck
Scott|||Hi
You can't use log shipping for Scale Out as the destination DB can not be
used for write activities.
If you need to impliment something like scale out, look at replication, but
replication could use more resources than what you might gain by off loading
a server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike" wrote:
> I have two SQL Server databases, each with their own server. Is it suitable
> to implement log shipping from each server to the other i.e. rather than
> having the standard set up with a production server and a standby server, I
> will set it up with two production servers 'swapping' logs...?
>
>

Log Shipping will not restore tran logs on secondary server

We're planning to implement log shipping on our databases, and I have been toiling with it all weekend trying to get it to work on some test databases. The result is the same whether I do it via the wizard or manually via T-SQL.

I am using 3 servers, all SQL Server 2005 Standard SP1. All 3 SQL Servers are configured identically.

When I setup log shipping, it initializes with no problems. When it processes the first tran log file, it restores it with no problem. Every successive log file thereafter is not restored. No errors are generated. The only outright indication of a problem is that the monitor server shows that there has not been a recent restore.

The backup and copy both suceed. The restore claims to suceed. If I review the job history for each step, it says that it skipped the log file and then reports that it did not fina any log files to restore.

Message
2006-11-06 05:00:01.92 Skipped log backup file. Secondary DB: 'MyDemo', File: 'D:\MSSQL\Backup\MyDemo\MyDemo_20061106115619.trn'

Message
2006-11-06 05:00:01.95 Could not find a log backup file that could be applied to secondary database 'MyDemo'.
2006-11-06 05:00:01.96 The restore operation was successful. Secondary Database: 'MyDemo', Number of log backup files restored: 0

Any ideas or suggestions?

A little more info for you. I can manually restore the successive log file backups without any errors. However, the output says that there were 0 pages processed. The successive log files are being created empty. Well, these are test databases, so there are no active transactions ocurring, so no big surprise, right? I updated a lot of data in the tables, and the next log file is ....... empty.

So even with committed transactions ocurring, the tran log backup is still empty.

|||

I found the problem. It was a security setting that the Log Shipping wizard does not give you the ability to change. It defaulted to using Windows security (the account used by SQL Agent) for the connection to the Monitor server to update the state of the restore process. Because we use local system accounts, not domain accounts, for SQL Agent, it was not able to update the Monitor.

My scripts were based off of the first log shipping instance that I set up, so the option to change it there wasn’t included in the script generated by SQL Server. Since I originally set it up with the primary, secondary, and monitor on my local machine, it worked fine.

In the wizard, there is a setting for the account that the monitor should use, but it only affects the primary's connection to the monitor, not the secondary's connection.

Log Shipping two Databases

Hi,
Is is possible to sepup log shipping for two databases on one server?
I have already setup logshipping for one database and it is working
fine. I need to setup logshipping for the second database that is on the
same primary server. Can I logship it to same secondary server?
Thanks.
Egbon
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!I believe it is possible to setup logshipping for 2 different databases on
the same server.
I suggest you set up replication btw these 2 instead ... that is if the
purpose of the standby server IS NOT for Primary Server loss purpose.
Tunji
"SQL Server" <anonymous@.devdex.com> wrote in message
news:%23T0gbKlFEHA.3540@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Is is possible to sepup log shipping for two databases on one server?
> I have already setup logshipping for one database and it is working
> fine. I need to setup logshipping for the second database that is on the
> same primary server. Can I logship it to same secondary server?
> Thanks.
> Egbon
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!|||Thanks Tunji. I created two maintenance plans; one for each DB and the
logshipping is working fine for the 2 DBs to the same destination
server.
Egbon
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

Log Shipping two Databases

Hi,
Is it possible to sepup log shipping for two databases on one server?
I have already setup logshipping for one database and it is working
fine. I need to setup logshipping for the second database that is on
the
same primary server. But while doing this is using the same schedule
for both databases but i want different schedules.
Can I logship it to same secondary server?
Thanks.
ParveenYes. Can you describe what you are doing when you set this up?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
<Parveen.Beniwal.Daffodil@.gmail.com> wrote in message
news:1146027423.468492.140520@.j33g2000cwa.googlegroups.com...
> Hi,
> Is it possible to sepup log shipping for two databases on one server?
> I have already setup logshipping for one database and it is working
> fine. I need to setup logshipping for the second database that is on
> the
> same primary server. But while doing this is using the same schedule
> for both databases but i want different schedules.
> Can I logship it to same secondary server?
> Thanks.
> Parveen
>|||Hi mike
yes sure,I am having a database Test on SERVER1 and i want to
transfer Log backups of Test to a secondry Server SERVER2 on Databases
Test and Test1 both are read-only restored databases. Jobs according to
that configuration are as follows:
SERVER1:
LSAlert_SERVER1
LSBackup_Test
SERVER2:
LSAlert_SERVER1
LSCopy_SERVER1_Test
LSRestore_SERVER1_Test
As above SERVER2 is having jobs only for one database not for the
second one that is Test1 to which i want to restore at some different
schedule. But i want log shpping for the both databases on a different
schedule.
How it is possible ?
Parveen|||I'm not sure what isn't working. In Management Studio, right click on the
Test database, select properties, and set it up for log shipping. Then rigt
click the test1 database, select properties, and set it up for log shipping.
A separate backup job is createdfor each database. You also get a separate
copy and restore job for each database. So, there are no issues with having
differet schedules.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Parv" <Parveen.Beniwal.Daffodil@.gmail.com> wrote in message
news:1146197628.535252.55870@.u72g2000cwu.googlegroups.com...
> Hi mike
> yes sure,I am having a database Test on SERVER1 and i want to
> transfer Log backups of Test to a secondry Server SERVER2 on Databases
> Test and Test1 both are read-only restored databases. Jobs according to
> that configuration are as follows:
> SERVER1:
> LSAlert_SERVER1
> LSBackup_Test
> SERVER2:
> LSAlert_SERVER1
> LSCopy_SERVER1_Test
> LSRestore_SERVER1_Test
> As above SERVER2 is having jobs only for one database not for the
> second one that is Test1 to which i want to restore at some different
> schedule. But i want log shpping for the both databases on a different
> schedule.
> How it is possible ?
> Parveen
>|||Hi mike
I think you are not getting my problem i want to transport
backup of Test on SERVER1 to two databases Test and Test1 on the
SERVER2 on a different schedule. I mean
SERVER1:
Test publisher databases whose Backup is to take.
SERVER2:
Test restore backup here after every 45 mins
Test1 restore backup here after every 75 mins
But jobs on the SERVER2 are created for the restoration of the
Test on Test only not for the Test1 Database. How it is possible ?
Parveen|||Right click the database you are backing up. Select properties. Select the
Transaction Log Shipping tab. Look in the middle of the screen. You can
add as many targets to this as you choose to add. So, you just have to add
another entry to this for the other database and it can be configured with
its own schedule.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Parv" <Parveen.Beniwal.Daffodil@.gmail.com> wrote in message
news:1146206287.127394.183270@.i39g2000cwa.googlegroups.com...
> Hi mike
> I think you are not getting my problem i want to transport
> backup of Test on SERVER1 to two databases Test and Test1 on the
> SERVER2 on a different schedule. I mean
> SERVER1:
> Test publisher databases whose Backup is to take.
> SERVER2:
> Test restore backup here after every 45 mins
> Test1 restore backup here after every 75 mins
> But jobs on the SERVER2 are created for the restoration of the
> Test on Test only not for the Test1 Database. How it is possible ?
> Parveen
>

Log Shipping two Databases

Hi,
Is it possible to sepup log shipping for two databases on one server?
I have already setup logshipping for one database and it is working
fine. I need to setup logshipping for the second database that is on
the
same primary server. But while doing this is using the same schedule
for both databases but i want different schedules.
Can I logship it to same secondary server?
Thanks.
ParveenYes. Can you describe what you are doing when you set this up?
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
<Parveen.Beniwal.Daffodil@.gmail.com> wrote in message
news:1146027423.468492.140520@.j33g2000cwa.googlegroups.com...
> Hi,
> Is it possible to sepup log shipping for two databases on one server?
> I have already setup logshipping for one database and it is working
> fine. I need to setup logshipping for the second database that is on
> the
> same primary server. But while doing this is using the same schedule
> for both databases but i want different schedules.
> Can I logship it to same secondary server?
> Thanks.
> Parveen
>|||Hi mike
yes sure,I am having a database Test on SERVER1 and i want to
transfer Log backups of Test to a secondry Server SERVER2 on Databases
Test and Test1 both are read-only restored databases. Jobs according to
that configuration are as follows:
SERVER1:
LSAlert_SERVER1
LSBackup_Test
SERVER2:
LSAlert_SERVER1
LSCopy_SERVER1_Test
LSRestore_SERVER1_Test
As above SERVER2 is having jobs only for one database not for the
second one that is Test1 to which i want to restore at some different
schedule. But i want log shpping for the both databases on a different
schedule.
How it is possible ?
Parveen|||I'm not sure what isn't working. In Management Studio, right click on the
Test database, select properties, and set it up for log shipping. Then rigt
click the test1 database, select properties, and set it up for log shipping.
A separate backup job is createdfor each database. You also get a separate
copy and restore job for each database. So, there are no issues with having
differet schedules.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Parv" <Parveen.Beniwal.Daffodil@.gmail.com> wrote in message
news:1146197628.535252.55870@.u72g2000cwu.googlegroups.com...
> Hi mike
> yes sure,I am having a database Test on SERVER1 and i want to
> transfer Log backups of Test to a secondry Server SERVER2 on Databases
> Test and Test1 both are read-only restored databases. Jobs according to
> that configuration are as follows:
> SERVER1:
> LSAlert_SERVER1
> LSBackup_Test
> SERVER2:
> LSAlert_SERVER1
> LSCopy_SERVER1_Test
> LSRestore_SERVER1_Test
> As above SERVER2 is having jobs only for one database not for the
> second one that is Test1 to which i want to restore at some different
> schedule. But i want log shpping for the both databases on a different
> schedule.
> How it is possible ?
> Parveen
>|||Hi mike
I think you are not getting my problem i want to transport
backup of Test on SERVER1 to two databases Test and Test1 on the
SERVER2 on a different schedule. I mean
SERVER1:
Test publisher databases whose Backup is to take.
SERVER2:
Test restore backup here after every 45 mins
Test1 restore backup here after every 75 mins
But jobs on the SERVER2 are created for the restoration of the
Test on Test only not for the Test1 Database. How it is possible ?
Parveen|||Right click the database you are backing up. Select properties. Select the
Transaction Log Shipping tab. Look in the middle of the screen. You can
add as many targets to this as you choose to add. So, you just have to add
another entry to this for the other database and it can be configured with
its own schedule.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Parv" <Parveen.Beniwal.Daffodil@.gmail.com> wrote in message
news:1146206287.127394.183270@.i39g2000cwa.googlegroups.com...
> Hi mike
> I think you are not getting my problem i want to transport
> backup of Test on SERVER1 to two databases Test and Test1 on the
> SERVER2 on a different schedule. I mean
> SERVER1:
> Test publisher databases whose Backup is to take.
> SERVER2:
> Test restore backup here after every 45 mins
> Test1 restore backup here after every 75 mins
> But jobs on the SERVER2 are created for the restoration of the
> Test on Test only not for the Test1 Database. How it is possible ?
> Parveen
>

Log Shipping Transaction Logs.

Hi,

We currently have a couple a large Databases running on SQL 2000 SP3 Clustered Windows 2000 SP3 environment.

Log Shipping is enabled for both databases shipping to a Standalone SQL 2000 SP3 Windows 2000 SP3 box.

Log Shipping occurs every 15 mins with the Transaction Files on average being no more than 500KB in size. However, every now and then a Transaction Log comes through and it can be as big as 3.52GB.

Not sure why this is happening. Anyone got any ideas?

Regards

Paul TowlerIs this after substantial activity or reindexing?|||i think auto shrink or some other job is enabled
if iam right, the auto shrink or job gets activated and the step goes thru
which will obviously create transaction file with huge size.|||Thanks for your replies.

There is a Job to Optimise the Database which does re-index the database. I presume all the indexing changes count as changes and therefore shipped as one big Transacton file.

Hopefully there is a way to prevent these hugh Transaction Files without turning off the indexing job.

Regards
Paul Towlersql

Log Shipping to two Databases on One Secondary Server

Is it possible to do SQL log shipping to more than one
Databases on same Secondry Server WITH A DIFFERENT SCHEDULE for each
log shipping?
You can set up log shipping to go to as many servers as
you want, but you only get one schedule in the plan. If
you set up a second log shipping schedule, you get an
error because the server is already set up for log
shipping in the other plan.
Just wondering if this is possible.
For example. I have 2 servers.
The Main server needs to ship it's logs to two other
databases. (Server A)
I want the main server to ship the logs to Server A every
45 minutes for ClientDatabase1.
I want the main server to ship the logs to Server A every
60 minutes for ClientDatabase2.
Can this be set up?
ParveenHi Parveen,
Yes, I believe that it is possible. I assume that you are setting up
log shipping by using the Database Maintenance Plan Wizard.
After you complete the setup of log shipping through the wizard there
will be a number of SQL Server Agent jobs created. Their names should
be similar to what I've listed below.
Jobs on primary/main server:
* Transaction Log Backup Job for DB Maintenance Plan <Plan Name>
Jobs on secondary/DR server:
* Log Shipping copy for <Primary Server>.<DB Name>_logshipping
* Log Shipping Restore for <Primary Server>.<DB Name>_logshipping
There are also jobs on the monitor server (if you have one) but you
don't need to worry about these for your purposes.
Now, all you need to do is alter the scheduling of the SQL Server Agent
jobs to get the timing that you want. Please note that the "copy" and
"restore" jobs should occur after the backup job (e.g. 2 minutes after)
and that the "copy" and "restore" jobs should not happen at the same
time. The "copy" job should be scheduled first and the "restore" job
should be scheduled after that (e.g. 2 minutes after the "copy" job).
HTH
Parveen.Beniwal.Daffodil@.gmail.com wrote:
> Is it possible to do SQL log shipping to more than one
> Databases on same Secondry Server WITH A DIFFERENT SCHEDULE for each
> log shipping?
> You can set up log shipping to go to as many servers as
> you want, but you only get one schedule in the plan. If
> you set up a second log shipping schedule, you get an
> error because the server is already set up for log
> shipping in the other plan.
> Just wondering if this is possible.
> For example. I have 2 servers.
> The Main server needs to ship it's logs to two other
> databases. (Server A)
> I want the main server to ship the logs to Server A every
> 45 minutes for ClientDatabase1.
> I want the main server to ship the logs to Server A every
> 60 minutes for ClientDatabase2.
> Can this be set up?
> Parveen|||Hi HTH
Thanx for the quick and helpful reply but i am configuring log
shipping using the Management Studio but i am not aware how to
configure log shipping using DB Maintenance Plan. Will you please guide
me a little bit abt that also.
Parveen|||Hi Parveen,
If you're already familiar with a way of configuring log shipping then
just do it that way. After you have configured your log shipping just
change the scheduling of the SQL Server Agent jobs like I said
previously.
I believe that you're using SQL Server 2005...The instructions I wrote
were geared towards SQL Server 2000. They should probably still be
valid though (i.e. there are log shipping jobs created and the
schedules of these can be edited to suit your needs)|||Hi HTH
Yes you are right i am using the SQL Server 2005 Management
Studio. Let me explain once more my problem. I am having a database
Test on SERVER1 and i want to transfer Log backups of Test to a
secondry Server SERVER2 on Databases Test and Test1 both are read-only
restored databases. Jobs according to that configuration are as
follows:
SERVER1:
LSAlert_SERVER1
LSBackup_Test
SERVER2:
LSAlert_SERVER1
LSCopy_SERVER1_Test
LSRestore_SERVER1_Test
As above SERVER2 is having jobs only for one database not for the
second one that is Test1 to which i want to restore at some different
schedule.
How it is possible ?
Parveen|||Hello Parveen,
Apologies for my late reply but I went offline shortly after posting.
I am not too experienced in the use of SQL Server 2005 so I'm afraid I
can't be of much more help. I would have imagined that you would get
more log shipping jobs showing up as you are log shipping to more than
1 DB.
Have you checked out Books Online for SQL Server 2005?
The only other thing can suggest is that you take a look at what the
backup, copy and restore jobs are actually doing (e.g. what T-SQL code
they execute) and maybe that could lead you down the right path.
Sorry I can't be of more help.

Log Shipping to two Databases on One Secondary Server

Is it possible to do SQL log shipping to more than one
Databases on same Secondry Server WITH A DIFFERENT SCHEDULE for each
log shipping?
You can set up log shipping to go to as many servers as
you want, but you only get one schedule in the plan. If
you set up a second log shipping schedule, you get an
error because the server is already set up for log
shipping in the other plan.
Just wondering if this is possible.
For example. I have 2 servers.
The Main server needs to ship it's logs to two other
databases. (Server A)
I want the main server to ship the logs to Server A every
45 minutes for ClientDatabase1.
I want the main server to ship the logs to Server A every
60 minutes for ClientDatabase2.
Can this be set up?
ParveenHi Parveen,
Yes, I believe that it is possible. I assume that you are setting up
log shipping by using the Database Maintenance Plan Wizard.
After you complete the setup of log shipping through the wizard there
will be a number of SQL Server Agent jobs created. Their names should
be similar to what I've listed below.
Jobs on primary/main server:
* Transaction Log Backup Job for DB Maintenance Plan <Plan Name>
Jobs on secondary/DR server:
* Log Shipping copy for <Primary Server>.<DB Name>_logshipping
* Log Shipping Restore for <Primary Server>.<DB Name>_logshipping
There are also jobs on the monitor server (if you have one) but you
don't need to worry about these for your purposes.
Now, all you need to do is alter the scheduling of the SQL Server Agent
jobs to get the timing that you want. Please note that the "copy" and
"restore" jobs should occur after the backup job (e.g. 2 minutes after)
and that the "copy" and "restore" jobs should not happen at the same
time. The "copy" job should be scheduled first and the "restore" job
should be scheduled after that (e.g. 2 minutes after the "copy" job).
HTH
Parveen.Beniwal.Daffodil@.gmail.com wrote:
> Is it possible to do SQL log shipping to more than one
> Databases on same Secondry Server WITH A DIFFERENT SCHEDULE for each
> log shipping?
> You can set up log shipping to go to as many servers as
> you want, but you only get one schedule in the plan. If
> you set up a second log shipping schedule, you get an
> error because the server is already set up for log
> shipping in the other plan.
> Just wondering if this is possible.
> For example. I have 2 servers.
> The Main server needs to ship it's logs to two other
> databases. (Server A)
> I want the main server to ship the logs to Server A every
> 45 minutes for ClientDatabase1.
> I want the main server to ship the logs to Server A every
> 60 minutes for ClientDatabase2.
> Can this be set up?
> Parveen|||Hi HTH
Thanx for the quick and helpful reply but i am configuring log
shipping using the Management Studio but i am not aware how to
configure log shipping using DB Maintenance Plan. Will you please guide
me a little bit abt that also.
Parveen|||Hi Parveen,
If you're already familiar with a way of configuring log shipping then
just do it that way. After you have configured your log shipping just
change the scheduling of the SQL Server Agent jobs like I said
previously.
I believe that you're using SQL Server 2005...The instructions I wrote
were geared towards SQL Server 2000. They should probably still be
valid though (i.e. there are log shipping jobs created and the
schedules of these can be edited to suit your needs)|||Hi HTH
Yes you are right i am using the SQL Server 2005 Management
Studio. Let me explain once more my problem. I am having a database
Test on SERVER1 and i want to transfer Log backups of Test to a
secondry Server SERVER2 on Databases Test and Test1 both are read-only
restored databases. Jobs according to that configuration are as
follows:
SERVER1:
LSAlert_SERVER1
LSBackup_Test
SERVER2:
LSAlert_SERVER1
LSCopy_SERVER1_Test
LSRestore_SERVER1_Test
As above SERVER2 is having jobs only for one database not for the
second one that is Test1 to which i want to restore at some different
schedule.
How it is possible ?
Parveen|||Hello Parveen,
Apologies for my late reply but I went offline shortly after posting.
I am not too experienced in the use of SQL Server 2005 so I'm afraid I
can't be of much more help. I would have imagined that you would get
more log shipping jobs showing up as you are log shipping to more than
1 DB.
Have you checked out Books Online for SQL Server 2005?
The only other thing can suggest is that you take a look at what the
backup, copy and restore jobs are actually doing (e.g. what T-SQL code
they execute) and maybe that could lead you down the right path.
Sorry I can't be of more help.

Log shipping sync error 14421

Hi
SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
broken, out of sync error for all databases on standby server error
14421. I have manually restored all the log backups and updated manually
log_shipping_secondaries columns set last_copied_last_updated &
last_loaded_last_updated with 15 min difference which i have configured.
But the log backups are not copied &last_copied_filename is not getting
updated. how can i fix this issues and continue log shipping with out
reconfiguring?
thanks for looking
kris
Did you look at:
Description of error message 14420 and error message 14421 that occur when
you use log shipping in SQL Server
http://support.microsoft.com/kb/329133
?
"krishna" wrote:

> Hi
> SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
> broken, out of sync error for all databases on standby server error
> 14421. I have manually restored all the log backups and updated manually
> log_shipping_secondaries columns set last_copied_last_updated &
> last_loaded_last_updated with 15 min difference which i have configured.
> But the log backups are not copied &last_copied_filename is not getting
> updated. how can i fix this issues and continue log shipping with out
> reconfiguring?
> thanks for looking
> kris
>
|||I looked into that kb article, i have tried accessing the folder on the
standby server from source machine. it is fine. i dont know why the logs
are not copied to standby server. I just want to fix the issue without
reconfiguring. Is there any way to copy & restore the remaining logs and
updating the logshipping tables and continue the process?
Edgardo Valdez wrote:[vbcol=seagreen]
> Did you look at:
> Description of error message 14420 and error message 14421 that occur when
> you use log shipping in SQL Server
> http://support.microsoft.com/kb/329133
> ?
> "krishna" wrote:
|||I looked into that kb article, i have tried accessing the folder on the
standby server from source machine. it is fine. i dont know why the logs
are not copied to standby server. I just want to fix the issue without
reconfiguring. Is there any way to copy & restore the remaining logs and
updating the logshipping tables and continue the process?
krishna wrote:
> Hi
> SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
> broken, out of sync error for all databases on standby server error
> 14421. I have manually restored all the log backups and updated manually
> log_shipping_secondaries columns set last_copied_last_updated &
> last_loaded_last_updated with 15 min difference which i have configured.
> But the log backups are not copied &last_copied_filename is not getting
> updated. how can i fix this issues and continue log shipping with out
> reconfiguring?
> thanks for looking
> kris

Log shipping sync error 14421

Hi
SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
broken, out of sync error for all databases on standby server error
14421. I have manually restored all the log backups and updated manually
log_shipping_secondaries columns set last_copied_last_updated &
last_loaded_last_updated with 15 min difference which i have configured.
But the log backups are not copied &last_copied_filename is not getting
updated. how can i fix this issues and continue log shipping with out
reconfiguring?
thanks for looking
krisDid you look at:
Description of error message 14420 and error message 14421 that occur when
you use log shipping in SQL Server
http://support.microsoft.com/kb/329133
?
"krishna" wrote:

> Hi
> SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
> broken, out of sync error for all databases on standby server error
> 14421. I have manually restored all the log backups and updated manually
> log_shipping_secondaries columns set last_copied_last_updated &
> last_loaded_last_updated with 15 min difference which i have configured.
> But the log backups are not copied &last_copied_filename is not getting
> updated. how can i fix this issues and continue log shipping with out
> reconfiguring?
> thanks for looking
> kris
>|||I looked into that kb article, i have tried accessing the folder on the
standby server from source machine. it is fine. i dont know why the logs
are not copied to standby server. I just want to fix the issue without
reconfiguring. Is there any way to copy & restore the remaining logs and
updating the logshipping tables and continue the process?
Edgardo Valdez wrote:[vbcol=seagreen]
> Did you look at:
> Description of error message 14420 and error message 14421 that occur when
> you use log shipping in SQL Server
> http://support.microsoft.com/kb/329133
> ?
> "krishna" wrote:
>|||I looked into that kb article, i have tried accessing the folder on the
standby server from source machine. it is fine. i dont know why the logs
are not copied to standby server. I just want to fix the issue without
reconfiguring. Is there any way to copy & restore the remaining logs and
updating the logshipping tables and continue the process?
krishna wrote:
> Hi
> SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
> broken, out of sync error for all databases on standby server error
> 14421. I have manually restored all the log backups and updated manually
> log_shipping_secondaries columns set last_copied_last_updated &
> last_loaded_last_updated with 15 min difference which i have configured.
> But the log backups are not copied &last_copied_filename is not getting
> updated. how can i fix this issues and continue log shipping with out
> reconfiguring?
> thanks for looking
> kris

Log shipping sync error 14421

Hi
SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
broken, out of sync error for all databases on standby server error
14421. I have manually restored all the log backups and updated manually
log_shipping_secondaries columns set last_copied_last_updated &
last_loaded_last_updated with 15 min difference which i have configured.
But the log backups are not copied &last_copied_filename is not getting
updated. how can i fix this issues and continue log shipping with out
reconfiguring?
thanks for looking
krisDid you look at:
Description of error message 14420 and error message 14421 that occur when
you use log shipping in SQL Server
http://support.microsoft.com/kb/329133
?
"krishna" wrote:
> Hi
> SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
> broken, out of sync error for all databases on standby server error
> 14421. I have manually restored all the log backups and updated manually
> log_shipping_secondaries columns set last_copied_last_updated &
> last_loaded_last_updated with 15 min difference which i have configured.
> But the log backups are not copied &last_copied_filename is not getting
> updated. how can i fix this issues and continue log shipping with out
> reconfiguring?
> thanks for looking
> kris
>|||I looked into that kb article, i have tried accessing the folder on the
standby server from source machine. it is fine. i dont know why the logs
are not copied to standby server. I just want to fix the issue without
reconfiguring. Is there any way to copy & restore the remaining logs and
updating the logshipping tables and continue the process?
Edgardo Valdez wrote:
> Did you look at:
> Description of error message 14420 and error message 14421 that occur when
> you use log shipping in SQL Server
> http://support.microsoft.com/kb/329133
> ?
> "krishna" wrote:
>> Hi
>> SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
>> broken, out of sync error for all databases on standby server error
>> 14421. I have manually restored all the log backups and updated manually
>> log_shipping_secondaries columns set last_copied_last_updated &
>> last_loaded_last_updated with 15 min difference which i have configured.
>> But the log backups are not copied &last_copied_filename is not getting
>> updated. how can i fix this issues and continue log shipping with out
>> reconfiguring?
>> thanks for looking
>> kris|||I looked into that kb article, i have tried accessing the folder on the
standby server from source machine. it is fine. i dont know why the logs
are not copied to standby server. I just want to fix the issue without
reconfiguring. Is there any way to copy & restore the remaining logs and
updating the logshipping tables and continue the process?
krishna wrote:
> Hi
> SQLServer 2000 sp3 enterprise running logshipping smoothly, today its
> broken, out of sync error for all databases on standby server error
> 14421. I have manually restored all the log backups and updated manually
> log_shipping_secondaries columns set last_copied_last_updated &
> last_loaded_last_updated with 15 min difference which i have configured.
> But the log backups are not copied &last_copied_filename is not getting
> updated. how can i fix this issues and continue log shipping with out
> reconfiguring?
> thanks for looking
> kris

log shipping set up via scripts instead of GUI

Is it possible to set up log shipping via scripts instead
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!
Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!
|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping=20
http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =
(White Paper)=20
http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping=20
http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping=20
http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping=20
http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =
Errors=20
http://support.microsoft.com/?id=3D329133
--=20
Keith
"Tom Horner" <thorner@.s1.com> wrote in message =
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead=20
> of GUI? We have over 50 databases being log shipped, and=20
> occasional (almost random) failures for various reasons=20
> cause us to have to "reset" (redo) the log shipping. =20
> Doing this via the GUI is a time-consuming process. I=20
> found 5/23/03 webcast with PPT slide saying this is "not=20
> supported". Does this mean not POSSIBLE? We are using=20
> SQL server 2000 on Windows 2000 boxes, two separate=20
> servers with primary and secondary (log shipped-to)=20
> databases.
>=20
> Thanks in advance!
|||yes.
this is exactly what we are doing here.
Here is an example script to apply logs to the standby.
Cheers,
Greg Jackson
PDX, Oregon
begin 666 RETORE LOG SCRIPT FOR ALL TRAN BAKS IN A DIR.SQL
M__XO`"H`*@.`J`"H`*@.`J`" `3P!B`&H`90!C`'0`.@.`@.`" `4P!T`&\`<@.!E
M`&0`( !0`'(`;P!C`&4`9 !U`'(`90`@.`'4`<P!P`%\`4@.!A`'0`:0!N`&<`
M<P!?`%0`<@.!A`&X`<P!A`&,`= !I`&\`;@.!,`&\`9P!?`%(`90!S`'0`;P!R
M`&4`( `@.`" `( !3`&,`<@.!I`' `= `@.`$0`80!T`&4`.@.`@.`# `-0`O`#$`
M,@.`O`#(`, `P`# `( `X`#H`-0`W`#H`,@.`U`" `4 !-`" `*@.`J`"H`*@.`J
M`"H`+P`-``H`+P`J`"H`*@.`J`"H`*@.`@.`$\`8@.!J`&4`8P!T`#H`( `@.`%,`
M= !O`'(`90!D`" `4 !R`&\`8P!E`&0`=0!R`&4`( !U`',`< !?`%(`80!T
M`&D`;@.!G`',`7P!4`'(`80!N`',`80!C`'0`:0!O`&X`3 !O`&<`7P!2`&4`
M<P!T`&\`<@.!E`" `( `J`"H`*@.`J`"H`*@.`O``T`"@.`O`"H`"0!7`'(`:0!T
M`'0`90!N`" `0@.!Y`#H`( !!`&P`90!X`" `5P!E`'(`9P!E`&P`90!S``T`
M"@.`J`" `"0!#`'(`90!A`'0`90!D`#H`( `@.`# `-0`O`# `,0`O`#(`, `P
M`#$`#0`*`"H`"0!.`&\`= !E`',`.@.`-``H`*@.`-``H`*@.`@.`" `( `@.`" `
M( `@.`" `( !!`&P`= !E`'(`90!D`" `0@.!Y`#H`( `@.`$$`; !E`'@.`( !7
M`&4`<@.!G`&4`; !E`',`#0`*`"H`( `@.`" `( `@.`" `( `@.`" `1 !A`'0`
M90`Z`" `( `P`#8`+P`P`#$`+P`R`# `, `Q``T`"@.`J`" `( `@.`" `( `@.
M`" `( `@.`$X`;P!T`&4`<P`Z`" `( !#`&\`;0!M`&4`;@.!T`&4`9 `-``H`
M*@.`-``H`*@.`@.`" `( `@.`" `( `@.`" `( !!`&P`= !E`'(`90!D`" `0@.!Y
M`#H`( `-``H`*@.`@.`" `( `@.`" `( `@.`" `( !$`&$`= !E`#H`#0`*`"H`
M( `@.`" `( `@.`" `( `@.`" `3@.!O`'0`90!S`#H`( `@.`$D`1@.`@.`%D`3P!5
M`" `00!,`%0`10!2`" `5 !(`$D`4P`@.`% `4@.!/`$,`10!$`%4`4@.!%`"P`
M( !#`$\`4 !9`" `00!.`$0`( !0`$$`4P!4`$4`( !4`$@.`10`@.`"<`00!,
M`%0`10!2`$4`1 `@.`$(`60`G``T`"@.`J`" `( `@.`" `( `@.`" `( `@.`%,`
M10!#`%0`20!/`$X`( !4`$\`( !$`%4`4 !,`$D`0P!!`%0`10`@.`$D`5 `[
M`" `5 !(`$4`3@.`@.`$4`1 !)`%0`( !4`$@.`10`@.`$8`20!2`%,`5 `@.`$(`
M3 !!`$X`2P`@.`$,`3P!0`%D`+ `@.`$P`10!!`%8`20!.`$<`#0`*`"H`( `@.
M`" `( `@.`" `( `@.`" `00`@.`$0`50!0`$P`20!#`$$`5 !%`" `20!.`" `
M4 !,`$$`0P!%`" `1@.!/`%(`( !4`$@.`10`@.`$X`10!8`%0`( !0`$4`4@.!3
M`$\`3@.`@.`%0`3P`@.`$4`1 !)`%0`( !4`$@.`20!3`" `4 !2`$\`0P`N``T`
M"@.`J``T`"@.`J`"\`#0`*``T`"@.`M`"T`9 !R`&\`< `@.`' `<@.!O`&,`90!D
M`'4`<@.!E`" `=0!S`' `7P!2`&$`= !I`&X`9P!S`%\`5 !R`&$`;@.!S`&$`
M8P!T`&D`;P!N`$P`;P!G`%\`4@.!E`',`= !O`'(`90`-``H`#0`*``T`"@.`M
M`"T`80!S``T`"@.`-``H`<P!E`'0`( !N`&\`8P!O`'4`;@.!T`" `;P!N``T`
M"@.`-``H`9 !E`&,`; !A`'(`90`@.`$ `<P!T`'(`:0!N`&<`( !V`&$`<@.!C
M`&@.`80!R`"@.`,0`P`# `, `I`"P`#0`*``D`0 !,`&\`9P!&`&D`; !E`" `
M=@.!A`'(`8P!H`&$`<@.`H`#$`, `P`# `*0`-``H`#0`*`&D`9@.`@.`&4`> !I
M`',`= !S`"@.`<P!E`&P`90!C`'0`( `J`" `9@.!R`&\`;0`@.`'0`90!M`' `
M9 !B`"X`+@.!S`'D`<P!O`&(`:@.!E`&,`= !S`" `=P!H`&4`<@.!E`" `:0!D
M`" `/0`@.`&\`8@.!J`&4`8P!T`%\`:0!D`"@.`)P!T`&4`;0!P`&0`8@.` N`"X`
M(P!,`&\`9P!3`&@.`:0!P`"<`*0`I``T`"@.!D`'(`;P!P`" `= !A`&(`; !E
M`" `(P!,`&\`9P!3`&@.`:0!P``T`"@.`-``H`8P!R`&4`80!T`&4`( !T`&$`
M8@.!L`&4`#0`*``D`(P!,`&\`9P!3`&@.`:0!P``T`"@.`)``D`* `-``H`"0`)
M``D`3 !O`&<`1@.!I`&P`90`@.`'8`80!R`&,`: !A`'(`* `Q`# `, `P`"D`
M#0`*``D`"0`I``T`"@.`-``H`:0!N`',`90!R`'0`( `C`$P`;P!G`%,`: !I
M`' `#0`*`&4`> !E`&,`( !M`&$`<P!T`&4`<@.`N`&0`8@.!O`"X`> !P`%\`
M8P!M`&0`<P!H`&4`; !L`" `)P!D`&D`<@.`@.`%P`7 !D`&$`= !A`'<`: !S
M`&4`, `Q`%P`4P!1`$P`0@.!!`$,`2P!5`% `7 !0`%(`3P!$`%,`40!,`# `
M,P!<`&0`8@.!(`$$`50!<`%0`4@.!.`%,`7 `J`" `+P!"`" `+P!/`$0`)P`-
M``H`#0`*``T`"@.`M`"T`<P!E`'0`( ! `$P`;P!G`$8`:0!L`&4`( `]`" `
M* !S`&4`; !E`&,`= `@.`"H`( `@.`&8`<@.!O`&T`( `C`$P`;P!G`%,`: !I
M`' `( !O`'(`9 !E`'(`( !B`'D`( !,`&\`9P!&`&D`; !E`" `9 !E`',`
M8P`I``T`"@.!D`&4`8P!L`&$`<@.!E`" `8P!U`'(`,0`@.`&,`=0!R`',`;P!R
M`" `9@.!O`'(`#0`*`',`90!L`&4`8P!T`" `; !O`&<`9@.!I`&P`90`-``H`
M9@.!R`&\`;0`@.`",`3 !O`&<`4P!H`&D`< `-``H`#0`*`&\`< !E`&X`( !C
M`'4`<@.`Q``T`"@.`-``H`9@.!E`'0`8P!H`" `;@.!E`'@.`= `@.`&8`<@.!O`&T`
M( !C`'4`<@.`Q`" `:0!N`'0`;P`@.`$ `3 !O`&<`1@.!I`&P`90`-``H`#0`*
M`'<`: !I`&P`90`@.`$ `0 !F`&4`= !C`&@.`7P!S`'0`80!T`'4`<P`@.`#T`
M( `P``T`"@.!B`&4`9P!I`&X`#0`*``T`"@.`-``H`<P!E`'0`( ! `',`= !R
M`&D`;@.!G`" `/0`@.`"<`4@.!%`%,`5 !/`%(`10`@.`$P`3P!'``T`"@.`)``D`
M"0!D`&(`2 !!`%4`#0`*``D`"0!&`%(`3P!-`" `1 !)`%,`2P`@.`#T`( `@.
M``T`"@.`)``D`"0!.`"<`( `K`" `)P`G`"<`)P`@.`"L`( `G`%P`7 !D`&$`
M= !A`'<`: !S`&4`, `Q`%P`4P!1`$P`0@.!!`$,`2P!5`% `7 !0`%(`3P!$
M`%,`40!,`# `,P!<`&0`8@.!(`$$`50!<`%0`4@.!.`%,`7 `G`" `*P`@.`$ `
M3 !O`&<`1@.!I`&P`90`@.`"L`( `G`"<`)P`G`" `*P`-``H`"0`)`"<`( !7
M`$D`5 !(``T`"@.`)``D`( `)`%,`5 !!`$X`1 !"`%D`( `]`" `)P`@.`"L`
M( `G`"<`)P`G`" `*P`@.`"<`7 !<`&0`80!T`&$`=P!H`',`90`P`#$`7 !3
M`%$`3 !"`$$`0P!+`%4`4 !<`% `4@.!/`$0`4P!1`$P`, `S`%P`9 !B`$@.`
M00!5`%P`5 !2`$X`4P!<`&0`8@.!(`$$`50!?`&P`;P!G`',`: !I`' `7P!5
M`&X`9 !O`$8`:0!L`&4`+@.!L`&0`9@.`G`"L`( `G`"<`)P`G``T`"@.`-``H`
M< !R`&D`;@.!T`" `* ! `',`= !R`&D`;@.!G`"D`#0`*`"T`+0!U`',`90`@.
M`' `<@.!I`&X`= `@.`'0`;P`@.`&,`<@.!E`&$`= !E`" `<P!C`'(`:0!P`'0`
M<P`-``H`+0`M`&,`80!N`" `8P!H`&$`;@.!G`&4`( !A`&(`;P!V`&4`( !T
M`&\`( !E`'@.`90!C`" `= !O`" `<@.!U`&X`( !I`&X`; !I`&X`90`-``H`
M9@.!E`'0`8P!H`" `;@.!E`'@.`= `@.`&8`<@.!O`&T`( !C`'4`<@.`Q`" `:0!N
M`'0`;P`@.`$ `3 !O`&<`1@.!I`&P`90`-``H`90!N`&0`#0`*``T`"@.!D`&4`
J80!L`&P`;P!C`&$`= !E`" `8P!U`'(`,0`-``H`#0`*`$<`3P`-``H`
`
end

log shipping set up via scripts instead of GUI

Is it possible to set up log shipping via scripts instead
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping=20
http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =
(White Paper)=20
http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping=20
http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping=20
http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping=20
http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =
Errors=20
http://support.microsoft.com/?id=3D329133
--=20
Keith
"Tom Horner" <thorner@.s1.com> wrote in message =
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead=20
> of GUI? We have over 50 databases being log shipped, and=20
> occasional (almost random) failures for various reasons=20
> cause us to have to "reset" (redo) the log shipping. =20
> Doing this via the GUI is a time-consuming process. I=20
> found 5/23/03 webcast with PPT slide saying this is "not=20
> supported". Does this mean not POSSIBLE? We are using=20
> SQL server 2000 on Windows 2000 boxes, two separate=20
> servers with primary and secondary (log shipped-to)=20
> databases.
>=20
> Thanks in advance!sql

log shipping set up via scripts instead of GUI

Is it possible to set up log shipping via scripts instead
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =(White Paper) http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =Errors http://support.microsoft.com/?id=3D329133
-- Keith
"Tom Horner" <thorner@.s1.com> wrote in message =news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead > of GUI? We have over 50 databases being log shipped, and > occasional (almost random) failures for various reasons > cause us to have to "reset" (redo) the log shipping. > Doing this via the GUI is a time-consuming process. I > found 5/23/03 webcast with PPT slide saying this is "not > supported". Does this mean not POSSIBLE? We are using > SQL server 2000 on Windows 2000 boxes, two separate > servers with primary and secondary (log shipped-to) > databases.
> > Thanks in advance!|||Tom,
the sql server resource kit has some scripts to do this,
which are particularly useful if you only have standard
edition or lower. Similar scripts are available for free
from various sites (eg http://www.sql-server-
performance.com/sql_server_log_shipping.asp). In both
cases you won't get access to a monitoring GUI, but
alerts/reports can be set up to perform this work.
Regards,
Paul Ibison

Log shipping reconciliation

I have a database reconciliation script that runs between two databases and
reconciles object counts and table counts etc between the two.
Is there a way to run such a script across a primary and secondary in log
shipping configuration. As the secondary is in RESTORING state it's not
accessible. Therefore is it possible to do something like bring it briefly up
to standby state, run the reconciliation and then take it back to restoring
again? Would this work and are there any gotchas?
Cheers.
Here is an example of how to do it:
there are two databases logshippingtestbak and logshippingtest.
I backup loshippingtest and restore this backup into the database
logshippingtestback with no recovery
backup log logshippingtest to disk='c:\logshippingtestlog.bak'
GO
--restoring my first log
restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
norecovery
GO
select * from logshippingtestbak.dbo.sysobjects
Server: Msg 927, Level 14, State 2, Line 1
Database 'logshippingtestbak' cannot be opened. It is in the middle of a
restore.
--i backup another log
backup log logshippingtest to disk='c:\logshippingtestlog.bak'
--i restore it with the standby option
restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
standby ='c:\standby.bak'
--i read this database
select * from logshippingtestbak.dbo.sysobjects
--I restore the same log this time with norecovery
restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
norecovery
--I verify this database is inaccessible again.
select * from logshippingtestbak.dbo.sysobjects
Server: Msg 927, Level 14, State 2, Line 1
Database 'logshippingtestbak' cannot be opened. It is in the middle of a
restore.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kev" <Kev@.discussions.microsoft.com> wrote in message
news:5722A586-57E3-41AA-B6DF-021F50F7F2CB@.microsoft.com...
>I have a database reconciliation script that runs between two databases and
> reconciles object counts and table counts etc between the two.
> Is there a way to run such a script across a primary and secondary in log
> shipping configuration. As the secondary is in RESTORING state it's not
> accessible. Therefore is it possible to do something like bring it briefly
> up
> to standby state, run the reconciliation and then take it back to
> restoring
> again? Would this work and are there any gotchas?
> Cheers.
|||Is it possible to do something like:
restore database [logshippingtestbak] with
standby=''c:\logshippingtestlog.bak'
<do the reconciliation>
restore database [logshippingtestbak] with norecovery
or do you always need to restore the last transaction log to switch modes.
Cheers
Kev.
"Hilary Cotter" wrote:

> Here is an example of how to do it:
> there are two databases logshippingtestbak and logshippingtest.
> I backup loshippingtest and restore this backup into the database
> logshippingtestback with no recovery
> backup log logshippingtest to disk='c:\logshippingtestlog.bak'
> GO
> --restoring my first log
> restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
> norecovery
> GO
> select * from logshippingtestbak.dbo.sysobjects
> Server: Msg 927, Level 14, State 2, Line 1
> Database 'logshippingtestbak' cannot be opened. It is in the middle of a
> restore.
> --i backup another log
> backup log logshippingtest to disk='c:\logshippingtestlog.bak'
> --i restore it with the standby option
> restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
> standby ='c:\standby.bak'
> --i read this database
> select * from logshippingtestbak.dbo.sysobjects
> --I restore the same log this time with norecovery
> restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
> norecovery
> --I verify this database is inaccessible again.
> select * from logshippingtestbak.dbo.sysobjects
> Server: Msg 927, Level 14, State 2, Line 1
> Database 'logshippingtestbak' cannot be opened. It is in the middle of a
> restore.
>
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kev" <Kev@.discussions.microsoft.com> wrote in message
> news:5722A586-57E3-41AA-B6DF-021F50F7F2CB@.microsoft.com...
>
>
|||It doesn't have to be the last transaction log, but it would have to be the
next one in the chain. Consider if you dump each hour, you might not have
another log for 1 hour or so.
Also you don't need to put it back into norecovery, the next log applied
will. I prefer to put it back into norecovery so my users can't access it
and then interfer with the next tlog restore.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kev" <Kev@.discussions.microsoft.com> wrote in message
news:629337E7-A409-49C3-9C99-7510FC802069@.microsoft.com...[vbcol=seagreen]
> Is it possible to do something like:
> restore database [logshippingtestbak] with
> standby=''c:\logshippingtestlog.bak'
> <do the reconciliation>
> restore database [logshippingtestbak] with norecovery
> or do you always need to restore the last transaction log to switch modes.
> Cheers
> Kev.
>
> "Hilary Cotter" wrote:
|||Would my bit of sql work?
"Hilary Cotter" wrote:

> It doesn't have to be the last transaction log, but it would have to be the
> next one in the chain. Consider if you dump each hour, you might not have
> another log for 1 hour or so.
> Also you don't need to put it back into norecovery, the next log applied
> will. I prefer to put it back into norecovery so my users can't access it
> and then interfer with the next tlog restore.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kev" <Kev@.discussions.microsoft.com> wrote in message
> news:629337E7-A409-49C3-9C99-7510FC802069@.microsoft.com...
>
>
|||No, you would have to restore the log, like this
restore log [logshippingtestbak] from disk='c:\mylog' with
standby=''c:\logshippingtestlog.bak'
<do the reconciliation>
restore log [logshippingtestbak] from disk='c:\mylog1.bak' with norecovery
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kev" <Kev@.discussions.microsoft.com> wrote in message
news:10217BE0-4F01-44D0-B7F6-6E6661B385F9@.microsoft.com...[vbcol=seagreen]
> Would my bit of sql work?
> "Hilary Cotter" wrote:
|||Are there any disadvantages to keeping it in standby mode all the time?
Presumably you can still restore in the same way - you just have to be
careful that nobody tries to access it at the wrong time.
Kev.
"Hilary Cotter" wrote:

> No, you would have to restore the log, like this
> restore log [logshippingtestbak] from disk='c:\mylog' with
> standby=''c:\logshippingtestlog.bak'
> <do the reconciliation>
> restore log [logshippingtestbak] from disk='c:\mylog1.bak' with norecovery
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kev" <Kev@.discussions.microsoft.com> wrote in message
> news:10217BE0-4F01-44D0-B7F6-6E6661B385F9@.microsoft.com...
>
>

log shipping question on two databases

Hi,
I created 2 log shipping plans at the same time, for database dbA and dbB
respectively, to ship logs to antother database server.
All the log transaction schedule and location are the same.
However, only log shipping plan for dbA succeed.
Is there any restriction on log shipping for 2 databases at the same time?
Thanks for help.
Jason
No, there is no such restriction. You can can configure two databases from
the same instance for log shipping.
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Jason Huang" wrote:

> Hi,
> I created 2 log shipping plans at the same time, for database dbA and dbB
> respectively, to ship logs to antother database server.
> All the log transaction schedule and location are the same.
> However, only log shipping plan for dbA succeed.
> Is there any restriction on log shipping for 2 databases at the same time?
> Thanks for help.
>
> Jason
>
>

log shipping question on two databases

Hi,
I created 2 log shipping plans at the same time, for database dbA and dbB
respectively, to ship logs to antother database server.
All the log transaction schedule and location are the same.
However, only log shipping plan for dbA succeed.
Is there any restriction on log shipping for 2 databases at the same time?
Thanks for help.
JasonNo, there is no such restriction. You can can configure two databases from
the same instance for log shipping.
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Jason Huang" wrote:

> Hi,
> I created 2 log shipping plans at the same time, for database dbA and dbB
> respectively, to ship logs to antother database server.
> All the log transaction schedule and location are the same.
> However, only log shipping plan for dbA succeed.
> Is there any restriction on log shipping for 2 databases at the same time?
> Thanks for help.
>
> Jason
>
>

log shipping question on two databases

Hi,
I created 2 log shipping plans at the same time, for database dbA and dbB
respectively, to ship logs to antother database server.
All the log transaction schedule and location are the same.
However, only log shipping plan for dbA succeed.
Is there any restriction on log shipping for 2 databases at the same time?
Thanks for help.
JasonNo, there is no such restriction. You can can configure two databases from
the same instance for log shipping.
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Jason Huang" wrote:
> Hi,
> I created 2 log shipping plans at the same time, for database dbA and dbB
> respectively, to ship logs to antother database server.
> All the log transaction schedule and location are the same.
> However, only log shipping plan for dbA succeed.
> Is there any restriction on log shipping for 2 databases at the same time?
> Thanks for help.
>
> Jason
>
>