NTbackup

R

RichGK

Perform a Normal backup on the first day (using overwrite) and then an
incremental every day (using append). This will be the smallest type
possible and also the fastest, but it will also be the longest to
restore (restore normal first then each incremental).

I don't think ntbackup will do this as it really goes against the
whole idea of a backup. Why would you want to have files overwritten?
This would render the backup useless in my opinion.

You'd be better off the make sure that the media you are using (disk
file, tape) has enough space on it for the backup. You can't know this
exactly beforehand (well you might) but you can make a good estimation
and use that.

If you have 200GB to store and you only have 150GB of storage space
then what you have to do is figure out what 50GB of the data you can
do without storing. Otherwise purchase another drive.
 
L

leew [MVP]

RichGK said:
On 14 Apr, 22:25, "John Smith" <[email protected]> wrote:

** snip **
I don't think ntbackup will do this as it really goes against the
whole idea of a backup. Why would you want to have files overwritten?
This would render the backup useless in my opinion.

You'd be better off the make sure that the media you are using (disk
file, tape) has enough space on it for the backup. You can't know this
exactly beforehand (well you might) but you can make a good estimation
and use that.

If you have 200GB to store and you only have 150GB of storage space
then what you have to do is figure out what 50GB of the data you can
do without storing. Otherwise purchase another drive.

Actually, if you setup a user account specifically for backups, apply a
quota to it, and then run the backups as that user, you should be able
to keep the backups from exceeding a certain size.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top