Backing up FULL configuration - Best practice?
Posted: 23 Jan 2014, 04:44
What is best practice to ensure no setup/parameter data is lost for whatever reason on a 1 node network
Obviously it takes a lot of effort to learn and set-up the CopperLan system and no-one wants to be in the awful position of staring from scratch without full restore capability.
I have seen talk whereby the whole system can be resurrected from any connected node on the network....fine.
But what if like a lot of new users, there is only one node and it dies?
Please describe a procedure for manually backing up and re-storing a one node system.
I would really hope an automatic backup system could be in place for a one node system, with the ability to select multiple locations where the backup could be replicated to.
Cheers
Obviously it takes a lot of effort to learn and set-up the CopperLan system and no-one wants to be in the awful position of staring from scratch without full restore capability.
I have seen talk whereby the whole system can be resurrected from any connected node on the network....fine.
But what if like a lot of new users, there is only one node and it dies?
Please describe a procedure for manually backing up and re-storing a one node system.
I would really hope an automatic backup system could be in place for a one node system, with the ability to select multiple locations where the backup could be replicated to.
Cheers