These are NDS objects.

We get exactly the same issue showing when ours gets backed up, even tho we
know for a fact that the size of the files is much smaller.

We put it down to a quirk in ADSM.

By the way, we do NOT trust the ADSM NDS backups as a restore-able backup.
All our NDS backups are done to a seperate tape for safety reasons (as in,
ADSM failing to restore NDS on more then one occassion claiming it didn't
have rights when it did).

Mike

> -----Original Message-----
> From: David Browne. [SMTP:dbrowne AT HUMANA DOT COM]
> Sent: ã àåâåñè 02 2000 22:26
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      NDS backups
> 
> My network guy was monitoring a backup and asked me if  the number that
> appears after the" Normal File-->"  is the size of the file being backed
> up. It appears all of these files are the same size and he is telling me
> they shouldn't be very large. Could TSM be using up space unnecessarily?
> This is a Netware 4.11 server with TSM 3.7.1 on it. Can someone give me
> some information?
> 
> Normal File-->         2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Lms6224
> [Sent]
> Normal File-->         2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Mjr3663
> [Sent]
> Normal File-->         2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Mmf2355
> [Sent]
> Normal File-->         2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Mmk7095
> [Sent]
> Normal File-->         2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=MWH4505
> [Sent]
> Normal File-->         2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Netman
> [Sent]
> Normal File-->         2,097,152
> .[Root].O=HUM.OU=Area42.OU=PIN.CN=NetShield_PI
> MKT1 [Sent]
> Normal File-->         2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=PINMKT1