Log shipping with clustering

We would like to implement 2 node active-passive clustering coupled
with log shipping. Clustering is for high availability and log
shipping for DR purpose. Do we have any white papers for this kind of
setup? Is it possible to host the log shiiping secondary database on
the inactive cluster server? Thouigh it doesn't server the DR purpose,
we are exploring all different methods. Please share your ideas
barbara wrote:
> We would like to implement 2 node active-passive clustering coupled
> with log shipping. Clustering is for high availability and log
> shipping for DR purpose. Do we have any white papers for this kind of
> setup?
SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
How to setup Log Shipping
http://support.microsoft.com/support...ppingFinal.asp
SQL Server Resource Kit (Part 4 is dedicated to Hig Availability)
http://www.microsoft.com/resources/d...s/default.mspx
SQL Server High Availability Resources
http://www.microsoft.com/sql/techinf...ailability.asp

> Is it possible to host the log shiiping secondary database on
> the inactive cluster server?
Yes, you can setup a stand-alone istance and ship one (or more) clustered
database to this istance but is preferable to setup an external box for log
shipping purpose

> Thouigh it doesn't server the DR purpose,
> we are exploring all different methods. Please share your ideas
Log Shipping can increase high availabilty because it reduce the time to
became operational when a disaster on primary server happen. In particular
Clustering
- high level of fault tolerance
- automatic failure
- high cost
Log shipping
- manual failure
- scale out (you can use secondary server as read-only server)
- low cost
Clustering increase the availability but Log Shipping reduce down-time if a
failure occur
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
http://italy.mvps.org
|||Luca,
Thanks for the info. I've looked at all these articles before. If I
create standby on same server as cluser node (business doesn't want to
spend on another server), how do I failover to this? How does the
client connects to
standby? What name does it uses because the cluster node also exists
on the same server.
"Luca Bianchi" <rightjoinREMOVE_THIS@.hotmail.com> wrote in message news:<2qajjjFs3b8qU1@.uni-berlin.de>...
> barbara wrote:
> SQL Server 2000 Failover Clustering
> http://www.microsoft.com/technet/pro.../failclus.mspx
> How to setup Log Shipping
> http://support.microsoft.com/support...ppingFinal.asp
> SQL Server Resource Kit (Part 4 is dedicated to Hig Availability)
> http://www.microsoft.com/resources/d...s/default.mspx
> SQL Server High Availability Resources
> http://www.microsoft.com/sql/techinf...ailability.asp
>
> Yes, you can setup a stand-alone istance and ship one (or more) clustered
> database to this istance but is preferable to setup an external box for log
> shipping purpose
>
> Log Shipping can increase high availabilty because it reduce the time to
> became operational when a disaster on primary server happen. In particular
> Clustering
> - high level of fault tolerance
> - automatic failure
> - high cost
> Log shipping
> - manual failure
> - scale out (you can use secondary server as read-only server)
> - low cost
> Clustering increase the availability but Log Shipping reduce down-time if a
> failure occur
> Bye
|||I am confused? What would you gain in availability by log shipping to
another cluster node? I would log ship to another (possibly lower
performing) server in another location. Copying data in a tight circle
won't really gain anything in availability, which is the real goal here.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"barbara" <barbara_2003@.hotmail.com> wrote in message
news:5cd01256.0409091029.5a87adcc@.posting.google.c om...
> Luca,
> Thanks for the info. I've looked at all these articles before. If I
> create standby on same server as cluser node (business doesn't want to
> spend on another server), how do I failover to this? How does the
> client connects to
> standby? What name does it uses because the cluster node also exists
> on the same server.
>
> "Luca Bianchi" <rightjoinREMOVE_THIS@.hotmail.com> wrote in message
news:<2qajjjFs3b8qU1@.uni-berlin.de>...[vbcol=seagreen]
http://www.microsoft.com/technet/pro.../failclus.mspx[vbcol=seagreen]
http://support.microsoft.com/support...ppingFinal.asp[vbcol=seagreen]
http://www.microsoft.com/resources/d...s/default.mspx[vbcol=seagreen]
http://www.microsoft.com/sql/techinf...ailability.asp[vbcol=seagreen]
clustered[vbcol=seagreen]
log[vbcol=seagreen]
particular[vbcol=seagreen]
if a[vbcol=seagreen]
|||"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:epFRtxplEHA.2968@.TK2MSFTNGP14.phx.gbl...
> I am confused? What would you gain in availability by log shipping to
> another cluster node? I would log ship to another (possibly lower
> performing) server in another location. Copying data in a tight circle
> won't really gain anything in availability, which is the real goal here.
>
Actually I can think of a case.... physical disk corruption.
We have a DB where one block of data on teh disk has a bad CRC. This
prevents backups, etc.
We didn't realize the extent of the problem until too late so a restore from
a recent backup is not possible.
In this situation, something like what barbara's proposing might have been
very useful to us.
Having said that, log-shipping to a different machine is even better.
[vbcol=seagreen]
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "barbara" <barbara_2003@.hotmail.com> wrote in message
> news:5cd01256.0409091029.5a87adcc@.posting.google.c om...
> news:<2qajjjFs3b8qU1@.uni-berlin.de>...
of
>
http://www.microsoft.com/technet/pro.../failclus.mspx
>
http://support.microsoft.com/support...ppingFinal.asp
>
http://www.microsoft.com/resources/d...s/default.mspx[vbcol=seagreen]
> http://www.microsoft.com/sql/techinf...ailability.asp
> clustered
for[vbcol=seagreen]
> log
to
> particular
> if a
>
|||barbara wrote:
> Luca,
> Thanks for the info. I've looked at all these articles before. If I
> create standby on same server as cluser node (business doesn't want to
> spend on another server), how do I failover to this? How does the
> client connects to
> standby? What name does it uses because the cluster node also exists
> on the same server.
I agree completely with Geoff and Greg about their consideration. High
Availability has a cost. If you don't consider it, probably you don't need a
cluster solution.
By the way you have to refer to the clustered instance with its VIRTUAL
SERVER NAME that is different by the name of two node machine. The stand
alone instance could be referred by the traditional host name.
Imagine that you have a clustered node called NODE1 and the other node
called NODE2 (either with its own IP address). When you setup a clustered
(at operating system level) you have to assign, for the clustered, one
VIRTUAL SERVER NAME and one VIRTUAL IP ADDRESS (of the same class of both
node). When you install the virtual server instance of SQL Server you have
to provide another VIRTUAL SERVER NAME and another VIRTUAL IP ADDRESS for
SQL Server.
For example
The machine that form the cluster are:
NODE1 (10.0.0.1)
NODE2 (10.0.0.2)
When you create a clustered at Windows 2000/2003 level you can assign the
following name and ip address to the virtual server
W2KCLUSTER (10.0.0.3)
And then you setup SQL Server in a clustered instance creating a new virtual
server name with its virtual ip address
SQLCLUSTER (10.0.0.4)
If you install a stand-alone instance on NODE1 you can refer to the
clustered instance with the clustered instance name (that could be run on
NODE1 or NODE2) using its name or ip address (SQLCLUSTER or 10.0.0.4). If
you would connect to the stand alone instance you can connect to it without
considering the virtual server name but using NODE1.
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
http://italy.mvps.org
|||Thanks for the good explanation. How do we change the client
configuration to point clients from SQLCLUSTER to node1? Oracle uses
LDAP/ONAMES for name resolution which is easier to change. Do we have
any for sql server? Is DNS name change is only option available? How
does it take care of caching at client level?
"Luca Bianchi" <rightjoinREMOVE_THIS@.hotmail.com> wrote in message news:<2qd1hrFueik4U1@.uni-berlin.de>...
> barbara wrote:
> I agree completely with Geoff and Greg about their consideration. High
> Availability has a cost. If you don't consider it, probably you don't need a
> cluster solution.
> By the way you have to refer to the clustered instance with its VIRTUAL
> SERVER NAME that is different by the name of two node machine. The stand
> alone instance could be referred by the traditional host name.
> Imagine that you have a clustered node called NODE1 and the other node
> called NODE2 (either with its own IP address). When you setup a clustered
> (at operating system level) you have to assign, for the clustered, one
> VIRTUAL SERVER NAME and one VIRTUAL IP ADDRESS (of the same class of both
> node). When you install the virtual server instance of SQL Server you have
> to provide another VIRTUAL SERVER NAME and another VIRTUAL IP ADDRESS for
> SQL Server.
> For example
> The machine that form the cluster are:
> NODE1 (10.0.0.1)
> NODE2 (10.0.0.2)
> When you create a clustered at Windows 2000/2003 level you can assign the
> following name and ip address to the virtual server
> W2KCLUSTER (10.0.0.3)
> And then you setup SQL Server in a clustered instance creating a new virtual
> server name with its virtual ip address
> SQLCLUSTER (10.0.0.4)
> If you install a stand-alone instance on NODE1 you can refer to the
> clustered instance with the clustered instance name (that could be run on
> NODE1 or NODE2) using its name or ip address (SQLCLUSTER or 10.0.0.4). If
> you would connect to the stand alone instance you can connect to it without
> considering the virtual server name but using NODE1.
> Bye
|||Currently there is no automagic client redirection. You can handle this in
a variety of ways. You can put the server portion of the conneciotn string
in a registry entry or an XML document and push changes otu to all the
clients. You can do a DNS alias redirect, but as you noted, there is the
client caching issue. This is one reason clustering is so useful. The
clients reconnect using the same connection string after a failover.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"barbara" <barbara_2003@.hotmail.com> wrote in message
news:5cd01256.0409100354.23e1b6a4@.posting.google.c om...
> Thanks for the good explanation. How do we change the client
> configuration to point clients from SQLCLUSTER to node1? Oracle uses
> LDAP/ONAMES for name resolution which is easier to change. Do we have
> any for sql server? Is DNS name change is only option available? How
> does it take care of caching at client level?
>
> "Luca Bianchi" <rightjoinREMOVE_THIS@.hotmail.com> wrote in message
news:<2qd1hrFueik4U1@.uni-berlin.de>...[vbcol=seagreen]
need a[vbcol=seagreen]
clustered[vbcol=seagreen]
both[vbcol=seagreen]
have[vbcol=seagreen]
for[vbcol=seagreen]
the[vbcol=seagreen]
virtual[vbcol=seagreen]
on[vbcol=seagreen]
If[vbcol=seagreen]
without[vbcol=seagreen]
|||That's the beauty of clustering. The client doesn't have to do anything,
except reconnect. The virtual server name and IP are both moved to the
other node. The client doesn't reference the node directly - only through
the virtual name and IP.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"barbara" <barbara_2003@.hotmail.com> wrote in message
news:5cd01256.0409100354.23e1b6a4@.posting.google.c om...
Thanks for the good explanation. How do we change the client
configuration to point clients from SQLCLUSTER to node1? Oracle uses
LDAP/ONAMES for name resolution which is easier to change. Do we have
any for sql server? Is DNS name change is only option available? How
does it take care of caching at client level?
"Luca Bianchi" <rightjoinREMOVE_THIS@.hotmail.com> wrote in message
news:<2qd1hrFueik4U1@.uni-berlin.de>...
> barbara wrote:
> I agree completely with Geoff and Greg about their consideration. High
> Availability has a cost. If you don't consider it, probably you don't need
a
> cluster solution.
> By the way you have to refer to the clustered instance with its VIRTUAL
> SERVER NAME that is different by the name of two node machine. The stand
> alone instance could be referred by the traditional host name.
> Imagine that you have a clustered node called NODE1 and the other node
> called NODE2 (either with its own IP address). When you setup a clustered
> (at operating system level) you have to assign, for the clustered, one
> VIRTUAL SERVER NAME and one VIRTUAL IP ADDRESS (of the same class of both
> node). When you install the virtual server instance of SQL Server you have
> to provide another VIRTUAL SERVER NAME and another VIRTUAL IP ADDRESS for
> SQL Server.
> For example
> The machine that form the cluster are:
> NODE1 (10.0.0.1)
> NODE2 (10.0.0.2)
> When you create a clustered at Windows 2000/2003 level you can assign the
> following name and ip address to the virtual server
> W2KCLUSTER (10.0.0.3)
> And then you setup SQL Server in a clustered instance creating a new
virtual
> server name with its virtual ip address
> SQLCLUSTER (10.0.0.4)
> If you install a stand-alone instance on NODE1 you can refer to the
> clustered instance with the clustered instance name (that could be run on
> NODE1 or NODE2) using its name or ip address (SQLCLUSTER or 10.0.0.4). If
> you would connect to the stand alone instance you can connect to it
without
> considering the virtual server name but using NODE1.
> Bye
|||Does microsoft know this problem? In enterprise environment, it is
very hard to push the DNS change to all clients. When they offer log
shipping, there should be an easy way for client redirection. I feel
this is is the biggest
drawback with sql server. How do you push XML or registry to all
clients? Do we need to have list of all clinet machine IPs?
Any other ideas in this subject is well appreciated.
Thanks
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message news:<O6i6nwzlEHA.3608@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> Currently there is no automagic client redirection. You can handle this in
> a variety of ways. You can put the server portion of the conneciotn string
> in a registry entry or an XML document and push changes otu to all the
> clients. You can do a DNS alias redirect, but as you noted, there is the
> client caching issue. This is one reason clustering is so useful. The
> clients reconnect using the same connection string after a failover.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "barbara" <barbara_2003@.hotmail.com> wrote in message
> news:5cd01256.0409100354.23e1b6a4@.posting.google.c om...
> news:<2qd1hrFueik4U1@.uni-berlin.de>...
> need a
> clustered
> both
> have
> for
> the
> virtual
> on
> If
> without

log shipping with cluster

is there any link about logshipping with windows 2000 cluster ?

Have you encountered a problem? These two technologies are independent of each other and shouldn't have problems when used together.|||

Hi Matt,

case closed, thank you for you response.

t tried to configure the log shipping from the passive node, not the owner, thats why it failed. thx.

sql

log shipping with cluster

is there any link about logshipping with windows 2000 cluster ?

Have you encountered a problem? These two technologies are independent of each other and shouldn't have problems when used together.|||

Hi Matt,

case closed, thank you for you response.

t tried to configure the log shipping from the passive node, not the owner, thats why it failed. thx.

Log Shipping two Databases

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

Log Shipping two Databases

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

Log Shipping two Databases

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

Log shipping trn file retention

What's the logshipping trn file retention most DBA usually set, 1,2 or 3
days? I am curious. In our production database, we set our LS file retention
for 3 days and I am just wonder if it 's too long or too short. Is there a
guideline or some short.
Thanks in advance
PhilN wrote:
> What's the logshipping trn file retention most DBA usually set, 1,2 or 3
> days? I am curious. In our production database, we set our LS file retention
> for 3 days and I am just wonder if it 's too long or too short. Is there a
> guideline or some short.
> Thanks in advance
>
We use a home-grown log shipping process here, and keep a solid week's
worth of backups. As each log is restored, it is zipped up into an
archive for that day. At any given point, we have 7 zip files,
containing the t-logs for the previous 7 days.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log shipping trn file retention

What's the logshipping trn file retention most DBA usually set, 1,2 or 3
days? I am curious. In our production database, we set our LS file retention
for 3 days and I am just wonder if it 's too long or too short. Is there a
guideline or some short.
Thanks in advancePhilN wrote:
> What's the logshipping trn file retention most DBA usually set, 1,2 or 3
> days? I am curious. In our production database, we set our LS file retention
> for 3 days and I am just wonder if it 's too long or too short. Is there a
> guideline or some short.
> Thanks in advance
>
We use a home-grown log shipping process here, and keep a solid week's
worth of backups. As each log is restored, it is zipped up into an
archive for that day. At any given point, we have 7 zip files,
containing the t-logs for the previous 7 days.
Tracy McKibben
MCDBA
http://www.realsqlguy.comsql

Log shipping trn file retention

What's the logshipping trn file retention most DBA usually set, 1,2 or 3
days? I am curious. In our production database, we set our LS file retention
for 3 days and I am just wonder if it 's too long or too short. Is there a
guideline or some short.
Thanks in advancePhilN wrote:
> What's the logshipping trn file retention most DBA usually set, 1,2 or 3
> days? I am curious. In our production database, we set our LS file retenti
on
> for 3 days and I am just wonder if it 's too long or too short. Is there a
> guideline or some short.
> Thanks in advance
>
We use a home-grown log shipping process here, and keep a solid week's
worth of backups. As each log is restored, it is zipped up into an
archive for that day. At any given point, we have 7 zip files,
containing the t-logs for the previous 7 days.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log shipping sync error 14421

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

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

Log shipping sync error 14421

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

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

Log shipping sync error 14421

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

Log shipping question.

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

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

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

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

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

Log shipping question.

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

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

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

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

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

log shipping question

Hi Guys,
i am planning to implement logshipping on sql 2000 EE.
i have two questions on this.
i am planning to use log shipping interval of 2 minutes
1) can dump the transaction log backup on network share
instead of production server.
if yes will it have any other impact?
2) every month i am rebuilding my indexes which will
create a huge transaction log
will it create any problem on log shipping.
pls advice me
Biju
Biju,
1: network share is OK. Obviously if the sahre is unavailable then there'll
be a problem, so local folders are normally used.
2: make sure the load and copy frequency are both one minute and this should
prevent a backlog building up.
HTH,
Paul Ibison

Log shipping procedure with replication

hello experts,

Im new to sqlserver database and i really need ur advice on this.

We are planning to setup logshipping for our sqlserver 2005 database.Our setup is like this

we have a primary database on server A which has to be logshipped to Server C.A reporting server B is also maintained by doing transactional replication between Server A and Server B.

Now i want to know whether the procedure for carrying out logshipping process between server A and Server C will remain the same or wil there be any change because a replication is also going on server A .Please give me a step by step procedure for doing the logshipping on a server which is even involved in replication process.

Thanks in advance

Regards

Arvind L

Hi Arvind,
Welcome to the world of Sql Server
pls refer the link it might help you, http://msdn2.microsoft.com/en-us/library/ms151224.aspx

Thanxx
Deepak

|||

Thanks deepak..

Log shipping procedure with replication

hello experts,

Im new to sqlserver database and i really need ur advice on this.

We are planning to setup logshipping for our sqlserver 2005 database.Our setup is like this

we have a primary database on server A which has to be logshipped to Server C.A reporting server B is also maintained by doing transactional replication between Server A and Server B.

Now i want to know whether the procedure for carrying out logshipping process between server A and Server C will remain the same or wil there be any change because a replication is also going on server A .Please give me a step by step procedure for doing the logshipping on a server which is even involved in replication process.

Thanks in advance

Regards

Arvind L

Hi Arvind,
Welcome to the world of Sql Server
pls refer the link it might help you, http://msdn2.microsoft.com/en-us/library/ms151224.aspx

Thanxx
Deepak

|||

Thanks deepak..

Log Shipping Plan fails (event: 208)

Hi,
We've been using logshipping successfully for over a year,
but recently we are experiencing more and more failures
relating to the Transaction Log Backup Job. We are
currently log shipping 30 databases from a W2K(SP4)
SQL2000(SP3) server to a W2K3 Server (SQL2000SP3).
The backup jobs aren't consistently failing, which is
making this harder to diagnose. If I manually run the jobs
from Enterprise Manager they work fine, and the only error
messages that i'm seeing are like the following:
EventID: 208
SQL Server Scheduled Job 'Transaction Log Backup Job for DB
Maintenance Plan 'Unity_Server1 Log Shipping''
(0x318A0055279BA840AABD24DA1BA5B440) - Status: Failed -
Invoked on: 2004-09-20 17:15:10 - Message: The job failed.
The Job was invoked by Schedule 59 (Schedule 1). The last
step to run was step 1 (Step 1).
There aren't any issues with disk space, and I don't think
this is a security issue, as the jobs aren't consistently
failing.
Hoping that someone has come across this issue before.
Thanks,
Martin
Martin,
I'm not too sure where this message originates from, but if it is the job,
then in the maintenance plan can you enable logging to the textfile and then
examine the resulting messages. I often just receive sqlmaint.exe failed
messages in the job, but in the textfile find out the real cause of the
problem.
Regards,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul Ibison wrote:
> Martin,
> I'm not too sure where this message originates from, but if it is the job,
> then in the maintenance plan can you enable logging to the textfile and then
> examine the resulting messages.
This is interesting - when I examine the folder containing the
log-shipping logs - whenever a job fails there is no log created.
However, successful log-shipping jobs do create a log file. So not only
is the job failing to complete, but it's also failing to create a log of
the failure.
Looking at the job history shows a complete list of all the log-shipping
jobs with corresponding results (failed or successful).
Thanks
Martin
|||Martin,
in that case you could use profiler. Some things are
incompatible with backups - eg file management operations
such as the ALTER DATABASE statement with either the ADD
FILE or REMOVE FILE options; shrink database or shrink
file - this includes autoshrink operations.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

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

Log Shipping Monitor - 2005

Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
Enterprise Manager still available with SQL Server 2005. I installed Log
Shipping on a 2005 server and selected the monitor option but I can not find
the nice Log Shipping monitor that give you status on log shipping. I also
searched through the Books Online documentation and several online resources
and I have not found a definitive answer.
Please help.
Thanks!
Chris
Hi Chris
"Cgal" wrote:

> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
> Enterprise Manager still available with SQL Server 2005. I installed Log
> Shipping on a 2005 server and selected the monitor option but I can not find
> the nice Log Shipping monitor that give you status on log shipping. I also
> searched through the Books Online documentation and several online resources
> and I have not found a definitive answer.
> Please help.
> Thanks!
> Chris
In SQLServer 2005 there is a standard report called "Transaction Log
Shipping Status" that gives you the current status.
http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4) currently
gives information on how to show the report prior to SP2. You will need to
show the Object Explorer tab (view menu and select Object Explorer detals) to
get the reports button (on the tab's toolbar). The list of reports are
sensitive to the context which you have selected in the object explorer (F8)
so if you don't see this report you are probably not on the node for the
instance.
After SP2 you can right click the node for the instance and select
Reports/Standard Reports/Transaction Log Shipping Status
HTH
john
|||John,
Thanks for the quick response.
I knew about the report that you referenced but I was hoping that there was
more. The report has no where near the functionality and usability of the
"Log Shipping Monitor" that came with SQL Server 2000.
Please let me know if there are any other tools for monitoring Log Shipping
beyond the report.
Thanks!
Chris
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9C6B2961-67CB-4B3A-A822-C73899577EBD@.microsoft.com...
> Hi Chris
> "Cgal" wrote:
>
> In SQLServer 2005 there is a standard report called "Transaction Log
> Shipping Status" that gives you the current status.
> http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4)
> currently
> gives information on how to show the report prior to SP2. You will need to
> show the Object Explorer tab (view menu and select Object Explorer detals)
> to
> get the reports button (on the tab's toolbar). The list of reports are
> sensitive to the context which you have selected in the object explorer
> (F8)
> so if you don't see this report you are probably not on the node for the
> instance.
> After SP2 you can right click the node for the instance and select
> Reports/Standard Reports/Transaction Log Shipping Status
> HTH
> john
|||Hi, Chris,
I guess that you would like to add a monitor server in your log shipping
environment.
If I have misunderstood, please let me know.
In SQL Server 2005, to monitor log shipping configuration, adding the
monitor server is required. If you do not have a monitor server, you may
need to manually run the system procedures such as
sp_help_log_shipping_primary_database,
sp_help_log_shipping_primary_secondary,
sp_help_log_shipping_secondary_database, and
sp_help_log_shipping_secondary_primary etc to query the status of your log
shipping.
For more detailed information, you can refer to this article:
How to: Enable Log Shipping (SQL Server Management Studio)
http://msdn2.microsoft.com/en-us/library/ms190640.aspx
Understanding Log Shipping
http://msdn2.microsoft.com/en-us/library/ms187103.aspx
Monitoring Log Shipping
http://msdn2.microsoft.com/en-us/library/ms190224.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi, Chris
Just check with you to see if the suggestions were helpful. Please let us
know if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====