COPY_ONLY backup and running transactions?

  • Netbackup is our backup solution and as a nightly backup, it works great.... but from time to time, i have to restore data into test och dev servers and then netbackup is too slow, its usually alot faster to just take a manual backup to disk, i do this with COPY_ONLY to not disrupt the backup chain kept within the "official" backups in Netbackup.

    During a normal backup, everything that gets written into the database during the backup process is included in the backup when the database backup is completed and the logfile is being backed up

    right ?

    how does it work with a COPY_ONLY backup ? since its not chaning the LSNs?

    My problem is that Netbackup starts at 21:00 and the data that i REALLY want to be included in the backup to the test systems arrive at 20:35 and the database takes about an hour to backup.... so i dont have enough time to start my manual backup after 20:35 for the test systems, that would interfere with the Netbackup jobs, and i cant push those later either =/

    If i start a manual backup at 20:00, and it completes before 21:00, am i sure to get the data that arrives in the database at 20:35 with COPY_ONLY?

    EDIT: the databases are all in simple recovery model.

    /J

  • COPY_ONLY backs up everything that the regular backup does. It just doesn't put a marker down in the database that a backup has been done (possibly interfering with differential backups). If the transaction completes during the backup process, yeah, you should have that data as part of the COPY_ONLY backup.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Grant Fritchey - Tuesday, September 5, 2017 7:08 AM

    COPY_ONLY backs up everything that the regular backup does. It just doesn't put a marker down in the database that a backup has been done (possibly interfering with differential backups). If the transaction completes during the backup process, yeah, you should have that data as part of the COPY_ONLY backup.

    Thank you, I suspected it would but wanted to confirm my thinking was the correct one.

  • jCoke - Tuesday, September 5, 2017 6:01 AM

    how does it work with a COPY_ONLY backup ? since its not chaning the LSNs? 

    Note: it's the Differential Base LSN that's not incremented by a copy_only backup.

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply