When performing a file backup, the following message is received in the client log:
[YYYY-MM-DD hh:mm:ss][erro][Error][New File] File="/proc/FILE" Error="[NixUtil.c.Java_com_afc_util_nix_NixUtil_read] Fail to read file. Error='Invalid argument'"
This type of error message does not appear on the backup report, but in the client log only.
The message suggests that ServosityPro is attempting to perform backup on system directories such as /proc, /dev, /tmp ... etc.
To resolve the issue, please exclude the "/proc" directory from the backup set. Please also exclude other directories from the backup source (e.g. /dev, /tmp, /root/.obm, /usr/local/obm ... etc)
The /proc file system is a pseudo file system that should never be backed up. It is not a real-file system, but rather a virtualized view of the running kernel and environment. It includes files such as /proc/kcore, which is a virtual view of the entire running memory.
A new /proc file system is created every time the machine reboots. Thus, it is unnecessary to perform backup on this directory.
In general, there are some directories that you want to back up:
- /etc -
contains all of your core configuration files. This includes your network configuration, system name, firewall rules, users, groups, and other global system items
- /var -
contains information used by your systems daemons (services) including DNS configurations, DHCP leases, mail spool files, HTTP server files, etc
- /home -
contains the default user home directories for all of your users. This includes their personal settings, downloaded files, and other information your users don't want to lose
- /root -
is the home directory for the root user
- /opt -
is where a lot of non-system software will be installed. OpenOffice, JDKs, and other software is also installed here by default
There are directories that you should consider not to back up:
- /proc -
should never be backed up. It is not a real-file system, but rather a virtualized view of the running kernel and environment. It includes files such as /proc/kcore, which is a virtual view of the entire running memory. Backing these up only wastes resources
- /dev -
contains the file representations of your hardware devices. If you are planning to restore to a blank system, then you can back up /dev. However, if you are planning to restore to an installed Linux base, then backing up /dev will not be necessary.