A copy-only backup in SQL Server(any version like 2012 or 2008 or 2005) is taken in cases you do not want effect the sequence of conventional SQL Server backups.
Usually in using a normal Backup,the backup changes the database and affects how later backups are restored. However, occasionally, it is useful to take a backup for a special purpose without affecting the overall backup and restore procedures for the database. copy-only backups serve this purpose.
Note: The transaction log is never truncated after a copy-only backup.
The types of copy-only backups are as follows:
Copy-only full backups (all recovery models)
Copy-only log backups (full recovery model and bulk-logged recovery model only)
Note:A copy-only full backup cannot serve as a differential base or differential backup and does not affect the differential base.
Mainly if a normal backup is taken without using copy_only then it should kept safe until next full backup finishes since a normal backup taken breaks the T-log backup chain by deleting fished transactions(Transactions written to disk already) from the .LDF File.
Learn about SQL Server detecting logical consistency based issues and how to resolve them.
Learn about SQL Server error 1222 and how to resolve the lock request time out…
Discover the new features of Microsoft SQL Server 2022 and how they compare to previous…
SQL Server Error 1222 lock request time out period exceeded Lock request time out…
SQL Server Error : 427, Severity: 20. Could not load the definition for constraint ID…
SQL Server Error : 204, Severity: 20. Normalization error in node %ls.
This website uses cookies.