SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Hardware requirements for Conversion / Migration Server


Hardware requirements for Conversion / Migration Server

Author
Message
scottminer1205
scottminer1205
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 0
We perform data migrations for clients.

We intend to allocate drive space according to the following guidelines:

C:\ OS
D:\ SQL Binaries and system databases
E:\ User DB Data Files
F:\ User DB Log Files
G:\ Temp DB (Data and Log Files)
H:\ Backups

My question is, are there any formulas dependent upon the source data to allocate the drive space (as in number of GB). For instance, we have determined that we need to make approximately 4 backups throughout this process, so if we know the size of the original .bak file (say it's 100GB), we can multiply that by 4 to suggest that the H:\ Drive receive 400 GB of space.

Are there any recommendations or formulas for how to size the remaining drives? Your help is much appreciated.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (601K reputation)SSC Guru (601K reputation)SSC Guru (601K reputation)SSC Guru (601K reputation)SSC Guru (601K reputation)SSC Guru (601K reputation)SSC Guru (601K reputation)SSC Guru (601K reputation)

Group: Administrators
Points: 601992 Visits: 21095
Here's what I'd say.

For OS/binaries, I'd probably put 100GB there, maybe more for pagefile depending on RAM. Guess high, since the system drive is a pain to alter later.
For SQL binaries, this is minimal, and you might drop the pagefile here. System databases should be fairly small, though depending on history, perhaps these might be in the 10s of GB range.
For user dbs, you need to know/guess data size. I usually try to size the data file for data + 3mo growth, re-evaluating this every (or every other) month. You do need extra space since your data will grow. Hopefully you can estimate a data size for the next year+. I don't know how easy it is to add space. If it's easy (you're on a SAN of some sort), guess low. If not, guess high.
For log files, this is workload dependent. You will be completely guessing if you don't have any history here. It's not like a log file is 10% of data. It could be that, could be lower, could be much higher. This is tracking the record of changes, so more changes could b e lots of log, even if data isn't growing. As a gross (and likely bad) rule of thumb, I'd set my log file at 15-20% of data and then see where I am. Log backups give me an idea of the workload log I'm generating during each period. However, no matter what, I want extra space here. I also like to include placeholders on this drive (And data drive) to get me out of emergencies. https://voiceofthedba.com/2014/11/24/placeholders-for-emergencies/

For backups, you have the idea for fulls, but you might need logs, so ensure you account for this. More log backups is more files, but the aggregate log is roughly the same. If I generate 10GB of log records a day, this could be 4 2.5GB log backups every 4 hours or 20 500GB files if I backup 20 times a day. Again, remember data grows, so I need to account for the fact that 4 full backups today at 100GB might be 4 backups at 150GB in a year.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search