Every system administrator should know that server backups are necessary and they must be configured so soon as possible. One of the first things you're taught as an IT professional. And yet every day another unlucky soul ends up with corrupted or deleted data, because the server hanged or the hard disk broke and suddenly realized that they forgot to setup a backup. Sounds familiar? I hope not, but almost everyone ends up in that place, eventually. Lett's at least try not to repeat these mistakes.
So, today, let me show you the basics of setting up a backup on your Linux system.
I'd recommend getting it directly from a DNS server. Keep reading!
A terminal is at the end of an electric wire, a shell is the home of a turtle, tty is a strange abbreviation and a console is a kind of cabinet.
Well, etymologically speaking, anyway.
In unix terminology, the short answer is that
Whether you've been there or not yet, cabling problems happen to everyone at somepoint. In no particular order here are some suggestions that have been helpful over the years.
We all know it happens. A bitter old IT guy leaves a backdoor into the system and network in order to have fun with the new guys and show the company how bad things are without him.
I've never personally experienced this. The most I've experienced is somebody who broke and stole stuff right before leaving. So what can we do about it?
Well, since you asked, let's go over some of the differences.
Servers are complex machines that generate a lot of heat when they work! A lot. Once in a while you might find your server room smelling funny. Don't panic! We gotchu! Here's what you do.
In 1998, Windows-98 used to run with as little as 16MB of RAM, whereas today even a lighter distro such as Xubuntu consumes at least 250MB at rest. So what's going on here? Rapid expansion of operating and storage technology, that's what.
An interesting question that boils down to how both operating systems handle file access. Read on.