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 recommendations 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 recommendations veeam backup repository recommendations](https://www.running-system.com/wp-content/uploads/2019/05/BCJ-from-BCJ-veeam-1024x362.jpg)
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.
![veeam backup repository recommendations veeam backup repository recommendations](https://www.vbrain.info/wp-content/uploads/2017/08/migrate_repository_02.jpg)
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 ) Another trick can be setting a database log file drive to independent to prevent it being snapshotted and cutting down on redos.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. To keep backup job times lower if there’s many disks I can run jobs with just one disk added each subsequent run to ensure the host can clear down the logs before they’ve grown too large. If I hit a fringe case where most of the above isn’t applicable then I get out the bag of tricks. Large VMs with little data change tend to be the ones on slower storage unless they’re transactional, so snapshots won’t grow as large in size, so it becomes more a conversation of ensuring the repository can commit data at a reasonable pace to keep snapshot time down.
![veeam backup repository recommendations veeam backup repository recommendations](https://reboote.weebly.com/uploads/2/1/3/2/21322080/493316_orig.jpg)
I prefer not to have to keep amending jobs. When it’s a large VM and the storage snapshot option is available I’d tend to use it for the initial backup if a maintenance window isn’t available to accept subpar performance. Or someone writing a SQL backup file every hour of a low changing database.
Veeam backup repository recommendations windows#
If there’s high data change I’d first ask the question of is it necessary data change? I’ve seen too many large CBT deltas due to Windows Deduplication enabled on a file server as an example. If it was highly transactional I’d be looking to leverage storage snapshots for backups where possible as this will be the best prevention for longer stuns. To provide some examples of what I’d be recommending: Can we use storage snapshots? What access modes can we use? Direct SAN Access? Hot-Add? What speed will our access mode be?įinally I’d look at the speed of the repository and the connection path between proxy and repository, is the primary backup on-site or offsite? What connectivity speed is between them? Once we know this then we need to know the connection options available.