Enterprise Support Seminar – June 2005

Enterprise Support Seminar – June 2005

© Copyright Research Machines plc, 1997 – 2005. All Rights Reserved.

Disaster Recovery

Steve Menzies



Disaster?

“an event which occurs on your network which makes normal day-to-day business functions impossible AND can or will result in data loss “

Microsoft White Paper on Disaster Recovery, November 2004



Agenda

• Causes of a Disaster• Best Practice

- Overview of previous seminars

• Providing Fault Tolerance- For Smart-Tools 3 environment

• Backup Provision- Existing and new solutions

• Summary



Causes of a Disaster

• Inadequate security - Physical barriers (doors & locks), Authorisation

• Ageing Hardware/Software- Older equipment more liable to fail, software can become unstable

• Software Updates- Installing incorrect updates/missing updates

• Physical Considerations- Air quality, temperature, location

• Human intervention- Accidental and deliberate, username/password misuse

• Not resolving small insignificant issues - Fan failures, hard-drive bad blocks, etc



Best Practice

Points to remember from previous seminars:• General Network Use • Server Hardware • Server Software • Different Backup Solutions• Regular Scheduled Backups • System Recovery • Hardware Recovery • Anti-virus provision• Needs to be integrated into overall college

disaster recovery plan



Providing Fault Tolerance

Native Microsoft Tools • Network Load Balancing (NLB)

- Not suitable for data critical servers- Improves data throughput rates/spreads load- Minimal fault tolerance – no data copying or protection- Suited for web-servers/ISA Server/Terminal Server- Maximum of 32 servers per cluster

• Microsoft Clustering Service (MSCS)- Requires specific hardware specifications (MSHCL)- Requires Windows Server 2003 Enterprise Edition- Suitable for File/Print/Database/Email Servers- Maximum of 2 servers/8 servers (Windows 2000/2003)




Current fault tolerance in Smart-Tools 3- Replica Domain Controllers- DNS- DHCP - drive mappings for RM shares- cached local log-ons

As part of your overall fault tolerance provision for Smart-Tools 3• DoubleTake

- multiple operating system compatibility- provides real-time (and open file) data replication - replicates from a source server to a target server - block level file replication (saves bandwidth), only changes are

copied- can provide failover for multiple servers- can be additionally configured using scripting (manual or

automatic)- augments your existing Backup Strategy



DoubleTake

User Home Directories



DoubleTake

• DemonstrationSmart-Tools 3 Domain Controller failure

Smart-Tools 3 & DoubleTake

on Microsoft Virtual Server 2005




Service Native ST3/ Windows Support

Double Take

Domain Controller Roles

Not required as other DCs can provide roles. FSMO roles should remain on failed server

DHCP DHCP can be load balanced using Standard MS Tools. Can be failed onto DoubleTake Server

DNS DNS Queries can be handled by other DCs

User Home Directories

If DC has failed then the UHD will not be accessible until recovered

Learning Resources

Certain LRs can be failed over to Double Take

RM Man. Cons.

RMMC can be accessed on other RM DC

RM Multimedia

Can be failed over to Double Take

RM Auditor Auditor Database will be unavailable until the Server is recovered

Printer Credits

Printer Database will be unavailable until the Server is recovered. Printing will still be available




DoubleTake Benefits• Cost

- No Specific Hardware or Software requirements• Simplicity

- Can be managed from a management console interface• Scalability

- One DoubleTake Server can provide fault tolerance for multiple servers performing different roles. Server can be added at any time without effecting others

- Can be used to provide tolerance for other mission critical member servers in a Smart-Tools 3 Environment (SQL, IIS)

DoubleTake does not replace a whole server in the event of a failure but rather provides fault tolerance for services that the failed server provides



Network Backup & Restore Protection

• Existing EBS- Veritas NetBackup 5- Veritas Backup Exec 9

• New EBS- Veritas Backup Exec 10

• Backup regime – full/differential/incremental• Centralised/local system• Shrinking backup window / Increasing data

volume




• Eliminating bottlenecks – Data Throughput

AIT3 Tapes 12 MB/sec*

SDLT320 Tapes 16 MB/sec*

SDLT600 Tapes 36 MB/sec*

100 Mbps Network ~ 7.5 MB/sec

1 Gbps Network ~ 75 MB/sec

Typical Database Server

~10 - 15 MB/sec

Typical User File Server

~ 1 – 5 MB/sec* Native uncompressed transfer speeds




• Reducing backup time• Tape technology is fast, and getting faster S4-

DLT and LTO3 likely to be around 130MB/sec• File systems are inherently slow to backup• Can backup multiple systems concurrently

over 1 Gbps network• Backup straight to tape (multiplex)

- Veritas NetBackup• Backup to intermediary disk stage

- Veritas Backup Exec 10 or Veritas NetBackup



Veritas Backup Exec 10

What’s New?

• Disk Staging • Policy Based Jobs• Increased Report Functionality • Cluster Support • Fault Tolerant • Advanced Disk-based Backup Option



Veritas Backup Exec 10

Disk Staging Demonstration

Using Microsoft Virtual Server 2005



Backup ProvisionEBS

FeatureBackup Exec

9.xBackup Exec

10NetBackup 5

Disk Staging

Multiplexing

Policy Based Jobs

Enhanced Report Functionality

Cluster Support

Enhanced Security Protection

Enhanced Fault Tolerance

Advanced Disk-based Backup

MS Virtual Server Compatible

Standard Components



Disaster Recovery

• Testing Disaster Recovery• Equipment

- Live server on the network- Test server in test network- Virtual server in virtual network



Disaster Recovery

• Microsoft Virtual Server 2005 benefits- Provides a test network for disaster

recovery testing, software updates, application testing

- Can be used to replace physical server in the event of disaster

- Can consolidate multiple servers on one physical “box”



Disaster Recovery

SummaryProtect against disaster• Disaster recovery strategy

- part of overall college disaster recovery strategy

- plan must be dynamic- under constant review- able to change to meet new threats

• Providing fault tolerance- data protection/failover



Disaster Recovery

Recovering from disasterBackup and restore strategy must be tried and

tested- When?

• End of term/start of term• Before/after Significant Network Changes• “Quiet” times

- With what?• Live server equipment – greater risk• Test server equipment – greater expense• Virtual server (Microsoft Virtual Server 2005)



Disaster Recovery

• Learn from past experiences• Seen before somewhere else• Learn from others• No need to reinvent the wheel

“Every minute saved before the disaster is one that will not be wasted after”

Date post:	25-May-2015
Category:	Technology
Upload:	cameroon45
View:	248 times
Download:	0 times

Enterprise Support Seminar – June 2005

Technology