System Restore

ElXemenes

New member
Joined
Apr 10, 2004
Messages
2
Location
USA
There needs to be a way you can fully restore the system, much like you can with user accounts. I did a system backup thinking that I could just as easily restore it but it turned out that I could not, and I'm finding it rather difficult to get everything back in order. Please come up with a System Restore.

Thanks

El
 
I've considered for a while that we should write a complete backup/restore system, perhaps also based on sysbk (we were using sysbk before it was part of DirectAdmin).

I know we could write one that would duplicate a server on a clean DA installation (one with no users/resellers/admins already installed on it), using the same IP#s.

I believe we could also write one with an IP substitution table.

What I'm not to sure of is how to handle overlapping resellers and/or users, so if we write it, it will require a clean system for the restore.

However if we were to do that we'd spend a lot of time and we'd definitely charge for it.

And we know what would happen then: almost everyone would tell us it should be free and that it should have been written by DA.

So we haven't been willing to invest the resources.

Jeff
 
options

Well one has the following option:

Write the application yourself, put the backup client as a plugin for DA, and when the user requires a restore, only then are they required to purchase a license.

That way, not everyone will need the restore client, and when the day comes that they do, they'll pay the fee for the restore option.
 
I don't know; if someone gave away a free backup client and charged me for the restore half when I needed it, I would call it extortion.

Jeff
 
nah

Nah, as long as it stated it in the plugin.

I.e. the person has the data backed up and can manually restore, however when the need came along and they needed a quick restore then they could pay for the license.

Think of it this way, I run SCSI raid 1 so dont beleive i'd need it any time soon, plus the hardware has been running 3 years with no issues. I dont need the resotre function yet so dont want to spend money on it, but if i had the client doing the backup all the time and if the time came that I did need to do a restore, i'd pay for the software.
 
In other words I should write it now so in the unlikely event you may need it in the future I can make a small portion of what it's worth for the time I put into it?

Wimpy said "I'll pay you tomorrow for a hamburger today". You're saying "I may or may not pay you in three years for work you do today."

I really don't want to be on either side of that transaction.

Perhaps you'd do it for us, since it's a model you clearly believe in?

Jeff
 
Jeff I would maybe pay depending on the price, but the thing that will put people off is that it isnt something they will be using a lot, maybe will never use it, it is something useful if perhaps the server dies and needs reformatting or doing a location move.

People will rightly think this should be already in DA, if you write a backup feature then the restore featore should be with it, are DA even planning on making the restore feature or are they satisfied they have a half finished feature.

I mean right now we backup all our users using the reseller backup feature but dont backup the resellers. We seem to have 3 options for backing up the resellers and their users.

1 - Use the system backup feature to backup all home dir's etc. But I think if backing up user's this way they are not compatible with the reseller restore feature, and its awlkrawd to specifically choose reseller's and their users with this.

2 - Login as the reseller's and run backup, this I assume would use their traffic quota.

3 - Do it manually either in the shell yourself or writing own script. This should defenitly not be needed as I expect the control panel to do it.
 
Depending on the cost I would not mind paying for it.
It's a core function which can be of great importance, I'd rather pay a certain fee and have things going smooth in the event of a crash instead of losing customers and having a really stressful period.
 
Chrysalis said:
Jeff I would maybe pay depending on the price, but the thing that will put people off is that it isnt something they will be using a lot, maybe will never use it, it is something useful if perhaps the server dies and needs reformatting or doing a location move.
I suppose you don't buy car insurance until after you wreck your car either, then.

Or flood insurance which perhaps millions of people didn't buy because they didn't think they needed it until New Orleans and lots of communities around it ended up under water.
People will rightly think this should be already in DA, if you write a backup feature then the restore featore should be with it,
I believe that at some point someone from DA posted that the reason they didn't write a restore was because how you restored could be very different depending on the purpose of your restore, whether you were restoring to an empty machine or a machine already in use, to the same OS distribution or another, etc. If they didn't write it, then they probably should have, or maybe I already did.

Because it's true. If we're to write the system it will be to restore a whole backup from one system to another, empty one, running the same OS distribution on the same architecture.

Why? because that's the only way to know in advance how to do the restore.

And you need to know what to do in order to script it.

Of course we'll also allow you to selectively unpack the backup if you just need a file or two.
are DA even planning on making the restore feature or are they satisfied they have a half finished feature.
I don't consider it a half finished feature, perhaps because I've been administering unix systems for long before Linux was even written. And I've never known a sysadmin who scripted a restore of content. We script a backup of enough files so we can do a restore of content. Or we script a backup of the entire server (a tarball of "/"). (In fact, that's why tar was written; it's a contraction of "tape archive".

But to find out what DA's plans are, the best thing would be to ask them.

I'll certainly ask them before beginning work on our own system; I wouldn't want to invest time in something that we'd neither need nor be able to sell.
I mean right now we backup all our users using the reseller backup feature but dont backup the resellers. We seem to have 3 options for backing up the resellers and their users.

1 - Use the system backup feature to backup all home dir's etc. But I think if backing up user's this way they are not compatible with the reseller restore feature, and its awlkrawd to specifically choose reseller's and their users with this.
I don't know if this would give you all you need.
2 - Login as the reseller's and run backup, this I assume would use their traffic quota.
When you're running your reseller backup you can checkmark all the users, including the reseller backup. Then when you restore you should:

a) create the reseller as a reseller on the new server

b) restore the reseller user first in one run

c) then restore the rest of the users.

This should work. At the moment there are some problems under certain circumstances. For example, if a user has ten mailboxes and then the reseller changes his package so he can only have five. We've also had problems with some suspended users, but we're not sure why. We've asked DA staff to look into these problems.
3 - Do it manually either in the shell yourself or writing own script. This should defenitly not be needed as I expect the control panel to do it.
Because we were previously a Plesk Gold Partner, we end up using Plesk as our reference example.

Their backup system creates a monolithic file of proprietary design; back when there was a 2 gig file limitation they didn't even handle that; they just explained how you could use linux commands to split the file, and to put it back together while restoring it. There was no way to restore individual files without restoring the entire system, and there was no way to run the restore unless you had another system running a licensed copy of the same Plesk version on the same OS. And Plesk licenses do not come cheap.

So we found the three methods included in DA to be a wonderful feature, and though we've got our complaints, we've learned to use them.

We've recently published the settings for system backup which should enable you to restore your system. That's as far as we're going to go for the community unless we decide to write a package to sell.

Our own clients know to what extents we go to get them up and running as quickly as possible should they have a problem.

Jeff
 
I agree with your points about system files such as backing up /etc and other system dirs, but there needs to be a better way to backup resellers and their packages.

Perhaps a new backup/restore feature is needed in the admin level that works like the reseller level except it backs up all accounts in the servers including the resellers. It should also backup their packages, when I moved server's I had to manually restore a few things like the packages and ticket's which should be in the scope of what DA can achieve.
 
The most efficient way to backup a system is with sysbk.

The most efficient way to restore may very well be sysbk.

When I do a sysbk restore from scratch it takes me less than four hours.

There were so many "issues" the one time I tried a system restore from the reseller backups that it took close to ten times four hours.

Fortunately the old server was still running.

I'm willing to write the restore system. If people are willing to buy it.

If not, then ask DA.

Which I guess you've done by posting under Feedback & Feature Requests.

So this thread can be locked, then?

:)

Jeff
 
I had no problems with reseller restore, it worked almost seamlessly, a couple of accounts had permission problems and I had to manually restore reseller packages and tickets but otherwise was fine.
 
Jeff,

If you can give us an approximate price of what we can expect it to cost then we can decide whether or not its worth coding it.

I'm in favor for such a system.
 
You've made a reasonable request. Unfortunately I have no idea what it might sell for; obviously we'd want to at least recover our costs with whatever sales we can make, and even make a small profit :).

4PSA sells their Total Backup package for the Plesk control panel for $129 for unlimited users/domains.

Any suggestions as to what price would make it interesting?

Jeff
 
does plesk already include a backup feature by default or they just done an entire new backup/restore feature?
 
Any update on the backup restore features?

Am I right in reading that backups often fail to restore with DA?

Is there a way to backup each individual user data (not doing it one at a time) and restore it individually or restore all at once?

If not then this is a feature DA needs!
 
I think $129 is pretty reasonable. As of course, you need to eat as well :)

Backups are one of the most important things around in my opinion. A solution taking care of that is another thing not to worry about.
 
Chrysalis said:
does plesk already include a backup feature by default or they just done an entire new backup/restore feature?
Please note that it's been a while since I studied the Plesk backup, and it's possible it's not exactly like this anymore:

Plesk includes a backup program. It's not available from the interface but must be run through a cron job.

If the created file is going to be over 2GB and if either the source or destination OS can't handle files over 2GB you have to filter the output through Unix commands to break and later restore the file as it's created/read.

If the file is larger than the space still available on the drive you have to use complex command line options to create the file on another server as you run the backup.

Once you're done you've got a single monolithic file which you have to restore to a running new plesk server (no users or resellers) of the same license level.

All in all, sysbk as included in DA is much better.

And that's what's left an opening that the 4PSA company filled with their own backup solution.

Our solution, if we do it, will be build on sysbk, because sysbk is quite good as far as it goes.

But that's just my opinon :) .

Jeff
 
Back
Top