Month: May 2014

TechEd2014 : OneDrive for Business

My notes from the session OneDrive for Business

75% of businesses allow personal devices, Only 25% have a BYOD policy

Productivity versus Compliance

File/Sync/Share – Very similar to SyncPlicity

All my files in one place

1TB of storage

anywhere access

Sync client – various clients

Office client integration <- Cool feature

Co-authoring <- This is really cool. Being to see other authors updates on a document in realtime

Easy sharing

Search & Discovery

Security

Management

Admin Control

Part of SharePoint and O365

File upload size 2GB

Automatic versioning

Post to Yammer

“Shared with me” view

Which version should I use?

SharePoint features update every 3 years

O365 updates very frequently

HIPAA certified

Custom apps can be developed on top of OneDrive

Site Folders – Team site document libraries

Recycle Bin

Recent Documents – across all office clients that you use <- Cool feature.

Launch “new” documents from O365

Rich preview from O365 <- Cool feature.

Edit from O365 with co-authoring in real time ( you can see the other person edits live) <- Awesome feature.

External sharing is optional via policy

Post to Yammer – can limit to groups and users

Search – my docs and shared with me

Workflows, Check in/out, workflows – just like in SharePoint

Email with attachment or link to doc with Outlook in O365

Code name Oslo “Office Graph” – New Search and Discovery across all Office content, includes edits, comments, trending, liked, relationships, adheres to permissions (only shows content that I have access to)

Coming Soon:

Document Conversations

Mac Sync Client

Native Android app

DLP

Auditing/Reporting

Encryption at Rest

Oslo + Office Graph

New Admin panel for SharePoint on-premise

Pricing – Standalone offering $2.50/user/month, 1TB per user, includes Office Online

Part of Office365 ProPlus

TechEd2014 : SQL on Azure VMs

My notes from the TechEd session on SQL inside of Azure VMs

 

This stuff is confusing. No standard storage terminology being used.

Someone asked if the disks in the BLOBS where Thick or Thin. Answer: We don’t use those terms.

 

Whitepaper:

Performance Guidance for SQL Server in Windows Azure Virtual Machines

http://msdn.microsoft.com/en-us/library/dn248436.aspx

 

Azure VMs tie to Azure Storage – need to understand how Azure Storage works

Azure service is a shared service, multi-tenet service

 

Azure BLOB storage

 VHDs stored in BLOB

3 copies automatic – persistent copies

Shared service – noisy neighbors can be an issue

No direct performance correlation between disk requests made by VM and the underlying physical disk

No performance SLA’s

500TB / BLOB

Total requests rate 20,000 /sec

Geo-redundant storage = 10gb/sec Ingress, 20 gb/sec Egress

Local redundant = 20gb/sec Ingress 30 gb/sec Egress

 

Two tiers of service for VMs

VM Basic tier = A0-A4 tiers

VM Standard tier = A5-A9 tiers

 

Disk types

C:- 127GB – persistent

D: Temp drive – 20GB-605GB depend on tier – may be wiped on reboot – local disk, low latency

Data Disks – up to 1TB each (thin)

 

Where and when you provision your VM matters – the service can move your VM around

Maintenance operations have an effect on performance – notified from Microsoft when they do maintenance

 

C:- D:are local disks versus Azure disks stored in a BLOB

– need to test to determine scenarios for performance of where to put what

 

VM Disk Cache

“Host Cache Preference” when creating a disk

Two tier cache:

Tier 1 – Most recently accessed data stored in RAM of physical virtualization host. This cache is sharedby all VMs on that host

Tier 2 – Less recently accessed data stored on the local disk of the physical host (disk based cache). Ther is cache space reserved to each VM OS disk and Data disk based VM size.

Scenarios

  • Reduce transaction against Azure Storage
  • Reduce disk IO latency when IO rate is low
  • Impr0ve boot time

 

Network Bandwidth and Delay

Bandwidth

I/O go through separate stack from Guest VM network

Latency

“Cloud Service” is a management, config, security, networking and service model boundary

Affinity group : Compute and storage to be placed close to each other

Going through load balancers adds latency

 

IO paths on Azure VM

Diagram:

Azure diagram

 

Disk recommendations:

Use Data disks (not local OS disk) for DBs larger than 10GB

Cache settings:

Use “None” for high OLTP – random I/O

Use “Read” if workload is sensitive to latency

Use “Read/Write” for sporadic disk access – not a write back cache

Static data, seldom accessed

Cache setting can be changed via PowerShell

 

VM instance size and limits

Place user DB & logs on different data disks

If on OS drive:

Avoid OS disk stripping, use SQL striping (ie. file group)

Warm up disk before measuring performance

After initialize the file by writing some bit patterns sequentially using SQLIO

Consider enabling SQL data compression (row, page) for I/O bound workloads

Reduces I/O

CPU usage can increase

Enable instant file initialization

Don’t use auto-grow, pre-allocate instead

Use 64KB DAU

 

Placement of data files

Option 1: DB across multiple files with a file group

Option 2: Create an “OS volume” on top of multiple disk

Option 3: Multiple striped volumes each with one or more data disks (based on specific I/O performance requirements)(Host level RAID 0)

 

TempDB

Place on OS or Data disks

Don’t use D: temp drive – performance issues can occur

 

Disk warm up

Disk Load balancers – cold disks get less performance, hot disks get better performance

Idol disks (cold) for 20 mins will reduce your performance. Azure remove disk load balancers from cold disks.

Manually Warm up disks for 10 mins – will get you better performance

Use a Script to warm up

 

VM Dashboard

Monitor tab for storage account

Storage analytics logging

Minimal or Verbose

Aggregated data place into hidden place in BLOB “&log” – accessible via PowerShell

 

Moving to the cloud doesn’t solve app design issues

Performance baseline needed prior to moving to Azure in order to understand performance

 

Backups

  1. Backup directly to BLOB storage via URL – within the same data center, if another datacenter will be charged egress
  2. Backup to regular disk

 

Repurposing of data -??

How to populate test/dev?

 

 

EMC and Microsoft – Friend or Foe?

You may think that EMC and Microsoft are bitter competitors, and you may be right because in some areas they do fiercely compete. But more often than not, the two companies work together to solve customer problems with joint solutions from both sides. Even with competing products, overlapping functionality, and differences in approach, it is the customer who ultimately drives the decision. That decision is rarely a one sided architecture. Most often we see a blend of technologies from both EMC and Microsoft that come together to solve business issues and initiatives.

Competitive

Microsoft has competitive technologies, guidance, and solutions in several areas. EMC has a different set of direction and federation partners.

Such examples are:

  1. Windows Azure public cloud services – These services compete directly against VMware vCHS public cloud services.
  • Microsoft’s Azure started off as PaaS (Platform as a Service) with providing custom .NET application hosting and SQL database service. Azure then added many more IaaS (Infrastructure as a Service) services to their offering. These are such as: Virtual Machine hosting, Backup, AD, Storage, Web sites, and a Service Bus. Azure is making inroads into bridging on premise with public cloud, but the transition is yet seamless.
  • VMware’s vCHS (vCloud Hybrid Services) is primarily a IaaS service providing seamless transition from on premise to public cloud. VMware is slowly adding PaaS service for custom application hosting.
  • VMware also offers the customer the choice of service providers, whereas Microsoft only offers Azure through their own hosting facility.
  1. Microsoft has virtualization technologies that are based on Windows Server, Hyper-V and System Center. These technologies compete directly against our federation story and solutions with VMware.
  2. Microsoft is advising customers to steer away from SANs and intelligent arrays, and towards DAS (Direct Attached Storage). This guidance is based on the fact that Microsoft has added high availability into their applications (Exchange and SQL) and intelligent storage services into their software (Storage Spaces and ReFS).

Microsoft however is hedging its bets by providing technology into their software that will leverage and take advantage of shared intelligent storage.

  1. ODX (Offloaded Data Transfer) – This provides the offloading of storage functions to array and takes the load off of the server.
  2. SMB 3.0 – This provides a robust file transfers protocol for CIFS and allows for critical workloads to leverage NAS.

Partnership

EMC and Microsoft have a long standing and mutually beneficial relationship. This relationship is formalized as EMC being a Microsoft “Global Alliance Partner”. Together EMC and Microsoft provide Industry leadership in cloud computing and IT Transformation.

There are several areas that show the commitment to this partnership:

  1. EMC has engineers and hardware in lab at Microsoft’s headquarters in Redmond, WA. In addition, EMC has hardware and staff at the Microsoft Technology Centers (MTC) located in various cities across the US and globally. The MTC’s are used in customer engagements for Envisioning, Architectural Design, and POC’s
  2. EMC and Microsoft have a Cooperative Support Agreement that facilitates technical support between the companies on behalf of the customer. The customer will need to open a service ticket with both tech support organizations, and then the two companies will work together to resolve the customer’s issues.
  3. EMC actively integrates Microsoft technologies into EMC technologies, and typically releases the solutions first to market. EMC has over 300 published technical solutions and another 100 data sheets on Microsoft technologies.
  4. EMC offers VSPEX Proven Infrastructures for the Microsoft stack, including: Virtualized Exchange, Virtualized SQL, Virtualized SharePoint, and Microsoft Private Cloud (converged infrastructure for Hyper-V and System Center).
  5. EMC Consulting has a very large global consulting practice for Microsoft technologies.
  6. EMC has created a Microsoft centric community site that is open to partners and customers. This site contains whitepapers, EMC Proven Solutions for Microsoft, videos, case studies, and open discussion threads on EMC/Microsoft solutions (www.emc.com/everythingmicrosoft).

Conclusion

As a Microsoft Certified Partner (with 16 competencies and a 21-time Partner of the Year winner), EMC offers our joint customers expertise and technologies to confidently integrate their Microsoft applications with EMC solutions. EMC and Microsoft have programs and solutions that can accelerate customers to transform their IT to private clouds, and provide IT as a Service. EMC is committed to the Microsoft platform and ecosystem, and actively continues to add value by added functionality, solutions, and leadership.

Even though the two companies compete in several areas, every customer of EMC has Microsoft in their environments to some degree. It is imperative that we talk to our customers about their Microsoft applications and communicate EMC’s value for Microsoft.

TechEd2014 : Azure Storage

Recap of my session at Microsoft TechEd 2014 – Microsoft Azure Storage

Azure Storage is a cloud based storage offering which is hosted in 16 regions across the world.

Links:

blogs.msdn.com/b/windowsazurestorage

azure.microsoft.com/storage

Azure Storage offerings:

1> BLOBS

  • An object store for unstructured data
  • REST API access only
  • Flat namespace
  • Up to 60 MB/sec throughput

  • Up to 1TB/BLOB

  • Charged by storage actual consumption

2> Disks

  • Network mounted virtual disk (inside of Azure for Azure-based VMs)
  • Stored in BLOB
  • up to 1TB Disk
  • Max 8KB IOPS – 500 IOPS
  • Snapshot and copy
  • Up to 60MB/sec throughput
  • Disks are exclusive to a single VM

3> Tables

  • noSQL cloud store
  • Odata protocol (AtomPub or JSON)

4> Queues

  • Reliable messaging system
  • Low latency, high throughput

5> Files (new offering as of May 2014)

  • Azure File Share – SMB and REST
  • SMB 2.1
  • Up to 5TB File Shares
  • Up to 1TB file
  • SMB 2.1, access only available within region, otherwise use REST
  • REST accessible from within Azure and from Internet
  • True directory structure
  • Up to 60 MB/sec throughput per share
  • Charged based file size
  • Can’t boot VM’s off of Azure File
  • Max 8KB IOPS – 1000 IOPS

Azure Storage Protection options:

LRS – Local Redundant Storage –

3 copies within a zone (facility)

ZRS – Zone Redundant Storage (for block BLOBs only)

3 copies between zones but within the same Region

GRS – 6 copies of data across two regions (3 in each region) – Async consistent

Read-only access to GRS

Read-only access to secondary data even if primary in unavailable

Strongly consistent within the primary region

Eventually consistent across regions

All writes go to primary

Azure import/Export

Move Tbs of data into and out of Azure BLOBS by shipping disks

Encrypted with BitLocker

Azure Copy for files

Utility to copy files into Azure Files (via REST API)

Tools and libraries:

Client libraries

.NET, Java, C++

Powershell commands

CLI tools

 What’s coming:

iOS library

Javascript

Zone redundant storage for BLOBs