Skip to main content

Windows Storage Server 2008 R2 Architecture and Deployment

A new white paper about Windows Storage Server 2008 R2 Architecture and Deployment (including the Microsoft iSCSI Software Target 3.3) has just been published.
Here’s an outline of this content:
  • Introduction
  • Windows Storage Server 2008 R2 Overview
    • Comparing Windows Server Operating System Storage Offerings
      • Comparing Windows Storage Server with Windows Server
      • Identifying Windows Storage Server Features
      • What’s New in Windows Storage Server 2008 R2
    • Comparing Windows Storage Server 2008 R2 with Windows Server 2008 R2
    • Windows Storage Server 2008 R2 Editions
    • Identifying Storage Challenges
      • Identify Scalability Storage Challenges
      • Identify Availability Storage Challenges
      • Identify Security Storage Challenges
      • Identify Manageability Storage Challenges
      • Identify Data Recovery Storage Challenges
    • Identifying Windows Storage Server Solution Benefits
      • Identifying Scalability Benefits
      • Identifying Availability Benefits
      • Identifying Security Benefits
      • Identifying Manageability Benefits
      • Identifying Data Recovery Benefits
  • Exploring Windows Storage Server Features and Capabilities
    • Providing Access to File Services Workloads
      • Supporting File Services Workloads Using CIFS, SMB, or SMB2
      • Supporting File Services Workloads Using NFS
      • Supporting File Services Workloads Using WebDAV
      • Supporting File Services Workloads Using Windows SharePoint Services
    • Providing Access to iSCSI Block I/O Workloads
      • Supporting iSCSI Block I/O Workloads Using Microsoft iSCSI Software Target
      • Supporting iSCSI Boot
    • Providing Access to Web Services Workloads
    • Providing Access to FTP Services Workloads
    • Providing Access to Print Services Workloads
    • Providing Reduction in Power Consumption
      • Improve the Power Efficiency of Individual Servers
      • Processor Power Management
      • Storage Power Management
      • Additional Power Saving Features
    • Performing Highly Automated Installations
  • Managing Windows Storage Server
    • Management Tools for All Workloads
    • Managing Power Consumption for All Workloads
      • Remote Manageability of Power Policy
      • In-Band Power Metering and Budgeting
    • Managing File Services Workloads
      • Managing File Services Using File Server Resource Manager
      • Managing File Services Using Share and Storage Management
      • Managing DFS Namespaces and DFS Replication
      • Managing Single Instance Storage
    • Managing iSCSI Block I/O Workloads
      • Managing the Microsoft iSCSI Software Target for iSCSI Block I/O Workloads
      • Managing the Microsoft iSCSI Software Initiator for iSCSI Block I/O Workloads
      • Managing iSCSI Block I/O Workloads Using Windows PowerShell
    • Managing Web Services Workloads
    • Managing Print Services Workloads
  • Protecting Windows Storage Server Workload Data
    • Using Windows Server Backup to Protect Data
    • Using Shadow Copies of Shared Folders to Protect Data
    • Using the Volume Shadow Copy Service to Protect Data
    • Using LUN Resynchronization to Protect Data
      • Comparison of LUN Resynchronization and Traditional Volume Shadow Copy Service
      • Comparison of LUN Resynchronization and LUN Swap
      • Benefits of Performing Full Volume Recovery Using LUN Resynchronization
      • Process for Performing Full Volume Recovery Using LUN Resynchronization
    • Using DFS Replication to Protect Data
    • Using Automated System Recovery to Protect Data
    • Using System Center Data Protection Manager 2007 to Protect Data
    • Using Virtual Disk Snapshots to Protect Data
    • Using the Appcmd.exe Tool to Backup IIS Configuration
    • Using the PrintBRM.exe Tool to Backup Printer Information
  • Securing Windows Storage Server Workloads
    • Securing Windows Storage Server for All Workloads
    • Securing File Services Workloads
    • Securing iSCSI Block I/O Workloads
    • Securing Web Services Workloads
    • Securing Print Services Workloads
  • Improving Availability of Windows Storage Server Workloads
    • Improving Availability of File Services Workloads
    • Improving Availability of iSCSI Block I/O Workloads
      • Creating Highly-Available iSCSI Targets
      • Creating Highly-Available iSCSI Initiators
    • Improving Availability of Web Services Workloads
    • Improving Availability of Print Services Workloads
  • Improving Performance and Scalability for Windows Storage Server Solutions
    • Improving Performance and Scalability for All Workloads
      • Improvements in Processor and Memory Capacity
      • Improvements in the Next Generation TCP/IP Protocol
      • Improvements in Network Adapter Performance
      • Reduction in Processor Utilization for I/O Operations
    • Improving Performance and Scalability for File Services Workloads
      • Review Improvements in the SMB2 Protocol
      • Review SMB-based File Services Workload Test Results
      • Reviewing Performance Improvements in SMB Version 2.1 in Windows Server 2008 R2
      • Improving Performance for Branch Offices Using BranchCache
      • Improving Performance for Folder Redirection and Offline Files
    • Improving Performance and Scalability for iSCSI Block I/O Workloads
      • Identify Methods for Improving iSCSI Block I/O Workload Performance and Scalability
      • Review I/O Storage Test Results
    • Improving Performance and Scalability for Web Services Workloads
      • Identify Methods for Improving Web Services Workload Performance and Scalability
      • Review Web Services Workload Test Results
    • Improving Performance and Scalability for Print Workloads
  • Windows Storage Server Deployment Scenarios
    • Overview of Windows Storage Server Configurations
      • Using Windows Storage Server in a Stand-Alone NAS Configuration
      • Using Windows Storage Server in a Highly-Available NAS Configuration
      • Using Windows Storage Server in a NAS Gateway Configuration
      • Using Windows Storage Server in iSCSI Block I/O Configuration
    • Creating Branch Office Solutions
    • Creating Highly-Available Solutions
    • Creating Solutions for Storage Consolidation
    • Creating Small to Medium Business Solutions
    • Creating Solutions for Heterogeneous Environments
    • Creating Application Consolidation Solutions
    • Creating Unified Storage Solutions
    • Creating Virtualization Solutions
      • Connecting Virtual Machines to iSCSI LUNs
      • Running Virtual Machines on Windows Storage Server
    • Creating iSCSI Boot Solutions
  • Conclusion

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N