System Requirements
by Frank McBath, Kimberly Tripp, Cathan Cook, Allan Hirt
Microsoft® SQL Server™ 2000 High Availability
- Microsoft® SQL Server™ 2000 High Availability
- A Note Regarding Supplemental Files
- Foreword
- Preface
- Acknowledgments
- I. The High Availability Primer
- 1. Preparing for High Availability
- 2. The Basics of Achieving High Availability
- Data Center Best Practices
- Staffing
- Manage Change or Be Managed by It
- System and Process Standardization
- Documentation
- Summary
- 3. Making a High Availability Technology Choice
- II. Technology Building Blocks
- 4. Disk Configuration for High Availability
- Quick Disk Terminology Check
- Capacity Planning
- Types of Disk Subsystems
- Server Clusters, Failover Clustering, and Disks
- Pre-Windows Disk Configuration
- File Placement and Protection
- Database File Size
- Configuration Example
- Summary
- 5. Designing Highly Available Microsoft Windows Servers
- General Windows Configuration for SQL Servers
- High Availability Options for Windows
- Server Clusters
- Planning a Server Cluster
- Certified Cluster Applications
- Ports, Firewalls, Remote Procedure Calls, and Server Clusters
- Geographically Dispersed Clusters
- Antivirus Programs, Server Clusters, and SQL Server
- Server Clusters, Domains, and Networking
- Implementing a Server Cluster
- Server Cluster Administration
- Network Load Balancing
- Summary
- 4. Disk Configuration for High Availability
- III. Microsoft SQL Server Technology
- 6. Microsoft SQL Server 2000 Failover Clustering
- Planning for Failover Clustering
- Versions of Windows Supported
- Number of SQL Server 2000 Instances per Server Cluster
- Name of the SQL Server Virtual Server
- Number of Nodes
- Disks
- IP Addresses, Ports, and Network Card Usage
- Applications and Failover Clustering
- Third-Party Applications, File Shares, Dependencies, and SQL Server 2000 Failover Clustering
- Hardware-Assisted Backups and SQL Server 2000 Failover Clustering
- Service Accounts and SQL Server 2000 Failover Clustering
- Memory
- Coexistence with Stand-Alone Instances and Other Versions of SQL Server
- Analysis Services and Failover Clustering
- SQL Mail and Failover Clustering
- Exchange and SQL Server on the Same Cluster
- Cluster Group Configuration for Failover Clustering
- Implementing SQL Server 2000 Failover Clustering
- Verifying Your Failover Cluster Installation
- Administering SQL Server Virtual Servers
- Ensuring a Virtual Server Will Not Fail Due to Other Service Failures
- Adding or Removing a Cluster Node from the Virtual Server Definition and Adding, Changing, or Updating a TCP/IP Address
- Renaming a SQL Server 2000 Virtual Server
- Uninstalling a SQL Server Virtual Server
- Manually Removing Failover Clustering
- Manually Removing Clustered Instances of SQL Server
- Changing SQL Server Service Accounts
- Changing Domains
- Troubleshooting SQL Server 2000 Failover Clusters
- Disaster Recovery for Failover Clustering
- Summary
- Planning for Failover Clustering
- 7. Log Shipping
- Uses of Log Shipping
- Basic Considerations for All Forms of Log Shipping
- Log Shipping and Database Backups
- Service Packs and Log Shipping
- Files, Filegroups, and Transaction Logs
- Custom Log Shipping Versus Microsoft’s Implementation
- Configuring and Administering the Built-In Functionality Using SQL Server 2000 Enterprise Edition
- Log Shipping Components
- Configuring Log Shipping
- Administering Log Shipping
- Role Changes
- Creating a Custom Coded Log Shipping Solution
- Log Shipping From SQL Server 7.0 to SQL Server 2000
- Summary
- 8. Replication
- 9. Database Environment Basics for Recovery
- 10. Implementing Backup and Restore
- Creating an Effective Backup Strategy
- Implementing Your Backup Strategy
- Options for Performing a Backup
- Creating a Backup Device
- Executing the Full Database–Based Backup Strategy Using Transact-SQL
- Executing the File-Based Backup Strategy Using Transact-SQL
- Simplifying and Automating Backups
- Implementing an Effective Backup Strategy: In Summary
- Database Recovery
- Phases of Recovery
- Useful RESTORE Options
- Disaster Recovery with Backup and Restore
- Collected Wisdom and Good Ideas for Backup and Restore
- Backing Up the Operating System
- Backing Up and Restoring Clustered Environments
- Summary
- 6. Microsoft SQL Server 2000 Failover Clustering
- IV. Putting the Pieces of the Puzzle Together
- 11. Real-World High Availability Solutions
- 12. Disaster Recovery Techniques for Microsoft SQL Server
- Planning for Disaster Recovery
- Testing Disaster Recovery Plans
- Executing Disaster Recovery Plans
- Disaster Recovery Techniques
- Step 1: Assessing Damage
- Step 2: Preparing for Reconstruction
- Step 3: Reconstructing a System
- Summary
- 13. Highly Available Upgrades
- General Upgrade, Consolidation, and Migration Tips
- Upgrading, Consolidating, and Migrating to SQL Server 2000
- Windows Version Upgrades
- SQL Server Version Upgrades or Migrations
- Attaching and Detaching Databases Versus Backup and Restore
- Service Packs and Hotfixes
- Summary
- V. Administering Highly Available Microsoft SQL Servers
- 14. Administrative Tasks for High Availability
- 15. Monitoring for High Availability
- Monitoring Basics
- Implementing a Monitoring Solution
- Hardware Layer Monitoring
- Monitoring Windows and SQL Server Events
- Monitoring Your Monitor and Other Critical Services
- Capacity Planning and Monitoring
- Summary
- Glossary
- Allan Hirt
- System Requirements
- Index
- About the Authors
- Copyright
Microsoft SQL Server 2000 120-day Evaluation Edition CD
Intel Pentium or compatible 166-megahertz (MHz) or higher processor.
Microsoft Windows Server 2003, Microsoft Windows 2000 Server, Microsoft Windows NT Server 4.0 with Service Pack 5 (SP5) or later, Microsoft Windows NT Workstation 4.0 with SP5 or later, Microsoft Windows XP Professional, Microsoft Windows XP Home Edition, or Microsoft Windows 2000 Professional.
64 megabytes (MB) of RAM; 128 MB recommended.
95 to 270 MB of available hard disk space for the server; 250 MB for a typical installation. 50 MB of available hard disk space for a minimum installation of Analysis Services; 130 MB for a typical installation; 80 MB of available hard disk space for English Query. MSDE requires 44 MB of available hard disk space.
CD-ROM drive.
VGA or higher-resolution monitor.
Microsoft Internet Explorer version 5.0 or later.
Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows Me, Microsoft Windows NT 4.0, Microsoft Windows 2000, and Microsoft Windows XP have built-in network software. Additional network software is required if you are using Banyan VINES or AppleTalk ADSP. Novell NetWare IPX/SPX client support is provided by the NWLink protocol of Windows-based networking.
Microsoft SQL Server 2000 High Availability Companion CD
The SQL Server–based utilities and scripts (job aids) require SQL Server 2000.
The job aids will take up about 20 MB of disk space if copied to hard disk.
The .zip files require decompression software such as WinZip or PKUnzip.
The .pdf files require the Adobe Acrobat Reader (link supplied on CD) or Adobe Acrobat; the .doc files require the Microsoft Word viewer (supplied on CD) or Microsoft Word; the .xls files require the Microsoft Excel viewer (supplied on CD) or Microsoft Excel.
-
No Comment