Guys,
Right after I setup up log shipping, there are a few jobs created under
job on the secondary server called "Log Shipping Alert Job - Backup"
and "Transaction Log Backup Job for DB Maintenance Plan...".
Without doing anything I would get a red "X", meaning failed on the
"Log Shipping Alert Job -Backup". When I run execute the "Transaction
Log Backup Job for DB Maintenance Plan...", it would fail too. This
is under the secondary server.
Is this normal? If not, how do i fix this? Do people actually backup
the transaction log on the secondary server on a log shipping?
Thanks,
Tonyhttp://www.sql-server-performance.c...og_shipping.asp
<tractng@.gmail.com> wrote in message
news:1147763695.248207.126980@.j33g2000cwa.googlegroups.com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||You cannot do any type of backup of a database restored using either NORECOV
ERY or STANDBY. But you
should be prepared to do backups of that database the minute this becomes th
e production database
(when a fail over is performed).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147763695.248207.126980@.j33g2000cwa.googlegroups.
com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||Tibor,
Just to clarify. You are saying I won't be able to do a backup when it
is in the standby state. When the fail over is performed, I should be
able to?
Thanks a lot,
Tony|||Yes.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147979332.349123.49520@.j55g2000cwa.googlegroups.c
om...
> Tibor,
> Just to clarify. You are saying I won't be able to do a backup when it
> is in the standby state. When the fail over is performed, I should be
> able to?
>
> Thanks a lot,
> Tony
>
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Friday, March 30, 2012
Log shipping Transactions Log backup on secondary server
Guys,
Right after I setup up log shipping, there are a few jobs created under
job on the secondary server called "Log Shipping Alert Job - Backup"
and "Transaction Log Backup Job for DB Maintenance Plan...".
Without doing anything I would get a red "X", meaning failed on the
"Log Shipping Alert Job -Backup". When I run execute the "Transaction
Log Backup Job for DB Maintenance Plan...", it would fail too. This
is under the secondary server.
Is this normal? If not, how do i fix this? Do people actually backup
the transaction log on the secondary server on a log shipping?
Thanks,
TonyYou cannot do any type of backup of a database restored using either NORECOVERY or STANDBY. But you
should be prepared to do backups of that database the minute this becomes the production database
(when a fail over is performed).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147763695.248207.126980@.j33g2000cwa.googlegroups.com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||http://www.sql-server-performance.com/sql_server_log_shipping.asp
<tractng@.gmail.com> wrote in message
news:1147763695.248207.126980@.j33g2000cwa.googlegroups.com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||Tibor,
Just to clarify. You are saying I won't be able to do a backup when it
is in the standby state. When the fail over is performed, I should be
able to?
Thanks a lot,
Tony|||Yes.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147979332.349123.49520@.j55g2000cwa.googlegroups.com...
> Tibor,
> Just to clarify. You are saying I won't be able to do a backup when it
> is in the standby state. When the fail over is performed, I should be
> able to?
>
> Thanks a lot,
> Tony
>
Right after I setup up log shipping, there are a few jobs created under
job on the secondary server called "Log Shipping Alert Job - Backup"
and "Transaction Log Backup Job for DB Maintenance Plan...".
Without doing anything I would get a red "X", meaning failed on the
"Log Shipping Alert Job -Backup". When I run execute the "Transaction
Log Backup Job for DB Maintenance Plan...", it would fail too. This
is under the secondary server.
Is this normal? If not, how do i fix this? Do people actually backup
the transaction log on the secondary server on a log shipping?
Thanks,
TonyYou cannot do any type of backup of a database restored using either NORECOVERY or STANDBY. But you
should be prepared to do backups of that database the minute this becomes the production database
(when a fail over is performed).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147763695.248207.126980@.j33g2000cwa.googlegroups.com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||http://www.sql-server-performance.com/sql_server_log_shipping.asp
<tractng@.gmail.com> wrote in message
news:1147763695.248207.126980@.j33g2000cwa.googlegroups.com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||Tibor,
Just to clarify. You are saying I won't be able to do a backup when it
is in the standby state. When the fail over is performed, I should be
able to?
Thanks a lot,
Tony|||Yes.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147979332.349123.49520@.j55g2000cwa.googlegroups.com...
> Tibor,
> Just to clarify. You are saying I won't be able to do a backup when it
> is in the standby state. When the fail over is performed, I should be
> able to?
>
> Thanks a lot,
> Tony
>
Monday, March 26, 2012
Log Shipping restore problem
I'm implementing SQL Server Log Shipping. I don't have
Enterprise, so I have to create my own jobs. I'm in the
step where I'm executing a store procedure on the stanby
server to restore the database and I get an error stating
that the database state cannot be change because it is in
used by other users. The exact error is at the bottom of
this message.
I'm not sure why I'm getting this and how to fix it.
Nobody else has access to this server but myself and the
database is set to DBO USE ONLY. I closed out
Enterprise manager and SQL Query Analyzer on the standby
server and I still get the error. Please help. The
exact error is:
Executed as user: sa. RESTORE DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013) Exclusive
access could not be obtained because the database is in
use. [SQLSTATE 42000] (Error 3101) ALTER DATABASE
statement failed. [SQLSTATE 42000] (Error 5069) Database
state cannot be changed while other users are using the
database 'myDBName' [SQLSTATE 42000] (Error 5070)
sp_dboption command failed. [SQLSTATE 01000] (Error
15627). The step failed.Before you restore, you need to make sure there's no one in the database.
You will have to kill all user connections in the database, if there are
any. More info can be found at:
http://vyaskn.tripod.com/administration_faq.htm#q16
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Vic" <vduran@.specpro-inc.com> wrote in message
news:017e01c3d93f$dd6bc360$a401280a@.phx.gbl...
I'm implementing SQL Server Log Shipping. I don't have
Enterprise, so I have to create my own jobs. I'm in the
step where I'm executing a store procedure on the stanby
server to restore the database and I get an error stating
that the database state cannot be change because it is in
used by other users. The exact error is at the bottom of
this message.
I'm not sure why I'm getting this and how to fix it.
Nobody else has access to this server but myself and the
database is set to DBO USE ONLY. I closed out
Enterprise manager and SQL Query Analyzer on the standby
server and I still get the error. Please help. The
exact error is:
Executed as user: sa. RESTORE DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013) Exclusive
access could not be obtained because the database is in
use. [SQLSTATE 42000] (Error 3101) ALTER DATABASE
statement failed. [SQLSTATE 42000] (Error 5069) Database
state cannot be changed while other users are using the
database 'myDBName' [SQLSTATE 42000] (Error 5070)
sp_dboption command failed. [SQLSTATE 01000] (Error
15627). The step failed.
Enterprise, so I have to create my own jobs. I'm in the
step where I'm executing a store procedure on the stanby
server to restore the database and I get an error stating
that the database state cannot be change because it is in
used by other users. The exact error is at the bottom of
this message.
I'm not sure why I'm getting this and how to fix it.
Nobody else has access to this server but myself and the
database is set to DBO USE ONLY. I closed out
Enterprise manager and SQL Query Analyzer on the standby
server and I still get the error. Please help. The
exact error is:
Executed as user: sa. RESTORE DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013) Exclusive
access could not be obtained because the database is in
use. [SQLSTATE 42000] (Error 3101) ALTER DATABASE
statement failed. [SQLSTATE 42000] (Error 5069) Database
state cannot be changed while other users are using the
database 'myDBName' [SQLSTATE 42000] (Error 5070)
sp_dboption command failed. [SQLSTATE 01000] (Error
15627). The step failed.Before you restore, you need to make sure there's no one in the database.
You will have to kill all user connections in the database, if there are
any. More info can be found at:
http://vyaskn.tripod.com/administration_faq.htm#q16
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Vic" <vduran@.specpro-inc.com> wrote in message
news:017e01c3d93f$dd6bc360$a401280a@.phx.gbl...
I'm implementing SQL Server Log Shipping. I don't have
Enterprise, so I have to create my own jobs. I'm in the
step where I'm executing a store procedure on the stanby
server to restore the database and I get an error stating
that the database state cannot be change because it is in
used by other users. The exact error is at the bottom of
this message.
I'm not sure why I'm getting this and how to fix it.
Nobody else has access to this server but myself and the
database is set to DBO USE ONLY. I closed out
Enterprise manager and SQL Query Analyzer on the standby
server and I still get the error. Please help. The
exact error is:
Executed as user: sa. RESTORE DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013) Exclusive
access could not be obtained because the database is in
use. [SQLSTATE 42000] (Error 3101) ALTER DATABASE
statement failed. [SQLSTATE 42000] (Error 5069) Database
state cannot be changed while other users are using the
database 'myDBName' [SQLSTATE 42000] (Error 5070)
sp_dboption command failed. [SQLSTATE 01000] (Error
15627). The step failed.
Log Shipping restore problem
I'm implementing SQL Server Log Shipping. I don't have
Enterprise, so I have to create my own jobs. I'm in the
step where I'm executing a store procedure on the stanby
server to restore the database and I get an error stating
that the database state cannot be change because it is in
used by other users. The exact error is at the bottom of
this message.
I'm not sure why I'm getting this and how to fix it.
Nobody else has access to this server but myself and the
database is set to DBO USE ONLY. I closed out
Enterprise manager and SQL Query Analyzer on the standby
server and I still get the error. Please help. The
exact error is:
Executed as user: sa. RESTORE DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013) Exclusive
access could not be obtained because the database is in
use. [SQLSTATE 42000] (Error 3101) ALTER DATABASE
statement failed. [SQLSTATE 42000] (Error 5069) Database
state cannot be changed while other users are using the
database 'myDBName' [SQLSTATE 42000] (Error 5070)
sp_dboption command failed. [SQLSTATE 01000] (Error
15627). The step failed.Before you restore, you need to make sure there's no one in the database.
You will have to kill all user connections in the database, if there are
any. More info can be found at:
http://vyaskn.tripod.com/administration_faq.htm#q16
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Vic" <vduran@.specpro-inc.com> wrote in message
news:017e01c3d93f$dd6bc360$a401280a@.phx.gbl...
I'm implementing SQL Server Log Shipping. I don't have
Enterprise, so I have to create my own jobs. I'm in the
step where I'm executing a store procedure on the stanby
server to restore the database and I get an error stating
that the database state cannot be change because it is in
used by other users. The exact error is at the bottom of
this message.
I'm not sure why I'm getting this and how to fix it.
Nobody else has access to this server but myself and the
database is set to DBO USE ONLY. I closed out
Enterprise manager and SQL Query Analyzer on the standby
server and I still get the error. Please help. The
exact error is:
Executed as user: sa. RESTORE DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013) Exclusive
access could not be obtained because the database is in
use. [SQLSTATE 42000] (Error 3101) ALTER DATABASE
statement failed. [SQLSTATE 42000] (Error 5069) Database
state cannot be changed while other users are using the
database 'myDBName' [SQLSTATE 42000] (Error 5070)
sp_dboption command failed. [SQLSTATE 01000] (Error
15627). The step failed.sql
Enterprise, so I have to create my own jobs. I'm in the
step where I'm executing a store procedure on the stanby
server to restore the database and I get an error stating
that the database state cannot be change because it is in
used by other users. The exact error is at the bottom of
this message.
I'm not sure why I'm getting this and how to fix it.
Nobody else has access to this server but myself and the
database is set to DBO USE ONLY. I closed out
Enterprise manager and SQL Query Analyzer on the standby
server and I still get the error. Please help. The
exact error is:
Executed as user: sa. RESTORE DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013) Exclusive
access could not be obtained because the database is in
use. [SQLSTATE 42000] (Error 3101) ALTER DATABASE
statement failed. [SQLSTATE 42000] (Error 5069) Database
state cannot be changed while other users are using the
database 'myDBName' [SQLSTATE 42000] (Error 5070)
sp_dboption command failed. [SQLSTATE 01000] (Error
15627). The step failed.Before you restore, you need to make sure there's no one in the database.
You will have to kill all user connections in the database, if there are
any. More info can be found at:
http://vyaskn.tripod.com/administration_faq.htm#q16
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Vic" <vduran@.specpro-inc.com> wrote in message
news:017e01c3d93f$dd6bc360$a401280a@.phx.gbl...
I'm implementing SQL Server Log Shipping. I don't have
Enterprise, so I have to create my own jobs. I'm in the
step where I'm executing a store procedure on the stanby
server to restore the database and I get an error stating
that the database state cannot be change because it is in
used by other users. The exact error is at the bottom of
this message.
I'm not sure why I'm getting this and how to fix it.
Nobody else has access to this server but myself and the
database is set to DBO USE ONLY. I closed out
Enterprise manager and SQL Query Analyzer on the standby
server and I still get the error. Please help. The
exact error is:
Executed as user: sa. RESTORE DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013) Exclusive
access could not be obtained because the database is in
use. [SQLSTATE 42000] (Error 3101) ALTER DATABASE
statement failed. [SQLSTATE 42000] (Error 5069) Database
state cannot be changed while other users are using the
database 'myDBName' [SQLSTATE 42000] (Error 5070)
sp_dboption command failed. [SQLSTATE 01000] (Error
15627). The step failed.sql
Friday, March 23, 2012
Log Shipping Problem
I have a warm standby 2003 Server and am trying to set up log shipping. I am
working with SQL Server 2005 and have created the log shipping jobs using the
wizard. Initially as suggested in the documentation, I backed up the primary
database using norecover options. I resored the database on the secondary to
overwrite the existing database with recovery and standby options which has
left the secondary database in Standby/Read-Only mode. All the the log
shipping job history on the primary and secondary servers show success (even
the restore on the secondary). When I insert records into tables on the
primary I do not see them appear in the secondary database after the restore
job executes. I don't have much experience with log shipping or partial
restores from log files for that matter, I have always done full restores
with no recovery. Why don't I see the new records in the secondary database
after a successful restore (according to job history). I can see the .trn
files in the shipped log file directory, how does this process work, does it
take a restore with norecovery before you can see them in the secondary
database? There is nothing in the documentation that indicates this, I'm
missing something here ... I guess it has something to do with partial
restores. What am I doing wrong.
Fran Morabito wrote:
> I have a warm standby 2003 Server and am trying to set up log shipping. I am
> working with SQL Server 2005 and have created the log shipping jobs using the
> wizard. Initially as suggested in the documentation, I backed up the primary
> database using norecover options. I resored the database on the secondary to
> overwrite the existing database with recovery and standby options which has
> left the secondary database in Standby/Read-Only mode. All the the log
> shipping job history on the primary and secondary servers show success (even
> the restore on the secondary). When I insert records into tables on the
> primary I do not see them appear in the secondary database after the restore
> job executes. I don't have much experience with log shipping or partial
> restores from log files for that matter, I have always done full restores
> with no recovery. Why don't I see the new records in the secondary database
> after a successful restore (according to job history). I can see the .trn
> files in the shipped log file directory, how does this process work, does it
> take a restore with norecovery before you can see them in the secondary
> database? There is nothing in the documentation that indicates this, I'm
> missing something here ... I guess it has something to do with partial
> restores. What am I doing wrong.
>
I don't know anything about the log shipping wizard, I've always rolled
my own log shipping routines. It's a pretty simple process:
1. Start with a full backup of the live database
2. Restore full backup to standby using WITH NORECOVERY option
3. Schedule frequent transaction log backups of the live database,
preferrably writing each backup to a seperate file
4. Monitor for new transaction log backups, when found, restore to
standby using WITH NORECOVERY option.
I would start by making sure your transaction log backups are occurring
on the live server, and that they are being restored on the standby server.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
working with SQL Server 2005 and have created the log shipping jobs using the
wizard. Initially as suggested in the documentation, I backed up the primary
database using norecover options. I resored the database on the secondary to
overwrite the existing database with recovery and standby options which has
left the secondary database in Standby/Read-Only mode. All the the log
shipping job history on the primary and secondary servers show success (even
the restore on the secondary). When I insert records into tables on the
primary I do not see them appear in the secondary database after the restore
job executes. I don't have much experience with log shipping or partial
restores from log files for that matter, I have always done full restores
with no recovery. Why don't I see the new records in the secondary database
after a successful restore (according to job history). I can see the .trn
files in the shipped log file directory, how does this process work, does it
take a restore with norecovery before you can see them in the secondary
database? There is nothing in the documentation that indicates this, I'm
missing something here ... I guess it has something to do with partial
restores. What am I doing wrong.
Fran Morabito wrote:
> I have a warm standby 2003 Server and am trying to set up log shipping. I am
> working with SQL Server 2005 and have created the log shipping jobs using the
> wizard. Initially as suggested in the documentation, I backed up the primary
> database using norecover options. I resored the database on the secondary to
> overwrite the existing database with recovery and standby options which has
> left the secondary database in Standby/Read-Only mode. All the the log
> shipping job history on the primary and secondary servers show success (even
> the restore on the secondary). When I insert records into tables on the
> primary I do not see them appear in the secondary database after the restore
> job executes. I don't have much experience with log shipping or partial
> restores from log files for that matter, I have always done full restores
> with no recovery. Why don't I see the new records in the secondary database
> after a successful restore (according to job history). I can see the .trn
> files in the shipped log file directory, how does this process work, does it
> take a restore with norecovery before you can see them in the secondary
> database? There is nothing in the documentation that indicates this, I'm
> missing something here ... I guess it has something to do with partial
> restores. What am I doing wrong.
>
I don't know anything about the log shipping wizard, I've always rolled
my own log shipping routines. It's a pretty simple process:
1. Start with a full backup of the live database
2. Restore full backup to standby using WITH NORECOVERY option
3. Schedule frequent transaction log backups of the live database,
preferrably writing each backup to a seperate file
4. Monitor for new transaction log backups, when found, restore to
standby using WITH NORECOVERY option.
I would start by making sure your transaction log backups are occurring
on the live server, and that they are being restored on the standby server.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Log Shipping Problem
I have a warm standby 2003 Server and am trying to set up log shipping. I am
working with SQL Server 2005 and have created the log shipping jobs using th
e
wizard. Initially as suggested in the documentation, I backed up the primary
database using norecover options. I resored the database on the secondary to
overwrite the existing database with recovery and standby options which has
left the secondary database in Standby/Read-Only mode. All the the log
shipping job history on the primary and secondary servers show success (even
the restore on the secondary). When I insert records into tables on the
primary I do not see them appear in the secondary database after the restore
job executes. I don't have much experience with log shipping or partial
restores from log files for that matter, I have always done full restores
with no recovery. Why don't I see the new records in the secondary database
after a successful restore (according to job history). I can see the .trn
files in the shipped log file directory, how does this process work, does it
take a restore with norecovery before you can see them in the secondary
database? There is nothing in the documentation that indicates this, I'm
missing something here ... I guess it has something to do with partial
restores. What am I doing wrong.Fran Morabito wrote:
> I have a warm standby 2003 Server and am trying to set up log shipping. I
am
> working with SQL Server 2005 and have created the log shipping jobs using
the
> wizard. Initially as suggested in the documentation, I backed up the prima
ry
> database using norecover options. I resored the database on the secondary
to
> overwrite the existing database with recovery and standby options which ha
s
> left the secondary database in Standby/Read-Only mode. All the the log
> shipping job history on the primary and secondary servers show success (ev
en
> the restore on the secondary). When I insert records into tables on the
> primary I do not see them appear in the secondary database after the resto
re
> job executes. I don't have much experience with log shipping or partial
> restores from log files for that matter, I have always done full restores
> with no recovery. Why don't I see the new records in the secondary databas
e
> after a successful restore (according to job history). I can see the .trn
> files in the shipped log file directory, how does this process work, does
it
> take a restore with norecovery before you can see them in the secondary
> database? There is nothing in the documentation that indicates this, I'm
> missing something here ... I guess it has something to do with partial
> restores. What am I doing wrong.
>
I don't know anything about the log shipping wizard, I've always rolled
my own log shipping routines. It's a pretty simple process:
1. Start with a full backup of the live database
2. Restore full backup to standby using WITH NORECOVERY option
3. Schedule frequent transaction log backups of the live database,
preferrably writing each backup to a seperate file
4. Monitor for new transaction log backups, when found, restore to
standby using WITH NORECOVERY option.
I would start by making sure your transaction log backups are occurring
on the live server, and that they are being restored on the standby server.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
working with SQL Server 2005 and have created the log shipping jobs using th
e
wizard. Initially as suggested in the documentation, I backed up the primary
database using norecover options. I resored the database on the secondary to
overwrite the existing database with recovery and standby options which has
left the secondary database in Standby/Read-Only mode. All the the log
shipping job history on the primary and secondary servers show success (even
the restore on the secondary). When I insert records into tables on the
primary I do not see them appear in the secondary database after the restore
job executes. I don't have much experience with log shipping or partial
restores from log files for that matter, I have always done full restores
with no recovery. Why don't I see the new records in the secondary database
after a successful restore (according to job history). I can see the .trn
files in the shipped log file directory, how does this process work, does it
take a restore with norecovery before you can see them in the secondary
database? There is nothing in the documentation that indicates this, I'm
missing something here ... I guess it has something to do with partial
restores. What am I doing wrong.Fran Morabito wrote:
> I have a warm standby 2003 Server and am trying to set up log shipping. I
am
> working with SQL Server 2005 and have created the log shipping jobs using
the
> wizard. Initially as suggested in the documentation, I backed up the prima
ry
> database using norecover options. I resored the database on the secondary
to
> overwrite the existing database with recovery and standby options which ha
s
> left the secondary database in Standby/Read-Only mode. All the the log
> shipping job history on the primary and secondary servers show success (ev
en
> the restore on the secondary). When I insert records into tables on the
> primary I do not see them appear in the secondary database after the resto
re
> job executes. I don't have much experience with log shipping or partial
> restores from log files for that matter, I have always done full restores
> with no recovery. Why don't I see the new records in the secondary databas
e
> after a successful restore (according to job history). I can see the .trn
> files in the shipped log file directory, how does this process work, does
it
> take a restore with norecovery before you can see them in the secondary
> database? There is nothing in the documentation that indicates this, I'm
> missing something here ... I guess it has something to do with partial
> restores. What am I doing wrong.
>
I don't know anything about the log shipping wizard, I've always rolled
my own log shipping routines. It's a pretty simple process:
1. Start with a full backup of the live database
2. Restore full backup to standby using WITH NORECOVERY option
3. Schedule frequent transaction log backups of the live database,
preferrably writing each backup to a seperate file
4. Monitor for new transaction log backups, when found, restore to
standby using WITH NORECOVERY option.
I would start by making sure your transaction log backups are occurring
on the live server, and that they are being restored on the standby server.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Log Shipping Problem
I have a warm standby 2003 Server and am trying to set up log shipping. I am
working with SQL Server 2005 and have created the log shipping jobs using the
wizard. Initially as suggested in the documentation, I backed up the primary
database using norecover options. I resored the database on the secondary to
overwrite the existing database with recovery and standby options which has
left the secondary database in Standby/Read-Only mode. All the the log
shipping job history on the primary and secondary servers show success (even
the restore on the secondary). When I insert records into tables on the
primary I do not see them appear in the secondary database after the restore
job executes. I don't have much experience with log shipping or partial
restores from log files for that matter, I have always done full restores
with no recovery. Why don't I see the new records in the secondary database
after a successful restore (according to job history). I can see the .trn
files in the shipped log file directory, how does this process work, does it
take a restore with norecovery before you can see them in the secondary
database? There is nothing in the documentation that indicates this, I'm
missing something here ... I guess it has something to do with partial
restores. What am I doing wrong.Fran Morabito wrote:
> I have a warm standby 2003 Server and am trying to set up log shipping. I am
> working with SQL Server 2005 and have created the log shipping jobs using the
> wizard. Initially as suggested in the documentation, I backed up the primary
> database using norecover options. I resored the database on the secondary to
> overwrite the existing database with recovery and standby options which has
> left the secondary database in Standby/Read-Only mode. All the the log
> shipping job history on the primary and secondary servers show success (even
> the restore on the secondary). When I insert records into tables on the
> primary I do not see them appear in the secondary database after the restore
> job executes. I don't have much experience with log shipping or partial
> restores from log files for that matter, I have always done full restores
> with no recovery. Why don't I see the new records in the secondary database
> after a successful restore (according to job history). I can see the .trn
> files in the shipped log file directory, how does this process work, does it
> take a restore with norecovery before you can see them in the secondary
> database? There is nothing in the documentation that indicates this, I'm
> missing something here ... I guess it has something to do with partial
> restores. What am I doing wrong.
>
I don't know anything about the log shipping wizard, I've always rolled
my own log shipping routines. It's a pretty simple process:
1. Start with a full backup of the live database
2. Restore full backup to standby using WITH NORECOVERY option
3. Schedule frequent transaction log backups of the live database,
preferrably writing each backup to a seperate file
4. Monitor for new transaction log backups, when found, restore to
standby using WITH NORECOVERY option.
I would start by making sure your transaction log backups are occurring
on the live server, and that they are being restored on the standby server.
Tracy McKibben
MCDBA
http://www.realsqlguy.comsql
working with SQL Server 2005 and have created the log shipping jobs using the
wizard. Initially as suggested in the documentation, I backed up the primary
database using norecover options. I resored the database on the secondary to
overwrite the existing database with recovery and standby options which has
left the secondary database in Standby/Read-Only mode. All the the log
shipping job history on the primary and secondary servers show success (even
the restore on the secondary). When I insert records into tables on the
primary I do not see them appear in the secondary database after the restore
job executes. I don't have much experience with log shipping or partial
restores from log files for that matter, I have always done full restores
with no recovery. Why don't I see the new records in the secondary database
after a successful restore (according to job history). I can see the .trn
files in the shipped log file directory, how does this process work, does it
take a restore with norecovery before you can see them in the secondary
database? There is nothing in the documentation that indicates this, I'm
missing something here ... I guess it has something to do with partial
restores. What am I doing wrong.Fran Morabito wrote:
> I have a warm standby 2003 Server and am trying to set up log shipping. I am
> working with SQL Server 2005 and have created the log shipping jobs using the
> wizard. Initially as suggested in the documentation, I backed up the primary
> database using norecover options. I resored the database on the secondary to
> overwrite the existing database with recovery and standby options which has
> left the secondary database in Standby/Read-Only mode. All the the log
> shipping job history on the primary and secondary servers show success (even
> the restore on the secondary). When I insert records into tables on the
> primary I do not see them appear in the secondary database after the restore
> job executes. I don't have much experience with log shipping or partial
> restores from log files for that matter, I have always done full restores
> with no recovery. Why don't I see the new records in the secondary database
> after a successful restore (according to job history). I can see the .trn
> files in the shipped log file directory, how does this process work, does it
> take a restore with norecovery before you can see them in the secondary
> database? There is nothing in the documentation that indicates this, I'm
> missing something here ... I guess it has something to do with partial
> restores. What am I doing wrong.
>
I don't know anything about the log shipping wizard, I've always rolled
my own log shipping routines. It's a pretty simple process:
1. Start with a full backup of the live database
2. Restore full backup to standby using WITH NORECOVERY option
3. Schedule frequent transaction log backups of the live database,
preferrably writing each backup to a seperate file
4. Monitor for new transaction log backups, when found, restore to
standby using WITH NORECOVERY option.
I would start by making sure your transaction log backups are occurring
on the live server, and that they are being restored on the standby server.
Tracy McKibben
MCDBA
http://www.realsqlguy.comsql
Wednesday, March 21, 2012
Log shipping not work, but jobs say successful
I have a pretty standard log shipping arrangement created with the Log
Shipping wizard against an existing database on the standby server. All the
jobs were created successfully and run on the correct schedule. However,
the copy job on the standby server doesn't work. It shows that it ran
successfully, but the files just aren't copied to the standby server's
directory, and so are not restored. After manually copying the transaction
log files to the standby server, the restore job will work. However, the
next log in sequence will not copy over.
The maintenance plan history shows no errors.
Both servers are running Windows 2000 servers and SQL Server 2000 Enterprise
SP3a. The link is a 45 Mbit leased line.
What could be the problem?
Thanks,
RS
RS,
usually this is a problem with the paths - the wizard is not very intuitive
and it's quite easy to set them incorrectly. On the screen that says
'Specify the Transaction Log Share', you must identify the file share on the
primary server and when setting up the destination, the name is a local
pathname, not a file share. If this is incorrect, there will be no errors
and the monitor will show continually the first setup file as being
transferred. So, initially check that you have a share on the primary server
and the logs are getting there.
HTH,
Paul Ibison
sql
Shipping wizard against an existing database on the standby server. All the
jobs were created successfully and run on the correct schedule. However,
the copy job on the standby server doesn't work. It shows that it ran
successfully, but the files just aren't copied to the standby server's
directory, and so are not restored. After manually copying the transaction
log files to the standby server, the restore job will work. However, the
next log in sequence will not copy over.
The maintenance plan history shows no errors.
Both servers are running Windows 2000 servers and SQL Server 2000 Enterprise
SP3a. The link is a 45 Mbit leased line.
What could be the problem?
Thanks,
RS
RS,
usually this is a problem with the paths - the wizard is not very intuitive
and it's quite easy to set them incorrectly. On the screen that says
'Specify the Transaction Log Share', you must identify the file share on the
primary server and when setting up the destination, the name is a local
pathname, not a file share. If this is incorrect, there will be no errors
and the monitor will show continually the first setup file as being
transferred. So, initially check that you have a share on the primary server
and the logs are getting there.
HTH,
Paul Ibison
sql
Monday, March 19, 2012
Log Shipping Jobs please help us (Urgent need)
Hi,
When i am changing Log Shipping job owner in Monitor server, stand by server
and primary server, i am getting error as "Error 14269:Job 'Log shipping
alert job-backup' is already targetted at server. xxxxxx(SQL Instance) The
Job was not saved.
please advise how to chnage the Job owners, if we are getting these errors.
Thanks,
John
All, i am working with MS Support now for this error. we analyzed due to
sp_add_job and other related stored procedures does not take instance name
more than 30 chars (our servers have more than 30 chars).
so when ever we are setting up Log shipping or replication, shall we need
our SQL Intance should be lesthan 30 character? my friend is telling for
Oracle databases they dont have any problem with intance name length.
hope this scenario may help someone in future.
good lcuk to all, John
"John" wrote:
> Hi,
> When i am changing Log Shipping job owner in Monitor server, stand by server
> and primary server, i am getting error as "Error 14269:Job 'Log shipping
> alert job-backup' is already targetted at server. xxxxxx(SQL Instance) The
> Job was not saved.
> please advise how to chnage the Job owners, if we are getting these errors.
> Thanks,
> John
|||John,
You could create aliases with shorter names. Open the client network
utility and go to Aliases.
M
When i am changing Log Shipping job owner in Monitor server, stand by server
and primary server, i am getting error as "Error 14269:Job 'Log shipping
alert job-backup' is already targetted at server. xxxxxx(SQL Instance) The
Job was not saved.
please advise how to chnage the Job owners, if we are getting these errors.
Thanks,
John
All, i am working with MS Support now for this error. we analyzed due to
sp_add_job and other related stored procedures does not take instance name
more than 30 chars (our servers have more than 30 chars).
so when ever we are setting up Log shipping or replication, shall we need
our SQL Intance should be lesthan 30 character? my friend is telling for
Oracle databases they dont have any problem with intance name length.
hope this scenario may help someone in future.
good lcuk to all, John
"John" wrote:
> Hi,
> When i am changing Log Shipping job owner in Monitor server, stand by server
> and primary server, i am getting error as "Error 14269:Job 'Log shipping
> alert job-backup' is already targetted at server. xxxxxx(SQL Instance) The
> Job was not saved.
> please advise how to chnage the Job owners, if we are getting these errors.
> Thanks,
> John
|||John,
You could create aliases with shorter names. Open the client network
utility and go to Aliases.
M
log shipping job
does anyone know about these tables on msdb: backup_movement_plans and
backup_movement_plan_database? Are they related to log shipping jobs? When we
create the log shipping jobs(copy and load) using script, how the data in
those tables get populated? and how the job know to retreive the data from
the tables? thanksI don't think these tables have anything to do with log shipping. Do you
have any third party applications running on or accessing the database?
Perhaps one such application might have added these tables for handling some
administrative tasks.
--
Anith|||Just found that these are tables from SQL Server 7.0 version which I hadn't
thought about before. Yes, these are valid log shipping related tables in
SQL Server 7.0. The log shipping scheme has changed considerably with SQL
2000 however.
Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
might find some more details about these tables.
--
Anith|||we are currently on 2000 SE version, since has no EE, we have to create the
jobs to do log shipping (copy and load), so do those tables need to manually
created also? thanks
"Anith Sen" wrote:
> Just found that these are tables from SQL Server 7.0 version which I hadn't
> thought about before. Yes, these are valid log shipping related tables in
> SQL Server 7.0. The log shipping scheme has changed considerably with SQL
> 2000 however.
> Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
> might find some more details about these tables.
> --
> Anith
>
>
backup_movement_plan_database? Are they related to log shipping jobs? When we
create the log shipping jobs(copy and load) using script, how the data in
those tables get populated? and how the job know to retreive the data from
the tables? thanksI don't think these tables have anything to do with log shipping. Do you
have any third party applications running on or accessing the database?
Perhaps one such application might have added these tables for handling some
administrative tasks.
--
Anith|||Just found that these are tables from SQL Server 7.0 version which I hadn't
thought about before. Yes, these are valid log shipping related tables in
SQL Server 7.0. The log shipping scheme has changed considerably with SQL
2000 however.
Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
might find some more details about these tables.
--
Anith|||we are currently on 2000 SE version, since has no EE, we have to create the
jobs to do log shipping (copy and load), so do those tables need to manually
created also? thanks
"Anith Sen" wrote:
> Just found that these are tables from SQL Server 7.0 version which I hadn't
> thought about before. Yes, these are valid log shipping related tables in
> SQL Server 7.0. The log shipping scheme has changed considerably with SQL
> 2000 however.
> Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
> might find some more details about these tables.
> --
> Anith
>
>
log shipping job
does anyone know about these tables on msdb: backup_movement_plans and
backup_movement_plan_database? Are they related to log shipping jobs? When we
create the log shipping jobs(copy and load) using script, how the data in
those tables get populated? and how the job know to retreive the data from
the tables? thanks
I don't think these tables have anything to do with log shipping. Do you
have any third party applications running on or accessing the database?
Perhaps one such application might have added these tables for handling some
administrative tasks.
Anith
|||Just found that these are tables from SQL Server 7.0 version which I hadn't
thought about before. Yes, these are valid log shipping related tables in
SQL Server 7.0. The log shipping scheme has changed considerably with SQL
2000 however.
Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
might find some more details about these tables.
Anith
|||we are currently on 2000 SE version, since has no EE, we have to create the
jobs to do log shipping (copy and load), so do those tables need to manually
created also? thanks
"Anith Sen" wrote:
> Just found that these are tables from SQL Server 7.0 version which I hadn't
> thought about before. Yes, these are valid log shipping related tables in
> SQL Server 7.0. The log shipping scheme has changed considerably with SQL
> 2000 however.
> Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
> might find some more details about these tables.
> --
> Anith
>
>
backup_movement_plan_database? Are they related to log shipping jobs? When we
create the log shipping jobs(copy and load) using script, how the data in
those tables get populated? and how the job know to retreive the data from
the tables? thanks
I don't think these tables have anything to do with log shipping. Do you
have any third party applications running on or accessing the database?
Perhaps one such application might have added these tables for handling some
administrative tasks.
Anith
|||Just found that these are tables from SQL Server 7.0 version which I hadn't
thought about before. Yes, these are valid log shipping related tables in
SQL Server 7.0. The log shipping scheme has changed considerably with SQL
2000 however.
Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
might find some more details about these tables.
Anith
|||we are currently on 2000 SE version, since has no EE, we have to create the
jobs to do log shipping (copy and load), so do those tables need to manually
created also? thanks
"Anith Sen" wrote:
> Just found that these are tables from SQL Server 7.0 version which I hadn't
> thought about before. Yes, these are valid log shipping related tables in
> SQL Server 7.0. The log shipping scheme has changed considerably with SQL
> 2000 however.
> Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
> might find some more details about these tables.
> --
> Anith
>
>
Monday, March 12, 2012
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
Wednesday, March 7, 2012
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:
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:
Friday, February 24, 2012
Log Shipping and Backup Jobs = Conflict?
Can we run log shipping alongside our backup plan?
The concern is that the full backup runs overnight and
then diff backups run during the day and at the same time
log shipping occurs every 30 mins - don't both jobs
require the resetting of the archive bit specifying when
the last trn backup took place?
Many thanks in advance for the help, Rgds, Simon.As long as the ONLY log backups are done through log shipping you should be
fine...Whole and differential backups do NOT affect the transaction log...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:2494501c46018$ae3cd380$a601280a@.phx
.gbl...
> Can we run log shipping alongside our backup plan?
> The concern is that the full backup runs overnight and
> then diff backups run during the day and at the same time
> log shipping occurs every 30 mins - don't both jobs
> require the resetting of the archive bit specifying when
> the last trn backup took place?
> Many thanks in advance for the help, Rgds, Simon.
The concern is that the full backup runs overnight and
then diff backups run during the day and at the same time
log shipping occurs every 30 mins - don't both jobs
require the resetting of the archive bit specifying when
the last trn backup took place?
Many thanks in advance for the help, Rgds, Simon.As long as the ONLY log backups are done through log shipping you should be
fine...Whole and differential backups do NOT affect the transaction log...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:2494501c46018$ae3cd380$a601280a@.phx
.gbl...
> Can we run log shipping alongside our backup plan?
> The concern is that the full backup runs overnight and
> then diff backups run during the day and at the same time
> log shipping occurs every 30 mins - don't both jobs
> require the resetting of the archive bit specifying when
> the last trn backup took place?
> Many thanks in advance for the help, Rgds, Simon.
Log Shipping and Backup Jobs = Conflict?
Can we run log shipping alongside our backup plan?
The concern is that the full backup runs overnight and
then diff backups run during the day and at the same time
log shipping occurs every 30 mins - don't both jobs
require the resetting of the archive bit specifying when
the last trn backup took place?
Many thanks in advance for the help, Rgds, Simon.
As long as the ONLY log backups are done through log shipping you should be
fine...Whole and differential backups do NOT affect the transaction log...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:2494501c46018$ae3cd380$a601280a@.phx.gbl...
> Can we run log shipping alongside our backup plan?
> The concern is that the full backup runs overnight and
> then diff backups run during the day and at the same time
> log shipping occurs every 30 mins - don't both jobs
> require the resetting of the archive bit specifying when
> the last trn backup took place?
> Many thanks in advance for the help, Rgds, Simon.
The concern is that the full backup runs overnight and
then diff backups run during the day and at the same time
log shipping occurs every 30 mins - don't both jobs
require the resetting of the archive bit specifying when
the last trn backup took place?
Many thanks in advance for the help, Rgds, Simon.
As long as the ONLY log backups are done through log shipping you should be
fine...Whole and differential backups do NOT affect the transaction log...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:2494501c46018$ae3cd380$a601280a@.phx.gbl...
> Can we run log shipping alongside our backup plan?
> The concern is that the full backup runs overnight and
> then diff backups run during the day and at the same time
> log shipping occurs every 30 mins - don't both jobs
> require the resetting of the archive bit specifying when
> the last trn backup took place?
> Many thanks in advance for the help, Rgds, Simon.
Log Shipping and Backup Jobs = Conflict?
Can we run log shipping alongside our backup plan?
The concern is that the full backup runs overnight and
then diff backups run during the day and at the same time
log shipping occurs every 30 mins - don't both jobs
require the resetting of the archive bit specifying when
the last trn backup took place?
Many thanks in advance for the help, Rgds, Simon.As long as the ONLY log backups are done through log shipping you should be
fine...Whole and differential backups do NOT affect the transaction log...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:2494501c46018$ae3cd380$a601280a@.phx.gbl...
> Can we run log shipping alongside our backup plan?
> The concern is that the full backup runs overnight and
> then diff backups run during the day and at the same time
> log shipping occurs every 30 mins - don't both jobs
> require the resetting of the archive bit specifying when
> the last trn backup took place?
> Many thanks in advance for the help, Rgds, Simon.
The concern is that the full backup runs overnight and
then diff backups run during the day and at the same time
log shipping occurs every 30 mins - don't both jobs
require the resetting of the archive bit specifying when
the last trn backup took place?
Many thanks in advance for the help, Rgds, Simon.As long as the ONLY log backups are done through log shipping you should be
fine...Whole and differential backups do NOT affect the transaction log...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:2494501c46018$ae3cd380$a601280a@.phx.gbl...
> Can we run log shipping alongside our backup plan?
> The concern is that the full backup runs overnight and
> then diff backups run during the day and at the same time
> log shipping occurs every 30 mins - don't both jobs
> require the resetting of the archive bit specifying when
> the last trn backup took place?
> Many thanks in advance for the help, Rgds, Simon.
Subscribe to:
Posts (Atom)