Apr 03, 2014 · At this time, the best low end primary backup storage for Veeam is Windows or Linux server with internal or direct attached (JBOD) storage. Below, I'm quoting a couple of weekly forum digest articles from earlier this year where I have discussed such backup targets in more details. #1.
04.06.2015 · Recommendations for backup storage, backup target. Post. by Gostev » Thu Apr 03, 2014 7:36 pm 5 people like this post. [UPDATE] This recommendation is still valid in 2021. In fact, V11 is so highly optimized for deployments on general-purpose servers that backup performance can exceed 11GB/s with a single box!
Figure 13: Recommended advanced backup repository storage options in Veeam console. CIFS/SMB shares require a mount (gateway) server for data movement to ...
Oct 19, 2017 · Primary storage is Compellent (DELL) SAN with 18 TB usable (Tier 1 and Tier 3 storage) running veeam 9.5 for onsite backups and replication. Need about 20 TB - 25 TB usable storage for backups. I use surebackup in veeam to test restoration. SAN is connected with iSCSI 10GB.
Jan 17, 2017 · For Backups i would alsways recommend Raid 10 (mirroring in storage spaces) since running vm's in a instant recovery settings is quite heavy on the storage. 80TB usable would require 160TB raw which would be 20 8TB drives and thus in a 24 bay enclosure / server this would give you 20 data and 4 spare drives. This could be done in a server of course.
13.09.2015 · Re: Recommendations for backup storage, backup target. You cannot switch between forever-incremental retention and GFS fulls, you can only add GFS fulls to the job. So in addition to your 15 full backups for GFS retention, you will have 1 'recent' full backup which is updated as often as the sync interval you set.
Backup target for veeam recommendations · Small Business (150 endpoints) · 3 ESXi hosts with VCenter (30 VMs) · Primary storage is Compellent (DELL) ...
18.10.2017 · Small Business (150 endpoints) 3 ESXi hosts with VCenter (30 VMs) Primary storage is Compellent (DELL) SAN with 18 TB usable (Tier 1 and Tier 3 storage) running veeam 9.5 for onsite backups and replication. Need about 20 TB - 25 TB usable storage for backups. I use surebackup in veeam to test restoration. SAN is connected with iSCSI 10GB.
In mid-sized or enterprise environments, the recommended amount of CPU for a repository is 1 core per concurrent job that processes data on a repository server.
Use the Veeam Size Estimator (VSE) to estimate capacity requirements · Use ReFS/XFS with block cloning to reduce space requirements for synthetic fulls and GFS ...
Cloudian HyperStore provides a proven on-prem backup target for Veeam Availability Suite or Veeam Backup for Office 365 (VBO). At 70% less cost than public ...
22.01.2019 · When using Veeam with a deduplicating storage system a best practice can be to have a non-duplicating storage system as the primary backup target for the most recent restore points and then use backup copy jobs for long term retention.
31.08.2016 · Typical I/O for Veeam is 256KB to 512KB, Windows Server 2012 defaults to 64KB, some arrays to 32KB. That’s a lot of wasted I/Os! A stripe of 128KB is recommended. Additionally, use as many drives as possible to avoid expansion at a later time (which divides performance across RAID arrays). In regards to the file system, NFTS is commonly used.
Jun 07, 2017 · In Veeam B&R console you just add the created server as a backup repository. So my 2 cents, Synology devices are great for storing your backups, but an old (er) server (not antique) will have more performance, and you can use that server as Data Mover and perhaps as Proxy in Network backup mode. Top. jamerson. Expert.
Aug 31, 2016 · Typical I/O for Veeam is 256KB to 512KB, Windows Server 2012 defaults to 64KB, some arrays to 32KB. That’s a lot of wasted I/Os! A stripe of 128KB is recommended. Additionally, use as many drives as possible to avoid expansion at a later time (which divides performance across RAID arrays). In regards to the file system, NFTS is commonly used.
Each of the following NAS backup components may consume up to 4 GB RAM per task (in case of deduplicating storage appliances, up to 8 GB RAM): backup repository, backup proxy, cache repository. Make sure you allocate enough memory resources for your installation.