Hot answers tagged deja-dup
Of course you can do that. From the gnome DejaDup Help wiki (oh and where it says file you can also read directory) Restore a Lost File with Déjà Dup Open the file browser (Nautilus) Browse to the folder containing the file you lost Click File ▸ Restore Missing Files… When the Restore dialog appears, it will scan for files that are in the backup but ...
You need to install the python-boto package.
Configure Deja Dup for your root backup: gksu deja-dup-preferences. Run backup then with: gksu "deja-dup --backup". At least this worked for me. (You have to configure Deja Dup for root, too, at first - next to your configuration for the "normal" user.) As mythsmith says: "You can do that just for system folders, and still keep your home folder ...
The deja-dup settings can also be changed with dconf-editor in the dconf-tools apt package. The settings are in org.gnome.DejaDup.
Files associated with full and incremental backups: A full backup contains all the data of that backup, and it does not depend on any other backups. It consists of at least three files: duplicity-full.DATE.manifest (just one) duplicity-full.DATE.volYYY.difftar (one or more) duplicity-full-signatures.DATE.sigtar (just one) If the backup is encrypted, ...
Install Scheduled Tasks: Add a job to it with the following parameters (replace every minute with every hour or the schedule you want to use): You can even hide the pop-up window by using deja-dup --backup --auto as the command or use X-Application: suppress outup in the default behavior drop box, it will hide the window while deja-dup runs.
Yes, Déjà Dup now (as of Ubuntu 11.10) supports backing up files directly into Ubuntu One. Select 'Ubuntu One' under 'Storage', like below:
Déjà Dup is the front-end for the duplicity program, Duplicity stores its data in ~/.cache/duplicity. That folder can safely be removed, if you connect with an earlier backup, those files will be recreated from the backup. Settings for Déjà Dup are stored in dconf. (source: Where is the configuration for dejadup stored?). To quote Michael Terry: Hello! ...
Although it seems like the Déjà Dup code could not be easily modified to accomodate an hourly option, backups can be manually initiated and this can easily be added as a cron job that runs on the hour. Here are the steps you need to take: Run the following two commands in a terminal to enable local access to the X server: xhost +local: xhost Now run ...
After setting up your backup, press "back up now". A dialog will then appear asking you if you want to password-protect your backup. If you do choose a password, your backup is automatically encrypted with that password.
Yes, you can, but it's a bit hidden. You can do it on the console: gsettings set org.gnome.DejaDup.S3 bucket 'MYBUCKETNAME' Or you can do it graphically: Install the package 'dconf-tools' Run dconf-editor Browse to /org/gnome/deja-dup/s3 Edit the bucket key
Firstly, this is not the system cache. The system cache is a cache that resides in memory and occupies physical memory that is not otherwise used by applications. This is a .cache folder inside your home directory, so not system-wide at all. You can, if you need the space, safely delete it (only a misbehaving program would die if you delete stuff it's put ...
This file is used to see the entropy when using cryptographic tools, e.g. OpenSSL. You can safely delete it and there's no need to backup it. So, why do we have it then? On most systems we don't have a lot of activity we can use as a random source and to speed up the process for generating random enough cryptographic keys, this file contains previously ...
I fix this problem by myself. The deja-dup-monitor is a component of "Deja Dup Backup Tool". When search with keyword "backup", this software appears blatantly in the first place in the Software Center. After uninstalling it, everything will return to order. I then reinstalled this software just to leave a review warning people not to install it, if they ...
So there are three possible places where Deja Dup might be out of space, and I don't think its error message tells you which. There is a bug filed about that. You may have run out of space on the target partition (which it sounds like you didn't) You may have run out of space in your home directory (~/.cache/deja-dup can get large) You may have run out of ...
Deja Dup cannot do that at the moment, you are right. And it currently doesn't plan to (the feature request bug is marked Won't Fix). I've heard good things about Back In Time, but haven't tried it myself.
Update Deja-dup to 24.x or latest release. In later version of 23.x they have added integrity check feature. Have a look this link. https://bugs.launchpad.net/deja-dup/+bug/1055356 After every backup, we make a small check to confirm we can restore a test file. And every two months, we make a more intensive check.
Great question! I actually do this quite frequently (every few months). To do so, I use rsync to copy all of my /home partition/directory from the OLD machine to the NEW one. First, ensure that you have openssh-server and ecryptfs-utils installed and running on the NEW machine. sudo apt-get install openssh-server ecryptfs-utils You could install your ...
Not yet, however there's been progress in this area, follow this bug report: https://bugs.launchpad.net/duplicity/+bug/1039511
The above answer did not work for me as the drive that had originally been backed up has has been removed. I share the procedure I followed below: In a terminal, type: duplicity list-current-files --no-encryption file:///[path_to_backup_folder] > /home/[your_username]/list.txt Be aware of the format "file:///..." in which duplicity expects to ...
That feature is on the wishlist, for now you can try setting the schedule to monthly in the preferences and setup your own schedule using crontab and deja-dup --backup.
From v14 release note: The most visible new feature is much better support for external drives. Now Deja Dup will notice if the drive is not connected when a scheduled backup occurs, and will wait for it to be connected. It will notify you that it is waiting.
My 'back up now' button was disabled. In my case the problem was that when I opened the Deja Dup config, the 'storage' option was set to 'Ubuntu One', and it opened another window for logging into that. I changed the storage setting to a local drive, but it took me a while to realise I had to cancel the Ubuntu One login before Deja Dup would allow me to run ...
In my case, there was no backup running but deja-dup had a couple of things running. I did a ps -eaf | grep dup and killed the pids. Then I started DejaDup from the menu and the button was active.
No, you can't. But Deja Dup is just a graphical front end for the command line tool duplicity, which you can use on a server. Its command line interface is a bit complicated, but read its man page or some of the instructions in Deja Dup's manual restore help page: https://live.gnome.org/DejaDup/Help/Restore/WorstCase
It looks like Déjà Dup keeps at least two full backups before it will free up space by overwriting old ones. You mention you have been using it for a 'couple months'. I bet that means you are up against this limitation. Full backups can't be scheduled exactly, but it is going to be about once a month with scheduled backups happening weekly. You can ...
duplicity, which Déjà Dup is built upon on, does not have any such intelligence. Hence any moved or renamed files will be treated as new files.
It seems that it doesn't really save them anywhere, but if you run it with the environment variable DEJA_DUP_DEBUG=1 you can get all the information that way. Source: https://answers.launchpad.net/deja-dup/+question/125731
Per manpage: http://manpages.ubuntu.com/manpages/natty/man1/deja-dup.1.html SYNTAX: deja-dup --restore FILES EXAMPLE: deja-dup --restore /usr/lib/cgi-bin/somefile.txt This will restore the last known copy of this file. So if your last backup was on 5/15/2014, then only data up to 5/15/2014 will be present in somefile.txt . I've actually run this ...
I've been able to solve my question after finding this web page. You need to update the owner and group for each file which is failing to backup. I used these commands to solve the situation. sudo chown mjwittering .cache/dconf .gvfs sudo chgrp mjwittering .cache/dconf .gvfs Then run the backup again, which should now complete successfully.
Only top voted, non community-wiki answers of a minimum length are eligible