Servers are often dedicated, meaning that they perform no other tasks besides their server tasks. On multiprocessing operating systems however, a single computer can execute several programs at once. A server in this case could refer to the program that is managing resources rather than the entire computer.

A server is a computer or a device on a network that manage network devices like network printer and other thing which is connected to the network.

“Dump backups are not ordinary file by file backups. The whole disk partition or file system is “dumped” to the backup medium as is. This means it is also necessary to restore the whole partition or file system at one go. The dump backup may be a disk image, which means it must be restored to a similar disk with same disk geometry and bad blocks in same places. Watch out for this.”

This is a description of dd, not dump. Dump scans the filesystem and intelligently chooses which files it needs to copy to the dump tape/file based on the last time and the level of this dump. When restoring files, you can ask restore to extract all files, or use it interactively and explore the files with cd and ls, and choose which ones you want to selectively restore. It restores to a new clean fs on any block device. It does not write to the raw block device when restoring, so it does not know or care about its size or bad blocks.

That is the only thing I know and why I expected to read. The same applies to almost everything in the article.

Some other commands available in Linux that may be of interest --
partimage
rdiff-backup
copydir (in pkg “mirrordir”)

I still think that dump/restore (through a process pipe) is quite useful
for migrating (populating) a new/local filesystem. Larry

Lets say we are backing up everything from / to /backup/

This gives you a full backup in /backup/1: rsync --archive --delete --links --progress --stats --verbose --exclude /backup/ / /backup/1

Then if you run: cp -al /backup/1 /backup/2
You’ll get a hardlinked copy of the full backup.

If you then run:
rsync --archive --delete --links --progress --stats --verbose --exclude /backup/ / /backup/2
Rsync will perform an incremental backup into 2, and only replace updated files. Thus, in /backup/1 you have the original backup, in /backup/2 you have the updated backup, and common files arn’t duplicated, so it’s nice and space efficient.

To restore, simply copy the most recent backup folder.

Of course, you might want more meaningful folders than /backup/1 and /backup/2. I use the date as the folder name myself.