[lbackup-discussion] Error messages running example backup in Mac OS X 10.5.8
reply to this message via the mailing list
Wed Jul 11 10:47:42 NZST 2012
On 10 July 2012 05:22, henri <shustak at connect.homeunix.com> wrote:
>> I am testing LBackup on my system running newly installed and updated
>> Mac OS X 10.5.8. I followed the configuring basic backup instructions
>> (http://www.lbackup.org/configuring_a_basic_backup) on the LBackup
> Glad to know you are trying out LBackup. Thank you for reaching out to the LBackup community and if you have any comments or suggestions then they are very welcome. Please report back once you have it working or if you are still having problems after looking over the information listed below.
> I believe the problem you are seeing is related to your LBackup configuration directory path containing a space.
> At present any LBackup configuration directory must not contain spaces (or various shell interpreted characters). There have been plans to add support for more complex paths to the LBackup configuration directories. However, adding this will require time and testing and there are many other features which are higher up in the priority list for the developers at Lucid. However, if you are willing to branch the project and work on a patch then we would assist with testing. A note has been added to the LBackup online manual about this : <http://www.lbackup.org/lbackup_manual#lbackup_configuration_directory_notes>
> To confirm my assumption is correct would you please report back on the current path to your LBackup configuration directory. For example when you run LBackup what is the full command? For example : "/usr/local/sbin/lbackup /etc/lbackup/testing/test_backup.conf"
> LBackup offers a great deal of flexibility with regards where the backup configurations may be located. For example, you are not limited to the "/etc/lbackup" directory. As an example, if you wanted to place the LBackup configuration(s) on your desktop or store them in multiple locations or organize them into a folder hierarchy that is fine. An example of the command to run LBackup with a LBackup configuration located on the desktop of the user with a short name of "backup" would be something like the following : "/usr/local/sbin/lbackup /Users/backup/Desktop/testing_backup_conf/test_backup.conf"
> Please note the issue regarding the log file names (if you are not using the alpha release) <http://www.lbackup.org/known_issues> : "If your log file has a space or other character which requires escaping in the path name then it will not work. A bug fix for this issue, is slated for the next release. It has already been fixed in the latest alpha."
> Finally, with regards spaces in the names <http://www.lbackup.org/known_issues> : "Backups will fail if the last directory specified in the path as the backup destination has a space in the name. Please ensure that the backup destination directory specified within your LBackup configurations has no space. The LBackup team are investigating this issue." My understanding is that this issue has been resolved. However, this requires confirmation. If you have any problems then please report back. Once this issue has been confirmed to be resolved then it will be removed from the known issue list or it will be re-assigned to someone to look investigate further.
> I hope this information is helpful. In conclusion, I will add a note to the LBackup documentation about this current restriction on the location of the LBackup configuration directory placement within the file system.
> Should you have any questions or need additional help then please let us know.
Thank you for your extensive reply! I did some testing and here is what I found:
(1) I move my LBackup configuration to a path that doesn't include a
space, and it worked. I will remember this in the future. Thank you
for adding a note about this in the online manual.
(2) I will also make sure my log files don't have spaces in their names.
(3) Once the configuration file worked, I tested backing up files and
folders with spaces in their names or paths. All seem to work so far.
This is very good and important!
Now that a basic backup works, I do have a few more questions that I
will post in another email.
Thank you again for your quick and detailed response!
More information about the lbackup-discussion