[case 45011,45028] 11.28 full backup is not a full backup: excludes files named core

[MironJ]

Hi,

When I manually run full backup via cPanel or automatically via daily cron backup, some files/folders are not copied to the backup folder/archive.

~~~~~~~~~~~~~~~~~
Skipping public_html/g2data/cache/module/core
Skipping public_html/modules/core
Skipping public_html/app/code/core
Skipping public_html/app/design/frontend/default/mvz/template/core
Skipping public_html/app/design/frontend/default/default/template/core
Skipping public_html/plugins/editors/ckeditor/ckfinder/core
~~~~~~~~~~~~~~~~~

So, most web sites will not work after I do a full backup restore or move&restore full backup on the another server.

Where I can setup server wide for all accounts to not skip folders with name "core"?


Regards,

 

[cPanelDon]

When I manually run full backup via cPanel or automatically via daily cron backup, some files/folders are not copied to the backup folder/archive.

~~~~~~~~~~~~~~~~~
Skipping public_html/g2data/cache/module/core
Skipping public_html/modules/core
Skipping public_html/app/code/core
Skipping public_html/app/design/frontend/default/mvz/template/core
Skipping public_html/app/design/frontend/default/default/template/core
Skipping public_html/plugins/editors/ckeditor/ckfinder/core
~~~~~~~~~~~~~~~~~

So, most web sites will not work after I do a full backup restore or move&restore full backup on the another server.

Where I can setup server wide for all accounts to not skip folders with name "core"?

Is "core" the entire name of each directory or file being skipped, or are there any other letters, numbers, or other characters in the names?

Check the contents of "/etc/cpbackup-exclude.conf":

# cat /etc/cpbackup-exclude.conf

Look for a single entry containing the following:

*/core

If you see a line containing only "*/core" try removing only that entry, then generate a fresh backup to verify the results. You may, optionally, force cpbackup to run using the following command; this should update your daily incremental backups:

# /scripts/cpbackup --force

The "*/core" entry exists for backwards compatibility with older Linux distributions using Kernel version 2.4 and older, where the default name of a core (memory) dump file is just "core" without an appended process ID (PID).

 

[MironJ]

Is "core" the entire name of each directory or file being skipped, or are there any other letters, numbers, or other characters in the names?

It's just a directory name, without any other letters, numbers or any other characters.
Many new Joomla components and modules are using directory name "core".

Check the contents of "/etc/cpbackup-exclude.conf":

# cat /etc/cpbackup-exclude.conf

Look for a single entry containing the following:

*/core

If you see a line containing only "*/core" try removing only that entry, then generate a fresh backup to verify the results.

Done that, I will wait for the next backup run.
Will leave more info tommorow after i see a backup log.

 

[cPanelNick]

We are discussing the potential removal of this default exclude in case 45011.

Thank you.

 

[MironJ]

Hi,

Just to confirm that after removing "*/core" entry from the file "/etc/cpbackup-exclude.conf" backup archive is finally full.

Thanks,
Miron

 

[VeZoZ]

We are discussing the potential removal of this default exclude in case 45011.

Thank you.

We hope this will be removed as looking at the code it seems silly:

*/core
*/core.[0-9]
*/core.[0-9]*
*/core.[0-9][0-9]

I assume it's attempting to deal with core dumps. Considering it would be core.[0-9] for a dump doing it for literally files and folders named "core" seems lazy.

 

[cPanelKenneth]

We hope this will be removed as looking at the code it seems silly:

*/core
*/core.[0-9]
*/core.[0-9]*
*/core.[0-9][0-9]

I assume it's attempting to deal with core dumps. Considering it would be core.[0-9] for a dump doing it for literally files and folders named "core" seems lazy.

Some systems name(d) their core dumps core.

 

[VeZoZ]

Some systems name(d) their core dumps core.

My mistake forgot about 2.4 kernels haven't ran those in ages.

 

[txspaderz]

If this is for core dumps only, I suggest fixing the regex.

Use this, or something like it:

core\.?[0-9]*$

I use this daily, and I have yet to have it match something that is NOT a core dump.

 

[TheSidewinder]

I can confirm that cpbackup's default config does exclude any directory named 'core'.

IP.Board forum software has a directory of that name under it's ./admin/applications/ directory.

Fortunately, there are no files in that directory that are ever changed, so if you simply upload the contents of that directory from the software's ZIP file (of the same version) you'll get back on line.

I've removed the line, referenced above, from my /etc/cpbackup-exclude.conf file, and will check the backups after they next run.

 

[cPanelKenneth]

My mistake forgot about 2.4 kernels haven't ran those in ages.

It's also FreeBSD, at least according to this:

Compiling with cc.

heh. Looks like the handbook is wrong: http://www.freebsd.org/cgi/man.cgi?...on=5&manpath=FreeBSD+4.11-RELEASE&format=html

 

[TheSidewinder]

Just to followup.....

Removing or commenting out that line resolved the issue.

 

[cPanelDavidG]

Re: [case 45011,45028] 11.28 full backup is not a full backup: excludes files named c

Both Cases 45011 and 45028 are addressed in 11.28.56. To see if your update tier is yet at this version (or later), visit Downloads - cPanel Inc.