Hello. thanks for the time. I was wondering in regards to some information on database size in a DAG scenario and recoverability.
We have a 4 node DAG. 1 Active copy and 3 passive. 4 Databases. Database 2 current size is 600GB and only has 10% free on disk space. We dont want to add more space. We have created another database and have moved some users over there. Initially I thought we could recover some of the white space and so far from my understanding you cannot recover white space even if Exchange is doing an online defrag. The checkbox where it does it 24x7 ESE scanning... that does not recover white space. only thing that does is a offline defrag. However being in a DAG scenario that is not recommended because you are then re-writing the database ...pretty much creating a new one. You are probably better off creating a new database and moving users there. That leaves me with a few questions.
1. What is the recommended size of a database ( 2TB is the recommended limit)?
2. How does one recover from a dirty database shutdown in a DAG? obviously doing an ESEUTIL on a 600GB database will take about 5-6days (4-6GB per hour).
3. Is the white space left behind when you move a user used for new data? or is it just sitting because it has been written to already?
I apologize for the noob questions...but only way to learn is on the job.