diff --git a/content/docs/object-storage-s3/meta.json b/content/docs/object-storage-s3/meta.json
index b4966bea..7a07d892 100644
--- a/content/docs/object-storage-s3/meta.json
+++ b/content/docs/object-storage-s3/meta.json
@@ -15,6 +15,7 @@
     "s5cmd",
     "boto3",
     "s3-features",
-    "veeam-backup"
+    "veeam-backup",
+    "synology"
   ]
 }
diff --git a/content/docs/object-storage-s3/synology.mdx b/content/docs/object-storage-s3/synology.mdx
new file mode 100644
index 00000000..ad38c0fe
--- /dev/null
+++ b/content/docs/object-storage-s3/synology.mdx
@@ -0,0 +1,52 @@
+---
+title: Synology Backup to S3
+---
+
+To backup data from a **Synology file server** to the **CESNET S3 storage**, please make sure you know the `endpoint address` (like `s3.cl4.du.cesnet.cz`) and have the `access key` and the `secret key` avilable.
+
+Open Synology web interface and log in. Open *Package Center* and run *Hyper Backup*. If *Hyper Backup* is not installed, install it here.
+
+![s3client](/img/data-care/synology/syn01.png)
+
+In Hyper Backup window, click the `+` button to start configuring a new automatic backup task.
+
+![s3client](/img/data-care/synology/syn02.png)
+
+Select an area of data you want to back up - start with *Folders and Packages* if you are not sure; click `Next`.
+
+![s3client](/img/data-care/synology/syn03.png)
+
+Select `S3 Storage` from the list.
+
+![s3client](/img/data-care/synology/syn04.png)
+
+Select `Custom Server URL` as *S3 Server* and complete the details about the backup target - `endpoint address` to *Server address*, `access key` as *Access Key*, and `secret key` as *Secret Key*. Choose `v4` as *Signature Version* and `Path Style` as *Request Style*. Select an existing bucket or create a new one. Enter the name of a directory in the selected bucket where backups will be stored.
+
+![s3client](/img/data-care/synology/syn05.png)
+
+Select what to backup.
+
+![s3client](/img/data-care/synology/syn06.png)
+
+Set details of the backup parameters and scheduling. You can enable a client-side encryption here; please **record the encryption password** as tha data cannot be recovered if the password is lost.
+
+![s3client](/img/data-care/synology/syn07.png)
+
+Configure backup rotation (select, how many old backups are kept until the oldest one is deleted).
+
+![s3client](/img/data-care/synology/syn08.png)
+
+Check the summary information and confirm the setup by clicking `Done`.
+
+![s3client](/img/data-care/synology/syn09.png)
+
+The home page of the Hyper Backup program shloud now contain the backup setup you just configured. The program will run the configured backup as scheduled during the setup process; to run an immediate backup or to test the functionality click the `Backup Now` button.
+
+![s3client](/img/data-care/synology/syn10.png)
+
+To check the presence of the backup, use an other [S3 client](s3-clients) to display the contents of the selected bucket; you should see a *directory-name*.hbk/ folder containing a set of folders and files. **Do not modify these files directly**; to keep the backup consistent, they can only be manipulated by the Synology *Hyper Backup* program.
+
+
+
+
+
diff --git a/public/img/data-care/synology/syn01.png b/public/img/data-care/synology/syn01.png
new file mode 100644
index 00000000..d9fd7204
Binary files /dev/null and b/public/img/data-care/synology/syn01.png differ
diff --git a/public/img/data-care/synology/syn02.png b/public/img/data-care/synology/syn02.png
new file mode 100644
index 00000000..813b9691
Binary files /dev/null and b/public/img/data-care/synology/syn02.png differ
diff --git a/public/img/data-care/synology/syn03.png b/public/img/data-care/synology/syn03.png
new file mode 100644
index 00000000..17fafaf0
Binary files /dev/null and b/public/img/data-care/synology/syn03.png differ
diff --git a/public/img/data-care/synology/syn04.png b/public/img/data-care/synology/syn04.png
new file mode 100644
index 00000000..9b49d12f
Binary files /dev/null and b/public/img/data-care/synology/syn04.png differ
diff --git a/public/img/data-care/synology/syn05.png b/public/img/data-care/synology/syn05.png
new file mode 100644
index 00000000..725806ce
Binary files /dev/null and b/public/img/data-care/synology/syn05.png differ
diff --git a/public/img/data-care/synology/syn06.png b/public/img/data-care/synology/syn06.png
new file mode 100644
index 00000000..80de2cbe
Binary files /dev/null and b/public/img/data-care/synology/syn06.png differ
diff --git a/public/img/data-care/synology/syn07.png b/public/img/data-care/synology/syn07.png
new file mode 100644
index 00000000..7e810fad
Binary files /dev/null and b/public/img/data-care/synology/syn07.png differ
diff --git a/public/img/data-care/synology/syn08.png b/public/img/data-care/synology/syn08.png
new file mode 100644
index 00000000..9e5cc5fc
Binary files /dev/null and b/public/img/data-care/synology/syn08.png differ
diff --git a/public/img/data-care/synology/syn09.png b/public/img/data-care/synology/syn09.png
new file mode 100644
index 00000000..b20f23b5
Binary files /dev/null and b/public/img/data-care/synology/syn09.png differ
diff --git a/public/img/data-care/synology/syn10.png b/public/img/data-care/synology/syn10.png
new file mode 100644
index 00000000..f3d718fb
Binary files /dev/null and b/public/img/data-care/synology/syn10.png differ