A
AZShuttler
I have a NAS (Promise NS4300) which is used by several XP systems as a
backup device. The box runs a firmware version of Linux and presents
a SAMBA interface to Windows. A backup quit early this morning when
utilization reached 99.9%. Yet, the sum of all allocated space on the
Terabyte server was less than 20%. 800 GB appeared to be missing.
After much thrashing around today, I discovered almost all of the
missing space was in the .RECYCLER subfolder of the BACKUPS folder on
the NAS. It contained dozens of 6-12GB-sized old backups.
(I have read several places on the web that XP does not maintain a
backup folder on networked drives, but this information apparently is
incorrect WRT SAMBA drives.)
I really don't need an archive of dozens of old backups of massive
size, so am wondering how to prevent this. The deletes are done using
a batch file that consists of NET USE, DEL xxx, NET USE /DELETE.
XP has an option to limit the size of the recycle bin on an individual
drive basis. The main recycle bin is set at 10% for all drives. There
does not appear to be any support of this for networked drives. I
seem to be caught between a rock and a hard place. On the one hand,
XP appears to view these drives as its own when moving them to the
recycler folder, but OTOH, the recycle bin manager app refuses
ownership of the problem.
Does anyone kow of any way to A) stop recycling on a networked
"drive", or B) limit the size of the recycle bin for a networked
drive? (From the client side)
backup device. The box runs a firmware version of Linux and presents
a SAMBA interface to Windows. A backup quit early this morning when
utilization reached 99.9%. Yet, the sum of all allocated space on the
Terabyte server was less than 20%. 800 GB appeared to be missing.
After much thrashing around today, I discovered almost all of the
missing space was in the .RECYCLER subfolder of the BACKUPS folder on
the NAS. It contained dozens of 6-12GB-sized old backups.
(I have read several places on the web that XP does not maintain a
backup folder on networked drives, but this information apparently is
incorrect WRT SAMBA drives.)
I really don't need an archive of dozens of old backups of massive
size, so am wondering how to prevent this. The deletes are done using
a batch file that consists of NET USE, DEL xxx, NET USE /DELETE.
XP has an option to limit the size of the recycle bin on an individual
drive basis. The main recycle bin is set at 10% for all drives. There
does not appear to be any support of this for networked drives. I
seem to be caught between a rock and a hard place. On the one hand,
XP appears to view these drives as its own when moving them to the
recycler folder, but OTOH, the recycle bin manager app refuses
ownership of the problem.
Does anyone kow of any way to A) stop recycling on a networked
"drive", or B) limit the size of the recycle bin for a networked
drive? (From the client side)