|
HowToUse
How to use FlyBack
To use the GUI, run like this: $ python flyback.py To perform a GUI-less backup, run like this: $ python flyback.py --backup |
Sign in to add a comment
|
|
Search
|
|
HowToUse
How to use FlyBack
To use the GUI, run like this: $ python flyback.py To perform a GUI-less backup, run like this: $ python flyback.py --backup |
Sign in to add a comment
using v 0.4 . . . how do I specify backups every 3 hours? Should the Backup Schedule "hour:" field be something like this: 3 6 9 12 15 18 21 0 ? Is it space separated, comma separated?
niels.olson: it's standard crontab format. See "man 5 crontab" for more details. You can specify every three hours with "0" for minute and "*/3" for hour.
i have installed flyback on a headless debian machine and configured it from another machine (connected with ssh -Y ...). If I connect to this machine with "ssh -Y" runnning flyback with "python /home/tone/flyback/flyback.py --backup #flyback" everything is ok, no gui launched. If I connect to this with standard "ssh 192.168...." I get the following error: "error: could not find python module gtk"
Does Flyback need X to run ?
Where can I find the file whith the log of flyback's operation? what can I do to controll if the backup doesn't start of some file aren't saved? I have a cron rule to run every 3 hour the python flyback.py --backup command?
thank
How do you specify a folder on another computer? The dialog to select the storage location won't show me folders mounted via SSH. I understand that relying on keyring for authentication might be problematic, but I have public/private key logins set up.
I tried typing in ssh://username@host:/path/to/backup/dir and the terminal from which I was running Flyback complained that it couldn't write the directory (presumably it tried creating the directory on the local file system). I'd rather not mount a folder to my local file system with sshfs because that has proven to be buggy for me.
Any ideas?
FB is doing the scheduled backups OK; I made the mistake of thinking that Sunday is the first day of the week.
But it's including a directory from an old FB setup. Where are the preference stored?
anyone got an idea why flyback wants to use gtk when launched GUI-less ?
Great app, just a correction on your project main page as to the required packages to install on ubuntu (hardy)
$ sudo apt-get install python python-glade2 python-gnome2 python-sqlite python-gconf rsync gksu
I would be happy if i had some kind of progress-bar showing how far the backup was.
Great app, just a correction on your project main page as to the required packages to install on ubuntu (feisty)
$ sudo apt-get install python python-glade2 python-gnome2 python-sqlite python-gconf rsync
right, the package is python-sqlite without the number 3.
May we have a more complete guide? It's not very cleare how to backup only a directory, for examples, for a newbie user of linux. Thank you
where can i find how-to restore from backup?
It is true that having a progress bar on the current backup would be very helpful... And more documentation would also be nice on how to set up the application and use it.
That said, I think this is a very good work you have done here. Thanks a heap!
Hi, great application. Simple and easy concept -> Reliable.
I have the same problem as outlined by a few before me here. When running GUI-less (as a cron-job or from a terminal without X) I get "error: could not find python module gtk.
Apparently this works for some but not for all. I am running Fedora 6.
...and I should add that I get this error when using:
$ python flyback.py --backup
When invoking flyback in exactly the same way in an X-enabled environment the backup works fine.
Appreciate advice.
I found a workaround for the gtk problem on a headless machine: - install xvfb - launch e.g. in a screen:
- add the following to the flyback cronjob:works for me. although it's just a workaround. the dependency should be removed for flyback when launched without gui
I found that running flyback.py from a cron job failed silently... turns out it too was the issue about being GUI-less, because the cron job doesn't have a DISPLAY variable set. Adding the line "export DISPLAY=:0.0" to the script which calls flyback.py cured the issue for me.
I just wonder if flyback is still being developed. I am using this tool now for some months and I love it. Can't see any release activities. Is this Project dead or frozen since release 0.4?
Is there a Help (or man) File with FlyBack??.py? I mean for Non-GUI (GUI-less)systems. When I do python flyback.py --help it returns:
option --help not recognized for help use --help
So I am not sure where exactly --help goes?
I also like to find out if this can be ran on a remote system via TCP/IP (such as ssh)?
Thanks! mehdi
PS: Thanks To Martyn .c for: "export DISPLAY=:0.0"
I have created a new file flyback.sh Which contains this: export DISPLAY=:0.0 python /home/USERNAME/programs/flyback/src/flyback.py --backup #flyback
And in my crontab I have this: 0 root /home/USERNAME/programs/flyback/flyback.sh
But still: /var/lib/python-support/python2.6/gtk-2.0/gtk/init.py:72: GtkWarning??: could not open display
Traceback (most recent call last):
glib.GError: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Autolaunch error: X11 initialization failed. )
What do I need to do to get this to work?
I've given up with this because it won't recognise an external HDD. I used to get round this by specifying a directory that would be mounted if the HDD was plugged in and some clever boot stuff in crontab that would mount if it was there, the new restricted interface doesn't allow this and doesn't see the external HDD.
This also involved hacking the crontab command so that it wouldn't run flyback if the disk wasn't mounted, but it worked.
I think I need to track down the old rsync command, which is sad, because the interface here is 10x better.