BackupPC-users

Re: [BackupPC-users] Exclude all cache folders in Unix

2015-01-05 20:01:15
Subject: Re: [BackupPC-users] Exclude all cache folders in Unix
From: Jose Miranda <joseamirandavelez AT gmail DOT com>
To: Holger Parplies <wbppc AT parplies DOT de>
Date: Mon, 5 Jan 2015 20:59:19 -0400

Holger,

I'm using rsync to back up a VPS root directory. What I want to exclude is the directories created by Wordpress caching plugins to store html files, all named "cache".

My host company actually added individual directories as you recommend. My intention was to avoid doing that in the future when I add new domains, but I guess I'm going to go the "difficult" way and exclude them individually.

On another subject, I'm new here. Is there a link where I can see the old email threads?

Thanks for the detailed answer!

-Jose

On Jan 5, 2015 4:55 PM, "Holger Parplies" <wbppc AT parplies DOT de> wrote:
Hi,

Jose Miranda wrote on 2015-01-04 21:55:01 -0400 [[BackupPC-users] Exclude all cache folders in Unix]:
> I'm trying to exclude all cache folders in the whole server. I'm backing up
> root and I want to exclude anything containing "cache", such as:
>
> /home/admin/.../.../cache/.../...
> /home/admin/.../cache/.../
> /.../.../cache/.../...
>
> What should I use as filter in BackupFileExclude in the web interface?
>
> I tried the following and it didn't work:
>
> /*/cache/*/
> */*cache*

as always, that really depends on the XferMethod, but I'd expect a simple

cache

to work. For rsync(d), there's also

/**/cache

(with no apparent advantage over just "cache"). You could also limit that to
only *directories* named "cache":

cache/

(not sure if that works for tar et al.).

When using the web interface, make sure you get the entry right. You need a
share name to which the exclude applies and one or more patterns to exclude
(not sure what it looks like exactly, I don't use the web interface).

That said, I hope you have no source code repositories with caching mechanisms
implemented in subdirectories named "cache". Relying solely on the name of a
directory for an exclude might not be a good idea. I tend to prefer gathering
a list of cache directories actually used, so I don't end up excluding
something I didn't intend to, because someone named it in a way I didn't
anticipate. This might take some work and will tend to require occasionally
adding new cache directories to the list. It really depends on what is worse
for you: missing files in your backup or having extraneous cache directories
ending up in your backup (which *can* make the whole backup fail). Just
remember that you likely won't notice files being missed, while you will
notice failing backups. Hopefully :-).

Regards,
Holger

P.S.: I can't see anything wrong with using excludes like
      /home/*/.mozilla/firefox/*/Cache
      (also note that not all cache directories are named "cache" ;-).
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
<Prev in Thread] Current Thread [Next in Thread>