Log Shipping Sql server 2005 enterprise edition

require some urgent help on Sql Server 2005 Log Shipping
Our Project :
Seprate Read & Write Process by building Report Server using Sql
Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
Windows 2003 (64- bit) Server as Production server we had implemented Log
Shipping on the production server which will transfer logs after every 15 min
to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both secondry
databases are in Standby / ReadOnly Mode .The system is working fine. All
logs are transffered sucessfully. we had tried online indexing on production
server which works fine.
Problem :--
Our main purpose of two standby server is 1st standby server will be
utilised as Report Server and 2nd standby Server we want to take full backup
everyday but when we try to take backup of 2nd standby server it give us
error like "cannot take backup the database is in warm standby mode".We
cannot take backup from Production server as it is required for online
indexing and data updation during night hrs.
OR
Is there any other way to take full backup from secondry servers?
We require help on following issues
1) How to take full backup of 2nd stand by server?
2) If Log shipping Failed How to restart Log Shipping without restoring a
new backup copy on secondry servers?
3) In this case how to make all server available with minimum downtime?
4) Is the process is Technically Perfect?
I think you have a problem here.
Only way i can think of is .Stop the standy mode -recover the database with
last log file. And make a fullbackup.
|||A database that is in STANDBY mode is technically in a RESTORING state with
a special stop point. You cannot back up a database while it is restoring.
Therefore, you cannot back up a log shipping target database.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"PankajP" <PankajP@.discussions.microsoft.com> wrote in message
news:49EB67A0-288F-4339-9F01-5EEBBB2CF86C@.microsoft.com...
> require some urgent help on Sql Server 2005 Log Shipping
> Our Project :
> Seprate Read & Write Process by building Report Server using Sql
> Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
> Windows 2003 (64- bit) Server as Production server we had implemented Log
> Shipping on the production server which will transfer logs after every 15
> min
> to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both
> secondry
> databases are in Standby / ReadOnly Mode .The system is working fine. All
> logs are transffered sucessfully. we had tried online indexing on
> production
> server which works fine.
> Problem :--
> Our main purpose of two standby server is 1st standby server will be
> utilised as Report Server and 2nd standby Server we want to take full
> backup
> everyday but when we try to take backup of 2nd standby server it give us
> error like "cannot take backup the database is in warm standby mode".We
> cannot take backup from Production server as it is required for online
> indexing and data updation during night hrs.
> OR
> Is there any other way to take full backup from secondry servers?
> We require help on following issues
> 1) How to take full backup of 2nd stand by server?
> 2) If Log shipping Failed How to restart Log Shipping without restoring a
> new backup copy on secondry servers?
> 3) In this case how to make all server available with minimum downtime?
> 4) Is the process is Technically Perfect?

Log Shipping Sql server 2005 enterprise edition

require some urgent help on Sql Server 2005 Log Shipping
Our Project :
Seprate Read & Write Process by building Report Server using Sql
Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
Windows 2003 (64- bit) Server as Production server we had implemented Log
Shipping on the production server which will transfer logs after every 15 min
to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both secondry
databases are in Standby / ReadOnly Mode .The system is working fine. All
logs are transffered sucessfully. we had tried online indexing on production
server which works fine.
Problem :--
Our main purpose of two standby server is 1st standby server will be
utilised as Report Server and 2nd standby Server we want to take full backup
everyday but when we try to take backup of 2nd standby server it give us
error like "cannot take backup the database is in warm standby mode".We
cannot take backup from Production server as it is required for online
indexing and data updation during night hrs.
OR
Is there any other way to take full backup from secondry servers?
We require help on following issues
1) How to take full backup of 2nd stand by server?
2) If Log shipping Failed How to restart Log Shipping without restoring a
new backup copy on secondry servers?
3) In this case how to make all server available with minimum downtime?
4) Is the process is Technically Perfect?I think you have a problem here.
Only way i can think of is .Stop the standy mode -recover the database with
last log file. And make a fullbackup.|||A database that is in STANDBY mode is technically in a RESTORING state with
a special stop point. You cannot back up a database while it is restoring.
Therefore, you cannot back up a log shipping target database.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"PankajP" <PankajP@.discussions.microsoft.com> wrote in message
news:49EB67A0-288F-4339-9F01-5EEBBB2CF86C@.microsoft.com...
> require some urgent help on Sql Server 2005 Log Shipping
> Our Project :
> Seprate Read & Write Process by building Report Server using Sql
> Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
> Windows 2003 (64- bit) Server as Production server we had implemented Log
> Shipping on the production server which will transfer logs after every 15
> min
> to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both
> secondry
> databases are in Standby / ReadOnly Mode .The system is working fine. All
> logs are transffered sucessfully. we had tried online indexing on
> production
> server which works fine.
> Problem :--
> Our main purpose of two standby server is 1st standby server will be
> utilised as Report Server and 2nd standby Server we want to take full
> backup
> everyday but when we try to take backup of 2nd standby server it give us
> error like "cannot take backup the database is in warm standby mode".We
> cannot take backup from Production server as it is required for online
> indexing and data updation during night hrs.
> OR
> Is there any other way to take full backup from secondry servers?
> We require help on following issues
> 1) How to take full backup of 2nd stand by server?
> 2) If Log shipping Failed How to restart Log Shipping without restoring a
> new backup copy on secondry servers?
> 3) In this case how to make all server available with minimum downtime?
> 4) Is the process is Technically Perfect?sql

Log Shipping Sql server 2005 enterprise edition

require some urgent help on Sql Server 2005 Log Shipping
Our Project :
Seprate Read & Write Process by building Report Server using Sql
Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
Windows 2003 (64- bit) Server as Production server we had implemented Log
Shipping on the production server which will transfer logs after every 15 mi
n
to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both secondry
databases are in Standby / ReadOnly Mode .The system is working fine. All
logs are transffered sucessfully. we had tried online indexing on production
server which works fine.
Problem :--
Our main purpose of two standby server is 1st standby server will be
utilised as Report Server and 2nd standby Server we want to take full backup
everyday but when we try to take backup of 2nd standby server it give us
error like "cannot take backup the database is in warm standby mode".We
cannot take backup from Production server as it is required for online
indexing and data updation during night hrs.
OR
Is there any other way to take full backup from secondry servers?
We require help on following issues
1) How to take full backup of 2nd stand by server?
2) If Log shipping Failed How to restart Log Shipping without restoring a
new backup copy on secondry servers?
3) In this case how to make all server available with minimum downtime?
4) Is the process is Technically Perfect?I think you have a problem here.
Only way i can think of is .Stop the standy mode -recover the database with
last log file. And make a fullbackup.|||A database that is in STANDBY mode is technically in a RESTORING state with
a special stop point. You cannot back up a database while it is restoring.
Therefore, you cannot back up a log shipping target database.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"PankajP" <PankajP@.discussions.microsoft.com> wrote in message
news:49EB67A0-288F-4339-9F01-5EEBBB2CF86C@.microsoft.com...
> require some urgent help on Sql Server 2005 Log Shipping
> Our Project :
> Seprate Read & Write Process by building Report Server using Sql
> Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
> Windows 2003 (64- bit) Server as Production server we had implemented Log
> Shipping on the production server which will transfer logs after every 15
> min
> to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both
> secondry
> databases are in Standby / ReadOnly Mode .The system is working fine. All
> logs are transffered sucessfully. we had tried online indexing on
> production
> server which works fine.
> Problem :--
> Our main purpose of two standby server is 1st standby server will be
> utilised as Report Server and 2nd standby Server we want to take full
> backup
> everyday but when we try to take backup of 2nd standby server it give us
> error like "cannot take backup the database is in warm standby mode".We
> cannot take backup from Production server as it is required for online
> indexing and data updation during night hrs.
> OR
> Is there any other way to take full backup from secondry servers?
> We require help on following issues
> 1) How to take full backup of 2nd stand by server?
> 2) If Log shipping Failed How to restart Log Shipping without restoring a
> new backup copy on secondry servers?
> 3) In this case how to make all server available with minimum downtime?
> 4) Is the process is Technically Perfect?

Log Shipping Resync process

Does anyone know how to reset or resync the Log Shipping Transaction on
the Standby Server?
I am in testing mode and ran a backup log dbname with truncate_only and
it caused my log shipping mechanism to fail and now I need to know how
to resync the process without having to Re-implement the maintenance
plan.
P.S. Is there a better method of shrinking my database logs using Log
Shipping?
Thanks,
BillTry this.
1) Disable all the logshipping jobs so they don't run
while you work. These are "Logshipping copy %"
and "Logshipping restore %" on the secondary; and "DB
Backup" and "Transaction log backup" on the primary.
2) Manually run the "DB Backup" job on the primary.
3) Copy that backup file to the secondary and restore the
file using the norecovery and standby options in the
restore database command. The standby option is if your
secondary was in readonly mode.
4) The databases should now be in sync. Run the
trasaction log backup on the primary. Then run the
Logshipping copy job on the secondary. Then run the
Logshipping restore job on the secondary. They should all
run successfully.
5) remember to reenable all your logshipping jobs.
This was a very quick summary. Hope it helps.
>--Original Message--
>Does anyone know how to reset or resync the Log Shipping
Transaction on
>the Standby Server?
>
>I am in testing mode and ran a backup log dbname with
truncate_only and
>it caused my log shipping mechanism to fail and now I
need to know how
>to resync the process without having to Re-implement the
maintenance
>plan.
>P.S. Is there a better method of shrinking my database
logs using Log
>Shipping?
>Thanks,
>Bill
>.
>

Log Shipping Problem

Hello Everyone. I am log shippping on a server that has heavy reads and
writes. The Log Ship process runs every 15 minutes and when it runs, it
tends to significantly slow down all the queries running on the box. Queries
which run 20-100 milliseconds run for over 2-3 seconds. The slowing causes
are webservers to back up which in turn slows are website.
I notice in PerMon that after every transaction log backup a checkpoint is
run immedialty after.
The queries are slow during the checkpoint process.
Is there a reason for this? Also, how can I avoid this slow down.
About the Server:
Windows 2003 Enterprise Edition
Quad processeor with Intel XEON 3.0 Ghz.
SQL 2000 version 8.00.936
Thanks,
George
George
There is no real way to avoid the checkpoint process. The checkpoint process
tells SQL Server to write completed transactions to disk, something you
obviously want to happen. You can make the gap between checkpoints longer by
altering the recovery interval. However if you do that the checkpoints will
last longer when they do happen (they will have more to do) and your
transation logs will probably get bigger, and you system will take longer to
come up following a reboot.
About the only thing you can do is look at your disk configuration, to see
if there is a way to speed up your I/O processes.
Hope this helps
John
"George teVelde" wrote:

> Hello Everyone. I am log shippping on a server that has heavy reads and
> writes. The Log Ship process runs every 15 minutes and when it runs, it
> tends to significantly slow down all the queries running on the box. Queries
> which run 20-100 milliseconds run for over 2-3 seconds. The slowing causes
> are webservers to back up which in turn slows are website.
> I notice in PerMon that after every transaction log backup a checkpoint is
> run immedialty after.
> The queries are slow during the checkpoint process.
> Is there a reason for this? Also, how can I avoid this slow down.
> About the Server:
> Windows 2003 Enterprise Edition
> Quad processeor with Intel XEON 3.0 Ghz.
> SQL 2000 version 8.00.936
> Thanks,
> George
|||Thanks for the reply, I have one more question.
Is there any reason Log Shipping would grab all the availble threads and not
release them?
I realize that it may not be the log shipping doing it, but I am trying to
eliminate as many variables as I can.
Thanks.
|||Hi
No, no reason. If checkpointing affects your performance, the disk layout is
probably not optimal. Basic rule, Logs on a separate set of drive, not on
RAID-5, but on mirrors.
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/
"George teVelde" <GeorgeteVelde@.discussions.microsoft.com> wrote in message
news:69243841-B076-4990-84E1-4C38A7FA4548@.microsoft.com...
> Thanks for the reply, I have one more question.
> Is there any reason Log Shipping would grab all the availble threads and
not
> release them?
> I realize that it may not be the log shipping doing it, but I am trying to
> eliminate as many variables as I can.
> Thanks.

Log Shipping Problem

Hello Everyone. I am log shippping on a server that has heavy reads and
writes. The Log Ship process runs every 15 minutes and when it runs, it
tends to significantly slow down all the queries running on the box. Querie
s
which run 20-100 milliseconds run for over 2-3 seconds. The slowing causes
are webservers to back up which in turn slows are website.
I notice in PerMon that after every transaction log backup a checkpoint is
run immedialty after.
The queries are slow during the checkpoint process.
Is there a reason for this? Also, how can I avoid this slow down.
About the Server:
Windows 2003 Enterprise Edition
Quad processeor with Intel XEON 3.0 Ghz.
SQL 2000 version 8.00.936
Thanks,
GeorgeGeorge
There is no real way to avoid the checkpoint process. The checkpoint process
tells SQL Server to write completed transactions to disk, something you
obviously want to happen. You can make the gap between checkpoints longer by
altering the recovery interval. However if you do that the checkpoints will
last longer when they do happen (they will have more to do) and your
transation logs will probably get bigger, and you system will take longer to
come up following a reboot.
About the only thing you can do is look at your disk configuration, to see
if there is a way to speed up your I/O processes.
Hope this helps
John
"George teVelde" wrote:

> Hello Everyone. I am log shippping on a server that has heavy reads and
> writes. The Log Ship process runs every 15 minutes and when it runs, it
> tends to significantly slow down all the queries running on the box. Quer
ies
> which run 20-100 milliseconds run for over 2-3 seconds. The slowing cause
s
> are webservers to back up which in turn slows are website.
> I notice in PerMon that after every transaction log backup a checkpoint is
> run immedialty after.
> The queries are slow during the checkpoint process.
> Is there a reason for this? Also, how can I avoid this slow down.
> About the Server:
> Windows 2003 Enterprise Edition
> Quad processeor with Intel XEON 3.0 Ghz.
> SQL 2000 version 8.00.936
> Thanks,
> George|||Thanks for the reply, I have one more question.
Is there any reason Log Shipping would grab all the availble threads and not
release them?
I realize that it may not be the log shipping doing it, but I am trying to
eliminate as many variables as I can.
Thanks.|||Hi
No, no reason. If checkpointing affects your performance, the disk layout is
probably not optimal. Basic rule, Logs on a separate set of drive, not on
RAID-5, but on mirrors.
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/
"George teVelde" <GeorgeteVelde@.discussions.microsoft.com> wrote in message
news:69243841-B076-4990-84E1-4C38A7FA4548@.microsoft.com...
> Thanks for the reply, I have one more question.
> Is there any reason Log Shipping would grab all the availble threads and
not
> release them?
> I realize that it may not be the log shipping doing it, but I am trying to
> eliminate as many variables as I can.
> Thanks.sql

Log Shipping Problem

Hello Everyone. I am log shippping on a server that has heavy reads and
writes. The Log Ship process runs every 15 minutes and when it runs, it
tends to significantly slow down all the queries running on the box. Queries
which run 20-100 milliseconds run for over 2-3 seconds. The slowing causes
are webservers to back up which in turn slows are website.
I notice in PerMon that after every transaction log backup a checkpoint is
run immedialty after.
The queries are slow during the checkpoint process.
Is there a reason for this? Also, how can I avoid this slow down.
About the Server:
Windows 2003 Enterprise Edition
Quad processeor with Intel XEON 3.0 Ghz.
SQL 2000 version 8.00.936
Thanks,
GeorgeGeorge
There is no real way to avoid the checkpoint process. The checkpoint process
tells SQL Server to write completed transactions to disk, something you
obviously want to happen. You can make the gap between checkpoints longer by
altering the recovery interval. However if you do that the checkpoints will
last longer when they do happen (they will have more to do) and your
transation logs will probably get bigger, and you system will take longer to
come up following a reboot.
About the only thing you can do is look at your disk configuration, to see
if there is a way to speed up your I/O processes.
Hope this helps
John
"George teVelde" wrote:
> Hello Everyone. I am log shippping on a server that has heavy reads and
> writes. The Log Ship process runs every 15 minutes and when it runs, it
> tends to significantly slow down all the queries running on the box. Queries
> which run 20-100 milliseconds run for over 2-3 seconds. The slowing causes
> are webservers to back up which in turn slows are website.
> I notice in PerMon that after every transaction log backup a checkpoint is
> run immedialty after.
> The queries are slow during the checkpoint process.
> Is there a reason for this? Also, how can I avoid this slow down.
> About the Server:
> Windows 2003 Enterprise Edition
> Quad processeor with Intel XEON 3.0 Ghz.
> SQL 2000 version 8.00.936
> Thanks,
> George|||Thanks for the reply, I have one more question.
Is there any reason Log Shipping would grab all the availble threads and not
release them?
I realize that it may not be the log shipping doing it, but I am trying to
eliminate as many variables as I can.
Thanks.|||Hi
No, no reason. If checkpointing affects your performance, the disk layout is
probably not optimal. Basic rule, Logs on a separate set of drive, not on
RAID-5, but on mirrors.
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/
"George teVelde" <GeorgeteVelde@.discussions.microsoft.com> wrote in message
news:69243841-B076-4990-84E1-4C38A7FA4548@.microsoft.com...
> Thanks for the reply, I have one more question.
> Is there any reason Log Shipping would grab all the availble threads and
not
> release them?
> I realize that it may not be the log shipping doing it, but I am trying to
> eliminate as many variables as I can.
> Thanks.

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 and purpose of the .tuf file

We have setup Log shipping on our production Database between two different
Data Centres in different cities. The process works well. All I want to know
,
is what is the purpose of the .tuf file?>> All I want to know, is what is the purpose of the .tuf file?
.tuf stands for Transaction Undo File. It is actually used while restoring
the transaction logs with the STANDBY option. Generally when you do a
transaction log restore, you can specify this file along with your RESTORE
LOG statement, for syntax details, refer to SQL Server Books Online.
Anith

Log Shipping and purpose of the .tuf file

We have setup Log shipping on our production Database between two different
Data Centres in different cities. The process works well. All I want to know,
is what is the purpose of the .tuf file?
>> All I want to know, is what is the purpose of the .tuf file?
..tuf stands for Transaction Undo File. It is actually used while restoring
the transaction logs with the STANDBY option. Generally when you do a
transaction log restore, you can specify this file along with your RESTORE
LOG statement, for syntax details, refer to SQL Server Books Online.
Anith

Log Shipping and purpose of the .tuf file

We have setup Log shipping on our production Database between two different
Data Centres in different cities. The process works well. All I want to know,
is what is the purpose of the .tuf file?>> All I want to know, is what is the purpose of the .tuf file?
.tuf stands for Transaction Undo File. It is actually used while restoring
the transaction logs with the STANDBY option. Generally when you do a
transaction log restore, you can specify this file along with your RESTORE
LOG statement, for syntax details, refer to SQL Server Books Online.
--
Anith