disturbedone
Vendor
Currently I have 1x 740GB database. This was setup by a contractor and I would like to split it for various reasons (management, backup etc).
These are virtual machines on VMware ESXi5.0
I currently have the following:
* 2 mailbox servers - MS1 & MS2, 2x CA servers - CA1 & CA2
* Database is called '2010 DAG cluster', database & log files stored in D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\2010* MS1 - C:\ (40GB, 17GB free), D:\ (1.8TB, 1.03TB free), E:\ (10GB, 3.85GB free)
* MS2 - C:\ (40GB, 12GB free), D:\ (2.0TB, 1.07TB free), E:\ (10GB, 3.85GB free)
* MS1/MS2 - C:\ (W2K8R2), D:\ (Exchange database & log files), E:\ (Page file)
* 1x DAG, witness directory (C:\DAG witness\ on CA1/CA2)
Firstly, why the log files were put on the same disk as the database I don't know. I think that is the first thing that should be sorted.
This is a school so I'm thinking of splitting the single database into the following:
* Staff
* Class of 2012
* Class of 2013
* Class of 2014
* etc
That way as each year of students leave the entire database can just be archived/deleted. It also allows for different policies eg size limits) to be applied to each database.
The database is currently 740GB. The log files are 500MB. CommVault Simpana does an incremental backup every hour to keep the log files to a minimum and reduce full backup times.
Questions:
1. Sorting the log file location out is what I think should be done first.
a. Create a new virtual disk and move them to it???? Need to unmount to do this???
b. Is having log files for each database on the same disk ok???? I would think so.
c. I'm thinking creating a single eg 5GB disk just for the log files. Big enough???
2. Leave D:\ as is. Moving 500MB of log files still leave ~1TB free on each server
a. I wouldn't think anything needs to be done to D:\. Am I missing something??
3. Creating new database seems straight forward - give it a name (eg 'Class of 2013), select server (MS1), select database location (D:\Program.....), select log location (new F:\Logs)
a. Any requirement for a new DAG or just let the single DAG manage it????
Any other thoughts/advice would be appreciated.
These are virtual machines on VMware ESXi5.0
I currently have the following:
* 2 mailbox servers - MS1 & MS2, 2x CA servers - CA1 & CA2
* Database is called '2010 DAG cluster', database & log files stored in D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\2010* MS1 - C:\ (40GB, 17GB free), D:\ (1.8TB, 1.03TB free), E:\ (10GB, 3.85GB free)
* MS2 - C:\ (40GB, 12GB free), D:\ (2.0TB, 1.07TB free), E:\ (10GB, 3.85GB free)
* MS1/MS2 - C:\ (W2K8R2), D:\ (Exchange database & log files), E:\ (Page file)
* 1x DAG, witness directory (C:\DAG witness\ on CA1/CA2)
Firstly, why the log files were put on the same disk as the database I don't know. I think that is the first thing that should be sorted.
This is a school so I'm thinking of splitting the single database into the following:
* Staff
* Class of 2012
* Class of 2013
* Class of 2014
* etc
That way as each year of students leave the entire database can just be archived/deleted. It also allows for different policies eg size limits) to be applied to each database.
The database is currently 740GB. The log files are 500MB. CommVault Simpana does an incremental backup every hour to keep the log files to a minimum and reduce full backup times.
Questions:
1. Sorting the log file location out is what I think should be done first.
a. Create a new virtual disk and move them to it???? Need to unmount to do this???
b. Is having log files for each database on the same disk ok???? I would think so.
c. I'm thinking creating a single eg 5GB disk just for the log files. Big enough???
2. Leave D:\ as is. Moving 500MB of log files still leave ~1TB free on each server
a. I wouldn't think anything needs to be done to D:\. Am I missing something??
3. Creating new database seems straight forward - give it a name (eg 'Class of 2013), select server (MS1), select database location (D:\Program.....), select log location (new F:\Logs)
a. Any requirement for a new DAG or just let the single DAG manage it????
Any other thoughts/advice would be appreciated.