Skip to main content

MSSQL Server Differential Backup Failure

Log Job History (TestDB_Maintenance_Plan.TestDB_Diff_Subplan)
Step ID 1
Server TestSRV
Job Name TestDB_Maintenance_Plan.TestDB_Diff_Subplan
Step Name TestDB_Diff_Subplan
Duration 00:00:05
Sql Severity 0
Sql Message ID 0
Operator Emailed 
Operator Net sent 
Operator Paged 
Retries Attempted 0

Executed as user: TestSRV\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 09:27:33 Progress: 2012-12-07 09:27:35.66 Source: {1F5637A5-DB54-422D-951C-AC4998857244} Executing query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp...".: 100% complete End Progress Error: Code: 0xD227A348 Source: TestDB Diff Back Up Database Task Execute SQL Task Description: Executing the query "BACKUP DATABASE [TestDB] TO DISK = N'E:\MSSQL\Bac..." failed with the following error: "Cannot perform a differential backup for database "TestDB", 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.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 09:27:33 Finished: 09:27:36 Elapsed: 2.949 seconds. The package execution failed. The step failed.

If you run into this error that's because since the last differential backup has been taken, there must be another task that ran a backup log with truncate_only or recovered the database. So the log chain was broken. You need to take another full backup and then differential backup.


Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are,, respectively. Proper communication with other servers on the network we should use routing tables. There are three

3 Node (Master Slave Slave) Redis Cluster with Sentinel

It is possible to make your Redis cluster Fault Tolerant and Highly Available by building a replica set and then monitor these nodes using sentinel for automatic failover. I am going to give an example setup to explain it. The structure is built with three nodes running one as a master and two as slaves. Master Node: (Centos 7.2) Slave1 Node: (Centos 7.2) Slave2 Node: (Centos 7.2) Edit System settings on each node: /etc/sysctl.conf Disable transparent hugepage (transparent_hugepage=never) on each node: /etc/default/grub Apply grub config and reboot each node: Master Node: /etc/redis/6379.conf Slave1 Node: /etc/redis/6379.conf Slave2 Node: /etc/redis/6379.conf Master Node: /etc/redis/sentinel.conf Slave1 Node: /etc/redis/sentinel.conf Slave2 Node: /etc/redis/sentinel.conf Each Node: /etc/systemd/system/ Each Node: /etc/