When and Image is captured multiple times, does it overwrite the previous capture? Or is there a way to access captures from different dates?
-
I’ve been tasked with setting up nightly image captures for a simple backup of user machines. I know, not a very practical or clean solution, but the decision wasn’t up to me.
When I capture an image, then capture again, is there a way to go back to a previous capture? Here’s the scenario I’m thinking of: A user gets a virus on their machine, but it goes unnoticed for a day or two. In that case, a capture would’ve been done overnight that created an image with a virus. In that case, I’d like to grab a capture from a few days prior. Is this possible with certain config settings? I’d be curious to see what the capabilities are for something like this. Storage space isn’t a concern, as our customer already has an entire host dedicated to FOG.
-
@yeet said in When and Image is captured multiple times, does it overwrite the previous capture? Or is there a way to access captures from different dates?:
When I capture an image, then capture again, is there a way to go back to a previous capture?
No, unless you use another software to grab daily backups of your FOG image store.
-
@sebastian-roth Would I just need to back up the /images folder, or are there other components that would need backing up as well?
-
@yeet said in When and Image is captured multiple times, does it overwrite the previous capture? Or is there a way to access captures from different dates?:
Would I just need to back up the /images folder, or are there other components that would need backing up as well?
Backing up /images is enough for what you want to achieve. BUT keep in mind that you keep track of image setting changes as well. So if you need to go back to an older image you can switch back to an older image setting as well. Those settings are not changed often and so backing those up alongside is probably too much (useless) effort.
-
@yeet TBH I would not use fog for this. There are better/cheaper solutions out there, specifically Veeam Backup Agent (free). You can have it take nightly backups to where you can do a bare metal restore if the system fails. You can setup a retention period for each backup (i.e. 14 days before rewriting the oldest backup).
The target of your veeam backup can be a nas, san, another CIFS based computer, or a Veeam B&R server. I use the Veeam backup agent at home for my windows and linux computers backing up to a Synology NAS. Works perfect.
-
We have an “easy” solution for this. We are using a NAS (a Syno in our case) to store the images, and we enabled the recycle bin. When the image is overwritten by FOG, the old one goes in to the recycle bin of the Syno (#recycle). Depending on the filestore size(we have around 32TB), number of hosts, size of the images and the size of the recycle bin, you can have the “history” for a few days.
The images are renamed in the #recycle of the Syno(e.g. d1p4_1.img or d1p4_5.img) and if you need an older image, you just copy it back, and rename it.(e.g. d1p4.img )
We can go back in this way, for 5-6 copies, in your case it would be 5-6 days.
I hope it helps.
