1.Upgrade / Migration & Virtualisation with SharePoint 2010
Dave Coleman & Alan Richards

2. Why virtualise when upgrading/migration to SharePoint 2010
Simple way to move to a 64bit environment.
Cost savings in a time of budget cuts.
Increased flexibility in growing and managing your server stock.
High availability of e-learning resources.
Improved protection against server failure (if in a fail over cluster).
3. SharePoint 2010 Software/Hardware Requirements
Software
64 Bit edition of SQL 2005 With SP3 or
64 Bit edition of SQL 2008 With SP1 and Cumulative Update 2 or
64 Bit Edition of SQL 2008 R2
64 Bit edition of windows server 2008 with SP2
64 Bit edition of Windows server 2008 R2
Hardware
64 Bit processor, 4 Cores
8GB Ram
80GB Hard Drive Space
4. Single Server Deployment
One server farm
Runs all SharePoint roles
Central admin
Web front end
SQL Server
5. Two Tier Farm
Single SharePoint Server
SQL Server could be MIS Server
6. Upgrade
In place upgrade
Patched SQL
X64 architecture
High availability upgrade
Patched SQL
Copy MOSS 2007 database and attached to new server
7. Metalogix SharePoint Site Migration Manager 2010
Quest Software Migration Manager (2003 to 2010)
TzunamiDeployer for SharePoint 2010 migration
AvePointDocAve SharePoint Migration Manager for 2001/2003/2007 to 2003/2007/2010
MetaVis Migrator for SharePoint
Xavor SharePoint 2010 Migration Tool
SharePoint Joel
http://www.sharepointjoel.com/default.aspx
Migration Tools
8. Virtualisation The Basics
Market players
Citrix
VMWare
Microsoft Hyper-V
9. Standard Model
One server = One role
New role = New Server
New Server = More Money
Virtualisation The Basics
10. Virtualisation Model
Start small
One server
Large memory and storage
One server runs multiple guests
Expand as necessary
Multiple servers
Centralised storage
Failover
Virtualisation The Basics
11. Failover Cluster Manager
12. Failover Cluster Manager

Live Migrate

13. Create New Virtual Servers 14. Start VM 15. Shutdown VM 16. Manage VMs With HyperV Manager 17. Manage Failover and Failback