Tags: backup, bakfile, cluster, database, disk, double, file, iintentionally, microsoft, mysql, oracle, overnight, range, server, size, sql

Why would backup file size double overnight?

On Database » Microsoft SQL Server

2,028 words with 2 Comments; publish: Sat, 17 May 2008 10:12:00 GMT; (25078.13, « »)

SQL 2005 cluster, one database, full backup to disk every night. .BAK

file size had been in the 10 GB range, until one night when I

intentionally failed the cluster over and back (installing security

updates). Ever since then, the size of the .BAK file has doubled in

size.

If I check the size of the actual database, it is still about 7 GB in

size. Any ideas why the backup file grew so large?

All Comments

Leave a comment...

  • 2 Comments
    • <stephendkay.sqlserver.todaysummary.com.gmail.com> wrote in message

      news:1173293884.960071.224960.sqlserver.todaysummary.com.8g2000cwh.googlegroups.com...

      > SQL 2005 cluster, one database, full backup to disk every night. .BAK

      > file size had been in the 10 GB range, until one night when I

      > intentionally failed the cluster over and back (installing security

      > updates). Ever since then, the size of the .BAK file has doubled in

      > size.

      > If I check the size of the actual database, it is still about 7 GB in

      > size. Any ideas why the backup file grew so large?

      >

      Database get set to SIMPLE RECOVERY?

      Or a DBCC DBREINDEX or something done?

      Greg Moore

      SQL Server DBA Consulting

      sql (at) greenms.com http://www.greenms.com

      #1; Sat, 17 May 2008 10:13:00 GMT
    • On Mar 7, 2:21 pm, "Greg D. Moore \(Strider\)"

      <mooregr_deletet....sqlserver.todaysummary.com.greenms.com> wrote:

      > Database get set to SIMPLE RECOVERY?

      > Or a DBCC DBREINDEX or something done?

      > --

      > Greg Moore

      > SQL Server DBA Consulting

      > sql (at) greenms.com http://www.greenms.com

      Nope, recovery model is still set to full. No reindexing or anything

      done. Just rebooted. I'm going to test the restore of the larger

      file to make sure it's not corrupted in any way, but I'm still at a

      loss to understand how this could happen. Backup log shows nothing

      other than the fact that it took twice as long to complete.

      #2; Sat, 17 May 2008 10:14:00 GMT