Skip to main content

Backup by rsync command

The rsync command will create an exact copy of your information in a new location based on what has changed. It functions in a way to synchronize two directories or drives. The format for using rsync is:

command options what_to_backup where_to_backup

Note that if you only want files, not the directory container itself to be backed up the end the directory to be backed up with a “/”.

Compression
If you want to make your transfer smaller then use the -z option to compress your transfer.

rsync -avz /home/office /bk

Archive Mode -a
This will ensure that all symbolic links, devices, attributes, permissions, ownerships,etc. are preserved and transferred. This is the same as rlptgoD

Verbose -v
This will provide you with information.

Get Stats on Transfer –stats

rsync -avz --stats /home/office /var/bk

Here is an example of the stats you will have available.
Number of files: 324352
Number of files transferred: 70613
Total file size: 20610660916 bytes
Total transferred file size: 11504455981 bytes
Literal data: 11504455981 bytes
Matched data: 0 bytes
File list size: 17670110
File list generation time: 37.718 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 11527010557
Total bytes received: 1887490

sent 11527010557 bytes received 1887490 bytes 21212323.91 bytes/sec
total size is 20610660916 speedup is 1.79

File size Transferred
11.5 MB

Create an exclude file.
If you have a number of extensions you want to exclude, create a file and then tell rsync where the file is so that these extensions or patterns will not be transferred.

rsync -avz --exclude-from=/root/scripts/exclude --stats /home/office /bk

Here the file containing the patterns is listed by using –exclude-from= followed by a path to the file. As you can see the patterns in the file are not transferred.

home/office/exclude file contents, one pattern on each line.
*.rpm
*.bz2
*.tar

Comments

Popular posts from this blog

LINUX CONTAINERS

LINUX CONTAINERS What is Linux Container:  Linux containers have different approach than the Virtualization technology. Simply we can say this is OS level Virtualization, which means all containers run on top of one linux operating system.  We can start containers on a hardware running machine or inside of running virtual machine. Each container run's as a fully isolated operating sysem. In container virtualization rather than having an entire Operating System guest OS, containers isolate the guest but do not virtualize the hardware. For running containers one needs a patched kernel and user tools, the kernel provides process isolation and performs resource management. Thus all containers are running under the same kernel but they still have their own file system, processes, memory etc. Linux based containers mainly involved with two concepts: 1. Namespaces 2. Cgroups ( Controll Groups) There are total 6 types of Namespaces: 1. PID Na...

Canonical Kubernetes Platform

Recently,  Canonical has announce the release of the Canonical Kubernetes Platform version 1.32, a robust and user-friendly solution for seamless cluster creation and management. This platform is designed to simplify the deployment and maintenance of containerized workloads, making it an ideal choice for both developers and enterprises. Here are some of the attracting features of this Platform.  ZeroOps with Built-in Essentials:  The platform comes pre-configured with critical components such as networking, DNS, metrics server, local storage, ingress, gateway, and load balancer, enabling immediate productivity post-installation. Simplified Installation and Maintenance:   Leveraging snap packages, the installation process is straightforward, and automated patch upgrades enhance security without manual intervention. Effortless Scalability:  Adding new nodes is seamless, and achieving high availability requires minimal effort, ensuring your infrastructure sca...

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image download...