I'm setting up a new SQL Server cluster, so my database storage is on a SAN. I'm on SQL Server 2014 Standard on Windows Server 2012R2. I have the block size for the data, log and tempdb LUNs set to 64k, per the recommendation in Brent Ozar's SQL Server Setup Checklist. My question: what should the block size be for my backup LUN?
Block size recommendation for SQL Server 2014 Standard backup LUN
1k Views Asked by Amandalina69 At
1
There are 1 best solutions below
Related Questions in SQL-SERVER
- having spring integration tcpserver to manage clients and send them messages
- psuedo TCP multicast with os.dup2() in python?
- Retrieve Data From EOC(Eithernet Over coxial) device
- Connecting a web client to a c++ server with TCP
- ECONNRESET on node.js RabbitMQ consumer in Azure
- how to respond from plain tcp client to MessagingTemplate's sendAndReceive
- Java Socket - how does the read() method know if the end of stream has been reached?
- Scala - TCP Packet frame using Akka
- Re-transmission concept in TCP
- Issues regarding multiplayer networking: input
Related Questions in SAN
- having spring integration tcpserver to manage clients and send them messages
- psuedo TCP multicast with os.dup2() in python?
- Retrieve Data From EOC(Eithernet Over coxial) device
- Connecting a web client to a c++ server with TCP
- ECONNRESET on node.js RabbitMQ consumer in Azure
- how to respond from plain tcp client to MessagingTemplate's sendAndReceive
- Java Socket - how does the read() method know if the end of stream has been reached?
- Scala - TCP Packet frame using Akka
- Re-transmission concept in TCP
- Issues regarding multiplayer networking: input
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Ah, no. Non sequitur - one does not follow the other. You set up a new SQL Server cluster. Your database storage is on SAN. There is no intrinsic requirement for this. In fact, for quite some time AOAG (Always On Availability Groups) with non shared storage are preferred for uptime reasons. Also performance - it is quire hard to get a multi gigabyte per second SAN LUN up (among other things because fiber is 8 gigaBIT - 800megabit raw). It is trivial to do so in a small server with a high performance SSD.
THat makes IMHO no sense and runs counter anything I ever experienced. SQL Server stores in 64kb extends - but it always tries to write and read multiple. 256kb to 512kb look better, ESPECIALLY with the caching that a proper IO subsystem does. Theoretically 64kb makes sure you never have split IO - practically this makes little sense, particularly on a SAN with gigabytes of cache.
Whatever you like. You give us little information how you make backups (or do you not have an enterprise backup tool?) Generally backups are a lot less problematic from IO than the active data store. There is, for example, very little random IO on them.