| home |
| weblog |
| about |
| search |
| license |
| download |
| install |
| docs |
| TooFPy |
| german |
| blogroll |
PyDS has a builtin backup/restore facility. This exports table data to XML files and restores those XML files back into the databases. This has the advantage that you can use it to sync installations on different machines, because you can upstream backup files to your cloud.
To enable backup, you just have to go to your preferences and add a timer with the database backup. Usually you put in a timer with interval 1440 (this is 24 hours). Now every day your backup is saved into a directory on your harddisc.
You can set up upstreaming of backups in your basic preferences (the setting is upstream backup files to cloud). This changes the directory where backup files are written: without upstreaming, it is ~/.PyDS/backup/ and with upstreaming enabled it is ~/.PyDS/www/backup/
With version 0.4.15 there is a run now button in the timer tool to enable you to trigger some timers on demand instead of waiting for it to happen (or deleting it and reinstalling the timer with a different first run time).
To restore, you have to stop the pyds and use the command line tool pyds-restore. This tool takes the URL of the files.xml file created on backup. This is either a local path (don't use the file:// notation, just use the local path like you would with other command line tools) if you don't want to pull your backup from the internet, or it is the full URL of the file. If the backup is password protected, from version 0.6.0 on pyds-restore should ask for the user and password to download stuff.
If you have to use a proxy, you can pass it with the -p parameter. Just give hostname:port for your HTTP proxy.
The restore restores everything that's in the tables and can be read - so if you restore files from different version than your running copy, there might be losses.
Backup doesn't backup all data. What is not backed up are passwords and user credentials. This is for security reasons, as your backups are fully viewable from outside users if you upstream your backups! So you always should store passwords in the PasswordTool and not in your stories or macros directly!
last change 2003-07-30 13:48:16
| July 2003 | ||||||
|---|---|---|---|---|---|---|
| Mo | Tu | We | Th | Fr | Sa | Su |
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 | |||
| Jun 2003 | Aug 2003 | |||||
This text gives a short rundown on how to backup PyDS and how to restore it.
(Donations will be used by the author to buy stuff, fullfill selfish wishes or do other silly recreational things. You have been warned.).
