Forum Discussion

ruet's avatar
ruet
Level 3
9 years ago

Wildly inaccurate Size Reported for Backup Sets

Hello,

I've run into a problem since upgrading BUE from 2014 to 15. BUE is reporting wildly inaccurate backup set sizes for at least on backed up resource. The resource in question runs a full backup every six months with daily incremental backups in-between. The full-backups for the resource are 5-6TB in size and are reported as 7-32GB in size in the "Backup Sets" tab of the storage device details. When drilling down to the "Details" of the backup sets the backup sizes appear correct in the "Contents" tab but incorrect in the "Properties" tab. The backups were successful and restores against the backup sets have been tested. All of the test restores were well above the reported size of the backup set(s). I am running BUE v14.2.1180.1673. Any suggestions?

Sets_E.jpg

Details.JPG

Properties.JPG

 

 

15
Backup and Recovery
Backup Exec
Windows Server (2003-2008)
  • CraigV's avatar
    CraigV
    9 years ago

    OK then it must be cosmetic. Check the Known Issues section and if your issue is listed there, vote it up. But log a call in the meantime with Veritas.

    Thanks!

12 Replies

Sort By
Show More
  • pkh's avatar
    pkh
    Moderator
    9 years ago

    If you use compression in your job, then it could have an effect on the data that is stored.  For example, if you are compressing data which are already compressed, like zipped or movie files, pictures, etc, you might end up with more data than you have started with.

    ============================

    The resource in question runs a full backup every six months with daily incremental backups in-between

    It is not advisable to have such a long interval between full backups.  

    1) When you do a restore, the full backup plus ALL the incremental backups up till the point in time of the restore need to be restored and this can take a long time.

    2) If any of the incremental backups is corrupted, then the rest of the backup chain is useless.

    3) DLM will keep the entire backup chain until the next chain is ready and this will occupy a lot of disk space.

    It is better to run more frequent full backups, like once a week.