I too have been thinking about backup's recently.
I've never managed to put much thought into Reflex - and any time my system has ever "failed" it's been on account of some form of more fatal error that I've attributed to having a PC running 24/7 for many years in an environment that's not exactly dust free. (The only real issues I've had are that I've had a PSU fail, and a Motherboard fail for no good reason - which isn't bad for the years it's been running).
Given Cortex controls all critical lighting & heating etc in the house, my wife has an extremely low tolerance for outages and so I really need to get some form of backup in place that would allow me to fail-over without any meaningful down time.
I already take regular scheduled backups of the Cortex DB - but my fear is of a fatal failure that wouldn't allow me to get into Cortex to go through the motions of removing the licence key to then move it to a new install - as good as Karam and Viv are at replying to emails, this would inevitably take a degree of time to sort the licence out and give me a headache in the wife Department. Plus, any new machine that I sort out as a back-up cortex machine will now be a Windows 10 machine - and so I need to do some testing first.
So my plan is to have a setup where;
1) My current PC running Windows 7 will remain the "Primary" Cortex Machine running 24/7.
2) I'll build a new Windows 10 PC that will serve as a Secondary Cortex Machine which I'll only run once a month (or when I make significant change to the setup of the Primary machine to want to back this up).
I'll arrange some form of scheduling whereby the Cortex DB files are then automatically copied over to the secondary box each month so that in theory, if the Primary box fails, I can simply plug the Idranet interface USB cable into the secondary box and fire it up. All should then "just run" and allow me to then resolve the issues without real outage.
With this, do I need a second Cortex Licence?
I've never managed to put much thought into Reflex - and any time my system has ever "failed" it's been on account of some form of more fatal error that I've attributed to having a PC running 24/7 for many years in an environment that's not exactly dust free. (The only real issues I've had are that I've had a PSU fail, and a Motherboard fail for no good reason - which isn't bad for the years it's been running).
Given Cortex controls all critical lighting & heating etc in the house, my wife has an extremely low tolerance for outages and so I really need to get some form of backup in place that would allow me to fail-over without any meaningful down time.
I already take regular scheduled backups of the Cortex DB - but my fear is of a fatal failure that wouldn't allow me to get into Cortex to go through the motions of removing the licence key to then move it to a new install - as good as Karam and Viv are at replying to emails, this would inevitably take a degree of time to sort the licence out and give me a headache in the wife Department. Plus, any new machine that I sort out as a back-up cortex machine will now be a Windows 10 machine - and so I need to do some testing first.
So my plan is to have a setup where;
1) My current PC running Windows 7 will remain the "Primary" Cortex Machine running 24/7.
2) I'll build a new Windows 10 PC that will serve as a Secondary Cortex Machine which I'll only run once a month (or when I make significant change to the setup of the Primary machine to want to back this up).
I'll arrange some form of scheduling whereby the Cortex DB files are then automatically copied over to the secondary box each month so that in theory, if the Primary box fails, I can simply plug the Idranet interface USB cable into the secondary box and fire it up. All should then "just run" and allow me to then resolve the issues without real outage.
With this, do I need a second Cortex Licence?
Comment