Using Windows XP Pro Backup
I've been trying to set up a backup that will be scheduled to run at night. It's of one folder going into one folder ... so that part's simple enough.
BUT, when I've set up the backup task I set it up to do an Incremental backup so that it will:
1) backup everything the first time
2) only back up new files thereafter
But, what it does instead is that it backs up the entire folder each time and I get this HUGE backup space growing daily.
How do I get what I want?
BUT, when I've set up the backup task I set it up to do an Incremental backup so that it will:
1) backup everything the first time
2) only back up new files thereafter
But, what it does instead is that it backs up the entire folder each time and I get this HUGE backup space growing daily.
How do I get what I want?
nobus
use syncback - fast and good : www.2brightsparks.com/SyncBack
ASKER
I meant *with* Windows XP Pro Backup .... Surely it must be possible.
You need 2 jobs. 1 job to do the First Full Backup. 2nd job to do the Incremental backups.
This will guarantee what you want to happen.
1. do a Manual Full - Normal backup (to ensure you really have a Full backup to to also clear any file archive attribute). By manual, I mean just make a backup job and run it.
For the Incremental backup, at the Scheduled Jobs tab, click Add Job, select your source folder and destination file, Choose Incremental method and also the Append this backup... mode
That should be it. You will have a Full - normal backup that you made manually. Lets call that file: FullBackup.bkp
And you should have the Incremental(s) backup in some file called (for example): DailyIncrBackup.bkp
The incremental backup file will contain individual backups for each time it runs (they will append/add to the file).
This will guarantee what you want to happen.
1. do a Manual Full - Normal backup (to ensure you really have a Full backup to to also clear any file archive attribute). By manual, I mean just make a backup job and run it.
For the Incremental backup, at the Scheduled Jobs tab, click Add Job, select your source folder and destination file, Choose Incremental method and also the Append this backup... mode
That should be it. You will have a Full - normal backup that you made manually. Lets call that file: FullBackup.bkp
And you should have the Incremental(s) backup in some file called (for example): DailyIncrBackup.bkp
The incremental backup file will contain individual backups for each time it runs (they will append/add to the file).
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
dew_associates: Thank you for the links. At least now I have better insight into what to expect.
From what I've read, it appears that the Windows backup won't do what I want. Here are the spec's:
1) Do a full (Normal) backup the first time. (Any backup can do that).
2) Do an Incremental backup thereafter.
3) Don't use more space than necessary for the entire set of backups.
4) Avoid having to rummage around to do a restore.
5) Save files in native format.
With Windows backup it appears that 3 and 4 are mutually exclusive.
It appears that Incremental backup will force dealing with 4.
With Windows backup it appears that 5 isn't possible. Is that right or did I miss a setting to "not compress" or ..... ?
chakko: So, I guess one might do a single Normal backup and then schedule an Incremental backup? Is that what you mean?
From what I've read, it appears that the Windows backup won't do what I want. Here are the spec's:
1) Do a full (Normal) backup the first time. (Any backup can do that).
2) Do an Incremental backup thereafter.
3) Don't use more space than necessary for the entire set of backups.
4) Avoid having to rummage around to do a restore.
5) Save files in native format.
With Windows backup it appears that 3 and 4 are mutually exclusive.
It appears that Incremental backup will force dealing with 4.
With Windows backup it appears that 5 isn't possible. Is that right or did I miss a setting to "not compress" or ..... ?
chakko: So, I guess one might do a single Normal backup and then schedule an Incremental backup? Is that what you mean?
I think maybe you have missed something in the explanation of the backup settings.
Indeed, while you may have to do the first full backup by creating the settings and running the backup utility, you then just have to set up the backup job and then set up the scheduler to run that job.
Thus, your #1 and #2 are covered.
Youre #3 cannot be done, as adding incremental backups will cause the backup space to grom incrementally.
#4 is covered by scheduling the backup as explained.
#5 - I'm not sure why you seem to think that compression changes the native format, as it does not.
Indeed, while you may have to do the first full backup by creating the settings and running the backup utility, you then just have to set up the backup job and then set up the scheduler to run that job.
Thus, your #1 and #2 are covered.
Youre #3 cannot be done, as adding incremental backups will cause the backup space to grom incrementally.
#4 is covered by scheduling the backup as explained.
#5 - I'm not sure why you seem to think that compression changes the native format, as it does not.
ASKER
dew_associates:
The #3 objective is to not use more space than *necessary*. It is necessary to add new files - so that kind of incrementalism is fine. But creating multiple copies of the same file is what I'm trying to avoid by this. And, this is what the Windows backup seemed to be doing in Incremental mode when I tried it! Specifically I was backing up a 29GB folder and was getting a single daily backup file that grew 29GB per day while the actual data added each day was way less than that.
The #4 objective is not met according to the Microsoft paper on the subject. It says clearly that restoration is going to be a chore. So, either that's correct or it isn't. I've never done it so I'm asking.
A compressed format is definitely not native. If I see .zip (or whatever) then I don't see .doc and .xls, etc. I need an *app* to make the underlying files visiable and accessible. Now, I grant that a Windows backup or a .zip would likely be so readily available that this isn't likely a huge issue. But I still prefer native format. Compression is only useful when it's really needed and can be a nuisance when it's not needed. An example of why this objective:
Lets say we use Backup MY PC. The resulting backup (as I recall) is in a proprietary format. Let's say the backed up computer dies. Backup My PC dies with it. Now we have to get an installation of Backup My PC (which may no longer exist or the file format may no longer exist, etc. etc.). I want to avoid that kind of step. So *native* format please. That said, I guess I would back off if the format were quite universal like .zip or .7z or .....
The #3 objective is to not use more space than *necessary*. It is necessary to add new files - so that kind of incrementalism is fine. But creating multiple copies of the same file is what I'm trying to avoid by this. And, this is what the Windows backup seemed to be doing in Incremental mode when I tried it! Specifically I was backing up a 29GB folder and was getting a single daily backup file that grew 29GB per day while the actual data added each day was way less than that.
The #4 objective is not met according to the Microsoft paper on the subject. It says clearly that restoration is going to be a chore. So, either that's correct or it isn't. I've never done it so I'm asking.
A compressed format is definitely not native. If I see .zip (or whatever) then I don't see .doc and .xls, etc. I need an *app* to make the underlying files visiable and accessible. Now, I grant that a Windows backup or a .zip would likely be so readily available that this isn't likely a huge issue. But I still prefer native format. Compression is only useful when it's really needed and can be a nuisance when it's not needed. An example of why this objective:
Lets say we use Backup MY PC. The resulting backup (as I recall) is in a proprietary format. Let's say the backed up computer dies. Backup My PC dies with it. Now we have to get an installation of Backup My PC (which may no longer exist or the file format may no longer exist, etc. etc.). I want to avoid that kind of step. So *native* format please. That said, I guess I would back off if the format were quite universal like .zip or .7z or .....
The first issue you mention is a settings issue. You need to be particularly careful in your selections so that only files that have change since the last increment are included.
Indeed, making a full backup followed by incremental backups will create a chore should you need to restore your system. This was your original request, although not a recommended procedure today given the large number of inexpensive USB backup drives.
In all honesty the best way to handle the issue would be with two inexpensive drives and do full backups and alternate the drives, verifying the backups as completed? Why? If one backup is corrupted for any reason, you at least have the previous to work with and at best loose only one days work.
Last but not least, while the backup compression does append a form of zip to the file, it remains readable within the Windows environment. Backup My PC is not what I would use.
In you are working with critical documents, and/or your time is important to you, I would follow another approach entirely. I would run a pair of drives in a basic RAID 1 configuration and then schedule regular backups as a safeguard. The mirrored drives will forestall most major events other than maybe total corruption via a virus etc.
Indeed, making a full backup followed by incremental backups will create a chore should you need to restore your system. This was your original request, although not a recommended procedure today given the large number of inexpensive USB backup drives.
In all honesty the best way to handle the issue would be with two inexpensive drives and do full backups and alternate the drives, verifying the backups as completed? Why? If one backup is corrupted for any reason, you at least have the previous to work with and at best loose only one days work.
Last but not least, while the backup compression does append a form of zip to the file, it remains readable within the Windows environment. Backup My PC is not what I would use.
In you are working with critical documents, and/or your time is important to you, I would follow another approach entirely. I would run a pair of drives in a basic RAID 1 configuration and then schedule regular backups as a safeguard. The mirrored drives will forestall most major events other than maybe total corruption via a virus etc.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
To schedule create a scheduled jod that runs similar command
ASKER
Thanks all