Re: need help managing volume size & Re: Using WMM

[timOleary]

On Nov 25, 3:38 pm, "Hot-text" <hot-t...@hotmail.com> wrote:
> One Time I Put a 1GB USB Flash Drive & map as X: and gave all the GBs  to VM
> You Know VM need memory too!!
> To help me with   moviemaker in  making videos..
> At Radio Shack today  you can get a  4GB USB Flash Drive for $9.99
> More VM may help
> ABC array <<<<Hmm this  a good ideal making a array I give you   10  :)  on
> that one!!!!!
>
> "timOleary" <timothy.w.ole...@gmail.com> wrote in message
>
> news:0a433f15-326e-4196...@o9g2000vbj.googlegroups.com...
>
> > XP pro
> > I use an array for automated daily backup,
> > I have set up three folders on the array A,B, C.
> > Problems:
> > The array stops accepting data after it reaches a certain level so
> > backups are not executed until I notice and take action.
> > I also wish to keep the size of each folder at a certain level.
> > Right now I am merging files across the array initially loading files
> > into the first folder (A) than moving to the next (B), then the last
> > (C), then purging from the last folder (C) using a program called
> > delinda which uses the files' creation date as the trigger for merging
> > and purging.
> > I want an app which uses volume size instead.Since due to
> > irregularities in the backup timeline (for example array overloads as
> > described), sometimes the folders will grow larger than the desired
> > level, and I have to go in manually and manage things.
>
> > The objective is to retain files until they become older than six
> > months, after which time I can dump them.
> > I also think gdelinda has a memory leak because the file sizes and
> > available storage numbers do not add up. I do not know how to test for
> > memory leaks, but as previously mentioned. an app which uses volume
> > size rather than creation date as the trigger.
> > I do not know how to write a script, which someone suggested is what I
> > need to do
> > TIA

thanks