log shipping restore fail

We've been experiencing above average "Log Shipping
Restore" fails. All copy and restore can be worked for
first two or three times. For no apparent reason, the job
of log shipping restore fails. I checked the windows event
viewer,the message is "SQL Server Scheduled Job 'Log
Shipping Restore for Test2.NorthwindCopy_logshipping'
(0x63382D0A9860D541B191C36DCB658480) - Status: Failed -
Invoked on: 2003-10-31 12:30:00 - Message: The job
failed. The Job was invoked by Schedule 12 (Schedule 1).
The last step to run was step 1 (Log Shipping Restore)."
I'm sure that disk space and netowkr access isn't an issue
and the secondary server isn't busy.Anyone knows what
might cause this .Thanks.Are users accessing the database at the time of failure?
Can you run the restore command yourself? Does it work?
You can get more information regarding log shipping here:
http://sqlguy.home.comcast.net/logship.htm
-- Keith
"kelly" <kelly_lu@.kingston.com.tw> wrote in message =news:45bd01c39f73$9f9f2b90$7d02280a@.phx.gbl...
> We've been experiencing above average "Log Shipping > Restore" fails. All copy and restore can be worked for > first two or three times. For no apparent reason, the job > of log shipping restore fails. I checked the windows event > viewer,the message is "SQL Server Scheduled Job 'Log > Shipping Restore for Test2.NorthwindCopy_logshipping' > (0x63382D0A9860D541B191C36DCB658480) - Status: Failed - > Invoked on: 2003-10-31 12:30:00 - Message: The job > failed. The Job was invoked by Schedule 12 (Schedule 1). > The last step to run was step 1 (Log Shipping Restore)."
> I'm sure that disk space and netowkr access isn't an issue > and the secondary server isn't busy.Anyone knows what > might cause this .Thanks. >

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 initial backup restore

hi,
sql2000 enterprise edi. Planning for 15 min log shipping .
database size is around 6 gb. took the full backup and try to copy to the
secondary server over the network taking too much of time (say .5mb/sec).
meanwhile i stoped the transaction log backup . because the full backup is
not restored in the secondary server. my question is , ' can i restore log
backups after the full backup restore on secondary to make sync. ? then start
the log shipping process? or peer to peer connection needed in between
primary and secondary?
2) Another question : after the reindex process, the log file size will be
similar to dbsize. so transafering the log file over the network will take
take and log shipping may break because of copy time? how can i handle this?
thanks
Hello
I had a quick question - Did you start the file copy process for your
Complete backup through the Log Shipping Setup wizard?
Assuming that you did not, then regarding your first question :
You can actually perform the transaction log backups on your primary server
while the complete backup is copying over.
1. Once the complete backup is finished copying, start the restore of this
complete backup in NORECOVERY mode and in the meantime start copying over
the transaction log backups.
2. When the restore of the complete backup is complete, start applying the
transaction logs with NORECOVERY option.
3. At some point, stop performing transaction log backups on your primary
server and complete copying/restoring the transaction log backups on the
secondary server.
4. Once the secondary database is ready, start the Log Shipping Setup
Wizard (through the Maintenance Plan) and on the Log Shipping secondary
dialog, select Existing database option and select the NORECOVERY database
that you have created in steps earlier. Selecting this option will prevent
the Wizard from actually initiating a copy/load of the complete backup
during setup.
Regarding your second question:
Since rebuilding an index is a logged operation, there is no way for you to
get around this problem. The only way you can avoid this is by
reinitializing log shipping which is going to be more time consuming. Think
of this process as "keeping your secondary database in complete sync with
your primary". Assume for a second that as soon as you've finished
restoring the large transaction log backup (performed after the index
rebuild operation) to the secondary standby database, your primary database
goes offline. At this point since you have to bring the secondary online,
you would expect it to perform just as fast as your primary (given all
other factors including hardware etc are the same between the 2 machines).
Well if there was a way for you to avoid transferring the info related to
index rebuild to the secondary, the performance on your secondary most
likely would be very slow since there were no index updates performed on it.
Let me know if you have further questions.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||pankaj,
Thanks for you suggestion.
I took the full backup and copied over the network to the standby server,
before starting Logshipping process Setup. But it was very slow. For setting
up logshipping for production environment, i dont want any sync problems
like copying delay and restore log after the reindex process. I want to
know that whether i missed something.
I am thinking of adding one more NIC to my production server to connect to
the standby to improve the copy process.
"Pankaj Agarwal [MSFT]" <pankaja@.online.microsoft.com> wrote in message
news:k0XK9CVkEHA.2656@.cpmsftngxa10.phx.gbl...
> Hello
> I had a quick question - Did you start the file copy process for your
> Complete backup through the Log Shipping Setup wizard?
> Assuming that you did not, then regarding your first question :
> You can actually perform the transaction log backups on your primary
server
> while the complete backup is copying over.
> 1. Once the complete backup is finished copying, start the restore of this
> complete backup in NORECOVERY mode and in the meantime start copying over
> the transaction log backups.
> 2. When the restore of the complete backup is complete, start applying the
> transaction logs with NORECOVERY option.
> 3. At some point, stop performing transaction log backups on your primary
> server and complete copying/restoring the transaction log backups on the
> secondary server.
> 4. Once the secondary database is ready, start the Log Shipping Setup
> Wizard (through the Maintenance Plan) and on the Log Shipping secondary
> dialog, select Existing database option and select the NORECOVERY database
> that you have created in steps earlier. Selecting this option will prevent
> the Wizard from actually initiating a copy/load of the complete backup
> during setup.
> Regarding your second question:
> Since rebuilding an index is a logged operation, there is no way for you
to
> get around this problem. The only way you can avoid this is by
> reinitializing log shipping which is going to be more time consuming.
Think
> of this process as "keeping your secondary database in complete sync with
> your primary". Assume for a second that as soon as you've finished
> restoring the large transaction log backup (performed after the index
> rebuild operation) to the secondary standby database, your primary
database
> goes offline. At this point since you have to bring the secondary online,
> you would expect it to perform just as fast as your primary (given all
> other factors including hardware etc are the same between the 2 machines).
> Well if there was a way for you to avoid transferring the info related to
> index rebuild to the secondary, the performance on your secondary most
> likely would be very slow since there were no index updates performed on
it.
> Let me know if you have further questions.
> Thank you for using Microsoft newsgroups.
> Sincerely
> Pankaj Agarwal
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
|||Unfortunately there is no way to get around the large transaction log when
you are performing index rebuild. If you feel that adding another NIC will
provide better bandwidth and hence faster copy, then that may be something
to consider.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

log shipping initial backup restore

hi,
sql2000 enterprise edi. Planning for 15 min log shipping .
database size is around 6 gb. took the full backup and try to copy to the
secondary server over the network taking too much of time (say .5mb/sec).
meanwhile i stoped the transaction log backup . because the full backup is
not restored in the secondary server. my question is , ' can i restore log
backups after the full backup restore on secondary to make sync. ? then star
t
the log shipping process? or peer to peer connection needed in between
primary and secondary?
2) Another question : after the reindex process, the log file size will be
similar to dbsize. so transafering the log file over the network will take
take and log shipping may break because of copy time? how can i handle this
?
thanksHello
I had a quick question - Did you start the file copy process for your
Complete backup through the Log Shipping Setup wizard?
Assuming that you did not, then regarding your first question :
You can actually perform the transaction log backups on your primary server
while the complete backup is copying over.
1. Once the complete backup is finished copying, start the restore of this
complete backup in NORECOVERY mode and in the meantime start copying over
the transaction log backups.
2. When the restore of the complete backup is complete, start applying the
transaction logs with NORECOVERY option.
3. At some point, stop performing transaction log backups on your primary
server and complete copying/restoring the transaction log backups on the
secondary server.
4. Once the secondary database is ready, start the Log Shipping Setup
Wizard (through the Maintenance Plan) and on the Log Shipping secondary
dialog, select Existing database option and select the NORECOVERY database
that you have created in steps earlier. Selecting this option will prevent
the Wizard from actually initiating a copy/load of the complete backup
during setup.
Regarding your second question:
Since rebuilding an index is a logged operation, there is no way for you to
get around this problem. The only way you can avoid this is by
reinitializing log shipping which is going to be more time consuming. Think
of this process as "keeping your secondary database in complete sync with
your primary". Assume for a second that as soon as you've finished
restoring the large transaction log backup (performed after the index
rebuild operation) to the secondary standby database, your primary database
goes offline. At this point since you have to bring the secondary online,
you would expect it to perform just as fast as your primary (given all
other factors including hardware etc are the same between the 2 machines).
Well if there was a way for you to avoid transferring the info related to
index rebuild to the secondary, the performance on your secondary most
likely would be very slow since there were no index updates performed on it.
Let me know if you have further questions.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||pankaj,
Thanks for you suggestion.
I took the full backup and copied over the network to the standby server,
before starting Logshipping process Setup. But it was very slow. For setting
up logshipping for production environment, i dont want any sync problems
like copying delay and restore log after the reindex process. I want to
know that whether i missed something.
I am thinking of adding one more NIC to my production server to connect to
the standby to improve the copy process.
"Pankaj Agarwal [MSFT]" <pankaja@.online.microsoft.com> wrote in message
news:k0XK9CVkEHA.2656@.cpmsftngxa10.phx.gbl...
> Hello
> I had a quick question - Did you start the file copy process for your
> Complete backup through the Log Shipping Setup wizard?
> Assuming that you did not, then regarding your first question :
> You can actually perform the transaction log backups on your primary
server
> while the complete backup is copying over.
> 1. Once the complete backup is finished copying, start the restore of this
> complete backup in NORECOVERY mode and in the meantime start copying over
> the transaction log backups.
> 2. When the restore of the complete backup is complete, start applying the
> transaction logs with NORECOVERY option.
> 3. At some point, stop performing transaction log backups on your primary
> server and complete copying/restoring the transaction log backups on the
> secondary server.
> 4. Once the secondary database is ready, start the Log Shipping Setup
> Wizard (through the Maintenance Plan) and on the Log Shipping secondary
> dialog, select Existing database option and select the NORECOVERY database
> that you have created in steps earlier. Selecting this option will prevent
> the Wizard from actually initiating a copy/load of the complete backup
> during setup.
> Regarding your second question:
> Since rebuilding an index is a logged operation, there is no way for you
to
> get around this problem. The only way you can avoid this is by
> reinitializing log shipping which is going to be more time consuming.
Think
> of this process as "keeping your secondary database in complete sync with
> your primary". Assume for a second that as soon as you've finished
> restoring the large transaction log backup (performed after the index
> rebuild operation) to the secondary standby database, your primary
database
> goes offline. At this point since you have to bring the secondary online,
> you would expect it to perform just as fast as your primary (given all
> other factors including hardware etc are the same between the 2 machines).
> Well if there was a way for you to avoid transferring the info related to
> index rebuild to the secondary, the performance on your secondary most
> likely would be very slow since there were no index updates performed on
it.
> Let me know if you have further questions.
> Thank you for using Microsoft newsgroups.
> Sincerely
> Pankaj Agarwal
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>|||Unfortunately there is no way to get around the large transaction log when
you are performing index rebuild. If you feel that adding another NIC will
provide better bandwidth and hence faster copy, then that may be something
to consider.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Log Shipping in multiple databases

I am trying to configure Log_Shipping in multiple databases on different
servers.
I tried to add it but it has to use the same destination copy folder, is
that true ?
i am using SQL2005.I haven't used the 2005 log shipping. Log shipping in general works under
the following model. There are two virtual jobs that run consecutively; the
first virtual job would be to create a log for a given time frame on the
source server and write it to the local disk and subsequently send a copy of
that log file to the destination server. The second virtual job is to read
the log file sent from the source server and when it reads the log file, it
can either delete it or more commonly, the file is saved for a given time to
another folder that consists of logs that have been read.
Example:
Write log to \\mysourceserver\backup\mylog_date_time.log
Copy mylog_date_time.log from \\mysourceserver\backup to
\\mysdestserver\backup
Read log \\mysourceserver\backup\mylog_date_time.log
Store log by moving \\mysourceserver\backup\mylog_date_time.log to
\\mysourceserver\storage\mylog_date_time.log
Finally there may be a purge time set to delete logs older than a set time.
--
Regards,
Jamie
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>|||Thanks Jamie for help,
I am already running Log Shipping from one server to another one, but i am
going to buy a new server with a highly configuration and want this new one
to be the main database and the old one be another log shipping database ( 1
main db and 2 log shipping db).
I tried it on a test server but any adding new server, has to change the
copy folder into the old server by force.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:786DB259-3386-4E4E-9A0A-FFE03BC5557B@.microsoft.com...
>I haven't used the 2005 log shipping. Log shipping in general works under
> the following model. There are two virtual jobs that run consecutively;
> the
> first virtual job would be to create a log for a given time frame on the
> source server and write it to the local disk and subsequently send a copy
> of
> that log file to the destination server. The second virtual job is to
> read
> the log file sent from the source server and when it reads the log file,
> it
> can either delete it or more commonly, the file is saved for a given time
> to
> another folder that consists of logs that have been read.
> Example:
> Write log to \\mysourceserver\backup\mylog_date_time.log
> Copy mylog_date_time.log from \\mysourceserver\backup to
> \\mysdestserver\backup
> Read log \\mysourceserver\backup\mylog_date_time.log
> Store log by moving \\mysourceserver\backup\mylog_date_time.log to
> \\mysourceserver\storage\mylog_date_time.log
> Finally there may be a purge time set to delete logs older than a set
> time.
> --
> Regards,
> Jamie
>
> "Mahmoud Amin" wrote:
>> I am trying to configure Log_Shipping in multiple databases on different
>> servers.
>> I tried to add it but it has to use the same destination copy folder, is
>> that true ?
>> i am using SQL2005.
>>|||Hi Amin,
You have 1 server which has primary db and you configure it
for log shipping to 2 different secondary servers....i guess this is what
you want....
but i think you are trying to configure log shipping from 1 st primary to 1
st secondary
and from the 1st primary to the same secondary server...so you'll have 2
copies of your log shipped db in your secoindary server......but that will
not server the purpose of log shipping as in case the seconday server is down
you won't have backup of primary server.......
but you can configure like that but you'll have only 1 shared folder which
conains both the logs from primary server
refer the below link for configuring log shipping just a sample
http://deepakinsql.blogspot.com/2007/06/how-to-configure-log-shipping-in-sql.html
Thanxx
Deepak
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>

Log Shipping Gap in Log Chain

Log Shipping on SQL 2005 is failing because of a gap in the log chain. The schedule is every 15 minutes, the backup and copy jobs run without issue. The failure occurs early in the morning when there are no users, maintenance activities, or scheduled jobs - this has happened twice since we applied SP2. The database that is participating in the log shipping is approximately 20Gb, and recovery takes several hours.

Are there any known issues with log shipping on SP2? Any ideas why this might be happening? Is there any other information I can provide to help debug this issue?

This seems to be a duplicate of another message. Please see following URL for replies to this question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1567987&SiteID=1

Log Shipping Gap in Log Chain

Log Shipping on SQL 2005 is failing because of a gap in the log chain. The schedule is every 15 minutes, the backup and copy jobs run without issue. The failure occurs early in the morning when there are no users, maintenance activities, or scheduled jobs - this has happened twice since we applied SP2. The database that is participating in the log shipping is approximately 20Gb, and recovery takes several hours.

Are there any known issues with log shipping on SP2? Any ideas why this might be happening? Is there any other information I can provide to help debug this issue?

This seems to be a duplicate of another message. Please see following URL for replies to this question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1567987&SiteID=1

Log shipping error

I m getting following error in copy/restore operation
"The process cannot access the file because it is being used by another
process."
This come against the file first_file_000000000000.trn every time copy
restore is done. Only first time it went successful. Error number is 32.
Please tell me how to avoid thisVSS
You could be getting this messaqge because it is trying to restore the log
before the copy is finished. How often do you backup and copy the transaction
log?
There is a setting for load delay. The default is 0, you could try setting
that to wait longer for the copy to finish.
Hope this helps
John
"VSS" wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
>|||VSS wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
Isn't it obvious what you need to do? The error message tells you that
some other process is using the file that you're trying to copy/restore.
Not a SQL Server problem. You need to figure out what is using that
file. Take a look at http://www.sysinternals.com for some utilities
that will help you figure that out.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log shipping error

I m getting following error in copy/restore operation
"The process cannot access the file because it is being used by another
process."
This come against the file first_file_000000000000.trn every time copy
restore is done. Only first time it went successful. Error number is 32.
Please tell me how to avoid thisVSS
You could be getting this messaqge because it is trying to restore the log
before the copy is finished. How often do you backup and copy the transactio
n
log?
There is a setting for load delay. The default is 0, you could try setting
that to wait longer for the copy to finish.
Hope this helps
John
"VSS" wrote:

> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
>|||VSS wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
Isn't it obvious what you need to do? The error message tells you that
some other process is using the file that you're trying to copy/restore.
Not a SQL Server problem. You need to figure out what is using that
file. Take a look at http://www.sysinternals.com for some utilities
that will help you figure that out.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

log shipping enquires

Hi,
I have set up log shipping in the following :
load/copy frequency - 1 mins
backup frequency - 5 mins
secondary db - standby mode
issue :
when i made some changes to a record of the primary db's tbl , it was not
reflected in the secondary db's table.
Is it due to the fact that the secondary db is a Read-Only ?
and if i do want to delete log shipping , what shld be the correct way in
doing this
appreciate ur advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200601/1the reason why the cahnges in primary DB are not reflected on secondary
maybe that you didnt setup the log shipping properly.
You can cross check if if have any out of sync errors...
and abt deleting the log shipping the best way will be ... from the
maintenance plan remove log shipping and then delete the plan.|||Did you wait long enough for the changs to be sent? You can verify the tran
log backups by looking in the directories on each machine. You can also
verify the backup and restore by looking in the errorlog. The log shipping
monitor will display the status of everything. If it isn't getting there,
you will be seeing errors.
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.
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:5af9a1affdb26@.uwe...
> Hi,
> I have set up log shipping in the following :
> load/copy frequency - 1 mins
> backup frequency - 5 mins
> secondary db - standby mode
> issue :
> when i made some changes to a record of the primary db's tbl , it was not
> reflected in the secondary db's table.
> Is it due to the fact that the secondary db is a Read-Only ?
> and if i do want to delete log shipping , what shld be the correct way in
> doing this
> appreciate ur advise
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200601/1|||tks ..
Shadow wrote:
>the reason why the cahnges in primary DB are not reflected on secondary
>maybe that you didnt setup the log shipping properly.
>You can cross check if if have any out of sync errors...
>and abt deleting the log shipping the best way will be ... from the
>maintenance plan remove log shipping and then delete the plan.
Message posted via http://www.droptable.com|||Hi,
I have managed to set up the log shipping correctly as i could see the
changes on my destination DB . However, i have specified that copy is 0
minutes , and load is 1 minutes but it took something like around 5 minutes
to see the updated data in my destination DB.
how can i acutally make the updates "almost immediate" ? or this is normal
as copying the txn log takes time and need to wait till user "give up" the
exclusive lock , then copy the txn log over and then load from the txn log ?
appreciate ur advice
tks & rdgs
Michael Hotek wrote:[vbcol=seagreen]
>Did you wait long enough for the changs to be sent? You can verify the tra
n
>log backups by looking in the directories on each machine. You can also
>verify the backup and restore by looking in the errorlog. The log shipping
>monitor will display the status of everything. If it isn't getting there,
>you will be seeing errors.
>
>[quoted text clipped - 16 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200602/1|||You can't. The entire thing runs as a set of jobs. The most frequently a
job can run is every minute and that is NOT recommended for log shipping
unless you want to watch the monitor throw a LOT of errors. You usually set
up the backup job at 2 minutes or more. (2 minutes is the lowest you want
to go). That means a new backup will be generated every 2 minutes. It then
takes time to copy over and time to restore. Most of that time is simply
the job shutting down and waiting for the SQL Server Agent to kick it off
again. 5 minutes start to finish is about the best you are going to get
with log shipping. If you need lower latency than that, you have to go to
either Database Mirroring (2005 only) or the replication engine.
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.
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:5b378dc949992@.uwe...
> Hi,
> I have managed to set up the log shipping correctly as i could see the
> changes on my destination DB . However, i have specified that copy is 0
> minutes , and load is 1 minutes but it took something like around 5
> minutes
> to see the updated data in my destination DB.
> how can i acutally make the updates "almost immediate" ? or this is
> normal
> as copying the txn log takes time and need to wait till user "give up" the
> exclusive lock , then copy the txn log over and then load from the txn log
> ?
> appreciate ur advice
> tks & rdgs
>
> Michael Hotek wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200602/1|||tks for ur clarifications ..
Cheers ..
Michael Hotek wrote:[vbcol=seagreen]
>You can't. The entire thing runs as a set of jobs. The most frequently a
>job can run is every minute and that is NOT recommended for log shipping
>unless you want to watch the monitor throw a LOT of errors. You usually se
t
>up the backup job at 2 minutes or more. (2 minutes is the lowest you want
>to go). That means a new backup will be generated every 2 minutes. It the
n
>takes time to copy over and time to restore. Most of that time is simply
>the job shutting down and waiting for the SQL Server Agent to kick it off
>again. 5 minutes start to finish is about the best you are going to get
>with log shipping. If you need lower latency than that, you have to go to
>either Database Mirroring (2005 only) or the replication engine.
>
>[quoted text clipped - 26 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200602/1

log shipping enquires

Hi,
I have set up log shipping in the following :
load/copy frequency - 1 mins
backup frequency - 5 mins
secondary db - standby mode
issue :
when i made some changes to a record of the primary db's tbl , it was not
reflected in the secondary db's table.
Is it due to the fact that the secondary db is a Read-Only ?
and if i do want to delete log shipping , what shld be the correct way in
doing this
appreciate ur advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200601/1
the reason why the cahnges in primary DB are not reflected on secondary
maybe that you didnt setup the log shipping properly.
You can cross check if if have any out of sync errors...
and abt deleting the log shipping the best way will be ... from the
maintenance plan remove log shipping and then delete the plan.
|||Did you wait long enough for the changs to be sent? You can verify the tran
log backups by looking in the directories on each machine. You can also
verify the backup and restore by looking in the errorlog. The log shipping
monitor will display the status of everything. If it isn't getting there,
you will be seeing errors.
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.
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:5af9a1affdb26@.uwe...
> Hi,
> I have set up log shipping in the following :
> load/copy frequency - 1 mins
> backup frequency - 5 mins
> secondary db - standby mode
> issue :
> when i made some changes to a record of the primary db's tbl , it was not
> reflected in the secondary db's table.
> Is it due to the fact that the secondary db is a Read-Only ?
> and if i do want to delete log shipping , what shld be the correct way in
> doing this
> appreciate ur advise
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200601/1
|||tks ..
Shadow wrote:
>the reason why the cahnges in primary DB are not reflected on secondary
>maybe that you didnt setup the log shipping properly.
>You can cross check if if have any out of sync errors...
>and abt deleting the log shipping the best way will be ... from the
>maintenance plan remove log shipping and then delete the plan.
Message posted via http://www.droptable.com
|||Hi,
I have managed to set up the log shipping correctly as i could see the
changes on my destination DB . However, i have specified that copy is 0
minutes , and load is 1 minutes but it took something like around 5 minutes
to see the updated data in my destination DB.
how can i acutally make the updates "almost immediate" ? or this is normal
as copying the txn log takes time and need to wait till user "give up" the
exclusive lock , then copy the txn log over and then load from the txn log ?
appreciate ur advice
tks & rdgs
Michael Hotek wrote:[vbcol=seagreen]
>Did you wait long enough for the changs to be sent? You can verify the tran
>log backups by looking in the directories on each machine. You can also
>verify the backup and restore by looking in the errorlog. The log shipping
>monitor will display the status of everything. If it isn't getting there,
>you will be seeing errors.
>[quoted text clipped - 16 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200602/1
|||You can't. The entire thing runs as a set of jobs. The most frequently a
job can run is every minute and that is NOT recommended for log shipping
unless you want to watch the monitor throw a LOT of errors. You usually set
up the backup job at 2 minutes or more. (2 minutes is the lowest you want
to go). That means a new backup will be generated every 2 minutes. It then
takes time to copy over and time to restore. Most of that time is simply
the job shutting down and waiting for the SQL Server Agent to kick it off
again. 5 minutes start to finish is about the best you are going to get
with log shipping. If you need lower latency than that, you have to go to
either Database Mirroring (2005 only) or the replication engine.
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.
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:5b378dc949992@.uwe...
> Hi,
> I have managed to set up the log shipping correctly as i could see the
> changes on my destination DB . However, i have specified that copy is 0
> minutes , and load is 1 minutes but it took something like around 5
> minutes
> to see the updated data in my destination DB.
> how can i acutally make the updates "almost immediate" ? or this is
> normal
> as copying the txn log takes time and need to wait till user "give up" the
> exclusive lock , then copy the txn log over and then load from the txn log
> ?
> appreciate ur advice
> tks & rdgs
>
> Michael Hotek wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200602/1
|||tks for ur clarifications ..
Cheers ..
Michael Hotek wrote:[vbcol=seagreen]
>You can't. The entire thing runs as a set of jobs. The most frequently a
>job can run is every minute and that is NOT recommended for log shipping
>unless you want to watch the monitor throw a LOT of errors. You usually set
>up the backup job at 2 minutes or more. (2 minutes is the lowest you want
>to go). That means a new backup will be generated every 2 minutes. It then
>takes time to copy over and time to restore. Most of that time is simply
>the job shutting down and waiting for the SQL Server Agent to kick it off
>again. 5 minutes start to finish is about the best you are going to get
>with log shipping. If you need lower latency than that, you have to go to
>either Database Mirroring (2005 only) or the replication engine.
>[quoted text clipped - 26 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200602/1

log shipping enquires

Hi,
I have set up log shipping in the following :
load/copy frequency - 1 mins
backup frequency - 5 mins
secondary db - standby mode
issue :
when i made some changes to a record of the primary db's tbl , it was not
reflected in the secondary db's table.
Is it due to the fact that the secondary db is a Read-Only ?
and if i do want to delete log shipping , what shld be the correct way in
doing this
appreciate ur advise
tks & rdgs
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200601/1the reason why the cahnges in primary DB are not reflected on secondary
maybe that you didnt setup the log shipping properly.
You can cross check if if have any out of sync errors...
and abt deleting the log shipping the best way will be ... from the
maintenance plan remove log shipping and then delete the plan.|||Did you wait long enough for the changs to be sent? You can verify the tran
log backups by looking in the directories on each machine. You can also
verify the backup and restore by looking in the errorlog. The log shipping
monitor will display the status of everything. If it isn't getting there,
you will be seeing errors.
--
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.
"maxzsim via SQLMonster.com" <u14644@.uwe> wrote in message
news:5af9a1affdb26@.uwe...
> Hi,
> I have set up log shipping in the following :
> load/copy frequency - 1 mins
> backup frequency - 5 mins
> secondary db - standby mode
> issue :
> when i made some changes to a record of the primary db's tbl , it was not
> reflected in the secondary db's table.
> Is it due to the fact that the secondary db is a Read-Only ?
> and if i do want to delete log shipping , what shld be the correct way in
> doing this
> appreciate ur advise
> tks & rdgs
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200601/1|||tks ..
Shadow wrote:
>the reason why the cahnges in primary DB are not reflected on secondary
>maybe that you didnt setup the log shipping properly.
>You can cross check if if have any out of sync errors...
>and abt deleting the log shipping the best way will be ... from the
>maintenance plan remove log shipping and then delete the plan.
--
Message posted via http://www.sqlmonster.com|||Hi,
I have managed to set up the log shipping correctly as i could see the
changes on my destination DB . However, i have specified that copy is 0
minutes , and load is 1 minutes but it took something like around 5 minutes
to see the updated data in my destination DB.
how can i acutally make the updates "almost immediate" ? or this is normal
as copying the txn log takes time and need to wait till user "give up" the
exclusive lock , then copy the txn log over and then load from the txn log ?
appreciate ur advice
tks & rdgs
Michael Hotek wrote:
>Did you wait long enough for the changs to be sent? You can verify the tran
>log backups by looking in the directories on each machine. You can also
>verify the backup and restore by looking in the errorlog. The log shipping
>monitor will display the status of everything. If it isn't getting there,
>you will be seeing errors.
>> Hi,
>[quoted text clipped - 16 lines]
>> tks & rdgs
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200602/1|||You can't. The entire thing runs as a set of jobs. The most frequently a
job can run is every minute and that is NOT recommended for log shipping
unless you want to watch the monitor throw a LOT of errors. You usually set
up the backup job at 2 minutes or more. (2 minutes is the lowest you want
to go). That means a new backup will be generated every 2 minutes. It then
takes time to copy over and time to restore. Most of that time is simply
the job shutting down and waiting for the SQL Server Agent to kick it off
again. 5 minutes start to finish is about the best you are going to get
with log shipping. If you need lower latency than that, you have to go to
either Database Mirroring (2005 only) or the replication engine.
--
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.
"maxzsim via SQLMonster.com" <u14644@.uwe> wrote in message
news:5b378dc949992@.uwe...
> Hi,
> I have managed to set up the log shipping correctly as i could see the
> changes on my destination DB . However, i have specified that copy is 0
> minutes , and load is 1 minutes but it took something like around 5
> minutes
> to see the updated data in my destination DB.
> how can i acutally make the updates "almost immediate" ? or this is
> normal
> as copying the txn log takes time and need to wait till user "give up" the
> exclusive lock , then copy the txn log over and then load from the txn log
> ?
> appreciate ur advice
> tks & rdgs
>
> Michael Hotek wrote:
>>Did you wait long enough for the changs to be sent? You can verify the
>>tran
>>log backups by looking in the directories on each machine. You can also
>>verify the backup and restore by looking in the errorlog. The log
>>shipping
>>monitor will display the status of everything. If it isn't getting there,
>>you will be seeing errors.
>> Hi,
>>[quoted text clipped - 16 lines]
>> tks & rdgs
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200602/1|||tks for ur clarifications ..
Cheers ..
Michael Hotek wrote:
>You can't. The entire thing runs as a set of jobs. The most frequently a
>job can run is every minute and that is NOT recommended for log shipping
>unless you want to watch the monitor throw a LOT of errors. You usually set
>up the backup job at 2 minutes or more. (2 minutes is the lowest you want
>to go). That means a new backup will be generated every 2 minutes. It then
>takes time to copy over and time to restore. Most of that time is simply
>the job shutting down and waiting for the SQL Server Agent to kick it off
>again. 5 minutes start to finish is about the best you are going to get
>with log shipping. If you need lower latency than that, you have to go to
>either Database Mirroring (2005 only) or the replication engine.
>> Hi,
>[quoted text clipped - 26 lines]
>> tks & rdgs
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200602/1

Log Shipping copy with compression

I've got several secondary servers setup against my production server, and
working fine. However, one is across a t-1, and the file copying can really
effect latency across this link.
I've been searching far an wide for a "replicator" that has a client server
component, that can do streaming compression. TRNs compress down incrediably
well. I could use a util to zip them to a unc, and then unzip on the other
side, but this seems dumb. Why oh why doesn't SMB support compression...we
have gone backwards since the z-modem days .
I'm trying to get rsync to work using cygwin, but of course it is a pain in
the butt. Does anyone know of affoardable software that does this seamly
simple task. I'm about to program my own.
Compression has been considered on the packet level, but the reason that it
is not implemented is that in general the data travelling across the wire is
binary and the compression ratio and cost involved in compressing binary
data outweighs the savings in doing so. Compressing purely textual data does
provide much better compression.
Your best bet is to zip then before sending, and then unzip them on the
other end.
"et" <et@.discussions.microsoft.com> wrote in message
news:83CF2440-9764-47D7-8163-AE47C3106035@.microsoft.com...
> I've got several secondary servers setup against my production server, and
> working fine. However, one is across a t-1, and the file copying can
really
> effect latency across this link.
> I've been searching far an wide for a "replicator" that has a client
server
> component, that can do streaming compression. TRNs compress down
incrediably
> well. I could use a util to zip them to a unc, and then unzip on the other
> side, but this seems dumb. Why oh why doesn't SMB support compression...we
> have gone backwards since the z-modem days .
> I'm trying to get rsync to work using cygwin, but of course it is a pain
in
> the butt. Does anyone know of affoardable software that does this seamly
> simple task. I'm about to program my own.
>
|||As I recall Windows 2003 was supposed to offer SMB copying of NTFS compressed
files from server to server without uncompressing in the middle.
But as I've never seen that feature advertised, I'm guessing it never made the
cut before release.

> I've been searching far an wide for a "replicator" that has a client server
> component, that can do streaming compression. TRNs compress down incrediably
> well. I could use a util to zip them to a unc, and then unzip on the other
> side, but this seems dumb. Why oh why doesn't SMB support compression...we
> have gone backwards since the z-modem days .
> I'm trying to get rsync to work using cygwin, but of course it is a pain in
> the butt. Does anyone know of affoardable software that does this seamly
> simple task. I'm about to program my own.
>
Neil Pike. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforu...?SRV=MSDevApps
(faqxxx.zip in lib 7)
or http://www.ntfaq.com/Articles/Index...partmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq

Log Shipping Copy Job reports successful, but copies nothing

I have set up log shipping between 2 servers but cant get it to
function correctly.
Everything seems to be fine, the backup job happens, dumping the
transaction log to the network share on the primary server(also the
monitoring server).
The copy job runs and completes in 1 second or less, but doesn't seem
to move anything even though it reports success.
If I look at the copy/restore history in the log shipping monitor, it
continuously says that the copy succeeded, but no files were moved and
the last file moved is first_file_00000000.trn
I have checked the settings for the shares, and they are both fine.
I am able to log into the secondary server using the Sql Agent account
and map to the network share on the primary server where the log files
are being created. No problem there.
If I manually move the files the restore job works fine.
The log_shipping_secondary table is getting updated by the restore job
too, and I am using sql authentication with the
log_shipping_monitor_probe account set to sysadmin and db_ownber in
msdb.
It seems to be just the copy jobs never seeming to find any files even
when they are there.
I am starting to go crazy! HELP!
-Gregory
Gregory,
usually when I troubleshoot this issue it is a problem with the setup of
directories and shares, which can be confusing in the wizard. Please can you
remove the existing maintenance plan and set up the directories/shares below
then recreate the plan.
You need a folder eg c:\ProductionLogs that is shared
(\\server\PRODUCTIONLOGS) on the production server.
You need a directory on the standby server c:\shippedlogs, not shared.
In the maintenance plan, the transaction log backup directory is
c:\ProductionLogs
The network sharename is \\server\PRODUCTIONLOGS
The destination is c:\shippedlogs.
HTH,
Paul Ibison
|||Log shipping gives me no love.
I tried as you suggested, created new network shares, deleted the
maintenance plan and recreated the plan using the info you supplied.
It continues to give me the same problem.
This is in the history for the job:
Executed as user: XXXXXXX\UserID. output
---
---
(null)
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998. The step succeeded..
So informational.
Beautiful huh?
Additional info:
The servers are not on a domain, they are both in a workgroup.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Gregory,
there isn't an easy way for me to debug this, and no offence to you but I'd
like to ensure this is not a setup issue.
Please can you send me screenshots of the options you select when you go
through the wizard?
TIA,
Paul Ibison

Log Shipping Copy Errors

We've been experiencing above average log shipping
log "copy" errors. This is the job in which the server
which the log is shipped to has a job on it that copies
the newest log files from the host server. For no apparent
reason, this job fails , but the next time it's run, it
works. Some times it fails 10 times in a row then catches
up all at once. Other times it's less frequent. Anyone
know what might cause this . Disk space and netowkr access
isn't an issue, we've checked that.
thanksTom
Do you have a delay between the source server backing up
the database and the log shipping picking it up? It may be
that the target database is trying to copy the source
backup before it is finished. When you have problems is it
at a busy time, when for instance the log may be larger
than normal?
Regards
John|||Whats the error message?
>--Original Message--
>We've been experiencing above average log shipping
>log "copy" errors. This is the job in which the server
>which the log is shipped to has a job on it that copies
>the newest log files from the host server. For no
apparent
>reason, this job fails , but the next time it's run, it
>works. Some times it fails 10 times in a row then catches
>up all at once. Other times it's less frequent. Anyone
>know what might cause this . Disk space and netowkr
access
>isn't an issue, we've checked that.
>thanks
>.
>

Log shipping Copy and Load frequency

Whats the best interval needed to set up the difference between the copy and
load frequency for log shipping. What i mean is if i set up the copy and
load each for 10 mins, would there be ever a contention where the load is
trying to restore a log file being copied also invoked at the same time
resulting in error " File being used by another process" since I have seen
those errors on our failure of restore jobs.
ThanksIt depends on the amount of transactions performed between the log =shipping routines and the performance of your servers. We perform log =shipping every 30 minutes. The restore the the standby server takes =less than 30 seconds.
-- Keith, SQL Server MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message =news:u0kTuxcSDHA.1552@.TK2MSFTNGP10.phx.gbl...
> Whats the best interval needed to set up the difference between the =copy and
> load frequency for log shipping. What i mean is if i set up the copy =and
> load each for 10 mins, would there be ever a contention where the load =is
> trying to restore a log file being copied also invoked at the same =time
> resulting in error " File being used by another process" since I have =seen
> those errors on our failure of restore jobs.
> > Thanks
> > >

Log shipping configuration - HELP

I'm having a difficult time making sence of the schedule SQL Server has
configured for my copy and restore jobs. I can't tie the monitor information
back to any of it.
My log shipping configuration does a backup every 120 minutes between 5AM
and 2:59AM; I run backups @. 3AM. The copy/load Frequency is set to 120
minutes with a load delay is 15 minutes.
Actual results are not what I expected, the log backups occur as expected
5AM, 7AM,9AM ect.., but the copy and restore jobs created on the secondary
are behind by 1 hour. Both the copy and restore jobs are executing on a 6AM,
8AM, 10AM schedule. Cany some one explain why this is happening? It is
causing an out of sync condition.
What effect does the load delay have on the restore job schedule.
Not sure it will help but look at
http://www.mindsdoor.net/SQLAdmin/LogShipping.html
If you want to replace it.
"Jerrick D.H" wrote:

> I'm having a difficult time making sence of the schedule SQL Server has
> configured for my copy and restore jobs. I can't tie the monitor information
> back to any of it.
> My log shipping configuration does a backup every 120 minutes between 5AM
> and 2:59AM; I run backups @. 3AM. The copy/load Frequency is set to 120
> minutes with a load delay is 15 minutes.
> Actual results are not what I expected, the log backups occur as expected
> 5AM, 7AM,9AM ect.., but the copy and restore jobs created on the secondary
> are behind by 1 hour. Both the copy and restore jobs are executing on a 6AM,
> 8AM, 10AM schedule. Cany some one explain why this is happening? It is
> causing an out of sync condition.
> What effect does the load delay have on the restore job schedule.
>
|||Nigel,
Thank you for taking the time to respond. I was using a similar process as
the one documented by mindsdoor, but switched to SQL automated process, and
I like it. Since I could not find a valid reason for the delay, I played
around with the job schedules until they woked they way I wanted them too.
"Nigel Rivett" wrote:
[vbcol=seagreen]
> Not sure it will help but look at
> http://www.mindsdoor.net/SQLAdmin/LogShipping.html
> If you want to replace it.
> "Jerrick D.H" wrote:

Log Shipping between 2 Clusters

Hi
I'm trying to setup log shipping between two 2-node Active/Passive clusters and I keep getting an error "Unable to copy the initialization file to the secondary server".
I've search KB, to find an article KB/811890, but both clusters are in the same domain, and thus this article shouldn't apply. However, I'll try anything, so I have re-registered the second (log ship recipient) cluster as per the recommendations (SERVERN
AME.DOMAIN), but still get the same message.
I know its probably me that doing something wrong, but I'm stuck at what.
I have tried registering the instances in the following ways.
- Using the Cluster name (as opened within Cluster Administrator)
- Using the Virtual Server Name (as provided within the SQL Install)
- Using the Cluster IP Address
- Using the Virtual SQL Server IP Address
In all cases, I either get the same error, or don't get that far.
Can you please assist?
Thanks, in advance for your assistance.
Bev
Try the following to see if it helps
1)Run the stored procs (http://support.microsoft.com/default...&Product=sql2k) to clean up log shipping.
2)Verify that the SQL Server and SQL Server Agent services on primary and secondary SQL Servers are running under a domain account
3)Verify with your NT Administrator that there is a two way trust between the domains.
4)Log on to primary server using the domain account used to start SQL Server services on primary server.
a)Open Query Analyzer and use xp_cmdshell command to copy a file (any file will do) from the share on primary server (i.e. the share on primary server where you
want the transaction log backups to be stored) to the share on the secondary server. If you get error like access denied then we will need to fix this first.
b)Open Enterprise Manager and verify that you can register the primary and secondary SQL Servers.
c)Verify that the database you want to use for log shipping does not have SIMPLE Recovery model.
d)Verify that that the domain account that is used to start SQL Server services has access permission to the database that you want to use for log shipping.
e)Configure Log Shipping.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx