Differential backup and tlog backup

Hi,
What is the advantage of doing a differential backup along with transactional log backup? For instance, if I'm planning on doing a weekly full backup and daily transactional log backups what does doing an differential backup get me? Does it make restoring
faster? Is it better to have that differential in case one of the transactional log backups are corrupt?
Please advise.
Thanks,
Phil

What is the advantage of doing a differential backup along with transactional log backup? For instance, if I'm planning on doing a weekly full backup and daily transactional log backups what does doing an differential backup get me? Does it make restoring
faster
Phil,
The best use of Differential backup is to reduce the RTO. It does not have any much special meaning. There is no disadvantage as such apart from disk getting filled with too many diff backups.
It makes restoring faster in sense that you have to restore fewer numbers of backup and this decreases time to bring DB online when disaster strikes.
Is it better to have that differential in case one of the transactional log backups are corrupt?
If transaction log is corrupt there are chances that differential backup could also be corrupt. Your question does not have actual meaning. I guess you wanted to ask can we skip transaction log backup and restore latest Diff backup. Well you can as long
as it is not corrupt.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Similar Messages

Restore log and differential backups on a Publication database.

Hi, i have the following issue, i have to restore a log backup and a differential backup in a publication database, the problem is that i want to keep the publications and the subscriptions without recreate the subscriptions.
So how can i perform this goal :/ is somebody know how can i do that please let me know :D !!! thanks in advance.
In my case is a merge replication....

For merge replication you do not need to worry about the log reader agent - in fact there should not be one. Ensure that you use the keep_replication switch when doing the restore.
Note that for merge replication the subscriber will backfill the publisher with changes in the publisher which are not in the subscriber. After this is done you might want to do a tablediff, but it should not be necessary, depending on how recent your full
and differential backups were done.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Procedure restore Differential backup and to restore windows 2003 server

Hello All,
i am sticking at some of the points
1. As per company policy they want to take full SAP offline + Redo log files backup once every two week and twice a week the differential backup. I suggested them the differential backup twice a week but now i have a question in mind since i never done it practically Do i need to have anything else like Log file to restore the Differential backup apart from full SAP backup or i can restore data with only Full SAP backup and differential backup.
2. I am not much familiar with Windows 2003 server backup, If i take full Widows 2003 server backup will i be able to restore windows server along with installed SAP and all other software in case something happen to my server.
if the answer is yes what are the pre-requisite if there be any to do the same. from the pre-requisite i mean do i need to be on same hardware as my previous server was or i can restore it on any other system too?
i will appreciate any reply on the same.
Mani

Hi Mandy,
      I am not sure weather you are treating Windows 2003 and SAP Backup i.e SQL Backup as two seperate things.
   SQL Backup : If you take MS SQL Backup ( directly from MSSQL or Schdule it from SAP DB13) and take full backup once a week or twice a week eg: Sunday full backup followed by monday, tuesday differential(Midnight) backups and Wednesday full backup again followed by Thursday and Friday differential(midnight).
     Should the database need to be restored to thursday @ 4:30 AM, you will restore Wednesday full backup + Thursday diffential + any log files backup taken there after.
Windows 2003 Backup:
            Regarding this, You do not have to take Full Windows backup every day. You may take backup of few files / network drives, which can be restored directly while you are logged in to Server. It is sright forward.
           Sienario: When whole C drives of Windows crashed. To prepare for this sicenaro, you should take Windows system backup when ever you make chnages to kernal, SQL upgrade or before and after Windows patching.
         If the server crashes due to hardware failure, you should restore the server from backup .. ( for this there are different methods, like boot from boot disk and attach tape drive and restore or boot from disk and attach to NAS device and restore, you have to refer Windows 2003 restoration methods or consult your Windows specilist) which will bring back OS, kernal and SQL to normal state. and followed by SQL restore.
       Hope this helps.
Krishna

Differential backup files are almost the same size as full backups.

Hello All,
I have done a little research on this topic and feel like we are not doing anything to cause this issue. Any assistance is greatly appreciated.
The details: Microsoft SQL Server 2008 R2 (SP2) - 10.50.4297.0 (X64) Nov 22 2013 17:24:14 Copyright (c) Microsoft Corporation Web Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor). The
database I am working with it 23GB. The full backup files are 23GB, differentials are 16GB (and growing) and transaction logs bounce between 700KB to 20MB. The backup schedules with T-SQL follow:
T-Log: daily every four hours
BACKUP LOG [my_dabase] TO DISK = N'F:\Backup\TLog\my_dabase_backup_2015_03_23_163444_2725556.trn' WITH NOFORMAT, NOINIT, NAME = N'my_dabase_backup_2015_03_23_163444_2725556', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
Diff: once daily
BACKUP DATABASE [my_database] TO DISK = N'F:\Backup\Diff\my_database_backup_2015_03_23_163657_1825556.dif' WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'my_database_backup_2015_03_23_163657_1825556', SKIP, REWIND, NOUNLOAD, STATS =
10
GO
declare @backupSetId as int
select @backupSetId = position from msdb..backupset where database_name=N'my_database' and backup_set_id=(select max(backup_set_id) from msdb..backupset where database_name=N'my_database' )
if @backupSetId is null begin raiserror(N'Verify failed. Backup information for database ''my_database'' not found.', 16, 1) end
RESTORE VERIFYONLY FROM DISK = N'F:\Backup\Diff\my_database_backup_2015_03_23_163657_1825556.dif' WITH FILE = @backupSetId, NOUNLOAD, NOREWIND
GO
Full: once weekly
BACKUP DATABASE [my_database] TO DISK = N'F:\Backup\Full\my_database_backup_2015_03_23_164248_7765556.bak' WITH NOFORMAT, NOINIT, NAME = N'my_database_backup_2015_03_23_164248_7765556', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
declare @backupSetId as int
select @backupSetId = position from msdb..backupset where database_name=N'my_database' and backup_set_id=(select max(backup_set_id) from msdb..backupset where database_name=N'my_database' )
if @backupSetId is null begin raiserror(N'Verify failed. Backup information for database ''my_database'' not found.', 16, 1) end
RESTORE VERIFYONLY FROM DISK = N'F:\Backup\Full\my_database_backup_2015_03_23_164248_7765556.bak' WITH FILE = @backupSetId, NOUNLOAD, NOREWIND
GO
As you can probably tell we are not doing anything special in the backups, they are simply built out in MSSQL Management Studio. All databases are set to full recovery mode. We do not rebuild indexes but do reorganize indexes once weekly and also update
statistics weekly.
Reorganize Indexes T-SQL (there are 255 indexes on this database)
USE [my_database]
GO
ALTER INDEX [IDX_index_name_0] ON [dbo].[table_name] REORGANIZE WITH ( LOB_COMPACTION = ON )
GO
Update Statistics T-SQL (there are 80 tables updated)
use [my_database]
GO
UPDATE STATISTICS [dbo].[table_name]
WITH FULLSCAN
GO
In a different post I saw a request to run the following query:
use msdb
go
select top 10 bf.physical_device_name, bs.database_creation_date,bs.type
from dbo.backupset bs
inner join dbo.backupmediafamily bf on bf.media_set_id=bs.media_set_id
where bs.database_name='my_database'
order by bs.database_creation_date
Results of query:
physical_device_name database_creation_date type
F:\Backup\Full\my_database_backup_2015_03_07_000006_2780149.bak 2014-02-08 21:14:36.000 D
F:\Backup\Diff\Pre_Upgrade_OE.dif 2014-02-08 21:14:36.000 I
F:\Backup\Diff\my_database_backup_2015_03_11_160430_7481022.dif 2015-03-07 02:58:26.000 I
F:\Backup\Full\my_database_backup_2015_03_11_160923_9651022.bak 2015-03-07 02:58:26.000 D
F:\Backup\Diff\my_database_backup_2015_03_11_162343_7071022.dif 2015-03-07 02:58:26.000 I
F:\Backup\TLog\my_database_backup_2015_03_11_162707_4781022.trn 2015-03-07 02:58:26.000 L
F:\Backup\TLog\my_database_backup_2015_03_11_164411_5825904.trn 2015-03-07 02:58:26.000 L
F:\Backup\TLog\my_database_backup_2015_03_11_200004_1011022.trn 2015-03-07 02:58:26.000 L
F:\Backup\TLog\my_database_backup_2015_03_12_000005_4201022.trn 2015-03-07 02:58:26.000 L
F:\Backup\Diff\my_database_backup_2015_03_12_000005_4441022.dif 2015-03-07 02:58:26.000 I
Is your field ready?

INIT basically intializes the backup file, in other words, it will overwrite the contents of the existing backup file with the new backup information.
basically, what you have now is you are appending all you backup files (differentials) one after the other (like chain).
you do not necessarily have to do it. these differential backups can exist as different files.
Infact, I would prefer them to separate, as it gives quick insight on the file, instead doing a "restore filelist" command to read the contents of the backup file.
The point Shanky, was mentioning is that : he wants to make sure that you are not getting confused between the actual differential backup file size to the physicial file size(since you are appending the backups) example : if you differential backup is 2
gb, and over the next five you take a differential backup and append to a single file,like you are doing now, the differential backup file size is 2gb but you physicial file size is 10Gb. he is trying to make sure you are confused between these
two.
Anyways, did you get a chance to run the below query and also did you refer to the link I posted above. It talks a case when differential backups can be bigger than full backups and ' inex reorganize' or 'dbcc shrinks' can cause this.
--backup size in GB
select database_name,backup_size/1024/1024/1024,Case WHEN type='D' then 'FULL'
WHEN type='L' then 'Log'
When type='I' then 'Differential' End as [BackupType],backup_start_date,backup_finish_date, datediff(minute,backup_start_date,backup_finish_date) as [BackupTime]
from msdb.dbo.backupset where database_name='mydatabase' and type in ('D','I')
order by backup_set_id desc
Hope it Helps!!

Hourly differential backups are too big

Hello,
Please let me first apologize if this isn't the correct forum.
I'm having a problem that, for the life of me, I can't seem to resolve. To begin with, I'm using MSSQL Server 2012.
I created a new MSSQL maintenance plan to perform a full nightly (12:00 am) backup for one of our databases. This new plan replaced an old plan that did nothing but perform a full backup. With this new plan I do the following:
Check DB Integrity, Backup DB (full), Shrink DB, Rebuild Index, Clean Up History, Maintenance Cleanup Tasks.
The size of our DB is only 12GB
Now, the new plan took effect last Friday and it functioned properly as it made a full backup of the DB. The problem I'm having is that the differential backups I'm also doing every hour are now 10 times as big as they were before the new plan went into effect.
Just to compare, before midnight Friday (when the new full backup plan took effect), my hourly differential backups were only in the range of 750MBs. My first differential backup after that came to 4+ GBS. So, as you can see, the increase is somewhat
alarming. Being that we have individual maintenance plans for both full and differential backups and being that I did not touch/modify our differential plan, can anyone please tell me why the size of these hourly differential backup plans are so big now? How
is it that creating a new full backup plan affect the size of the differential files? Could this have anything to do with me doing db shrinks and/or Index rebuilds?
I'm at a loss here so I will really appreciate any feedback on this. Thank you very much!
Rob
P.S. Just in case, here's a screenshot of the differences:

Hi Rob,
Rebuilding all indexes daily is not necessary. I would actually recommend you to use the free solution by Ola Hallegran which only rebuilds indexes if an index is fragmented. I would not use or recommend to use maintenance plans for rebuild indexes/update
stats as it lack many options and also Ola's solution is free and is used by 1000's of dba's across the globe.
Yeah...but not supported by Microsoft. Use it at your own risk.
It is better to use Maintenance Plan Wizard, a proper Microsoft product:
Use the Maintenance Plan Wizard
Generally, indexes should be rebuilt periodically like every weekend or every month end.
STATISTICS should be updated nightly.
Missing indexes should be eliminated.
Optimization: http://www.sqlusa.com/articles/query-optimization/
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

Differential backup files--how long should I keep them?

Our SQL server administrator had scheduled SQL diferential backup every night since February 2012. The backup files have been stored in a folder on the server which now has the size over 8 GB. All the differential backup files are in this folder.
I am thinking we only need them for 30 days (with the full backup available). So can I remove the differential backup files manually? Thanks!

. I am thinking we only need them for 30 days (with the full backup available). So can I remove the differential backup files manually? Thanks!
You should not ask this question here how can we tell whether you can remove anything or not. But yes keeping Diff files from 2012 onwards on harddrive is not a good idea. Discuss same with you manager of course you need to to delete and keep files only for
a month.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Veritas MS SQL differential backup interrupt MS SQL Native differential backup

I have MS SQL 2005 Enterprise edition and I am taking weekly(Every Sunday) full backup and daily differential backup using Veritas backup tool.
Now I got request from application team to take SQL native full backup on Tuseday and daily differential backup till next 2 days(i.e., till Thursday.) and keep intact current veritas backup strategy of daily differential and weekly full backup
Now my question is will My MS SQL differential native backup will hamper by daily Veritas SQL differential backup or vice versa.
Thanks in Advance!!!!!

Hi,
You should ask Veritas about this question whether Veritas backup would affect SQL Server backup or not I guess it will do.
Now a solution here can be
copy only backup. But unfortunately there is no meaning of differential copy only backup but you can take copy only log backup. What copy only backup does is it does not affect the current backup sequence which is occurring neither effects the restore.
Now since you already have full and diff backup in place why cant you use Veritas backup.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Restoration of Differential Backup

Hi,
I am running Microsoft SQL server 2008 in our environment. I have created one new database and configured Full and differential Backups.Full backup on every week and differential backup on every day.Now the database went to recovery mode accidentally.
I have not yet taken Full backup for that particular database.I have only the Differential backup.
While i am trying to restore that differential backup its showing an error.Its not allowing me to restore.
Please help me to solve this problem.
Vinodh Selvaraj

Hi,
I am running Microsoft SQL server 2008 in our environment. I have created one new database and configured Full and differential Backups.Full backup on every week and differential backup on every day.Now the database went to recovery mode accidentally.
I have not yet taken Full backup for that particular database.I have only the Differential backup.
While i am trying to restore that differential backup its showing an error.Its not allowing me to restore.
Please help me to solve this problem.
Regards,
vinodh selvaraj.
Vinodh Selvaraj
Hello,
You cannot take differential backup without taking full backup.You have to first restore full backup with no recovery and then latest differential backup taken after full backup with recovery.
What is the error which you are facing?
Duplicate post
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/91c2ac7e-b122-426a-8a52-62ad452551c0/restoration-of-differential-backup?forum=sqldatabaseengine
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Differential backup failed because old backup does not exist

Hi,
We scheduled the backups of TFS through the TFS Administration console.
* Full each sunday at 18:00
* Differnetial each evening at 22:00
* Transactional each hour
* rentention time 8 days
The differential back-ups of Monday (20-4) and Thuesday (21-4) did go well. But for some reason the differential of Wednesday and Thursday didn't work out.
Start of log file of 21-4:
[21-4-2015 20:00:00] [Info] Requested Backup Job: Differential
[21-4-2015 20:00:00] [Info] -------------------------------------------------------------------
[21-4-2015 20:00:00] [Info] Jobs Requested: Differential. Completed:None. To Run:Differential.
[21-4-2015 20:00:00] [Info] RunDifferentialBackupJob
[21-4-2015 20:00:00] [Info] Scanning configuration for new DBs
[21-4-2015 20:00:00] [Info] BackupSettings changed ? False
[21-4-2015 20:00:00] [Info] Starting differential backups
[21-4-2015 20:00:00] [Info] Database Tfs_Configuration parent is 9859022596859328236
[21-4-2015 20:00:00] [Info] Starting Differential Backup server:RDSQL11\TFS database:Tfs_Configuration filename:\\RDSQL11\Backup$\Tfs_Configuration_9859024468858452975D.bak
[21-4-2015 20:00:00] [Info] BACKUP DATABASE [Tfs_Configuration] TO DISK = N'\\RDSQL11\Backup$\Tfs_Configuration_9859024468858452975D.bak' WITH DIFFERENTIAL, NOFORMAT, NOINIT, NOSKIP, REWIND, NOUNLOAD, STATS = 10
[21-4-2015 20:00:01] [Info] Backup Complete for database Tfs_Configuration
On 22-4 the log looks like this:
[22-4-2015 20:00:00] [Info] Requested Backup Job: Differential
[22-4-2015 20:00:00] [Info] -------------------------------------------------------------------
[22-4-2015 20:00:00] [Info] Jobs Requested: Differential. Completed:None. To Run:Differential.
[22-4-2015 20:00:00] [Info] RunDifferentialBackupJob
[22-4-2015 20:00:00] [Info] Scanning configuration for new DBs
[22-4-2015 20:00:00] [Info] BackupSettings changed ? False
[22-4-2015 20:00:00] [Info] Starting differential backups
[22-4-2015 20:00:00] [Info] Database Tfs_Configuration parent is 9859022596859328236
[22-4-2015 20:00:00] [Info] Starting Differential Backup server:RDSQL11\TFS database:Tfs_Configuration filename:\\RDSQL11\Backup$\Tfs_Configuration_9859025332862172100D.bak
[22-4-2015 20:00:00] [Info] BACKUP DATABASE [Tfs_Configuration] TO DISK = N'\\RDSQL11\Backup$\Tfs_Configuration_9859025332862172100D.bak' WITH DIFFERENTIAL, NOFORMAT, NOINIT, NOSKIP, REWIND, NOUNLOAD, STATS = 10
[22-4-2015 20:00:00] [Error]
Exception Message: Cannot perform a differential backup for database "Tfs_Configuration", because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option.
BACKUP DATABASE is terminating abnormally. (type SqlException)
SQL Exception Class: 16
SQL Exception Number: 3035
SQL Exception Procedure:
SQL Exception Line Number: 1
SQL Exception Server: RDSQL11\TFS
SQL Exception State: 1
SQL Error(s):
SQL Error[1]: System.Data.SqlClient.SqlError: BACKUP DATABASE is terminating abnormally.
    Class: 16
    Number: 3013
    Server: RDSQL11\TFS
    Source: .Net SqlClient Data Provider
    State: 1
    Procedure:
    Line Number: 1
Exception Data Dictionary:
HelpLink.ProdName = Microsoft SQL Server
HelpLink.EvtSrc = MSSQLServer
HelpLink.EvtID = 3035
HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
HelpLink.LinkId = 20476
So this is the same parent and the the file is still present on disk.
Can someone point in a direction to solve this issue?
Thanks!!

Hi RemkoP,
Based on your description, you can check whether you have a full backup file in your backup folder. Differential backups are backups of the changes that have occured since your last full database backup. If there no full backups, then we cannot perform a
differential backup.
You might do a full backup for the database, then do the differential backup. If you have any other concerns, please elaobrate more details about your scenario and reproduce steps.
Best regards,

Restore Differential Backup

Hi Balmukund,
We are using Sql server 2005 in production server.we are maintaining two servers.. one for current day & another for Archive data .For the past few months we taking the full backup & restoring the same in the Archive sever.Now the volume
got increased & it takes too much time to restore the full backup.So i am planning to restore the differential backup on the daily basis.I am planning as mentioned below,
Weekly once (say Sunday)- Full backup
Daily backup say Monday to Saturday) - Differential backup.
So i can restore the full backup on day 1 morning.
and can restore differential backup on day 2 morning.
From day 3 to day 6 onwards,how can i restore the same.
Kindly send the script for the same or give me any other idea for the same.

Hi... Balmukund
Restored the full backup on day 1 morning.
and restored differential backup on day 2 morning
From day 3 onwards restored the latest differential backup and
changed the database to Standby / No recovery mode
for some reasons, I changed the database mode using the following script.
ALTER DATABASE [DatabaseName] SET READ_WRITE WITH NO_WAIT
Now my question is ,
Kindly confirm Is it possible to restore differential backup in that database
What was the output of your alter database command? Also, if your db is still in restoring mode, you can restore additional diff backups on it. You can check the status of your db with the below query. If the status = online and is_in_standy = 0 then
you have recovered the db and cannot restore additional backups. Will need to restart from full and lates diff again. HTH
select
name,
state_desc,is_in_standby
from sys.databases
HTH...

Differential backup cleanup tasks leave empty files behind

Hello,
I have a full backup done weekly and then differential backups every 4 hours. Both backups are followed by cleanup tasks. Full backups and cleanup tasks run with no problems and so do differential backups too and their cleanup tasks, but sometimes differential
backup cleanup leaves behind empty files (0 bytes in size).
I checked the logs, and differential backup tasks are completing succesfully and I can see the backup files being created too and being cleaned up too, but sometimes there are empty backup files left over. I had the same issue while using SQL Server maintenance
tasks and Ola Hallengren's SQL Server Maintenance Solution. I tried googling and asking Ola too but couldn't come up with a solution.
Has anybody else had anything like this happenning or has any idea what might be causing this?

Hello,
A 0 byte file generally means there was a problem with whatever created it. Maintenance plan cleanups check the file header to see if it's a SQL Server backup file. If it isn't, it won't delete it thus the reason why it's "left behind". figure
out why the files are created as 0 bytes and if that can be fixed, there will be no cleanup issue.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Sharepoint full farm backup generates sql logs for search application differential backups

We are running full farm backups for sharepoint. Backup completes normally but SQL logs are generated for differential backups for search service application.
it says something like:
Database differential changes were backed up: database: search_serv.......
Thanks,
Basit

This can happen for a few reasons, such as is disk contention or network issues. Are you backing up to a shared directory on the SQL Server? If not, try that.
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Snapshots interfering with differential backups

1- Setup full backs to happen Saturday nights.
2- Setup differential backups to happen every night, execpt Saturdays
3- This is on a VM machine, and we take a snapshot of it every Wednesday night.
4- SQL Server records the snapshot as a valid, full backup, although it is marked as is_snapshot = 1.
5- All differential backups after the snapshot are rendered useless. They are done based on the snapshot backup, not on the actual valid full backup done on Saturday.
After research I found KB article 951288 (http://support.microsoft.com/kb/951288). Apparently this is a Microsoft issue.
So, how do we tell SQL server to ignore the snapshot backup when doing the differential backups? And no, we do not want to stop doing our snapshots on Wednesdays. Is there a solution or a work around to this?
This is really annoying and dangerous that SQL Server would consider these snapshots as valid, viable full backups on which to base its differential backups.
Help much appreciated,
Raphael
rferreira

Hi Raphael,
According to the following document, virtualization Snapshots for Hyper-V or for any virtualization vendor are not supported to use with SQL Server in a virtual machine. I want to confirm whether there is any other important application running on the VM
machine. If not, we can turn off VM Snapshot, if the VM machine failed, we just need to restore the database backup. For more detail information, please refer to the following link:
Support policy for Microsoft SQL Server products that are running in a hardware virtualization environment
http://support.microsoft.com/?id=956893
Allen Li
TechNet Community Support

Huge differential backup

My differential backup is huge even after a full backup.
When i do a full backup, the differential backup starts with 5GB, and grows only 30mb each hour. I need a help to solve this problem, because i don´t know why it's starting too big.
tks.

Hello,
Please examine jobs on the system and look for recurrent run jobs using logged statements. That could be one possibility.
Take in consideration that just one small change on an extent (1 extent = 8 x 8 KB pages = 64 KB) and the whole extent is included on
the differential backup.
Are you using different tools to backup your database? Are you using SQL Server native tool and a third party tool? That could explain
that behavior too.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Restore one full backup(need to move), 1 differential backup,2 transaction log backup

Is following script correct? I don't need to add "move" when do restore differential, log later. Correct?
RESTORE DATABASE AdventureWorks FROM DISK = 'C:\AdventureWorks.BAK'
WITH
MOVE
'Adventureworks_DB'
TO
'C:\test\Adventureworks.mdf',
MOVE
'AdventureWorks_Log'
TO
'C:\Adventureworks_Log.ldf',
WITH NORECOVERY
GO
RESTORE DATABASE AdventureWorks FROM DISK = 'C:\AdventureWorks.DIF'
WITH NORECOVERY
GO
RESTORE LOG AdventureWorks FROM DISK = 'C:\AdventureWorks.TRN'
WITH NORECOVERY
GO
RESTORE LOG AdventureWorks FROM DISK = 'C:\AdventureWorks2.TRN'
WITH RECOVERY
GO

Yes, that would be fine. It will work without move filename as well. You can add replace parameter incase.
Also, make sure to check the mentioned path they must exist and SQL is able to access
Before running the restore run below to check the backup file path:
Corrected the script with needed only once in full backup restore
Restore filelistonly from disk= 'C:\AdventureWorks.BAK'
RESTORE DATABASE AdventureWorks FROM DISK = 'C:\AdventureWorks.BAK'
WITH MOVE'Adventureworks_DB'TO'C:\test\Adventureworks.mdf',
MOVE'AdventureWorks_Log'TO'C:\Adventureworks_Log.ldf',
NORECOVERY, replace
GO
RESTORE DATABASE AdventureWorks FROM DISK = 'C:\AdventureWorks.DIF'
WITH NORECOVERY, replace
GO
RESTORE LOG AdventureWorks FROM DISK = 'C:\AdventureWorks.TRN'
WITH NORECOVERY, replace
GO
RESTORE LOG AdventureWorks FROM DISK = 'C:\AdventureWorks2.TRN'
WITH RECOVERY, replace
GO
Please let us know if you face any issue
Please click the Mark as answer button and vote as helpful if this reply solves your problem

Differential backup and tlog backup

Similar Messages

Maybe you are looking for