As I said, I'm not aware of any difference in path requirements for the
* exclusions. I have a mix of full and relative pathnames in the *
exclusions for my personal PC and they work just fine. There are
differences between the backup methods (samba, rsync, tar, etc) since
the exclusions are passed along to them and some of them have slightly
different syntax requirements.
On 1/5/2018 12:28 PM, A.Rubio wrote:
is correct, but in my experience, many years ago, to exclude a
directory in *, you need to place the full pathname because if you
only put a relative name it does not work well.
it's possible ?
El 05/01/18 a las 18:05, Bowie Bailey escribió:
In my example, sharename1 and sharename2 are explicitly specified in
BackupFilesExclude. So the * exclusions will apply to all shares
except sharename1 and sharename2. If all you have is the *
exclusions, then they apply to everything.
$Conf{BackupFilesExclude} = {
'sharename1' => [
'exclusion1',
'exclusion2',
],
'sharename2' => [
'exclusion3',
'exclusion4',
],
'*' => [
'exclusion5',
'exclusion6',
],
};
On 1/5/2018 11:20 AM, A.Rubio wrote:
OK, but, i don't understand "shares that are not explicitly specified".
If I put my config on the server. Are all directories
wp-content/cache excluded from /home/www/* ?
thanks
El 05/01/18 a las 17:03, Bowie Bailey escribió:
If you use * as the share name in the exclude, then that will apply
to any shares that are not explicitly specified. If you specify a
share to add additional exclusions, you'll have to duplicate the
generic ones for that share.
I am not aware of any special path requirements. The path
specification should be the same regardless of how you specify the
share. It is simply relative to the root of the share directory.
Bowie
On 1/5/2018 10:24 AM, A.Rubio wrote:
If sharename is *, you must place the full path of the directory.
For example
$Conf{BackupFilesExclude} = {
'*' => [
'/home/www/*/wp-content/cache', // wordpress
]
};
El 05/01/18 a las 16:16, Augusto Murri escribió:
Okk thank you Bowie,
so a common option can be use * as share name, and put a list of
common cms cache path's, is not wrong isn't?
$Conf{BackupFilesExclude} = {
'*' => [
'wp-content/cache/', // wordpress
'cache/cachefs/', // prestashop
'var/cache/' // pcscart
]
};
thanks again
2018-01-05 15:43 GMT+01:00 Bowie Bailey <[email protected]
<mailto:[email protected]>>:
On 1/5/2018 7:55 AM, Augusto Murri wrote:
Hi all,
i am tring to configure BackupPc to EXCLUDE some
directories on my backups.
I need to exclude many (very big) caches directories from
backups on different machines
can you help me?
this is my configuration but doen't work, navigationg on
the backups i always have /wp-content/cache/ directory
filled of GB of files
$Conf{BackupFilesExclude} = {
'cscart-cache' => [
'/*/var/cache/*'
],
'prestashop-cache' => [
'/*/cache/cachefs/*'
],
'wordpress-cache' => [
'/*/wp-content/cache/*'
]
};
Looks like the mistake is that the first part of the
exclusion isn't a label, it has to either exactly match one
of your share names, or '*' if the exclusions apply to all
shares. Since I don't know your share names, I can't tell
you exactly what it should look like, but it general, it
looks like this:
$Conf{RsyncShareName} = [
'sharename1',
'sharename2',
'sharename3',
'sharename4',
];
$Conf{BackupFilesExclude} = {
'sharename1' => [
'exclusion1',
'exclusion2',
],
'sharename2' => [
'exclusion3',
'exclusion4',
],
'*' => [
'exclusion5',
'exclusion6',
],
};
So the first two exclusions only apply to sharename1, the
next two only apply to sharename2, and the last two apply to
all other shares (sharename3 and sharename4 in this example).
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project:http://backuppc.sourceforge.net/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project:http://backuppc.sourceforge.net/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project:http://backuppc.sourceforge.net/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
