Z-way backup strategy
-
@ArcherS said in Z-way backup strategy:
The downside of the .img strategy is that I need to power-off the Pi for a while when making the backup. However if the Z-way backup files work then the complete .img backup need not be done so very often.
//ArcherS
This is good information. However, no need to power-off the pi for a while as you can clone the SSD to a USB drive and then make the .img from the USB. Check out rpi-clone: https://github.com/billw2/rpi-clone . I just succesffully used this method yesterday.
-
There's an option on pi in Accessories - SD Card Copier which clones the sd card. Don't know if it works on SSDs. I rotate the cards (8gb) and keep one in the drawer just in case. After reading posts I wonder if I do need SSD now though.
-
@ArcherS said in Z-way backup strategy:
The downside of the .img strategy is that I need to power-off the Pi for a while when making the backup. However if the Z-way backup files work then the complete .img backup need not be done so very often.
//ArcherS
This is good information. However, no need to power-off the pi for a while as you can clone the SSD to a USB drive and then make the .img from the USB. Check out rpi-clone: https://github.com/billw2/rpi-clone . I just succesffully used this method yesterday.
@kfxo said in Z-way backup strategy:
@ArcherS said in Z-way backup strategy:
The downside of the .img strategy is that I need to power-off the Pi for a while when making the backup. However if the Z-way backup files work then the complete .img backup need not be done so very often.
//ArcherS
This is good information. However, no need to power-off the pi for a while as you can clone the SSD to a USB drive and then make the .img from the USB. Check out rpi-clone: https://github.com/billw2/rpi-clone . I just succesffully used this method yesterday.
Is it possible to copy the .img across a network?
-
@kfxo said in Z-way backup strategy:
@ArcherS said in Z-way backup strategy:
The downside of the .img strategy is that I need to power-off the Pi for a while when making the backup. However if the Z-way backup files work then the complete .img backup need not be done so very often.
//ArcherS
This is good information. However, no need to power-off the pi for a while as you can clone the SSD to a USB drive and then make the .img from the USB. Check out rpi-clone: https://github.com/billw2/rpi-clone . I just succesffully used this method yesterday.
Is it possible to copy the .img across a network?
@powisquare said in Z-way backup strategy:
Is it possible to copy the .img across a network?
I'm not really sure what you are asking. Once you create the .img you can do whatever you want with it, including copying it across your network to a different storage location.
-
If that can help others... I'm running all these in a VMs and using RaZboard or UZB with a raspberry just to send out the serial traffic over the network to the VM that run z-way!
So in my case, the only thing I need to do on rPI it's installing debian + sending the traffic to the VM!
Of course, all the VMs are doing backup! -
If that can help others... I'm running all these in a VMs and using RaZboard or UZB with a raspberry just to send out the serial traffic over the network to the VM that run z-way!
So in my case, the only thing I need to do on rPI it's installing debian + sending the traffic to the VM!
Of course, all the VMs are doing backup!@dest
I wondered about doing the same, but with 3 devices. RFXTRX, Zigate and UZB. Just wondering if the extra communication link could make a noticable latency? Gues not, as it's ethernet?My backup plan is to have a script that copies the config files of the systems to a network location. If total breakdown occurs, I run a docker-compose file on a reset system and copy in the config files. Should be an OK plan right?
-
@powisquare said in Z-way backup strategy:
Is it possible to copy the .img across a network?
I'm not really sure what you are asking. Once you create the .img you can do whatever you want with it, including copying it across your network to a different storage location.
@kfxo said in Z-way backup strategy:
@powisquare said in Z-way backup strategy:
Is it possible to copy the .img across a network?
I'm not really sure what you are asking. Once you create the .img you can do whatever you want with it, including copying it across your network to a different storage location.
I read somewhere the card is unmounted after writing a backup using the in-build card copier. This is to prevent two system images competing with each other. Would the rpi-clone .img have the same issue?
-
If that can help others... I'm running all these in a VMs and using RaZboard or UZB with a raspberry just to send out the serial traffic over the network to the VM that run z-way!
So in my case, the only thing I need to do on rPI it's installing debian + sending the traffic to the VM!
Of course, all the VMs are doing backup!@dest said in Z-way backup strategy:
If that can help others... I'm running all these in a VMs and using RaZboard or UZB with a raspberry just to send out the serial traffic over the network to the VM that run z-way!
So in my case, the only thing I need to do on rPI it's installing debian + sending the traffic to the VM!
Of course, all the VMs are doing backup!This sounds ideal. I have a rpi in the cupboard behind me doing the heavy lifting already. Is there a guide available to do this?
-
@kfxo said in Z-way backup strategy:
@powisquare said in Z-way backup strategy:
Is it possible to copy the .img across a network?
I'm not really sure what you are asking. Once you create the .img you can do whatever you want with it, including copying it across your network to a different storage location.
I read somewhere the card is unmounted after writing a backup using the in-build card copier. This is to prevent two system images competing with each other. Would the rpi-clone .img have the same issue?
@powisquare said in Z-way backup strategy:
@kfxo said in Z-way backup strategy:
@powisquare said in Z-way backup strategy:
Is it possible to copy the .img across a network?
I'm not really sure what you are asking. Once you create the .img you can do whatever you want with it, including copying it across your network to a different storage location.
I read somewhere the card is unmounted after writing a backup using the in-build card copier. This is to prevent two system images competing with each other. Would the rpi-clone .img have the same issue?
rpi-clone does not actually create an .img but instead clones the booted source disk, e.g. if you boot from a SD card, while running, you can clone the SD card to a USB drive so you can boot from the USB drive if the SD card fails.
-
Which one would that be out of the various methods on https://github.com/billw2/rpi-clone ?
-
As i understand it in layman's terms rpi-clone will backup an installation to a connected USB. This creates a bootable copy of the system. If one wanted to copy that copy across a network to safe storage would that be possible? Just been reading about dd comand https://robotzero.one/headless-pi-zero-backup-clone/ that creates an .img file of a running system. Is that the way to go to have something transferable? Without having a SSD is it safe enough to have just a USB plugged in and rpi-clone?
