White PapersThis white paper provides an overview of the Snap EDR product, and details the components and configuration of the Snap EDR Archive data management module. The Archive module allows users to remove selected data such as rarely used files from remote sites and store them at a central location. This frees up additional disk space on the remote agents. The Remote Archive module allows for two methods of archiving data:
• Remote Archive ShortCut (creates Windows shortcuts to the archived file for easy retrieval)
• Remote Archive Move (gives users the option to create version changes of an archived file)
These two methods are discussed in more detail laterin this document.
Snap EDR runs on the following platforms: Snap Servers powered by GuardianOS,Windows clients, and UNIX/Linux clients. Common business needs for archiving file data include, but are not limited to, the following:
• Removing rarely-used files from the system and store them elsewhere
• Creating additional storage space by removing
rarely-used files from the system
STORAGE SYSTEMS WHITE PAPER1. Abstract........................................................................12. Introduction to Snap EDR............................................12.1. Product Architecture.............................................23. System Setup and Software Installation .....................33.1. Installing the Snap EDR Management Console Software.....................................................33.2. Installing Snap EDR Agents..................................34. Archive Data Management Module.............................44.1. Default Functionality.............................................45. Configuring an Archive Job ..........................................45.1. Remote Archive Move...........................................45.2. Remote Archive ShortCut.....................................55.3. Remote Archive Details ........................................55.3.1. File Transfer Options......................................55.3.2. How Files are Archived With Windows ShortCut................................................55.3.3. Archived File Layout in Target Storage Location................................................................65.3.4. Disk Layout for Remote Archive Move Module........................................................66. Best Practices - Archive...............................................66.1. Windows ShortCut vs. Versioning.........................66.2. Solution Agent Selection......................................76.3. Source Directories Specified................................76.4. Open File Support in Windows.............................76.5. Debugging ............................................................77. Creating Archive Policies..............................................77.1. How Solutions Work Together...............................77.2. Sample Archiving Policies ....................................77.2.1. Use Case Parameters....................................88. Monitoring Performance ..............................................88.1. Viewing Job Statistics...........................................88.2. Viewing the Job Log Files.....................................99. Verifying Performance ..................................................99.1. Report Types.........................................................910. Conclusion................................................................10Archiving File Data with Snap Enterprise DataReplicator (Snap EDR): Technical Overview1. AbstractThis white paper provides an overview of the SnapEDR product, and details the components and config-uration of the Snap EDR Archive data managementmodule. The Archive module allows users to removeselected data such as rarely used files from remotesites and store them at a central location. This frees upadditional disk space on the remote agents. TheRemote Archive module allows for two methods ofarchiving data:" Remote Archive ShortCut (creates Windows short-cuts to the archived file for easy retrieval)" Remote Archive Move (gives users the option tocreate version changes of an archived file)These two methods are discussed in more detail laterin this document.Snap EDR runs on the following platforms: SnapServers powered by GuardianOS, Windows clients,and UNIX/Linux clients.Common business needs for archiving file datainclude, but are not limited to, the following:" Removing rarely-used files from the system andstore them elsewhere" Creating additional storage space by removingrarely-used files from the system2. Introduction to Snap EDR Snap EDR includes three Data Management tools toautomate the secure flow of data between systems:" The Aggregate tool allows jobs to be scheduled totransfer files from multiple agents to a single targetagent" The Distribute tool allows jobs to be scheduled totransfer files from one source machine to one ormore target machines" The Replicate tool allows jobs to be scheduled totransfer files between two systemsSnap EDR also includes the Advanced Data Manage-ContentsUntitled DocumentSTORAGE SYSTEMS WHITE PAPERArchiving File Data with Snap Enterprise Data Replicator (Snap EDR): Technical Overview2ment (ADM) Suite that groups together the function-ality of Remote Inventory, Remote Archiving, andRemote Backup and Restore. These solutions provideexceptional functionality to create and deploy policiesfor solving remote data management problems such asvariability, dissimilar computing platforms, securityneeds, and data integrity.The Advanced Data Management Suite performs thefollowing tasks:" Inventory, to determine storage utilization" Archive, to move selected data for permanentarchive" Backup, to protect data" Restore, to recover backup data The following describes a typical use case of theAdvanced Data Management Suite:Figure 1:ADM Configuration1. The user has a set of locations (with Snap EDRAgents) that are part of the enterprise but connect-ed over the wide area network (WAN). (Note:agents can be anywhere on the network.)2. The user runs a remote inventory job to report onthe remote location file sets. It shows that over 15gigabytes of data have not been accessed in over 270days. The user decides to create an archiving policybased on the information provided by the remoteinventory job.3. The user runs a remote archive job with the policycreated in step 2 to archive unused files. This freesmore disk space on the remote locations, anddecreases the amount of data that needs to bebacked up. Archiving also shortens the time a back-up takes because less data needs to be moved.4. The user wants to run backups of the remote loca-tions. Using a simple Web UI, s/he schedules aremote backup job to run on a regular basis. Thebacked up data from the remote locations is storedon a central location where it can be restored quick-ly, if required, using the Remote Restore tool.5. It is assumed that this location backup data wouldthen be backed up by any central backup softwaresuch as: BakBone NetVault (which comes standardon GuardianOS-based Snap Servers,) EMC s LegatoNetworker or Veritas NetBackup, and so on.Separate white papers provide details on the Aggregate,Distribute and Replicate tools and each module in theADM suite, and are available from the following loca-tion:http://www.adaptec.com/worldwide/product/markeditin-dex.html?sess=no&language=English+US&docType=Whitepapers2.1. Product ArchitectureSnap EDR consists of a Management Console that isinstalled on a Snap Server powered by GuardianOS,and a collection of agents running on the otherservers/workstations involved in the transfer. TheManagement Console coordinates and logs the datatransfer activities carried out by the distributed agents.The Snap EDR agents are responsible for the actualtransfer of data.Users access the Management Console using a webbrowser that allows them to configure Snap EDR andto create data management and transfer jobs from anylocation.The following diagram illustrates the Remote Archivemodule using Windows ShortCuts in a typical cus-tomer environment:Figure 2:Sample Archive Shortcut DeploymentSNAP SERVER 18000MANAGEMENT CONSOLE Remote LocationsTarget AgentSource AgentsInventoryReport FileInventoryReport FileInventoryReport FileInventoryReport FileSNAP EDR AGENTSNAP EDR AGENTSNAP EDR AGENTSNAP SERVER4500SNAP SERVER18000em ote LocationsCentral SitesInventoryArchiven r DR itestoreRestoreDisk-Based BackupOff-Line BackupUntitled DocumentSTORAGE SYSTEMS WHITE PAPERArchiving File Data with Snap Enterprise Data Replicator (Snap EDR): Technical OverviewIn the above diagram, the Snap EDR agent is deployedon all of the machines involved in the Remote Archivejob. All the machines involved in this deployment(except the storage host) are Windows machines. Inthis deployment, a common Universal Naming Con-vention (UNC) share is required between source andtarget agent machines to archive the files, since thefiles must be retrievable when recalled by the user.The following diagram shows a common deploymentof the Remote Archive module using the file version-ing option:Figure 3:Sample Archive Versioning DeploymentIn the above diagram, the Snap EDR agent is deployedon all of the machines involved in the remote archivejob. The machines involved in this deployment can berunning any supported platform of Snap EDR. In thisdeployment, the files archived from the source agentmachines are moved to the target agent. Once moved,the files are removed from the source agent machines(optional).3. System Setup and Software InstallationThe Snap EDR system requires users to install theManagement Console that coordinates and logs thedata transfer activities of the distributed agents. TheManagement Console should be installed on a SnapServer running GuardianOS. Users can install theAgent software on a GuardianOS-based Snap Server,Windows, or Unix/Linux system involved in the datatransfers.Installing and configuring the Snap EDR softwareinvolves the following procedures:" Installing the Management Console software on aSnap Server" Installing Snap EDR agent software on a Snap Server, Windows, and/or UNIX/Linux systemNote that Snap EDR installs only on GuardianOS3.2.019 or higher.Once the software is installed, users can login to theManagement Console and configure and schedulearchiving jobs.3.1. Installing the Snap EDR ManagementConsole SoftwareNote: Only one Management Console should be config-ured to handle all of the agents in the Snap EDR replica-tion environment.Install the Management Console through the browser-based Administration Tool for the Snap Server. Fordetailed procedures on how to install the ManagementConsole software, refer to the product documentation.3.2. Installing Snap EDR AgentsSnap EDR agents are responsible for the actual trans-fer of data. An agent is installed automatically on theSnap Server that is designated as the ManagementConsole. The Snap EDR agent software must beinstalled on each remote node in the system that willbe part of the Snap EDR data replication environment.Users can install a Snap EDR agent on any Snap Serv-er, Windows, or UNIX/Linux system that meets thefollowing requirements:For detailed procedures on installing the Snap EDR agentsoftware on a Snap Server,Windows,or UNIX/Linux sys-tem,refer to the product documentation.ItemDescriptionOperatingSystem Snap Server with GuardianOS v3.2.019 or higherAIX 4.3, 5.1, 5.2Solaris 5.7, 5.8HP-UX 11.x, 11iFedora Linux, RedHat Linux 7.2/7.3, EnterpriseLinux 2.1 or 3.0 or SUSELINUX 8.2 and 9.0Windows 2000 (with SP2 or higher), Windows2003, Windows Server Appliance Kit (SAK) 2.01,or Windows XPSystem Memory128 MB or moreDisk SpaceWindows systems: 5 MB or more UNIX systems: 5 MB or moreInstallation directory: 100 MB, 20 MB free in/tmp on all platformsNetworkConnection100 Mbps Ethernet or faster OR a WAN connec-tion capable of supporting the throughputrequired to meet the volume and window of time requirementsMANAGERT1T1T1arget AgentSource AgentsAGENTAGENTAGENTAGENTNAS/SAN STORAGEPublic Network3Untitled DocumentSTORAGE SYSTEMS WHITE PAPERArchiving File Data with Snap Enterprise Data Replicator (Snap EDR): Technical Overview4. Archive Data Management ModuleThe Remote Archive module provides a method forarchiving files that satisfies a user-defined set of crite-ria. Archiving the files reduces the amount of diskusage at remote sites, which results in faster backups,less storage space required for backups, and increasedavailable disk space.The Remote Archive module allows for two methodsof archiving files. The first method uses Windowsshortcuts. With this module, files selected forarchiving are replaced with a Windows shortcut.If the file is required at a later point in time, theuser simply clicks on the Windows shortcut file toretrieve the contents of the original file.The second module allows for versioning of thearchived files. With this module, the files selectedfor archiving are copied to the target disk storage.The user has the option to remove the file fromthe source machine once the file is archived onthe target, which would be the default behavior.This module can also be used to keep versionchanges to a file. Multiple versions of the file canbe stored on the target storage.4.1. Default FunctionalityThe following are the features of the RemoteArchive module:" Archive files from multiple agents to a com-mon location" Archive files from heterogeneous host platforms toa single common location" Archive files maintaining Windows shortcut" Archive files using file versioning, with a config-urable number of versions to maintain" Specify files to archive based on user-definedarchiving rules" Store files in common archive location in a flatname space or on a per host basis" Full scheduling functionality for automating fre-quency of jobs" Centralized control for viewing job status, control-ling job execution, and managing agents involved" Manage the amount of bandwidth the backup jobwill utilize" Network fault tolerance during backups5. Configuring an Archive JobOnce the Snap EDR software has been installed, loginto the Management Console to configure the RemoteArchive module to schedule the type of archive jobdesired.Upon login to the Management Console, the followingscreen appears, displaying a menu on the left side thatallows users to schedule a variety of jobs (Aggregate,Distribute, Backup, Replicate, and so on), installagents, change user preferences, run maintenancetasks, generate reports, and view transfer logs:Figure 4:Management ConsoleSnap EDR provides a straightforward interface toschedule an archive job by clicking on the RemoteArchive Move or Remote Archive ShortCut menuitems on the left side of the screen.5.1. Remote Archive MoveThe Remote Archive Move module allows for version-ing of the archived files. With this module, the filesselected for archiving are copied to the target diskstorage. The user has the option to remove the filefrom the source machine once the file is archived onthe target, which would be the default behavior. Thismodule can also be used to keep version changes to afile. Multiple versions of the file can be stored on thetarget storage.The Remote Archive Move configuration and schedul-ing screen is similar to the following:4Untitled DocumentSTORAGE SYSTEMS WHITE PAPERArchiving File Data with Snap Enterprise Data Replicator (Snap EDR): Technical OverviewFigure 5:Remote Archive Move Job Creation Screen5.2. Remote Archive ShortCutThe Remote Archive ShortCut module uses Windowsshortcuts to select files for archiving and replace themwith a Windows ShortCut. If the file is required at alater point in time, the user simply clicks on the Win-dows shortcut link to retrieve the contents of the orig-inal file.The Remote Archive ShortCut configuration andscheduling screen is similar to the following:Figure 6:Remote Archive ShortCut Job Creation ScreenIn the above diagrams, the Snap EDR agent isdeployed on all of the machines involved in theRemote Archive module. The machines involved inthis deployment can be running any supported plat-form of Snap EDR. In this deployment, the filesarchived from the source agent machines are movedto the target agent. With the archive move job, oncemoved, the files are removed from the source agentmachines (optional). With the Archive ShortCut job,the files are removed and replaced with a WindowsShortCut.When creating an Archive job, users can specify theagent to which the data should be archived, the sourceagents and types of files to archive (by date, size, etc.),the number of archive versions to keep (with ArchiveMove), and so on. For detailed instructions on creat-ing a remote archive move or a Remote ArchiveShortCut job, see the product documentation.5.3. Remote Archive DetailsThis section describes how archived files are stored onthe target archive directory using the Remote Archivemodule.5.3.1. File Transfer OptionsThe files are transferred between the source agentsand target host using the following file transferoptions:1. Files are considered for transfer based on the user-defined criteria. If no criteria are specified, all fileswill be transferred.2. Files in use during a transfer are skipped.5.3.2. How Files are Archived With WindowsShortCutFiles selected for archiving using the WindowsShortCut method are archived in the following man-ner. This information does not apply to the ArchiveMove module." File meeting the selected criteria is transferred tocommon UNC target directory" On the source host, the transferred file is used asthe target of the Windows ShortCut" The shortcut name will be the file name with a".lnk" extension added" The Archive Base directory will be used as the loca-tion of the real file" The original file name with the ".lnk" extension willbe used to name the shortcut file" Once the file is transferred and the shortcut is cre-ated, the original source file is deleted on the sourcemachineThe figure below shows the resulting shortcut filesafter the Remote Archive module has archived with5Untitled DocumentSTORAGE SYSTEMS WHITE PAPERArchiving File Data with Snap Enterprise Data Replicator (Snap EDR): Technical OverviewWindows ShortCuts the files in the directory "f:\basic-dataset1\dir1\subdir1". In this case, all the files in thedirectory were archived. By hovering the mouse over afile, the resulting popup window displays the details ofthe Windows ShortCut.Figure 7:Windows ShortCut Details5.3.3. Archived File Layout in Target Storage Loca-tionThe files to archive from the source agents are storedin the specified target archive directory. The files maybe stored on a per-host basis, or in one flat name-space, depending on the user configuration.The following depicts archived files stored on a per-host basis.User specified target storage location as"\\share1\ArchiveData"User specified source agents in company.com, host1,host2, and host3.\\share1\ArchiveData\host1.company.com\users\user1\file.dochost2.company.com\users\user2\file.dochost3.company.com\users\user3\file.docIf the user specified not to store the files on a per-hostbasis, but instead in one flat namespace, the same dataset above would look like the following in the targetarchive directory:\\share1\ArchiveData\users\user1\file.docusers\user2\file.docusers\user3\file.docWith the flat namespace option (not storing data on aper-host basis) the user runs the risk of having samenamed files from one source host being overwrittenby another source host.5.3.4. Disk Layout for Remote Archive Move ModuleThe disk layout for the Remote Archive Move moduleis the same as the Windows ShortCut module whendealing with the base target archive directory. The dif-ferences occur when the user has specified to keepmultiple versions of the files on the target archivedirectory and does not remove the files from thesource after transferring to the target. In this case,when file changes are detected on the source machineand the file exists on the target, a copy of the existingfile on the target is made before being overwritten bythe new version from the source. The copy main-tained on the target machine is referred to as a ver-sion of the file.When a version of the target file must be created, thefollowing steps are performed:1. Below the root target directory, a new directory iscreated called "archiveversions" (if it does notalready exist).2. The directory structure leading to the file for whicha version will be created is set up under the"archiveversions" directory (if it does not alreadyexist).3. A directory is created with the same file name asthe file for which a version must be created (if itdoes not already exist).4. The file that will become the archived version ismoved into this directory and the name is prefixedwith the current date timestamp.5. The new copy of the file is transferred from thesource machine into the original target archivedirectory location.6. Best Practices - ArchiveThis section describes the recommended configura-tion options and best practices to deploy the RemoteArchive Module.6.1. Windows ShortCut vs. VersioningThe Archive module provides two options for archiv-ing files. One option archives files using WindowsShortCuts, and the other option moves the files to thetarget storage.Consider using the Windows ShortCut option toarchive files under the following circumstances:" The user wants to recall data quickly " All machines involved are Windows agents" All machines involved have access to the targetstorage location6Untitled DocumentSTORAGE SYSTEMS WHITE PAPERArchiving File Data with Snap Enterprise Data Replicator (Snap EDR): Technical OverviewThe number of files should probably not be excessiveeither. Although the module does not limit the num-ber of ShortCuts that can be created, keep in mind aShortCut file is created for each archived file.Consider using the archive versioning solution underthe following circumstances:" Non-Windows agents involved " All the agents involved do not have access to acommon share drive " Files do not have to be recalled back to sourcemachines with link file6.2. Solution Agent SelectionWhen using the Remote Archive Windows ShortCutsolution, all the agents involved in the transfer mustbe Windows machines since Windows shortcuts areused.The Remote Archive Move solution can use any agentsrunning any of the supported Snap EDR platforms.6.3. Source Directories SpecifiedThe source directories to search for files to archiveshould be consistent across all source agents of ascheduled remote archive job. If the source agents toarchive data from have different source directories, thesource agents with the common directories should begrouped into the same job.For example, agents 1 through 5 must be part of anarchive job.Agents 1 and 3 have common directories toarchive, c:\appdata\userfiles.Agents 2, 4, and 5 have thecommon directories to archive, e:\documentrepository.Create one job for host 1 and 3 specifying the sourcedirectory c:\appdata\userfiles, and another job for host2, 4, and 5 specifying the source directories e:\docu-mentrepository.Only one root directory can be specified for a remotearchive job. From this root directory the search crite-ria and exclusions will be applied to all subdirectories.To archive files in more than one root directory, speci-fy each root directory in a separate job, with the targetdirectory or common UNC share drive being thesame.6.4. Open File Support in WindowsWhen open files are encountered during a remotearchive (unlikely, since it is probably archiving filesthat have not been used in a long time), the files willbe skipped by default. If open file support is required,users can run either of the Snap EDR Remote Archivemodules in conjunction with Open File Manger(OFM) from St. Bernard Systems to transfer open filesencountered during an archive.OFM enables Snap EDR to successfully capture andtransfer files that are open and in use during thetransfer process.OFM runs as a service and watches the process list.When the transfer portion of the agent is launched,OFM becomes active, performing certain actions toensure that open and in-use files can be transferred.NOTE: Transferring open files is not generally recom-mended, as the data in these files may not be in a consis-tent state if archived while open, as data may still be intransit buffers and not yet flushed.6.5. DebuggingUsers can set the job log detail level option whenscheduling a job, to produce agent and job logs usefulfor debugging. For more information, see the productdocumentation.7. Creating Archive PoliciesThis section describes, through a use case, how to cre-ate data archiving policies based on the results of a filescan inventory report generated from the RemoteData Inventory module.7.1. How Solutions Work TogetherThe remote data inventory solution file scan featurecan be used to create archiving policies. Based on filescan criteria specified, the remote data inventory solu-tion reports the resulting file information and disksize usage of the files. Running various remote datainventory jobs with different file scan criteria lets theuser experiment with different archiving policies.Users can apply the same file scan criteria used in theremote data inventory job to a remote data archivingjob. The directories and files reported in the remotedata inventory job can be specified in the Archivemodule job to indicate which files and directories andfrom which agents to archive.With this process, the remote data inventory solutionis used to create archiving policies and the remotedata archiving solution is used to implement thearchiving policy.7.2. Sample Archiving PoliciesThis section runs through an example of how theremote data inventory report is used to create anarchiving policy.7Untitled DocumentSTORAGE SYSTEMS WHITE PAPERArchiving File Data with Snap Enterprise Data Replicator (Snap EDR): Technical Overview7.2.1. Use Case ParametersIn this use case, a corporation has deployed Snap EDRin the enterprise and is working with the Remote DataInventory and Remote Data Archiving modules.File ServersThe user has three Windows 2000 servers where dataresides:" Host1.company.com" Host2.company.com" Host3.company.comFile SystemsEach server has two file systems from which the userwants to archive data. The user suspects there is a lotof data which has not been modified in a long timetaking up significant disk space, resulting in slowerbackup times.The file systems to perform archiving from are:" F:\applicationdata" E:\userdataEach server has the same drive names for ease ofmaintenance, but different users accessing each server.RequirementThe user wants to develop an archiving policy thatwill archive the following files:" Files that have not been modified in the last 90 days" Do not include ".lnk" files (Windows shortcuts)" Do not include subdirectory "finance"Remote Data Inventory JobThe user schedules a Remote Data Inventory job torun with the appropriate parameters:" Source Agents (Host1.company.com, Host2.compa-ny.com, Host3.company.com)" Files that have not been modified in the last 90days" Do not include ".lnk" files (Windows shortcuts)" Do not include the "finance" subdirectory When the remote data inventory job runs with theseparameters, the following results appear:The user decides to create a remote data archive job toarchive the files that meet the specified criteria. Thiswill free disk space and speed up the backup jobs thatrun on the specified directories.The user has also scheduled this remote data invento-ry job to run every two weeks to monitor the unmodi-fied file count on the servers in question.Remote Data Archiving PolicyThe user can take the parameters specified in theremote data inventory job and use them to create anarchiving policy. In this case, the user wants to archivethe unused files that are taking up disk space on thesource host machines where the user ran the remotedata inventory job.The user is going to schedule a remote data archivejob with the same file scan criteria used in the remotedata inventory job. The job will run every two weeksand archive the applicable files from the source hostmachines. The schedule, along with the file scan crite-ria constitutes the file archiving policy. The archive jobwill do the following:" Archive files from the source agents (Host1.compa-ny.com, Host2.company.com, Host3.company.com)" Archive files that have not been modified in the last90 days" Do not Archive ".lnk" files (Windows shortcuts)" Do not Archive the "finance" subdirectory These parameters apply to either the WindowsShortCut or the Archive Move modules of theRemote Data Archive module.By using the criteria from the remote data inventorysolution, the user has pre-determined the number offiles and disk space that will be moved from thesource host machines.8. Monitoring PerformanceThere are a number of ways a user can monitor theperformance of a job, including the following:" Viewing Job Statistics" Viewing the Job Log Files8.1. Viewing Job StatisticsWhen a job that has run to completion is selected, thescreen displays the job's statistics, including informa-tion such as the start and end time of the job andwhether or not the job ran successfully. The ScheduledJob View screen also allows access to Console func-tions where other tasks can be performed with thescheduled job. These tasks include manually running ajob and viewing past log files. The following is a sam-ple of the Job View screen:HostNumber of FilesTotal Disk SpaceUsedHost1.company.com101471.2 gigabytesHost2.company.com7839402 megabytesHost3.company.com11342812 megabytes8Untitled DocumentSTORAGE SYSTEMS WHITE PAPERArchiving File Data with Snap Enterprise Data Replicator (Snap EDR): Technical OverviewFigure 8:Job Statistics ScreenExit codes appear in the Exit Code column in the listof job runs. An exit code indicates whether or not ajob completed successfully, and if there was an error,the type of error that occurred. A 0 exit code indi-cates that the job completed successfully. For adescription of what each non-zero exit code means,click more info beside the exit code in the ExitCode column of the job screen, or refer to the prod-uct documentation.8.2. Viewing the Job Log FilesWhenever users run a scheduled job, the ManagementConsole generates a log file. If the job is clicked on,the job's display area shows log files for the mostrecent run and up to ten previous job runs. If thereare more than ten job runs, the oldest job log is delet-ed to allow space for the latest job log.Clicking on the word view beside any past job rundisplays a detailed log summary for that particular jobrun:Figure 9:Job Log ScreenThis summary displays messages about the data trans-fer, and is generated while the job is running by theManagement Console and the Aaents. These messagesvary in severity, from simple information messages(e.g., starting group: RemoteArchive (sequential)), towarnings (e.g., Preserve ownership may fail for target'snap01' because the system types are different. ) toerrors and debug messages. These messages are usefulfor evaluating the job run.Click the Filter button to change the type of loginformation displayed or to download the job log fileto the local machine. Downloading the file allows it tobe loaded into different programs (for searching,printing and so on). The log file is a plain text file.9. Verifying PerformanceThe Management Console creates statistical recordsfor each completed job run and stores them in therules database. Using the Management Console, userscan generate a number of different types of reports toevaluate the operation of each job.9.1. Report TypesUsing the Management Console, the following typesof reports can be generated:Template names can be assigned to reports that arecreated. The template appears in the Report view.Report templates allow you to generate reports with-out having to change the initial parameters. Templatesare especially useful for generating the same type ofreport on a regular basis. Run, Edit, Remove, orSchedule a report by clicking on the appropriate wordbeside the report template. Click Schedule to runReport TypeDescriptionStats SummaryReportProvides a summary and totals of the data fromall jobs in the selected job group (Archive jobs arein the RemoteArchiveMove andRemoteArchiveShortCut groups), based on howthe user chooses to group the data (by month,day, etc.).Detail ReportProvides a detailed record of the data from theselected job group (Archive jobs are in theRemoteArchiveMove and RemoteArchiveShortCutgroups). Note that the number of records thereport displays depends on the number of agentson which the job runs. The report displays a recordfor every Agent on which the job runs.Custom QueryReportProvides a customized query of detail records fromthe job name within a selected job group (Archivejobs are in the RemoteArchiveMove andRemoteArchiveShortCut groups). Note that thenumber of records the report displays depends onthe number of agents on which the job runs. Thereport displays a record for every agent on whichthe job runs.9Untitled Documentreports daily, weekly or monthly at specific times. Thefollowing diagram is a sample of a Stats SummaryReport:Figure 10:Sample Stats Summary ReportFor detailed instructions on how to generate reports,see the product documentation.10. ConclusionThe Snap EDR Archive data management modules arevaluable and easy-to-use modules to manage storageutilization. The Archive modules are comprehensivesolutions that can assist users in removing rarely usedfiles from remote agents to free up disk space.STORAGE SYSTEMS WHITE PAPERArchiving File Data with Snap Enterprise Data Replicator (Snap EDR): Technical Overview10Copyright 2005 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 666760-011 Printed in USA 03/05 3719_1.3Adaptec, Inc.691 South Milpitas BoulevardMilpitas, California 95035Tel: (408) 945-8600Fax: (408) 262-2533Literature Requests:US and Canada: 1 (800) 442-7274 or (408) 957-7274World Wide Web: http://www.adaptec.comPre-Sales Support: US and Canada: 1 (800) 442-7274 or (408) 957-7274Pre-Sales Support: Europe: Tel: (32) 2-352-34-11 or Fax: (32) 2-352-34-00
