DPM Express Full Backups Causing SQL timeouts

Hi,
We run a SQL 2008 R2 failover cluster on Server 2008 R2 SP1 connected to an Equallogic SAN. The SQL failover cluster is fully servicepacked and installed the latest cumulative updates.
We have all our databases in full recovery mode and protected by DPM 2012 SP1 with latest cumulative updates.
The protection groups for SQL are configured to synchronise every 60mins and 1 express full backup every night. Every time the SQL express backups run the SQL server experiences timouts and end users report applications timing out. In the SQL server Application
logs I see Event ID 833 numerous times, these only occur as the express full backups take place. Every time the express full backups run we see the same timeouts and event logged that I/O has taken longer than 15 seconds to complete:
Log Name: Application
Source: MSSQLSERVER
Date: 01/04/2014 04:10:10
Event ID: 833
Task Category: Server
Level: Information
Keywords: Classic
User: N/A
Computer: WDCSQL02.local
Description:
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x00000000000008F8. The offset
of the latest long I/O is: 0x000000042eae00
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSSQLSERVER" />
<EventID Qualifiers="16384">833</EventID>
<Level>4</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-01T03:10:10.000000000Z" />
<EventRecordID>14165629</EventRecordID>
<Channel>Application</Channel>
<Computer>WDCSQL02.local</Computer>
<Security />
</System>
<EventData>
<Data>1</Data>
<Data>15</Data>
<Data>D:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf</Data>
<Data>msdb</Data>
<Data>4</Data>
<Data>00000000000008F8</Data>
<Data>0x000000042eae00</Data>
<Binary>410300000A0000000600000055004B00530051004C00000000000000</Binary>
</EventData>
</Event>
I was under the impression that DPM SQL backups would remain online during the backup.
Is this normal?
Any way to fix this issue?
Thanks,
Microsoft Partner

Hi
A copy backup will not truncate the logs but a full backup will and it will also stamp the database once it does a full backup.

Similar Messages

System state synchronizations and express full backups of protected 2012 R2 machines overload DPM server.

I have one DPM 2012 R2 UR2 server which is running on Windows 2008 R2 and 2 protection groups (A, and B). The server uses direct attached storage for all replicas and recovery volumes.
Group A protects the system state and bare metal recovery of 25 Windows 2008R2 servers. It creates recovery points using express full backup each night at 6PM. The servers range from file/print, SQL, domain controllers, terminal servers, web servers, etc. Total
data 3TB.
Group B protects the system state and bare metal recovery of only 3 Windows 2012R2 servers. It creates recovery points using express full backup each night (morning) at 1AM. The servers are 1 domain controller, 1 WSUS server, and 1 server that runs VMware VCenter.
Total data 90GB.
During group A's nightly backup, which takes approximately 2 hours, the DPM server becomes noticeably slower but remains functional. I can open Windows update and check for updates, copy files to and from network locations, launch intenet explorer, etc. It's
stressed since 25 servers are creating backups on it but it remains functional.
During group B's nightly backup the DPM server grinds to a complete halt. Launching internet explorer takes an hour (literally), 10 minutes will pass before I get a menu after clicking the start button. Basically it becomes completely unresponsive until the
backups finish which typically doesn't happen because I'm forced to cancel them upon arriving at work...8 hours later.
I read that DPM uses the built in Windows Backup to protect system state and bare metal recovery. Did something change in Windows Backup from 2008R2 to 2012R2 that would cause this? Why can my DPM server easily backup 25 Windows 2008R2 machines at once in 2
hours yet freezes solid for 8 hours or more when backing up only 3 Windows 2012R2 machines?
I left performance monitor running during the night and it showed an average disk queue length of 49 during group B's backup but everything else was normal. Seems the disks on the DPM server are the bottleneck but again I ask why can my DPM server easily backup
25 Windows 2008R2 machines at once in 2 hours yet freezes solid for 8 hours or more when backing up only 3 Windows 2012R2 machines? Both protection groups use the same disks.
How can I fix this?
Teenage angst has paid of well, now I'm bored and old.

Hi CS,
You can also run a performance monitor.
For some basic perfmon counters to help narrow down the possible bottleneck:
Perf Counters for DPM
Logical Disk/Physical Disk
\%idle
• 100% idle to 50% idle = Healthy
• 49% idle to 20% idle = Warning or Monitor
• 19% idle to 0% idle = Critical or Out of Spec
\%Avg. Disk Sec Read or Write
• .001ms to .015ms = Healthy
• .015ms to .025 = Warning or Monitor
• .026ms or greater = Critical or Out of Spec
Current Disk Queue Length (for all instances)
80 requests for more than 6 minutes.
• Indicates possibly excessive disk queue length.
Memory
\Pool Non Paged Bytes*
• Less that 60% of pool consumed=Healthy
• 61% - 80% of pool consumed = Warning or Monitor.
• Greater than 80% pool consumed = Critical or Out of Spec.
\Pool Paged Bytes*
• Less that 60% of pool consumed=Healthy
• 61% - 80% of pool consumed = Warning or Monitor.
• Greater than 80% pool consumed = Critical or Out of Spec.
\Available Megabytes
• 50% of free memory available or more =Healthy
• 25% of free memory available = Monitor.
• 10% of free memory available = Warning
• Less than 100MB or 5% of free memory available = Critical or Out of Spec.
Processor
\%Processor Time (all instances)
• Less than 60% consumed = Healthy
• 51% - 90% consumed = Monitor or Caution
91% - 100% consumed = Critical
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Understanding replica volume and recovery point volume usage with SQL Express Full Backup

I am running some trials to test DPM 2012 R2's suitability for protection a set of SQL Server databases and I am trying to understand what happens when I create a recovery point with Express Full Backup.
The databases use simple recovery model and in the tests I have made so far I have loaded more data into the databases between recovery points since that will be a typical scenario - the databases will grow over time. The database files are set to autogrowth
by 10%
I have been looking at the change in USED space in the replica volume and in the recovery point volume after new recovery points and have a hard time understanding it.
After the first test where data was loaded into the database and an Express Full Backup recovery point was created, I saw an increase in used space in the replica volume of 85 Gb and 29 GB in the recovery point volume. That is somewhat more than I think
the database grew (I realize that should have monitored that, but did not), but anyway it is not completely far out.
In the next test I did the same thing except I loaded twice as much data into the database.
Here is where it gets odd: This causes zero increased usage in the replica volume and 33 GB increased use in the recovery point volume.
I do not understand why the replica volume use increases with some recovery points and not with others.
Note that I am only discussing increased usage in the volumes - not actual volume growth. The volumes are still their original size.
I have been using 3-4 days on the test and the retention period is set to 12 days, so nothing should be expired yet.

Hi,
The replica volume usage represents the physical database file(s) size. The database file size on the replica should be equal to the database file size on the protected server. This is both .mdf and .ldf files. If when you load data
into the database and you overwrite current tables versus adding new ones, or if there is white space in the database files and the load simply uses that white space, then there will not be any increase in the file size, so there will not be any increase
in the replica used space.
The recovery point volume will only contain delta changes applied to the database files. As the changed blocks overwrite the files on the replica during express full backup, VSS (volsnap.sys) driver copies the old blocks about to be overwritten
to the recovery point volume before allowing the change to be applied to the file on the replica.
Hope this helps explain what you are seeing.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM is Only Allowing Express Full Backups For a Database Set to Full Recovery Model

I have just transitioned my SQL backups from a server running SCDPM 2012 SP1 to a different server running 2012 R2. All backups are working as expected except for one. The database in question is supposed to be backuped up iwht a daily express
full and hourly incremental schedule. Although the database is set to full recovery model, the new DPM server says that recovery points will be created for that database based on the express full backup schedule. I checked the logs on the old DPM
server and the transaction log backups were working just fine up until I stopped protection the data source. The SQL server is 2008 R2 SP2. Other databases on the same server that are set to full recovery model are working just fine. If we
switch the recovery model of a database that isn't protected by DPM and then start the wizard to add it to the protection group it properly sees the difference when we flip the recovery model back and forth. We also tried switching the recovery model
on the failing database from full to simple and then back again, but to no avail. Both the SQL server and the DPM server have been rebooted. We have successfully set up transaction log backups in a SQL maintenance plan as a test, so we know the
database is really using the full recovery model.
Is there anything that someone knows about that can trigger a false positive for recovery model to backup type mismatches?

I was having this same problem and appear to have found a solution. I wanted hourly recovery points for all my SQL databases. I was getting hourly for some but not for others. The others were only getting a recovery point for the Full Express
backup. I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem. I was still not getting the hourly recovery points.
I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started. My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery
mode SCDPM continued to treat it as simple.
I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db.
It worked. The original db was still only getting express full recovery points and the copy was getting hourly. I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify
that it is set to full, and then add it back to protection. I have not tested this yet.
This is the article I read:
Article I read

Maximum Express full backups per day per Datasource?

I have 3 DB server having 24 databases. Some of these are SIMPLE recovery model and some are FULL. Express full backups are set one in a day at 8:00 PM and Synchronization is set to every 4 hours.
Now customer want to keep backup of every 2 hours. So I have some queries on this.
1) Its not possible to set EXPRESS full backup after 2 hours. So what should I do here, Should set synchronization frequency to 2 hours?
2) If I set Synchronization Frequency to 2 hours, it will backup only FULL Recovery model databases only? SIMPLE one will be backed up 8 PM only?
3) Incremental Backups recovery is only allow to restore Instance? cant be copy to Network folder? As when I tried to restore 4 hours synchronization backup it shows cant be copied, only recovery point associated with express backup will be copied.
4)Based on my understanding, I should change all recovery models to FULL and should set Synchronization to 2 Hours to achieve customer demand. It will allow me to restore 2 hours recovery point to directly Instance or another instance (But not to Network
folder and tape in case of Incremental recovery)
Am I right? Thoughts!
Thanks in Advance
VJay

See.
My 4 hours Synchronization frequency/Incremental backups are creating recovery points successfully and I can see these from recovery tab. But when I am trying to restore Incremental recovery point, it doesn't allowing me to restore. See in below image, I
am trying to restore Incremental recovery point which was created yesterday at 4:00 PM but its asking me to restore yesterday's 12:20 PM. This incremental backups tooks place after 12:20, doesn't mean anything in terms of recovery!
As my final decision, should I choose EXPRESS Full backup for evry 2 hours and Synchronization just before Express backup for these 24 databases since these are now in FULL model.

Express Full Backups

Good Afternoon,
I am thinking about setting my express full backup to run during the day during the day to decrease supporting this at night. My question is will this impact our databases to the point of customer impact. We currently do 4 sync jobs a
day, then a full backup on Friday night. Just trying to make sure there is no impact.
Thanks

It will also depend on how you are setup, if you have a DAG you can run a full backup against the passive copy. I would suggest doing an EF once a day at night and sync to what your recovery goal needs are.
Regards, A.Nadar, This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 backup Causes Redirected CSV IO on SOFS Cluster.

Hi, I have a Scale out Storage Spaces Server with 2 nodes, and a 10 node 2012 R2, Hyper-V cluster using this via SMB3.0
I also have installed a DPM2012 R2 backup server.
the DPM agent is installed on all nodes of all servers and I have followed the pre-requisite from Microsoft for setting up DPM backup of SMB Hyper-V machines.
The DPM backups all work fine. but occasionaly I get these errors on the SOFS cluster.
Cluster Shared Volume 'Volume3' ('Cluster Disk 4') has entered a paused state because of '(c0130021)'. All I/O will temporarily be queued until a path to the volume is reestablished.
I really thought this issue had been resolved in this revision, this doesn't seem to cause any issues with my VM's that I can notice. and all DPM backups are working fine, but it still causes me concern.
has anyone else seen this or have any suggestions what I can try to resolve.
Regards
Mark Green

We also encounter this issue. We use Windows Server 2012 R2 and SCVMM 2012 R2 (with RU1). Be carefull with this issue, because it can cause serious issues. Btw, note that Windows Server 2012 R2 used Direct I/O instead of Redirected I/O.
If you can't find a full fix as we are in right now, there are two things that might offer a work-around for you:
Disabled ODX (if your storage system does not support it):
Deploy Windows Offloaded Data Transfers
http://technet.microsoft.com/en-us/library/jj200627.aspx
Serialize virtual machine backups per node
Migrate to a hardware VSS provider
http://technet.microsoft.com/en-us/library/hh758027.aspx
The second option works best, because this issue mostly occurs when you run a backup of many VMs at once. It it not a full fix and makes you backup windows much longer, but can avoid you other problems. Also keep a close eye on this link:
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://support.microsoft.com/kb/2920151
Boudewijn Plomp, BPMi Infrastructure & Security

WIll cancel sql server database backup cause anything to be hurt?

I run full backup of one big database. After 20 seconds, I click "stop action now" to cancel this backup. Will it cause anything to hurt? Want to make sure that database is still safe.
Thanks

I run full backup of one big database. After 20 seconds, I click "stop action now" to cancel this backup. Will it cause anything to hurt? Want to make sure that database is still safe.
No it will not cause any issue to SQL server database.Backup request reads data from disk using separate thread you just killed the thread.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

DPM 2012 R2 Hyper-V backup of SQL server VM

Hello!
I have a question about using DPM 2012 R2 in Hyper-V 2012 R2 cluster and backing up Windows 2003 VM, that has SQL 2008 installed.
When i use VM, host level backup with DPM2012 R2, would it trigger a full DB backup on SQL server or not?
Problem is, that we are using SQL (maintanance plans) for backing up databases and doing transaction logs backup.
I want to back up the whole VM, but i want to be sure, that this would not mess up SQL backup inside the VM?
Is it possible, that i wont install DPM agent inside the SQL server VM? But can i then still restore files from the VHD/X or only entire VM?

Hi,
Apply the following registry entry in the GUEST virtual machine so application logs are not truncated by host level backups.
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtualization\VssRequestor
Name: BackupType
Type: REG_DWORD
Value: 1
If this registry entry is created and its value is set to 1 , application backup will not be affected by the virtual machine backup operation on the server that is running Hyper-V. If this registry entry does not exist, or if its value is 0 , then host level
backups will truncate logs in the guest.
Yes - you can perform item level recovery for files inside the .vhd by double-clicking the .vhd while browsing to restore the VM. That will mound the .vhd and allow you to copy files out without having to restore the entire .vhd file.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Automate SQL full backup

Dear Experts,
In our company we have a SAP 4.7 installed on MS SQL server 2000, Daily we need to stay untill all the users complete their work and fire the db13 backup and SQl query disk backup, for this i have scheduled a job in the SQL server enterprise manager and put a script where in i have to change the script everyday.
if you can provide me a script where in it changes the date & time of the file name every day automatically
The script i use is as follows:
use master
exec sp_addumpdevice 'disk','PRDF270807_1909','<path>\PRDF270807_1909'
backup DATABASE PRD to PRDF270807_1909
Kindly help me in this regards,
Thnx in advance
Kishore.

Hi,
i use this script to make a backup to a different device every week, you can easily modify this to a daily change. You can add a network share as target as well.
I have this script scheduled as a SQL Agent Job and it works like a charm.
Regards
Clas
declare @week varchar(3)
declare @devl varchar(20)
declare @devp varchar(400)
declare @dev varchar(20)
select @week = datepart(ww,getdate())
set @devl = 'vsdata_week_' + @week + '.db'
set @devp = 'c:\tools\VSWMI\Backup\vsdata_week_' + @week + '.db'
if not exists (select name from sys.backup_devices where name = @devl)
        exec sp_addumpdevice 'DISK',@devl,@devp
declare crs cursor for
        select name from sys.backup_devices
        where name like 'vsdata%' and
              name <> @devl
open crs
fetch next from crs into @dev
while (@@fetch_status = 0) begin
     exec sp_dropdevice @dev
     fetch next from crs into @dev
end
close crs
deallocate crs
BACKUP DATABASE [VSData] TO @devl WITH NOFORMAT, NOINIT,
NAME = N'VSData-Full Database Backup', SKIP, NOREWIND, NOUNLOAD,
STATS = 10, CHECKSUM, CONTINUE_AFTER_ERROR

DPM 2012 R2 protecting a SQL 2008 Cluster/Vss Writer problems on SQL Server

Hola,
I am running DPM 2012 R2 rollup 4. My Server OS is 2012 Datacenter. I have a SQL 2008 Active/Passive cluster and MS support has kicked this to the SQL team for review. OK hear we go ..When I run the vssadmin list writer I do see the SQL Writer. Also
says no errors. When I run diskshadow /l c:a.txt from an admin command prompt the output does show the SQL Writer information but under that should display all the meta data for each connection to the database so DPM can expand the SQL database to
be chosen for protection. I am already confused.
I am going to include a snippet from the vssadmin and the diskshadow command:
vssadmin list writers:
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {8d773b6f-0196-4c34-9943-f258f99c2d9a}
   State: [1] Stable
   Last error: No error
Diskshadow /l c:a.txt
* WRITER "SqlServerWriter"
  - Writer ID   = {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
  - Writer instance ID = {8d773b6f-0196-4c34-9943-f258f99c2d9a}
  - Supports restore events = TRUE
  - Writer restore conditions = VSS_WRE_ALWAYS
  - Restore method = VSS_RME_RESTORE_IF_CAN_REPLACE
  - Requires reboot after restore = FALSE
  - Excluded files:
* WRITER "BITS Writer"
  - Writer ID   = {4969d978-be47-48b0-b100-f328f07ac1e0}
  - Writer instance ID = {5ad5c4f7-5f68-4c1d-a4fc-92d5ef898881}
  - Supports restore events = TRUE
  - Writer restore conditions = VSS_WRE_UNDEFINED
  - Restore method = VSS_RME_UNDEFINED
  - Requires reboot after restore = FALSE
  - Excluded files:
   - Exclude: Path = C:\Windows\System32, Filespec = bits.log
   - Exclude: Path = C:\Windows\System32, Filespec = bits.bak
   - Exclude: Path = C:\ProgramData\Microsoft\Net
As you can see this did not return the expected results. I should see the meta data for each database. This is why DPM can't list the databases for backup in my 2008 production SQL cluster. Any thoughts? This has not been working for quite sometime. I was
hoping the update to rollup 4 would have fixed the problem. I know this is a SQL problem but has anyone had this experience?
Thanks
Steve J.

Update:
Uninstalled SQL Server instance and downloaded SQL Server 2012 SP1 image from link in error message. It takes you to the download page for the express edition of SQL Server 2012. I downloaded the SQLEXPRADV_x64_ENU file and used it to re-install
the SQL Server instance.
Ultimately I had to use the ISO image to upgrade the instance to Standard because the SQL Server Agent will not run under the express edition and caused the DPM install to fail.
The DPM installation then completed successfully and after immediately went to Windows Update and SQL Server 2012 SP2 was installed.
Evidently you cannot start with SP2 until the installation is complete.

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!!

Sharepoint Farm backup with powershell timeout

Hello experts.
I have faced with the problem using powershell script to manage automatic full farm backups with file rotations.
I use common script taken from this page
http://gallery.technet.microsoft.com/office/9b99c435-8831-4c9e-a70b-1f13158ef22a
And every was fine until backup procedure of wss_content database grew up to 1 hour
I have MS RBS configured for wss_content database and files in BLOB store have about 100Gb in summary
Now i can't build full backup and have error in spbackup.log
[12/4/2012 12:59:21 AM] Progress: [WSS_Content_MP27] 80 percent complete.
[12/4/2012 1:02:03 AM] Warning: [WSS_Content_MP27] Time is out. Server did not respond within the timeout period.
The backup or restore was aborted.
After that script try to repeat failed command 3 times using next statement
SQL command timeout is set to 1.00 hours
Question is how i can increase timeout for this operation?
Because for our database 1 hour is dramatically low value.
One week ago full backup of wss_content database takes 50 minutes.
Thanks.
ruslanin

Hi,
have you tried to used backupthread parameter like
Backup-SPFarm -Directory C:\Backup -BackupMethod full -BackupThreads 10 -ForceBackupThreads
Specifies the number of threads to be used during the backup. The fewer the threads, the easier the backup log file is to read and understand. The more the threads, the more components that can be backed up in parallet, potentially resulting in a faster backup operation. The minimum value is 1 and the maximum value is 10.
The default value is 3.
If a backup is performed with the –ShowTree parameter, then the BackupMethod parameter is not used.
http://technet.microsoft.com/en-us/library/ff607881.aspxWhere you are backing up ur data local drive or shared drive, also check connectivity and speed incase of shared drive.thx
iffi

Will Log Backup cause issue?

Hi Experts,
we have been getting complaints from application users about slowness on and off. tried all the ways, no clues. finally, one business user is helping me with the exact timings of slowness in the application. the trend is exactly at the time of log backup
happening time. log backups are completing in less 30 sec. even the slowness is only at that time.
Now I didn't understand, will log backups cause slowness to the databases access? I believe, full backups will cause a bit.
please help.
thanks in advance
Vinod Mallolu
Cheers, Vinod Mallolu

Hi Vinod,
It really depends on I/O subsystem and your server configuration. For example:
Poorly performing I/O subsystem can cause poor during log backups.
Poor performance can occur if your database log drive is same as your backup drive. If you are using SAN then make sure that both drives are not commissioned from same LUN.
Transaction Log activity and the size of your log files. If your database is highly transactional database than you should experience some slowness if you are performing Log backups. If you are using SQL Server 2012 or about with Enterprise edition and
have standby server than use Availability Groups to offload your transaction log backups.
Increasing the frequency of log backup also helps.
I hope this information is useful for you to rectify the issue.
Regards,
Basit A. Farooq (MSC Computing, MCITP SQL Server 2005 & 2008, MCDBA SQL Server 2000)
http://basitaalishan.com
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

User did an append when doing a backup of SQL now trying to do a restore

User did a backup of SQL doing an append now getting the message:
The media set has 2 media families.....
The directory of the first media set was copied to an external drive. The system was then wiped to load Win7 what can be done to restore the files?
Bonnie Whalon

Hello,
The command I use was:
restore filelistonly FROM DISK = N'C:\Freedom Ente\Client Data Backup\Sewickley-fsc-backup-20140403'
The error message
Msg 3201, Level 16, State 2, Line 1
Cannot open backup device 'C:\Freedom Ente\Client Data Backup\Sewickley-fsc-backup-20140403'. Operating system error 5(Access is denied.).Msg 3013, Level 16, State 1, Line 1RESTORE FILELIST is terminating abnormally.
I gave myself full rights to the directory.
Bonnie Whalon

DPM Express Full Backups Causing SQL timeouts

Similar Messages

Maybe you are looking for