Restoring Backup via DA fails!!

[xsxn]

Hello had to reinstall one of our boxes en now i am trying to restore a reseller from admin level. The restore is added to the queue but I do not recieve any ticket about a failure etc. I geus the file size is to big (over 40MB) so is it possible to restore the backup true ssh and where is this tool.

[Webcart]

Hello had to reinstall one of our boxes en now i am trying to restore a reseller from admin level. The restore is added to the queue but I do not recieve any ticket about a failure etc. I geus the file size is to big (over 40MB) so is it possible to restore the backup true ssh and where is this tool.

40MB is definitely not a big backup file. We routinely restore backups as big as few GBs :)

I notice that it's a little bit old thread for this kind of problem, but if you are still interested in troubleshooting this issue feel free to post back.

[floyd]

I recently restored a backup that was 24 GB. It took a few hours since it was on a busy server but it worked.

[nobaloney]

Backups and restores are intentionally done behind the scenes with message notification so they won't have a timeout issue. You can (and perhaps should) use tar to untar the backup so you can find the problem.

Jeff

[dynamicwebs]

definitiely broken. I've been trying to restore for 2 days (server change) and it just doesn't restore.

Is there an SSH command I can use to try to restore the sites?

[DirectAdmin Support]

The ssh restore would be the exact same as the DA restore.
Basically, you'd add your restore commands to the:
/usr/local/directadmin/data/task.queue file.

So, go into DA, issue the restore, and quickly check the task.queue to see if the restore command was added to task.queue file.

If things are working right, then the task.queue should be deleted when the minute turns over (at seconds :00)

Check the /var/log/directadmin/errortaskq.log for clues.

This could be related:
http://help.directadmin.com/item.php?id=107

Also if the account is getting restored but you're just not getting any notices about it, check:
/usr/local/directadmin/data/admin/next_ticket.number
It should contain a number inside it.. and shouldn't be empty.
The value of the number should be the next highest number in the sequence past:
/usr/local/directadmin/data/tickets/*/*

If the next_ticket.number is the problem, there should be a note about it in the errortaskq.log anyway.

Lastly, if the restore starts, keep an eye on "top" and "ps -ax" to see what's going on.
You can try to manually extract the file if you want:
cd /path/to/your/backups
mkdir temp
cd temp
tar xvzf ../backupfilename.tar.gzAnd 40 meg is quite small, shouldn't be a problem. 24 gig is huge, I'm impressed it worked ;)

John

[lseawell]

Moved to new thread