You might have heard of this term, but you don’t know what it actually presumes.
Read this next article to understand what a copy-only backup is and how it fits in the big picture of SQL Server.
Having a complete backup history of all of your backup and restore operations can become quite useful at times.
All the data that you might need to be related to this, like who created the backup, at what time, on what media, and many other details are stored in the system databases of the SQL Server instance.
So, SQL Server 2014 CTP2 has been released and now we can have a look at some of its new features before its official commercial release later this year.
What we’re mostly interested in is, obviously, improvements related to backups and restores. Here is a shortlist with improvements.
At the time this article was written only SQL Server 2014 CTP2 was available, so information related to this subject is limited to only what was known from the perspective of the CTP2 edition.
This post is a continuation of a previous post where we explained how to do a maintenance plan that will take care of creating backups via a schedule.
Now that we have a schedule that consistently creates backups, we might want to create a backup cleanup schedule to remove older backup files.