Distributing File Data with Snap Enterprise Data Replicator (Snap EDR)

Transcription

1 TECHNICAL OVERVIEW Distributing File Data with Snap Enterprise Data Replicator (Snap ) Contents 1. Abstract Introduction to Snap Product Architecture Distribute Data Management Tool Default Functionality System Setup and Software Installation Installing the Snap Management Console Software Installing Snap Agents Configuring Schedules Monitoring Performance Viewing Job Statistics Viewing the Job Log Files Verifying Performance Report Types Best Practices Bandwidth Requirements Directory Configuration on Remote Nodes Permissions Selection Platform Choice Use of Compression Delivery Mode Synchronize Source and Targets Conclusion Abstract This white paper provides an overview of the Snap product, and details the components and configuration of a Snap Distribute solution. This solution allows users to schedule a job where files are transferred from one source machine to one or more target machines on the following platforms: Snap Servers powered by GuardianOS, Windows clients, and UNIX/Linux clients. Common business needs for distribution of file data include, but are not limited to, the following: Sending updated price lists to branch stores Delivering product manuals to widely-dispersed customers Sending source code Sending/synchronizing standard corporate legal documents 2. Introduction to Snap Snap includes three Data Management Tools to automate the secure flow of data between systems: The Aggregate tool allows jobs to be scheduled to transfer files from multiple agents to a single target agent The Distribute tool allows jobs to be scheduled to transfer files from one source machine to one or more target machines The Replicate tool allows jobs to be scheduled to transfer files between two systems Snap also includes the Advanced Data Management (ADM) Suite that groups together the functionality of Remote Inventory, Remote Archiving, and Remote Backup and Restore. These solutions provide exceptional functionality to create and deploy policies for solving remote data management problems such as variability, dissimilar computing platforms, security needs, and data integrity. The Advanced Data Management Suite performs the following tasks: Inventory, to determine storage utilization Archive, to move selected data for permanent archive Backup, to protect data Restore, to recover backup data Separate white papers provide details on the Aggregate and Replicate tools and each tool in the ADM suite, and are available from the following location:

2 Distributing File Data with Snap Enterprise Data Replicator (Snap ) 2 3. Product Architecture Snap consists of a Management Console that is installed on a Snap Server powered by GuardianOS, and a collection of agents running on the other servers/workstations involved in the transfer. The Management Console coordinates and logs the data transfer activities carried out by the distributed agents. The Snap agents are responsible for the actual transfer of data. Users access the Management Console using a web browser that allows them to configure Snap and create data transfer jobs from any location. The following diagram shows an example of a Snap solution: MANAGEMENT CONTROL INTERFACE SERVER Control Data Movement IP Network Figure 1: Snap Architecture The Administrator logs into the Management Console to create and configure jobs through this interface. The Management Console then communicates with the Snap agents involved in the job, and the agents transfer the data to the appropriate machine(s). The Management Console logs the transfer activity, and allows the user to view these logs and reports. Note that the flow of control and data movement illustrated above differs depending on the type of transfer one has created. In some cases, users may want to transfer data from a single source agent to one or more target agent(s) (called a "push" transfer). In other cases, users may want to transfer data from multiple source agents to one target agent (called a "pull transfer"). The distribution of data using Snap is a straightforward process involving the activation of the Snap agents on two or more machines, configuring the parameters of the distribution job (e.g., source and target directories, etc.) and scheduling the job. REMOTE UNIX SERVER REMOTE SERVER 4500 REMOTE LINUX SERVER REMOTE WINDOWS SERVER 4. Distribute Data Management Tool The Distribute data management tool allows users to schedule a job where files are transferred from one source machine to one or more target machines. The target agent can start up to four independent TCP streams (i.e., up to four files will be transferred simultaneously) Default Functionality The Distribute data management tool has the following default functionality: File transfer from one source to one or many target agents Cross-platform support Option to exclude files from transfer Option to exclude directories from transfer By default, any files that are in use during the transfer will be skipped without error. This allows users to transfer common files from a central repository. Users can set information in the following categories: Source agent selection Target agent selection Directory and file selection File transfer options (such as file compression, certified delivery, source and target synchronization, etc.) Schedule notification 5. System Setup and Software Installation The Snap system requires users to install the Management Console that coordinates and logs the data transfer activities of the distributed agents. The Management Console should be installed on a Snap Server powered by GuardianOS. Users can install the agent software on a GuardianOS-based Snap Server, Windows, or UNIX/Linux system involved in the data transfers. Installing and configuring the Snap software involves the following procedures: Installing the Management Console software on a Snap Server Installing Snap agent software on Snap Server, Windows and/or UNIX/Linux system Note that Snap installs only on GuardianOS or higher. Once the software is installed, users can login to the Management Console and configure and schedule distribution jobs Installing the Snap Management Console Software Note: Only one Management Console should be configured to handle all of the agents in your Snap replication environment.

3 Distributing File Data with Snap Enterprise Data Replicator (Snap ) 3 Install the Management Console through the browser-based Administration Tool for the Snap Server. For detailed procedures on how to install the Management Console software, refer to the product documentation Installing Snap Agents Snap agents are responsible for the actual transfer of data. An agent is installed automatically on the Snap Server that is designated as the Management Console. The Snap agent software must be installed on each remote node in the system that will be part of the Snap data replication environment. Users can install a Snap agent on any Snap Server, Windows, or UNIX/Linux system that meets the following requirements: Item Operating System System Memory Disk Space Description Snap Server with GuardianOS v or higher AIX 4.3, 5.1, 5.2 Solaris 5.7, 5.8 HP-UX 11.x, 11i Fedora Linux, RedHat Linux 7.2/7.3, Enterprise Linux 2.1 or 3.0 or SUSE LINUX 8.2 and 9.0 Windows 2000 (with SP2 or higher), Windows 2003, Windows Server Appliance Kit (SAK) 2.01, or Windows XP 128 MB or more Windows systems: 5 MB or more UNIX systems: 5 MB or more Installation directory: 100 MB, 20 MB free in /tmp on all platforms Network Connection 100 Mbps Ethernet or faster OR a WAN connection capable of supporting the throughput required to meet the volume and window of time requirements For detailed procedures on installing the Snap agent software on a Snap Server, Windows, or UNIX/Linux system, refer to the product documentation. Figure 2: Management Console Snap provides a straightforward interface to schedule a distribute job by clicking on the distribute menu item on the left side of the screen. The Distribute configuration and scheduling screen is similar to the following: 6. Configuring Schedules Once Snap has been installed, login to the Management Console to configure the Distribute Data Management tool to schedule the type of distribution job desired. Login to the Management Console, and the following screen appears, displaying a menu on the left-side that allows users to schedule a variety of jobs (aggregate, distribute, backup, replicate, and so on), install agents, change user preferences, run maintenance tasks, generate reports and view transfer logs: Figure 3: Distribute Job Creation Screen When creating a job, users can specify the source and target agents, which directories to exclude, file ownership preservation and so on. For detailed instructions on creating a Distribute job, see the product documentation.

4 Distributing File Data with Snap Enterprise Data Replicator (Snap ) 4 7. Monitoring Performance There are a number of ways a user can monitor the performance of a job, including the following: Viewing Job Statistics Viewing the Job Log Files 7.1. Viewing Job Statistics When a job that has run to completion is clicked on, the screen displays the job s statistics, including information such as the start and end time of the job and whether or not the job ran successfully. The Scheduled Job View screen also allows access to Console functions where other tasks can be performed with the scheduled job. These tasks include manually running a job and viewing past log files. The following is a sample of the Job View screen: Figure 5: Job Log Screen This summary displays messages about the data transfer, and is generated by the Management Console and the agents while the job is running. These messages vary in severity, from simple information messages (e.g., starting group: Distribute (sequential)), to warnings (e.g., Preserve ownership may fail for target 'snap01' because the system types are different. ), to errors and debug messages. These messages are useful for evaluating the job run. Click the Filter button to change the type of log information displayed or to download the job log file to your local machine. Downloading the file allows you to load it into different programs (for searching, printing and so on). The log file is a plain text file. Figure 4: Job Statistics Screen Exit codes appear in the Exit Code column in the list of job runs. An exit code indicates whether or not a job completed successfully, and if there was an error, the type of error that occurred. A 0 exit code indicates that the job completed successfully. For a description of what each non-zero exit code means, click more info beside the exit code in the Exit Code column of the job screen, or refer to the product documentation Viewing the Job Log Files Whenever users run a scheduled job, the Management Console generates a log file. When a job is clicked on, the job's display area shows log files for the most recent run and up to ten previous job runs. If there are more than ten job runs, the oldest job log is deleted to allow space for the latest job log. Clicking on the word view beside any past job run displays a detailed log summary for that particular job run: 8. Verifying Performance The Management Console creates statistical records for each completed job run and stores them in the rules database. Using the Management Console, users can generate a number of different types of reports to evaluate the operation of each job Report Types Using the Management Console, you can generate the following types of reports: Report Type Stats Summary Report Detail Report Custom Query Report Description Provides a summary and totals of the data from all jobs in the selected job group (all distribute, aggregate and replicate jobs are in the Published_Solutions job group), based on how the user chooses to group the data (by month, day, etc.). Provides a detailed record of the data from the selected job group (all distribute, aggregate and replicate jobs are in the Published_Solutions job group) Note that the number of records the report displays depends on the number of agents on which the job runs. The report displays a record for every agent on which the job runs. Provides a customized query of detail records from the job name within a selected job group (all distribute, aggregate and replicate jobs are in the Published_Solutions job group). Note that the number of records the report displays depends on the number of agents on which the job runs. The report displays a record for every agent on which the job runs.

5 Distributing File Data with Snap Enterprise Data Replicator (Snap ) 5 Template names can be assigned to created reports. The template appears in the Report view. Report templates allow you to generate reports without having to change the initial parameters. Templates are especially useful for generating the same type of report on a regular basis. Run, Edit, Remove or Schedule a report by clicking on the appropriate word beside the report template. Click Schedule to run reports daily, weekly, or monthly at specific times. The following diagram is a sample of a Stats Summary Report: Use the following equations to manually calculate bandwidth requirements: Sender bandwidth Mbps=(MB to transfer*8)/(avail. Hrs for Distribution *3600) Receiver bandwidth Mbps=Sender bandwidth Mbps * Number of Agents Example: Updated price lists need to be distributed nightly (between 6pm and 6am) to 100 locations. The maximum logsize is 1GB and each node that you are sending to has a T-1 (1.544 Mbps) network connection. The sending (source) machine has a T-3 connection (44 Mbps) Determine if the sender has enough bandwidth to send the data in the time required AND if the receiver has enough bandwidth to receive the data. Sender bandwidth Mbps=(MB to transfer*8)/(avail Hrs*3600) Sender bandwidth Mbps = 1000 * 8 / 12 * 3600 Sender bandwidth Mbps = 8,000 / 43,200 Sender bandwidth Mbps = Mbps (Each sender has sufficient bandwidth: Mbps < Mbps) Figure 6: Sample Stats Summary Report For detailed instructions on how to generate reports, see the product documentation. 9. Best Practices To obtain the best performance from the distribute job, consider the following issues: bandwidth requirements ("window of time" to transfer the data, and the volume of data) directory configuration on remote nodes permissions selection platform choice use of compression delivery mode synchronizing source and targets 9.1. Bandwidth Requirements To determine performance requirements for the distribution job, it is important to have the following information: Amount of data to be retrieved Amount of time available for the distribution Bandwidth of the most constrained segment of the network (can be either the speed of the network or a limit imposed by bandwidth throttling) Activity of the network at the time the job is run. If the network is busy, the effective throughput could be substantially less than during off-peak times. Receiver bandwidth required Mbps=Sender bandwidth Mbps * Number of Agents Receiver bandwidth required Mbps=0.185 x 100 Receiver bandwidth required Mbps=18.5 Mbps (The receiver has sufficient bandwidth, as the required 18.5 Mbps is less than the available T-3 (44 Mbps).) To determine the maximum network performance to the receiver, perform a transfer of a single large file (i.e., 20 MB or more) across the same network using the same equipment and storage that will be used in production to the receiver. Ensure that the network performance exceeds required performance. Several network factors will impact the ability of the Snap agents to use all of the available bandwidth: network latency, packet drop rates, network congestion, etc. For these reasons, it is useful to perform test data transfers over the actual networks that will be used. IMPORTANT: This calculation would be an estimate of WORST CASE bandwidth requirements. The Snap software is optimized to make the best use of network bandwidth through features like in-stream data compression and byte-level incremental transfers. Therefore, for repeatedly transferring files that change only by a small amount, the bandwidth required might be very small for transfers that are not the first time transfer. Although a T1, for example, claims a throughput of Mbps, it is an absolute BEST CASE number. The effective throughput is much less, and an accurate throughput number can be determined ONLY by running the test suggested previously under the SAME conditions when the distribute job is intended to run.

6 Distributing File Data with Snap Enterprise Data Replicator (Snap ) Directory Configuration on Remote Nodes When running a distribute job using hosts on multiple platforms, users must ensure that the same directory is being used on each host, or run separate jobs where the directories are different Permissions Selection The file ownership transfer option allows users to specify whether files maintain the source user ID and group ownership after they are transferred, and what method is used. Users can choose from the following options to preserve ownership: GuardianOS - When transferring between two Snap Servers powered by GuardianOS, ACLs are extracted and set using Snap Server-specific routines. ACLs are transferred only if both the source and target are Windows or if both are Snap Servers running on GuardianOS. If no match is found, a warning is generated. ACLs without matches are dropped. When transferring between Windows, UNIX, Linux, or GuardianOS, user name matching is done for the owner and group regardless of the source and target OS type. Owners and groups without matches are replaced with the transfer user (root on UNIX, system on Windows, or UID 1 on GuardianOS). Inherited ACLs are not explicitly copied between Windows machines. For example, a file that inherits its ACLs from a folder on the source is transferred to a folder on the target that has different ACLs. However, the source folder is not transferred. In this case, the file's inherited ACLs on the target will come from the target folder into which it is transferred and not from the source folder. GuardianOS mode is the default mode of transfer. Windows - Preserves Windows SIDs in homogenous Windows environments. A security identifier (SID) is a unique value of variable length that is used to identify a security principal (e.g., user or security group) in Windows Well-known SIDs are a group of SIDs that identify generic users or generic groups - these do not change from system to system. In this mode, the security stream, and all other alternate data streams, are copied; inherited ACLs are explicitly copied. Use this option when transferring data between Windows hosts only. UNIX - Tries to match the usernames/groupnames found on the source and target systems. Used when transferring between Windows/UNIX/Linux/GuardianOS. The file ownership transfer capability may not work on some UNIX systems such as HPUX 11 and Solaris 7 that use Orange Book security standards. Off - Does not preserve ownership. The user ID specified in the target User ID field of this job template owns files written to the target. The file will be owned by root on UNIX, NT Authority/System on Windows and UID1 on GuardianOS. The following table provides a matrix for transfer of ownership, permissions, and attributes with Snap : Transfer Type Replicate, Aggregate, Distribute Tool Permissions Transferred Windows To Windows All Windows Windows to UNIX RWX, Owner, Group UNIX Windows to GuardianOS RWX(a),Owner, Group, Others Optimal Permissions Transfer Setting (c) GuardianOS GuardianOS to Windows RWX(b), Owner, Group, Others Windows UNIX to Windows RWX, Owner, Group GuardianOS UNIX to UNIX RWX, Owner, Group UNIX UNIX to GuardianOS RWX, Owner, Group UNIX GuardianOS to GuardianOS All GuardianOS (a) The read-only file attribute is mapped by setting permission bits to r--r--r-- for read-only files and rw-rw-rw- for all others. The execute bit is also set for folders and executable files (e.g., file suffix.exe,.com, etc). The system, hidden, temporary, encrypted and compressed attributes are dropped. The modified and accessed dates are preserved from the source. The create date is not preserved from the source (b) File owner, group, and other users are mapped. If the write permission mode bit is off for "all" on the source, the read-only attribute is set on the target. The system, hidden, temporary, encrypted and compressed attributes are set to "off " on the target. The modified date and accessed date are preserved from the source The create date is not preserved from the source (c) Optimal file ownership and permissions transfer is achieved when users are consistent across the servers involved in the data transfer, such as being in the same Domain. If not, Snap will try to match users based on the permissions transfer method selected. When using the file ownership transfer options for Windows, the backup job user must be a member of the Backup Operators group on the Windows hosts. As well, ensure that the backup job user has the following local security policies (the Backup Operators group may already be assigned to these security policies): Backup files and directories Manage auditing and security log Restore files and directories Note that as members of the Administrators group, Domain Admins automatically become members of the Backup Operators group.

7 Distributing File Data with Snap Enterprise Data Replicator (Snap ) Platform Choice Cross-platform transfer of file data is supported natively; however, to preserve permissions it is recommended that you distribute data between similar platforms (e.g., Windows to Windows and UNIX/Linux to UNIX/Linux) Use of Compression If the compression option is set to Yes, the source Agent(s) compresses each file in the data transfer stream before sending it. The files will be uncompressed automatically on the target Agent(s). The degree of compression depends on the type of data being transferred. The following are typical rates of compression for different types of data: Plain text: 70-95% TIFF images: 20-40% Binary files: 0-5% 9.7. Synchronize Source and Targets This option specifies whether the agent creates identical directory structures on the source and target nodes. If set to Yes, the agent deletes any files in the target directory structure that do not have a corresponding file in the source directory structure, and transfers any files from the source that do not have a corresponding file in the target directory structure. The default value is No. 10. Conclusion The Snap Distribute solution is a valuable and easy-to-use tool to distribute file data to a common location from multiple Snap Servers powered by GuardianOS, Windows, or UNIX/Linux servers. It provides a comprehensive solution for distributing file data from one or many remote sources to assist with common business needs for distribution in a variety of business scenarios. Generally this feature provides maximum benefit in WAN data transfers where bandwidth is limited (e.g., less than 3 mbits per second). Using this feature may increase CPU usage, and is not recommended on a local area network (LAN), since it may slow down the transfer Delivery Mode In considering the selection of a delivery mode, the first question to ask is whether a signed receipt of the delivery is required. If so, the certify file content option is the only mode that should be considered. The fast mode option will perform best when bandwidth is high-speed and highly available; however, check pointing of file data will not be used (i.e., if a transfer is interrupted the entire file will be retransmitted). In most local area networks, the fast mode option is the best choice. Fast mode should be used when writing to a NAS share and preserving ownership. Adaptec, Inc. 691 South Milpitas Boulevard Milpitas, California Tel: (408) Fax: (408) Literature Requests: US and Canada: 1 (800) or (408) World Wide Web: Pre-Sales Support: US and Canada: 1 (800) or (408) Pre-Sales Support: Europe: Tel: (32) or Fax: (32) Copyright 2003 Adaptec Inc. All rights reserved. Adaptec and the Adaptec logo are trademarks of Adaptec, Inc., which may be registered in some jurisdictions. All other trademarks used are owned by their respective owners. Information supplied by Adaptec Inc., is believed to be accurate and reliable at the time of printing, but Adaptec Inc., assumes no responsibility for any errors that may appear in this document. Adaptec, Inc., reserves the right, without notice, to make changes in product design or specifications. Information is subject to change without notice. P/N Printed in USA 2/ _1.1