![]() ![]() Because of this, we couldn't boot the cloned VMs. We should have removed the VMs from the virtual flash pool before attempting to run from a cloned snapshot. We found that the outbreak occurred midday the previous Friday so we wanted to run from a snapshot on Friday morning. I called Nimble support back for a walk through in our first snapshot recovery. Sure enough, I found decryption instructions on our shared folders.ĭue to the infection's symptoms, we were quickly able to find the machine that caused the outbreak and quarantine the PC and the two servers affected. After a brief chat, the technician suggested I look for evidence of ransomware. On my way to the office I called the Nimble Storage support line to discuss the snapshot consolidation errors. The interesting thing is the VMs worked just fine, but all documents were corrupt. He rebooted the virtual servers, but the problems remained. He mentioned seeing VMware errors regarding snapshot consolidation. ![]() Monday morning: I got a text from my coworker - our file servers are down. To sum that up, we have Pernix using flash writes on the host and Nimble with flash reads on the SAN, giving us killer performance. (If you've never heard of Pernix, check them out.) We use Nimble Storage for our SAN and Veeam for our backups. ![]() If you'd be interested in writing a post on the subject of best practices, security, networking, backup, storage, virtualization, or MSPs for the series, PM Eric to get started.Įquipment check: We are a VMware house running HP Proliant D元60 G8 hosts, each with one 480GB Intel 730 series SSD for a virtual flash pool powered by Pernix Data. This is the 363rd entry in the Spotlight on IT series.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |