Tuesday Tech Tip (Advanced) - Transitioning from Single Server to Storage Clustering

Every second Tuesday, we will be releasing a tech tip video that will give users information on various topics relating to our Storinator storage servers.
We are shifting gears with our bi-weekly tech tips from our usual longer-form technical videos to a combination of basic and technical tutorials.
Last video, we had Chris back on camera to talk about everything you need to know when deciding if (and when) you should be transitioning from a single server infrastructure to storage clustering. Now, you have made the decision to upgrade.
For this week, Brett is back to dig deeper into the aspects of carefully planning the transition from a single server infrastructure to a clustered storage. Brett will go deeper into assessing your physical environment, networking, and talk about the ability to use any existing hardware. Your workflow is going to change, so we want to prepare you for any questions about data migration and backing up while you make this transition.
Check out the first video on this topic: • Tuesday Tech Tip (Basi...
---
Chapters:
00:00 - Introduction
01:30 - Transitioning from Single Server to Storage Cluster
02:16 - Transitioning to Storage Clustering: Infrastructure Assessment
02:57 - Transitioning to Storage Clustering: Your Physical Environment
04:00 - Transitioning to Storage Clustering: Power and Electricity
06:00 - Transitioning to Storage Clustering: Using Existing IT Hardware & Networking
09:03 - Transitioning to Storage Clustering: Reusing Hardware & Components
10:50 - Transitioning to Storage Clustering: Data Migration & Backup
13:26 - Building a Storage Cluster with 45Drives
Visit our website: www.45drives.com/
Check out our GitHub: github.com/45drives
Read our Knowledgebase for technical articles: knowledgebase.45drives.com/
Check out our blog: www.45drives.com/blog
Ceph Clustering Buying Guide: www.45drives.com/solutions/di...
To enroll in our 2-day Clustered Storage Bootcamp: www.45drives.com/support/clus...
#45drives #storinator #stornado #storageserver #serverstorage #singleserver #storagenas #nasstorage #networkattachedstorage #proxmox #virtualization #cephstorage #storageclustering #virtualmachines #cephcluster #storagecluster #proxmox #ansible #nasstorage #prometheus #samba #cephfs #allflash #ssdstorage #ssdserver #allflashserver #allflashstorage #zfs #ransomwareprotection #linux #linuxtraining #nasstorage #selfencryptingdrives #jbod #justabunchofdisks #justabunchofdrives #serverexpansion #esxi #migratevirtualmachines #ssd #ssdtrim #sed #dataencryption #harddrives #harddrivehandling #seagate #westerndigital

[@Froggie92]

is the sound a little off for anyone else? sounds a lil quiet / muffled

[@Anonymous______________]

It's ashame Ceph is such a pain to setup and manage when compared to MooseFS, SeaweedFS, GlusterFS, BeeGFS or MinIO. One thing I have noticed is none of your videos demonstrate failure, recovery, or scaling with Ceph. I deployed several multi-peta scale clusters with Ceph and in nearly all cases, the erasure codes in conjunction with the crush algorithm has been abysmal in terms of dealing with drive failures, recovery, and actually scaling (i.e. adding new drives and PG's). Often times there would be issues with transient corruption of files or entire volumes. Even worse the developers removed things like ceph-deploy or offline deployment capabilities in favor of using containers. Which is complicated for environments that are air gapped and require an offline registry. Ceph has way too many constraints for any legitimate production environment. And I suspect the only reason your company utilizes it, is because it's one of the only truly free distributed file systems that supports erasure codes. Most of the others have some sort of restrictions (i.e. only stripe or replicate data without EC) or performance issues (eg. GlusterFS).