Hi,
We are running SQL Server Failover cluster in Active/Passive mode.
Now, we want to setup DR server for this clustered database using
Log shipping.
But my concern is, can we do log shipping with clustered database ?
and the answer of this question is Yes then Please let me know How ?
Thanks & Regards,
Sajid C.
Yep...you can. Just like how you do it in a non-clustered instance. The only
problem you will have in here is if you want to be notified thru email if
your restore jobs fail as MAPI is not supported in a clustered environment.
MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
"Helping people grow and develop their full potential as God has plan for
them"
"csajid@.gmail.com" wrote:
> Hi,
> We are running SQL Server Failover cluster in Active/Passive mode.
> Now, we want to setup DR server for this clustered database using
> Log shipping.
> But my concern is, can we do log shipping with clustered database ?
> and the answer of this question is Yes then Please let me know How ?
>
> Thanks & Regards,
> Sajid C.
>
|||Hi,
Thanks for your reply.
Can you please provide me some document or any link for the same.
What are the necessary steps which should i take to do this task.
Thanks & Regards,
Sajid C.
bass_player wrote:[vbcol=seagreen]
> Yep...you can. Just like how you do it in a non-clustered instance. The only
> problem you will have in here is if you want to be notified thru email if
> your restore jobs fail as MAPI is not supported in a clustered environment.
> --
> MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
> "Helping people grow and develop their full potential as God has plan for
> them"
>
> "csajid@.gmail.com" wrote:
Showing posts with label setup. Show all posts
Showing posts with label setup. Show all posts
Friday, March 30, 2012
Log Shipping with clustered database.
Hi,
We are running SQL Server Failover cluster in Active/Passive mode.
Now, we want to setup DR server for this clustered database using
Log shipping.
But my concern is, can we do log shipping with clustered database ?
and the answer of this question is Yes then Please let me know How ?
Thanks & Regards,
Sajid C.Yep...you can. Just like how you do it in a non-clustered instance. The only
problem you will have in here is if you want to be notified thru email if
your restore jobs fail as MAPI is not supported in a clustered environment.
--
MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
"Helping people grow and develop their full potential as God has plan for
them"
"csajid@.gmail.com" wrote:
> Hi,
> We are running SQL Server Failover cluster in Active/Passive mode.
> Now, we want to setup DR server for this clustered database using
> Log shipping.
> But my concern is, can we do log shipping with clustered database ?
> and the answer of this question is Yes then Please let me know How ?
>
> Thanks & Regards,
> Sajid C.
>|||Hi,
Thanks for your reply.
Can you please provide me some document or any link for the same.
What are the necessary steps which should i take to do this task.
Thanks & Regards,
Sajid C.
bass_player wrote:
> Yep...you can. Just like how you do it in a non-clustered instance. The only
> problem you will have in here is if you want to be notified thru email if
> your restore jobs fail as MAPI is not supported in a clustered environment.
> --
> MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
> "Helping people grow and develop their full potential as God has plan for
> them"
>
> "csajid@.gmail.com" wrote:
> > Hi,
> >
> > We are running SQL Server Failover cluster in Active/Passive mode.
> >
> > Now, we want to setup DR server for this clustered database using
> > Log shipping.
> >
> > But my concern is, can we do log shipping with clustered database ?
> > and the answer of this question is Yes then Please let me know How ?
> >
> >
> > Thanks & Regards,
> > Sajid C.
> >
> >
We are running SQL Server Failover cluster in Active/Passive mode.
Now, we want to setup DR server for this clustered database using
Log shipping.
But my concern is, can we do log shipping with clustered database ?
and the answer of this question is Yes then Please let me know How ?
Thanks & Regards,
Sajid C.Yep...you can. Just like how you do it in a non-clustered instance. The only
problem you will have in here is if you want to be notified thru email if
your restore jobs fail as MAPI is not supported in a clustered environment.
--
MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
"Helping people grow and develop their full potential as God has plan for
them"
"csajid@.gmail.com" wrote:
> Hi,
> We are running SQL Server Failover cluster in Active/Passive mode.
> Now, we want to setup DR server for this clustered database using
> Log shipping.
> But my concern is, can we do log shipping with clustered database ?
> and the answer of this question is Yes then Please let me know How ?
>
> Thanks & Regards,
> Sajid C.
>|||Hi,
Thanks for your reply.
Can you please provide me some document or any link for the same.
What are the necessary steps which should i take to do this task.
Thanks & Regards,
Sajid C.
bass_player wrote:
> Yep...you can. Just like how you do it in a non-clustered instance. The only
> problem you will have in here is if you want to be notified thru email if
> your restore jobs fail as MAPI is not supported in a clustered environment.
> --
> MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
> "Helping people grow and develop their full potential as God has plan for
> them"
>
> "csajid@.gmail.com" wrote:
> > Hi,
> >
> > We are running SQL Server Failover cluster in Active/Passive mode.
> >
> > Now, we want to setup DR server for this clustered database using
> > Log shipping.
> >
> > But my concern is, can we do log shipping with clustered database ?
> > and the answer of this question is Yes then Please let me know How ?
> >
> >
> > Thanks & Regards,
> > Sajid C.
> >
> >
Log Shipping with clustered database.
Hi,
We are running SQL Server Failover cluster in Active/Passive mode.
Now, we want to setup DR server for this clustered database using
Log shipping.
But my concern is, can we do log shipping with clustered database ?
and the answer of this question is Yes then Please let me know How ?
Thanks & Regards,
Sajid C.Yep...you can. Just like how you do it in a non-clustered instance. The onl
y
problem you will have in here is if you want to be notified thru email if
your restore jobs fail as MAPI is not supported in a clustered environment.
--
MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
"Helping people grow and develop their full potential as God has plan for
them"
"csajid@.gmail.com" wrote:
> Hi,
> We are running SQL Server Failover cluster in Active/Passive mode.
> Now, we want to setup DR server for this clustered database using
> Log shipping.
> But my concern is, can we do log shipping with clustered database ?
> and the answer of this question is Yes then Please let me know How ?
>
> Thanks & Regards,
> Sajid C.
>|||Hi,
Thanks for your reply.
Can you please provide me some document or any link for the same.
What are the necessary steps which should i take to do this task.
Thanks & Regards,
Sajid C.
bass_player wrote:[vbcol=seagreen]
> Yep...you can. Just like how you do it in a non-clustered instance. The o
nly
> problem you will have in here is if you want to be notified thru email if
> your restore jobs fail as MAPI is not supported in a clustered environment
.
> --
> MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
> "Helping people grow and develop their full potential as God has plan for
> them"
>
> "csajid@.gmail.com" wrote:
>
We are running SQL Server Failover cluster in Active/Passive mode.
Now, we want to setup DR server for this clustered database using
Log shipping.
But my concern is, can we do log shipping with clustered database ?
and the answer of this question is Yes then Please let me know How ?
Thanks & Regards,
Sajid C.Yep...you can. Just like how you do it in a non-clustered instance. The onl
y
problem you will have in here is if you want to be notified thru email if
your restore jobs fail as MAPI is not supported in a clustered environment.
--
MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
"Helping people grow and develop their full potential as God has plan for
them"
"csajid@.gmail.com" wrote:
> Hi,
> We are running SQL Server Failover cluster in Active/Passive mode.
> Now, we want to setup DR server for this clustered database using
> Log shipping.
> But my concern is, can we do log shipping with clustered database ?
> and the answer of this question is Yes then Please let me know How ?
>
> Thanks & Regards,
> Sajid C.
>|||Hi,
Thanks for your reply.
Can you please provide me some document or any link for the same.
What are the necessary steps which should i take to do this task.
Thanks & Regards,
Sajid C.
bass_player wrote:[vbcol=seagreen]
> Yep...you can. Just like how you do it in a non-clustered instance. The o
nly
> problem you will have in here is if you want to be notified thru email if
> your restore jobs fail as MAPI is not supported in a clustered environment
.
> --
> MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
> "Helping people grow and develop their full potential as God has plan for
> them"
>
> "csajid@.gmail.com" wrote:
>
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!
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
>
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
>
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 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,
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
>
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
>
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
>
Wednesday, March 28, 2012
Log Shipping transaction log backup files have wrong timestamp
I'm experiencing a weird problem with log shipping in SQL 2005.
I've setup Log Shipping for a production database between two sites. The standby database is being updated correctly and everything seems to be working as expected but for one detail: the name of the transaction log backups are generated with an UTC timestamp instead of my local timezone.
The the data below extracted from the backup history:
2007-06-23 17:30:00.000 D:\Backup\Databases\mydb\mydb_20070623073000.trn
2007-06-23 17:15:00.000 D:\Backup\Databases\mydb\mydb_20070623071500.trn
2007-06-23 17:00:00.000 D:\Backup\Databases\mydb\mydb_20070623070000.trn
2007-06-23 16:45:00.000 D:\Backup\Databases\mydb\mydb_20070623064500.trn
My timezone here is GMT+10.
Although it's not affecting Log Shipping, it's very confusing as the full backups have a timestamp in the local timezone!
Has anyone seen experienced something similar to this? Please see below my SQL details:
1 ProductName NULL Microsoft SQL Server
2 ProductVersion 589824 9.00.3042.00
3 Language 1033 English (United States)
4 Platform NULL NT AMD64
5 Comments NULL NT AMD64
6 CompanyName NULL Microsoft Corporation
7 FileDescription NULL SQL Server Windows NT - 64 Bit
8 FileVersion NULL 2005.090.3042.00
9 InternalName NULL SQLSERVR
10 LegalCopyright NULL ? Microsoft Corp. All rights reserved.
11 LegalTrademarks NULL Microsoft? is a registered trademark of Microsoft Corporation. Windows(TM) is a trademark of Microsoft Corporation
12 OriginalFilename NULL SQLSERVR.EXE
13 PrivateBuild NULL NULL
14 SpecialBuild 199360512 NULL
15 WindowsVersion 248381957 5.2 (3790)
16 ProcessorCount 4 4
17 ProcessorActiveMask 4 f
18 ProcessorType 8664 NULL
19 PhysicalMemory 4095 4095 (4294037504)
20 Product ID NULL NULL
Thanks,
Andr
Hi Andre
The use of UTC timestamp for the log shipping files is by design and how log shipping is supposed to work. The main reason for this is so that there is no way timestamps can jump backward or forward when daylight savings time starts or finishes, for example. Log shipping uses the timestamps to work out if there is anything new to process and using UTC ensures this process works reliably.
Thanks, Mark
|||Thanks, Mark.It would be good, though, that the maintenance plan's backup task had at least an option to use the same approach when naming backup files, for consistency purposes.
Is this feature documented in Books Online? I couldn't find any reference.
Thanks,
Andr
Log Shipping Setup Problem
When using the Database Maintenance Plan WIzard to setup log shipping I have
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.com
Easy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.com
Easy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
Log Shipping Setup Problem
When using the Database Maintenance Plan WIzard to setup log shipping I have
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
Log Shipping Setup Problem
When using the Database Maintenance Plan WIzard to setup log shipping I have
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I ha
ve
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is n
ot
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I ha
ve
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is n
ot
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
Monday, March 26, 2012
log shipping question
What happens when you check the " Allow database to assume primary role"
option during log shipping setup. What happens if you dont check it ?
Also, does anyone have any links as far as recovery procedures for a log
shipping implementation used for disaster recovery..i.e. if Server A fails,
what are the exact steps to follow to recover the application onto Server B
which would also include changing the servername from Server B to Server A
...
Allow database to assume primary role - When this option is enabled, this secondary server becomes the primary server if there are any problems on the original primary server. If you select this option, you must provide a share where the transaction logs
are stored when the server assumes the role of a primary server (for example, (\\secondary_computername\sharename).
KBA http://support.microsoft.com/default...314515&sd=tech about complete FAQ sheet on Log shipping.
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Hassan" wrote:
> What happens when you check the " Allow database to assume primary role"
> option during log shipping setup. What happens if you dont check it ?
> Also, does anyone have any links as far as recovery procedures for a log
> shipping implementation used for disaster recovery..i.e. if Server A fails,
> what are the exact steps to follow to recover the application onto Server B
> which would also include changing the servername from Server B to Server A
> ...
>
>
option during log shipping setup. What happens if you dont check it ?
Also, does anyone have any links as far as recovery procedures for a log
shipping implementation used for disaster recovery..i.e. if Server A fails,
what are the exact steps to follow to recover the application onto Server B
which would also include changing the servername from Server B to Server A
...
Allow database to assume primary role - When this option is enabled, this secondary server becomes the primary server if there are any problems on the original primary server. If you select this option, you must provide a share where the transaction logs
are stored when the server assumes the role of a primary server (for example, (\\secondary_computername\sharename).
KBA http://support.microsoft.com/default...314515&sd=tech about complete FAQ sheet on Log shipping.
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Hassan" wrote:
> What happens when you check the " Allow database to assume primary role"
> option during log shipping setup. What happens if you dont check it ?
> Also, does anyone have any links as far as recovery procedures for a log
> shipping implementation used for disaster recovery..i.e. if Server A fails,
> what are the exact steps to follow to recover the application onto Server B
> which would also include changing the servername from Server B to Server A
> ...
>
>
Friday, March 23, 2012
log shipping question
What happens when you check the " Allow database to assume primary role"
option during log shipping setup. What happens if you dont check it ?
Also, does anyone have any links as far as recovery procedures for a log
shipping implementation used for disaster recovery..i.e. if Server A fails,
what are the exact steps to follow to recover the application onto Server B
which would also include changing the servername from Server B to Server A
...Allow database to assume primary role - When this option is enabled, this se
condary server becomes the primary server if there are any problems on the o
riginal primary server. If you select this option, you must provide a share
where the transaction logs
are stored when the server assumes the role of a primary server (for example
, (\\secondary_computername\sharename).
KBA http://support.microsoft.com/defaul...;314515&sd=tech a
bout complete FAQ sheet on Log shipping.
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Perform
ance topic.
"Hassan" wrote:
> What happens when you check the " Allow database to assume primary role"
> option during log shipping setup. What happens if you dont check it ?
> Also, does anyone have any links as far as recovery procedures for a log
> shipping implementation used for disaster recovery..i.e. if Server A fails
,
> what are the exact steps to follow to recover the application onto Server
B
> which would also include changing the servername from Server B to Server A
> ...
>
>
option during log shipping setup. What happens if you dont check it ?
Also, does anyone have any links as far as recovery procedures for a log
shipping implementation used for disaster recovery..i.e. if Server A fails,
what are the exact steps to follow to recover the application onto Server B
which would also include changing the servername from Server B to Server A
...Allow database to assume primary role - When this option is enabled, this se
condary server becomes the primary server if there are any problems on the o
riginal primary server. If you select this option, you must provide a share
where the transaction logs
are stored when the server assumes the role of a primary server (for example
, (\\secondary_computername\sharename).
KBA http://support.microsoft.com/defaul...;314515&sd=tech a
bout complete FAQ sheet on Log shipping.
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Perform
ance topic.
"Hassan" wrote:
> What happens when you check the " Allow database to assume primary role"
> option during log shipping setup. What happens if you dont check it ?
> Also, does anyone have any links as far as recovery procedures for a log
> shipping implementation used for disaster recovery..i.e. if Server A fails
,
> what are the exact steps to follow to recover the application onto Server
B
> which would also include changing the servername from Server B to Server A
> ...
>
>
Log Shipping Question
Hello,
I want to setup SQL Log Shipping btwn two servers.
- Do the servers have to run same version of Windows? Can one be Win2003 and
the other Win2K Server? Or one Win2k Advanced and one Win2k Standard Server?
- Do I have to run the same version/build/ServicePack of SQL Server?
many thanks
christos
If you are using the Enterprise Edition of SQL Server's Log Shipping
functions both SQL Server's have to be Enterprise Edition. If you are
rolling your own version of Log Shipping, there are no SQL Server version
requirements or OS requirements (other than NT workstation/server, XP
professional, Win2k server/professional, Windows 2003).
"Christos Kritikos" <ChristosKritikos@.discussions.microsoft.com> wrote in
message news:D025AB19-599D-4806-9817-2804C182F38A@.microsoft.com...
> Hello,
> I want to setup SQL Log Shipping btwn two servers.
> - Do the servers have to run same version of Windows? Can one be Win2003
and
> the other Win2K Server? Or one Win2k Advanced and one Win2k Standard
Server?
> - Do I have to run the same version/build/ServicePack of SQL Server?
> many thanks
> christos
>
I want to setup SQL Log Shipping btwn two servers.
- Do the servers have to run same version of Windows? Can one be Win2003 and
the other Win2K Server? Or one Win2k Advanced and one Win2k Standard Server?
- Do I have to run the same version/build/ServicePack of SQL Server?
many thanks
christos
If you are using the Enterprise Edition of SQL Server's Log Shipping
functions both SQL Server's have to be Enterprise Edition. If you are
rolling your own version of Log Shipping, there are no SQL Server version
requirements or OS requirements (other than NT workstation/server, XP
professional, Win2k server/professional, Windows 2003).
"Christos Kritikos" <ChristosKritikos@.discussions.microsoft.com> wrote in
message news:D025AB19-599D-4806-9817-2804C182F38A@.microsoft.com...
> Hello,
> I want to setup SQL Log Shipping btwn two servers.
> - Do the servers have to run same version of Windows? Can one be Win2003
and
> the other Win2K Server? Or one Win2k Advanced and one Win2k Standard
Server?
> - Do I have to run the same version/build/ServicePack of SQL Server?
> many thanks
> christos
>
Log Shipping Question
While reviewing our log shipping setup, I noticed we backup, ship and restore
logs from 7am-7pm. We also perform a full backup at 9pm.
My question is this: Will the transaction backup at 7am pick up
transactions since the last transaction log backup at 7pm or since the full
backup at 9PM. Are we losing 2 hours of transactions?
SqlServer2005 SP2.
Thanks.
Ron
Full and transaction logs are almost completely independent. Almost means
that you have to have a full backup to initialize the log chain. After
that, a full backup has no impact on the transaction log backups. For
example, if last night's backup was bad, you can go back two days and
restore logs up to today. As a side effect, full backups do not mark any
part of the transaction log as inactive so transaction log backups are
necessary to truncate a log when in full recovery mode.
Each log backup consists of the completed and checkpointed transactions
since the last transaction log backup. Once these transactions are backed
up, the log space is marked inactive and can be reused.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:4A35A3CB-E733-4AE5-9780-1DACB82C9ABE@.microsoft.com...
> While reviewing our log shipping setup, I noticed we backup, ship and
> restore
> logs from 7am-7pm. We also perform a full backup at 9pm.
> My question is this: Will the transaction backup at 7am pick up
> transactions since the last transaction log backup at 7pm or since the
> full
> backup at 9PM. Are we losing 2 hours of transactions?
> SqlServer2005 SP2.
> Thanks.
> Ron
logs from 7am-7pm. We also perform a full backup at 9pm.
My question is this: Will the transaction backup at 7am pick up
transactions since the last transaction log backup at 7pm or since the full
backup at 9PM. Are we losing 2 hours of transactions?
SqlServer2005 SP2.
Thanks.
Ron
Full and transaction logs are almost completely independent. Almost means
that you have to have a full backup to initialize the log chain. After
that, a full backup has no impact on the transaction log backups. For
example, if last night's backup was bad, you can go back two days and
restore logs up to today. As a side effect, full backups do not mark any
part of the transaction log as inactive so transaction log backups are
necessary to truncate a log when in full recovery mode.
Each log backup consists of the completed and checkpointed transactions
since the last transaction log backup. Once these transactions are backed
up, the log space is marked inactive and can be reused.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:4A35A3CB-E733-4AE5-9780-1DACB82C9ABE@.microsoft.com...
> While reviewing our log shipping setup, I noticed we backup, ship and
> restore
> logs from 7am-7pm. We also perform a full backup at 9pm.
> My question is this: Will the transaction backup at 7am pick up
> transactions since the last transaction log backup at 7pm or since the
> full
> backup at 9PM. Are we losing 2 hours of transactions?
> SqlServer2005 SP2.
> Thanks.
> Ron
Log Shipping Question
I am setting up log shipping according to the "How to Setup Log Shipping" Microsoft White Paper. I want to use log shipping for multiple databases on the same machine and I guess I need to configure each DB separately. My question is do I/should I use s
eparate transaction log backup shares on the primary and secondary machines corresponding to each database. Just wondering if there is a chance for a collison with the log file names between to different DBs? Thanks.
Jeff
Jeff,
I have used both scenarios: separate directories and the same directory for all files. The filenames are prefixed with the database name and the maintenance plan takes it into account, so there's no problem. However, I find maintenance easier (clearer) wi
th several directories.
HTH,
Paul Ibison
eparate transaction log backup shares on the primary and secondary machines corresponding to each database. Just wondering if there is a chance for a collison with the log file names between to different DBs? Thanks.
Jeff
Jeff,
I have used both scenarios: separate directories and the same directory for all files. The filenames are prefixed with the database name and the maintenance plan takes it into account, so there's no problem. However, I find maintenance easier (clearer) wi
th several directories.
HTH,
Paul Ibison
Log Shipping Question
I have successfully setup log shipping between my production SQL 2000 Server
(setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a WAN)
What is the best way if any to stop the log shipping for a extended period
of time and re-enable it without setting up the entire maintenance plan
again. Is this possible? What happened is I needed to shut down my
production server due to hurricane Wilma as a precaution. I disabled the log
shipping jobs on both servers but didn't actually physicall shut down the
Disaster Recovery SQL 2000 Server.
The servers got out of synch...although it said the logs were being shipped
and they were working correctly after I turned the production server back on.
However, the log were not being copied to the Disaster Recovery Server.
Any help would be appreciated. Thanks!!
Hello mate,
The way I understand it is you could have just shut down your production
server without changing/stopping/disabling the log shipping jobs and just
bring it back online when your happy (the hurricane has passed!) and the
backup/copy and restores should resume as normal?
The shipping jobs seems very automated once started and syncronised - think
of it like a 'long reboot' of your production boxes. Your boxes aer fine
after bouncing them right - so whats the difference if they are down for a
few days?
I'm in the middle of documenting a similar setup with my production box (non
clustered) getting logs sent to the backup SQL box accross a WAN - the most
complex part of the exercise seems to be getting the backup DB up and running
post failure/disaster of the production box.
Hope this helps you mate.
Paul.
"foghorn69@.news.postalias" wrote:
> I have successfully setup log shipping between my production SQL 2000 Server
> (setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a WAN)
> What is the best way if any to stop the log shipping for a extended period
> of time and re-enable it without setting up the entire maintenance plan
> again. Is this possible? What happened is I needed to shut down my
> production server due to hurricane Wilma as a precaution. I disabled the log
> shipping jobs on both servers but didn't actually physicall shut down the
> Disaster Recovery SQL 2000 Server.
> The servers got out of synch...although it said the logs were being shipped
> and they were working correctly after I turned the production server back on.
> However, the log were not being copied to the Disaster Recovery Server.
> Any help would be appreciated. Thanks!!
(setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a WAN)
What is the best way if any to stop the log shipping for a extended period
of time and re-enable it without setting up the entire maintenance plan
again. Is this possible? What happened is I needed to shut down my
production server due to hurricane Wilma as a precaution. I disabled the log
shipping jobs on both servers but didn't actually physicall shut down the
Disaster Recovery SQL 2000 Server.
The servers got out of synch...although it said the logs were being shipped
and they were working correctly after I turned the production server back on.
However, the log were not being copied to the Disaster Recovery Server.
Any help would be appreciated. Thanks!!
Hello mate,
The way I understand it is you could have just shut down your production
server without changing/stopping/disabling the log shipping jobs and just
bring it back online when your happy (the hurricane has passed!) and the
backup/copy and restores should resume as normal?
The shipping jobs seems very automated once started and syncronised - think
of it like a 'long reboot' of your production boxes. Your boxes aer fine
after bouncing them right - so whats the difference if they are down for a
few days?
I'm in the middle of documenting a similar setup with my production box (non
clustered) getting logs sent to the backup SQL box accross a WAN - the most
complex part of the exercise seems to be getting the backup DB up and running
post failure/disaster of the production box.
Hope this helps you mate.
Paul.
"foghorn69@.news.postalias" wrote:
> I have successfully setup log shipping between my production SQL 2000 Server
> (setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a WAN)
> What is the best way if any to stop the log shipping for a extended period
> of time and re-enable it without setting up the entire maintenance plan
> again. Is this possible? What happened is I needed to shut down my
> production server due to hurricane Wilma as a precaution. I disabled the log
> shipping jobs on both servers but didn't actually physicall shut down the
> Disaster Recovery SQL 2000 Server.
> The servers got out of synch...although it said the logs were being shipped
> and they were working correctly after I turned the production server back on.
> However, the log were not being copied to the Disaster Recovery Server.
> Any help would be appreciated. Thanks!!
Log Shipping Question
I have successfully setup log shipping between my production SQL 2000 Server
(setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a WAN)
What is the best way if any to stop the log shipping for a extended period
of time and re-enable it without setting up the entire maintenance plan
again. Is this possible? What happened is I needed to shut down my
production server due to hurricane Wilma as a precaution. I disabled the log
shipping jobs on both servers but didn't actually physicall shut down the
Disaster Recovery SQL 2000 Server.
The servers got out of synch...although it said the logs were being shipped
and they were working correctly after I turned the production server back on.
However, the log were not being copied to the Disaster Recovery Server.
Any help would be appreciated. Thanks!!
Hello,
Based on my experience, you shall remove and recreate log shipping for this
situation becaseu the expected backup on the primary servers were not
properly created due to server shutdown.
More related information:
329133.KB.EN-US INF: Troubleshooting SQL Server 2000 Log Shipping "Out of
Sync" Errors
http://support.microsoft.com/default...B;EN-US;329133
314515.KB.EN-US INF: Frequently Asked Questions - SQL Server 2000 - Log
Shipping
http://support.microsoft.com/default...B;EN-US;314515
SQL Server 2000 How To Setup Log Shipping
http://www.microsoft.com/downloads/d...&familyid=7395
ec1b-199f-42bc-a31b-2056adf73f94
http://www.microsoft.com/technet/tre...hnet/prodtechn
ol/sql/deploy/prodspecs/logship1.asp
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Log Shipping Question
| thread-index: AcXmR7EoN/OMKH5UTPqRcRbKocEcOg==
| X-WBNR-Posting-Host: 66.20.1.9
| From: "=?Utf-8?B?Rm9naG9ybkxlZ2hvcm4=?=" <foghornleghorn@.nospam.postalias>
| Subject: Log Shipping Question
| Date: Thu, 10 Nov 2005 14:40:03 -0800
| Lines: 17
| Message-ID: <E1996FA4-68BA-4906-9886-D05F65119C1A@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.replication
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:66533
| X-Tomcat-NG: microsoft.public.sqlserver.replication
|
| I have successfully setup log shipping between my production SQL 2000
Server
| (setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a
WAN)
|
| What is the best way if any to stop the log shipping for a extended
period
| of time and re-enable it without setting up the entire maintenance plan
| again. Is this possible? What happened is I needed to shut down my
| production server due to hurricane Wilma as a precaution. I disabled the
log
| shipping jobs on both servers but didn't actually physicall shut down the
| Disaster Recovery SQL 2000 Server.
|
| The servers got out of synch...although it said the logs were being
shipped
| and they were working correctly after I turned the production server back
on.
| However, the log were not being copied to the Disaster Recovery Server.
|
| Any help would be appreciated. Thanks!!
|
|
|
(setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a WAN)
What is the best way if any to stop the log shipping for a extended period
of time and re-enable it without setting up the entire maintenance plan
again. Is this possible? What happened is I needed to shut down my
production server due to hurricane Wilma as a precaution. I disabled the log
shipping jobs on both servers but didn't actually physicall shut down the
Disaster Recovery SQL 2000 Server.
The servers got out of synch...although it said the logs were being shipped
and they were working correctly after I turned the production server back on.
However, the log were not being copied to the Disaster Recovery Server.
Any help would be appreciated. Thanks!!
Hello,
Based on my experience, you shall remove and recreate log shipping for this
situation becaseu the expected backup on the primary servers were not
properly created due to server shutdown.
More related information:
329133.KB.EN-US INF: Troubleshooting SQL Server 2000 Log Shipping "Out of
Sync" Errors
http://support.microsoft.com/default...B;EN-US;329133
314515.KB.EN-US INF: Frequently Asked Questions - SQL Server 2000 - Log
Shipping
http://support.microsoft.com/default...B;EN-US;314515
SQL Server 2000 How To Setup Log Shipping
http://www.microsoft.com/downloads/d...&familyid=7395
ec1b-199f-42bc-a31b-2056adf73f94
http://www.microsoft.com/technet/tre...hnet/prodtechn
ol/sql/deploy/prodspecs/logship1.asp
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Log Shipping Question
| thread-index: AcXmR7EoN/OMKH5UTPqRcRbKocEcOg==
| X-WBNR-Posting-Host: 66.20.1.9
| From: "=?Utf-8?B?Rm9naG9ybkxlZ2hvcm4=?=" <foghornleghorn@.nospam.postalias>
| Subject: Log Shipping Question
| Date: Thu, 10 Nov 2005 14:40:03 -0800
| Lines: 17
| Message-ID: <E1996FA4-68BA-4906-9886-D05F65119C1A@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.replication
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:66533
| X-Tomcat-NG: microsoft.public.sqlserver.replication
|
| I have successfully setup log shipping between my production SQL 2000
Server
| (setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a
WAN)
|
| What is the best way if any to stop the log shipping for a extended
period
| of time and re-enable it without setting up the entire maintenance plan
| again. Is this possible? What happened is I needed to shut down my
| production server due to hurricane Wilma as a precaution. I disabled the
log
| shipping jobs on both servers but didn't actually physicall shut down the
| Disaster Recovery SQL 2000 Server.
|
| The servers got out of synch...although it said the logs were being
shipped
| and they were working correctly after I turned the production server back
on.
| However, the log were not being copied to the Disaster Recovery Server.
|
| Any help would be appreciated. Thanks!!
|
|
|
log shipping question
What happens when you check the " Allow database to assume primary role"
option during log shipping setup. What happens if you dont check it ?
Also, does anyone have any links as far as recovery procedures for a log
shipping implementation used for disaster recovery..i.e. if Server A fails,
what are the exact steps to follow to recover the application onto Server B
which would also include changing the servername from Server B to Server A
...Allow database to assume primary role - When this option is enabled, this secondary server becomes the primary server if there are any problems on the original primary server. If you select this option, you must provide a share where the transaction logs are stored when the server assumes the role of a primary server (for example, (\\secondary_computername\sharename).
KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;314515&sd=tech about complete FAQ sheet on Log shipping.
--
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Hassan" wrote:
> What happens when you check the " Allow database to assume primary role"
> option during log shipping setup. What happens if you dont check it ?
> Also, does anyone have any links as far as recovery procedures for a log
> shipping implementation used for disaster recovery..i.e. if Server A fails,
> what are the exact steps to follow to recover the application onto Server B
> which would also include changing the servername from Server B to Server A
> ...
>
>
option during log shipping setup. What happens if you dont check it ?
Also, does anyone have any links as far as recovery procedures for a log
shipping implementation used for disaster recovery..i.e. if Server A fails,
what are the exact steps to follow to recover the application onto Server B
which would also include changing the servername from Server B to Server A
...Allow database to assume primary role - When this option is enabled, this secondary server becomes the primary server if there are any problems on the original primary server. If you select this option, you must provide a share where the transaction logs are stored when the server assumes the role of a primary server (for example, (\\secondary_computername\sharename).
KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;314515&sd=tech about complete FAQ sheet on Log shipping.
--
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Hassan" wrote:
> What happens when you check the " Allow database to assume primary role"
> option during log shipping setup. What happens if you dont check it ?
> Also, does anyone have any links as far as recovery procedures for a log
> shipping implementation used for disaster recovery..i.e. if Server A fails,
> what are the exact steps to follow to recover the application onto Server B
> which would also include changing the servername from Server B to Server A
> ...
>
>
Subscribe to:
Posts (Atom)