Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
The error messages that you receive is because sockets are not real files, but connection between two programs. For postfix it seems to be OK to backup while live.
The oracle think looks more serious, what is that, a database? You might run into trouble when you need to restore that ever.
For both processes I recommend to stop them first before backing up, then restart them. For postfix you might leave it like that, or skip the /var/spool/directories directories. For oracle it is better to stop it to prevent that you have an inconsistent database when restoring.
Would also suggest that you add v in your options, that way you'll see every file as it's being processed, this will give you a warm fuzzy feeling that things are still working.
As per the my knowledge, /var contains changing files when running the OS.
So can I avoid the /var when I take an OS backup? I really dont need any application specific files to be backed up.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
In principle that assumption is correct. But if I can avoid it, I would not skip the var directory. The OS must be able to reconstruct the /var, but it doesn't mention the amount of effort needed.
Just skip /var/tmp and /var/spool/postfix and that problem is solved.
However, Oracle might not be happy at all when backing up and restoring at database(?) which is in unknown state, so again, it is better to stop that Oracle process during backup, or make a database dump before backing up. Making a dump is MySQL or Postgresql speak, I don't know what your Oracle thingy is or supports.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.