[very] Long Restore
- Thread starter MtK
- Start date
floyd
Verified User
- Joined
- Mar 29, 2005
- Messages
- 6,248
I have noticed that after the restore DA does a quota check on every user and not just the user that was restored. If you have a lot of users with a lot of files then this will take a long time. I have a really nice server with a lot of users and files and the restore can take over 2 hours. All the files are in place and the sites come up. But no message about it being done for over 2 hours.
To get the user to show up you can delete the show_all_users cache.
To get the user to show up you can delete the show_all_users cache.
not sure I know why a global quota check is needed on a simple user-restore process...
can u explain more about this?
floyd
Verified User
- Joined
- Mar 29, 2005
- Messages
- 6,248
When you click Show All Users you are looking at a cache. If you delete the cache and then click Show All Users a new cache file will be created.
The task queue does this automatically at the end of a restore. But it is taking a long time for it to get to that point.
I KNOW. I have been meaning to report it but other things have taken priority. Maybe they will see this post.
The task queue does this automatically at the end of a restore. But it is taking a long time for it to get to that point.
I KNOW. I have been meaning to report it but other things have taken priority. Maybe they will see this post.
- Joined
- Feb 27, 2003
- Messages
- 8,437
Hello,
The disk usage is re-counted because the Reseller needs an updated total of all items, including disk usage, email accounts, etc..
You can disable this post-restore tally with this feature:
http://www.directadmin.com/features.php?id=853
Note the post restore tally does not run the "quotacheck" command, but rather a disk usage and totals update (repquota, user.usage, etc). It won't run webalizer or rotate any logs here.. it's just a counting tally.
John
The disk usage is re-counted because the Reseller needs an updated total of all items, including disk usage, email accounts, etc..
You can disable this post-restore tally with this feature:
http://www.directadmin.com/features.php?id=853
Note the post restore tally does not run the "quotacheck" command, but rather a disk usage and totals update (repquota, user.usage, etc). It won't run webalizer or rotate any logs here.. it's just a counting tally.
John
in my case, most user are under one reseller therefore each simple/small backup will take forever to be seen...
- Joined
- Feb 27, 2003
- Messages
- 8,437
The tally should not be done for all Resellers, but only for the creator of that User and all of his Users. In any case, for those who don't wish to use this feature, as mentioned, it can be disabled in the directadmin.conf.
John
John
do we have this feature for post-backup?
is it relevant...?
- Joined
- Feb 27, 2003
- Messages
- 8,437
The tally isn't run after a backup because nothing is being added.
If you want the tally to run, it would be only to count the space used from the newly created backup.. which could be done with one of the backup post.sh scripts... but most people aren't too worried about that, since it's usually admin doing it, and it will be added up later anyway.
John
If you want the tally to run, it would be only to count the space used from the newly created backup.. which could be done with one of the backup post.sh scripts... but most people aren't too worried about that, since it's usually admin doing it, and it will be added up later anyway.
John
thanks, you're right, I don't really need to run the tally.
just wanted to be sure it doesn't run (and if so, can be stopped).