February-4th-2022, 06:20 PM
Well supposing the netPI image is a constant thing, the device is well configured and operating as it should ... then
a. indeed the TPI device supports the socalled backup function which is saving all the relevant data on the SD card inclusive the loaded docker containers to a single file. This can be stored aside and be used with the USB recovered device to restore all the previous settings and data. But it needs two steps the customer needs to be familiar with inclusive finding a properly working USB stick that USB recovery works with. A risky thing.
b. another way which I would prefer is to backup the whole SD card image manually. This needs to
* unscrew the 4 housings screws
* slight up the upper housing part to get it removed
* push the SD card to get it thrown out
* put it in external an SD card reader,
* get an 1:1 image copy of the 8/32GByte image using Win32DiskImager
* put back the SD Card
* shift the housing parts together
* screw the 4 back to their place
you can do all this without losing any guarantee. And then I personally would deliver a separate SD card containing the 1:1 SD card image copy to the customer along with the device. Then he is able to exchange later the "broken" SD card with the previously well prepared card in 5 minutes just in case and gets his application back to running state nearly immediately. The replaced card he can use by the way again to overwrite it with the image copy again to have it well prepared for any next incoming problem.
c. Since mostly all the knowledge/function lies in the Docker containers themselves you can save each Docker container separately as single file. But a recovery needs someone who reloads all the container back into the device after it was USB recovered inclusive all the set container parameters. I feel this is the most complicated process and not feasible for a customer to do.
Thx
Armin
a. indeed the TPI device supports the socalled backup function which is saving all the relevant data on the SD card inclusive the loaded docker containers to a single file. This can be stored aside and be used with the USB recovered device to restore all the previous settings and data. But it needs two steps the customer needs to be familiar with inclusive finding a properly working USB stick that USB recovery works with. A risky thing.
b. another way which I would prefer is to backup the whole SD card image manually. This needs to
* unscrew the 4 housings screws
* slight up the upper housing part to get it removed
* push the SD card to get it thrown out
* put it in external an SD card reader,
* get an 1:1 image copy of the 8/32GByte image using Win32DiskImager
* put back the SD Card
* shift the housing parts together
* screw the 4 back to their place
you can do all this without losing any guarantee. And then I personally would deliver a separate SD card containing the 1:1 SD card image copy to the customer along with the device. Then he is able to exchange later the "broken" SD card with the previously well prepared card in 5 minutes just in case and gets his application back to running state nearly immediately. The replaced card he can use by the way again to overwrite it with the image copy again to have it well prepared for any next incoming problem.
c. Since mostly all the knowledge/function lies in the Docker containers themselves you can save each Docker container separately as single file. But a recovery needs someone who reloads all the container back into the device after it was USB recovered inclusive all the set container parameters. I feel this is the most complicated process and not feasible for a customer to do.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
