Difficulties with restore large user database account

[burekas]

Hi,

I have a large user account that I need to restore
(It includes ~3G sql file in the "backup" directory)

At the first time after a few hours (~6,7 hours)
I got few main errors:
1. Unable to get quotas: repquota: Mountpoint (or device) / not found or has no quota enabled.
repquota: Not all specified mountpoints are using quota.

2. Unable to run webalizer for <domain> : /usr/bin/webalizer: error while loading shared libraries: libgd.so.2: cannot open shared object file: No such file or directory

3. Unable to run webalizer for mizrahit.co: Error: Unable to restore run data (99)

Basically I think I fixed them, and in addition config mysql paramters for big database.

But I still don't succeed to restore this user.
The restore progress is stuck on the same value for a long time on "Restoring Databases" according to the "Backup Monitor"

My questions are:
1) How long usually it takes to restore user account like this?
2) How can I know if is it stuck or is it still in progress? So I'll be able to know if I need to wait.
3) Do you any tips for restoring users like this?

Tell me if you need more info to help me with that.

Thanks.

 

[burekas]

In addition, after ~6,7 hours of waiting for restore to be done, the "Backup Monitor" says that "Backup is stalled"
and "Details: No progress in 6 hours, lost connection to tracker".

So my question is:
1) Why and what could make this happens?
2) How can I know there is no progress before I'm waiting these 6 hours?

Is there any other way to try to restore this tough user that will make the same effect as restoring through DA panel? SSH?

 

[burekas]

And according to the last comment, just to mention that mysql is still creating the database (There is a very large table based on InnoDB engine that takes a very long time)
So my question is that when mysql will finish its progress, DA will recognize it and back in order to finish the entire restore progress, or this "Backup is stalled" message will remain?

Thanks.

 

[burekas]

You can close this issue, after 17 hours it done.