Backuppc

[Nefarious]

I'm trying to configure a Backuppc server and am running into a few problems. The server finds the shares and backs them up - fine, but I can't seem to get it to exclude files. I have this variable set with no include option given (as BPC will only allow one or other and not both).

$Conf{BackupFilesExclude} = {
'c' => ['/windows', '/i386', '/Program\ Files'],
};


And yet those folders are still backed up, any ideas?

 

[BillytheImpaler]

I'm not familiar with how the config works, but the 'c' portion is suspicious. Is that supposed to denote the Windows mount point? Might it care that C is not capitalized? Same for /windows.

 

[Nefarious]

That wasn't it, lowercase c is the version given in the example files and I tried with all variations as well.

Any more ideas?

 

[Bob Wya Jnr]

I had a look at the docs for your backup program. I wouldn't have a clue what you are doing wrong - basically because you haven't posted enough information. I think we would need to dissect the full configuration file. Do I presume that the backup program is backing up all the files on the "C$" share... but just a little too industriously??

Certainly I can't see anything wrong with what you have posted.

Maybe you could check if it does work if you try:

$Conf{BackupFilesExclude} = ['/windows', '/i386', '/Program\ Files'];

(share matching problem)

or failing that:

$Conf{BackupFilesExclude} = ['/windows', '/i386'];

(escaped characters = fail??)

Bob

 

[Nefarious]

Yes, far far too industriously....

I see what you mean about the lack of information but this is the only part of the BPC config files that deal with exclusions (other than the specific host config file which I have not set any overrides in).

I have tried without the 'Program\ Files' option and making it a universal setting and not just for C.

I am actually running this for a C share not a C$ share as in this instance it's to back up some accounting software that's in the root directory rather than the userfiles (doc'n'settings et al).

The documentation mentioned something about having a reg ex * for exclusions after the directory that you want to exclude but it was a little unclear and didn't work for me anyway.

 

[Nefarious]

Though I am apparently a tard - the expressions are with inverted commas and do not need escape characters......

Still not solved the problem but it does seem to be accepting the $Conf{BackupFilesOnly} setting

 

[Nefarious]

Right, from what I have surmised, there is no problem with my syntax as the same expression works perfectly with the enforced backup just not with the exclude.

I may just have to manually set which folders to backup which is a bit of a hassle but seems the only option open to me that I can get to work ATM.

 

[Bob Wya Jnr]

Yes, far far too industriously....

I see what you mean about the lack of information but this is the only part of the BPC config files that deal with exclusions (other than the specific host config file which I have not set any overrides in).

I have tried without the 'Program\ Files' option and making it a universal setting and not just for C.

I am actually running this for a C share not a C$ share as in this instance it's to back up some accounting software that's in the root directory rather than the userfiles (doc'n'settings et al).

The documentation mentioned something about having a reg ex * for exclusions after the directory that you want to exclude but it was a little unclear and didn't work for me anyway.

Though I am apparently a tard - the expressions are with inverted commas and do not need escape characters......

OK

C = C$

The $ character donotes a "hidden" Windows share i.e. not very hidden at all - as someone busily copies out all your boot drive files . So called "administrative shares" that Windows defaults to. (Sorry if I'm patronising you here!!)

Yeh just wanted to see the whole file... You would be surprised how other statements can impact on the one causing the problem (both syntactically and semantically).

Glad to hear that you have sorted out the escape/inverted comma character issues!!

Your best bet is to back up and the configuration file and keep trying single changes to the file (e.g. simplifying it) till you isolate the problem.

Also is there any way to turn on verbose logging for the software (or a debug mode)?? In my experience Linux/Unix log files are brilliant because they actually contain useful information (contrast with Windows)!!

Bob

 

[Nefarious]

OK

C = C$

The $ character donotes a "hidden" Windows share i.e. not very hidden at all - as someone busily copies out all your boot drive files . So called "administrative shares" that Windows defaults to. (Sorry if I'm patronising you here!!)

Yeh just wanted to see the whole file... You would be surprised how other statements can impact on the one causing the problem (both syntactically and semantically).

Glad to hear that you have sorted out the escape/inverted comma character issues!!

Your best bet is to back up and the configuration file and keep trying single changes to the file (e.g. simplifying it) till you isolate the problem.

Also is there any way to turn on verbose logging for the software (or a debug mode)?? In my experience Linux/Unix log files are brilliant because they actually contain useful information (contrast with Windows)!!

Bob

Not patronising at all, but I do know what the C$ share but I'm not using it, I've created a C share which is non-administrative and can be accessed by 'guest' users. This makes the permissions easier but it wont allow access to Docs'n'Settings, which is fine for my purposes.

I have been making minor alterations and looking at the logs. The program just doesn't seem to 'see' the exclude line. I'm still plugging away at it, I'll let you know if I get anywhere.