How To:Use Wake-On-LAN to Awaken Clients: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(removed Category:How To and added {{How To Header}}) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{How To Header}} | |||
Backup Clients will go to sleep if there is no activity on the client. To backup clients that | Backup Clients will go to sleep if there is no activity on the client. To backup clients that | ||
have to gone to sleep, "wakeonlan" feature has to be used. Currently, Amanda does not do | have to gone to sleep, "wakeonlan" feature has to be used. Currently, Amanda does not do | ||
Latest revision as of 22:10, 22 May 2007
This article is a part of the How Tos collection.
Backup Clients will go to sleep if there is no activity on the client. To backup clients that have to gone to sleep, "wakeonlan" feature has to be used. Currently, Amanda does not do "wakeonlan" before trying doing dump estimate and backup run. There are two ways to resolve the problem:
- Do not allow automatic sleep on servers that need backup.
- Let the amanda server start a script that keeps the clients wake during the backup time: write a marker-file, and start a script in the background that does wakeonlan e.g. every 15 minutes as long as the file exists. When amdump is finished, remove the file. User could even parse the output of amstatus and let the wakeonlan only bother with machines that have not done yet:
amstatus config --waitdumping --estimate --gestimate
The above command would list the necessary machines (no need for --dumping, because real activity does not let the machine go to sleep).