Been a lurker on and off for a few months and have had a go with the trial (it's great). I'm not actually looking to put into production yet as we haven't nailed down our new hardware setup. We're currently not virtualised and run a single server with multiple roles and old-school backup (Acronis).
We're looking to build our main server (fast storage, loads of RAM for production use) and a slower (less RAM and slower storage) 'limp server' in the same cabinet for replication/planned and unplanned failover. We can tolerate some downtime so we reckon replication can occur every 30 minutes or so (hence not opting for failover clusering/HA and the associated cost). A virtual drive on the limp server (possibly an iSCSI target, not sure yet) will also serve as our on-site backup and we'll have a NAS in a nearby building serving as our iSCSI offsite backup. We also have a third hyper-v host running just a single VM at present for our firewall, but in fairness it could host another couple of light-load VMs if necessary.
We have on-prem Exchange, AD, SQL, File Server and a few Linux VMs such as PBX system, Rocket.Chat etc.
All of our hardware is existing (we don't need to purchase any, or at least we don't think) and we're cobbling together what we can.
- Dual Xeon E5-2620 v4 with 128GB RAM
- Small SSD for host OS
- Dual mirrored SSDs for Exchange/High IOPS/random stuff
- Dual NVMe SSDs for cache on main storage array
- 4x mechanical drives for main file storage in RAID10, supplemented by cache above
- Dual Xeon E5-2620 v3 with 64GB RAM
- Storage almost same arrangement with possibly more SSD cached mechanical drives for backup and no SSD volume for exchange/SQL
- Slow Pentium Dual Core with SSD and 8GB DDR3, more or less desktop spec.
- Which physical machine would you put the backup server on? Production, limp or firewall?
- Would you run it in a VM?
- Same two questions for the database - with the backup server or on our SQL server?
- I gather VEEAM now backs up its config to the backup repos by default now, so a fresh install and settings import would be possible if the site was lost along with both the production machine and the limp machine.
The next one is more of a general query:
How do you guys use VEEAM with your archiving solution? We don't yet have anything for data archiving but would primarily like to get data off the costly storage and onto cheaper storage. We were looking at using the in-place archive for Exchange and having the archive database on mechanical storage to keep the primary database small. We have no idea where to go with it for files but are considering just using the backups. Any suggestions?
Thanks, and sorry for the lengthy post!