This weekend I noticed that my FreeNAS box (named Soteria) was getting filled up. It didn’t take me long to figure out what was happening: Time Machine was filling up with changes made to my VMs. Each time I would open up a VM, it would make small changes and so the entire VM storage file would need to be uploaded via Time Machine when I got home.
At over 10 GB a crack, it doesn’t take long to fill up 750 GB of space (especially when Laura’s hard drive is filling up as well with images).
So I was left with what I should do to alleviate the problem and came up with the quickest, most barbaric one possible: remove the current ZFS dataset and set up a new one. It was not quite as easy as I thought.
Removing the dataset from ZFS through the FreeNAS web GUI didn’t work, so I updated to the latest released beta for FreeNAS 8.2.0 and tried again. Success was close at hand. I created another dataset and thought I had everything setup until Time Machine failed on the first attempted backup.
Rule of the day? Don’t forget to to set up your backup user as the owner of the dataset you are going to be using.
After that small change everything worked wonderfully.
While this is only a temporary solution, it worked for now. I have Time Machine working like usual and should buy me enough time to gather together some more storage space so that I can push the entire system over 2 TB total and then I’ll make the following changes:
- a separate ZFS dataset and user for each device
- MOAR RAM
- switch to the 64-bit installation (this really goes along with the prior one)
Everything else should be just fine, but the RAM is one of the areas I would really like to bump up along with (obviously) the disk storage. With 2 TB drives now sitting around $120/drive, things are looking better.