diff --git a/files/bashscripts/dockerserver/akanealw/crontab.bak b/files/bashscripts/dockerserver/akanealw/crontab.bak
new file mode 100644
index 0000000..c5051e6
--- /dev/null
+++ b/files/bashscripts/dockerserver/akanealw/crontab.bak
@@ -0,0 +1,24 @@
+# Edit this file to introduce tasks to be run by cron.
+# 
+# Each task to run has to be defined through a single line
+# indicating with different fields when the task will be run
+# and what command to run for the task
+# 
+# To define the time you can provide concrete values for
+# minute (m), hour (h), day of month (dom), month (mon),
+# and day of week (dow) or use '*' in these fields (for 'any').
+# 
+# Notice that tasks will be started based on the cron's system
+# daemon's notion of time and timezones.
+# 
+# Output of the crontab jobs (including errors) is sent through
+# email to the user the crontab file belongs to (unless redirected).
+# 
+# For example, you can run a backup of all your user accounts
+# at 5 a.m every week with:
+# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
+# 
+# For more information see the manual pages of crontab(5) and cron(8)
+# 
+# m h  dom mon dow   command
+0 12 * * * /home/akanealw/scripts/restart-gluetun-and-services.sh >> /home/akanealw/restart-gluetun-and-services.log
diff --git a/files/bashscripts/dockerserver/root/crontab.bak b/files/bashscripts/dockerserver/root/crontab.bak
new file mode 100644
index 0000000..d1c5aa5
--- /dev/null
+++ b/files/bashscripts/dockerserver/root/crontab.bak
@@ -0,0 +1,23 @@
+# Edit this file to introduce tasks to be run by cron.
+# 
+# Each task to run has to be defined through a single line
+# indicating with different fields when the task will be run
+# and what command to run for the task
+# 
+# To define the time you can provide concrete values for
+# minute (m), hour (h), day of month (dom), month (mon),
+# and day of week (dow) or use '*' in these fields (for 'any').
+# 
+# Notice that tasks will be started based on the cron's system
+# daemon's notion of time and timezones.
+# 
+# Output of the crontab jobs (including errors) is sent through
+# email to the user the crontab file belongs to (unless redirected).
+# 
+# For example, you can run a backup of all your user accounts
+# at 5 a.m every week with:
+# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
+# 
+# For more information see the manual pages of crontab(5) and cron(8)
+# 
+# m h  dom mon dow   command
diff --git a/files/bashscripts/fileserver/akanealw/backup-scripts-to-gitrepo.sh b/files/bashscripts/fileserver/akanealw/backup-scripts-to-gitrepo.sh
index d743c98..c65da9c 100755
--- a/files/bashscripts/fileserver/akanealw/backup-scripts-to-gitrepo.sh
+++ b/files/bashscripts/fileserver/akanealw/backup-scripts-to-gitrepo.sh
@@ -5,36 +5,42 @@ if ping -c 1 192.168.1.41 &> /dev/null
         # proxyserver
         ssh plexserver "crontab -l | tee /home/akanealw/scripts/crontab.bak \
         && sudo crontab -l | sudo tee /root/scripts/crontab.bak \
+        && rm /home/akanealw/scripts/debian-essentials.sh \
         && rsync -azvP /home/akanealw/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/proxyserver/akanealw/ \
         && sudo rsync -azvP /root/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/proxyserver/root/"
 
         # dockerserver
         ssh dockerserver "crontab -l | tee /home/akanealw/scripts/crontab.bak \
         && sudo crontab -l | sudo tee /root/scripts/crontab.bak \
+        && rm /home/akanealw/scripts/debian-essentials.sh \
         && rsync -azvP /home/akanealw/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/dockerserver/akanealw/ \
         && sudo rsync -azvP /root/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/dockerserver/root/"
 
         # plexserver
         ssh plexserver "crontab -l | tee /home/akanealw/scripts/crontab.bak \
         && sudo crontab -l | sudo tee /root/scripts/crontab.bak \
+        && rm /home/akanealw/scripts/debian-essentials.sh \
         && rsync -azvP /home/akanealw/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/plexserver/akanealw/ \
         && sudo rsync -azvP /root/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/plexserver/root/"
 
         # proxmox1
         ssh proxmox1 "crontab -l | tee /home/akanealw/scripts/crontab.bak \
         && sudo crontab -l | sudo tee /root/scripts/crontab.bak \
+        && rm /home/akanealw/scripts/debian-essentials.sh \
         && rsync -azvP /home/akanealw/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/proxmox1/akanealw/ \
         && sudo rsync -azvP /root/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/proxmox1/root/"
 
         # proxmox2
         ssh proxmox2 "crontab -l | tee /home/akanealw/scripts/crontab.bak \
         && sudo crontab -l | sudo tee /root/scripts/crontab.bak \
+        && rm /home/akanealw/scripts/debian-essentials.sh \
         && rsync -azvP /home/akanealw/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/proxmox2/akanealw/ \
         && sudo rsync -azvP /root/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/proxmox2/root/"
 
         # fileserver
         crontab -l | tee /home/akanealw/scripts/crontab.bak
         sudo crontab -l | sudo tee /root/scripts/crontab.bak
+        rm /home/akanealw/scripts/debian-essentials.sh
         rsync -azvP /home/akanealw/scripts/ /home/akanealw/gitrepos/fileserver/files/bashscripts/fileserver/akanealw/
         sudo rsync -azvP /root/scripts/ /home/akanealw/gitrepos/fileserver/files/bashscripts/fileserver/root/
 
diff --git a/files/bashscripts/fileserver/akanealw/plexserver.sh b/files/bashscripts/fileserver/akanealw/plexserver.sh
new file mode 100755
index 0000000..f06dedc
--- /dev/null
+++ b/files/bashscripts/fileserver/akanealw/plexserver.sh
@@ -0,0 +1,6 @@
+#!/bin/bash
+
+        ssh plexserver "crontab -l | tee /home/akanealw/scripts/crontab.bak \
+        && sudo crontab -l | sudo tee /root/scripts/crontab.bak \
+        && rsync -azvP /home/akanealw/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/proxyserver/akanealw/ \
+        && sudo rsync -azvP /root/scripts/ akanealw@fileserver:/home/akanealw/gitrepos/fileserver/files/bashscripts/proxyserver/root/"
diff --git a/files/bashscripts/plexserver/akanealw/crontab.bak b/files/bashscripts/plexserver/akanealw/crontab.bak
new file mode 100644
index 0000000..e69de29
diff --git a/files/bashscripts/plexserver/root/crontab.bak b/files/bashscripts/plexserver/root/crontab.bak
new file mode 100644
index 0000000..4f0bc1e
--- /dev/null
+++ b/files/bashscripts/plexserver/root/crontab.bak
@@ -0,0 +1,24 @@
+# Edit this file to introduce tasks to be run by cron.
+# 
+# Each task to run has to be defined through a single line
+# indicating with different fields when the task will be run
+# and what command to run for the task
+# 
+# To define the time you can provide concrete values for
+# minute (m), hour (h), day of month (dom), month (mon),
+# and day of week (dow) or use '*' in these fields (for 'any').
+# 
+# Notice that tasks will be started based on the cron's system
+# daemon's notion of time and timezones.
+# 
+# Output of the crontab jobs (including errors) is sent through
+# email to the user the crontab file belongs to (unless redirected).
+# 
+# For example, you can run a backup of all your user accounts
+# at 5 a.m every week with:
+# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
+# 
+# For more information see the manual pages of crontab(5) and cron(8)
+# 
+# m h  dom mon dow   command
+0 15 * * * /root/scripts/clean-plex-photo-cache.sh
diff --git a/files/bashscripts/proxmox1/akanealw/crontab.bak b/files/bashscripts/proxmox1/akanealw/crontab.bak
new file mode 100644
index 0000000..e69de29
diff --git a/files/bashscripts/proxmox1/root/crontab.bak b/files/bashscripts/proxmox1/root/crontab.bak
new file mode 100644
index 0000000..fbb5682
--- /dev/null
+++ b/files/bashscripts/proxmox1/root/crontab.bak
@@ -0,0 +1,25 @@
+# Edit this file to introduce tasks to be run by cron.
+# 
+# Each task to run has to be defined through a single line
+# indicating with different fields when the task will be run
+# and what command to run for the task
+# 
+# To define the time you can provide concrete values for
+# minute (m), hour (h), day of month (dom), month (mon),
+# and day of week (dow) or use '*' in these fields (for 'any').
+# 
+# Notice that tasks will be started based on the cron's system
+# daemon's notion of time and timezones.
+# 
+# Output of the crontab jobs (including errors) is sent through
+# email to the user the crontab file belongs to (unless redirected).
+# 
+# For example, you can run a backup of all your user accounts
+# at 5 a.m every week with:
+# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
+# 
+# For more information see the manual pages of crontab(5) and cron(8)
+# 
+# m h  dom mon dow   command
+@reboot /root/scripts/ping-before-starting-cts-vms.sh
+30 12 * * * /root/scripts/rsync-import-debian-ubuntu-cloud-images.sh
diff --git a/files/bashscripts/proxmox2/akanealw/crontab.bak b/files/bashscripts/proxmox2/akanealw/crontab.bak
new file mode 100644
index 0000000..1960c31
--- /dev/null
+++ b/files/bashscripts/proxmox2/akanealw/crontab.bak
@@ -0,0 +1,24 @@
+# Edit this file to introduce tasks to be run by cron.
+# 
+# Each task to run has to be defined through a single line
+# indicating with different fields when the task will be run
+# and what command to run for the task
+# 
+# To define the time you can provide concrete values for
+# minute (m), hour (h), day of month (dom), month (mon),
+# and day of week (dow) or use '*' in these fields (for 'any').
+# 
+# Notice that tasks will be started based on the cron's system
+# daemon's notion of time and timezones.
+# 
+# Output of the crontab jobs (including errors) is sent through
+# email to the user the crontab file belongs to (unless redirected).
+# 
+# For example, you can run a backup of all your user accounts
+# at 5 a.m every week with:
+# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
+# 
+# For more information see the manual pages of crontab(5) and cron(8)
+# 
+# m h  dom mon dow   command
+0 11 * * * /home/akanealw/scripts/restart-gluetun-and-services.sh
diff --git a/files/bashscripts/proxmox2/root/crontab.bak b/files/bashscripts/proxmox2/root/crontab.bak
new file mode 100644
index 0000000..0c7f951
--- /dev/null
+++ b/files/bashscripts/proxmox2/root/crontab.bak
@@ -0,0 +1,26 @@
+# Edit this file to introduce tasks to be run by cron.
+# 
+# Each task to run has to be defined through a single line
+# indicating with different fields when the task will be run
+# and what command to run for the task
+# 
+# To define the time you can provide concrete values for
+# minute (m), hour (h), day of month (dom), month (mon),
+# and day of week (dow) or use '*' in these fields (for 'any').
+# 
+# Notice that tasks will be started based on the cron's system
+# daemon's notion of time and timezones.
+# 
+# Output of the crontab jobs (including errors) is sent through
+# email to the user the crontab file belongs to (unless redirected).
+# 
+# For example, you can run a backup of all your user accounts
+# at 5 a.m every week with:
+# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
+# 
+# For more information see the manual pages of crontab(5) and cron(8)
+# 
+# m h  dom mon dow   command
+@reboot /root/scripts/ping-before-starting-cts-vms.sh
+0 12 * * * /root/scripts/download-import-debian-ubuntu-cloud-images.sh
+30 9 * * * /root/scripts/wake-proxmox1.sh