SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Basuc question about High Availability solution.


Basuc question about High Availability solution.

Author
Message
SQL*
SQL*
Say Hey Kid
Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)

Group: General Forum Members
Points: 668 Visits: 1726
Hi,

I am very new to the DBA scenarios, i am learning the things from the Online stuff.

For high availability solution:
1. We need to take the full backup.
2. We need to take the T-Log backup.

My Question is:

Is full backup doesn't contains the Log backup (As per my knowledge full backup takes the Transaction log also.)? If yes what is the use of taking again T-Log backups.

Please provide info on these basic questions.

Thanks,

:-)
Perry Whittle
Perry Whittle
SSC-Insane
SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)

Group: General Forum Members
Points: 20248 Visits: 17244
SQL* (9/17/2012)
Hi,

I am very new to the DBA scenarios, i am learning the things from the Online stuff.

For high availability solution:
1. We need to take the full backup.
2. We need to take the T-Log backup.

My Question is:

Is full backup doesn't contains the Log backup (As per my knowledge full backup takes the Transaction log also.)? If yes what is the use of taking again T-Log backups.

Please provide info on these basic questions.

Thanks,

I'm assuming you're referring to backup regimes is this correct?

Full backups will form the base of your recovery solution with logs and\or differentials to bring databases up to a set point in time

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Grant Fritchey
Grant Fritchey
SSC-Forever
SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)

Group: General Forum Members
Points: 40661 Visits: 32666
Full backups do not contain the transaction logs. That's a myth. A full backup has a complete copy of the database including all completed transactions up to the point of the backup. Any incomplete transactions are cleaned up as part of the restore process.

The thing is, a full backup, depending on the size of your system, can take quite a while and will use some system resources. So you can't run a full backup every 1/2 hour on most production systems. Instead, other backups are used in combination to protect the data in a more granular fashion. That's what log backups are for. They backup just the transaction log. This allows for very fast, lightweight backups, and, as was already mentioned, the ability to restore to a specific point in time. A full backup can only be restored to when it occurred. Logs can be restored to specific moments.

Backups are not a technology problem. They're a business problem. Talk to your business and find out exactly how much time they can afford to lose on the database. If that number is small, you're going to need to work on setting up a recovery mechanism that covers the business adequately.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
SQL*
SQL*
Say Hey Kid
Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)

Group: General Forum Members
Points: 668 Visits: 1726
Thank you,

I have read in blogs/books that, when we are setting up mirroring/Log shipping we have to take the both Full backup&Transactional backup and restore them to the secondary server as an initial step.

If the Full backup contains all the completed transactions then what is the benefit of again taking the Transactional backup again?

Even if we take the t-log if that contains not completed transactions those will not be committed over secondary right?


Kindly explain.

:-)
Grant Fritchey
Grant Fritchey
SSC-Forever
SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)

Group: General Forum Members
Points: 40661 Visits: 32666
Because you have to take an initial transaction log backup to begin that process. You're setting up log shipping. It requires you to have logs to ship. The log being referred to is the transaction log. The way you back it up, is the transaction log backup.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
SQL*
SQL*
Say Hey Kid
Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)

Group: General Forum Members
Points: 668 Visits: 1726
That means, with out Transaction log (Only with the Full Backup) the log shipping and Mirroring will not work.

I could have try but i need to get the confirmation form the experts. I have not find any information related to this question.

Thank you for your time.

:-)
Perry Whittle
Perry Whittle
SSC-Insane
SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)

Group: General Forum Members
Points: 20248 Visits: 17244
SQL* (9/17/2012)
I have read in blogs/books that, when we are setting up mirroring/Log shipping we have to take the both Full backup&Transactional backup and restore them to the secondary server as an initial step.

That's Database Mirroring, Log shipping doesn't require you to take at least one log backup, you only need to initialise the secondary database from a full backup of the primary or let the Log Shpping wizard do this for you.

Furthermore, for mirroring Books Online goes on to say the following

Books Online
Typically, at least one log backup must be taken on the principal database, copied to the mirror server, and restored on the mirror database (using WITH NORECOVERY). However, a log backup might be unnecessary, if the database has just been created and no log backup has been taken yet, or if the recovery model has just been changed from SIMPLE to FULL.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
SQL*
SQL*
Say Hey Kid
Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)

Group: General Forum Members
Points: 668 Visits: 1726
However, a log backup might be unnecessary, if the database has just been created and no log backup has been taken yet, or if the recovery model has just been changed from SIMPLE to FULL


Is there any specific reason on this restriction?

:-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search