VERITAS Storage Replicator

1. VERITAS Storage Replicator Protect Your Remote Office Data

2. WAN VERITAS Replication Technologies Remote office data protection MAN/WAN Disaster Recovery MAN Remote Mirroring over Fibre Channel:Volume Manager Replication over IP:Volume Replicator Backup Centralization:Storage Replicator

3. Key IT Issues for Protecting Remote Office Data • Greater emphasis placed on disaster recovery and data protection of all data • Backup is the foundation for any viable DR plan • Organizations tend to invest heavily in protecting their headquarters data • Little emphasis placed on protecting remote office data • Limited staff • Limited backup administrators at remote offices • Need centralized control for consistency and guaranteed protection • Limited Budget • Lack of IT budget for remote office data protection resources including hardware, media and administrators

4. Centralized Management ROI • Reduce hardware media investment • No longer need tape drives at remote locations • No longer need media at remote locations • Reduce resource investment • No longer need administrators at remote locations managing backup process • Allow central administrators to manage more data

5. VERITAS Storage ReplicatorArchitecture • Replicating remote data to central location • Eliminate tape drives and backup software in remote offices • Centralize all backups for easy management • Provide greater protection of remote data assets Install VSR Client agent (RSA) on all servers Install NetBackup or Backup Exec Client agent (NBA) on Target servers RMS Remote Sites (Branch offices, Source servers) Replicateremote sites to Datacenter Firewall Backup Target servers to tape ‘Across the WAN Tape storage Datacenter(Clustered Target servers)

6. VERITAS Storage Replicator Product Overview • Easy to use real time file-based replication for Windows NT, Windows 2000, Windows 2003 and MS Powered • Scalable • 100 nodes in a replication domain and thousands of tasks in each replication domain • Flexible • Pick and choose what data gets replicated • Support for wide variety of replication topologies including one-to-one, one-to-many, many-to-one • Bandwidth throttling • Scheduling of replication • Replication of open files • Easy to use • Windows based GUI, central management and reporting • Wizard-based installation • Push deployment

7. VERITAS Storage Replicator Product Overview • Asynchronous Replication • Replicates only changed data • Cost effective use of network resources • Replication can occur without affecting application performance • Data Consistency • Target host(s) receives data in the same order as it was created on the source host • Restore files quickly over the wire to remote locations • Integration • Tested with VERITAS NetBackup and VERITAS Backup Exec • Supported with VERITAS Cluster Server and Microsoft Cluster Server to make replication services highly available • Available in English and Japanese

8. Why use VSR for Backup Consolidation? • File-based replication matches up very well with file based backup • The replication selection rules can map one-to-one to the backup selection rules so only the data being backed up is replicated • Data on Target is readable and can be backed up without stopping Replication • Restoration to the Source can take place without stopping replication • VSR is compatible with Open File Managers so file system snapshot backups can be made • Multiple Sources can replicate to the same consolidated Target volume simultaneously • Target drives can be completely different shape than Source • VSR helps off-host backup all enterprise Windows servers regardless of the shape and size of the file systems

9. Why use VSR for Backup Consolidation? • All meta-data is preserved for the replicated files • Archive bit is special – the archive bit is ignored during synchronization • Pre- and Post- Job scripts can help facilitate backup jobs • Replication Modes: • Continuous replication: Transferring changed data to central location as it is being modified which reduces the network spike • Scheduled: Can be configured to replicate at specific time intervals, for instance when the network usage is low • More complex scheduling can be accomplished via an external scheduling engine or choice and the use of srTool to start and stop jobs • In all cases, VSR will only transfer changed data

10. VSR OverviewInstallation and Management is easy • Installation is easy • Standard Windows installation wizard • RMS (the master server) is detected during install • RSAs can be remotely installed from any VSR Console. Push-deploy will even optionally reboot the remote machine • New RSAs appear automatically in all administrative consoles • Job Creation is interactive and simple • All jobs can be created from the native Windows console • The Jobs Wizard walks the user through all the steps necessary to create a properly configured job • Jobs can be edited and changed in the Console • Jobs can also be created via the command line tool and can be created in scripts (Perl, etc.) • Job and System Monitoring is easy • The Console provides a place to view all alerts • Replication activity can be viewed on every active pair • All logs (Server, Job and Replication Pair) are available through the console

11. VSR OverviewSecurity • VSR uses Windows native security • VSR does not implement any security functionality – it relies completely on the Windows Domain security • VSR requires users to have Backup rights on the RMS machine • VSR requires users to have Backup rights on every server being added to a Job • Administrator rights are required to push-install an RSA to a remote machine • An administrator at a Console can provide alternate credentials to access machines that the currently logged in user can’t access • By default the replication services run as Local System and can therefore access all data in the file systems • The replication services can be changed to run as a specified user with at least backup rights

12. VSR: Basic Definitions and Components

13. VERITAS Storage ReplicatorComponents • VSR is composed of three main components: • Replication Management Server (RMS) • Replication Service Agent (RSA) • Administrative Console • Clustering Agents: VCS and MSCS • Accessory Programs: • Status Applet: Used for monitoring without having the entire console displayed • srTool: Command line interface • Configuration Estimator: Helps analyze the replication needs and the amount of bandwidth needed to effectively replicate

14. Basic Definitions & ComponentsReplication Management Server (RMS) • Contains configuration data for the replication system • Drives the replication process according to the configuration settings administered from the console • Manages: • Job configuration information including start and stop • Server information • Logs • Alerts • Historical information • Why is the RMS important? • Replication system integrity is only as good as your network connections and your RMS. • It needs to be available 24x7 • Replication can continue between RSA’s if the RMS goes down • It is highly recommended that the RMS is clustered with VCS or MSCS • It is recommended that you install an Uninterruptible Power Supply (UPS) to guarantee availability, and that you back up this server regularly. • There is only one RMS per Replication Neighborhood

15. Basic Definitions & ComponentsReplication Server Agent (RSA) • A Server in a Replication Neighborhood that can act as a Source or Target (or both) in Replication Jobs • RSA is responsible for doing the actual data replication between servers • The RMS is responsible for starting and stopping replication • The RSA service must be installed on all machines that are to take part in replication. • An RSA belongs to only one Replication Neighborhood and is controlled by only one RMS • The RMS is also an RSA • Management and monitoring can be done from any node in the Replication Neighborhood • The RMS must have the RSA service running on the server it is installed on in order to operate. • The RSA software can be installed on the server itself from the product CD, or it can be installed from the Console, over the network. • Every RSA gets the Console and srTool installed by default

16. Basic Definitions & Components Administrative Console • The Administrator Console is your interface to the configuration and replication processes. You can use it to: • Deploy and enable servers for replication • Install the RSA to a remote machine • Create, modify, view replication jobs • Set rules for including or excluding files, folders or volumes • View the status of all replication Servers within a Replication Neighborhood • Control replication scheduling • View logs and alerts • Getting help on using VSR

17. Basic Definitions & Components Clustering Agents • Makes replication components highly available • Available for VERITAS Cluster Server (VCS) or Microsoft Cluster Server (MSCS) • It is an optional feature that can be installed after both the clustering software (VCS or MSCS) and VSR have been installed and configured • RMS Agent: Designed to make the RMS highly available • Job Agent: Designed to support the failover of a primary Job server to a secondary server.

18. Basic Definitions & ComponentsReplication Neighborhood • Replication Neighborhood • A named collection of RSAs and one RMS • All replication takes place within a Replication Neighborhood • The neighborhood name is selected at installation time and is not changeable • The Replication Neighborhood can cross NT Domains • The Replication Neighborhood can cross subnets

19. Basic Definitions & ComponentsReplication Job • Basic unit of replication management for VSR • Each Job contains: • A Schedule (can be empty) • Replication Servers • One Source Server and one or more Target Servers • -OR- • One Target Server and one or more Source Servers • Each Source/Target in a Job make up a “Replication Pair” • Job Options • Pre-scan • Target Protection • Exact Replica

20. Basic Definitions & ComponentsReplication Pair • Replication Pair • One Source and one Target Server in a Job • There can be multiple Replication Pairs per Job • The Replication Pair contains: • Selection Rules – what files get replicated from the Source Server to the Target Server • Redirection Rules – where the files go on the Target Server • Network Utilization Limits – the ability to use only a subset of the available network connection between the source and target (Dynamic Replication Only) • Pre- and Post-Script commands • The relationship between any two servers in a Replication Pair is unique to a particular Job

21. Accessory ProgramsStatus Applet andsrTool • Status Applet: Intended for administrators and job operators to be able to monitor servers, jobs and alerts and to start and stop jobs only. • srTool is a “shell” program that runs in a Command Prompt (cmd) window and allows the administrator to: • Create, • Configure • Control replication jobs without using the Console • srTool incorporates a powerful command language that enables administrators to easily automate many complex administrative tasks • Can be used to pull out more detailed information about your system • Use it to place commands into pre- and post-script files for customized processing of VSR jobs.

22. Accessory ProgramsConfiguration Estimator • Tool developed to analyze the amount of bandwidth needed to efficiently and effectively replicate data • Simple to use application • Native Windows application • Runs without installation • Wizard based • Walks you through the issues and asks the right questions • Provides estimates on the environment for moving data across various types of networks (10mb, 100mb, Gigabit, T1, T3, etc). • The tool will tell you immediately if the data will fit through the pipe and how long it will take • This is a best-case tool. If the network is shared or if optimistic inputs are provided then it will not be accurate

23. Configuration Estimator

24. Configuration Estimator

25. Configuration Estimator • Summary:

26. Configuration Estimator • Final Output:

27. Exchange Replication with Storage Replicator

28. VSR and Exchange:Whitepaper Available • VSR Exchange 5.5 and 2000 Whitepaper • Describes using VSR for both: • Graceful Migration of Exchange Servers • DR protection of Exchange Servers • Paper is available on the both the internal and external web sites • Internal: http://products.veritas.com/products/high_avail/storage_rep/docs/pdf/vsr_exchange_5_5_2k_wp.pdf • External: http://eval.veritas.com/downloads/pro/vsr_exchange_5_5_2K_wp.pdf

29. How Exchange Data is Stored • Mailbox Data • Mailbox Data is the individual user’s mailboxes. This data is stored on-disk in a database named priv.edb. • Public Folder Data • Stored on-disk in a database named pub.edb. • Exchange Organizational Data • Exchange 5.5 • Stored on-disk in a database named dir.edb. • Exchange 2000 • Stored in the Active Directory data repository.

30. How Exchange Data is StoredTransaction Logs • Exchange Transaction Logs • Exchange uses transaction logs for playback during server recovery • The logs need to be replicated with the normal data • Each version stores the logs in different places: • Exchange 5.5: mdbdata\edb.log • Exchange 2000: dsadata\edb.log • As logs fill (5MB each) they are renamed to a numbered sequence of files named edb<xxxxx>.log

31. VERITAS Storage ReplicatorReplicating andAccessing Exchange Data • Moving Exchange Data is all about the Server Name • The Exchange Server Name is encoded in the Exchange database files. This makes it impossible for Exchange on a backup or stand-by server to open these databases without doing some significant work. • Adjusting (hacking) the database files to contain a new server name is not possible. • Exchange 2000 stores the server identity in the Active Directory. So how do you use Exchange data on a different machine? You can’t so you must: • Make the replication Target look like the Source machine • With Exchange 5.5 this involves changing the name of the machine on the network • With Exchange 2000 clustering software can be used with Active Directory to virtualize the name the Exchange server (tested with MSCS, VCS research still ongoing)

32. VERITAS Storage Replicator Installation Overview • Install the Replication Management Server (RMS) first • Installing the RMS is the key to the replication system • Needs to be installed first because every server in the replication neighborhood needs access to the RMS • Only one RMS per replication neighborhood • Install the Replication Service Agent (RSA) • Can be installed on local machine or across the network to a remote machine • Install the Console • Console is the human interface to the replication process • Install as many consoles as needed but each console works in only one replication neighborhood

33. RMS NT 4.0 or higher, with Service Pack 4 or greater (Windows XP is not supported) Continuous availability on the network Network card and connection 64 MB of RAM 25 MB of disk space Minimum 100 MB of disk space for database RSA Server class machine with Pentium 90 or greater NT 4.0 or higher, with Service Pack 4 or greater Network card and connection 64 MB of RAM Minimum 100 MB of disk space for journals Additional disk space for replica on target (at least 10% more then on source) Replicated volumes must be NTFS Console Monitor with 256 color display, 800x600 pixels minimally, optimally set to 1024x768 or greater Mouse or trackball 64 MB of RAM 23 MB of disk space Installation of components on the same machine: Windows NT4.0 Service Pack 5 or greater (Windows XP is not supported) Network card and connection 64 MB of RAM 25 MB of disk space for software installation of RMS, RSA and Console 100+ MB of disk space for logs and alerts The console requires both Service Pack 5 on NT 4.0, and IE 4.0 or higher to display some of the help content. (The main help files are available without IE.) VERITAS Storage ReplicatorHardware Requirements

34. VERITAS Storage ReplicatorFrequently Asked Questions • Does VSR support replication between different versions of the Windows operating system? • Yes, VSR supports the replication between Windows operating systems as long as the replication is upward. • So, VSR can replicate from NT 4.0 to NT 4.0, Windows 2000 to Windows 2000 and NT 4.0 to Windows 2000. However, Windows 2000 to NT 4.0 is not supported. • What files are not replicated with VERITAS Storage Replicator? • Reparse Points: Reparse points can be used to produce files that are visible in Explorer as if those files were present on the disk. However, what is present is a reference to a file located in another location. Since VSR can't replicate the actual data these are not supported. • Encrypted Files: VSR does not replicate encrypted files because once Windows 2000 encrypted data is replicated to another machine, no standard de-encryption method can restore the data.

35. VERITAS Storage ReplicatorPackaging • Server Edition • VSR Product Installer: (English and Japanese) • RMS • RSA(s) • Console • srTool • VCS Agent (English and Japanese) • Job and RMS • Advanced Server Edition • VSR Product Installer: (English and Japanese) • RMS • RSA(s) • Console • srTool • MSCS Agents: (English and Japanese) • Job and RMS

36. Thank You