| backup system has no restore procedure [message #65278] |
Tue, 19 May 2009 15:11  |
dj-m  Messages: 88 Registered: May 2009 |
Valuable Member |
|
|
I find the backup system to be nearly pointless. It has no restore procedure.
There is the "go to browse backup, find what you want, click copy, go to the place you want to restore the files, click paste" option, but this is rediculous.
Doing this procedure creates a tar file which requires 2 times more disk space then what you are restoring due to the way it archives the files, copies the archives, then restores. This makes it not always possible to restore a full VM.
The other problem, is that the backup system doesn't maintain any type of permissions when restoring (ie; copy/paste'ing)- so anything you restore will have messed up permissions- again impossible to restore a full VM. Any custom files restored have to be manually permissioned correctly before they will work like they should.
I'm posting this as a bug, because what good is the backup system when there is no proper restore procedure?
I think the following should happen;
1. when restoring- it should use rsync or some other method that will prevent having to create a full archive of whatever you are restoring.
2. permissions should be correctly restored to their original value. I see the backup system keeps the files with their respective owner ID so this really shouldn't be a problem using rsync.
3. the process of restoring should not require a "copy" in the "browse backup" area, then a whole new navigation to "file manager" find the location then "paste". Any file you're going to restore -presumably- will go to the same place it was when it was backed up, so I would have expected to see a simple "restore" button in the browse backup area to put the file on the server where it was backed up from.
Cheers
[Updated on: Tue, 19 May 2009 15:12] Report message to a moderator
|
|
|
|
| Re: backup system has no restore procedure [message #68337 is a reply to message #68076] |
Thu, 18 June 2009 18:06   |
dj-m  Messages: 88 Registered: May 2009 |
Valuable Member |
|
|
| Marie wrote on Sat, 13 June 2009 14:14 | Not sure what your problem is ? I have been restoring full vps with no problem at all with rsync. You've got to use command line, no big deal...
|
I don't have any problems at all, but thanks for checking. Concern for our peers on space ship earth is a rare find these days.
hypervm has a problem that it has no restore procedure, as was mentioned.
Find the procedure;
lxlabs.com/software/hypervm/backup/
As well as many other problems like you mention here;
forum.lxlabs.com/index.php?t=msg&th=11624
Of course the command line is no big deal, but then a person could argue- what good is the backup system built in to hypervm if;
1. it doesn't work right
2. it fails if an upgrade takes place during the process
3. it has no restore procedure
4. the restore procedure that it DOES have is no good unless you have a partition available 2.5x the size of whatever you are trying to restore
5. the restore procedure that it DOES have does not restore permissions, and makes a tar archive needlessly prior to copying the files
You might as well just make your own backup and restore procedure or modify the existing one to make it work right which it looks like you and I have both wound up doing. Clearly there is something wrong if you and I are both modifying things at the command line to make the gui accessible functions work right.
[Updated on: Thu, 18 June 2009 18:14] Report message to a moderator
|
|
|
|
| Re: backup system has no restore procedure [message #68354 is a reply to message #65278] |
Fri, 19 June 2009 01:01  |
dj-m  Messages: 88 Registered: May 2009 |
Valuable Member |
|
|
You know what this had me wondering earlier, is what happens with the backup system where users can make manual backups on demand? I know it makes a big tar file, but what about the restore procedure from it? Does it restore the archive properly, permissions and all?
Its a difficult one to test due to the size of vm's.
Oh well, in a holding pattern for staff updates to see if we'll even be using this software much longer and in what capacity.
Cheers
|
|
|