Spurious "deprecated" warning?

Yesterday I did my quarterly update of the software on 3 virtual machines running debian/testing and rdiff-backup was updated from 2.2.2-1 to 2.2.6-1. Today when I looked at the log output from my nightly backup scripts emailed to me from these machines, I see that every invocation of

Re: Backups not working after running out of space

FWIW, my script(s) run "df -h" on the volume (as suggested in the FAQ entry) before and after so I can see the effect of my "remove increments --older-than 1Y" and "backup --print-statistics" invocations, so I knew was down to 5% free, but I also (thought I) had a good idea of the rate of

Re: Backups not working after running out of space

Thanks Eric, Idea #1 didn't help (none of the .gz files where corrupt), but the diagnostic messages I got running idea #2 helped me realize that I needed to remove a(nother) current_mirror, and after I did that the regress succeed, and a subsequent backup also succeeded.  After that,

Re: Backups not working after running out of space

Anyone have any suggestions? If nothing else, is there some way I could remove appropriate files from the rdiff-backup-data directory to get my backups working again? thanks, Peter On 2023-11-13 13:01, Peter Canning wrote: Here's the command I've been using, with -v 6 added, followed by the

Re: Backups not working after running out of space

Here's the command I've been using, with -v 6 added, followed by the output it produced: C:\Users\pcanning\rdiff-backup-2.2.2-64\rdiff-backup.exe -v 6 backup --print-statistics `     --exclude "H:/Lightroom/Processing Catalog/Backups" `     --exclude "H:/Lightroom/Processing

Backups not working after running out of space

Using rdiff-backup 2.2.2 on Windows 10 Pro 22H2, I have a scheduled task that runs my system backup PowerShell script at 2 AM every morning. The script runs rdiff-backup several times to backup several different directories. A few days ago one of the backups failed because the NAS volume

Re: version 2.2 --remove-older-than behavior changed

On 2023-02-16 21:34, Eric Zolf ewl+rdiffbackup-at-lavar.de |rdiff-backup-users| wrote: Hi, On 16/02/2023 20:41, qx6uwum...@liamekaens.com wrote: IMHO, "No increment is older than " is normal behavior and should not cause a warning, especially since nonzero status codes are considered

Re: version 2.2 --remove-older-than behavior changed

IMHO, "No increment is older than " is normal behavior and should not cause a warning, especially since nonzero status codes are considered abnormal termination by most shells (even the Python docs mention this), and can cause backup

Re: What caused my rdiff-backup failure and how can I resolve it.

Thank you Reio.  It was a path length issue.  I used the Local Group Policy Editor to remove the 260 Character Path Limit (as described in https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/) and the backup completed successfully expect for 4 warnings

What caused my rdiff-backup failure and how can I resolve it.

CrystalDiskInfo is reporting that a couple of the S.M.A.R.T attributes for one of my hard drives have changed cause the health status of the drive to switch to "Caution". Fortunately the Windows 10 drive test doesn't report any errors and I haven't had any operational problems yet. I'm

Re: Mangled example(s) in the "Usage examples" page?

On 2023-01-16 22:07, Eric Zolf ewl+rdiffbackup-at-lavar.de |rdiff-backup-users| wrote: Hi, On 16/01/2023 03:48, qx6uwum...@liamekaens.com wrote: It appears that the examples to "lists the times of the available versions of the file ..." in section 6 (Getting information about the backup

Mangled example(s) in the "Usage examples" page?

It appears that the examples to "lists the times of the available versions of the file ..." in section 6 (Getting information about the backup directory) in the "Usage examples" page (https://rdiff-backup.net/examples.html#getting_information_about_the_backup_directory) have gotten mangled.

Re: How to exclude all dotfiles in a folder but include a specific set?

Yeah, I do that (except using Debian/testing) with duplicity for my encrypted off-site backup since it doesn't provide a windows build, but haven't with rdiff-backup because I assumed its Windows build would work better (this is for my existing backups of my

Re: How to exclude all dotfiles in a folder but include a specific set?

Nice, I haven't used --include/exclude before, but I have a use case now so I want to try it. How do I make this work on Windows where there isn't (AFAIK) a common root for all the drives?  For example I want to do rdiff-backup \     --include C:/from1 \     --exclude C:/from1/exclude1 \    

Re: cross-platform backup tool Fwd: [rdiff-backup/rdiff-backup] Pre-release v2.1.2b2 - 2nd beta v2.1.2b2 just fixing Windows

I just noticed I forgot to respond to this. My github user id is pcanning. FYI, I posted a comment to https://github.com/rdiff-backup/rdiff-backup/issues/740 with a question (probably for you).     - Peter On 2022-10-27 01:31, Eric Zolf ewl+rdiffbackup-at-lavar.de |rdiff-backup-users|

Re: cross-platform backup tool Fwd: [rdiff-backup/rdiff-backup] Pre-release v2.1.2b2 - 2nd beta v2.1.2b2 just fixing Windows

That's awesome.  Thanks for fixing it, and for all your work on rdiff-backup. Just FYI, I started working on implementing https://github.com/rdiff-backup/rdiff-backup/issues/740 at the end of September.  Unfortunately I have been busy with some other stuff the last couple weeks, but I'm

Re: cross-platform backup tool Fwd: [rdiff-backup/rdiff-backup] Pre-release v2.1.2b2 - 2nd beta v2.1.2b2 just fixing Windows

I'm still seeing the behavior described below in v2.1.3b3.  Is the need for the extra "\" intentional?  If not I can report an issue. On 2022-09-16 17:44, qx6uwumzvv-at-liamekaens.com |rdiff-backup-users| wrote: Thanks Eric. https://github.com/rdiff-backup/rdiff-backup/release

Re: cross-platform backup tool Fwd: [rdiff-backup/rdiff-backup] Pre-release v2.1.2b2 - 2nd beta v2.1.2b2 just fixing Windows

Thanks Eric. https://github.com/rdiff-backup/rdiff-backup/releases/download/v2.1.2b2/rdiff-backup-2.1.2b2.win64exe.zip is working for for me on Windows 10, but I did encounter one slight surprise. I've been running rdiff-backup 2.0.5 (from Powershell) to backup to a CIFS/SMB share on my NAS

Re: cross-platform backup tool First beta v2.1.2b1 release towards v2.2.0

Is anyone else seeing problems on Windows 10? After downloading and extracting https://github.com/rdiff-backup/rdiff-backup/releases/download/v2.1.2b1/rdiff-backup-2.1.2b1.win32exe.zip, I get a ModuleNotFoundError when i try to run it. > .\rdiff-backup-2.1.2b1-64\rdiff-backup.exe --help

cross-platform backup tool How to see changes in the latest increment?

I run rdiff-backup with --print-statistics, so it displays counts and sizes for new, deleted and changed files. Sometime I look at those numbers (e.g. if they are bigger than I expected) and wonder, which files caused the statistics. I've read the rdiff-backup man page and other documentation