ferroteam.blogg.se

Veeam backup repository
Veeam backup repository










veeam backup repository
  1. #VEEAM BACKUP REPOSITORY HOW TO#
  2. #VEEAM BACKUP REPOSITORY PLUS#

If you want a single chassis and you want an unusual set of options such as "lots of NVMe PLUS lots of SAS/SATA" then you will find your selection seriously constrained, maybe to as little as "no options." This just feels like you're not trying that hard to me, but I do this stuff professionally, so my opinion may be a bit slanted. You can use the 847 JBOD if you don't mind some drives being on the backside of the chassis, something I don't personally care for. It gives you 48 bays of NVMe and then really as many bays of 3.5" SATA/SAS as you'd like to add, easily up to 96, a little less easily beyond that. This is normally the way a larger NAS is built. That is, plan for failures.Īnyways, if you don't want to do that, and you're stuck in the "enterprise" mindset, you can go and pick any NVMe server like this Supermicro 2U 48 bay system and hook a SC846 up to it as a JBOD. One of them is to maintain spare capacity to cope with failures. There's a certain amount of wisdom there, and those of us who run far-flung networks typically embrace the best ideas. Eventually the entire installation is decommissioned and replaced. You put in racks of servers, and as they fail, they're just dead. It's easier and cheaper to just have stuff ready to go in place, spare disks and SSD's online, and even spare servers ready to spin up at a moment's notice. The petty "enterprise" use case where you merely don't want to shut down a server pales in comparison to those of us who operate networks flung across thousands of miles, where the logistical challenges of getting staff on-site are significant. Some of us who do this professionally spare SSD's at a 50% level in servers. Thanks for help and sorry for my broken english :) I have built two labs (one mentioned) so i want to give it a shot. I dont trust yet truenas for production environment so backup is really my first try.

#VEEAM BACKUP REPOSITORY HOW TO#

what performance to expect? Will it handle my reqs? What would you look after ? What would you change to have more reliability / perf stability ? How to tweak zfs for large files ? (one veeam backup is like 50G and incremental 5-10G, and hundreds of VMs) I think broadcom (lsi) hbas 9400 or 9500 series.Ĥx nvme 3-4TB drives like intel p1725b or intel p4610. Supermicro 847BE1C4-R1K23LPB 36x sata/sas with optional nvmeġx AMD EPYC™ Rome 7542 - 32 Core - 64 Threads - 2.9GHz - Boost 3.4GHz - 225W - 128MB CacheĢ6x10TB wd sas drives HC510 or smth like that in raid z3 (for sure 3 drives can die, i can manage new in about 1 week and change instantly as it arrives ) (veeam it will mount as datastore and you can run VM from there and do live vmotion to main cluster storage)

veeam backup repository

Special volume for instant recovery VM 10TB would satisfy. (Now i have about 120TB storage and buying another ) Backup is with one month retention.Ĥx nvme 4TB drives with 3dwpd idk if samsung or intel. (DD zero to file on disk went about 1.2GB/s -> i believe limitation of slog drive)ĭaily is written about 2-4T of new datas.ĥ00TB of deduplicated and compressed datas in final. With dataset i have copied about one third of datas from main repository (synology 10x10TB and 2x960G ssd 0 ) and i have reached dedup ratio about 2~3.ĭue to 10G network and secondary lab storage i could not pass to more than 700MB/s of write. (i had some spare so i needed to try to eliminate slow parts of spinners ) I came here because i have been looking for backup enterprise solutions and also tried truenas in lab which comes much cheaper with use of high end DC stuff than enterprise solution offers.Ģx960G s4510 for dedup.












Veeam backup repository