Archived from groups: microsoft.public.win2000.general (More info?)
I have the Win 2000 backup utility configured for automatic backups to an
external hard drive dedicated to that purpose. However after 2-3 backups I
get a "disk full" error even though I am using only 8gigs of a 160 gig
drive. Erasing the backup file temporarily solves the problem but again
after several backups I get the same message. Any ideas?
Archived from groups: microsoft.public.win2000.general (More info?)
Thanks. I do think it is the backup hard drive since the same backup
procedure done manually when the drive is cleared of prior backups goes
fine. I am now wondering whether I am running into the fact that the backup
drive is FAT 32 with an inherent backup size limitation of 4G (based on
further rooting around in Microsoft knowledge documents). It seems that
whenever a single backup operation results in a final backup file size of
greater than 4 G things fall apart. If this is true am I stuck with
splitting the backup into smaller bits?
"abc" <abd@nd.sss> wrote in message
news:jQE7e.2722$XF3.563@twister.nyroc.rr.com...
> I have the Win 2000 backup utility configured for automatic backups to an
> external hard drive dedicated to that purpose. However after 2-3 backups I
> get a "disk full" error even though I am using only 8gigs of a 160 gig
> drive. Erasing the backup file temporarily solves the problem but again
> after several backups I get the same message. Any ideas?
>
>
>
Archived from groups: microsoft.public.win2000.general (More info?)
What exactly are you wishing to back up? is it merely data, or is it a sys
backup. If sys backup ntbackup is not really designed for this.
"abc" <abd@nd.sss> wrote in message
news:GbP7e.2753$XF3.2607@twister.nyroc.rr.com...
> Thanks. I do think it is the backup hard drive since the same backup
> procedure done manually when the drive is cleared of prior backups goes
> fine. I am now wondering whether I am running into the fact that the
backup
> drive is FAT 32 with an inherent backup size limitation of 4G (based on
> further rooting around in Microsoft knowledge documents). It seems that
> whenever a single backup operation results in a final backup file size of
> greater than 4 G things fall apart. If this is true am I stuck with
> splitting the backup into smaller bits?
> "abc" <abd@nd.sss> wrote in message
> news:jQE7e.2722$XF3.563@twister.nyroc.rr.com...
> > I have the Win 2000 backup utility configured for automatic backups to
an
> > external hard drive dedicated to that purpose. However after 2-3 backups
I
> > get a "disk full" error even though I am using only 8gigs of a 160 gig
> > drive. Erasing the backup file temporarily solves the problem but again
> > after several backups I get the same message. Any ideas?
> >
> >
> >
>
>
Archived from groups: microsoft.public.win2000.general (More info?)
Just data - text, graphic files,etc. Not sys.
"DL" <dl@spoofmail> wrote in message
news:%23sTKRigQFHA.3888@TK2MSFTNGP10.phx.gbl...
> What exactly are you wishing to back up? is it merely data, or is it a sys
> backup. If sys backup ntbackup is not really designed for this.
>
> "abc" <abd@nd.sss> wrote in message
> news:GbP7e.2753$XF3.2607@twister.nyroc.rr.com...
> > Thanks. I do think it is the backup hard drive since the same backup
> > procedure done manually when the drive is cleared of prior backups goes
> > fine. I am now wondering whether I am running into the fact that the
> backup
> > drive is FAT 32 with an inherent backup size limitation of 4G (based on
> > further rooting around in Microsoft knowledge documents). It seems that
> > whenever a single backup operation results in a final backup file size
of
> > greater than 4 G things fall apart. If this is true am I stuck with
> > splitting the backup into smaller bits?
> > "abc" <abd@nd.sss> wrote in message
> > news:jQE7e.2722$XF3.563@twister.nyroc.rr.com...
> > > I have the Win 2000 backup utility configured for automatic backups to
> an
> > > external hard drive dedicated to that purpose. However after 2-3
backups
> I
> > > get a "disk full" error even though I am using only 8gigs of a 160 gig
> > > drive. Erasing the backup file temporarily solves the problem but
again
> > > after several backups I get the same message. Any ideas?
> > >
> > >
> > >
> >
> >
>
>
Archived from groups: microsoft.public.win2000.general (More info?)
Yes, there is a limitation on size with ntbackup.
There are many low cost, and some free, backup apps that do not have this
limitation, or can automatically split
"abc" <abd@nd.sss> wrote in message
newsEX7e.2913$XF3.2549@twister.nyroc.rr.com...
> Just data - text, graphic files,etc. Not sys.
>
>
> "DL" <dl@spoofmail> wrote in message
> news:%23sTKRigQFHA.3888@TK2MSFTNGP10.phx.gbl...
> > What exactly are you wishing to back up? is it merely data, or is it a
sys
> > backup. If sys backup ntbackup is not really designed for this.
> >
> > "abc" <abd@nd.sss> wrote in message
> > news:GbP7e.2753$XF3.2607@twister.nyroc.rr.com...
> > > Thanks. I do think it is the backup hard drive since the same backup
> > > procedure done manually when the drive is cleared of prior backups
goes
> > > fine. I am now wondering whether I am running into the fact that the
> > backup
> > > drive is FAT 32 with an inherent backup size limitation of 4G (based
on
> > > further rooting around in Microsoft knowledge documents). It seems
that
> > > whenever a single backup operation results in a final backup file size
> of
> > > greater than 4 G things fall apart. If this is true am I stuck with
> > > splitting the backup into smaller bits?
> > > "abc" <abd@nd.sss> wrote in message
> > > news:jQE7e.2722$XF3.563@twister.nyroc.rr.com...
> > > > I have the Win 2000 backup utility configured for automatic backups
to
> > an
> > > > external hard drive dedicated to that purpose. However after 2-3
> backups
> > I
> > > > get a "disk full" error even though I am using only 8gigs of a 160
gig
> > > > drive. Erasing the backup file temporarily solves the problem but
> again
> > > > after several backups I get the same message. Any ideas?
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.