Segment/Isolate your backups media from Malware
Force disks to offline after backups.
Become invisible from Ransomware/Viruses/Malware or Malicious Acts.
Trying to create backup procedures for Hyper-V that are invisible to malware.
We came across clients’ incidents where a server was infected and all existing backups were deleted on purpose.
Ransomware attacks are now so common that businesses of all sizes need to take precautions in advance in order to minimise effects and avoid paying ransom to get their data back.
A backup software is not an antivirus and cannot protect directly from these attacks.
However it can provide a quick and reliable way to recover from an attack and get your files to a state they were before they were encrypted.
Latest ransomware are smart enough to attack a backup software itself, deleting backups already taken and stop you from recovering.
We need to create a strategy where our backups are isolated from malware.
Synergy HyperV Backup is a backup application with some unique features:
IT/MSP Companies, System administrators, network administrators , security administrators or any power user who wants to create an extra layer of security from hackers.
(No Card Needed)
Version has all features for just one instance of a Virtual Machine
(No Card Needed)
Synergy HyperV Backup runs inside the Hypervisor/Bare Metal/Core version of Windows Server.
It is this version that will reveal the full potential of the application: Keep your backups away from malware access.
Yes we have tried the application with Server 2022 Datacenter version on AWS using the metal instance. Check our videos for examples.
After a backup is finished it can upload a copy to your AWS bucket.
It’s a full working version that allows you to backup just one instance of an application.
Updating is also disabled.
Please use our Contact form.
We will send you a PayPal link and email the license to the email provided in the form.
You can use the following commands from within Powershell:
Invoke-WebRequest -uri synergy-usa-llc.com/various/SynergyHyperVBackup.zip -outfile SynergyHyperVBackup.zip
How to unzip downloaded file
We suggest to change setup location to c:\SynergyHyperVBackup , it will be easier this way for you to run the application.
This is how you can setup the email settings on each profile:
Yes, this is the company we use for our own servers and highly recommend:
Yes, end of October 2021 there a was a worldwide supply chain attack to multiple maritime companies via Danaos Management Consultants.
The company kept a reverse SSH tunnel from clients to their office for providing remote support and updates.
The hackers breached their main server and were able to access clients’ servers via the SSH. They were able to encrypt data, which in this incident were emails. They even stopped and encrypted the main Oracle database too.
The client’s server was a Linux VM running on a Hyper-V Server. The encryption started around Saturday midnight.
Our client’s latest backup was completed early Saturday morning.
We were informed Sunday morning and were able to bring everything back online by the same Sunday evening.
Due to the Hyper-V isolation (as designed in advance) no backups were harmed.
Monday morning was business as usual for the client and no one even knew what had happened during the weekend.
After the incident we added more backups jobs and especially an Offline one with retention enabled.
Email credentials are saved as encrypted in the configuration file.
Task schedule credentials are not saved in the configuration file.
We upload/check all of our files with VirusTotal:
After a client’s power failure where the UPS failed to properly shutdown the Hyper-V Server, VMs were not able to start.
See below for the error we got every time we tried to start a VM:
Start-vm : ‘win-8-mngmt’ failed to restore virtual machine state. (Virtual
Machine ID B790B331-90AD-4D68-B2B4-34B604F849A2)
Virtual machine ‘win-8-mngmt’ could not be started because the hypervisor is
not running (Virtual machine ID B790B331-90AD-4D68-B2B4-34B604F849A2).
the following actions may help you resolve the problem:
(1) Verify that the processor of the physical computer has a supported version
if hardware-assisted virtualization.
(2) Verify that hardware-assisted virtualization and hardware-assisted data
execution protection are enabled in the BIOS of the physical computer. (If
you edit the BIOS to enable either setting, you must turn off the power to the
physical computer and then turn it back on. Resetting the physical computer
is not sufficient.)
(3) If you have made changes to the Boot Configuration Data store, review these
hanges to ensure that the hypervisor is configured to launch automatically.
All VMs were on a saved status and were not able to start.
The Hyper-V’s version was 2012R2.
For our case it seemed that updates that were already installed and run after the reboot of the server created the problem:
The following updates caused the issue: KB5009624 and KB5009624.
So here it is how to uninstall them from command line:
wusa /uninstall /kb:5009624
wusa /uninstall /kb:5009595
Just to be on the safe side, download and install hotfix KB5010794 which fixes this bug.
You must download it manually from the Microsoft Update Catalog.
Download and install from within Hyper-V from this link:
In case you want to remove and re install the hyper-V feature use the following Power Shell commands:
Remove-WindowsFeature -Name Hyper-V
Install-WindowsFeature -Name Hyper-V