From 7bfe0ab791c1087e8faf27ee39e7ad361467b9bf Mon Sep 17 00:00:00 2001 From: Nexus-Security Date: Fri, 12 Jul 2024 11:33:53 +0000 Subject: [PATCH] deploy: Nexus-Security/Stack@66a297f8168dbe324859e27cebcd76eb72b51cd5 --- .../index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/what-is-your-method-for-backing-up-your-hyper-v-virtual-machines/index.html b/what-is-your-method-for-backing-up-your-hyper-v-virtual-machines/index.html index 777fa73607b..ce8c72d1b7e 100644 --- a/what-is-your-method-for-backing-up-your-hyper-v-virtual-machines/index.html +++ b/what-is-your-method-for-backing-up-your-hyper-v-virtual-machines/index.html @@ -9,7 +9,7 @@ How do you ensure your Hyper-V virtual machines are backed up? You do back them up, right? I recently dedicated a day to improving my “data center infrastructure,” specifically focusing on my Hyper-V backups. For years, I relied on batch files and VBS scripts to save my VMs and then copied the VHDs to a file server. This system worked well for a while. However, after replacing my Windows file server with a Synology NAS, I stopped compressing my VHD files and started offsite backups.">