Question : SQL 2005 Standard Log Shipping - Backups

I have a 380Gb Database that is Log Shipping to a second server without any problems.

The Primary Server requires an update from our developers. (SQL Scripts, Schema etc...)  I am happy that if I do nothing the Log Shipping will continue and pass all changes to the secondary server.

If there is an issue with the Primary Server during the upgrade and I want to roll back, I really want to avoid taking a backup of the secondary server and restoring it as it will take hours...  Is there anyway I can take a backup of the Primary server without disrupting the transaction log sequence numbers?

I am fairly new to SQL Log Shipping so maybe I have missed something obvious.

Answer : SQL 2005 Standard Log Shipping - Backups

>> Is there anyway I can take a backup of the Primary server without disrupting the transaction log sequence numbers?

Use WITH COPY ONLY option in your Backup statement. A copy-only backup is created independently of your regularly scheduled, conventional backups. A copy-only backup does not affect your overall backup and restore procedures for the database.

BACKUP DATABASE ur_db_name
 TO DISK = 'C:\ur_db_name.bak'
   WITH FORMAT, COPY_ONLY;
GO

Above script would take a backup without breaking transaction log sequence