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 with additional backups

I am planning to implement log shipping between two servers.
I understand that if I perform a full database backup of the primary
database during the log shipping, this will have no effect on the log
shipping. If I am log shipping every 30 minutes, so I have a log backup at
09:00 and 09:30, perform a full database backup at 09:15, the log backup at
09:30 will contain all changes from 09:00.
Can I use this full database backup and the log shipping logs to perform a
database recovery? Can I restore the 09:15 full backup and then the 09:30
log? Or, do I need to perform additional log backups, e.g. every hour? If
so, how do these log backups affect the log shipping backups?
Many ThanksYes you can use the log shipping log backups to do a recovery. You will
probably have to look at your log shipping scripts to make sure they are not
deleting the log backup files.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"si" <si@.discussions.microsoft.com> wrote in message
news:819CBAE2-0A90-42BB-8B2B-2B1DFF7DBE05@.microsoft.com...
>I am planning to implement log shipping between two servers.
> I understand that if I perform a full database backup of the primary
> database during the log shipping, this will have no effect on the log
> shipping. If I am log shipping every 30 minutes, so I have a log backup
> at
> 09:00 and 09:30, perform a full database backup at 09:15, the log backup
> at
> 09:30 will contain all changes from 09:00.
> Can I use this full database backup and the log shipping logs to perform a
> database recovery? Can I restore the 09:15 full backup and then the 09:30
> log? Or, do I need to perform additional log backups, e.g. every hour?
> If
> so, how do these log backups affect the log shipping backups?
> Many Thanks

Log Shipping with additional backups

I am planning to implement log shipping between two servers.
I understand that if I perform a full database backup of the primary
database during the log shipping, this will have no effect on the log
shipping. If I am log shipping every 30 minutes, so I have a log backup at
09:00 and 09:30, perform a full database backup at 09:15, the log backup at
09:30 will contain all changes from 09:00.
Can I use this full database backup and the log shipping logs to perform a
database recovery? Can I restore the 09:15 full backup and then the 09:30
log? Or, do I need to perform additional log backups, e.g. every hour? If
so, how do these log backups affect the log shipping backups?
Many ThanksYes you can use the log shipping log backups to do a recovery. You will
probably have to look at your log shipping scripts to make sure they are not
deleting the log backup files.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"si" <si@.discussions.microsoft.com> wrote in message
news:819CBAE2-0A90-42BB-8B2B-2B1DFF7DBE05@.microsoft.com...
>I am planning to implement log shipping between two servers.
> I understand that if I perform a full database backup of the primary
> database during the log shipping, this will have no effect on the log
> shipping. If I am log shipping every 30 minutes, so I have a log backup
> at
> 09:00 and 09:30, perform a full database backup at 09:15, the log backup
> at
> 09:30 will contain all changes from 09:00.
> Can I use this full database backup and the log shipping logs to perform a
> database recovery? Can I restore the 09:15 full backup and then the 09:30
> log? Or, do I need to perform additional log backups, e.g. every hour?
> If
> so, how do these log backups affect the log shipping backups?
> Many Thanks

Log Shipping with additional backups

I am planning to implement log shipping between two servers.
I understand that if I perform a full database backup of the primary
database during the log shipping, this will have no effect on the log
shipping. If I am log shipping every 30 minutes, so I have a log backup at
09:00 and 09:30, perform a full database backup at 09:15, the log backup at
09:30 will contain all changes from 09:00.
Can I use this full database backup and the log shipping logs to perform a
database recovery? Can I restore the 09:15 full backup and then the 09:30
log? Or, do I need to perform additional log backups, e.g. every hour? If
so, how do these log backups affect the log shipping backups?
Many Thanks
Yes you can use the log shipping log backups to do a recovery. You will
probably have to look at your log shipping scripts to make sure they are not
deleting the log backup files.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"si" <si@.discussions.microsoft.com> wrote in message
news:819CBAE2-0A90-42BB-8B2B-2B1DFF7DBE05@.microsoft.com...
>I am planning to implement log shipping between two servers.
> I understand that if I perform a full database backup of the primary
> database during the log shipping, this will have no effect on the log
> shipping. If I am log shipping every 30 minutes, so I have a log backup
> at
> 09:00 and 09:30, perform a full database backup at 09:15, the log backup
> at
> 09:30 will contain all changes from 09:00.
> Can I use this full database backup and the log shipping logs to perform a
> database recovery? Can I restore the 09:15 full backup and then the 09:30
> log? Or, do I need to perform additional log backups, e.g. every hour?
> If
> so, how do these log backups affect the log shipping backups?
> Many Thanks

log shipping will NOT work

I am trying to set up log shipping between some servers. They are in different domain, but there is a two way trust. And I couldn't get it to run inside one domain as well. The SQL agent and SQL server services are running under a domain account that has access to the shares. The jobs actually run but the "last run outcome" remains unknown and the "last run" says never. The error log for these jobs have nothing logged.

Am I missing something here? I have setup and torn this down a million times, and the same thing every time...nothing.

I can also manually backup a log to the Backup share across domains.

Does anyone have a clue what the heck is going on here?

All server are on 9.0.2047.

Thanks,
jason
do you mean to say theres no information in job history ? ? ?.....if the job has run then the sql server agent in either primary or secondary might have been in hanged state........just try to restart the sql server agent and try........anywasys you cud verify if it has run or not by manually logging into the shared folder in primary and see if the tran logs are present........and similarly in secondary check if the tran log files are copied in the secondary servers folder..........else you can check the same in the monitor server which states the recently restored log files in the secondary and the ones which were copied recently and last log file to be backed up in primary|||oh jeez, just a simple restart of the agent did the trick. Thanks for your time.
sql

Log Shipping Transaction Log Question

I am going through a security audit on our servers. We use log shipping
for a standby database. One of the questions in the audit has me
looking for answers.

"Are the transaction logs that are being shipped to the standby
database encrypted?"

I am assuming no. However, I need to know definitively. I have not been
able to find an answer in BOL or in Google. If the logs are not
encrypted, is there an option where I could send them encrypted, if
necessary?

Thanks,
JennieThey're not encrypted - there are a number of 3rd-party products
available which can reconstruct SQL commands from reading transaction
log files. I'm afraid I have no idea whether or not there is a simple
(or even a complex!) way to encrypt/decrypt them, though.|||Hi

If you are worried about encryption over the wire, then you need to do it at
network packet level as all your other traffic is sniffable.

SQL will not encrypt the files, and if you are using the built-in Log
shipping, you can't do it.

If you were to roll your own version of log shipping using scripts, you
could use a 3rd party tool the encrypt it.

Regards
----------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@.epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Phil" <philip.yale@.gmail.com> wrote in message
news:1113571698.710644.115450@.z14g2000cwz.googlegr oups.com...
> They're not encrypted - there are a number of 3rd-party products
> available which can reconstruct SQL commands from reading transaction
> log files. I'm afraid I have no idea whether or not there is a simple
> (or even a complex!) way to encrypt/decrypt them, though.

Log Shipping Role Reversal

I have log shipping configured on a pair of test SQL 2000 servers, both are
at SP3. The log shipping is working fine, but the problem occurs when I try
to reverse roles. I run this SQL statement on the primary server:
USE master
GO
EXEC msdb.dbo.sp_change_primary_role
@.db_name = 'ModelCopy',
@.backup_log = 1,
@.terminate = 1,
@.final_state = 3,
@.access_level = 1
This places the primary database into read-only mode. I then run this SQL
statement on the secondary server.
USE master
GO
EXEC msdb.dbo.sp_change_secondary_role
@.db_name = 'ModelCopy',
@.do_load = 1,
@.force_load = 1,
@.final_state = 1,
@.access_level = 1,
@.terminate = 1,
@.keep_replication = 0,
@.stopat = null
At which time I get this error:
Server: Msg 927, Level 14, State 2, Line 1
Database 'ModelCopy' cannot be opened. It is in the middle of a restore.
Server: Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
Server: Msg 14440, Level 16, State 1, Procedure sp_change_secondary_role,
Line 49
Could not set single user mode.
In each case, I am runnig the statements in Query Analyzer with the
Enterprise Manager window closed. I understand that these statements cause
the primary to make a final copy and the secondary to do a final restore, but
the database I'm using is very small (a copy of the Model databae) and
shouldn't take but a few seconds, which is all the time it took to create and
initialize the database on the secondary to begin with. Is this process hung,
or am I just being impatient? It's been over 20 minutes.
TIA,
Ken
Ken,
See the KB article 294397 BUG: sp_change_secondary_role Fails with Error
3101 if There Are Outstanding Transaction Log Backups
http://support.microsoft.com/default...&Product=sql2k
This is similar, though not identical, to the error you are getting. The
upshot is that you need to make sure that all the transaction logs have been
restored if you set the @.terminate parameter to 1.
Hope this helps,
Ron
Ron Talmage
SQL Server MVP
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:733456B1-BC99-43B2-B6BD-4030A08DB6EC@.microsoft.com...
> I have log shipping configured on a pair of test SQL 2000 servers, both
are
> at SP3. The log shipping is working fine, but the problem occurs when I
try
> to reverse roles. I run this SQL statement on the primary server:
> USE master
> GO
> EXEC msdb.dbo.sp_change_primary_role
> @.db_name = 'ModelCopy',
> @.backup_log = 1,
> @.terminate = 1,
> @.final_state = 3,
> @.access_level = 1
> This places the primary database into read-only mode. I then run this SQL
> statement on the secondary server.
> USE master
> GO
> EXEC msdb.dbo.sp_change_secondary_role
> @.db_name = 'ModelCopy',
> @.do_load = 1,
> @.force_load = 1,
> @.final_state = 1,
> @.access_level = 1,
> @.terminate = 1,
> @.keep_replication = 0,
> @.stopat = null
> At which time I get this error:
> Server: Msg 927, Level 14, State 2, Line 1
> Database 'ModelCopy' cannot be opened. It is in the middle of a restore.
> Server: Msg 5069, Level 16, State 1, Line 1
> ALTER DATABASE statement failed.
> Server: Msg 14440, Level 16, State 1, Procedure sp_change_secondary_role,
> Line 49
> Could not set single user mode.
> In each case, I am runnig the statements in Query Analyzer with the
> Enterprise Manager window closed. I understand that these statements cause
> the primary to make a final copy and the secondary to do a final restore,
but
> the database I'm using is very small (a copy of the Model databae) and
> shouldn't take but a few seconds, which is all the time it took to create
and
> initialize the database on the secondary to begin with. Is this process
hung,
> or am I just being impatient? It's been over 20 minutes.
> TIA,
> Ken
|||Thanks for the info Ron. It pointed me in the right direction. I still needed
to to a detach/attach sequesnce on the database before running the secondary
stored procedure, but at least it is working in a predictable manner now.
"Ron Talmage" wrote:

> Ken,
> See the KB article 294397 BUG: sp_change_secondary_role Fails with Error
> 3101 if There Are Outstanding Transaction Log Backups
> http://support.microsoft.com/default...&Product=sql2k
> This is similar, though not identical, to the error you are getting. The
> upshot is that you need to make sure that all the transaction logs have been
> restored if you set the @.terminate parameter to 1.
> Hope this helps,
> Ron
> --
> Ron Talmage
> SQL Server MVP
> "kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
> news:733456B1-BC99-43B2-B6BD-4030A08DB6EC@.microsoft.com...
> are
> try
> but
> and
> hung,
>
>
|||OK, I spoke too soon. Occasionally, the sp_change_secondary_role procedure
will end with a "sqlmaint.exe failed. [SQLSTATE 42000][Error 22029]. The step
failed." message. I haven't been able to find any helpful information on this
message yet. Can you shed some more light on what is happening during this
procedure? Same scripts as posted previously in this thread, and include the
manual running of the restore job and a database detach/attach sequence in
Enterprise Manager immediately prior to running the secondary role change
stpred procedure.
Thanks Again,
Ken
"kmkrause2" wrote:
[vbcol=seagreen]
> Thanks for the info Ron. It pointed me in the right direction. I still needed
> to to a detach/attach sequesnce on the database before running the secondary
> stored procedure, but at least it is working in a predictable manner now.
> "Ron Talmage" wrote:

Log Shipping Restore Failed - How do I find out why?

I set up log shipping for a database to fire every 10 mins. All the steps on
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServer
Even I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:

> I set up log shipping for a database to fire every 10 mins. All the steps on
> both servers work the first two times. On the 3rd 10 min interval, the log
> bkp is created on the source server and is copied to the destination server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer

Log Shipping Restore Failed - How do I find out why?

I set up log shipping for a database to fire every 10 mins. All the steps o
n
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more
.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServerEven I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:

> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the lo
g
> bkp is created on the source server and is copied to the destination serve
r.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any mo
re.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
--
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer

Log Shipping Restore Failed - How do I find out why?

I set up log shipping for a database to fire every 10 mins. All the steps on
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
--
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServerEven I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:
> I set up log shipping for a database to fire every 10 mins. All the steps on
> both servers work the first two times. On the 3rd 10 min interval, the log
> bkp is created on the source server and is copied to the destination server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
--
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer

Log shipping recover

I have changed the roles of primary and secondary servers due to server failure.
Can anyone advise how to revert back to previous main server? Are these any links available?See BOL topic:
How to set up and perform a log shipping role change (Transact-SQL)

In couple words - you have to set up log shipping again (move last backup from secondary to primary with stopping any activity of course on first one).|||If I set up log shipping with the old server, it becomes secondary. But I want to make my old server primary again.

Would I need to copy the db from current primary to old primary server, switch off the current server and switch on the old one?

Log Shipping Question: reset copy delta

SQL Server 2000 on both servers. Log shipping between them.
We had to reboot the primary server and now the trn files are not
being copied to the secondary server.
In the past when this happened, we manually copied the files from
primary to secondary and then ran the upload job on the secondary
server. The copy delta would then reset at some point (usually
overnight).
This time after I have copied the files and uploaded them, the copy
delta has not reset and now stands at 5415 minutes. The Load delta is
at 0 minutes currently.
Is there a way to force the copy delta to update itself because all
the trn files now have been loaded?
If there isn't I will have to run the wizard to create the log
shipping plans again for all four of our databases.
Regards
Nicko
Hi
What does mean 'copy delta'?
http://www.sql-server-performance.com/sql_server_log_shipping.asp
<nickostle@.hotmail.com> wrote in message
news:1179713332.252623.51410@.z28g2000prd.googlegro ups.com...
> SQL Server 2000 on both servers. Log shipping between them.
> We had to reboot the primary server and now the trn files are not
> being copied to the secondary server.
> In the past when this happened, we manually copied the files from
> primary to secondary and then ran the upload job on the secondary
> server. The copy delta would then reset at some point (usually
> overnight).
> This time after I have copied the files and uploaded them, the copy
> delta has not reset and now stands at 5415 minutes. The Load delta is
> at 0 minutes currently.
> Is there a way to force the copy delta to update itself because all
> the trn files now have been loaded?
> If there isn't I will have to run the wizard to create the log
> shipping plans again for all four of our databases.
> Regards
> Nicko
>
|||Copy Delta is the time dfference between when it says the last file
was copied to the present time on the server.
sql

Log Shipping Question: reset copy delta

SQL Server 2000 on both servers. Log shipping between them.
We had to reboot the primary server and now the trn files are not
being copied to the secondary server.
In the past when this happened, we manually copied the files from
primary to secondary and then ran the upload job on the secondary
server. The copy delta would then reset at some point (usually
overnight).
This time after I have copied the files and uploaded them, the copy
delta has not reset and now stands at 5415 minutes. The Load delta is
at 0 minutes currently.
Is there a way to force the copy delta to update itself because all
the trn files now have been loaded?
If there isn't I will have to run the wizard to create the log
shipping plans again for all four of our databases.
Regards
NickoHi
What does mean 'copy delta'?
http://www.sql-server-performance.c...og_shipping.asp
<nickostle@.hotmail.com> wrote in message
news:1179713332.252623.51410@.z28g2000prd.googlegroups.com...
> SQL Server 2000 on both servers. Log shipping between them.
> We had to reboot the primary server and now the trn files are not
> being copied to the secondary server.
> In the past when this happened, we manually copied the files from
> primary to secondary and then ran the upload job on the secondary
> server. The copy delta would then reset at some point (usually
> overnight).
> This time after I have copied the files and uploaded them, the copy
> delta has not reset and now stands at 5415 minutes. The Load delta is
> at 0 minutes currently.
> Is there a way to force the copy delta to update itself because all
> the trn files now have been loaded?
> If there isn't I will have to run the wizard to create the log
> shipping plans again for all four of our databases.
> Regards
> Nicko
>|||Copy Delta is the time dfference between when it says the last file
was copied to the present time on the server.

Log Shipping Question: reset copy delta

SQL Server 2000 on both servers. Log shipping between them.
We had to reboot the primary server and now the trn files are not
being copied to the secondary server.
In the past when this happened, we manually copied the files from
primary to secondary and then ran the upload job on the secondary
server. The copy delta would then reset at some point (usually
overnight).
This time after I have copied the files and uploaded them, the copy
delta has not reset and now stands at 5415 minutes. The Load delta is
at 0 minutes currently.
Is there a way to force the copy delta to update itself because all
the trn files now have been loaded?
If there isn't I will have to run the wizard to create the log
shipping plans again for all four of our databases.
Regards
NickoHi
What does mean 'copy delta'?
http://www.sql-server-performance.com/sql_server_log_shipping.asp
<nickostle@.hotmail.com> wrote in message
news:1179713332.252623.51410@.z28g2000prd.googlegroups.com...
> SQL Server 2000 on both servers. Log shipping between them.
> We had to reboot the primary server and now the trn files are not
> being copied to the secondary server.
> In the past when this happened, we manually copied the files from
> primary to secondary and then ran the upload job on the secondary
> server. The copy delta would then reset at some point (usually
> overnight).
> This time after I have copied the files and uploaded them, the copy
> delta has not reset and now stands at 5415 minutes. The Load delta is
> at 0 minutes currently.
> Is there a way to force the copy delta to update itself because all
> the trn files now have been loaded?
> If there isn't I will have to run the wizard to create the log
> shipping plans again for all four of our databases.
> Regards
> Nicko
>|||Copy Delta is the time dfference between when it says the last file
was copied to the present time on the server.

Log shipping question.

Hi all,
I have a question about the scheduling of different backup types under log
shipping. Let's say I have two servers, ServerA and ServerB, and there's
one database called DatabaseA that exists on both servers. Imagine that I
have it setup so that a full backup is generated every day at midnight,
differential backups every hour, and a transaction log every 15 minutes.
These are copied over to ServerB, and restored into the database as they
come in. Thus, my database on ServerB is (at most) about 15 minutes behind.
Question: is there any advantage, given this scenario, to doing the full
backup every night versus once a week? For that matter, why even do the
differentials every hour? What if I changed it to do the full backup once a
week, differentials once a day, and kept generating the transaction logs
every 15 minutes?
It seems to me that, so long as I keep the transaction logs in order and
restore them as they are deposited on ServerB, my data would be just as
up-to-date as if I did the full and differentials more often -- plus, I'd be
generating less network traffic, which is a bonus in my scenario.
I'd appreciate any thoughts or observations ...
Thanks for the help!
WadeWade (wwegner23NOEMAILhotmail.com) writes:
> I have a question about the scheduling of different backup types under
> log shipping. Let's say I have two servers, ServerA and ServerB, and
> there's one database called DatabaseA that exists on both servers.
> Imagine that I have it setup so that a full backup is generated every
> day at midnight, differential backups every hour, and a transaction log
> every 15 minutes. These are copied over to ServerB, and restored into
> the database as they come in. Thus, my database on ServerB is (at most)
> about 15 minutes behind.
> Question: is there any advantage, given this scenario, to doing the full
> backup every night versus once a week? For that matter, why even do the
> differentials every hour? What if I changed it to do the full backup
> once a week, differentials once a day, and kept generating the
> transaction logs every 15 minutes?
Others have more experience of setting backup schedules than I have, but I
would keep the nightly full backup and the log backups, but skip the
differential backups.
One thing of interest here is how far ServerA and ServerB are from each
other. Are they on different sides of town, or in the same computer room?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||Hi
You did not state your DB size, but running differentials every hours seems
a bit much to me.
Most people use the:
Full one per week
Differential once per day
Transaction log every 15 minutes.
For a restore, you need your last full backup, the most recent differential
and the transaction logs after the differential to the point in time.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message
news:ON3vTRNrFHA.1128@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a question about the scheduling of different backup types under log
> shipping. Let's say I have two servers, ServerA and ServerB, and there's
> one database called DatabaseA that exists on both servers. Imagine that I
> have it setup so that a full backup is generated every day at midnight,
> differential backups every hour, and a transaction log every 15 minutes.
> These are copied over to ServerB, and restored into the database as they
> come in. Thus, my database on ServerB is (at most) about 15 minutes
> behind.
> Question: is there any advantage, given this scenario, to doing the full
> backup every night versus once a week? For that matter, why even do the
> differentials every hour? What if I changed it to do the full backup once
> a week, differentials once a day, and kept generating the transaction logs
> every 15 minutes?
> It seems to me that, so long as I keep the transaction logs in order and
> restore them as they are deposited on ServerB, my data would be just as
> up-to-date as if I did the full and differentials more often -- plus, I'd
> be generating less network traffic, which is a bonus in my scenario.
> I'd appreciate any thoughts or observations ...
> Thanks for the help!
> Wade
>|||Thanks, Mike.
> You did not state your DB size, but running differentials every hours
> seems a bit much to me.
The sizes are all over the place -- 20 MBytes to 2.7 GBytes. Obviously, if
there's not really a reason to do the fulls more often (which is what it
appears like ...), then the less frequenct the backups occur the better.
> Most people use the:
> Full one per week
> Differential once per day
> Transaction log every 15 minutes.
Yes, exactly what I stated.
> For a restore, you need your last full backup, the most recent
> differential and the transaction logs after the differential to the point
> in time.
... thanks.
Wade|||> Others have more experience of setting backup schedules than I have, but I
> would keep the nightly full backup and the log backups, but skip the
> differential backups.
I've thought of that too ... but, it seems like having the diffs is a good
catch, because if something happens and the LSN #'s get out of sequence with
the transaction logs (which has happened to me in testing, although I think
I have that resolved) the differential backups can usually clean it up.
> One thing of interest here is how far ServerA and ServerB are from each
> other. Are they on different sides of town, or in the same computer room?
Denver, CO --> Reston, VA. We have a 1 megabit pipe that we're replicating
data over. Perhaps I should have added a bit more of the real world into
the question. :)
Thanks,
Wade|||Wade (wwegner23NOEMAILhotmail.com) writes:
>> One thing of interest here is how far ServerA and ServerB are from each
>> other. Are they on different sides of town, or in the same computer room?
> Denver, CO --> Reston, VA. We have a 1 megabit pipe that we're
> replicating data over. Perhaps I should have added a bit more of the
> real world into the question. :)
That's good. It has to be pretty bug disaster that wipes out both.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||God forbid.
So ... kind sounds like there's no reason to backup anymore than the
following
Full: 1 / week
Diff: 1 / day
Tran: Every 15 minutes
Sound good?
Thanks!
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns96C2811C71153Yazorman@.127.0.0.1...
> Wade (wwegner23NOEMAILhotmail.com) writes:
>> One thing of interest here is how far ServerA and ServerB are from each
>> other. Are they on different sides of town, or in the same computer
>> room?
>> Denver, CO --> Reston, VA. We have a 1 megabit pipe that we're
>> replicating data over. Perhaps I should have added a bit more of the
>> real world into the question. :)
> That's good. It has to be pretty bug disaster that wipes out both.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
>

Log shipping question.

Hi all,
I have a question about the scheduling of different backup types under log
shipping. Let's say I have two servers, ServerA and ServerB, and there's
one database called DatabaseA that exists on both servers. Imagine that I
have it setup so that a full backup is generated every day at midnight,
differential backups every hour, and a transaction log every 15 minutes.
These are copied over to ServerB, and restored into the database as they
come in. Thus, my database on ServerB is (at most) about 15 minutes behind.
Question: is there any advantage, given this scenario, to doing the full
backup every night versus once a week? For that matter, why even do the
differentials every hour? What if I changed it to do the full backup once a
week, differentials once a day, and kept generating the transaction logs
every 15 minutes?
It seems to me that, so long as I keep the transaction logs in order and
restore them as they are deposited on ServerB, my data would be just as
up-to-date as if I did the full and differentials more often -- plus, I'd be
generating less network traffic, which is a bonus in my scenario.
I'd appreciate any thoughts or observations ...
Thanks for the help!
Wade
Wade (wwegner23NOEMAILhotmail.com) writes:
> I have a question about the scheduling of different backup types under
> log shipping. Let's say I have two servers, ServerA and ServerB, and
> there's one database called DatabaseA that exists on both servers.
> Imagine that I have it setup so that a full backup is generated every
> day at midnight, differential backups every hour, and a transaction log
> every 15 minutes. These are copied over to ServerB, and restored into
> the database as they come in. Thus, my database on ServerB is (at most)
> about 15 minutes behind.
> Question: is there any advantage, given this scenario, to doing the full
> backup every night versus once a week? For that matter, why even do the
> differentials every hour? What if I changed it to do the full backup
> once a week, differentials once a day, and kept generating the
> transaction logs every 15 minutes?
Others have more experience of setting backup schedules than I have, but I
would keep the nightly full backup and the log backups, but skip the
differential backups.
One thing of interest here is how far ServerA and ServerB are from each
other. Are they on different sides of town, or in the same computer room?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
|||Hi
You did not state your DB size, but running differentials every hours seems
a bit much to me.
Most people use the:
Full one per week
Differential once per day
Transaction log every 15 minutes.
For a restore, you need your last full backup, the most recent differential
and the transaction logs after the differential to the point in time.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message
news:ON3vTRNrFHA.1128@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a question about the scheduling of different backup types under log
> shipping. Let's say I have two servers, ServerA and ServerB, and there's
> one database called DatabaseA that exists on both servers. Imagine that I
> have it setup so that a full backup is generated every day at midnight,
> differential backups every hour, and a transaction log every 15 minutes.
> These are copied over to ServerB, and restored into the database as they
> come in. Thus, my database on ServerB is (at most) about 15 minutes
> behind.
> Question: is there any advantage, given this scenario, to doing the full
> backup every night versus once a week? For that matter, why even do the
> differentials every hour? What if I changed it to do the full backup once
> a week, differentials once a day, and kept generating the transaction logs
> every 15 minutes?
> It seems to me that, so long as I keep the transaction logs in order and
> restore them as they are deposited on ServerB, my data would be just as
> up-to-date as if I did the full and differentials more often -- plus, I'd
> be generating less network traffic, which is a bonus in my scenario.
> I'd appreciate any thoughts or observations ...
> Thanks for the help!
> Wade
>
|||Thanks, Mike.

> You did not state your DB size, but running differentials every hours
> seems a bit much to me.
The sizes are all over the place -- 20 MBytes to 2.7 GBytes. Obviously, if
there's not really a reason to do the fulls more often (which is what it
appears like ...), then the less frequenct the backups occur the better.

> Most people use the:
> Full one per week
> Differential once per day
> Transaction log every 15 minutes.
Yes, exactly what I stated.

> For a restore, you need your last full backup, the most recent
> differential and the transaction logs after the differential to the point
> in time.
... thanks.
Wade
|||> Others have more experience of setting backup schedules than I have, but I
> would keep the nightly full backup and the log backups, but skip the
> differential backups.
I've thought of that too ... but, it seems like having the diffs is a good
catch, because if something happens and the LSN #'s get out of sequence with
the transaction logs (which has happened to me in testing, although I think
I have that resolved) the differential backups can usually clean it up.

> One thing of interest here is how far ServerA and ServerB are from each
> other. Are they on different sides of town, or in the same computer room?
Denver, CO --> Reston, VA. We have a 1 megabit pipe that we're replicating
data over. Perhaps I should have added a bit more of the real world into
the question.
Thanks,
Wade
|||Wade (wwegner23NOEMAILhotmail.com) writes:
> Denver, CO --> Reston, VA. We have a 1 megabit pipe that we're
> replicating data over. Perhaps I should have added a bit more of the
> real world into the question.
That's good. It has to be pretty bug disaster that wipes out both.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
|||God forbid.
So ... kind sounds like there's no reason to backup anymore than the
following
Full: 1 / week
Diff: 1 / day
Tran: Every 15 minutes
Sound good?
Thanks!
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns96C2811C71153Yazorman@.127.0.0.1...
> Wade (wwegner23NOEMAILhotmail.com) writes:
> That's good. It has to be pretty bug disaster that wipes out both.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinf...2000/books.asp
>

Log shipping question.

Hi all,
I have a question about the scheduling of different backup types under log
shipping. Let's say I have two servers, ServerA and ServerB, and there's
one database called DatabaseA that exists on both servers. Imagine that I
have it setup so that a full backup is generated every day at midnight,
differential backups every hour, and a transaction log every 15 minutes.
These are copied over to ServerB, and restored into the database as they
come in. Thus, my database on ServerB is (at most) about 15 minutes behind.
Question: is there any advantage, given this scenario, to doing the full
backup every night versus once a week? For that matter, why even do the
differentials every hour? What if I changed it to do the full backup once a
week, differentials once a day, and kept generating the transaction logs
every 15 minutes?
It seems to me that, so long as I keep the transaction logs in order and
restore them as they are deposited on ServerB, my data would be just as
up-to-date as if I did the full and differentials more often -- plus, I'd be
generating less network traffic, which is a bonus in my scenario.
I'd appreciate any thoughts or observations ...
Thanks for the help!
WadeWade (wwegner23NOEMAILhotmail.com) writes:
> I have a question about the scheduling of different backup types under
> log shipping. Let's say I have two servers, ServerA and ServerB, and
> there's one database called DatabaseA that exists on both servers.
> Imagine that I have it setup so that a full backup is generated every
> day at midnight, differential backups every hour, and a transaction log
> every 15 minutes. These are copied over to ServerB, and restored into
> the database as they come in. Thus, my database on ServerB is (at most)
> about 15 minutes behind.
> Question: is there any advantage, given this scenario, to doing the full
> backup every night versus once a week? For that matter, why even do the
> differentials every hour? What if I changed it to do the full backup
> once a week, differentials once a day, and kept generating the
> transaction logs every 15 minutes?
Others have more experience of setting backup schedules than I have, but I
would keep the nightly full backup and the log backups, but skip the
differential backups.
One thing of interest here is how far ServerA and ServerB are from each
other. Are they on different sides of town, or in the same computer room?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Hi
You did not state your DB size, but running differentials every hours seems
a bit much to me.
Most people use the:
Full one per week
Differential once per day
Transaction log every 15 minutes.
For a restore, you need your last full backup, the most recent differential
and the transaction logs after the differential to the point in time.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message
news:ON3vTRNrFHA.1128@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a question about the scheduling of different backup types under log
> shipping. Let's say I have two servers, ServerA and ServerB, and there's
> one database called DatabaseA that exists on both servers. Imagine that I
> have it setup so that a full backup is generated every day at midnight,
> differential backups every hour, and a transaction log every 15 minutes.
> These are copied over to ServerB, and restored into the database as they
> come in. Thus, my database on ServerB is (at most) about 15 minutes
> behind.
> Question: is there any advantage, given this scenario, to doing the full
> backup every night versus once a week? For that matter, why even do the
> differentials every hour? What if I changed it to do the full backup once
> a week, differentials once a day, and kept generating the transaction logs
> every 15 minutes?
> It seems to me that, so long as I keep the transaction logs in order and
> restore them as they are deposited on ServerB, my data would be just as
> up-to-date as if I did the full and differentials more often -- plus, I'd
> be generating less network traffic, which is a bonus in my scenario.
> I'd appreciate any thoughts or observations ...
> Thanks for the help!
> Wade
>|||Thanks, Mike.

> You did not state your DB size, but running differentials every hours
> seems a bit much to me.
The sizes are all over the place -- 20 MBytes to 2.7 GBytes. Obviously, if
there's not really a reason to do the fulls more often (which is what it
appears like ...), then the less frequenct the backups occur the better.

> Most people use the:
> Full one per week
> Differential once per day
> Transaction log every 15 minutes.
Yes, exactly what I stated.

> For a restore, you need your last full backup, the most recent
> differential and the transaction logs after the differential to the point
> in time.
... thanks.
Wade|||> Others have more experience of setting backup schedules than I have, but I
> would keep the nightly full backup and the log backups, but skip the
> differential backups.
I've thought of that too ... but, it seems like having the diffs is a good
catch, because if something happens and the LSN #'s get out of sequence with
the transaction logs (which has happened to me in testing, although I think
I have that resolved) the differential backups can usually clean it up.

> One thing of interest here is how far ServerA and ServerB are from each
> other. Are they on different sides of town, or in the same computer room?
Denver, CO --> Reston, VA. We have a 1 megabit pipe that we're replicating
data over. Perhaps I should have added a bit more of the real world into
the question.
Thanks,
Wade|||Wade (wwegner23NOEMAILhotmail.com) writes:
> Denver, CO --> Reston, VA. We have a 1 megabit pipe that we're
> replicating data over. Perhaps I should have added a bit more of the
> real world into the question.
That's good. It has to be pretty bug disaster that wipes out both.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||God forbid.
So ... kind sounds like there's no reason to backup anymore than the
following
Full: 1 / week
Diff: 1 / day
Tran: Every 15 minutes
Sound good?
Thanks!
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns96C2811C71153Yazorman@.127.0.0.1...
> Wade (wwegner23NOEMAILhotmail.com) writes:
> That's good. It has to be pretty bug disaster that wipes out both.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp
>sql

Log Shipping Question

Hello,
I want to setup SQL Log Shipping btwn two servers.
- Do the servers have to run same version of Windows? Can one be Win2003 and
the other Win2K Server? Or one Win2k Advanced and one Win2k Standard Server?
- Do I have to run the same version/build/ServicePack of SQL Server?
many thanks
christos
If you are using the Enterprise Edition of SQL Server's Log Shipping
functions both SQL Server's have to be Enterprise Edition. If you are
rolling your own version of Log Shipping, there are no SQL Server version
requirements or OS requirements (other than NT workstation/server, XP
professional, Win2k server/professional, Windows 2003).
"Christos Kritikos" <ChristosKritikos@.discussions.microsoft.com> wrote in
message news:D025AB19-599D-4806-9817-2804C182F38A@.microsoft.com...
> Hello,
> I want to setup SQL Log Shipping btwn two servers.
> - Do the servers have to run same version of Windows? Can one be Win2003
and
> the other Win2K Server? Or one Win2k Advanced and one Win2k Standard
Server?
> - Do I have to run the same version/build/ServicePack of SQL Server?
> many thanks
> christos
>