Re: [opensuse] Backup scheduling
Regarding my problems getting scheduled backups (defined using YaST) to run: I read another description of scheduling backups in yet another of my SuSE Linux books, and came across some very non-obvious requirements in the notes there. I'll point them out here, in case anyone else is in the same situation as I. For one, there can be no spaces in the name of a backup. I'm not talking about the backup _file_ name, but the name of the backup itself. So apparently 'full system backup' won't work, but 'full_system_backup' should be okay. According to that book, the backup tool will accept a backup name with a space in it without complaint (as I found out), but the backup won't run. Also, after scheduling the backup(s), one must restart the computer. Nowhere else did I see any indication of that requirement. So I've renamed my two backups, rescheduled them, and rebooted the system. Hopefully that will do it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston pecked at the keyboard and wrote:
Regarding my problems getting scheduled backups (defined using YaST) to run:
I read another description of scheduling backups in yet another of my SuSE Linux books, and came across some very non-obvious requirements in the notes there. I'll point them out here, in case anyone else is in the same situation as I.
For one, there can be no spaces in the name of a backup. I'm not talking about the backup _file_ name, but the name of the backup itself. So apparently 'full system backup' won't work, but 'full_system_backup' should be okay. According to that book, the backup tool will accept a backup name with a space in it without complaint (as I found out), but the backup won't run.
This is why I try to avoid spaces in file/directory names, it just gums up the works. Also, always use an explicit path to the executable unless you also set a path environment before calling the program.
Also, after scheduling the backup(s), one must restart the computer. Nowhere else did I see any indication of that requirement.
Not needed with recent linux releases. Crontab will automatically re-read and changes in the crontab without need for a reboot.
So I've renamed my two backups, rescheduled them, and rebooted the system. Hopefully that will do it.
-- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston wrote:
Regarding my problems getting scheduled backups (defined using YaST) to run:
I read another description of scheduling backups in yet another of my SuSE Linux books, and came across some very non-obvious requirements in the notes there. I'll point them out here, in case anyone else is in the same situation as I.
For one, there can be no spaces in the name of a backup. I'm not talking about the backup _file_ name, but the name of the backup itself. So apparently 'full system backup' won't work, but 'full_system_backup' should be okay. According to that book, the backup tool will accept a backup name with a space in it without complaint (as I found out), but the backup won't run.
Also, after scheduling the backup(s), one must restart the computer. Nowhere else did I see any indication of that requirement.
Eh? I doubt that. I can't envision any possible scenario where such an action would require a linux reboot. Perhaps someone cut and pasted from a guide originally written for windows, or some similar silliness? I'd love to see the reference. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Sloan wrote:
Also, after scheduling the backup(s), one must restart the computer. Nowhere else did I see any indication of that requirement.
Eh? I doubt that. I can't envision any possible scenario where such an action would require a linux reboot. Perhaps someone cut and pasted from a guide originally written for windows, or some similar silliness?
I'd love to see the reference.
Page 572 of "Beginning SUSE Linux", from Apress. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston wrote:
Joe Sloan wrote:
Also, after scheduling the backup(s), one must restart the computer. Nowhere else did I see any indication of that requirement.
Eh? I doubt that. I can't envision any possible scenario where such an action would require a linux reboot. Perhaps someone cut and pasted from a guide originally written for windows, or some similar silliness?
I'd love to see the reference.
Page 572 of "Beginning SUSE Linux", from Apress.
My first reaction on seeing advice to reboot is to think "what idiot wrote this" but I will for the time being withhold judgement until I can find a copy of that and read the context. If my first impression is correct though, it wouldn't be the first time some well meaning writer from a microsoft background recommended a completely unnecessary reboot on a linux system, supposedly to cause some trivial configuration change take effect. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Sloan wrote:
My first reaction on seeing advice to reboot is to think "what idiot wrote this" but I will for the time being withhold judgement until I can find a copy of that and read the context. If my first impression is correct though, it wouldn't be the first time some well meaning writer from a microsoft background recommended a completely unnecessary reboot on a linux system, supposedly to cause some trivial configuration change take effect.
I understand what you're saying. I'm too new at Linux to debate the issue, but I don't know of a Windows system that requires a reboot after creating a scheduled task, either, so it would be hard to place the blame there. It could just be a misunderstanding, but the author(s) seem to know Linux well, judging from the rest of the book. The exact quote on that page, following the section on setting up an automated backup, is: "You'll need to reboot your system for the new scheduling to take effect." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston wrote:
The exact quote on that page, following the section on setting up an automated backup, is:
"You'll need to reboot your system for the new scheduling to take effect."
Yeah that just sounds completely insane. Can you tell me, did the book say to schedule the task with cron? Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Sloan wrote:
"You'll need to reboot your system for the new scheduling to take effect."
Yeah that just sounds completely insane. Can you tell me, did the book say to schedule the task with cron?
No. I think I mentioned earlier that I used the YaST System Backup module to set it up. That writes to /etc/cron.d, but I didn't use cron directly. (And that's the method described in the book as well.) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston wrote:
Joe Sloan wrote:
"You'll need to reboot your system for the new scheduling to take effect."
Yeah that just sounds completely insane. Can you tell me, did the book say to schedule the task with cron?
No. I think I mentioned earlier that I used the YaST System Backup module to set it up. That writes to /etc/cron.d, but I didn't use cron directly. (And that's the method described in the book as well.)
OK, so it does use cron then - whether via a crontab command, or files in /etc/cron.d the end result is the same. and editing cron entries has never required a reboot in any version of unix ever made. That glaring blooper in itself is enough to make me doubt the author really knows much about linux, since it's such a basic point. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston wrote:
Joe Sloan wrote:
My first reaction on seeing advice to reboot is to think "what idiot wrote this" but I will for the time being withhold judgement until I can find a copy of that and read the context. If my first impression is correct though, it wouldn't be the first time some well meaning writer from a microsoft background recommended a completely unnecessary reboot on a linux system, supposedly to cause some trivial configuration change take effect.
I understand what you're saying. I'm too new at Linux to debate the issue, but I don't know of a Windows system that requires a reboot after creating a scheduled task, either, so it would be hard to place the blame there. It could just be a misunderstanding, but the author(s) seem to know Linux well, judging from the rest of the book.
The exact quote on that page, following the section on setting up an automated backup, is:
"You'll need to reboot your system for the new scheduling to take effect."
About the only thing in Linux that requires a reboot is a kernel update. However, some configuration changes may require restarting some service. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Knott pecked at the keyboard and wrote:
Jerry Houston wrote:
Joe Sloan wrote:
My first reaction on seeing advice to reboot is to think "what idiot wrote this" but I will for the time being withhold judgement until I can find a copy of that and read the context. If my first impression is correct though, it wouldn't be the first time some well meaning writer from a microsoft background recommended a completely unnecessary reboot on a linux system, supposedly to cause some trivial configuration change take effect.
I understand what you're saying. I'm too new at Linux to debate the issue, but I don't know of a Windows system that requires a reboot after creating a scheduled task, either, so it would be hard to place the blame there. It could just be a misunderstanding, but the author(s) seem to know Linux well, judging from the rest of the book.
The exact quote on that page, following the section on setting up an automated backup, is:
"You'll need to reboot your system for the new scheduling to take effect."
About the only thing in Linux that requires a reboot is a kernel update. However, some configuration changes may require restarting some service.
Kernel boot parameter changes also need a reboot AFAIR. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On December 22, 2007 06:00:53 pm James Knott wrote:
About the only thing in Linux that requires a reboot is a kernel update. However, some configuration changes may require restarting some service.
Yes. For example, tonight I changed the address of the airport I get weather info from in Kweather, and it wouldn't change location unless I rebooted. -- Bob Smits bob@rsmits.ca A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Robert Smits wrote:
On December 22, 2007 06:00:53 pm James Knott wrote:
About the only thing in Linux that requires a reboot is a kernel update. However, some configuration changes may require restarting some service.
Yes. For example, tonight I changed the address of the airport I get weather info from in Kweather, and it wouldn't change location unless I rebooted.
Nah, I'll bet my life savings that you didn't need to reboot. Linux just doesn't work that way. But I've heard of people reinstalling the OS rather than editing a config file, so nothing surprises me anymore. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Sloan wrote:
Robert Smits wrote:
On December 22, 2007 06:00:53 pm James Knott wrote:
About the only thing in Linux that requires a reboot is a kernel update. However, some configuration changes may require restarting some service.
Yes. For example, tonight I changed the address of the airport I get weather info from in Kweather, and it wouldn't change location unless I rebooted.
Nah, I'll bet my life savings that you didn't need to reboot. Linux just doesn't work that way.
But I've heard of people reinstalling the OS rather than editing a config file, so nothing surprises me anymore.
That's because Microsoft taught them that reinstalling the OS is the only thing that works. When Bill Gates dies, I will dance in the street, and make immediate plans to visit his grave...so I can urinate on it. If I'm lucky, it will be while his friends and family are there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Robert Smits wrote:
On December 22, 2007 06:00:53 pm James Knott wrote:
About the only thing in Linux that requires a reboot is a kernel update. However, some configuration changes may require restarting some service.
Yes. For example, tonight I changed the address of the airport I get weather info from in Kweather, and it wouldn't change location unless I rebooted.
That doesn't sound right. Logging out and logging back in restarts KDE, and therefore, should restart Kweather. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Robert Smits wrote:
On December 22, 2007 06:00:53 pm James Knott wrote:
About the only thing in Linux that requires a reboot is a kernel update. However, some configuration changes may require restarting some service.
Yes. For example, tonight I changed the address of the airport I get weather info from in Kweather, and it wouldn't change location unless I rebooted.
Did you try restarting the app or service? -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston wrote:
Joe Sloan wrote:
My first reaction on seeing advice to reboot is to think "what idiot wrote this" but I will for the time being withhold judgement until I can find a copy of that and read the context. If my first impression is correct though, it wouldn't be the first time some well meaning writer from a microsoft background recommended a completely unnecessary reboot on a linux system, supposedly to cause some trivial configuration change take effect.
I understand what you're saying. I'm too new at Linux to debate the issue, but I don't know of a Windows system that requires a reboot after creating a scheduled task, either, so it would be hard to place the blame there. It could just be a misunderstanding, but the author(s) seem to know Linux well, judging from the rest of the book.
The exact quote on that page, following the section on setting up an automated backup, is:
"You'll need to reboot your system for the new scheduling to take effect."
That has NEVER been true form of Unix released as far back as 1980, and probably even older. I would never trust anything ever written by that author concerning Unix or Linux ever again. Or anyone else associated with this book (the editors and internal reviewers, if named in the front piece, dedication or acknowledgements sections). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston wrote:
Regarding my problems getting scheduled backups (defined using YaST) to run:
I read another description of scheduling backups in yet another of my SuSE Linux books, and came across some very non-obvious requirements in the notes there. I'll point them out here, in case anyone else is in the same situation as I.
For one, there can be no spaces in the name of a backup. I'm not talking about the backup _file_ name, but the name of the backup itself. So apparently 'full system backup' won't work, but 'full_system_backup' should be okay. According to that book, the backup tool will accept a backup name with a space in it without complaint (as I found out), but the backup won't run.
Remember...embedded spaces in names cause innumerable problems. By the way: full.system.backup is easier to type than full_system_backup.
Also, after scheduling the backup(s), one must restart the computer.
Are you sure? If it's scheduled in cron there's no need to reboot... cron re-reads the crontab files every time a new one is committed (using the crontab command).
Nowhere else did I see any indication of that requirement.
So I've renamed my two backups, rescheduled them, and rebooted the system. Hopefully that will do it.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Aaron Kulkis -
James Knott -
Jerry Houston -
Joe Sloan -
Ken Schneider -
Robert Smits