As the title infers, I 'inherited a nightmare'. In use: a Server 2012 R2 system on a terribly under-powered system that I've 'pushed' about as far as I can go.. and since there's NO interest in doing much for this hardware (unfortunately), I 'need' to do as much as I can "performance-wise" with this AMD . My thoughtwas: 'clone' the OS to an SSD (Samsung Evo 850) so it might 'feel' as though there's some 'gumption' to this system. As I think was mentioned in this forum on another post (which I read just as bit ago) my thought was to simply use Samsung Migration software to 'clone' to this Samsung SSD.. but before I make any presumptions about this, I figured it might be wise to post a question: Earlier, when I first got my mitts on this, because ALL the hard disks in this system were 'aging', as well as 'way too full', my very first efforts with this server was to install and create a 'storage pool', using 4 W/D 4TB Red drives (NAS class) so at least they have sufficient 'room to move' (Y'shoulda seen it before.. OMG..).. But how does this "intent to clone" possibly or potentially affect anything surrounding this storage pool? My thought was since this 'pool' is all controlled by the Server 2012 OS, simply cloning would be the fastest (and cheapest) means to kick it in the butt. But then it occurred to me that I'd better ask whether of not my presumption was accurate or if I was just fooling myself. Whaddya all think?
BTW: nothing else will change 'hardware-wise' OTHER THAN cloning to the SSD. And I suppose I could just "give it a go" because the original system will be undisturbed, but thought I'd defer to input, nonetheless....
BTW: nothing else will change 'hardware-wise' OTHER THAN cloning to the SSD. And I suppose I could just "give it a go" because the original system will be undisturbed, but thought I'd defer to input, nonetheless....
Last edited: