We are using Veeam 8 to replicate VMware VMs to a DR site.
The SQL DBA has suggested we exclude TEMPDB on SQL VMs as this is recreated when SQL server starts and it is responsible for a large change rate.
The suggestion is to house TEMPDB on its own Windows Volume, then either exclude that volume within advanced settings in the replication job, or create that volume (disk) as VMware independent, so Veeam skips over it.
The issue is that the Replicated SQL Server at the DR site needs to have that volume presented, so that on boot it will auto-create TEMPDB.
How do we exclude the data of TEMPDB for replications, whilst retaining the disk structure to the DR VM?
We're thinking of running a full replication so Veeam replicates the new volume one time, then changing it to independent disk so from that point onward Veeam skips it over (but hopefully the disk is then known and just hold old TEMPDB data)