Kingston Technology’s Post

When quality meets affordability, amazing things happen with IBM Storage FlashSystem.Learn how you can find the perfect balance of price and quality: #ibmstorage #storagesolutions #storagesystems #datastorage

The IM7200 is EOS this month. But before you replace, read our comprehensive post that compares newer models to alternative options, with a complete list of migration SKUs to help you get started. Check it out here https://hubs.li/Q021lND_0 #serialconsole

hot take: a single drive is the same reliability as a mirrored pair and a waste of money. For the k8s people, Mirroring (or RAID1 if you like) is writing data to two disks so that they remain identical at the block level. Generally speaking, in our industry, we like to do mirrored OS drives to reduce the maintenance costs of bringing a server back online (a handful of minutes instead of a multi-hour outage). Drives come in two flavors: spinning and SSD. Spinning disk lifetimes are statistically based due to all the moving parts, etc. SSDs are measured in bytes written because that is what damages the mosfet's substrate. For OS drives, where performance isn't a question, spinning drives make a ton of sense. Mirroring spinning disks isn't measured in writes, so things like logs, temp files, ZFS scrubs, and compiling things don't take a toll on them (as much). Most of the time, it's total time in operation and assembly batch that plays the more critical factor. Meaning that the longer the server is online, the more likely you are to experience a spinning disk failure. SSDs don't like writes despite being really fast at them. An SSD's life isn't determined by time online but by how many bytes you've written. Logging can destroy your SSDs in production, especially when someone accidentally leaves debug logging on (yeah, it happens once in a while). Regardless of the technology, using only two drives is dumb. Both mediums have equivocal death patterns. When one drive dies, the other is usually not far behind unless it's an early failure like a bad disk/firmware. When your mirror fails over, it's not all okay. You didn't save yourself any money on maintenance. The urgency exists now, and you need to dispatch people to swap out the bad disk and let it rebuild. But if you don't replace the other disk, then you will just end up dispatching only a few weeks later for the same thing. You saved no money and doubled your costs. You took a double maintenance, and hopefully, it was agnostic to your customers. Hear me out. The sane approach that I haven't seen anyone else saying is that you should use 3 drives if you really want to save money and have ease of mind. Two drives in a mirror, one as a warm spare. It's not on the cage floor, it has to be already in the server. When a disk dies, you have an instant rebuild. No downtime, and you saved one maintenance and remote-hands ticket. Now you can decide how much urgency there is and maybe do multiple servers in the same maintenance. The important part here is that you know the drive is online, there is no reboot downtime, and that it should have plenty of life left, especially an SSD whose lifetime is more predictable. Two options: design around servers being more disposable or run 2+1 drives. If you run only a mirrored pair, you might as well run a single disk to recoup your inevitable technical debt.

How Much Does Seagate Charge For Data Recovery? Should you be wondering about the pricing of Seagate’s data recovery, specifically their lab-based service, keep in mind that multiple factors could influence the final cost. The device type you own, the duration needed to fix the problem, and the cost of replacing parts for your high-quality hard drive all<span class="excerpt-hellip"> […]</span> https://lnkd.in/eDfTa5Np

Can your storage alert you to cyber attacks in under a minute? IBM FlashCore Modules Gen4 (FCM4) can…

If you take cyber resiliency as seriously as IBM, read this brief piece from the instructional mind of Barry Whyte about the incredible announcement we made today. Denis Kennelly, Sam Werner, Jim Comstock Michael Flynt, Scott Baker, Ian Shave, Jeff Barber, Elisa Ortiz Fava, Gail G. Randy Daniel Andrew Bishop Douglas O'Flaherty Marty Hillman Rodney Araujo Cecilia Luque Karen Hsu Jessica Johnson Wolfgang Kugler David Chancellor-Maddison Sara Krumrei Kim Theng Lim Tohru Sumiyoshi Ivo Koerner #IBM, #IBMStorage, #IBMFlashSystem, #IBMpartners, #CyberStorage, #FlashCoreModule

Exciting news from IBM Storage! IBM FlashSystems with FCM4s can now detect data corruption events, including those caused by ransomware, in under a minute. #ibm #ibmstorage

Achieve cyber-resilient data storage for all through the unified IBM Storage FlashSystem, offering a cost-effective storage array without compromising performance. https://hubs.ly/Q02lR04J0

Can your storage alert you to cyber attacks in under a minute? IBM FlashCore Modules Gen4 (FCM4) can…

Businesses, now more than ever, need to be determined to protect their business from #cybersecuritythreats . It's not just about having strong #cybersecurity, but also having a solid #dataresilience plan in place for when (not if) an attack happens. With this latest technology from #ibm you can find threats in your data in less than a minute. I highly recommend looking into this topic and taking necessary measures to ensure your business is cyber resilient. Let's stay one step ahead of those cyber criminals! #cyberresilience #cybersecurity #stayprotected #cyberresilience #cyberrecovery David Chancellor-Maddison, Thomas Harrer, Joshua Lewis, Andrew Walls, Scott Baker, Elisa Ortiz Fava, Brian Sherman, Ivo Koerner, Kelly Robinson, Gonzalo de la Hoz, Jack Wilkins, Stan Wilkins, Justin Joanknecht, Jens Heitmann, Suvi-Maria Saarilehto, Alistair Symon, Sam Werner, Denis Kennelly, Alison Say, Nazeer Parak, Loay Tabbaa, Louise Gunsjö♦️, Frank Theisen, Charbel Antonios, Saumil Shah, Chris Saul, Wolfgang Kugler, Karen Hsu, Jessica Johnson, Jude Lancaster, CISSP, CCSP, Christopher Vollmar, Ana Picazo, Ana Joy Bellosillo, Stacie Mason, Kelli Millette