Netapp Snapmirroring And Its Scope In Eircomnet: By Dba Team, Eircomnet

NetApp SnapMirroring

NetApp SnapMirroring and Its Scope in Eircomnet By DBA Team, Eircomnet © eircom

NetApp SnapMirroring

- Background - What is SnapMirroring? - SnapMirroring Usage - Scope of SnapMirroring In Eircomnet - Various Models - Next Step - Q&A © eircom

NetApp SnapMirroring

- Background Current Scenario -

Database Backup takes hours to complete

-

Backups are taken once a day

-

Recovery Time and Process is a Complicated & Time Consuming Task

-

Maintaining Test & Development environment is a Complicated & Time Consuming Task

-

No Provision for Load Balancing

-

No Provision for Data Replication

Ideal Scenario

© eircom

-

Database Backup on different geographical location can be completed in seconds

-

Database Backups can be taken as many times as required

-

Recovery Time and Process is a Simple and Quick Task

-

Maintaining Test & Development environment is a Simple & Quick Task

-

A Flexible System where Multiple Systems can be maintained without impacting the performance & availability

NetApp SnapMirroring

- SnapMirroring Technology - Replicates file system from one NetApp Storage to another - Replication can be made at Volume or Qtree level - Two filers can be at different geographical location - Files/Data is replicated using NetApp Snapshots - Replication can be Synchronous, Asynchronous or Mixed of both - Synchronous Mirroring replicates data on change basis -

As and when any change is spotted at the source filer it is immediately replicated across the target filer. The changes are scanned at the block level

- Asynchronous Mirroring replicates data on fixed intervals -

A snapshot taken at fixed interval is compared to the previous snapshot and the difference is replicated across the target filer

- Mirroring is intialized by copying the entire Source Vol to Target Vol -

© eircom

Once initialization is complete, replication events thereafter copy only changed blocks from the source volume to the target volume

NetApp SnapMirroring

- SnapMirroring Usage - Disaster Recovery Solution - Data Replication - Database Cloning - Load Balancing - Test & Development Environment

© eircom

NetApp SnapMirroring

- SnapMirroring Scope In OBSS - Disaster Recovery Solution -

Traditional Backups (copying datafiles) can be replaced completely. Backups through SnapMirroring are quick, flexible and neglegible resource consuming. Multiple Backups on different filers (same or different locations) can be maintained. Immediate availability of backups, Restore & Recovery process is in seconds.

- Data Replication -

Multiple copies of the data can be maintained with neglegible impact on the performance Data can be maintained across different filers at the same or different locations Specific data (partial or selective data) can also be maintained across different filers

- Load Balancing -

Specific data can be replicated across different filer to be accessed by separate server

- Standby Database -

Standby database can be maintained by replicating only ‘Archived Logs’ across the filer linked to the Standby Database

- Test & Development Environment -

© eircom

SnapMirroring is best suitable for maintaining the Test & Development environment Refreshing the test or development environment is a simple & matter of few seconds

NetApp SnapMirroring

- Backup Model

© eircom

NetApp SnapMirroring

- Standby Database Model

© eircom

NetApp SnapMirroring

- Load Balancing Model

© eircom

NetApp SnapMirroring

- Multi Database Servers Model

© eircom

NetApp SnapMirroring

- Next Step

Scope of SnapMirroring On New CMS Environment

© eircom

NetApp SnapMirroring

- Existing Proposal

© eircom

NetApp SnapMirroring

- New Proposal:

© eircom

NetApp SnapMirroring

- Next Step:

© eircom

NetApp SnapMirroring

-Q&A

© eircom