SQL server backup full with over 120 incrementals, does each backup have to be restored?

Have a SQL database restored all is well, problem is it restored to the full backup point and there are over 100 incremental backups made to the full backup. I believe each one has to be restore hoping I'm wrong or there is a way to skip and restore the latest incremental back to the database.
LVL 17
WORKS2011Austin Tech CompanyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Phillip BurtonDirector, Practice Manager and Computing ConsultantCommented:
Do you have any differential backups? If so, restore the latest one of those and then only the incremental backups thereafter.

Otherwise, you have over 100 backups to restore - sorry!
0
Steve WalesSenior Database AdministratorCommented:
Unless something has changed in the latest version of SQL Server (doesn't look like it according to the docs), there is no such thing as an "Incremental" backup for SQL Server.

There is a Full Database Backup.
There is a Differential Database Backup (all changes since last full backup)
There is a Transaction Log Backup

In the case you describe above, you should be seeing your 120 backups slowing growing in size as the changes keep coming after that full.

So, you should be able to do the Full, the most recent Differential and then any Transaction Logs to bring it up to as recent as possible.

Books Online can be helpful here too:

Backup and Restore of SQL Server Databases
Create a Differential Database Backup (SQL Server)
Differential Backups (SQL Server)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WORKS2011Austin Tech CompanyAuthor Commented:
Very good point, thank you. The Acronis backups are incremental how does this make the restore happen?
0
Steve WalesSenior Database AdministratorCommented:
Sorry, I am not familiar with that software.  Looking at their website, they specifically mention an incremental backup for SQL Server - you may want to look at the documentation and see what it says, or see what you can look at in the restore GUI.  We use Dell LiteSpeed - I can prep a restore in the restore GUI and it will show me all the files needed in the restore - does your tool offer that functionality ?
0
Racim BOUDJAKDJIDatabase Architect - Dba - Data ScientistCommented:
Log back ups are chained and are relative to one another so you in case of log backups you must apply of them using the NORECOVERY for 99 and recovery for the 100th
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Some applications calls Incremental backups to SQL Server Differential backups. That's wrong of course, since SQL Server doesn't has the option for Incremental backups.
I would guess that it's really differential backups and so you'll only need to restore the Full backup and the last Differential backup plus all the transaction log backups until the desired time of restore (STOP AT option).
0
Racim BOUDJAKDJIDatabase Architect - Dba - Data ScientistCommented:
I agree with Vitor: it's al about third party proprietary terminology and incremental could be differential.  However, I don't see any third party proposing a solution ending up with 100 differential backups which would kill space hence the product itself.  We can safely assume that most third party vendors mean log backups by incremental backups.  Hence a full restore of all backups with STOP AT seems the way to go...

0> Confirm with your vendor that incremental backups=log backups.
1> If incremental=log backups, Find and Restore the full backup in NO RECOVERY mode
2> Restore all incremental/log backups using STOP AT
3> Put the database in RECOVERY

Hope this helps...
0
WORKS2011Austin Tech CompanyAuthor Commented:
thank you
0
Racim BOUDJAKDJIDatabase Architect - Dba - Data ScientistCommented:
Tip: to speed up recovery process in case of a large database, and if you have a spare box somewhere, instead of simply doing you can set up an frequent log shipping process to the spare box.   If loosing a box you can redirect your queries without having to restore anything. (except putting the recover database in RECOVERY mode).  Simply set up an alias on the Active Directory for the DNS and redirect it on will.

Hope this helps.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.