Backup KB more than twice physical data

[MOHAMED_PATEL]

Hi all,

Just completed an upgrade of NB 6.0 MP6 to NB6.5.3 for Windows 2003 Ent. Had a bit of a hiccup but was graciously sorted out immediately by Symantec.
The issue I am encountering is the amount of data that is being backed up from the file-server which is the 1.9TB of physical SAN capacity but the actual physial data is 780GB.
I cannot understand how this amount of data has been backed up when the physical data is nowhere near this capacity. It should be noted that the job did retry 6 times, and on every count was a different amount of data which does not equat to the actual data amount.
The configuration was as follows,
Client still on NB6.0 MP6
No multiplexing
No Multiple streams
Disk Backup
Full Backup
Windows NT policy type - not Flash-backup

Any thoughts...

[quebek]

Hello
Check for junction point on that drive or any NFS mounted under this drive.
no other ideas for now.

[Marianne]

I'd like to see result of "ALL_LOCAL_DRIVES" with Allow Multiple Data Streams.
That will show you size backed up from each drive letter.
Also ensure you have bpbkar log on client.

[MOHAMED_PATEL]

Only a specific drive was backed up and not "ALL_LOCAL_DRIVES"....

One more thing to note, I had found a short-cut to the entire drive letter on this specific drive -
Should this make a difference - Windows not Unix viz 'cross mount points'

Checkpoint was also selected - every 15 Min

[Yasuhisa_Ishika]

Are there any folder with compress attribute on?

[MOHAMED_PATEL]

Compression is not enabled on NB or files/dirs.

currently restoring the backed up data - waiting to check how much gets restored...

[Marianne]

Please share output of 'bpimagelist -client <client> -d <start_time> -e <end_time> -U'

[rj_nbu]

Hi

I saw this issue once. A customer reported that their actual data on the server was about 25 Gb, but backup size was 125 Gb !!!!
It was isolated to an issue with shadow copy components . UNder certain conditions, SCC would backup again and again.
Customer engaged MSFT for the issue, and the fixed it by installing VSS rollout patch 2

http://support.microsoft.com/kb/940349

This might not necessarily fix your issue, just sharing my thoughts. Have you opened a ticket with support?