January 19, 2018 at 11:10 am
We have a SAN with a log drive and a data drive. The log drive is provisioned to store sequential data, mostly writes, whereas the data drive is for random read/writes.
We have created seperate .ndf file groups for historical data that never get updated and are rarely read. Does it make sense to store these on the log drive or the data drive?
Thanks.
January 19, 2018 at 12:08 pm
Do you know the RAID level of the "drives"? Since you are using a SAN, there's also the possibility that the log drive you see is really carved out of the same set of physical drives as others in the SAN, and it wouldn't matter then because all the operations would be random. If you actually do have dedicated physical disks for your log drive, definitely keep data off of them! If not, it would probably make sense to keep the historical data with other data anyway just for consistency and capacity planning.
January 19, 2018 at 1:20 pm
To quote our network guy:
"Transaction logs have heavy sequential write activity while database files have more random read/write activity and thus by setting the Nimble Performance Policy to match the function of the datastore we should optimize SAN access.."
So yeah, carved out of the same drive but with difference performance policies. Not sure if they actually do anything though.....
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply