Okay, I might have handled that incorrectly . . . the "***" (triple asterisk signs) were to obscure the ip address on the mailing list only. That is NOT the ip address my server is using for a client.

Sorry for confusion.

I found my "old" BackupPC notes book and in it found a mailing list post from 2009 that instructions to "rm -rf /var/lib/backuppc/pc/[hostname]" and that "BackupPC Nightly" will take care of the rest.

I have decided to give that a go and see what happens.

Bob Wooden of Donelson Trophy

615.885.2846
www.donelsontrophy.com

"Everyone deserves an award!!"

On 2015-07-24 10:02, Michael Stowe wrote:

On 2015-07-24 06:54, Bob of Donelson Trophy wrote:

I am receiving this email: The following directories are bogus and are not being used by BackupPC. This typically happens when PCs are removed from the backup list. If you don't need any old backups from these PCs you should remove these directories. If there are machines on this list that should be backed up then there is a problem with the hosts file: - /var/lib/backuppc/pc/192.168.***.119 Regards, PC Backup Genie This was a 'test' host and the host was removed, weeks ago. I assumed that BackupPC (v3.3.0) would eventually remove the bogus directory. Searching the 'net' results in some very old ways of removing this directory. In the past I simply "rm -rf /var/lib/backuppc/pc/192.168.***.119" but I have read that it does not work properly. What is the correct manner to remove this bogus directory?

Well, that filename is a bit of a treat.  The shell will try to expand it and you may have unintended consequences unless you escape the stars ...

cd /var/lib/backuppc/pc
cd 192.168.\*\*\*.119 (or) cd "192.168.***.119"
rm -f -r *
cd ..
rmdir 192.168.\*\*\*.119 (or) rmdir "192.168.***.119"