mistofeles
New Member
- Joined
- Feb 12, 2009
- Messages
- 58
- Thread Author
- #1
There should be a backup system built in to the Win7 !
The original Backup/Restore is a disaster:
- it is using aproprietary file format. Every version of MSDOS and Windows has had an incompatible file format.
- it does not know what to backup
We had some thinking:
Normally an user creates max 1 GB of data/day.
1. Two hard disks of similar size to every PC (let it be 1 TB here)
- the first is the work space and contains a 990GB partition (HD1.1) for the user and a 10 GB partition (HD1.2) for the system
- the second for the copy and has a 990GB partition (HD2.1) for RAID1 and a 10 GB partition (HD2.2) for a daily work copy, 'snapshot'. HD2 is closed with Administrator permissions.
2. The workspace HD1.1 is mirrored to the HD2.1
3. The daily changes are copied to HD2.2 daily to two heaps alternating. The heaps are cleaned every two weeks alternating.
4. every time a program is installed, the backup program indexes those file, which can be collected from the installation CD - those will not be backed up. All the changing files: conf files, ini files, registry and user data etc will be copied. The same goes with the OS itself. Updates, upgrades and programs, which can be downloaded from the network are not copied to backup.
The RAID1 takes care of the mechanical failures. The snapshots take care of the mistakes made by the user or viruses.
There should be some thinking about those daily backups. Very often changes build chains. Somehow the backup should handle the chains so that the restore could be done for at least 5 days backwards.
Of course there should be a PANIC -ikon which freeses all and everything so that the user can stop the automatic bacup-engine so that it doesn't delete the backup heap when she finds, that she got to restore something.
This kind of backup shold be a part of the OS.
There is very much free space for new ideas around this system. For example the automatisation of the daily heaps. A good algorithm is needed to decide, when the heap can be cleaned and what to clean.
All the backup has to be done as linear copy -no ZIP, TAR or other fancy file formats.
Of course the second HD costs $$$ but as we have seen, the users tend to buy CDs, DVDs, USB sticks and USB HDs to make copies of their data. So why not make it in the beginning and make it part of the daily life.
Comments ?
The original Backup/Restore is a disaster:
- it is using aproprietary file format. Every version of MSDOS and Windows has had an incompatible file format.
- it does not know what to backup
We had some thinking:
Normally an user creates max 1 GB of data/day.
1. Two hard disks of similar size to every PC (let it be 1 TB here)
- the first is the work space and contains a 990GB partition (HD1.1) for the user and a 10 GB partition (HD1.2) for the system
- the second for the copy and has a 990GB partition (HD2.1) for RAID1 and a 10 GB partition (HD2.2) for a daily work copy, 'snapshot'. HD2 is closed with Administrator permissions.
2. The workspace HD1.1 is mirrored to the HD2.1
3. The daily changes are copied to HD2.2 daily to two heaps alternating. The heaps are cleaned every two weeks alternating.
4. every time a program is installed, the backup program indexes those file, which can be collected from the installation CD - those will not be backed up. All the changing files: conf files, ini files, registry and user data etc will be copied. The same goes with the OS itself. Updates, upgrades and programs, which can be downloaded from the network are not copied to backup.
The RAID1 takes care of the mechanical failures. The snapshots take care of the mistakes made by the user or viruses.
There should be some thinking about those daily backups. Very often changes build chains. Somehow the backup should handle the chains so that the restore could be done for at least 5 days backwards.
Of course there should be a PANIC -ikon which freeses all and everything so that the user can stop the automatic bacup-engine so that it doesn't delete the backup heap when she finds, that she got to restore something.
This kind of backup shold be a part of the OS.
There is very much free space for new ideas around this system. For example the automatisation of the daily heaps. A good algorithm is needed to decide, when the heap can be cleaned and what to clean.
All the backup has to be done as linear copy -no ZIP, TAR or other fancy file formats.
Of course the second HD costs $$$ but as we have seen, the users tend to buy CDs, DVDs, USB sticks and USB HDs to make copies of their data. So why not make it in the beginning and make it part of the daily life.
Comments ?