americaneldercare
asked on
Symantec Backup Exec SQL backup 3.5 times larger
I am running Symantec Backup Exec 12d on Server 2003. It is backing up two SQL 2000 instances running on Server 2003 x64.
The first one appears to work correctly, the backup and database sizes are nearly identical. However, the other database is backing up 3.5x MORE data than actually in the database(s). The final backup is showing at nearly 230GB while the sum of the databases is only about 65GB.
This is eating through my tapes rather quickly as well as causing this backup to run significantly longer then expected.
The first one appears to work correctly, the backup and database sizes are nearly identical. However, the other database is backing up 3.5x MORE data than actually in the database(s). The final backup is showing at nearly 230GB while the sum of the databases is only about 65GB.
This is eating through my tapes rather quickly as well as causing this backup to run significantly longer then expected.
is it possible that you are using the option "Append to the existing backup set"?
ASKER
We are using that option, however I am under the impression that is allowing it to append to the existing tape - not increase the actual size of the current backup it is recording.
To make sure we are speaking of the same thing, I am referring to the actual "byte count" of the individual backup, not the total GB consumed on the backup media. The "Byte count" on the differential based backup is showing as 266GB - when I check the details, it is indicating that ~228GB of that is coming from a database which only totals 65GB, another 37GB is coming from a database totaling ~40GB, and the remainder from a few folder (these don't change often so under a differential only a few 100 MB's are written).
A full backup of the same system, using the same selections, and also tagged as 'append to media, overwrite if not appendable media is available' totals only 104GB.
To make sure we are speaking of the same thing, I am referring to the actual "byte count" of the individual backup, not the total GB consumed on the backup media. The "Byte count" on the differential based backup is showing as 266GB - when I check the details, it is indicating that ~228GB of that is coming from a database which only totals 65GB, another 37GB is coming from a database totaling ~40GB, and the remainder from a few folder (these don't change often so under a differential only a few 100 MB's are written).
A full backup of the same system, using the same selections, and also tagged as 'append to media, overwrite if not appendable media is available' totals only 104GB.
ASKER
I am testing putting this backup job on hold and creating a new one as a copy off of the "Full" which, as indicated, appears to be functioning correctly.
are you dropping to the same tape in both example?
ASKER
No, we have a tape library. Certain tapes are designated for Full and others Differential, and the individual jobs are designated to use their appropriate tape sets.
Sounds like a problem with the selection list, you might have the physical file as well as the database that lives in that file selected for example. Text view rather than the graphical view readily shows the difference if there is one.
ASKER
the "new" job created by copying the Full is working correctly. Compared the text view of selections as well as the 'View Summary' between the original and current Differential backups - only difference currently is the old one had "Advanced Open File" on. enabled for the new one, will see if the next differential (monday) runs any different.
otherwise, it appears that *something* is just corrupt with the original backup.
otherwise, it appears that *something* is just corrupt with the original backup.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
not sure why the Advanced Open File option causes this issue, but not using it resolves the problem.