@John-Nicholson said in Adding a New Hyperconverged Cluster to Your Existing Network:
Of course, there is always the option to keep the old infrastructure indefinitely. This can be an excellent choice if the old infrastructure is purpose designed for a specific workload, such as perhaps VDI, and the HC cluster is designed for more general purpose needs (or vice versa, of course.) Using each tuned for specific use cases is absolutely viable, but does require knowledge of and support of two different clusters each of a unique type which creates IT overhead, but remains a very realistic option.
I'd argue dropping the skill sets to maintain legacy clusters is one of the main appeals to HCI. (I Personally want to FORGET about HBA Queue depth management, and FC Zoning). The problem of running old gear indefinably is the hardware support costs, environmental costs, and lack of support for new hypervisor versions and other things eventually catch up with you before you realize it.
Yes, it's technical debt for sure and in most cases, you want to head towards phasing it out. But whatever skill set you had for it, you will still have at the time that you begin replacing it and can slowly reduce the dependency and the skills related to it together.
