July 24, 2010 – flaphead.com

http://www.mmmug.co.uk/4-18th_August_2010_-_Exchange_backup_and_recovery

The subject of this meeting is Exchange backup and recovery and we have Microsoft’s Anthony Tyler talking about System Centre Data Protection Manager’s take on backing up exchange and Kroll Ontrack’s offering for recovery.

Kroll Ontrack is now celebrating its 25^th Anniversary as a global leader in the provision of data management solutions, specialising in data recovery, restoration, erasure and investigative products and services (www.krollontrack.co.uk).

Ontrack PowerControls software for Microsoft Exchange empowers users to search, recover, extract, restore and migrate Microsoft Exchange data (www.ontrackpowercontrols.co.uk).

Faced with increasing hardware and administration costs together with tighter budgets, organisations are seeking more cost-effective and efficient solutions to manage ad-hoc and routine Microsoft Exchange data requests. The core functionality of Ontrack PowerControls enables System Administrators to search, recover and restore entire .edb, .pst files and granular level items, whilst retaining data integrity.

Kroll Ontrack is pleased to be demonstrating the core functionality, features and application of this invaluable Microsoft Exchange administration tool.

Agenda:

18:00pm – 18:30pm Arrival
18:30pm – 19:30pm Ontrack PowerControls

Company & Product overview
Single item restore / recovery
Intuitive searching
Additional functionality
Existing customers
Live demo
Extraction of Microsoft Exchange data from backup
Browsing single / multiple .edb & .pst files, to single item level
Searching across multiple .edb’s
Compliance, investigations and legal requirements
Restoration of data
Reporting
Hands-on demo
Q & A

19:30pm – 20:00pm Refreshments
20:00pm – 20:45pm Microsoft DPM

Why build DPM?
Introducing DPM
Demo – Protecting Data
How Does DPM work?
Demo – Rapid & Reliable Recovery
Protected Platforms

20:45pm – 21:00pm Discussions & Questions on Exchange backup / recovery.

Location: Kroll Ontrack Limited, Tower Place East, London EC3R 5BS, United Kingdom

#Exchange2010

Interesting, from WES 2010 session ‘WA25: Best Practices in Deploying Microsoft® Exchange for BlackBerry’ jointly presented by RIM and Microsoft Jeff Mealiffe (Sr. Development Lead, Scalability & Capacity Planning) it says:

Database IOPS per user is equivalent to a Microsoft® Outlook® client, not 5x and not 3x
Our past data represented the worst case scenario
- Workload assumes both BlackBerry and Microsoft Outlook clients active
- 100% BlackBerry enabled users
- High density of BlackBerry users on a single storage group
Our focus in the past has also been on providing a single impact number
- Database I/O more expensive and needs to be our focus (random I/O)
- ransaction log I/O gets optimized well by disk infrastructure (increase is not as relevant – sequential I/O)

Dual clients per user active (Outlook and BlackBerry )
- DB IOPS increase by 1.85x for BlackBerry enabled users only
- DB IOPS increase by 1.7x for BlackBerry enabled users only (5.0.2
  optimizations)
- DB IOPS with optimization equivalent to an outlook client
Truly mobile users (only BlackBerry client)
- DB IOPS equivalent to an Outlook client

BES 5.0 SP2 DB IOPS increase by only 1.7x with Exchange 2010 compared with 2.16x on Exchange 2007 with BES 5.01

Mail server role

Mail server CPU recommendation is about 1.4 -1.5x MCycles/mailbox recommended by Microsoft
Memory, same as what is recommended by MS for outlook users/clients

CAS Server role

CPU core recommendation is inline with 4:3 ratio recommend by Microsoft for CAS:Mail server
NSPI connection count needs to be increased to 1 per BlackBerry smart phone – default is 50 (too low)
Throttling needs to be disabled for the service account used for the BlackBerry Enterprise Server

Check out some of the other stuff from WES here: www.attendwes.com/virtualwes

Day: July 24, 2010

#MMMUG: 18th August 2010 – #Exchange backup and recovery

BES 5.0 SP2: Blackberry User #Exchange 2010 IOPS now equal to an Outlook Client