What do these backup options mean only backups?

Question

I am currently trying to back up a SQL Server 2008 R2 database that I developed for a project that is currently closed. I went through the backup procedure through SQL Management Studio when I noticed that it is possible to backup only the backup. I looked at him to understand what it was, but I did not fully understand the options that I received.

http://technet.microsoft.com/en-us/library/ms191495.aspx

I read the entry above, as well as other entries, and I continue to see the phrase "regardless of the sequence of regular SQL Server backups."

Can anyone clarify what this statement means or more about backing up only backups in general? I'm not sure if this is the backup I have to do in this case? (My first reaction is no)

Answer 1

Usually, when you take a backup, it starts (or continues, depending on the type of backup you use), which is called a log chain. Say you need a copy of your database, and for some reason you cannot use your planned backups for this purpose. Go through a script where you are not using copy_only backup

• Normal full backup
• Differential Backup Bundle
• Another full backup (to make your database copy)
• More differential backups
• Delete the backup from step 3 (you know ... to save space)
• An accident in your real database that requires recovery from a backup.

In this case, you can restore only the last differential backup made in step 2, because the differential backups made in step 4 depend on the full backup from step 3. Now, if the backup in step 3 was a copy_only backup, You will be fine because you are not restoring the log chain (which means that the differential backup in step 4 depends on the full backup from step 1.

Answer 2

This is a complete database dump, where you intend to take this dump and load it into some other SQL sql instance. for example This is a great way to make a full copy of the database without having to remove db, detach db, copy .mdf files, reattach, etc.

Naturally, since you are not using this “backup” as an actual backup, you do not want it to interfere with your normal backup schedules, and therefore, copy-only functions. This is a full backup, but the backup schedule will not reset, so your regular next incremental / snapshot will work as usual.

This mechanism is necessary because the built-in hotcopy / migration tools in MSSMS are mostly useless and cannot process their own databases in many cases.

Answer 3

If you back up the archive and continue to back up to the server, this is not a concern, then it doesn’t matter if you use it or not. It will be restored as a database anyway.