M710q Tiny 1L Backup Server

[tjb_altf4]

A project server that I've been meaning to do for some time is a small backup server, able to be located seperately from my main rack.

I came across the M710q at local auctions and eventually picked one up for under AUD$100.

Out of the box it is well specced, with one m.2 slot and one 2.5" drive... but I really wanted 2x 2.5" so I could run a raid1 pool for backups.

 

Enter a slew of additional purchases, modifying a sata splitter, and a couple hours on the 3D printer to prototype a solution:

 

 

[tjb_altf4]

Final ingredient was small + thin sata cables, which came today!



Took the time while waiting to reprint drive carrier and riser/spacer in ASA black filament








Happily running on 6.12.4 at the moment


Looking forward to testing out subvolumes and snapshots plugin as part of this backup server journey 

Edited September 19 by tjb_altf4

[Rick Sanchez]

This looks great and it's similar to what I want to do.

I currently have a node 304 case, but, might sell it for something smaller

Sent from my Pixel 6 using Tapatalk

[denishay]

Several notes on my side.

 

First, the "cache". Why? Your array is made of SSDs, why have a separate, most probably slower SSD as cache? Unless you're rocking 10GB/s in that tiny box, any SSD, even a SATA one, will more than max a Gigabit connection (and a 2.5BGps one).

 

You mention a "backup" server, but it seems to be more a separate "test" server than a backup repository, is it? Or is it one that will be used as a target for backing up data?

 

Quick questions:

 

• Is the "cache" also a SATA SSD? If yes, I would probably have used that last SATA slot to get a larger raidz1 ZFS pool

• I don't see the main array anywhere in your screenshots. Did you just hide it, or did you find a way to NOT have a main array?

Edited September 19 by denishay

[tjb_altf4]

13 minutes ago, denishay said:

Several notes on my side.

 

First, the "cache". Why? Your array is made of SSDs, why have a separate, most probably slower SSD as cache? Unless you're rocking 10GB/s in that tiny box, any SSD, even a SATA one, will more than max a Gigabit connection (and a 2.5BGps one).

 

You mention a "backup" server, but it seems to be more a separate "test" server than a backup repository, is it? Or is it one that will be used as a target for backing up data?

 

Quick questions:

 

• Is the "cache" also a SATA SSD? If yes, I would probably have used that last SATA slot to get a larger raidz1 ZFS pool

• I don't see the main array anywhere in your screenshots. Did you just hide it, or did you find a way to NOT have a main array?

I don't mind being challenged on the setup, this was all whipped together over a few days, even though I wanted to do it for ages

 

The M.2 is a 250GB NVME that came with the unit from auction, its a freebie I wouldn't of bought for this but it'll get used for appdata etc for convenience + separation of roles, the pool name "cache" is the default first pool name and I've haven't sought fit to change it yet.  I was able to setup what I wanted out of Unraid in about 5min, but I'm not afraid to nuke and pave this to get the format right.

 

The targets for this server will be backups of vms, appdata, user docs, photos, music etc... basically all the important non-video media from my main servers.

A mirrored 4TB will be plenty for now, and its really just a +1 safeguard given existing data is already mirrored and/or parity protected on other respective servers.

Once first backup is done, I'm not expecting the backup deltas to use a lot of bandwidth... and if it does I won't notice anyway.

 

Main array is a spare thumbdrive, next release should remove the requirement for it to exist.

In release 6.12 you can customise the visible panels, I've simply hidden the array + parity panels (see below).