Hello, we are currently testing out Veeam Availability Suite and have ran into a few issues and would like some information about them:
1. What is the correct way to restore a full Exchange Mailbox Database, currently we have to restore it via a file restore?
2. After restoring from an incremental SQL backup the database gets excluded from the transaction log backups, the only way to get it protected again is to perform an incremental backup, is this the correct way?
1. If you need to restore the database file, then FLR wizard is a way to go. For application item restores you can use Veeam Explorer for Exchange > Restore Scenarios
2. Yes, that would the correct way to do that. Transaction logs can be backed up if Veeam backup have an image backup of the database, "knows" its latest state. In your case it is changed after restore, so either incremental or full job pass is needed.
When backing up to tape (Incremental M-F, full on Sunday) how does Veeam handle the restore? I'm expecting something like having to restore the full backup to disk and then incremental up to the day I want to restore to. Any info on this would be great
We would like to run Exchange backups hourly from 9AM to 6PM, but we also want out full backup to be run out of hours at 11PM on Saturday, Is this possible?
You can try to use backup window options to block specific time, so that you job doesn't run. See periodic schedule options and backup window configuration > Define Job Schedule
We have a job that backs up 6 servers that sit on the same host, Hyper-V reports that 4 of them are backing up at the same time and that is hammering our Hyper-V performance, any way to reduce this to 2 at a time? We have a 2 server limit on our Backup Repositories.
Yes, you can do that, just set concurrent tasks limit on the on-proxy server (in your case it will be Hyper-V server itself) if you want to reduce the amount of VMs processed at the same time.
We currently use automatic selection on the jobs for picking the guest interaction proxy, if we add our two Hyper-V hosts to the Backup Proxies section will the concurrent task rule still be applied if we keep it as automatic?