Microsoft introducing windows server 2008 Resource Kit phần 9 pptx

380 Introducing Windows Server 2008 The Provision A Shared Folder Wizard provides an integrated file share provisioning experience that lets you easily select sharing protocols (SMB or NFS). Depending on your protocol selection, the wizard lets you configure either SMB or NFS settings. The following SMB settings can be configured: ■ User limit ■ Access-based enumeration ■ Offline settings ■ NTFS and share permissions Or you can specify NFS settings such as these: ■ Allow anonymous access ■ Client groups and host permissions In addition, the wizard lets you specify a quota or file screen template and add or publish your share to a DFS namespace. Here’s a screen shot showing the Provision A Shared Folder Wizard and displaying on the left the various steps involved in running the wizard: Chapter 12 Other Features and Enhancements 381 Windows Server Backup Windows Server Backup is the replacement for the NTBackup.exe tool found on previous versions of Windows Server. It’s implemented as an optional feature you can install using Server Manager, the Initial Configuration Tasks screen, or the ServerManagerCmd.exe command. Windows Server Backup uses the Volume Shadow Copy Service first included in Windows Server 2003. Because of this, Windows Server Backup takes a snapshot of any vol- ume and backs the volume up without having to take the server down because of applications or services that are running. The result of this is that you no longer need to worry about scheduling backups during downtimes when the system is idle. Windows Server Backup was basically designed to target the single-server backup needs for DIYs (do-it-yourselfers) because most small organizations don’t bother to back up until a disaster strikes. Additionally, Microsoft studies revealed that the NTBackup.exe tool found in previous versions of Windows Server was generally too complex for this market segment to use effectively. Windows Server Backup is not targeted toward typical mid- and large-sized organizations, as they typically use third-party backup solutions from vendors. In a nutshell, here’s what Windows Server Backup is all about: Windows Server Backup is an in-box backup and recovery tool in Windows Server 2008 that protects files, folders, volumes, application data, and operating system components. It provides recovery granularity for 382 Introducing Windows Server 2008 everything from full servers to data pertaining to individual files or folders, applications, or system state information. It is not, however, intended as a feature-by-feature replacement for NTBackup.exe. The focus of the tool’s design is simplicity, reliability, and performance so that the IT generalist can use it effectively. The tool has minimal configuration requirements and provides a wizard-driven backup/recovery experience. Figure 12-1 shows the new Windows Server Backup MMC snap-in, which can be used to perform either scheduled or ad hoc backups on your server. Figure 12-1 Windows Server Backup MMC snap-in Windows Server Backup uses the same block-level image-based backup technology that is used by the CompletePC Backup And Recovery feature in Windows Vista. In other words, Windows Server Backup backs up volumes using the Microsoft Virtual Server .vhd image file format just like CompletePC does on Windows Vista. Using snapshots on the target disk opti- mizes space and allows for instant access to previous backups when needed, and block-level recovery can be used to restore a full volume and for bare-metal restore (BMR). This improved bare-metal restore (which builds on the ASR of NTBackup.exe in Windows Server 2003) means also that no floppy disk is needed anymore to store disk configuration information. In addition, you can perform recovery from the Windows Recovery Environment (WinRE) using single-step restore, where only one reboot is required. You can also mount a snapshot of a .vhd file as a volume for performing file, folder, and application data recovery. Note that Windows Server Backup takes only one full snapshot of your volume—after that it’s just differentials that are captured. An important point is that Windows Server Backup is optimized for backing up to disk, not tape. You can also use it for backing up servers to network shares or DVD sets, but there is no tape support included. Why is that? Well, just consider some of the trends occurring in today’s storage market that are beginning to drive new backup practices. For example, one Chapter 12 Other Features and Enhancements 383 strong trend is the movement toward disk-based archival storage solutions. The cost of disk storage capacity was originally around ten times the cost of tape, but with massive consumer adoption of small form-factor devices that include hard drives in them, the cost of disk storage capacity has dropped precipitously to about twice the cost of tape. As a result, many admins are now implementing “disk to disk to tape” backup solutions, which leverage the low latency of disk drives to provide fast recoveries when needed. And with Windows Server Backup on Windows Server 2008, an admin can quickly mount a local (SATA, USB, or FireWire) disk or a SAN (iSCSI or FC) disk and seamlessly schedule regular backup operations. Finally, Windows Server Backup also includes a command-line utility, Wbadmin.exe, that can be used to perform backups and restores from the command line or using batch files or scripts. Here’s a quick of example of how you can use this new tool. Say that you’re the admin- istrator of a mid-sized company with a dozen or so Windows Server 2008 servers that you need to have backed up regularly. Instead of purchasing a backup solution from a third-party ISV, you decide to use the Wbadmin.exe tool to build your own customized backup solution. You’ve installed the Windows Server Backup feature on all your servers, and they have backup disks attached. You want to ensure that the C and E drives on your servers are being backed up daily at 9:00 PM. Here’s a command you can run to schedule such backups: Wbadmin get disks Wbadmin enable backup –addtarget:<disk identifier> -schedule:21:00 –include:c:,e: Say that you then get a call from one of your users informing you that some important documents were accidentally deleted from d:\users\tallen\business and need to be recovered. You can try recovering these documents from the previous evening’s backup by doing this: Wbadmin get versions Wbadmin start recovery –version:<version-id> -itemtype:file –items: d:\users\tallen\business –recursive Wbadmin start recovery –version:<version-id> -itemtype:file –items: d:\users\tallen\business –recoverytarget: d:\AlternatePath\ -recursive What if a server failed and you had to do a bare-metal recovery? To do this, just use the Windows Server 2008 media to boot in to the WinRE environment and choose the option to perform a recovery of your entire server from the backup hard disk onto the current hard disk. To do this, once you’re in the WinRE environment, launch a command prompt and type this: Wbadmin get versions –backuptarget:<drive-letter> Wbadmin start BMR –version:<version-id> -backuptarget:<drive-letter> - restoreAllVolumes –recreateDisks 384 Introducing Windows Server 2008 Finally, for those of you who are still not convinced that Windows Server Backup is better than the NTBackup.exe tool in the previous platform (and I know you’re out there some- where, griping about “No tape support”), Table 12-1 provides a comparison of features for the two tools. Guess which one has the most supported features? Storage Explorer Storage Manager for SANs (SMfS) was available in Windows Server 2003 R2 as a tool to help you create and manage logical unit numbers (LUNs) on Fibre Channel (FC) and iSCSI disk drive subsystems that support the Virtual Disk Service (VDS) in your storage area network (SAN). Windows Server 2008 builds on this by providing a new tool called Storage Explorer, an MMC snap-in that provides a tree-structured view of detailed information concerning the topology of your SAN. Storage Explorer uses industry-standard APIs to gather information about storage devices in FC and iSCSI SANs. With Storage Explorer, the learning curve for Windows admins is much easier than traditional proprietary SAN management tools because it is implemented as an MMC snap-in and therefore looks and behaves like applications that Windows admins are already familiar with. The Storage Explorer GUI provides a tree-structured view of all the com- ponents within the SAN, including Fabrics, Platforms, Storage Devices, and LUNs. Storage Explorer Management also provides access to the TCP/IP management interfaces of individ- ual devices from a single GUI. By combining Storage Explorer and SMfS, you get a full- featured SAN configuration management system that is built into the Windows Server 2008 operating system. Let’s now take a look at a few screen shots showing Storage Explorer at work. First, here’s a shot of the overall tree-structured view showing the components of the SAN, that is Windows servers, FC Fabrics, and iSCSI Fabrics: Ta b l e 1 2 - 1 Comparison of Windows Server Backup with NTBackup.exe Feature NT Backup Server Backup User Data Protection Yes Yes System State Protection Yes Yes Disaster Recovery Protection Yes Yes Application Data Protection No Yes Disk Media (not VTL) Storage Yes Yes DVD Media Storage No Yes File Server Storage Yes Yes Tape Media Storage Yes No Remote Administration No Yes Chapter 12 Other Features and Enhancements 385 Let’s drill down into each of these three subnodes. Here’s a shot of the Servers node showing various servers (these shots were taken using internal test servers at Microsoft, so their names have been obfuscated): 386 Introducing Windows Server 2008 And here’s a screen capture displaying details under the Fibre Channel Fabrics subnode: Finally, this one shows details under the iSCSI Fabrics subnode: SMB 2.0 Another enhancement in Windows Server 2008 (and in Windows Vista) is version 2 of the Server Message Block (SMB) protocol. SMB is used by client computers to request file services from servers over a network. SMB is also used as a transport protocol for remote procedure calls (RPCs) because it supports the creation and use of named pipes. Unfortunately, SMB 1.0 on previous Windows platforms is considered overly “chatty” as a protocol—that is, it gener- ates too much network traffic, especially for use over slow or congested WAN links. In addi- tion, SMB 1.0 has some restrictive constants regarding the number of open files and the total number of shares it can support and it doesn’t support durable handles or symbolic links. Finally, the signing algorithms used by SMB 1.0 are cumbersome to use. As a result of these considerations, Microsoft introduced SMB 2.0 in Windows Vista and includes support for this protocol in Windows Server 2008. The benefits of the new protocol Chapter 12 Other Features and Enhancements 387 include less restrictive constants for file sharing, packet compounding to reduce chattiness, improved message signing, and support for durable handles and symbolic links. Note that Windows Server 2008 and Windows Vista support both SMB 1.0 and SMB 2.0. The version of SMB that is used in a particular file-sharing scenario is determined during the SMB session negotiation between the client and the server, and it also depends on the operating system on the client and server as well—see Table 12-2 for details. Multipath I/O When you think of high-availability storage for your organization, you might think of using RAID to provide disk redundancy and fault tolerance. Although this is a good solution, it pro- tects only your disks. Also, if there’s only one path from your server to your storage device and any component in that path fails, your data will be unavailable—no matter how much disk redundancy you’ve implemented. A different approach to providing high-availability storage is to use multipathing. A multipath- ing (or multipath I/O) solution is designed to provide failover using redundant physical path components, such as adapters, cables, or switches that reside on the path between your server and your storage device. If you implement a multipath I/O (MPIO) solution and then any component fails, applications running on your server will still be able to access data from your storage device. In addition to providing fault tolerance, MPIO solutions can also load-balance reads and writes among multiple paths between your server and your storage device to help eliminate bottlenecks that might occur. MPIO is basically a set of multipathing drivers developed by Microsoft that enables software and hardware vendors to develop multipathing solutions that work effectively with solutions built using Windows Server 2008 and vendor-supplied storage hardware devices. Support for MPIO is integrated into Windows Server 2008 and can be installed by adding it as an optional feature using Server Manager. To learn more about MPIO support in Windows Server 2008, let’s hear now from a couple of our experts at Microsoft: Ta b le 1 2 - 2 SMB 1.0 and 2.0 Support for Various Windows Operating Systems Client Server Version of SMB used Windows Server 2008 or Windows Vista Windows Server 2008 or Windows Vista SMB 2.0 Windows Server 2008 or Windows Vista Windows XP, Windows Server 2003, or Windows 2000 SMB 1.0 Windows XP, Windows Server 2003, or Windows 2000 Windows Server 2008 or Windows Vista SMB 1.0 Windows XP, Windows Server 2003, or Windows 2000 Windows XP, Windows Server 2003, or Windows 2000 SMB 1.0 388 Introducing Windows Server 2008 From the Experts: Multipathing Support for High Availability Windows Server 2008 includes many enhancements for the connectivity of Windows Server servers to SAN devices. One of these enhancements, which enables high availabil- ity for connecting Windows Server servers to SANs, is integrated Microsoft MPIO sup- port. The Microsoft MPIO architecture supports iSCSI, Fibre Channel, and Serial Attached SCSI (SAS) SAN connectivity by establishing multiple sessions and connec- tions to the storage array. Multipathing solutions use redundant physical path compo- nents—adapters, cables, and switches—to create logical paths between the server and the storage device. If one or more of these components fail and cause the path to fail, mul- tipathing logic uses an alternate path for I/O so that applications can still access their data. Each NIC (in the case of iSCSI) or host bus adapter (HBA) should be connected through redundant switch infrastructures to provide continued access to storage in the event of a failure in a storage fabric component. Failover times will vary by storage ven- dor and can be configured through timers in the parameter settings for the Microsoft iSCSI Software Initiator driver, the Fibre Channel host bus adapter driver, or both. New Microsoft MPIO features in Windows Server 2008 include a native Device Specific Module (DSM) designed to work with storage arrays that support the Asymmetric logi- cal unit access (ALUA) controller model (as defined in SPC-3) as well as storage arrays that follow the Active/Active controller model. The Microsoft DSM provides the follow- ing load balancing policies (note that load balancing policies are generally dependent on the controller model—ALUA or true Active/Active—of the storage array attached to Windows): ■ Failover No load balancing is performed. The application will specify a primary path and a set of standby paths. Primary path is used for processing device requests. If the primary path fails, one of the standby paths will be used. Standby paths must be listed in decreasing order of preference (that is, most preferred path first). ■ Failback Failback is the ability to dedicate I/O to a designated preferred path whenever it is operational. If the preferred path fails, I/O will be directed to an alternate path until but will automatically switch back to the preferred path when it becomes operational again. ■ Round Robin The DSM will use all available paths for I/O in a balanced, round robin fashion. ■ Round Robin with a Subset of Paths The application will specify a set of paths to be use in Round Robin fashion, and a set of standby paths. The DSM will use paths from primary pool of paths for processing requests as long as at least one of the paths is available. The DSM will use a standby path only when all the primary paths fail. Standby paths must be listed in decreasing order of preference (that is, most preferred path first). If one or more of the primary paths become available, Chapter 12 Other Features and Enhancements 389 DSM will start using the standby paths in their order of preference. For example, given 4 paths–A, B, C, and D, A, B, and C are listed as primary paths and D is standby path. The DSM will choose a path from A, B, and C in round robin fashion as long as at least one of them is available. If all three fail, the DSM will start using D, the standby path. If A, B, or C become available, DSM will stop using D and switch to the available paths among A, B, and C. ■ Dynamic Least Queue Depth The DSM will route I/O to the path with the least number of outstanding requests. ■ Weighted Path Application will assign weights to each path; the weight indicates the relative priority of a given path. The larger the number the lower the priority. The DSM will choose a path, among the available paths, with least weight. The Microsoft DSM remembers Load Balance settings across reboots. When no policy has been set by a management application, the default policy that will be used by the DSM will be either Round Robin, when the storage controller follows the true Active-Active model, or simple Failover in the case of storage controllers that support the SPC-3 ALUA model. In the case of simple Failover, any one of the available paths could be used as primary path, and the remaining paths will be used as standby paths. Microsoft MPIO was designed specifically to work with the Microsoft Windows operating system, and Microsoft MPIO solutions are tested and qualified by Microsoft for compatibility and reliability with Windows. Many customers require that Microsoft support their storage solutions, including multipathing. With a Microsoft MPIO-based solution, customers will be supported by Microsoft should they experience a problem. For non-Microsoft MPIO multipathing implementations, Microsoft support is limited to best-effort support only, and customers will be asked to contact their multi- path solution provider for assistance. Customers should contact their storage vendor to obtain multipathing solutions based on Microsoft MPIO. Microsoft MPIO solutions are also available for Windows Server 2003 and Windows 2000 Server as a separately installed component. Adding MPIO Support To install MPIO support on a Windows Server 2008 server, do the following: 1. Add the Microsoft MPIO optional feature by selecting the Add Features option from Server Manager. 2. Select Multipath I/O. 3. Click Install. 4. Allow MS MPIO installation to complete and initialize. 5. Click Finish. [...]... the rapid adoption and deployment of Windows operating systems Windows Deployment Services allows network-based installation of Windows Vista and Windows Server 2008 to deploy Windows Server 2008 to systems with no operating system installed 400 Introducing Windows Server 2008 Installation to an iSCSI Boot LUN The following steps are used to install Windows Server 2008 directly to an iSCSI boot LUN:... in step 1 8 Windows will complete installation and automatically reboot The ability to boot a Windows Server using the Microsoft iSCSI Software Initiator is also available for Windows Server 2003 as a separate download Windows Server 2008 provides this capability out of the box and provides more direct integration with Windows Server 2008 Setup Windows Server 2008 and previous versions of Windows continue... in Windows Server 2003 while reducing your cost because you’re able to use commodity NICs In addition, Windows Server 2008 can be used in conjunction with System Center Configuration Manager 2007 to easily manage your boot volumes on the SAN Our experts will now give us more details on booting Windows Server 2008 from a SAN: From the Experts: Booting Windows Server 2008 Remotely Windows Server 2008. .. the DHCPv6 client uses the Stateless mode of operation DHCPv6 Stateless and Stateful Servers in Windows Server 2008 In Windows Server 2008, Microsoft has also introduced DHCPv6 functionality to the DHCP server The Windows Server 2008 DHCP server includes support for both the DHCPv6 Stateless and the DHCPv6 Stateful Server functionality In the DHCPv6 stateless mode, clients use DHCPv6 only to obtain... the new granular audit policy feature with Group Policy, you must use it in a script Microsoft Knowledge Base article 92 14 69 discusses how to accomplish this; the article can be found at http://support .microsoft. com/kb /92 14 69 412 Introducing Windows Server 2008 There are also many new Security events in Windows Server 2008 in fact, 340 such events in total Here is the prototype for the new event when... System Security For additional information concerning security enhancements in Windows Vista and Windows Server 2008, see the “Security and Protection” section in the Windows Vista TechCenter Library found on Microsoft TechNet at http://technet .microsoft. com/en-us/ windowsvista/aa905062.aspx 414 Introducing Windows Server 2008 Other Improvements Finally, here are a couple more improvements you might... hardware that is certified by the Windows Logo Program, you can deploy Microsoft Exchange Server, SQL Server, and Windows SharePoint Services on iSCSI SANs iSCSI solutions are simple to implement You just install the Microsoft iSCSI Initiator (which was an optional download for Windows Server 2003 but is now a built-in component in Windows Server 2008) on the host server, configure a target iSCSI storage... more improvements you might be interested in hearing about The first concerns some enhancements that have been made to the Fax Server role in Windows Server 2008 A lot of what is shipping in Windows Server 2008 for this role is based on Windows Server 2003 However, Windows Server 2008 has some major new features for this role, including a new accounts infrastructure and a new feature called Reassign, which... Deployment Using Windows as an iSCSI host is also supported with Windows 2000, Windows Server 2003, and Windows XP as a separate download from http://www .microsoft. com/ downloads iSCSI Configuration iSCSI initiator configuration can be launched from the control panel (classic view) or from Administrative Tools iSCSI is supported with all SKUs and versions of Windows Server 2008, including the Windows server. .. process and consolidate equipment resources—for example, by deploying racks of blade servers Booting from SAN To boot from SAN over an IP network on Windows Server 2003, you needed to install an iSCSI HBA that supported iSCSI boot on your server This is because the HBA BIOS contains 398 Introducing Windows Server 2008 the code instructions that make it possible for your server to find the boot disk on . used Windows Server 2008 or Windows Vista Windows Server 2008 or Windows Vista SMB 2.0 Windows Server 2008 or Windows Vista Windows XP, Windows Server 2003, or Windows 2000 SMB 1.0 Windows. 1.0 Windows XP, Windows Server 2003, or Windows 2000 Windows Server 2008 or Windows Vista SMB 1.0 Windows XP, Windows Server 2003, or Windows 2000 Windows XP, Windows Server 2003, or Windows 2000 SMB. 1.0 388 Introducing Windows Server 2008 From the Experts: Multipathing Support for High Availability Windows Server 2008 includes many enhancements for the connectivity of Windows Server servers