230 likes | 625 Vues
VERITAS Replication Exec Product Overview. Exchange and SQL Applications. Life-blood of business activity for many organizations Any downtime cannot be tolerated Only backed up to tape once a day Untimely restore Outdated replica Exposure to loss in the event of server loss.
E N D
Exchange and SQL Applications • Life-blood of business activity for many organizations • Any downtime cannot be tolerated • Only backed up to tape once a day • Untimely restore • Outdated replica • Exposure to loss in the event of server loss
Replication Exec • Provides continuous data protection of Exchange and SQL • Replicates application data in real-time to secondary server • Maintains consistent record with up-to-the-second accuracy • Enables recovery of application with minimal downtime
How Replication Exec Works • Copies files from the application server to a secondary server • LAN or WAN connection • Data is replicated in real-time as it gets created or changed • Replicates only changed portion of files at the byte level • Updated data is highly available if application server fails
Key Benefits • Minimizes downtime due to application server failure • Minimizes data loss following application server failure • Enables seamless migration for application server upgrades
Failing Back • Primary server is repaired • Secondary server has updated information • Create “reverse” replication job to update Primary Server • Create job with Secondary Server as the Source and Primary Server as the Target
Configuration 1 Primary SQL / Exchange Server Standby SQL / Exchange Server* LAN or WANConnection 1 • Initial synchronization • Consistent replica created on standby server 3 4 *Version of SQL or Exchange must be the same on both servers
Continuous Protection for SQL Servers Primary SQL / Exchange Server Standby SQL / Exchange Server LAN or WANConnection • Data is continuously protected • Whenever data is created or changed • Only changed portion of data gets replicated • Up-to-the-second accuracy 3 3 4
Standby ApplicationServer Continuous Protection for SQL Servers Primary Application Server X • If Primary Server fails • Standby server can be quickly brought online • Minimizing downtime 3 4
Continuous Protection for SQL Servers Repaired Primary Server Standby Server • Once Primary Server is repaired • Primary server is update “Reverse” replication job gets it updates • Minimizing data loss 3 4
Continuous Protection for SQL Servers Application Server File Server LAN or WANConnection • SQL data can also be replicated to a File Server • If Primary Server fails • New SQL Server is brought online • Updated data is copied from File Server to new SQL Server 3 4
Continuous Protection for SQL Servers SQL Server File Server LAN or WAN • Pros and Cons • Eliminates need to purchase additional SQL Server license • Downtime is greater than having a standby SQL Server 3 4
Planned Migration SQL Server 7.0 SQL Server 2000 LAN or WAN • Planned Migration • Seamless migration for SQL or Exchange upgrade • Target server must be the same release or newer 3 4
Flexibility and Efficiency • Select how data gets replicated • Continuous or Scheduled • Select what data gets replicated • Only relevant files • Support variety of replication topologies • One-to-one, one-to-many, many-to-one • Maximizes network efficiency • Replicates only changed data • Bandwidth throttling • Protects open files
Ease of Use • Simple and intuitive interface • Same look and feel as Backup Exec • Centralized management • Wizard-Based Installation • Push deployment • Automated replication • Minimal administration required
Pricing • Each server involved with replication requires a license
Qualifying Questions • How are you currently protecting SQL and Exchange applications? • How much downtime would you have if a SQL or Exchange Server failed? • How much downtime can your business tolerate? • Would you like continuous protection for your SQL and Exchange Servers?
NSI Double-Take Failover Feature • NSI likes to tout “automated failover” • Only a “light failover” • Only automates IP address failover • Not complete failover like VCS or MSCS • Replication Exec can perform similar functionality with minimal scripting • “Light failover” adds complexity and cost • While providing minimal value • What does IP address failover entail?