Copyright: © Copyright 2000 Computer Associates Int'l Inc. and/or its subsidiaries


ARCserve Online Help

Click the Help Topics button to continue.


ARCserve Online Help

© Copyright 2000 Computer Associates International, Inc. and/or its subsidiaries.


Introduction

What is ARCserve?

ARCserve is a data management and backup program that allows you to back up data from your workstation or other machines attached to your network.

ARCserve's advantages include:

Scheduled Backups:  Schedule custom-made backup jobs that begin at any designated time and/or at fixed regular intervals.

Easy-to-use GUI interface:  Allow ARCserve administrators to use a simple but advanced graphical interface to perform administration and job management functions.

Media Rotation:  Plan and customize your GFS media rotation schemes using a user friendly calendar view interface.

Media Spanning:  Large backups automatically span multiple media until the backup is complete.

Built-in Small Changer Support:  ARCserve has built-in changer support for one tape drive with 20 slots or less.  It offers a separate Library option for changers with multiple drives and 100 slots or more.

Parallel Streaming:  Run jobs concurrently when using multiple storage devices.

Reports:  View job history and activity on the machines, directories, tapes and other media.

Enterprise client agent support:  Back up remote machines using the Computer Associates client agents (such as Client Agent for NetWare), which employ the latest PUSH technology.  Client agents maximize your ARCserve server's capabilities and speed by off-loading the processing of the backup, restore, and compare functionality directly to the machine on which the Client Agent resides.  Available for the Enterprise edition only.

Computer Associates AntiVirus integration:  Automatically scans files for viruses during a backup operation.  Viruses can be excluded from the backup or the file names can be logged.

User-defined scripts:  Configure jobs once and re-uses them when needed.

Encryption support:  All ARCserve backup jobs can be encrypted with a session/encryption password to enhance network security.

Automatic Media Rotation Scheme:  ARCserve can schedule repeating backup jobs that are custom-made for your environment.  ARCserve uses an automatic rotation scheme, which can be a simple rotation or a Grandfather-Father-Son (GFS) rotation.

GFS Media prediction report:  You can produce reports to generate detailed media information for media pools used in your rotation schemes including the media status and session information.

ARCserve job queue security:  You can restrict access to the ARCserve job queue by granting varying security permissions  for different user/group identities for the job queue.

ASJS.exe:  Command line program can be used to monitor vital ARCserve job functions.

Multiple node copy support:  This function will enable users to copy files from multiple locations to a single target directory.

Preferred machines:  You can now set up all the volumes of a specified machine as a share in the ARCserve browser.  It will be displayed under the Preferred Shares node of the ARCserve browser.

Intelligent restore:  The ARCserve database system allows you to quickly locate and restore your archived data.

Tape support:  Back up your files to a wide variety of SCSI 4mm, 8mm, DLT, and QIC tape devices.

Remote Management of ARCserve Servers:  Allows you to manage multiple ARCserve servers from a single machine.  Gives you the ability to back up, copy, and restore any Windows NT machine, UNIX and Novell NetWare servers in your network.

Event-driven notification system:  The Computer Associates Alert notification system informs you of key events in your operations.  Notification is available through pager, broadcast, email, trouble tickets and SNMP messages.

Applications agents:  Allows you to backup complex databases and groupware such as MS-Exchange and Lotus Notes.

Windows 2000 and Windows 2000 support:  Back up compressed files, directories, and drives on Windows NT File System (NTFS) formatted drives.  Also supports Service Security Impersonation.

Distributed Data Migration support:  ARCserve comes with limited data migration options to further enhance your data management capabilities.


Supported Operating Systems and Applications

Windows 2000 Support:  Full support for System State, NTFS-extensions Active Directory, and Certificate Server.

Windows NT 4.0 integration:  ARCserve is fully integrated with Windows NT 4.0 through Shell Extensions.

Context Menu Handler:  Instant backup of drives from context menu by just right clicking on drives.  Submit pre-saved jobs from context menu item by right clicking on job scripts.

Icon Handler:  Display different icon for each job type for ARCserve job scripts.

Property Sheet Handler:  Display Computer Associates-ARCserve backup status on properties of drives.  Display job information from properties of job scripts.

Enhanced detailed Registry backup performance:  You can now backup (partial or full) your Windows Registry entries to the key level as a separate media session with optimized performance.

NetWare compatibility:  With the NetWare Client Agent installed, ARCserve can back up and restore any Novell NetWare server (v3.x, v4.1x) attached to your network.

UNIX compatibility:  ARCserve can back up and restore any UNIX server attached to your network.

Enterprise client agent support:  Back up remote machines using the Computer Associates Client Agents (such as Client Agent forNetware, Windows 95/98, Windows NT/2000, Windows 3.x, Linux, UNIX, OS/2, and MacOS).  ARCserve's Client Agents will efficiently back up and restore complete system information for all the listed platforms employing the latest PUSH technology.  Available for the Enterprise edition only.

Applications/DB Agents:  ARCserve can support a wide variety of complex databases and groupware applications such as Oracle, Informix, SQL, SAP R/3, MS-Exchange, and Lotus Notes.  These agents are sold separately.  For detailed information about any Database Agent, refer to the User Guide for that particular agent.


Centralized Database and Job Management

ODBC database support:  ARCserve will support SQL ODBC database formats to use as its main database system.

Centralized database management:  From the ARCserve Central Database Manager, you can administrate the various ARCserve host database systems from a single console.

Remote Management of ARCserve Servers:  The Enterprise and Advanced versions allow you to manage multiple ARCserve host servers from a single ARCserve Manager.  All ARCserve Servers on the network can be browsed through a tree view display.  Users can group preferred ARCserve Servers and view job status, monitor active jobs as well as view activity logs.

Remote job management:  The ARCserve Manager provides you with the ability to back up, copy, and restore any network machine and other servers in your network from a central console.

Advance event-driven notification system:  The Computer Associates Alert notification system informs you of key events in your operations.  Browser find functions with wildcard pattern matching for error messages as an Alert event, per event and per job based Alert notify methods and recipients configured through ARCserve.  You can also re-use the configurations you define for different jobs and view the entire ALERT configuration in the Activity Log for each job.  Users can use ALERT notifications for specific non-job related events, such as the tape or database engine starting, error messages, or other events viewed through the Activity log.

Automatic discovery:  ARCserve automatically discovers all other ARCserve Servers, client agents and database agents on your network.


Options Support - Summary

RAID Option support:  RAID stands for Redundant Array of Inexpensive Devices.  It refers to a system of multiple drives that process data as a single high-performance drive.  The ARCserve RAID Option is fault tolerant – if one tape becomes inoperable, you can use the remaining tapes to back up your data.  In addition, the ARCserve RAID Option allows you to use a Tape RAID system for high-speed backups.

Image Option support:  ARCserve Image option allows you to perform high-speed image backups.  The Image Option achieves high backup speeds by connecting directly to the volume you want to backup, bypassing the file systems and reading in data directly.  In this way it creates an "image" of the volume and achieves high speeds by writing this volume image to media rather than backing up the volume file by file.  The ARCserve Image Option must be purchased separately.

Disaster Recovery (DR) Option support:  For advance disaster recovery methods, ARCserve includes built-in support for the ARCserve Disaster Recovery Option.  The ARCserve DR Option must be purchased separately.

Library Option support:  For both the UNIX and NT platforms, ARCserve will have a built-in changer that will consist of one tape drive supporting 20 slots or less.  Both platforms will offer a separately purchased Library Option that will enhance the built-in changer to support a larger changer with multiple drives and 100 slots or more.  For ARCserve, small changer support is built-in and provided free to all users.  With the Library Option installed, ARCserve administrators can use a changer device as a destination with your backup rotation.  Advance media operations are also available depending on the changer device and its configuration.  The ARCserve Library Option must be purchased separately.


Archive Security

CRC Verification support:  You can verify your backed up data with CRC verification.  CRC stands for Cyclic Redundancy Check and it detects data corruption by re-generating a numeric value for your data, then checking that value against the data on the media.

Compression support:  ARCserve now supports software compression for data transport and archival needs.

Encryption support:  All ARCserve backup jobs can be encrypted with a session password to enhance network security.


Advanced Backup

Advance scheduled backups (Grandfather Father Son or GFS ):  You can schedule repetitive backup jobs that are custom-made for your environment.

GFS Media prediction report:  Now you can run reports to produce detailed media information for media pools used in your rotation schemes including the media status and session information.

ARCserve job queue security:  You can restrict access to the ARCserve job queue by granting varying security permissions to ARCserve$ for different user/group identities for the job queue.

Jobmon.exe:  Command line program can be used to monitor vital ARCserve job functions.

Multiple node copy support:  This function will enable users to copy files from multiple locations to a single target directory.

Preferred machines:  You can now setup all the volumes of a specified machine as a share in the ARCserve browser.  It will be displayed under the Preferred Shares node of the ARCserve browser.

Intelligent restore:  the ARCserve database system allows you to quickly locate and restore your archive data.  Although the files that you restore will always come from a media, the way you select these source files can vary.  ARCserve provides you with the most convenient and thorough methods for finding the files you want to restore.  There are four methods by which you can choose your source files:  Restore by Tree, by Session, by Query and by Backup Media.


Related Topics

  Selecting data from media


Media and Device Management

Media rotation:  The ARCserve administrator can design specific media rotation schemes (such as GFS) to suit the particular archive needs.

Media Spanning:  Large backups can be submitted to automatically span multiple media until the backup is complete.

Parallel Streaming:  You can submit jobs concurrently when using multiple storage devices.

Vast media support:  ARCserve will now support a wide variety of media including 4mm, 8mm, DLT, QIC, removable optical drives, Iomega's Zip or Jazz media, PDs, and MO formats.

Advanced media merging performance via cataloging:  ARCserve now creates a catalog file on your media to improve performance for merge jobs and database backup jobs.

Media pool management:  The new Media Pool Manager window allows you to create and maintain media pools for a logical grouping of media.  A serial number and/or a bar code can be assigned to a particular media to help manage your rotations.

Tape Alert Support:  ARCserve supports Hewlett Packard's Tape Alert management feature for DDS-3 devices that support the TAPEALERT firmware.  System Administrators will now be able to monitor ARCserve tape devices and media by using HP Open View through the SNMP protocol.


Miscellaneous

Detailed report generator:  With the detailed report functions, the administrator can view/print ARCserve's job histories and activities.  The detail report includes the source and destination target(s) and media statistics, such as sequence and session number.  You can also specify the level of detail in the log by choosing the Log options before you submit the job.  ARCserve provides several options to help you create and maintain your reports to your own specifications.

User-defined scripts:  Reusable scripts can be configured to run specific ARCserve tasks.

Pre/Post commands based upon job status:  ARCserve contains conditional pre-execution, job execution and post-execution based on previous results (exit codes).  Pre/post execution not only is supported for before/after job execution but also before/after execution on machines.  Now you can select to run or not to run a command if a job fails, is completed, or incomplete.  For instance, you may or may not want to run a detailed report on a job if it fails.

ARCbatch utility:  The ARCbatch job utility allows you to submit, delete, or modify the execution time for jobs in local or remote ARCserve job queues from the Command Prompt (Console mode).  You can use a job script created in the ARCserve manager or in a text file using the ARCbatch Job Information Template in the ARCbatch.wri file located in the ARCserve home directory.


Key Features of ARCserve

The main software components of ARCserve are as follows:

Backup

Back up data to media.  ARCserve allows you to perform a complete system backup of all network machines.  The network system information (such as registry information for each machine) is backed up intact, allowing you to completely restore the machine in the event of system failure.

The optional Client Agent for NetWare is available for backing up NetWare file servers.  Without the agent, NetWare-specific files (such as bindery and NDS information) are backed up as DOS files.  With the agent, all NetWare-specific files are backed up intact, ensuring complete backup/restore of the NetWare file server.  Client agent software is also available for other operating systems.

Information about each backup job (such as the path and name of each file, as well as the media used) is logged in the ARCserve database.  This will become useful to restore your files to their original machine and path.  Depending on your requirements, you can choose to log all information, only job and session information, or to disable database recording entirely.

Restore

Restore data from media using a variety of intelligent restore techniques, including rapid lookup and retrieval of lost data.  Each time you run a backup job, ARCserve records information in its databases about the machines, directories, and files that have been backed up, and the media that were used.  This allows ARCserve to locate files whenever you need to restore them.  ARCserve provides you with four methods for selecting the data you want to restore (the source), and also several methods for selecting a Destination to restore the data to the machine.  In addition, backing up data through RAID can increase the throughput and ensure fault tolerance of your backup job.

Media Pool Management

Manage media pools by creating and maintaining media pools for a logical grouping of media.  Serial numbers and/or bar codes can be assigned to a particular media to help manage your rotations.

Job Status

Monitor all pending, completed, and active jobs from the Job Status Manager.  Reschedule pending or completed jobs.  Submit new jobs, delete jobs, and stop active jobs.  Log information is provided for each completed job.

Device

View information about your storage devices and media, change a drive's compression mode, and perform media maintenance functions such as formatting, erasing, and retensioning.

Database

View information from the ARCserve database, such as the jobs processed by ARCserve, the media used by ARCserve, and the devices you are using with ARCserve.  Generate reports from the database.

Wizards

For users who want to initiate a job without having to launch the ARCserve Manager, ARCserve now comes standard with independent Wizards for its main operations.  Similar to other wizard software, the ARCserve wizards will take the user step-by-step to complete the specific task.  Using the wizards can be an alternative operation to save time and complications in performing a backup job.


How ARCserve Works

ARCserve consists of two working components — the ARCserve Manager and the ARCserve Server.

The ARCserve Manager

The ARCserve Manager is the application you use to manage your ARCserve jobs.  All configurations for ARCserve operations are handled here.  You specify a source and, sometimes, a destination.  From the ARCserve Manager you have complete control over all aspects of your past, active and future jobs.  You can configure and manage the storage devices, the database and media pools.  Optional features such as advanced options, filters, and logs and reports are specified here, too.  When you are done, the ARCserve Manager packages all this information together, and submits it to the ARCserve Server.

The ARCserve Server

The ARCserve Server is composed of three separate server modules.  These server modules (commonly referred to as "engines") are the:

Database Engine

Job Engine

Tape Engine

The ARCserve Server performs the operation.  The engines work together to back up, copy, restore, and perform all the ARCserve jobs you submitted through the ARCserve Manager.

The Database Engine

This engine is responsible for maintaining the history of several things:

Files, directories, drives, and machines that ARCserve has backed up or copied

Information about jobs that have been processed by ARCserve, such as the type, the final result, the start and end time, etc.

Media used by ARCserve, such as its name, date it was first formatted, date it expires, sessions on it, etc.

By default, everything that happens within ARCserve is recorded by the Database Engine.

The Tape Engine

The Tape Engine is responsible for communicating with and controlling your storage devices.  The tape engine performs all of the actual reading and writing from the media devices.  In simple terms, when a media is needed for an ARCserve job, the Tape Engine tells your hardware that its media is needed.

The Job Engine

The Job Engine is responsible for processing your jobs at their designated date and time.  It constantly scans the job queue searching for a job that is ready to run then takes the job and sends it off to the appropriate handler for the job.


ARCserve Product Home Page

The ARCserve Home Page is composed of three main elements:

Navigation Bar: This area can be found on the left-most portion of the page.  It is composed of two parts, Contents and Most Recently Used.  The contents of the Most Recently Used area is saved between sessions.  The Navigation Bar displays with all Manager pages unless it is disabled.  To disable this feature, select View and deselect Navigation Bar.

Browser Bar: This bar displays above the Browser Window.  It shows five standard web browser buttons: Back Forward, Stop, Refresh, and Home.

Browser Window: This area displays to the right of the Navigation Bar.  ARCserve features can be accessed here.


Related Topics

  ARCserve Contents Menu

  ARCserve Browser


ARCserve Contents Menu

The Contents area displays in the Naviagation Bar which is part of the Home Page.  The following features can be accessed here:

Home: Displays the ARCserve Product Home Page.

Quick Access: Provides quick access to the ARCserve Managers.  While at the Quick Access page, pause the cursor over a Manager icon to display a brief description.

Wizards: Allows you to quickly accomplish many of the common tasks relating to the backup devices.  A description of each feature is provided on the Wizard page.

Utilities: Provides access to tools that can help you to manage files on a machine.  While at the Utilities page, pause the cursor over a Utility icon to display a brief description.

News: Links you to the ARCserve Internet Home Page.

Support: Access Support tools that help you solve issues.


Related Topics

  ARCserve Product Home Page

  ARCserve Browser


ARCserve Browser

The layout of the Browser is comprised of three panes:

Tree View Pane: The left portion of the page is referred to as the Tree View.  Use the Tree View for navigation.  By default the branches (directories) of a tree display.  To display the leaves (files) of the branches in this pane, select View, Preferences, Show Leaf Node in Tree.

List View Pane: The upper right portion of the page is referred to as the List View.  This pane displays the leaves (details) for the selected Tree branch.  Objects can be selected in the List View.  The information that displays in this area can be sorted by any one of the detail headings that are shown.  Click a heading to sort the information based on one of the details.  The area in which this information is displayed can be made larger by selecting the push-pin icon button on the toolbar and then choosing Show List.  To hide this pane, select the push-pin icon button on the toolbar and then choose Show Properties.

Note:  When device/media information is shown in the ARCserve Browser, you can right-click in the List View Pane to access a menu that allows you to change the way the information displays.

Properties View Pane: The lower right portion of the page is referred to as the Properties View.  This area displays additional information for a selected object as well as context menu choices.  The area in which this information is displayed can be made larger by selecting the push-pin icon button on the toolbar and then choosing Show Properties.  To hide this pane, select the push-pin icon button on the toolbar and then choose Show List.


Related Topics

  ARCserve Product Home Page

  ARCserve Contents Menu


Using the ARCserve Menus

ARCserve's menu bar appears at the top of every window.  This menu bar contains drop-down menus by which you can select a function to be performed.

You can also use keystrokes to choose menu options.  From the Main menu you can press the ALT key together with the underlined letter to select a menu.

Once the menu is displayed, you can select an option from it by pressing the underlined letter in the option name.


Selecting an ARCserve Server

You can select an ARCserve Server from any Manager window that submits job configurations to a server, such as the Backup window or the Restore window.  You can select a different server from each open Manager window.


Related Topics

  Select an ARCserve Server from a Manager Window


Using the Browser


Introducing the ARCserve Browser

The Browser facility is used in many Manager windows to enable you to choose the source and destination for your backup, copy, and restore operations.  The Browser operates in two modes:

Machine tree: view and select files, directories, drives, shares, machines, volumes, and servers.

Media tree: view and select a backup media.

The Browser mode is determined by the type of operation (e.g. backup or restore) and whether the Source or Destination tabs are selected.


Adding Preferred Shares to the machine tree

The Preferred Shares are a collection of your favorite backup shares.  (A share is a shared drive or directory.)  You can manually add individual share points to the Preferred Shares tree.  The share point is remembered and displayed regardless of the status of the network connection.  This provides quick access to commonly used shares on your machines.  You can also setup shares at the machine level, which enables you to browse, backup, or restore all of the shared drives on a machine under a single preferred share.

This feature can be used to back up share points provided by other operating systems that are capable of creating "shares" in a Microsoft network, such as UNIX NFS shares or OS/2 LAN Server shares.

This feature is also useful for users that frequently back up "shares" within a network, instead of "machines".  Shares are considered "named" short-cuts or aliases to machine drives and directories on the network.  Shares perform the same function as drive mappings, with the advantage of allowing the user to provide a descriptive name to the share.


Related Topics

  Add a Preferred Share to the machine tree


Adding objects to the machine tree

You can add objects to the machine tree that are unavailable when you set up a job.  For example, you can add a machine that is temporarily unavailable and schedule a backup/restore for the machine.

You can add the following types of objects to the machine tree:

Microsoft Networks domains or workgroups, machines, or shares

NetWare servers and volumes


Related Topics

  Click here to add a Microsoft domain


Providing security information

You must provide a valid username and password for the remote machines or shares that you wish to back up, copy, or restore data to.  To enter the username and password:

From the Browser, by right-clicking on the machine or share.

From the Browser, when attempting to expand the machine or share to view directories.  (You will be prompted for the information.)

When submitting a backup, copy, or restore job.  (You will be prompted for the information.)

From the Browser

The Browser uses your local username and password by default in order to access machines or shares for browsing.  If your local username and password are not valid on the remote machine or share, then you will be prompted to enter the information when you attempt to expand that node.

When submitting a job

You may also change or verify the username and password for a machine or share each time you submit a job.  If you have already provided account information for a machine or share, either in the browse mode or in a previous backup job, ARCserve will retain this information and simply ask you to verify it.  (This information is stored for future sessions.)

When you submit a job, the Security Information dialog box opens.  This dialog box displays the security information for each machine or share that is accessed during this job.  To change the account information, select the machine/share, and click the Security button.


Related Topics

  Click here to enter a username and password from the Browser


Selecting media groups and media

The Browser is also used to select the media groups and media that you want to use for your jobs.  Depending on the job you want to perform, you may need to select a media or media group as your source or destination.  Whether a media or media group will be the job's source or destination, the method for selecting them is the same.


Related Topics

  Select a media group or a media

  Configuring the media options


Configuring the backup media options

You can configure the media options for a backup job so that if the media name is left blank, ARCserve will automatically use the next available media for the backup job.

The media options also allow you to specify append, overwrite, and time-out procedures for backup jobs, and time-out procedures for restore and other jobs.


Related Topics

  Backup Media options


Backing Up


Backing up data on your network

ARCserve allows you to back up of most machines attached to your network.

For complete system backups of non-Windows NT systems, such as NetWare or UNIX, use ARCserve in conjunction with the appropriate Computer Associates Client Agent.  The Client Agent for Windows NT/2000 is also available for more efficient backups of Windows NT/2000 machines.  Computer Associates' Backup Agents allow you to back up and restore complete databases, such as Oracle and Microsoft SQL.  Refer to the ARCserve user guide for more information on Backup Agents.

The following software is integrated into the base product to enhance ARCserve's backup capabilities:

RAID Option: to configure tape RAIDs for high-speed backups.

Built-in Small Changer Support: allows you to use a small changer for backup jobs (one tape drive with 20 slots or less).

The following additional software options are also available to enhance ARCserve's backup capabilities:

Image Backup Option: to perform high-speed image backups.

Library Option: to use an autochanger with your backup rotation.

Serverless Backup Option: to reduce CPU utilization and increase backup performance.

Contact your Computer Associates representative for information on any of these options.


Related Topics

  About ARCserve Agents


Submitting a backup job

To back up data from your network, you must configure and submit a backup job using the Backup Manager.

ARCserve allows you great flexibility in specifying options, filters, and scheduling information for your jobs.


Related Topics

  Submitting a backup job

  Backing up Windows NT machines

  Operation options (Backup)

  Group Configuration Screen

  Device Group Properties

  Source Priority


Selecting a backup method

The backup method determines which files in a selected drive or directories are backed up.  The following types of backup methods are available:

Note: These methods do not apply to UNIX files.

Method	Which files are included?	Check archive bit?	Reset archive bit?
Full (Keep Archive Bit)	All source files.	No.	No.
Full (Clear Archive Bit)	All source files.	No.	Yes.
Incremental (Archive Bit)	Source files whose archive bit is turned on.	Yes.	Yes.
Differential (Archive Bit)	Source files whose archive bit is turned on.	Yes.	No.

In general, if you have large amounts of data to be backed up every day, running regular differential or incremental backup jobs and an occasional full backup job may be your best solution.

The following table describes the advantages of each method:

Method	Description
Full (Keep Archive Bit)	Includes all the source files.  This method does not change the archive bit.  You might use this option if you wish to perform an unscheduled full backup that will not affect your incremental for differential backups.
Full (Clear Archive Bit)	Includes all the source files.  This method ignores the file's archive bit until after the file is backed up.  At that time, ARCserve turns off the file's archive bit.  At the end of the job, all files that have been backed up have their archive bits turned off.
Incremental	Includes only files that have changed since the last Full (Clear Archive Bit) or Incremental backup. ARCserve checks the file's archive bit.  If the archive bit is on, ARCserve backs up the file, then turns archive bit off.  The next time an incremental backup is done, this file is skipped (unless it is modified again).
Differential	Includes files that have been changed since the last Full (Clear Archive Bit) or Incremental backup.  ARCserve checks the file's archive bit. If the archive bit is on, ARCserve backs up the file, but in this case, ARCserve does not turn off the archive bit afterwards.


Related Topics

  Selecting a backup method

  About archive bits


About archive bits

What is an archive bit?

A file's archive bit is a marker that indicates whether the file has been modified.  An archive bit that is set (turned on) indicates that the file has changed since it was last backed up or copied.

Why turn off a file's archive bit?

Turning off (resetting) the file's archive bit is a procedure that affects what ARCserve will back up or copy the next time.  An archive bit that is off indicates to ARCserve that this file has not changed since it was last backed up.

The method you select determines whether ARCserve will back up or copy all files, or only files whose archive bit is on.  It also determines whether ARCserve will turn off the archive bit after the file has been backed up or copied.

Note that a file's archive bit can also be turned on and off by other applications.

Warning:  ARCserve's Copy feature can set or clear file archive bits that may effect your Incremental or Differential backups.  Plan your copy operations carefully to ensure that they do not interfere with your backup jobs.


Specifying media overwrite/append rules

You can specify the overwrite/append rules for the media used in your backup job while you are configuring the job.

The following types of options are available:

First Media Options: Determines the overwrite rules for the first media that is used for the backup job.

Additional Media Options: Determines the overwrite rules for the additional media.

First Media Options

The first media is the media you use when the backup job begins.  The options for the first media are:

Append to Media

Append job sessions to the selected media.

Overwrite Same Media Name, or Blank Media

Overwrite the media in the drive only if it is the one you specified for the job or if the media is blank.  If neither of these conditions is met, ARCserve prompts you to supply the specific media name.

Overwrite Same Media Name or Blank Media First, then Any Media

Overwrite any media found in the drive. If you select this media option, ARCserve checks to see if the media in the drive is the one specified for the job.  If it isn't, ARCserve checks to see if the media is blank.  If the media isn't blank either, ARCserve reformats whatever media it finds in the device and starts backing up files at the beginning of the media.

Timeout for First Media

Number of minutes ARCserve will attempt to write to media before canceling job.

Additional Media Options

These options apply to jobs that require more than one media.  You need to specify which media ARCserve can use when the job spans media.

Overwrite Same Media Name, or Blank Media

Write to the media in the device only if it has the same media name (but a different media ID) or if it is blank.  ARCserve remembers the name and ID of the job's first media.  When the job requires an additional media, ARCserve checks if the new media has the same name (but different media ID) or if it is a blank media.  As long as the ID is different, ARCserve reformats the media, giving it the same name and ID as the first media.  The sequence number will be different.

Overwrite Same Media Name or Blank Media First, then Any Media

Overwrite any media found in the device (as long as it has a different ID from the first media's ID).  All subsequent media are reformatted with the same name and ID as the first media.  Only the sequence number will be different.

Timeout for Additional Media

Number of minutes ARCserve will attempt to write to media before canceling job.


Related Topics

  Specifying the media overwrite/append rules for your backup job


Specifying a password for your backup job

You can specify a Session/Encryption password for an entire backup job, for data from a selected drive, or for data from a database backup agent.  The password will be required in order to restore the data from media.  You can select to compress or encrypt your backup files by selecting the appropriate check box.  However, you MUST type the Session/Encryption password in Session/Encryption Password edit box in order to restore this session!


Related Topics

  Specifying a session password for a selected drive or for an entire backup job


Verifying your data on media

ARCserve allows you to verify that your data was correctly backed up to media.  You can verify the data for the entire backup job, or for a selected drive that is included in your backup job.  The global verification options (applied to the entire job) will be overridden by the options selected for a drive.

Scan Backup Media Contents

Check the header of each file on the backup media.  If the header is readable, ARCserve assumes the data is reliable.  If the header is not readable, the Activity Log is updated with this information.  Of the two verification methods, this one is faster.

Compare Backup Media to Disk

Read blocks of data from the media and compares the data, byte for byte, against the source files on the source machine.  This option is more time consuming, but it ensures that all data on the media is exactly as it is on disk.  If ARCserve finds a mismatch, the Activity Log is updated with this information.


Related Topics

  Verifying the data for selected drive or for an entire backup job


Specifying pre/post commands

ARCserve allows you to specify pre/post commands that are run immediately before and/or after your data is backed up to media.  You can specify pre/post commands:

For the entire backup job: These commands are executed at the beginning or end of the job.

For a selected machine: These commands are executed before and/or after the data from the selected machine is backed up.

If you specify pre/post commands for the entire job, as well as for machines in the job, the global pre/post commands are executed before/after the job starts/ends and local commands are executed when the selected machine is backed up.


Related Topics

  Specifying a pre/post command for a selected machine or for an entire job


Pre/Post options

These options allow you to run a command on your machine before and/or after the job is executed.  For example, you may want to use this option to load a virus scanning application before files are backed up and then run a batch file you created that sends a detailed report to the printer


Pre/Post options

The available pre/post options are:

Run Command Before Operation

Enter the path to and name of the file to be executed on the machine before the operation takes off.

Delay in Minutes

Enter the time to wait before the operation will start when the appropriate exit code is detected.  This period of time gives the application or file specified in the Run Command Before Operation field time to process.

On Exit Code

ARCserve detects exit codes of other programs.  You can specify the following options for a particular exit code:

Run Operation Immediately - The operation runs immediately if the appropriate code is selected.

Skip Operation - The operation does not run if the appropriate exit code is detected.

Skip Post Application - Skip any commands specified to run after the operation if the appropriate code is detected.

Run Command After Operation

Enter the path to and name of the file to be executed on the machine after the operation is completed.

Do not run Command if

Specify for a operation not to run if ARCserve detects that the following events occur:

Operation Fails - If ARCserve detects that an operation fails, then an operation does not run.

Operation is Incomplete - If ARCserve detects that an operation is not completed, an operation does not run.

Operation is Complete - If ARCserve detects that an operation is completed, an operation does not run.


Run Command Before Operation

Enter the path to and name of the file to be executed on the machine before the operation takes off.


On exit code

ARCserve detects exit codes of other programs.  Enter the exit code in the adjacent field and select one of options for that particular code:

Run Operation Immediately - The operation runs immediately if the appropriate code is selected.

Skip Operation - The operation does not run if the appropriate exit code is detected.

Skip Post Application - Skip any commands specified to run after the operation if the appropriate code is detected.


Exit Code

ARCserve detects exit codes of other programs.  Enter the exit code in the adjacent field and select one of options for that particular code.


Run Operation Immediately

The operation runs immediately if the appropriate exit code is selected.


Skip Operation

The operation does not run if the appropriate exit code is detected.


Skip Post Application

Skip any commands specified to run after the operation if the appropriate code is detected.


Delay

Enter the time to wait before the operation will start when the appropriate exit code is detected.  This period of time gives the application or file specified in the Run Command Before Operation field time to process.


Minutes

Enter the time to wait before the operation will start when the appropriate exit code is detected.  This period of time gives the application or file specified in the Run Command Before Operation field time to process.


Run Command After Operation

Enter the path to and name of the file to be executed on the machine after the operation is completed.


Operation Fails

If ARCserve detects that an operation fails, then an operation does not run.


Operation is Incomplete

If ARCserve detects that an operation is not completed, an operation does not run.


Operation is Complete

If ARCserve detects that an operation is completed, an operation does not run.


Backing up Windows NT machines
Backing up Windows NT/2000 machines

ARCserve allows you to back up any Windows NT/2000 machine on your Microsoft network.  Backing up a Windows NT/2000 machine can be done one of two ways:

Back up the administrative shared drives

Back up user shared files, directories, and drives

Administrative shared drives

By default, Windows NT/2000 creates an administrative share for the root directory of each drive on the machine.  Unless the administrative share is deleted, you can select it for backup and ARCserve is able to back up all the files and directories on the drive.

User shared drives and directories

In addition to creating default administrative shares, Windows NT/2000 also allows you to designate specific files and directories as shareable.  The owner of these files and directories has specified that they are accessible to all.  These files and directories are displayed in ARCserve's Browser, and with a click of the mouse button, you can quickly select these specially shared files and directories for backup.

Performing domain or workgroup level backups

Do you want to quickly back up all the machines belonging to a specific domain or workgroup?  Since ARCserve separates and lists Windows NT/2000 machines by the domain or workgroup to which they belong, this is easily done by selecting the name of the domain or workgroup.  Doing this automatically selects all the machines that are members of the domain or workgroup for backup.


Related Topics

  Backing up a Windows NT Registry


Backing up a Windows NT Registry or System State

ARCserve allows you to backup the Windows NT Registry or System State for a Windows NT or Windows 2000 machine.  You must enter security information for the machine in order to back up the registry information.


Related Topics

  Select a Backup Method

  System State Restore


Backing up a NetWare server

The optional Client Agent for NetWare is available for backing up NetWare file servers.  Without the agent, NetWare-specific files (such as bindery and NDS information) are backed up as DOS files.  With the agent, all NetWare-specific files are backed up intact, ensuring complete backup/restore of the NetWare file server.  Client agent software is also available for other operating systems.

Note: You must specify a NetWare user in order to backup a NetWare server.


Restoring


Restoring data from media

See the following topics:

About restoring

Submitting a restore job

Selecting data from media

Selecting a destination for your restored data

Options for restore jobs

Recovering from a disaster


About restoring

Each restore job requires a source and destination.  The files you select as your source will always come from a media, and the place you select as your destination will always be a hard drive.

ARCserve provides you with four methods for selecting the data you want to restore (the source), Restore by Tree, Media, Query, and Tape Media.  Three of these methods use information logged in ARCserve's database, while the fourth method doesn't.  In addition, if you have separately purchased the Image Backup Option, you will also have Restore by Image available.

You also have several methods for selecting a Destination to restore the data to the machine.


Related Topics

  Submitting a Restore Job


Selecting data from media

Although the files that you restore will always come from a media, the way you select these source files can vary.  ARCserve provides you with the most convenient and thorough methods for finding the files you want to restore.  There are five methods by which you can choose your source files:

Restore by Tree - Using its database, ARCserve reconstructs a directory tree in the Browser of all machines, directories, and files that were backed up.

Restore by Session - Using its database, ARCserve displays all media used for backups and the source for each session on the media.

Restore by Query - You specify a search pattern and ARCserve searches its database for the specified files and directories.

Restore by Image - Restore an entire drive.  This option is only available if you purchase the ARCserve Image Option.

Restore by Backup Media - Place a media in the storage device and select a particular media session to restore.

NOTE:  An additional Restore method appears on the list in the drop-down box, Restore by Image.  This method refers to the ARCserve Image Option, which is sold separately.  If you have not purchased the Image Option this Restore method is not available.

The method you choose to select your source depends on what you know about the files you want to restore and the media(s) you need to use.

The "Restore by Query" source view uses the ARCserve database and a search pattern that you specify to display files you want to restore.  The Restore by Query can be as general or specific as you want.  You can specify a search pattern directed towards a specific machine, directories, or files.  Subdirectories can also be included in the search.

Use the "Restore by Query" source view when you know the names of the files and/or directories you want to restore, but do not know the machine it was backed up from or the media it was backed up to.


Restoring by Tree

The Restore by Tree view lets you restore a specific directory or drive.  This view displays a machine tree of files and directories that were backed up with ARCserve.


Related Topics

  Selecting data using the Restore by Tree view


Restoring by Session

The Restore by Session view allows you to select the session, and the files and directories you want to restore.  This source view is useful if you know from which media you want to restore, but you may not be sure which session it is in.


Related Topics

  Select data using the Restore by Session View


Restoring by Query

Use the Restore by Query source view to restore files when you know the name of the file or directory you want to restore, but do not know the machine it was backed up from or the media(s) it was backed up to.

This view also uses ARCserve's database.  As long as the file and directory information is logged in the database, you can effectively use this view to select files to restore.

Note: This source view is useful if either:

You know the entire path, a partial path, or only the name of the file or directory to restore.

You do not know which machine it was backed up from or which media it was backed up to.


Related Topics

  Restore data by query


Restoring by Backup Media

The Restore by Backup Media Records allows you to restore complete sessions on a media in a storage device.  All files in the session are restored to the destination, unless filters are added to the job.

This source view is useful if information from your ARCserve database is unavailable, or you are trying to recover your network after a disaster.


Related Topics

  Restoring by Backup Media


Restoring by Image

The Restore by Image View lets you restore drives based on an image backup.

This option is only available if you have purchased the ARCserve Image Option.


Related Topics

  Restoring by Image


Selecting a destination for your restored data

With the default option, Restore files to their original location(s) selected, your files are restored to their original machine and path.  You can also clear this option and select another destination using the Browser.  In addition, with either type of destination, you can use the Options button to specify destination options.


Related Topics

  Selecting a destination for your restored data


Specifying destination options

The Destination options determine how the directory structure is created on the destination when files are restored.  They also determine which files (if any) can be overwritten.


Related Topics

  Specifying Destination Options


Recovering from a disaster

When recovering from a disaster, first make sure that you have the appropriate installation disks and the backup media to restore from.


Related Topics

  Recover procedures for a Windows NT machine

  Preparing for a disaster


Preparing for a disaster

This section describes how to use ARCserve to best protect and recover your data in the event of a system failure.

Make sure you back up ARCserve's database often

Whenever you select your ARCserve home directory for backup, ARCserve's database is backed up as well.  Always maintain a current backup of your ARCserve database files so that recovering from a disaster is easier.

Always maintain current backups

The most important thing you can do to ensure against data loss is to maintain current backups of all your network machines.   If you do not have these backups, then ARCserve is limited in its ability to recover against data loss or disaster.  Be sure to create a media rotation scheme using different backup methods and scheduling as a means of maintaining current backups.

If something happens to any machine between full backups, you can recover with the last full backup (a backup job with the Full (Clear Archive Bit) method selected), and your most recent differential or incremental backup (which contains all the modifications to the data since the last full backup).


Managing Data


Utilities

ARCserve offers several utilities that you can use to manage files.  The utilities are:

Recover Database  - Overwrites your ARCserve database files with a backed up copy of the database files.

Merge Media - Merges information from media into your ARCserve database.

Scan Media - Reports information about one or more media backup sessions.

Compare - Compares the contents of a media to files on a machine.

Count - Counts files on a machine.

Purge - Deletes files from a machine.


Recovering the ARCserve Database

This option allows you to restore database files from a media to your ARCserve database.

Each time you run a backup job, ARCserve records information in its databases about the machines, directories, and files that have been backed up, and the media that were used.  This allows ARCserve to locate files whenever you need to restore them.  This database information is backed up whenever you back up your ARCserve home directory.

The Recover Database option lets you restore this information to your ARCserve database.

Unlike the Merge Media option, which appends database information from media to your existing database files, the Recover Database option overwrites existing database files.

Why would you need to use the Recover Database option?

You could use the Recover Database option anytime you lose your ARCserve database files, such as after a disaster like a fire, flood, or a machine crash, and you want to restore your files on a machine where you can create new ARCserve database files.

Note:  If you have multiple drives and one of them is performing a Recover Database job, and you want to send another job that would write to the database (such as Backup), disable writing to the database to avoid any problems with the Recover Database job.


Related Topics

  Recover Database Options

  Recovering the ARCserve Database


Recover Database Options

ARCserve provides several types of advanced database recovery options.  They are:

Backup Media - Specify media options for the job such as the media timeout period.

Operation - Specify the database session date you want to restore from.  The database session created on or before this date will be restored.

Pre/Post options - Run commands or batch files before the job runs and/or after it finishes.

Log - Allow you to determine the level of detail you want recorded into the Job Queue's Log.

Alert - Send messages about events in your operation.

See Applying job options to learn how to apply these options to your job.


Merging Media Information

If you need to restore files to an ARCserve machine that you did not use to create the backup, or if you removed information from your ARCserve database that you now need, you can use the Merge Media option.

This option allows you to take a media that contains one or more backup sessions and merge the information from the media into your ARCserve database.  The database information from the media will be appended to your existing database files.

Each time you run a backup job, ARCserve records information in its databases about the machines, directories, and files that have been backed up, and the media that were used.  This allows ARCserve to locate files whenever you need to restore them.  This database information is backed up whenever you back up your ARCserve home directory.

If you have a media that has a backup session that is not included in the ARCserve database (the backup was created using ARCserve on a different machine, for example), you can use the Merge Media option to get the media's information into the database in ARCserve's home directory.

Unlike the Recover Database utility, which overwrites existing database files with database information from media, the Merge Media utility appends database information to your existing database files.

Why would you need to use the Merge Media option?

You could use the Merge Media utility if you need to restore files to an ARCserve machine that you did not use to create the backup.  You could also use the Merge Media utility if you pruned (deleted) information from your ARCserve database that you now need.


Related Topics

  Merge Media Options


Merge Media Options

See Applying job options to learn how to apply these options to your job.

ARCserve provides several types of advanced merge options.  They are:

Backup Media - Specify media options for the job such as the media timeout period

Pre/Post options - Run commands or batch files before the job runs and/or after it finishes

Log - Allow you to determine the level of detail you want recorded into the Job Queue's Log

Alert - Send messages about events in your operation


Scanning Media

This option gives you information about your media backup sessions.  Each source that you select to back up is saved on media as an individual session.  You can scan a single session or an entire media.  Results of the Scan Media job can be seen in the Job Queue (by clicking the Log tab).

The Log tab in the Options menu allows you to select the level of detail you will see in the Job Queue's Log.  You can select to see just summary information and any errors that occurred during the scan or you can select to see each file that was backed up as well as the summary information and any errors.

Why would you use the Scan Media option?

Use the Scan Media option to find out what is on a media.

You would need to do this if you are trying to recover an ARCserve machine and you need to find the most recent backup of the ARCserve database so that you can restore it.  You could also use the Scan Media option if you want a list of the files that were backed up.


Related Topics

  Scan Media Procedures

  Scan Media Options


Scan Media Options

See Applying job options to learn how to apply these options to your job.

ARCserve provides several types of advanced scan options.  They are:

Backup Media - Specify media options for the job such as the media timeout period.

Operation - Specify some general options for the job such as whether or not to scan files with CRC verification.

Pre/Post options - Run commands or batch files before the job runs and/or after it finishes.

Log - Allow you to determine the level of detail you want recorded into the Job Queue's Log.

Alert - Send messages about events in your operation.


Comparing Media

This option allows you to compare the contents of a media session to files on a machine.

Results of the Compare Media job can be seen in the Job Queue (by clicking the Log tab).

The Log tab in the Options menu allows you to select the level of detail you will see in the Job Queue's Log.  You can select to see just summary information and any errors that occurred during the scan, or you can create a report that lists each file that was compared and indicates if there is any difference in the file name, size, date, time, or attributes.

Why would you use the Compare Media option?

You could use this option after a backup to verify that the backup copied all of the files to media without error.


Related Topics

  Comparing Media Procedures

  Compare Media Options


Compare Media Options

See Applying job options to learn how to apply these options to your job.

ARCserve provides several types of advanced compare options.  They are:

Backup Media Specify media options for the job such as the media timeout period.

Operation - Specify some general options for the job.

Pre/Post options - Run commands or batch files before the job runs and/or after it finishes.

Log - Allow you to determine the level of detail you want recorded into the Job Queue's Log.

Alert - Send messages about events in your operation.


Counting files

This option allows you to count the number of files and directories on a machine.

Results of the Count job can be seen in the Job Queue (by clicking the Log tab).

The Log tab in the Options menu allows you to select the level of detail you will see in the Job Queue's Log.  You can select to see just totals and any errors that occurred or you can create a report that lists each file in every directory that was counted.  This includes the file name, size, date, time, and file attributes.


Related Topics

  Counting Files Procedure

  Count Options


Count Options

ARCserve provides several types of advanced count options.  They are:

Operation - Specify some general options for the job.

Pre/Post options - Run commands or batch files before the job runs and/or after it finishes.

Log - Allow you to determine the level of detail you want recorded into the Job Queue's Log.

Virus - Scan files for viruses before they are counted.

Alert - Send messages about events in your operation.

See Applying job options to learn how to apply these options to your job.


Deleting (Purging) files

This option allows you to delete files and directories from a machine.  (Using filters, you can include or exclude files to be deleted.)

Results of the Purge job can be seen in the Job Queue (by clicking the Log tab).

The Log tab in the Options menu allows you to select the level of detail you will see in the Job Queue's Log.  You can select to see just totals and any errors that occurred or you can create a report that lists each file and directory that was deleted.

Warning:  This utility does not delete records from the ARCserve database, it deletes the actual files from the filesystems on the machines where they reside.


Related Topics

  Deleting (purging) Files Procedure

  Purge Media Options


Purge Media Options

See Applying job options to learn how to apply these options to your job.

ARCserve provides several types of advanced purge options.  They are:

Operation - Specify some general options for the job such as whether or not to remove directories.

Pre/Post options - Run commands or batch files before the  job runs and/or after it finishes.

Log - Allow you to determine the level of detail you want recorded into the Job Queue's Log.

Alert - Send messages about events in your operation.


APPLYING OPTIONS


Applying job options

Job options apply to the current job that you are configuring.  They can be used to configure any type of job that is submitted to the ARCserve engine, including backup, copy, and restore jobs.


Related Topics

  Applying Job Options


Destination options (Restore and Copy)

The Destination options determine how the directory structure is created on the destination when files are copied or restored.  They also determine which files (if any) can be overwritten.

Directory Structure options

Select the method ARCserve should use to create directories on your destination.

Do Not Create the Base Directories - default

Do not create the base directory on the destination path, but create all subdirectories below the source base directory.  A "base directory" is considered the first directory selected in the source path.

Create Directories from the Base

Create the destination path beginning from the base directory.

Create Entire Path from the Root

Create the entire source path (except the root drive or volume name) on the destination.  No files from any parent directories are restored.  Only the directory path to the base directory is created on the destination.

Create Empty Directories

If the source has a directory that is empty, it will be copied to the destination.

File Conflict Resolution options:

Select the method ARCserve should use when there are files on the destination disk that have the same name as files being copied from the source.  The default is Overwrite All Files.

Overwrite All Files

Restore all source files to the destination regardless of conflicting file names.  The files from the source will overwrite existing files on the destination.

Rename Files

Copy the source file to the destination with the same filename but a different extension. The extension will maintain the first two characters of the original, but the last character will be 1, 2, 3..., depending on how many files ARCserve has encountered with the same name.  Filenames without extensions will be renamed with extensions ".__0", ".__1", ".__2", etc.

Skip Existing Files

Do not restore a source file if a file with the same name already exists on the destination.

Overwrite with Newer Files Only

Only restore source files whose modification date is later than the modification date of the file with the same name on the destination. Source files whose modification date is earlier will not be copied to the destination.

Confirm Overwrites (for Run Now only)

Applies when submitting an immediate job (if Run Now is selected).  Before ARCserve tries to restore the source file, you will be prompted to confirm that you want the file on the destination to be overwritten.


Do Not Create the Base Directories

Do not create the base directory on the destination path, but create all subdirectories below the source base directory.  A "base directory" is considered the last directory selected in the source path.


Create Directories from the Base

Create the destination path beginning from the base directory.


Create Entire Path from the Root

Create the entire source path (except the root drive or volume name) on the destination.  No files from any parent directories are restored.  Only the directory path to the base directory is created on the destination.


Create Empty Directories

If the source has a directory that is empty, it will be copied to the destination.


Overwrite All Files

Restore all source files to the destination regardless of conflicting file names.  The files from the source will overwrite existing files on the destination.


Rename Files

Copy the source file to the destination with the same filename but a different extension.


Skip Existing Files

Do not restore a source file if a file with the same name already exists on the destination.


Overwrite with Newer Files Only

Only restore source files whose modification date is later than the modification date of the file with the same name on the destination.


Confirm Overwrites (for Run Now only)

Before ARCserve tries to restore the source file, you will be prompted to confirm that you want the file on the destination to be overwritten.


Log options

The Log options determine the level of detail that is included in the log report for the operation.  You can view the log report in the Job Queue window or Database Manager window (Job Records).

The log options can be set in the following windows:

Backup

Restore

Compare

Scan

Copy

Count

Delete

Purge

Recover DB

Merge

The log options are:

Log All Activity

Record all of the activity that occurs while the job is running in the Job Log.

Log Summary Only

Record summary information of the job (including source, destination, session number, and totals) and errors.

Log Disabled

Do not record any information about this job in the Job Log.


Log All Activity

Record all of the activity that occurs while the job is running in the Job Log.


Log Summary Only

Record summary information of the job (including source, destination, session number, and totals) and errors.


Log Disabled

Do not record any information about this job in the Job Log.


Operation options (Backup)

The Operation options for Backup determines related actions that occur during or after the backup, and the level of information that is recorded in the database.

Basic Operation options

The (basic) Operation options are:

Delete Files After Backup

Delete source files from the source machine after they have been backed up to media.  Use this option to perform disk grooming.  Set a filter to back up files that haven't been accessed for a certain period of time (say, three months or so), and then select this option to delete these files from the source disk.

Disable File Estimate

By default, before any file is backed up to media, ARCserve, performs an estimate of how long the job will take.  Select this option if you want ARCserve to skip this function.

Calculate and store CRC value on Backup media

Calculating and storing the CRC value on the backup media will enable ARCserve to perform CRC verification during the backup job. To instruct ARCserve to use the CRC value stored on media, see the Backup Options, Verification tab .

Eject Backup Media at the End

Eject the media from the drive after the job finishes.  This helps prevent any other job from overwriting information on this media.

Backup ARCserve Database files

Select this option to back up the ARCserve database files with your backup job. You must also select whether to backup the database on every backup job or only when the ARCserve home directory is backed up, by clicking on the appropriate option button.

Database Operation options

The database operation options are:

Record Detail Information

Log all the information pertaining to the source and destination in the database.

Record Job and Session Information Only

Log only job and session information in the ARCserve database.

Disable Database Recording

Do not log any information about this job in the database.  Select this option if you are backing up the ARCserve database or if you have limited disk space.

You will have to submit a Merge Media operation before you can use any of the database views to restore this data.  Or, you can restore data from this job using the Restore by Media source view.


Delete Files After Backup

Delete source files from the source machine after they have been backed up to media.  Use this option to perform disk grooming.  Set a filter to back up files that haven't been accessed for a certain period of time (say, three months or so), and then select this option to delete these files from the source disk.


Disable File Estimate

By default, before any file is backed up to media, ARCserve, performs an estimate of how long the job will take.  Select this option if you want ARCserve to skip this function.


Calculate and Store CRC Value on Backup Media

Calculating and storing the CRC value on the backup media will enable ARCserve to perform CRC verification during the backup job. To instruct ARCserve to use the CRC value stored on media, see the Backup Options, Verification tab.


Eject Backup Media at the End

Eject the media from the drive after the job finishes.  This helps prevent any other job from overwriting information on this media.


Backup ARCserve Database file

Select this option to back up the ARCserve database files with your backup job. You must also select whether to backup the database on every backup job or only when the ARCserve home directory is backed up, by clicking on the appropriate option button.


Only if ARCserve Home Directory is selected

Select this option to backup the database only when the ARCserve home directory is backed up.


In every Backup job

Select this option to backup the database with every backup job.


Copy Media to MBO after Backup

This option backs up to media, then copies the files from the media to the mainframe.


Enable Data Multiplexing

Check this box to enable Data Multiplexing which removes the limitation of processing sources in sequence, one volume at a time and allows for simultaneous multiple streams of data to one destination.  Data Multiplexing attempts to meet the write throughput limits of the destination media, and is designed to increase efficiency to allow for faster backups.

Note:   Some devices may not support Data Multiplexing.


Record Detail Information

Log all the information pertaining to the source and destination in the database.


Record Job and Session Information Only

Log only job and session information in the ARCserve database.


Disable Database Recording

Do not log any information about this job in the database.  Select this option if you are backing up the ARCserve database or if you have limited disk space.

You will have to submit a Merge Media operation before you can use any of the database views to restore this data.  Or, you can restore data from this job using the Restore by Media source view.


Operation options (Copy)

The Operation options (for Copy) determine related actions that occur during or after the copy operation, and the level of information that is recorded in the database.

Basic Operations options

The basic Operation options for Copy are:

Mirror

Create a mirror image of the source machine on the destination.  Copy files and directories from source and delete all files and directories that do not appear on source.

Delete Files

Delete files from the source machine after copying to destination.

Copy File Security Information (NTFS only)

Copy the file-level security information for file access on NTFS volumes.

Database options

The Database Operation options for Copy are:

Record Job Information Only

Record job information.

Disable Database Recording

Do not record job information.


Mirror

Create a mirror image of the source machine on the destination.  Copy files and directories from source and delete all files and directories that do not appear on source.


Delete Files

Delete files from the source machine after copying to destination.


Copy File Security Information (NTFS only)

Copy the file-level security information for file access on NTFS volumes.


Record Job Information Only

Record job information.


Disable Database Recording

Do not record job information.


Operation options

The Operations options determine related actions that occur during or after the job, and the level of information that is recorded in the database.

Restore Registry Files and Event logs: Restore registry files and event logs to the machine.

Restore and Preserve Directory Attributes and Security Information: Restore the existing directory attributes (such as "Read Only", "Archive" and "Hidden") and security data to the machine.

Database

Record Job Information Only: Record job information.

Disable Database Recording: do not record job information.


Restore Registry Files and Event logs

Operation_options_Restore_Compare_Scan_Count

Restore registry files and event logs to the machine.


Restore and Preserve Directory Attributes and Security Information

Operation_options_Restore_Compare_Scan_Count

Restore the existing directory attributes (such as "Read Only", "Archive" and "Hidden") and security data to the machine.


Record Job Information Only

Operation_options_Restore_Compare_Scan_Count

Keep a record of this job in the ARCserve database.


Disable Database Recording

Operation_options_Restore_Compare_Scan_Count

Do not keep a record of this job in the ARCserve database.


Related Topics

  Operation Options (Recover Database)

  Operation Options (Compare Media)

  Operation Options (Count)

  Operation Options (Purge)

  Operation Options (Scan)


Operation Options (Recover Database)

Most Recent Database Session Backup up On or Before

Specify the date the database was backed up.  The database session created on or before this date will be restored.


Operation Options (Compare Media)

The Operation options for Compare include two Database options:

Report Job Information Only

Keeps a record of the current job in the ARCserve database.

Disable Database Recording

Does not keep a record of the job in the ARCserve database.


Operation Options (Count)

The Operation options for count include two Database options:

Report Job Information Only

Keeps a record of the current job in the ARCserve database.

Disable Database Recording

Does not keep a record of the job in the ARCserve database.


Operation Options (Purge)

The Operation options for Purge allow you to choose whether or not to Remove Directories.  There are also two Database Options:

Remove Directories

Remove directories if all files within the directory are purged.

Report Job Information Only

Keeps a record of the current job in the ARCserve database.

Disable Database Recording

Does not keep a record of the job in the ARCserve database.


Remove Directories

Remove directories if all files within the directory are purged.


Report Job Information Only

Keeps a record of the job in the ARCserve database.


Disable Database Recording

Does not keep a record of the job in the ARCserve database.


Operation Options (Scan)

The Operation options for Scan allow you to choose whether to scan files with CRC verification.  There are also two Database Options:

Scan files with CRC verification

Scan files with a CRC check.

Report Job Information Only

Keeps a record of the current job in the ARCserve database.

Disable Database Recording

Does not keep a record of the job in the ARCserve database.


Scan Files with CRC verification

Scan files with a CRC check.


Report Job Information Only

Keeps a record of the current job in the ARCserve database.


Disable Database Recording

Does not keep a record of the job in the ARCserve database.


Retry options (Backup and Copy)

There are two types of Retry options:

Open File Retry: determines how frequently (if at all) ARCserve will attempt to back up or copy open files.

File Sharing: determines how ARCserve shares the files with other applications when backing up or copying a file.

Open File Retry options

Select the option ARCserve should take if it attempts to back up or copy an open file:

Retry Immediately

Back up or copy the file again immediately after the first attempt failed.  If the file is still unavailable, this information is written to ARCserve's Activity Log, and the job is labeled "Incomplete".

Retry After Job

Back up or copy the file again after all the other source files have been backed up.  If the file is still unavailable after these attempts, this information is written to ARCserve's Activity Log, and the job is labeled "Incomplete".

Number of Retries

Number of times you want ARCserve to try to back up or copy the file.

Retry Interval (sec)

Period of time you want ARCserve to wait between attempts.

File Sharing options

The file sharing options are:

Use Deny None if Deny Write Fails [default]

Attempt to place the file in "Deny Write" mode.  If this is not possible (because the file is already open), then place the file into "Deny None" mode.

Use Lock Mode if Deny Write Fails

Attempt to place the file in "Deny Write" mode.  If this is not possible (because the file is already open), then lock the file completely (prohibiting any user from opening or writing to the file).  This option ensures the most recent version of the file is backed up or copied.

Deny Write

Prevent another process from writing to the file while ARCserve has it open.  If another process has the file open before ARCserve can open it, ARCserve will not back up the file (unless you specified an Open File Retry option).

Deny None

Allow another process to read or write to the file, regardless of whether ARCserve opens it first or opens it after another process already has it open.  This option ensures that your files are up-to-date, although the file that was backed up or copied may not be the most recent version.

Considerations

If you use applications (such as e-mail) that are in operation 24 hours a day, you may want to choose one of the Deny None methods.  As long as no other process is writing to these files during the job, the backup or copy will be consistent.

If you want to ensure that only the most current version of every file is backed up or copied, you should select a Deny Write or Lock Mode option.


Retry Immediately

Back up or copy the file again immediately after the first attempt failed.  If the file is still unavailable, this information is written to ARCserve's Activity Log, and the job is labeled "Incomplete".


Retry After Job

Back up or copy the file again after all the other source files have been backed up.  If the file is still unavailable after these attempts, this information is written to ARCserve's Activity Log, and the job is labeled "Incomplete".


Number of Retries

Number of times you want ARCserve to try to back up or copy the file.


Retry Interval (sec)

Period of time you want ARCserve to wait between attempts.


Use Deny None if Deny Write Fails

Attempt to place the file in "Deny Write" mode.  If this is not possible (because the file is already open), then place the file into "Deny None" mode.


Use Lock Mode if Deny Write Fails

Attempt to place the file in "Deny Write" mode.  If this is not possible (because the file is already open), then lock the file completely (prohibiting any user from opening or writing to the file).  This option ensures the most recent version of the file is backed up or copied.


Deny Write

Prevent another process from writing to the file while ARCserve has it open.  If another process has the file open before ARCserve can open it, ARCserve will not back up the file (unless you specified an Open File Retry option).


Deny None

Allow another process to read or write to the file, regardless of whether ARCserve opens it first or opens it after another process already has it open.  This option ensures that your files are up-to-date, although the file that was backed up or copied may not be the most recent version.


Backup Media options

The following Media options are available for backup jobs:

Options for First Backup Media: determine the overwrite rules for the first media that is used for the backup job.

Options for Additional Backup Media: determine the overwrite rules for the additional media.

Compression/Encryption: Decide if files should be compressed or encrypted before backup and specify a password for encrypted files.

First Backup Media Options

The first backup media is the media you use when the backup job begins.  The options for the first media are:

Append to Media

Append job sessions to the selected media.

Overwrite Same Media Name, or Blank Media

Overwrite the media in the drive only if it is the one you specified for the job or if the media is blank.  If neither of these conditions are met, ARCserve prompts you to supply the specific media name.

Overwrite Same Media Name or Blank Media First, then Any Media

Overwrite any media found in the drive. If you select this media option, ARCserve checks to see if the media in the drive is the one specified for the job.  If it isn't, ARCserve checks to see if the media is blank.  If the media isn't blank either, ARCserve reformats whatever media it finds in the device and starts backing up files at the beginning of the media.

Timeout for First Media

Number of minutes ARCserve will attempt to write to media before canceling job.

Options for Additional Backup Media

These options apply to jobs that require more than one media.  You need to specify which media ARCserve can use when the job spans media.

Overwrite Same Media Name, or Blank Media

Write to the media in the device only if it has the same media name (but a different media ID) or if it is blank.  ARCserve remembers the name and ID of the job's first media.  When the job requires additional media, ARCserve checks if the new media has the same name (but different media ID) or if it is a blank media.  As long as the ID is different, ARCserve reformats the media, giving it the same name and ID as the first media.  The sequence number will be different.

Overwrite Same Media Name or Blank Media First, then Any Media

Overwrite any media found in the device (as long as it has a different ID from the first media's ID).  All subsequent media are reformatted with the same name and ID as the first media.  Only the sequence number will be different.

Timeout for Additional Media

Number of minutes ARCserve will attempt to write to media before canceling job.

Compression/Encryption

Compress Files Before Backup

Specify whether or not files will be compressed before backup.

Encrypt Files Before Backup

Specify whether or not files will be encrypted before backup.

Session/Encryption Password

Specify a Session/encryption password that will be required in order to restore this data from media.

Note:  You MUST remember the Session/Encryption password in order to restore this session!


Append to Media

Append job sessions to the selected media.


Overwrite Same Media Name, or Blank Media

Overwrite the media in the drive only if it is the one you specified for the job or if the media is blank.  If neither of these conditions are met, ARCserve prompts you to supply the specific media name.


Overwrite Same Media Name, or Blank Media First, then Any Media

Overwrite any media found in the drive. If you select this media option, ARCserve checks to see if the media in the drive is the one specified for the job.  If it isn't, ARCserve checks to see if the media is blank.  If the media isn't blank either, ARCserve reformats whatever media it finds in the device and starts backing up files at the beginning of the media.


Overwrite Same Media Name, or Any Media First, then Blank Media

If you select this media option, ARCserve checks to see if the media in the drive is the one specified for the job.  If it is not, ARCserve will attempt to reformat whatever media it finds in the device.  If it cannot reformat the media that it finds ARCserve will then check for blank media and start backing up files.


Timeout for First Media

Number of minutes ARCserve will attempt to write to media before canceling job.


Overwrite Same Media Name, or Blank Media, Additional
Overwrite Same Media Name, or Blank Media

Write to the media in the device only if it has the same media name (but a different media ID) or if it is blank.  ARCserve remembers the name and ID of the job's first media.  When the job requires additional media, ARCserve checks if the new media has the same name (but different media ID) or if it is a blank media.  As long as the ID is different, ARCserve reformats the media, giving it the same name and ID as the first media.  The sequence number will be different.


Overwrite Same Media Name, or Blank Media First, then Any Media, Additional
Overwrite Same Media Name, or Blank Media First, then Any Media

Overwrite any media found in the device (as long as it has a different ID from the first media's ID).  All subsequent media are reformatted with the same name and ID as the first media.  Only the sequence number will be different.


Overwrite Same Media Name, or Any Media First, then Blank Media, Additional
Overwrite Same Media Name, or Any Media First, then Blank Media

Write to the media in the device only if it has the same media name (but a different media ID) or any media found in the device (as long as it has a different ID from the first media's ID).  Or, if the media is blank ARCserve remembers the name and ID of the job's first media.  All subsequent media are reformatted with the same name and ID as the first media.  Only the sequence number will be different.


Timeout for Additional Media

Number of minutes ARCserve will attempt to write to media before canceling job.


Session/Encryption Password

Specify a Session/Encryption password that will be required in order to restore this data from media.

Note:  You MUST remember the Session/Encryption password in order to restore this session!


Compress Files Before Backup

Specify whether or not files will be compressed before backup.


Encrypt Files Before Backup

Specify whether or not files will be encrypted before backup.


Backup Media options (Restore, Compare, Scan)

The Media options for Restore, Compare, and Scan allow you to specify a timeout period ARCserve should wait for you to provide the media you need to restore your data.  Available Media options are:

Timeout for First Backup Media

Period of time that ARCserve waits for the first media required for your restore job.  If the time expires and the first media has not been provided, the job will fail.  By default, ARCserve will wait five minutes.

Timeout for Additional Backup Media

Period of time that ARCserve waits for any additional media to become available.  By default, the timeout is 60 minutes.


Timeout for First Backup Media

Period of time that ARCserve waits for the first media required for your restore job.  The default is five minutes.


Timeout for Additional Backup Media

Period of time that ARCserve waits for any additional media to become available.  The default is no timeout.


Verification options (Backup)

The Backup Verification options allow you to verify that your data was backed up correctly.  (These options may be overridden by specifying local options for individual machines.)  Available Verification options are:

None

The backup is not verified.

Scan Backup Media Contents

Check the header of each file on the backup media.  If the header is readable, ARCserve assumes the data is reliable.  If the header is not readable, the Activity Log is updated with this information.  Of the two verification methods, this one is faster.  If the "Calculate and store CRC value on media" option is selected on the Operation tab, ARCserve will also perform CRC verification by recalculating the CRC value and comparing it with the one stored on media.

Compare Backup Media to Disk

Reads block of data from the media and compares the data, byte for byte, against the source files on the source machine.  This option is more time consuming, but it ensures that all data on the media is exactly as it is on disk.  If ARCserve finds a mismatch, the Activity Log is updated with this information.


None

The backup is not verified.


Scan Backup Media Contents

Check the header of each file on the backup media.  If the header is readable, ARCserve assumes the data is reliable.  If the header is not readable, the Activity Log is updated with this information.  Of the two verification methods, this one is faster.  If the "Calculate and store CRC value on media" option is selected on the Operation tab, ARCserve will also perform CRC verification by recalculating the CRC value and comparing it with the one stored on media.


Compare Backup Media to Disk

Reads blocks of data from the media and compares the data, byte for byte, against the source files on the source machine.  This option is more time consuming, but it ensures that all data on the media is exactly as it is on disk.  If ARCserve finds a mismatch, the Activity Log is updated with this information.


Virus options (Backup, Copy, Count, Restore)

You can automatically scan for viruses during a backup, copy, count, or restore operation using the virus scanning options.  Available virus scanning options are:

Enable Virus Scanning

Select this option to enable virus scanning.

Skip

Do not backup/restore the infected file.

Rename

Rename the infected files with the extension AVB.  (If a file with the same name and the extension AVB exists, then extension AV1 is used, and so on.)

Delete

Delete the infected file.

Cure

ARCserve cures the files that have been found to be virus infected.


Enable Virus Scanning

Select this option to enable virus scanning.


Skip

Do not backup/restore the infected file.


Rename

Rename the infected files with the extension AVB.  (If a file with the same name and the extension AVB exists, then extension AV1 is used, and so on.)


Delete

Delete the infected file.


Cure

ARCserve cures the files that have been found to be virus infected.


Alert Options

You can use the Alert notification system to send messages about events in your backup operation.  For detailed information on the Alert system, refer to the ARCserve User Guide.

Event

Choose one or more of the following events for which you want to be notified:

Event	Description
Job completed successfully	All of the nodes and drives/shares were processed.
Job incomplete	Some nodes and/or drives/shares were missed.
Job canceled by user	The user canceled the job.
Job failed	The job was started but could not be completed.
Virus detected	A virus was detected in one of the files to be backed up. See Virus options (Backup, Copy, Count)
Customized Event	A customized event occurred.  To specify this type of event, enter an error, warning or notification code in the space below the Event drop-box.  You can enter multiple codes and use wild cards, for example, E1???; W*; N1?31.

Methods and Recipients

Choose one or more of the defined Alert configurations.  The <default> configuration means that you will use whatever is configured in Alert Manager.  Before you choose, click the Configure button to define further configurations.

Attach job log

Select this option to include the job log information in the Alert message.  (This option applies for Trouble Tickets and Email only.)

Note: The list you create using Alert Options is saved with the Job Script together with the configuration defined using the Configuration button.


Event List

This area displays events that have already been defined for event-notification.  Using the appropriate buttons, you can add or delete an event, or modify an existing event.


Event

Select an event from the drop-down list box or select Customized Event and enter the appropriate error codes (using wildcard characters) in the field below.


Error

Using wildcard characters, enter error codes for a Customized Event.


Methods and Recipients

Select one or more of the defined Alert configurations.  Choose the Configure button to define additional configurations.


Attach Job Log

Select this option to include the job log information in the Alert message.  (This option applies to Trouble Tickets and E-mail only.)


Related Topics

  Add an event to the Alert list

  Configuring methods and recipients

  Virus options (Backup, Copy, Count)


Configuring methods and recipients

ARCserve allows you to define configurations for your methods and recipients used in the Alert notification system.  A Method and Recipients Configuration is set of available methods (for example, Printer) and their respective recipients (the printers on your network which will receive the alert notification).

Note: The first time you open the Methods and Recipients dialog box, an untitled configuration tree is displayed in the browser at the left of the dialog.  If you modify this configuration, you will be prompted to enter a new name for it.


Related Topics

  Add a new Methods and Recipients Configuration

  Alert Options


Configuring Alert recipients

Configuring Broadcast recipients

Configuring E-mail recipients

Configuring Pager recipients

Configuring SNMP recipients

Configuring the Printer recipient

Configuring Event recipients

Configuring Lotus Notes Recipients


Configuring Pager recipients

The pager option is used to a send an alphanumeric pager message. When you click the Pager tab, the current list of recipients appears:

To add pager recipients, you first need to configure your communications ports for Alert if you have not already done so.


Configuring Pager recipients

Pager Type

Indicate that you are using an alphanumeric pager.

Pager Number

Enter a maximum of 24 characters.  If a digit, such as 9, must be dialed to get a dial tone, it must be included in this field.  A comma can be entered to indicate a one second pause.  If a longer pause is desired, a string of commas can be entered.  A dash (-) can be used to separate digits, but it has no function.  (Since this can vary by modem, you should verify this with your modem manual.)

Pager ID

Enter up to eight digits to identify the pager that will receive the alerts.

Site ID

Enter up to four digits to identify where the alert occurred.  This number is included in the message to the pager.  Therefore, if the number is less than four digits, you should use leading zeros.

Connection Delay

Enter the number of seconds for each delay you want to wait before a connection is made with the pager company.

When a phone number is dialed, a connection is made. The connection may be established immediately or it may be delayed. This will vary with your pager company, location, time of day, telephone equipment, and telephone traffic. If the connection is not established immediately, adding a delay can prevent the alert from being sent before the connection is established.

Message Delay

Enter the number of seconds for each delay you want to wait between the time the connection is made and the alert message is sent.

To complete the process of configuring pager recipients, you need to enter the parameters for the communications port you want the pager message to be broadcast from.

Interpreting the pager message

There are several messages that can be sent to an alphanumeric pager.   Each message is listed below. Words that appear in Italics are variables that will be filled in with an actual user name, workstation address, path and file name, virus name, or server name.

Boot Virus Detected – [username] at [workstation address]

Manager Detected a Virus [virus name] in [path] –[ username]] at [workstation address]

Infected File [server name/path] Detected

Infected File [path*] Accessed by [username] at [workstation address]

This can be the path on a server or workstation.


Related Topics

  Configuring Pager Recipients


Configuring SNMP recipients

The SNMP option is used to send an SNMP 'trap' (message) to an SNMP manager.

An example of an SNMP manager includes Computer Associates Unicenter TNG (The Next Generation).

This section explains the SNMP fields on the SNMP Configuration screen.

When you click the SNMP tab, the current list of managers appears:


Related Topics

  Add SNMP recipients


Configuring the Printer recipient

Print recipients are used to alert users through a printed document.  (These recipients are called Trouble Tickets in the Alert Manger.)


Related Topics

  Configure the Trouble Ticket option or choose a printer


Configuring E-mail recipients

The E-mail option is used to send E-mail messages to specific users.

Note: Microsoft Mail or Microsoft Exchange Client must be installed on your computer in order to be able to send messages or to enter configuration data on this screen. Consult your network manual for instructions about how to set up your E-mail account.


Related Topics

  Configuring E-mail Recipients


Configuring Event recipients

Note: Microsoft Mail or Microsoft Exchange Client must be installed on your computer in order to be able to send messages or to enter configuration data on this screen. Consult your network manual for instructions about how to set up your E-mail account.


Related Topics

  Alert Options

  Add Event Notification Recipients


Configuring Lotus Notes Recipients

The Lotus Notes option is used to send alert messages to specific Lotus Notes users.

Note: Lotus Notes must be installed on your computer in order to be able to send messages or to enter configuration data on this screen. Consult your operating system manual for instructions about how to set up your account.


Related Topics

  Configuring Lotus Notes Recipients


Configuring Unicenter TNG Recipients

The CA-Unicenter TNG (The Next Generation) Option makes it possible to send a message to the CA-Unicenter TNG console and/or World View repository when an alert is generated.


Related Topics

  Configuring Unicenter TNG Recipients


CUSTOMIZING JOBS


Filter basics

The Filter option allows you to configure file filters for your backup, restore, and other jobs.  See the following topics for more information:

Using filters

About filtering

How to apply filters

Modifying and deleting filters

Types of filters

File Pattern filter

Directory filter

File Attributes filter

File Modified/Created/Accessed filters

File Size Filter


About filtering

Filters allow you to include or exclude files and directories from your backup, copy, or restore jobs, as well as from the utilities, such as count and purge.  For example, you could create a filter to back up only those files that were modified on or after a certain date.  You could also create a filter to exclude a particular directory from being restored.  Use the filters to focus on the files you want.

For backup and count jobs, filtering can be performed on a per machine basis.  This means you can include a directory from one machine and exclude the same directory from another machine.  These filters makes it easy for you to create a job that best suits your needs, one that contains only the data that you want.


About filtering

Fields

Exclude over include

One thing you should be aware of is that exclusions will always take precedence over inclusions.  For example, if you add a File Pattern filter to include only files that have a .exe extension, and you add a Directory filter to exclude your \system32 directory, all .exe files in the \system32 directory will be excluded.

Include only

Specifying to "Include" files will result in a backup or restore containing only those files that satisfy the filter specifications.  For example, suppose in the source area you selected to back up your entire local hard drive, then set up a Directory filter to include files in the \system32 directory.  The result would be that ARCserve would only back up files from your \system32 directory.  No other files would be backed up.

Available filters

You have the option of including and excluding files based on the following criteria:

Specific file names or patterns

Specific directory names or patterns

File attributes (hidden, system, etc.)

Files created, modified, or last accessed before, on, or after a specific date or within a date range

Default filter settings - everything is included in the job

If you do not specify any filters for a job, ARCserve will include all files that are on the selected source.


Related Topics

  Directory filter

  How to apply filters

  File Modified/Created/Accessed filters

  File Pattern filter

  Filter basics


How to apply filters

Machine-level filters

Machine-level filters can be created for backup and count jobs.   These filters apply to one specific machine, not the entire job.  (A backup or count job can have machine-level and job-level filters for the same job.)  If you want to add a filter that applies to the whole job, refer to the 'Job-level filters' section below.

Job-level filters

Job-level filters can be created for backup, copy, and restore, jobs, as well as for the utilities, such as count.  Job-level filters are applied to the whole job, not to a specific machine.


Related Topics

  Apply a machine-level filter

  Apply a job-level filter

  Directory filter

  How to apply filters

  File Modified/Created/Accessed filters

  File Pattern filter

  Filter basics


File Pattern filter

Use a File Pattern filter to include or exclude certain files from a job.  You can specify a particular file name or you can use wildcards to specify a file pattern.

The following table describes the recognized file patterns:

Pattern	What it means	Example
DRIVE:\PATH\FILE	An absolute path on your local hard drive.	C:\SYSTEM\*.FOT C:\BAT\AUTOEXEC.BAT
\\MACHINE\PATH\FILE	An absolute path on any network drive.	\\ENG\DOS\SYSTEM.BAT
\PATH\FILE	An absolute path on any network drive.	\WINNT\SYSTEM\*.FOT \BAT\AUTOEXEC.BAT
DRIVE:FILE	The file may be in any directory on the specified network drive.	C:*.FOT C:AUTOEXEC.BAT
FILE	The file may be in any directory on any drive.	*.FOT AUTOEXEC.BAT


Related Topics

  Exclude files with a .BAK extension


Directory filter

The Directory filter allows you to exclude or include files in entire directories.  As with the File Pattern filter, you can enter an entire directory name, or provide a pattern that the directory name follows.  For example, setting a filter to include the \user directory will include all of the files in the \user directory with your job.  If you enter: "use*", all directories that begin with the letters "use" will be included with your job (user, users, userdoc, etc.).

The following table shows you how to specify paths for Microsoft Network machines and NetWare servers:

Pattern	What it means	Example
DRIVE:\PATH	An absolute path on your local hard drive.	C:\WINNT\MSAPPS C:\WIN*
\\MACHINE\PATH	An absolute path on any network drive.	\\ENG\DOS
\PATH	An absolute path on any network drive.	\WINNT\MSAPPS \WIN*
DRIVE:DIR_NAME	The directory may be in any other directory on the specified drive.	C:MSAPPS C:MS*
DIR_NAME	The directory may be in any other directory on any network drive.	MSAPPS *APPS


Related Topics

  Exclude the directory \REPORTS\BACKUP from a job


File Modified/Created/Accessed filters

These filters allow you to filter files based on a threshold date or date range.  Specify a date or date range and whether to include or exclude files that were created, modified, or last accessed before, after, or between the date range.

Filter types

There are three types of filters from which to choose:

Modified - will include or exclude files last modified (changed) on this date.

Created - will include or exclude files created on this date.

Accessed - will include or exclude files last accessed (used but not changed) on this date.

Filter criteria

There are four options from which to choose:

Before - Files whose date matches, or whose date is earlier than, this date will be included or excluded.

After - Files whose date matches, or whose date is later than, this date will be included or excluded.

Between - You must specify two dates for this selection.  Files whose date falls between the two dates will be included or excluded from the job.

Within - Selecting this option requires you to enter a number of days, months, or years to be used for the comparison (for example, within the past 12 months).  Enter a number between 1 and 250, inclusive.  ARCserve will use the current date as the basis from which to count back.

Specifying dates

You can specify a date in two ways:

Enter a specific date.

Double-click in the date field to display a calendar to select a specific date.


Related Topics

  File Modified/Created/Accessed filters


File Size Filter

These filters allow you to filter files based on the file size.

Filter types

There are four types of filters from which to choose:

Equal to - will include or exclude files equal to the specified size.

Greater than - will include or exclude files greater than the specified size.

Less than - will include or exclude files less than the specified size.

Between - will include or exclude files whose size falls between the two file sizes specified.

Filter sizes

There are four types of filter sizes to specify:

Bytes

Kilobytes

Megabytes

Gigabytes


SCHEDULE


Scheduling a job

For basic scheduling information:

About scheduling

Scheduling your job

Specifying a repeat method with custom scheduling

Creating scripts for your jobs

For information about Rotation Schemes:

Using Rotation Schemes

Grandfather-Father-Son (GFS) rotation

GFS media pools

Using the Use Rotation Scheme option

Options with Use Rotation Scheme

Using the Calendar View to customize Your Rotation Scheme

Adding and modifying exceptions

Viewing media pool information using the Media tab


About scheduling

Backup, Restore and Copy jobs can all be scheduled in essentially the same way, using the Schedule options available in the ARCserve Manager.  Backup jobs can also be configured to use Media Rotation schemes, as described in the topic Using Rotation Schemes

Running a job immediately vs. scheduling it for a later time

Run your job immediately when:

The job you are submitting is a "one-shot" job that you want executed immediately.

You want to monitor the job as it runs.

When shouldn't you run a job immediately?

If your storage device is currently busy and you want to run a backup job as soon as the drive is free, you should not select Run Now.  Instead, you should schedule your backup job, keeping the current date and time.  This way, when ARCserve discovers that the storage device is busy, it will automatically retry the backup job until the drive becomes free.

If you select Run Now, ARCserve will report that the storage device is busy and the backup job will not be submitted to the job queue.  Instead, you will be asked to wait until the drive is available before you can resubmit the job.

To run your job immediately:

In the Submit Job dialog box, select Run Now and click OK.

You will be taken to the Job Status Manager so that you can watch the progress of your job.


Related Topics

  Using Rotation Schemes


Scheduling your job

You can schedule your job to run at a specified date and time, and/or to repeat regularly (automatically resubmitted to the job queue).

When should you schedule your job?

Schedule your job when:

You are submitting a "one-shot" job, but you do not want it to run now.  You want it to run at a specific time, such as 12 am.

You are submitting a job that should run regularly.  This is especially useful for setting up a media rotation scheme for your network.

Your storage device is currently busy and you want to run a backup job as soon as the drive is free.  To do this, schedule your backup job with the current date and time.  ARCserve will retry the job until the drive is free.


Backup_Use_Custom_Schedule
Backup Using Custom Schedule

Custom Schedule  Select this option to specify repeat and backup methods for you jobs.

Repeat Method  Once, Every, Day(s) of Week, Week(s) of Month, Day of Month, and Custom.

Repeat Interval  Specify the number of months, days, hours, and /or minutes you want the backup job to repeat.

Exclude Days  Specify the day(s) of the week you do not want the backup job to run.

Full (Keep Archive Bit)  Includes all source files.  The archive bit is not checked or reset.

Full (Clear Archive Bit)  Includes all source files.  The archive bit is not checked, but is reset once the backup is complete.

Incremental  Includes all source files whose archive bits are turned ON.  The archive bit is checked and then reset once the backup is complete.

Differential  Includes all source files whose archive bit is turned ON. The archive bit is checked but is not reset once the backup is complete.


Custom Schedule

Select this option to specify repeat and backup methods for you jobs.


Repeat Method

Includes Once, Every, Day(s) of Week, Week(s) of Month, Day of Month, and Custom.


Repeat Interval

Specify the number of months, days, hours, and /or minutes you want the backup job to repeat.


Exclude Days

Specify the day(s) of the week you do not want the backup job to run.


Full (Keep Archive Bit)

Includes all source files.  The archive bit is not checked or reset.


Full (Clear Archive Bit)

Includes all source files.  The archive bit is not checked, but is reset once the backup is complete.


Incremental

Includes all source files whose archive bits are turned ON.  The archive bit is checked and then reset once the backup is complete.


Differential

Includes all source files whose archive bit is turned ON. The archive bit is checked but is not reset once the backup is complete.


Related Topics

  Specify a Scheduling Option


Specifying a repeat method with custom scheduling

Custom Schedule dialog box presents the following repeat methods:

Repeat Method	Description
Once	Run the job once at the specified time.
Every	Run the job repeatedly at the specified interval.
Day(s) of Week	Run the job on the selected days of the week at the specified time.
Week(s) of Month	Run the job during the specified week or weeks on the specified day of the week.
Day of Month	Run the job once a month on a given (numerical) day of the month.
Custom	Run job at specified interval excluding selected days of the week.


Using Rotation Schemes

ARCserve allows you to configure a rotation scheme for your backup jobs.

For more information:

Grandfather-Father-Son (GFS) rotation

GFS media pools

Using a simple rotation scheme

Using the Use Rotation Scheme option

Options with Use Rotation Scheme

Using the Calendar View to customize Your Rotation Scheme

Adding and modifying exceptions

Viewing media pool information using the Media tab


Backup Schedule Use Rotation Scheme
Backup Schedule Using Rotation Scheme

Use Rotation Scheme:  Select this option to specify simple or GFS rotation.

Scheme Name:  The type of rotation job being submitted.

Start Date:  The date the backup will start.

Exe Time:  The time the backup will start.

Retry Missed Targets:  Enter a specific time that the job will repeat in order to back up any missed target drives.

Backup Method (Full):  Includes all source files.  This method does not change the archive bit.

Backup Method (Incremental):  The archive bit is cleared after every incremental backup job.

Backup Method (Differential):  Only the files that have changed since the last full backup job are backed up.  The archive bit is not cleared.

Enable GFS:  Select to enable GFS rotation.

Append Media:  Allow data from GFS rotation to append to existing jobs on the media.

Media Pool Prefix:  Define a prefix for the media pool’s daily, weekly, and monthly backups.


Use Rotation Scheme

Select this option to specify simple or GFS rotation.


Scheme Name

The type of rotation job being submitted.


Start Date

The date the backup will start.


Exe Time

The time the backup will start.


Retry Missed Targets

Enter a specific time that the job will repeat in order to back up any missed target drives.


Backup Method Full
Backup Method (Full)

Includes all source files.  This method does not change the archive bit.


Backup Method Incremental
Backup Method (Incremental)

The archive bit is cleared after every incremental backup job.


Backup Method Differential
Backup Method (Differential)

Only the files that have changed since the last full backup job are backed up.  The archive bit is not cleared.


Enable GFS

Select to enable GFS rotation.


Append Media

Allow data from GFS rotation to append to existing jobs on the media.


Media Pool Prefix

Define a prefix for the media pool’s daily, weekly, and monthly backups.


Repeat Method

Select a Repeat Method from the drop-down list box.

Repeat Method	Description
Once	Run the job once at the specified time.
Every	Run the job repeatedly at the specified interval.
Day(s) of Week	Run the job on the selected days of the week at the specified time.
Week(s) of Month	Run the job during the specified week or weeks on the specified day of the week.
Day of Month	Run the job once a month on a given (numerical) day of the month.
Custom	Run job at specified interval excluding selected days of the week.


Grandfather-Father-Son (GFS) rotation

ARCserve's Grandfather-Father-Son (GFS) rotation scheme is based on what is standard in the mainframe and minicomputer environments.

ARCserve's GFS offers the following advantages:

Incremental backups

On the Schedule tab of ARCserve's Backup Manager, you can select to use a five or seven-day rotation scheme consisting of incremental or differential backups.  In incremental backup jobs, the archive bit is cleared after every incremental backup job.  Thus, only the files that have changed since the last incremental job are backed up again.  In general, GFS rotation schemes that use incremental backup jobs require less time to perform the daily backup jobs during the week.

Differential backups

In GFS rotation schemes using differential daily backup jobs, only the files that have changed since the last full backup job are backed up.  Since differential backup jobs do not clear a file's archive bit, the files that were backed up in the last differential job are backed up again.  Using this scheme, the backup jobs require more time to process than incremental backup jobs.  However, this strategy requires less effort to restore servers and workstations because you might need less media to restore your network machines.

GFS media naming

When media is assigned to a GFS rotation media pool, ARCserve automatically assigns a name to the media, then labels the media with the backup type, date, and usage.  This media naming convention allows administrators to easily identify backup media.  Media for GFS rotation schemes is automatically named using the following syntax:

(backup type)-(user-defined media pool prefix)-(day-of-the-week)-(date)

Where…	Is…
Backup Type	"F" - full backup "I" - incremental backup "D" - differential backup "W" - weekly backup "M" - monthly backup
User-defined media pool prefix	The name you assigned to the media pool for your GFS Rotation scheme.
Day of the week	An abbreviation for the day of the week on which the job was performed.
Date	The date on which the backup was performed in mm/dd/yy format.
Based on a weekly schedule

The GFS strategy is a method of maintaining backups on a daily, weekly, and monthly basis.  GFS backup schemes are based on a seven-day weekly schedule, beginning any day.  A full backup is performed at least once a week.  All other days, full, partial, or no backups are performed.  The daily backups are the Son.  The last full backup in the week (the weekly backup) is the Father.  The last full backup of the month (the monthly backup) is the Grandfather.

By default, you can re-use daily media after six days.  Weekly media can be overwritten after five weeks have passed since it was last written to.  Monthly media are saved throughout the year.  These can and should be taken off-site for storage.  You can change any of these media rotation defaults to suit your particular environment.

NOTE:  A five-day GFS rotation scheme requires 21 media-per-year, while a seven-day scheme requires 23 media-per-year.

The primary purpose of the GFS scheme is to suggest a minimum standard and consistent interval at which to rotate and retire the media.

Selecting GFS rotation schemes

ARCserve allows you to select from predefined GFS rotation schemes on the Schedule tab of the Backup Manager when you click the Use Rotation Scheme option.


Related Topics

  Customizing GFS rotation schemes


Customizing GFS rotation schemes

Use the following tabs on the bottom of the Schedule tab of the Backup Manager to customize your GFS rotation jobs.

Exceptions - Defining particular days on which the back up type and the execution time or date differs from the pre-existing schemes.  You can also select specific days off.

Rotation Rules - Customizing rotation rules which differ from the predefined GFS Rotation schemes.

Calendar View - Customizing individual days in the GFS Calendar view.

Media - Viewing Media Pool information.


Using the Calendar View to customize your GFS rotation scheme

With GFS rotation either enabled or disabled, you can use the Calendar View feature to customize your rotation scheme according to the types of backups you want for particular days of the week or month.  This feature enables you to specify exceptions to the standard rotation scheme you are using.


Related Topics

  Customize a Rotation Scheme


GFS media pools

The GFS rotation scheme automatically creates three media pools - daily, weekly, and monthly when you schedule a backup using this scheme.  These pools are named according to the Media Pool Prefix you enter in the Schedule dialog box.  Each media pool has its own Scratch Set and Save Set with a default retention period and minimum number of media to save.

The following are the GFS media pools and the formulas used to calculate their retention periods and number of media to save, when the default values are used:

Daily pool:  This pool holds the daily media.  The default retention period is six days and the number of Save Set media is based on the number of daily media in the GFS rotation minus one [# of daily media -1].

For example, if you are using the default GFS setup, where you preserve six daily media, the number of Save Set media in the GFS Daily Media Pool would be five: six daily media minus one.  After six days have passed since the media was used  [on the seventh day], it can be moved from the Save set to the Scratch set.

Weekly pool:  This pool holds the weekly media.  The retention period equals the number of weekly media times seven, minus one [(# of weeklies * 7) - 1] .  The number of save media is based on the number of weekly media in the GFS setup minus one [# of weekly media - 1].

For example, if you are using the default GFS scheme, where you preserve five weekly media, 34 days would be the length of the retention period (5 times 7 minus 1). In the same example, four would be the number of save media in the GFS Media Pool (5 weekly media minus 1).  After 34 days since the media was used (on the 35th day), it can be moved to the Scratch set, provided there are four (4) other media in the save set of the Weekly pool.

Monthly pool:  This pool holds the monthly media.  The retention period equals the number of monthly media times 29 minus five [(# of monthlies * 29) - 5].  The number of save media is based on the number of monthly media in the GFS setup minus one [# of monthly media - 1].

For example, if you are using the default GFS scheme, where you preserve 12 monthly media, 343 days would be the length of the retention period (12 times 29 minus 5). In the same example, 11 would be the number of save media in the GFS Media Pool (12 monthly media minus 1).  After 343 days since a media has been used, it can be moved to the Scratch set, provided there are 11 media in the Save Set of the Monthly pool.

Note:  If you preserve one media each month (12 monthly media), the retention period is 343 days, using the (12 *29)-5 formula, which takes into account months with differing number of days.


Related Topics

  Incremental vs. Differential backups

  Options with Use Rotation Scheme

  Using the Use Rotation Scheme option


Incremental vs. Differential backups

There are basically three backup modes for use with rotation schemes, either custom or GFS:

Full

Incremental

Differential

The first weekly backup will be a full backup.  Subsequent backups (until the next full backup) can either be incremental or differential (but all one mode).

In incremental backup mode, on the first day after the last full backup, only those files that have changed since the last full backup are backed up.  With subsequent incremental backups, only those files that have changed since the previous incremental backup are backed up.

In differential backup mode, every file that has changed since the last full backup is backed up during every differential backup.

Thus incremental backups are, on average, much faster than differential backups because fewer files need to be backed up.  However, restoring data backed up with a rotation scheme using incremental backups is much slower, since data from the last full backup plus data from all the incremental backups must be restored.  Restoring data backed up in differential mode only requires the last full backup plus the last differential backup.


Using the Use Rotation Scheme option

This section describes how to configure a rotation scheme for a backup job by using ARCserve's default GFS scheme or by specifying your own rotation parameters.

The basic configuration of a rotation scheme consists in specifying one of the following parameters for a backup on a given calendar day:

Full backup

Incremental backup

Differential backup

No backup

Full backup is self-explanatory.  A full backup is performed each time the job is repeated.

An incremental backup backs up only those files that have changed (their archive bit has been set) since the last backup was done will be backed up.  After each backup, archive bits are reset so that they are not backed up during the next incremental backup job.

With differential backup, the backup is performed daily after one weekly full backup and the following occurs:

A full backup will be made of the job and all archive bits will be cleared.

The next day, the differential Backup will back up files that have their archive bit set.  (The archive bit will not be reset after the backup.)

The following day, the differential backup will contain all files that have their archive bit set from the previous two days.


Related Topics

  Configure a Rotation Scheme


Using the Calendar View to customize Your Rotation Scheme

With GFS rotation either enabled or disabled, you can the Calendar View feature to customize your rotation scheme according to the types of backups you want for particular days of the week or month.  This feature enables you to specify exceptions to the standard rotation scheme you are using.


Related Topics

  Customize a Rotation Scheme


Options with Use Rotation Scheme

At the bottom of the Use Rotation Scheme dialog are the following four tabs:

Rotation Rules: see Using the Use Rotation Scheme option

Exceptions: see Adding and modifying exceptions

Media: see Viewing media pool information using the Media tab

Calendar View: see Using the Calendar View to customize Your Rotation Scheme

The previous section describes the use of the Rotation Rules and Calendar View tabs.  The following two sections describe the Exceptions and Media tabs.


Adding and modifying exceptions

Click the Exceptions tab.

The box in this tab displays a list of the dates that have exceptions in backup method.  Using the buttons (Add, Modify, Remove) you can perform the following operations on your exceptions.


Related Topics

  Add or Remove an Exception


Viewing media pool information using the Media tab

Media Pool Information

View information about the media pool, including name, serial number, next serial number, etc.

Preserve Media

Click on the Daily, Weekly, or Monthly boxes to change the number of required media per year.


Related Topics

  View Media Pool Information


CREATING SCRIPTS


Creating scripts for your jobs

You can save any type of job as a script.  The script will contain the source, destination, and options that you selected, as well as the schedule information.  It will also contain any filters you created to include and exclude files and directories.

Creating a script has the following advantages:

You can re-use the same settings at a later time.

You can copy your settings to a different network machine running ARCserve.

You can quickly re-submit regularly executed jobs after a job has been accidentally deleted.

To use a script, go to the Job Status Manager and use the Add Job button.  When you specify the job script name, all of the information that you set when you saved the job script will be used, including the files and directories and the scheduling information.


Related Topics

  Create and Use a Script


MANAGING JOBS


Using the Job Status Manager

The Job Status Manager provides an intuitive way to centrally manage ARCserve Servers enterprise-wide.

To learn about Job Manager basics:

Introduction to the Job Status Manager

Accessing and using pop-up menus

To learn about the tasks you can perform with the Job Status Manager:

Managing Servers in the Job Status Manager  - View all available ARCserve servers, job queues and activity logs.

Managing jobs in the queue - add/delete/modify/reschedule job.

Monitor progress of active jobs.

Displaying Job Detail and Job Log

View activity logs


Accessing and using pop-up menus

Pop-up menus can be used to perform various operations with the Job Status Manager.  These pop-up menus appear in both the left (Server Browser) and right (Job Queue) panes.


Related Topics

  Access a Pop-up Menu


Managing Servers in the Job Status Manager

Use the Job Status Manager to manage your jobs enterprise-wide.


Related Topics

  Creating and managing Server Groups

  Adding a server to a server group

  Managing a server in the Job Status Manager

  Viewing Server Properties

  Displaying a job queue for a server


Managing jobs in the queue

All jobs can be managed from the Job Queue window.  The Job Queue window appears in the right pane of the Job Status Manager.

To view the job queue, see Viewing the job queue

The Job Queue allows you to perform the following tasks:

Reviewing information about jobs

Adding a job script to the queue

Changing a job's execution date, time, or status

Displaying information about a job

Modifying a job

Deleting a job

Stopping a job

Changing the way jobs are listed


Reviewing information about jobs

A job listed in the Job Queue with a Done status is a job with no repeat interval that has already been executed.  Done jobs remain listed in the Job Queue for a specified number of hours.  This is set up through ARCserve's Server Admin feature.  A repeating job (a backup job that runs every Friday, for example) will not have a Done status after it has been executed.  Instead, it will have a Ready status (it is ready to be executed again next Friday).

The Last Result Field

The Last Result field tells you whether or not your executed job was successful.  And, if it wasn't successful, the Last Result field helps you figure out why the job may have failed.

What can be done if a job didn't complete successfully

If you determine that your job was not successful, you can use the information provided in the Last Status field to remedy the problem.  You can then resubmit the job to run.


Adding a job script to the queue

You can quickly submit a job to the queue by using a previously saved script.  A script is a job that you saved to a file.  It contains the original source, destination, option, and schedule information for the job.


Related Topics

  Add a Job to the Job Queue


Changing a job's execution date, time, or status

The Job Queue window makes it easy for you to quickly change a job's execution date, time, or status.  This allows you to resubmit a Done job that is in the Job Queue.


Related Topics

  Change Execution Information about a Job


Displaying information about a job

The Job Detail report

The Job Detail report displays the details about a job, including the source and destination target(s) and media statistics, such as sequence and session number.


Related Topics

  Display the Job Detail Report for a Job


Stopping a job

You can use the Stop Job button or the Delete Job button to cancel an active job.  If the job you are stopping is a job that repeats at regular intervals (this is determined when you create the job), you should read the following information to determine which button to use:

Stop Job button:  cancels the active job and reschedules it for its next regular interval.

Delete Job button:  cancels the active job and deletes it completely.  The job will not be rescheduled for its next regular interval.


Related Topics

  Stopping a Job


Modifying a job

Use the Job Queue window to modify a job already in the queue.  This way you can add options or additional sources to an existing job, without having to create a new job.


Related Topics

  Modifying a Job


Deleting a job

You can delete jobs from the queue, if they are held or scheduled.  Deleting jobs from the Job Queue window will completely remove them from the job queue.  This means that repeating jobs will not be rescheduled.

Note:  You can not use the Delete Job button to delete an active job..


Related Topics

  Deleting a Job


Changing the way jobs are listed

When you first open the Job Queue window, the jobs in the queue are listed in order of execution time.  At any time, you can change the way in which jobs are listed in the queue.  Jobs can be sorted by clicking any of the following fields:

Status

Execution Time

Job Type

Server (for Global View)

Last Result

Owner

Total Files

Description

You can resize these columns by using the "drag and drop" method with the mouse.  Place the cursor on the divider between columns, click and hold down the left mouse button, and then move the divider in either direction until the column is the size you want.

Sorting the job queue is for informational purposes only.  It does not affect the order in which jobs are processed.


Related Topics

  Sort the Job Queue


STORAGE DEVICES


Device Manager basics

The Device Manager allows you to view information about your storage devices and to configure and maintain media groups and media.  See the following topics for more information:

About the Device Manager

How to use the device manager

Viewing Device Information

Configuring media groups

Maintaining your media


About the Device Manager

Whenever you want information about storage devices that are connected to your system, the media in these devices, or the status of these devices, use the Device Manager.

Whenever you need to format, erase, or retension media, use the Device Manager.  Also use the Device Manager to change the compression mode for your storage devices, if they support compression.  ARCserve will allow device management commands to be performed during a backup at the point when the job spans media.  The commands you are able to perform at this point are: format, erase, import and export.  This is currently supported on stand alone media devices and tape and optical libraries.

Several media devices = media groups

If you have more than one storage device connected to your network machine, ARCserve lets you separate them into two or more "groups".  Establishing media groups is a key component to ARCserve's flexibility and efficiency.

Media groups allow for:

Parallel streaming: You can have several operations occurring simultaneously, one for each media group configured for your system.

Automated media spanning: If, during a backup session, the media becomes filled, ARCserve automatically spans to another media in another device within the same media group.  Note that this requires two or more devices in the media group for this to happen.

By default, ARCserve is installed with each media device assigned to its own group.  If ARCserve finds identical storage devices during installation, it automatically places them in the same group.  Later, you can use the Device Manager to regroup your devices.  Since you can have up to seven media devices connected to each SCSI bus in your machine, you can have up to seven media groups per SCSI board.

Multiple media groups = parallel streaming

If you have more than one media group configured on your machine, you can take advantage of "parallel streaming".  Parallel streaming means that you can have more than one job requiring a media device running at a time.  For example, suppose you have two media groups, "GROUP1" and "GROUP2", respectively.  You could then have a backup job running with GROUP1, while a restore job runs with GROUP2.

Multiple devices in a group = "automated" media spanning

Media spanning means that, when one media becomes full, the session will automatically span to another media.  If you have a media group that consists of two or more devices, media spanning will occur across devices.  That means, when one media in a group drive becomes full, the job spans to another media in another device within the same media group.

For example, suppose you have two media groups, "GROUP1" and "GROUP2", respectively.  GROUP1 is made up of one storage device and GROUP2 is made up of two storage devices.  If you submitted a backup job that will take up two media, you can insert blank media in each GROUP2 drive and let ARCserve automate the media spanning for you.  If you used GROUP1 for the same backup job, you will need to manually eject the first media and then insert a second media.  As you can see, automated media spanning lets you let ARCserve do most of the work for you.

There is only one rule when assigning media devices to the same group:  the devices in the group must be identical.  That means they must be the same make and model.


Configuring media groups

The Device Manager allows you configure media groups for you backup and restore jobs.

For more information:

About media groups

Creating a new media group

Assigning a storage device to a group

Removing a storage device from a media group

Deleting or renaming a media group


About media groups

ARCserve uses media groups to organize the media used for backing up and restoring files.  Since you can have up to fifteen storage devices connected to a SCSI bus on a board in your machine, ARCserve allows you to separate these storage devices into groups.  Grouping devices allows you to take advantage of parallel streaming.  And, if you have several devices in a group, you can also take advantage of "automated" media spanning.  You may also configure library groups .

One rule for grouping multiple devices in one group

If you want to have several devices in a group, there is only one rule:  each device in the group must be identical (same brand and model).  When you install ARCserve, each storage device that you have is automatically placed in a media group.  Identical drives are grouped together and differing drives are separated into different groups.  For example, if you have five drives attached to your machine, three of which are identical, you will have three groups:  GROUP0, GROUP1, and GROUP2.  The three identical drives will be in one group and the remaining two, since they are different from all others, are each placed in their own individual group.

Since ARCserve automatically groups your storage devices every time the Tape engine starts, you can keep these media group names or you can regroup and rename them.


Related Topics

Use the Device Manager to perform the following tasks:

  Creating a New Media Group

  Assigning a Storage Device to a Group

  Removing a Storage Device from a Media Group

  Deleting or Renaming a Media Group

  Configure Library Groups


Maintaining your media

You can perform the following maintenance tasks on your media:

Formatting Media

Erasing media

Retensioning a tape

Compressing data on media  - This task can only be used if the storage device supports media compression

Ejecting media  from the storage device - This task can only be used if the storage device supports this feature

Note:  Before you use these options, especially the destructive ones (formatting and erasing), make sure you have the right media selected.


Retensioning a tape

Computer tapes are similar to audio tapes in that the more you use them, rewinding and fast forwarding, the more the tape becomes uneven and loose on the spools.  When a tape becomes unevenly wound, it is prone to errors, may jam, or worse yet, break.  Use ARCserve's Retension feature to make sure a tape is evenly wound and properly tensioned.  Retension a tape especially if you are having trouble writing to it or reading from it.

Note:  This option applies only to Quarter Inch Cartridge tapes.  It does not apply to 8mm or 4mm Digital Audio Tapes (DATs).


Related Topics

  Retension a Tape


Compressing data on media

If your storage device supports compression, you can tell ARCserve to use it by turning it on.  Normally, you will want to leave compression on.  The only time you should turn it off is if you plan to use the media in another drive that doesn't support compression.  The drive that doesn't support compression will not be able to read the compressed data on the media.

Note:  You can only change compression when a blank media is in the drive.  This prevents the "mixing" of uncompressed and compressed data between sessions on a media.


Related Topics

  Turn Compression On or Off


MEDIA MANAGEMENT


Media Pooling

ARCserve helps you to create media pools for your media backups.

For information on media pooling, see

Overview of Media Pooling

Creating a media pool

Assigning media to a media pool

Viewing media pools

Modifying media pools


Overview of Media Pooling

A media pool is a collection of media managed as a unit.

Media rotation or grandfather-father-son (GFS) methods of backup are based on media pools.

Each media pool is assigned a name and the media are organized according to serial numbers.  The serial numbers assigned are permanent and if you are using a device with a bar code reader, the bar code labels will be used for the serial number of the media.  The media pools are organized by the range of serial numbers of the media they contain and are divided into two sets, the Save Set and the Scratch Set.

The set of media containing important data that can not be overwritten is called the Save Set.  Once the media has passed several criteria (minimum number of media to save and a retention period) they will be recycled and re-used.

Those media from the Save Set that can be re-used and overwritten because they have met several criteria (minimum number of media to save and retention period) are placed in the Scratch Set.

Each time a media is written to, it moves from the Scratch Set to the Save Set.  That media will move back to the Scratch Set once the specified criteria has been met.

Media pools apply to every media, regardless of which backup type and method were selected.  All Rotation backup jobs will create their own media pool based on the name entered in the Media Pool Name field of the Schedule dialog box for simple rotation, or the prefix entered in the Media Pool Name Prefix field with GFS enabled.  The GFS backup uses three media pools: Daily, Weekly, and Monthly.  These three pools are also based on the information entered in the Media Pool Name Prefix field.  For example, if you enter ACTG as the Media Pool Name Prefix for a GFS backup job, the Daily media pool name would be ACTG_DLY.

For a simple (single media pool) rotation, you specify the complete name for the media pool.

Save Set

The media pool Save Set is a set of media that can not be overwritten.  You can modify Save Set information for all Custom backup jobs. You can move media from the Save Set to the Scratch Set and you can move media from one media pool Save Set to another media pool Save Set. You cannot modify Save Set information for GFS and Rotation backup jobs that have a pre-determined number of media pools and rules.

You define the minimum number of media contained within the Save Set and the retention period.

Scratch Set

The media pool Scratch Set is a set of media which has been recycled from the Save Set after its retention period has passed. All media in the Scratch Set will be overwritten the next time they are used.  Those media that have not been formatted in the longest period of time will be used first.

Retention period

The retention period is the number of days media has not been used before it is moved into the Scratch Set.  For example, if you specify a retention period of 14 days, media will remain in the Save Set as long as it has been used within that specified time.  If the media has not been used for 14 days, it will be moved to the Scratch Set.

Minimum number of saved media

You can specify the minimum number of save media to be retained in the media pool.  This is the number of media that need to be retained in the Save Set before the older media are recycled to the Scratch Set.  This is a safeguard for preventing data loss in case backups are not done for extended periods of time.

Rotation and GFS media pools

Rotation and GFS media pools are based on basic media pooling architecture.  The Rotation backup names its media pool based on what you enter in the Media Pool Name field of the Schedule dialog box in the Backup Manager.

The GFS backup uses three media pools: Daily, Weekly, and Monthly.  Each media pool has a default retention period and number of media to save.

Serial number information

The serial number of a media is one of the factors used in categorizing media pools.  One of the following three ways may be used to create a serial number for media:

Bar Code: A number is read from a bar code label, assigning the serial number.  A changer with a bar code reader is required for this method.  This will override any previously defined media pool settings.

User defined: You enter a serial number when the media is formatted.  This will override any previously defined media pool settings.

Automatic: ARCserve will automatically assign a serial number for the media based on the Base and Range of serial numbers set when the pool was created.

You can not change the serial number of media, however, you can add and modify the following serial number information on the Pool Information screen.

Field	Description
Base	This is the base number that ARCserve will use when automatically assigning serial numbers.  The first media formatted will have the same serial number as the Base number.  Each media's serial number thereafter will be incremented by one.
Range	You can specify the range (up to 31 digits) from which the media pool serial numbers will be categorized. For example, if you specify 200000-299999 as the range for all media in the MKTG media pool, all numbers that fall into the 200000-299999 range will be categorized in the MKTG media pool.
Next Available	This number begins the same as the base number, but is increased by one (1) for each media that is formatted. You do not need to enter any number here ARCserve will automatically increase this number according to the other media pool settings.
Once the serial number is assigned to a media, it will remain constant for the life of the media, even if the media is erased or formatted, unless you explicitly want to destroy the serial number manually.


Creating a media pool

To assign media to a media pool, you first need to create the media pool.  You can create media pools using the ARCserve Media Manager.

Note: The Media menu in the Media Pool Manager window can be invoked as a pop-up menu by selecting a media pool in the left panel and then clicking the right mouse button.

ARCserve itself also creates a media pool or pools (if they do not already exist) when you submit a backup job either with simple or GFS rotation.


Related Topics

  Create a Media Pool


Assigning media to a media pool

You can assign media to a media pool in one of two ways:

Via the Device Manager during the process of formatting the media.

Through the Media Manager, Assign Media option.

Assigning Media to a Media Pool via the Device Manager

When you format media, using the Device Management function, you define certain media pooling information that will be associated with the media.  You can define the following media pool information when formatting media:

Field	Description
New Media Name	If the media inserted in the storage device is named, that name will be displayed.  If the media is blank, you can assign a media name.  If the media is blank, but has an assigned serial number, it can be assigned to any existing media pool.
Expiration Date	You can set an expiration date for the media to be formatted.  When this date arrives, ARCserve will remind you that the media has reached expiration.
Media Pool	You can select any existing media pool previously created using the Media Manager.
Serial Number	The serial number shown here is the current serial number, bar code label, or the next available serial number (based on pre-defined rules).  You can manually enter a different serial number only if that number is not already in use. ARCserve scans the database, and if the serial number already exists (in any of the media pools), an error message is displayed prompting you to enter a new, unique serial number.

To Asssign Media:

1.	Select the set in the Tree or List view and choose Assign Media from the menu, toolbar, context menu, or Properties View.

 A dialog window containing a list of all unassigned media appears.

2.	Select the media you want to assign, then click the Assign button.

To Remove Media:

1.	Select the set in the Tree or List view, then choose Remove Media from the menu, toolbar, context menu, or Properties View.

A dialog window containing a list of all media assignedto a set appears.

2.	Select the media you want to remove, then click the Remove button.


Related Topics

  Managing Media in a Media Pool


Modifying media pools

You can also modify media pool information from the Media Pool Manager window.  Using the Media Pool Manager, you can perform the following tasks:

Delete an existing media pool.

Move media in a pool from Scratch Set to Save Set and vice versa.

View media properties.

Perform location maintenance.

Reconfigure media pool properties.

View the Media Pool and GFS Rotation Profile Reports


Viewing media properties

You can view the following properties for any media in a media pool:

Media name, serial number and Random ID number

Name of media pool to which media belongs

Expiration date of media

Date first formatted

Date last formatted

Date media was sent

Date media was last read


Related Topics

  View Media Properties for a Media in a Media Pool


Performing location maintenance

You can assign or reassign offsite locations to media using the Media Manager.  You can also enter new locations or modify the information about existing locations.


Related Topics

  Perform Location Maintenance


Using a simple rotation scheme

This topic describes how to configure a rotation scheme for a backup job by using ARCserve's default scheme or by specifying your own rotation parameters.

The basic configuration of a rotation scheme consists of specifying one of the following parameters for a backup on a given calendar day:

Full backup: Performed each time the job is repeated.

Incremental backup:  Backs up only those files that have changed (their archive bit has been set) since the last backup was done will be backed up.  After each backup, archive bits are reset so that they are not backed up during the next incremental backup job.

Differential backup: The backup is performed daily after one weekly full backup and the following occurs:

A full backup will be made of the job and all archive bits will be cleared.

The next day, the differential Backup will back up files that have their archive bit set.  (The archive bit will not be reset after the backup.)

The following day, the differential backup will contain all files that have their archive bit set from the previous two days.

No backup


Related Topics

  Configure a Rotation Scheme


Viewing the Media Pool and GFS Rotation Profile Reports

The Media Pool and GFS Rotation Profile Reports can be viewed like any other reports.  For more information on viewing these reports, see the section 'Viewing reports in the Report Manager', in the Online Administrator Guide.


DATABASE


Database basics

The ARCserve Database Manager allows you to display, sort, update, and delete database records in the Database Manager window.

For more information:

About the ARCserve database

How to use the database

Summary View

Viewing Device Information

Job Records

Media Records


About the ARCserve Database

ARCserve stores information about the jobs you have run, the media you have used for backups, and the devices you use for backups.

How is database information used in ARCserve?

Database information helps when you restore files from media.  The ARCserve database stores information about every file and directory that has been backed up.  When you are looking to restore a specific file, ARCserve's database helps you determine which media to use.  This eliminates the time it would take to search through media looking for files.  ARCserve's Reports Manager is another place where database information is used.  Information for the reports comes from the ARCserve database.  The Reports Manager window allows you to view and print reports with this information.

What can you do in the Database Manager window?

You can display, sort, update, and delete database records in the Database Manager window.  For example, you can:

View graphical information about the hard disk on your machine and the amount of space the database takes up

Keep track of the location of your media

Determine the session number of your most recent backup

Delete old records from the database


Related Topics

  How to use the Database


Summary View

The Summary View displays information about the size of your ARCserve database and your configuration settings.  You can view the database information in in graphical form by selecting the Charts option in the lower right pane.  This window is informational only and cannot be modified.

If you are using the standard ARCserve database, this view displays information about your machine's hard disk and the size of your ARCserve database.

If you are using the alternate SQL Server database, this view displays information about the size of the database and amount of space used within the database.

Note:  If your database has grown very large, you may want to set ARCserve to prune old records from the database.


Job Records

The Job Records window displays information about all jobs that have been processed by ARCserve.

Each time ARCserve runs a job, a record is added to the database.  This record contains basic information about the job, such as type of job, who ran it, when it started, when it ended, and its status (finished, incomplete, etc.).

For backup jobs, session and file information is all recorded in the database.

You can view more details about a backup job.  For each backup job, you can see a list of the sessions that were created on media and a list of files backed up for each session.


Related Topics

  View Information about Jobs Processed by ARCserve


Media Records

The Media Records window displays information about the media used with ARCserve.  This includes information about formatting, how much the media has been used since it was put into service, and number of errors (if any) that have occurred while ARCserve was using the media.

Each time a media is formatted by ARCserve, a new record is added to the database.

You can view additional details about a media.  This includes how many errors ARCserve has encountered while reading from or writing to the media, how much data (total) has been written to the media, and number of read and write passes ARCserve has made over the media.  In addition, you can see a list of the sessions that were created on the media and a list of files backed up for each session.

Viewing details about media

You can view additional details about a media.  This includes how many errors ARCserve has encountered while reading from or writing to the media, how much data (total) has been written to the media, and the number of read and write passes ARCserve has made over the media.  In addition, you can see a list of the sessions that were created on the media and a list of files backed up for each session.


Related Topics

  View Media Information about the Media Used with ARCserve

  View Information on Media


Device Records

The Device Records window displays information about the storage devices used with ARCserve.  This includes the type of device, vendor, SCSI ID, head clean count, and usage time.

Error Log tab

You will only see information in the Error Log if the tape drive has a critical error.  An explanation of the fields in the Error Log appears below:

Field	Description
Code	Type of error - hardware or media (see explanation alongside the Statistics tab above).
Time	Time the error occurred.
Sense Info	SCSI error code.
Media	Number of media errors (see explanation above) that occurred during the job.
Soft Write	Number of soft write errors (see explanation above) that occurred during the job.
Soft Read	Number of soft read errors (see explanation above) that occurred during the job.
Media Usage	Amount of time the media was used during the job.
KB written	Amount of data written to the tape during the job.
Times Formatted	Number of times media has been formatted.


Related Topics

  View Information about the Media Devices Used to Backup your Data


REPORTING


Viewing and printing reports

ARCserve provides the following options for displaying logs and reports:

Activity Log - Logs all ARCserve activity.

Tape Log - Logs all media activity (for debugging purposes only)

Job Logs - Logs activity related to a specific job.

Reports Manager - Generates reports from the ARCserve database for viewing or printing.


Viewing the Activity Log

The Activity Log contains comprehensive information about the operations performed by ARCserve.  It provides an audit trail of all ARCserve activity, including every job that is run.

For each job, the log includes the following:

Time the job started and ended

Type of job

Average throughput of the data

Number of directories and files processed (backed up, copied, etc.)

Job session number and Job ID

Result of the job

Errors and warnings that occurred

You can scan this log every day to see if any errors have occurred.  You can also use it to find out a session number in case you need to restore a specific session.


Related Topics

  View the Activity Log


Viewing the Job Log

A Job Log is generated for each job that is run by ARCserve.  You can specify the level of detail in the log by choosing the Log options before you submit the job.


Related Topics

  Configure the Log Report for a Job


Viewing the Tape Log

The Tape Log contains messages sent by the storage devices to ARCserve.  This log is not generated for normal operation.  It is designed for debugging purposes only.


Related Topics

  Generate or View a Tape Log


Types of reports available in the Report Manager

The following types of reports are available in the Report Manager:

Job Report

This report provides a brief listing of all jobs that have been run by ARCserve.  It contains the information that is found in the Database Manager on the Job Records window. For each job, this report lists the following information: Job ID, Job type, Job status, Start time, Submitter, and Description.

Backup Media Erro Report

This report provides information about the media you use with ARCserve.  It contains the information that is found in the Database Manager on the Media Records window.  You must select a media before you can generate this report.  This report includes the following: media name, ID, and sequence number; media type; usage time; creation, format, and expiration date; amount of data written to the media; number of errors; media usage statistics.

Media Session Report

This report provides information about all of the backup sessions that are on media.  (Each source you select to back up is saved on media as an individual session.)  The report contains the session information that is found in the Database Manager on the Job Records or Media Records window when you highlight a record and click the Session tab. When you go to view this report you will be asked if you want the report to include all media or just one that you select.  For each media session, this report includes the following: Session number, Status, Source selected, Start time, End time, Session method, Flags, Total files/KB in the session.

Session Detail Report

This report includes all of the information found in the Media Session Report and also lists every file that was backed up in each session.  The report contains the session information that is found in the Database Manager on the Job Records or Media Records windows when you highlight a record and click the Files tab. When you go to view this report you will be asked to select a media and a session from that media.

Backup Device Report

This report provides information about all of the storage devices you are using with ARCserve.  It contains the information that is found in the Database Manager on the Device Records window.  This report gives you a convenient way of getting a hard copy printout of your Device Records information. When you go to view this report you will be asked to select a storage device.  For each storage device, this report includes the following: vendor, firmware revision, SCSI ID, device type, last head cleaning date, head cleaning count, amount of usage, and errors.

Enterprise Job Status

Provides Enterprise job statistics.  The Enterprise Job Status Report contains information about the jobs that have been run by all the servers within a specific period of time.  The information includes server name, job ID, start time, time elapsed, job status, and submitter, along with session numbers and file statistics for each job.

Media Pool Report

Provides information about the defined media pools.  This information includes Pool Name, date activated, serial number ranges, as well as the media properties of the media contained in the pool.

GFS Rotation Profile Report

Displays GFS rotation information.  The information in this report includes data on the media in the Scratch and Save Sets, media pool name, number of media in each set, media names, backup method for each media (Full, Incremental, or Differential), Status, and location.  This report also contains the Source, Session Number and file statistics for each media.

GFS Prediction Report

Provides the prediction of media scheduled to be used for the selected GFS job.


SERVER ADMIN


Administrating engines from Manager windows

At the top left hand corner of each Manager window, a mini ARCserve Server Admin appears.  This area is provided for two purposes:

Displaying the state of each ARCserve engine - whether it is running, paused, or stopped

Changing the state of the ARCserve engines

Determining engine status

The color of the lights in the mini ARCserve Server Admin indicates the current state of each ARCserve engine:

Green: the engine is running

Red: the engine is stopped

Yellow: the engine is paused


Related Topics

  Change the Current State of an Engine


Starting and stopping the Server

The ARCserve Server consists of three separate engines that together make up the "ARCserve Server".  These engines are:

Database Engine

Job Engine

Tape Engine

Although the ARCserve Server is considered running as long as any one of the engines listed above is running, its functionality is limited.  Therefore, to achieve ARCserve's fullest potential, you should have all three engines running concurrently.

To start or stop the ARCserve Server, you can:

Use ARCserve's Server Admin: this method also allows you to pause and resume the engines.  Refer to the Using the Server Admin to manage the ARCserve Server's status section for details about this method.

Start the ARCserve Manager: the engines start automatically when you start the ARCserve Manager or when you log in.  Refer to Administrating engines from Manager windows

Note:  In addition to these two methods, you also have the following options:

Use Services in the Control Panel.  This method allows you to automatically, as well as manually, start the ARCserve Server as soon as you boot up your machine.  Refer to the Using Services to manage the ARCserve Server's status section for details about this method.

Use the NET START command at the DOS prompt.  Refer to the Starting and stopping the ARCserve Server from the DOS prompt section for details about this method.


Using Services to manage the ARCserve Server's status

Control Panel's Services function allows you to specify which services you want started as soon as you login.  You must manually start services that are not automatically started.

Note:  The ARCserve engines each can also be manually started, stopped, paused, and continued from Control Panel's Services option.


Related Topics

  Use the Services Option to Manage the ARCserve Server's Status


Automatically starting the ARCserve Server

ARCserve engines will be set to start automatically when you boot into your operating system.  This can later be changed in the Services option of the Control Panel.


Related Topics

  Automatically Start the ARCserve Server


AGENTS


About ARCserve Agents

What is a Client Agent?

The ARCserve Client Agents are optional software products that can be used with ARCserve Enterprise edition.  The benefits of using the Client Agent in conjunction with ARCserve are:

Maximize your ARCserve server's capabilities and speed by off-loading the processing of the backup, restore, and compare functionality directly to the machine on which the Client Agent resides.

Compatibility and support for SPX/IPX and TCP/IP protocols.

Support for file system "browsing" of the remote clients.

The Client Agent for NetWare enables ARCserve to back up all NetWare specific information (such as bindery and trustee information).

Client Agents are available for the following operating systems:

Windows NT/2000

Windows 95/98 and Windows 3.1

NetWare

UNIX and Linux

OS/2

Macintosh

Note: For additional information on the Windows Client Agents, please refer to the online Help and Documentation that resides on the machine where the respective Agent is installed.

How do the Client Agents work?

ARCserve allows you the option of performing complete and safe backup, compare, and restore jobs with or without the Client Agents running.  Client Agents provide added functionality when you perform these jobs.  These features include:

Multi-stream processing: One client agent can handle different requests and perform multiple jobs at the same time.

Integrated Authentication: Use existing NT security for remote authentication.

Push Agent technology and efficient backups

All seven Client Agents utilize the Push Agent technology to accomplish backup, restore, and compare jobs.  The advantage of Push Agent technology is that it requires a NetWare server or a Windows for NT machine to perform the necessary filtering of files and directories prior to "pushing" them to the host server (the server running ARCserve) for processing. By utilizing this technology, the transfer of data to the ARCserve host is now minimized thereby reducing load on your communications network. The host server is more efficient because it no longer has to process the files or directories that were flagged for a job. For example:

System Files

An important advantage of the Push Agent technology is that it retains the attributes of system files. This is useful, particularly as it relates to NetWare servers. Because the attributes of the system files are maintained, they are restored as system files rather than as DOS files. This enables you to perform complete disaster recovery.

While a backup done without using the Push Agent technology is as effective and safe, the Push Agent technology allows the restore operation to be completed much more efficiently. Since the system files are backed up intact (native attributes are maintained), they can be restored as is in the event of a disaster, thereby reducing your down time. A restore operation on a server that was backed up without utilizing the Push Agent technology would require that the system files and bindery be rebuilt. In effect, your NetWare server would be restored but it would be generic.


Enabling the Client Agent

Before enabling the Client Agent, you must load it on each machine you will be accessing. Be sure to note the address of the source machine (the machine the Agent is loaded on) when loading the Client Agent.  You must enable the client agent before performing a backup, restore, or copy operation.

There are two methods to enabling the agent.  Both will give you the same results but require different information to be supplied.


Related Topics

  View the Two Methods to Enable the Agent


Using the Client Agent for Windows NT

See the following topics:

Starting and stopping the Client Agent for Windows NT

Configuring the Client Agent for Windows NT

Backing up with the Client Agent for Windows NT


Starting and stopping the Client Agent for Windows NT

The Client Agent starts automatically each time you start your Windows NT machine.  You can also manually start or stop the Client Agent from the Client Agent Admin dialog box.


Related Topics

  Start (or Stop) the Client Agent


Backing up with the Client Agent for Windows NT

In order to back up or restore a machine using ARCserve and the Client Agent for Windows NT, you must:

Make sure that the Client Agent software is properly installed and started on the Windows NT machine.

Choose one of the following methods:

1.	Add the client to the machine tree in the ARCserve Manager Browser.

2.	Select the Use Agent option for the client in the Browser.

Back up or restore the machine following the standard ARCserve backup procedures.

Provide the username and password at the node level.


Related Topics

  Backing up with the Client Agent for Windows NT


Using the Backup Agent for Open Files

If the Backup Agent for Open Files (BAOF) is installed on any of your computers, you can manage the BAOF Engine directly from the Backup Manager.

1.	In the ARCserve Backup Manager, go to the Source tab and select a server from the browser in the left pane.

2.	If this server has the BAOF Engine installed, right-click the computer and select from the following menu items or simply click these items in the Additional Information pane, located in the bottom-right corner of the window:

Configure Open File Agent: This displays the BAOF Configuration screen. From here, you can set various global settings for BAOF on the selected computer.

View Open File Agent Status: This displays the BAOF Status screen. This shows which files and groups BAOF is currently processing on the selected computer.

View Open File Agent Log File: This displays the Log File Viewer screen. This shows the log file for the selected computer.

Note:  Please refer to the Backup Agent for Open Files Administrator Guide for further details.


TROUBLE SHOOTING


Troubleshooting

This section contains what we've identified as some common problems that you might encounter while using ARCserve.  Click on any of the following to see possible solutions:

Trouble writing information to, or reading information from, Media

Experiencing slow backup and restore rates

After installing ARCserve, still have trouble seeing storage device(s)

Having trouble with one of the storage devices

Most of the problems that you might encounter, especially if you are using SCSI host adapters, will be hardware related.  Therefore, the troubleshooting focuses on solving hardware and media problems.

Two important points to consider when tracking down hardware problems:

Make sure your hardware is functional.  This includes the host adapter card, the cables, and the storage device itself.  If you can, test your hardware by connecting it to a system that you know works.

Make sure the hardware is configured properly.  This includes setting the proper switches on the controller card (according to the manufacturer's instructions) and making sure the SCSI bus is terminated properly at both ends.

Check the CDC (Link).

Check for updated SCSI Drivers.


Trouble writing information to, or reading information from, media

Check the following:

Since ARCserve has been installed, has the storage device ever worked?  If you haven't used the storage device, check the hardware configuration.

Check all the board settings on the host adapter card.  Check the firmware of the storage device.  Is this firmware the latest update?  Has Computer Associates certified it?  Check the termination of the bus.  The first and last device on the bus should be terminated.

Clean the storage device heads.  Regular cleaning of storage device heads is required if you want to get the most from your equipment.

Check the brand of media you are using.  Only use manufacturer suggested brand media.


Experiencing slow backup and restore rates

When you restore or backup a remote network machine, ARCserve's performance drops, and the transfer rate is extremely low.

If ARCserve seems to have a very slow restore or backup rate only on some devices, the problem could be due to the number of files on the device.


After installing ARCserve, still have trouble seeing storage device(s)

Make sure that all cards, cables, and devices are connected properly.  Check the following:

If you installed a new card in your system before installing ARCserve, make sure it is seated properly in its slot.  If that doesn't work, try putting the card in a different slot.

Make sure your SCSI bus is terminated properly.  The general rule for terminating devices chained to a SCSI bus is that there must be two sets of terminating resistors, one at the beginning of the chain and one at the end.  If you only have one device connected to your machine, then you have two devices on the SCSI bus; the host adapter card and the storage device.  Both the host adapter card and the storage device should be terminated.

Make sure each SCSI device in the chain has a unique ID number.  If you have two storage devices attached to the SCSI bus, each with the same SCSI ID, chances are neither device will work.  Set each device to a unique SCSI ID.  Check the documentation that came with your hardware for information about changing the ID of the device.

Make sure all the storage devices are turned on.  Sometimes if one device in a chain is off, the others will behave erratically.

Make sure your computer's power supply is up to the task.  The more cards and peripherals you add to your machine, the more demands you place on the power supply.

Make sure the jumper settings on your adapter board are correct.  Check the documentation that came with the board to make sure the jumpers are set correctly for use with your hardware.

Replace the cables you are using with ones you know are good.  If the problem goes away, you know you had a bad cable.


Having trouble with one of the storage devices

If you are having trouble with one particular storage device, remove all other devices from the chain so you are working with just the one device.  Make sure the SCSI chain is terminated properly after you make these hardware changes.

The storage device may not be an available device on the SCSI Bus, one way to rectify this would be to turn the storage device off and on.


Centralized Database


ARCserve Central Database Administrator

You can now use ARCserve's central database to restore data and use tape and session detail for generating ad hoc reports for central database members.  The members, which are subordinate ARCserve machines on your network, update the central ARCserve database with tape session information and details from their own databases.  The central database is set up locally on a network machine used to manage the centralized database, which contains tape session information for all of the ARCserve machines in your enterprise.

You can configure the relationships between the central database and the databases of the domain's other ARCserve machines in ARCserve's Central Database Administrator.  Once you configure your central database, you can view its properties in the Server Properties dialog box by right-clicking on the central database in the browser and selecting Properties.

You can set up a Microsoft SQL database or ARCserve's VLDB database as your central database.  (See the sections detailing installing ARCserve and ARCserve's support for the Microsoft SQL databases.)  Administrators can now use the central database to perform the following functions:

Query for historical information from multiple backup machines from a central location.

Generate ad hoc reports for all of the individual ARCserve databases in your enterprise since all of your data resides in a central location.

Restore machines from a central location in your enterprise.

Note:  If your central database is local to your central ARCserve machine, your central ARCserve machine will have increased performance.


The Central Database Administrator

You can configure the ARCserve central database from the Central Database Administrator:

Click on the Start button and select Programs, ARCserve, Central Database Configuration.

The Central Database Administrator appears.


Related Topics

In the Central Database Administrator, you perform the following tasks:

  Designate your central database

  Add members to your central database

  Configure the job information stored in your central database


Add Members to your Central Database

You can add members to an ARCserve central database to establish an informational relationship between the parent database and the subordinate databases.  The data flows from the dependent ARCserve databases to the ARCserve's central database.

Note:  To view the properties of the central database or the existing members in a central database, double-click on a central database expanding the members, right-click on a member and select Properties.  The Server Properties dialog box appears.

Dependent ARCserve machines only send data to one central database.


Related Topics

  Add Members to your Central Database


Configuring job information for your local database

In the Central Database Administrator, you can configure what job information is stored locally or in the central database.  The following are the different database methods you can configure for the central and subordinate databases:

Method	Central Database	Local Database
1.	Job summary information, including tape session information, is recorded, but no job detail is stored.	No job details are recorded.
2.	All job details are recorded in the central database only.	No job details are recorded.
3.	Job summary information, including tape session information, is recorded, but no job detail is stored.	Summary and detailed job information is recorded on the databases of the subordinate ARCserve machines.
4.	Summary and detailed job information is also recorded in the central ARCserve database.	Summary and detailed job information is recorded on the databases of the subordinate ARCserve machines.


Related Topics

  Configuring Job Information for your Local Database


Central Database Security

When you attempt to assign a remote NT machine as the Central Database or add the machines as contributing members to a central database, you must have administrator rights to the target machine.  You provide the security credentials in the Security dialog box.


Monitoring Job Status for Central Databases

Now you can monitor the job activity for all ARCserve members from the Central Database, including the following:

Job queue for all jobs being run by ARCserve members.

Activity log for all ARCserve members' activity.

Tape log including all ARCserve members' tape session information.


Related Topics

  Monitor Job Status for Central Databases


Backup Wizard

ARCserve's Backup Wizard allows you to submit a backup job of the local machine to ARCserve's job queue without running the ARCserve Manager.


Related Topics

  Backing Up Data on your Network

  Use Backup Wizard


Compressing and Encrypting your backup job

To enhance network security, you can specify a Session/Encryption password for a backup job or a selected drive.  The password will be required in order to restore the data from media.  Select the Encrypt Files Before Backup option to enable this feature.

You MUST remember the Session password in order to restore this session!


Related Topics

  Compress and Encrypt your Backup Job


Restore Wizard

ARCserve's Restore Wizard allows you to submit a restore job to ARCserve's job queue without running the ARCserve Manager.


Related Topics

  Submitting a restore job

  Procedures – Submit a Restore Job


Job Detail / Activity Log tab pop-up menu

If you are viewing information in the Job Detail or Activity Log tab and you click your right mouse button, the following menu appears:

Fonts:  Use to change the font that the log displays.

Print:  Use to print the log.

Find:  Use to search for specific text within the log.

Find Next F3:  Repeat the text search.

Refresh F5:  Update information in the log.


Server pop-up menu

When a server is selected, a menu with the following options appears:

Start all engines - Starts the ARCserve engines it they have been stopped.

Stop all engines - Stops the ARCserve engines.

Delete - Deletes the server from its group.

Properties - A box appears listing the status of the ARCserve engines for this server, build number, version, CD licensing key, options installed, etc.

Security - Allows you to enter the appropriate security in order to connect to the machine.


Pruning your database

You may want to set ARCserve to prune old records from the database.  The Summary View shows how much space on your hard disk is being used by the ARCserve database.  This view is displayed by default when you open the Database window.


Enable Database Pruning

Information regarding the files and directories that were backed up in a session is deleted when database pruning is done.  By default, this option is selected.  It is useful to maintain the detailed information for restoring purposes.  However, not pruning your database can mean that it fills up quickly.  If you want to free up space in the database file, you might want to set this option on.

Prune Database Records Older Than _ Day(s)

This field is active only if the Enable Database Pruning option is on.  By default, the record will be pruned (if enabled) after it has been in the database for 30 days.  To change the length of time, specify a number between one and 365.  This option is operational only on the standard ARCserve database.

Run Database Pruning at _

This field is active only if the Enable Database Pruning option is on.  Specify when you want the pruning operation to run.  By default, pruning (if enabled) will occur at 12:00 AM.


Microsoft Sequel Server Support

You now have two database options when you install ARCserve.  You can use the standard ARCserve database or Microsoft Sequel Server 6.5.

Note:  For the SQL database to function properly, you must start it in Microsoft's SQL Service Manager.

Transferring data from a Raima database to an SQL database

When configuring a Microsoft SQL database for ARCserve, you might want to use an existing SQL database for storing ARCserve tape session, job summary, and detailed job information.

Note:  You cannot restore by tree in the ARCserve using the Microsoft SQL database.

You can use the transfer utility (SQLIN.EXE) located in the ARCserve home directory to transfer this job information from an ARCserve standard database to a Microsoft SQL database.  However, any information existing in the database is overwritten.

Note:  You should not attempt to transfer information from a Raima database to an SQL database containing information because the SQL database might be overwritten.  Instead, you should create a new SQL database for storing your ARCserve tape and job information.


RAID


What is a RAID?

RAID (Redundant Array of Inexpensive Devices) enables you to set up a system using multiple drives to process (back up, restore, etc.) data.  The concept of RAID was originally used with an array of hard disks.  Data is written across all the drives (or disks) used in the array in a predefined order.

With RAID, you can use an array to process jobs (back up, restore, etc.). The drive array you set up will appear (on all informational screens) as a single drive.  Internally, the multiple drives are accessed in parallel.

Notes for the ARCserve Enterprise Edition:

RAID applies only to an array of tape drives (not hard disks).

RAID supports tape libraries.

Devices in RAID must be identical.


Major features of the ARCserve RAID Option

The most important benefit of RAID (in both RAID 1 mirroring and RAID5 mode) is fault tolerance.  During a restore, if one of the tapes becomes unusable, you can still restore from the remaining tape(s).

RAID offers two main types of fault tolerance modes from which you can select:

RAID 1 Mirroring (uses an array of two devices)

RAID5 or striped parity RAID (uses an array of three or more drives)

RAID5 Fault Tolerant StripingParity Generation	RAID5 (striped parity) mode involves data striping.  This improves reliability so that in case of failure of one drive, the parity (error correction) can be used to generate the lost data.  Performance is improved because data is striped across three or more drives and parity (error correction information) is generated and stored. RAID5 increases the "virtual" capacity of your tape (with RAID, three drives appear as one "virtual" drive).  For example, if your tape's capacity is two gigabytes, normally you would need two tapes (spanning) to back up four gigabytes.  However, with RAID5 you can store the same four gigabytes on one "virtual" tape (no spanning).  If you are using three drives with RAID5 your storage capacity will double.  If you are using five drives with RAID5 your "perceived" storage capacity will quadruple.
RAID0  Striping (Not fault tolerant)	Data striping transparently distributes data over multiple drives to make them appear as a single, high-performance drive.  Data striping improves throughput performance by allowing data to be processed in a parallel manner.  Striping creates high throughput, but does not provide fault tolerance.   RAID Level 0 is an ideal solution when you require optimum throughput rather than fault tolerance.
RAID Level 1 Fault Tolerance Tape Mirroring	Level 1 provides fault tolerance and tape mirroring.  The mirroring mode maintains both tape drives as exact duplicates. Tape mirroring ensures that the data will continue to be delivered to a drive even if the other drive fails.  This RAID level is preferred if you want to maintain a tape at one site while sending the mirrored tape to a different location.  You can transport your data easily without performing a tape copy operation. Tip:  We recommend that when using mirroring, you maintain one tape copy offsite for safekeeping for full restoration, even if a tape is lost or damaged.


RAID configuration levels

RAID works "behind the scenes" and makes the multiple drives you set up in your array appear as one "virtual" drive.  In this way, RAID provides several data management advantages.  RAID works with your backup and restore jobs to ensure fault tolerance and increase throughput.

The following section describes and compares the various modes used by RAID:

Mirroring RAID 1	Mirroring provides fault tolerance and reliability.   In mirroring mode the operations of the drives are duplicated.  Whenever data is written to one drive, the same data is also written to the redundant drive, so there are always two copies of the data. This redundant drive ensures that the backup can be completed, even if a drive or media fails.  In case of drive failure, the backup or restore continues with the remaining drive.   The tape sets used in mirroring are compatible with ARCserve (in non-RAID mode) functions.  You can use ARCserve (non-RAID mode) to restore data from any of the RAID tapes, but it is not recommended to back up to any of the RAID tapes with ARCserve (in non-RAID mode). NOTE:  A session cannot be appended to a RAID-1 tape in a standalone drive.
Data Striping RAID 0	Data striping transparently distributes data over multiple drives to make them appear as a single, high-performance drive.  Data striping improves throughput performance by allowing data to be processed in a parallel manner.  Although you have high performance with data striping, you do not have fault tolerance.
Parity RAID 5	Parity is an error-detection method that is used to detect and correct errors in data transmissions.   Parity is used to perform specific checks of the data blocks within a stripe.  In the event of a single failure, the information for the missing drive or tape can be re-created by examining the remaining data and parity and regenerating the missing data bits. With a RAID array using three or more drives, data and parity are striped across all the drives. Think of parity as part of an equation.  Let's say, for example you are using RAID with three drives.  Data is processed on two drives while the third drive holds the parity.  If one of the media is lost, parity ensures that the missing data can be re-created.


System requirements for ARCserve RAID

To install and use the ARCserve RAID Option, the following hardware and software is required:

System Element	Requirement
Processor Type and RAM:	Pentium machine with 32 MB of RAM (64 MB is recommended).
Disk space:	4 MB of free disk space.
Operating System and Software:	Microsoft Windows NT or 4.0/2000. ARCserve 7.0 for Windows NT/2000.
Tape Drives and Tape Libraries	All devices should be of the same make and model.
SCSI Adapter	No more than two drives per board are recommended.


Installing the ARCserve Option

The ARCserve RAID Option Setup program carries out the following functions:

Copies the necessary files to your local network machine

Allows you to create, modify, and delete RAID

The first time you run Setup, it copies files to your network machine and adds the Setup icon to your ARCserve program group. Subsequently, you can run Setup from this icon to reconfigure your RAID group(s).

Note:  You must have ARCserve installed and running on your computer before you can install a RAID Option.


Related Topics

  Install the ARCserve Raid Option


Adding, deleting, and modifying RAIDs

You can add, delete, or modify a RAID at any time from the ARCserve Device Configuration program.


Related Topics

  Adding, Deleting, and Modifying RAIDs


Set RAID Compatibility

RAID tapes generated by different RAID configurations are fully compatible.  That is, you can add additional drives to an existing RAID without losing the data that has already been backed up by the RAID.

For example, suppose you create a three-drive RAID device and back up data to this RAID.  You can now add an additional drive to the RAID.  Backups made after the new drive has been added will take advantage of the additional drive.  For a new tape set of four tapes, the data is now distributed across four drives.  However, you can still restore data previously backed up with the three-drive RAID by inserting the set of three tapes into any three of the four RAID drives.  You can also still use the set of three tapes for backups in the four-drive RAID.

NOTE:  RAID Level 1 tapes can be read in a non-RAID tape drive but not written to.  RAID Level 1 tapes cannot be used in a RAID Level 0 or RAID Level 5 . RAID Level 0 and RAID Level 5 tapes are compatible.


Uninstalling RAID Option

Select the RAID Option from Add/Remove Programs Properties in the Control Panel.


Assigning a RAID device to a RAID Group

Before you can back up data to a RAID device, the RAID device must be added to a group in the ARCserve Device Manager.  When running the job, ARCserve will automatically assign a RAID device to a group, if it is not already assigned.  You can also manually assign a RAID device to a RAID group.


Related Topics

  Manually Assign a RAID Device to a RAID Group


Backing up and restoring with RAID

RAID's fault tolerance allows you to continue your backup or restore even if the media goes bad or if one drive fails.  Using this feature improves backup and restore performance by distributing data over multiple drives.

IMPORTANT:  RAID is available as an option with ARCserve.

Backing up data using RAID ensures fault tolerance and increases the throughput of your backup job. RAID is displayed in ARCserve as a virtual drive, and the special processing of the RAID backup is transparent.

Using RAID is very similar to regular ARCserve operation.  The main difference is that you are now dealing with a RAID tape set as a unit, instead of, for example, a single tape drive.

With a RAID device assigned to a RAID group, you can proceed to perform backup and restore operations using that RAID device just as you would in regular operation.

The main difference between the types of groups is:

Device management operations (such as format, erase, eject, change compression) affect all the tapes in a RAID group and in a Tape Library RAID group.

Restoring Data from a RAID

To restore data from a RAID device, select the RAID grouping as the source in the Restore window. Follow the standard restore procedures.


Parity Checking

Parity checking enables RAID Level 5 ARCserve to recreate lost data if one of the drives fails.  With parity checking, when data is written to an array of drives, an extra data element, called parity, is added to the stored data.

The parity check uses Boolean logic to recreate lost data.  For example, say you are using a RAID consisting of three drives.  When you do a backup, for every two elements of ordinary data, the third element, parity, is added.  If the drive containing the second data element is damaged, data from the lost drive can be recreated using the parity data element and the data elements from the remaining two drives by applying Boolean logic.


Maximizing RAID performance

ARCserve RAID offers significant performance benefits to your backup system by providing fault tolerance.  You can monitor your system performance using the Windows NT Performance Monitor.

In order to maximize your performance, make sure of the following:

Your data bus can handle the increased data flow.

Your hard disk can support the increased data flow.

If you are not getting the performance benefits that you expect, check your system hardware.  You may have to reconfigure or purchase new hardware in order to take maximum advantage of the RAID capabilities.  Make sure that your hardware and software requirements match those recommended by Computer Associates.

Use PCI/VLB or EISA adapters (for example, Adaptec AHA-2940).

Connect your tape drives to dedicated controllers.

When using high performance drives, you may need to limit the number of drives per adapter.

Use proper media type (DLT IV vs. DLT III, DDS3 vs. DDS)

Make sure that your drives are identical

For some types of drives, connecting more than one drive to the same board can significantly reduce performance.

There are other factors that could affect performance:

The hard disk could be the bottleneck.  Make sure you have a hard disk that is fast enough to feed data to the RAID.

One of the tape drives is slow due to bad media, etc.

If another application accesses the same hard disk during backup, the performance will not be optimized because of hardware limitations.

The performance of a RAID device will depend on the speed of the slowest drive attached. For example, in a 3-drive Level 0 RAID where drive 1=100 MB/min., drive 2=120 MB/min., and drive 3=120 MB/min., the total throughput will be 300 MB/min. Keep this information in mind when coordinating drives for RAID.

By increasing the buffer size, the performance of a backup or restore job can be improved.  The optimum buffer size to set depends on a number of factors:

the hardware being used i.e. the tape drive, the hard disk and the amount of memory in the system

the number of jobs that are running at that instance

You can modify the buffer size in the Properties window of Device Configuration.  If Default is specified, ARCserve will calculate an optimum value and use it.  If Custom is specified, you can specify the buffer size.  You can find out the best buffer size for you environment by trying a few of values.  To determine the amount of memory you want to be used by one job, you should divide the total memory specified by the number of jobs that you will run simultaneously.


catalog file

A directory of disk files or files used in an application.  Also any map, list or directory of storage space used by the computer.


Appending Media

In addition to the backup options, you can apply options to the destination (media) you have selected.  You have the option of overwriting existing jobs or appending to the existing jobs on the media.  Appending data to media will place the new backup job after any previous backup jobs, leaving the previous backup jobs untouched.

You append data to media currently in the scratch set of your GFS media pools.

To append data to existing media, click Enable GFS on the Quick Access Panel.

There are three exceptions to appending media:

In the beginning of the week, a blank backup media is used.

Any full backup job uses blank media.

Any job after a full backup uses blank media.


Configuring SANO - Storage Area Network Option

The Storage Area Network Configuration is a utility for configuring the relationships between the Primary and Distributed ARCserve servers.  Once all the servers have the SANO installed, you can go to any server to run the Storage Area Network Configuration.


Related Topics

  Configure the Storage Area Network Option


Image Option Help


Basic Concepts

The Image Option is a separately-sold product that works with ARCserve to greatly enhance the speed with which you can back up your local Windows NT/2000 machine. The following sections describe how the image backup works, the features, and troubleshooting tips.


High-Speed Image-Based Backup

The Image Option accomplishes high speed backups by bypassing the file system, creating an "image" of the volume and achieves high speeds by asynchronously reading data blocks from the disk, as if the entire drive were a single large file.  This method replaces the traditional, and slower method, of traversing an entire file system file-by-file.

Although you can only back up a complete volume, you have a choice of restoring an entire volume, directories or individual files.


Snapshot Capability

Snapshot Capability allows you to run a backup operation by taking a snapshot of the partition at a specific point in time, the hard drive appears "frozen-in-time"-- a snapshot of an image; whereas, for other applications, it appears "normal".  This permits other applications to continue sending read/write requests to the partition.  (The Snapshot filter driver, the Hot Backup Manager, is automatically installed when you run the setup program.)

When a backup begins, an "image" or snapshot is taken of the drive.  Any data written during the real-time of the Image backup operation is filtered and stored in a preview.dat file.  The data integrity is not compromised.  The data in the preview.dat file is copied back to the proper place after the Image backup operation is complete.

Snapshot Capability means:

If applications write to the drive while a backup is in progress, the integrity of the backup is maintained.

At the start of the backup process the Image Option will not attempt to lock the drive about to be backed up.

The backup will continue and be successful even when files are being written to during the backup process.


Related Topics

  Features and Functions


Features and Functions

Along with Snapshot Capability, Image Option includes:

Optimized file scanning.

Device independence--writes to any device ARCserve supports, including tape devices, tape/optical libraries, optical devices, and tape RAID devices.

Restores individual files as well as full volumes.

Backs up both NTFS and FAT file systems.

Backs up NTFS compressed files, directories, and drives.

Maintains all file attributes and security information of your Windows NT/2000 environment.

Backs up only occupied volume space.

The following table displays ARCserve features that are not available when using Image Option.

During Backup
Methods	Keep Archive Bit, Clear Archive Bit, Incremental, and Differential.
Retry	Open File Retry and File Sharing
Verification	Scan Backup Media Contents and Compare Backup Media to Disk.
Operation	Delete Files After Backup, Disable File Estimate, Calculate and Store CRC Value on Backup Media, and Backup ARCserve Database files.
Virus	Enable Virus Scanning and Skip, Rename, and Delete.
During Restore
Destination	Directory Structure and File Conflict Resolution.
Operation	Restore Registry Files and Create Empty Directories.
Virus	Enable Virus Scanning and Rename and Delete.


Using the Image Wizard

Image Wizard is used to simplify your backups.  The Backup Wizard is activated when you install the Image Option.  Use the Image Wizard to enable the Image Option for your backups.


Related Topics

  Use the Image Wizard


Backing Up Source Drives

There are two ways to back up with the Image Option, using either the Wizard or the ARCserve Backup Manager (by selecting the source and right-clicking the mouse).  This section describes backing up with the ARCserve Backup Manager.  For further information on how to use the Backup Wizard, please refer to the Online ARCserve Procedures.

Note:  You can only perform an Image backup on a computer where ARCserve and the Image Option are installed.


Related Topics

  Use the ARCserve Manager


Restoring Data

The following two methods can be used to restore data backed up using the Image Option:

Restore by Image: Restore the entire volume in one pass

Note:  The Image Restore must be completed from beginning to end in order to be successful.  Canceling an Image Restore in Image mode, will leave the partition in an inconsistent stage, and will make it inaccessible.

Restore by File: Restore individual files and directories.

Note:  Canceling an Image Restore in File mode, can leave many incompletely restored files on the partition.

Important:  Using the Restore by Image option will completely overwrite your volume.  Be sure that this is exactly what you want to do.  Make sure you do not have valuable data and system-specific configuration files such as the Windows NT Registry on the volume that you need before you begin the restore operation.

Note:  During an image restore the volume cannot have any open files. The Image Option will attempt to lock the drive before the restore process begins, and if any files are open, the drive lock will fail and the restore job will also fail.


Related Topics

  Restore a Volume with Restore by Image or Restoring Individual Files


Troubleshooting Tips

General suggestions for running successful image backups/restores.

Keep some empty space on the volume where ARCserve is installed.  Since ARCserve creates temporary files to enhance performance and logs, it needs space in this drive.  Ideally, 70-100 MB free space should be sufficient.

To accommodate the Snapshot Capability feature, Image creates a temporary storage file on a local drive that has the most free space available.  In addition to the 70-100 MB free space suggested above, you must have at least 20 MB free for the Snapshot Capability feature.

While restoring the active system drive, you must have at least 50 MB available on the drive.  This amount of space will be needed to store additional temp files and Registry files when you back up and restore.

If there is activity on the volume, then it may not be able to freeze the volume.  The following will occur if the volume cannot be frozen during the backup:

If the volume does not freeze, it will try to lock the volume for exclusive access.

If the volume is not locked, and you change any data, there is the possibility of data getting backed up that is inconsistent and unusable.

The volume can not be locked, if:

File Manager has this volume expanded

DOS box is opened with this drive letter

Any application opens a file on the volume

To provide information about any problems and supply descriptions about recent or ongoing operations, do the following to check on the status of a job:

Click on the Activity Log tab under ARCserve Manager's Job Status.  It has time stamped events about the operations and any errors descriptions.  Error incidents will have the prefix E with a number following it.  For example:   E11018.


Disaster Recovery


What Is Disaster Recovery?

When a mission-critical server goes down, only one thing matters: time.  Each tick of the clock means business lost, opportunities squandered, efforts wasted.  You need to get your system back on line quickly, accurately, and safely.  That's been a tough proposition: until now.  By simply booting from the start-up diskettes with bootable CD and following a simple Wizard interface, even a novice user can have a server back on line in record time.

The Disaster Recovery Option for Windows NT lets you conquer time.  Using a boot-strap recovery process, Disaster Recovery takes you from disk, to tape, to up-and-running, faster than any solution – ever.

Engineered to bypass all the slow curves, Disaster Recovery navigates the critical bends in the road that let time slip away.


Disaster Recovery Wizard

The Disaster Recovery Wizard restores the partition to the original configuration.  However you can do the following only in Windows NT 4.0

:

Retain your current partitions.

Modify the size and/or drive letters of your current partitions.

Create new partitions.

Create volume sets, stripe sets and stripe sets with parity.

Use any combination of the above.

Note:  MTF Information!  If you are using an MTF tape, the Disaster Recovery option cannot distinguish between full and partial backups. Therefore, you must know which sessions are full sessions, and select a full session for restore.


Functionality

Disaster Recovery is a flexible, easy-to-use, enterprise-wide solution. The following section describes some of the advantages of using its features.

Flexible	You can create recovery boot disks locally and remotely. You can recover any machines using the storage devices attached to your ARCserve server (remote Disater Recovery for Windows NT 4.0 only). Supports full RAID and tape/optical library restore procedures. Supports multiple session tapes and spanned tapes. Supports MTF (Microsoft Tape Format) tapes. Supports backup through the Windows NT Client Agent.
Enterprise-wide	Supports multiple tape drives and multiple host adapters. Supports use of tape drives in autochangers.  Supports Storage Area Network Option (Windows NT 4.0).
Easy To Use	There are no special backup procedures to learn. Disaster Recovery works with regular tape backups. Wizards help to create recovery boot diskettes, to partition and format hard drives, to scan sessions, and begin restores.
Remote Disaster Recovery	Allows you to use the storage devices attached to your ARCserve server when you are recovering any machine on your network.  You do not need to carry tape drives or changers to a machine where you want to recover data (Windows NT 4.0).


Related Topics

  Restrictions on Usage


Restrictions on Usage

Disaster Recovery is subject to the following restrictions:

Disaster Recovery can only restore a full session.  Individual files cannot be restored through Disaster Recovery.

Disaster Recovery supports only NTFS and FAT partitions and FAT 32 (for W2K).

Please consult the Disaster Recovery Release Notes for ARCserve to obtain the most current updates on product limitations.


Pre-Installation Notes

Requirements for installing Disaster Recovery are as follows:

ARCserve

Windows NT 3.51 or above.

Note:  (Compaq SmartStart users need SmartStart version 3.0.)

The Disaster Recovery Setup adds icons for the Create Boot Disk utility, Release Notes and Uninstall program.  In addition, Setup gives you a chance to run the Create Boot Disk utility at the end of installation.


Using the Windows NT Client Agent with Disaster Recovery

Disaster Recovery allows you to automatically retrieve information for each workstation on the network using the Client Agent.  When a machine is backed up using the NT Agent, the information needed for disaster recovery is retrieved, such as hard disk partition information, network card information, and NT Registry information.  Disaster Recovery uses this information to create the fifth boot disk of the Disaster Recovery boot kit.  With this information, the original configuration of the hard disk and partitions can be restored exactly as it was before the disaster occurred.  This information is also used to connect to the network for remote disaster recovery (for Windows NT 4.0).

Refer to your Client Agent for Windows NT User Guide for detailed information on how to install the Client Agent.


Related Topics

  The Disaster Recovery Boot Disks


The Disaster Recovery Boot Disks

You must create boot disks to protect your machine from any future potential hazards.  You can create them at any time, even after the workstation has crashed.  The only pre-requisite is that the machine must have been backed up by an ARCserve server.

The Disaster Recovery boot disks are a modified set of Windows NT/2000 setup software.  Disaster Recovery modifies the three NT or four for W2K setup disks and creates a fourth and sometimes fifth disk of its own. These four or five disks let you start up any server, even one with an unformatted hard drive, and fully restore the system using an ARCserve backup tape or MTF tape.

With ARCserve, a Disaster Recovery directory is automatically created within the ARCserve home directory, after you perform your backups (local backups or backups through the Windows NT Client Agent).  The Disaster Recovery directory will be used to contain a server's or workstation's specific data (such as configuration information and system-dependent files).  The data stored here will be used to create your machine's boot disk.

Tip:  Remember to inform everyone (including overnight or weekend personnel) who may need to access the Disaster Recovery disks about their location.

For Windows 2000 you can use the CD boot function to boot a machine that has crashed.  You only need to create the 5th floppy (machine specific DR floppy).


Creating the DR Boot Diskettes
Creating the Disaster Recovery Boot Diskettes

Important!  Before you proceed, you must have:

Four or five blank, formatted high-density disks, depending on which DR boot disk method you choose.  Label the disks as follows:

ARCserve Disaster Recovery Disk

Windows NT Setup Boot Disk (see following section)

Windows NT Setup Disk 2 (see following section)

Windows NT Setup Disk 3 (see following section)

ARCserve Network DR Disk


Related Topics

  Make Copies of the Windows NT Setup Disks


What You Need to Recover From a Disaster

To recover from a disaster, you will need all the items on the following checklist:

A set of Disaster Recovery boot disks (created on any NT server) or the bootable CD and number five disk.

A Windows NT CD (v 3.51 or higher in your CD drive) that matches the version used to create the boot disks.

A backup device connected to the server (can be a remote ARCserve server) for Windows NT 4.0 only with an ARCserve backup tape or MTF tape containing the data you want to restore in the drive. The tape must contain at least one full backup session.


Related Topics

  Recover from a Disaster


Express vs. Custom Setup
Express vs. Custom Setup for Windows NT 4.0

Express Setup is the fastest way to recover your system. Express Setup will automatically detect your system drivers and partition information.

Custom Setup allows you to specify particular drivers for the devices controlled by your server.  Custom may be required if your system uses drivers not included in the NT Setup program (such as OEM drivers).

Custom Setup also allows you to re-partition your hard disk(s) and/or change the file system being used (NTFS or FAT).


Important Partition Information

If a backup session is larger (in MB) than a partition, you can assign that session to the partition, but the recovery may not be complete.

For Image backup sessions, if the size of the session is smaller than the partition, the partition can be truncated to the size of the session, and an additional area of free space will be created.  This free space will be added to any existing free space, and can be re-formatted into an empty partition.  Alternately, you can restore the session as is, and any remaining space will become empty disk space on the new partition.


Start the recovery Process

After making all necessary partition selections and modifications, click Next.

The Wizard is now ready to begin recovery for each partition to which you assigned a backup session.  If you are restoring to the active partition, you will be prompted to insert the Windows NT CD in the CD-ROM drive at this time (for Windows NT 4.0).

To start the recovery process, click Start Disaster Recovery.

The Disaster Recovery Wizard copies the data from the specified session(s) to the specified partition(s).

Note:  You can stop the recovery by clicking Abort and then Cancel. However, we strongly recommend you complete the recovery, otherwise the results are unpredictable.  Also, in some circumstances you may be asked to reboot the server at this point.  The recovery process will then pick up where it left off when the machine restarts.

A progress bar will show the progress of the restore process.  Upon completion of the restore, your machine will reboot and return to the exact condition it was in at the time the backup tape was created.

A directory named DRBOOT.TMP is created during the restore process.  After successfully restoring, this directory may be deleted.


Volume Sets and Stripe Sets

Windows NT allows for the creation of volume sets and stripe sets.

Volume set	A volume set is created by combining space on a physical drive or drives into a logical volume.  The logical volume is treated like a single partition: that is, it appears as one drive letter.
Stripe set	A stripe set is similar to a volume set, but each partition is of a similar size to allow data to be written in stripes across each partition.  Stripe sets require at least two physical drives.
For further details on volume sets and stripe sets, please see the Windows NT documentation.


Related Topics

  Restoring to Volume Sets and Stripe Sets


Restoring to volume sets and stripe sets

Follow the restore instructions in Recovering from a disaster before proceeding.

To create a volume set or stripe set, you must have free space available.  To continue with restore procedures, click here


Special Considerations for Database Restores

Computer Associate's ARCserve product has special options available to backup databases, such as Oracle, Microsoft SQL, Exchange, and Lotus Notes.

If you have backed up one or more of these databases using ARCserve, it cannot be restored using the Disaster Recovery product.

When ARCserve backs up a database, a special tape session is created, apart from the rest of the backup.  This database session is not a full backup, and therefore cannot be seen in the Disaster Recovery session list.

However, after restoring the rest of the server using the Disaster Recovery option, it is a simple process to start ARCserve and begin a normal database recovery procedure.


To install Disaster Recovery

The setup program for Disaster Recovery Option guides you through the installation procedure.  For full procedures, click here

Note:  The Disaster Recovery Release Notes contain important information related to certain situation-specific cases.  Please read the Release Notes fully before using the Disaster Recovery option.


Creating the Disaster Recovery boot diskettes

The Disaster Recovery Wizard will create a set of Disaster Recovery disks that you can use to recover your machine in the event of a disaster.  Please remember to use the DR Wizard to update your disks whenever you make a modification to your machine's operating environment, such as changing your network card.

Reminder Note:  It is essential that you create and update your DR disks for your ARCserve local machine on a regular basis.

We recommend that you read Recovering From a Disaster thoroughly.  This topic contains important information and procedures required to recover your data.  If you review this material and have a practice Disaster Recovery session, you will be well prepared for any circumstances, should a real life disaster occur.


Related Topics

  Create Disaster Recovery Boot Diskettes


To restore your server

Tip:  If you are using Express Setup and your system cannot locate your CD-ROM drive, start the recovery process again using Custom Setup.


Related Topics

  Restore your Server

  For Local Recovery Only

  For Remote Recovery Only


For Local Recovery Only

The Disaster Recovery Wizard scans the local machine for any backup devices connected to your computer and reports drive and media information.


Related Topics

  Local Recovery Procedures

  Local and Remote Delivery

  Restoring to volume sets and stripe sets


For Remote Recovery Only

IMPORTANT:   The ARCserve Tape Engine must be started on the remote machine before you attempt to establish a connection.


Related Topics

  Remote Recovery Procedures

  Local and Remote Delivery

  Restoring to volume sets and stripe sets


Local and Remote Delivery

If you are not sure which tape contains the last full backup, the DRIF file will indicate the tape ID and allow you to locate the correct tape quickly.

Note:  Disk space is displayed in three forms:

Formatted partitions.

Unformatted partitions - space that is partitioned but not formatted.  They are formatted when a session is assigned to them.

Free space - disk space that is not formatted and not partitioned. Free space is created when a partition is deleted.  To assign a drive letter to free space, you must first partition it.


Related Topics

  Local and Remote Delivery Procedures

  Disaster Recovery Wizard

  Restore using the existing partition information as is

  Restore using new partitions or modified partitions

  Restore to unformatted space using it as is


To restore using the existing partition information as is

  Procedures

  View Important Partition Information

  Restore using new partitions or modified partitions

  Restore to unformatted space using it as is

  Start the recovery Process


To restore using new partitions or modified partitions:

  Procedures

  To restore using the existing partition information as is

  To restore to unformatted space using it as is

  Start the recovery Process


To restore to unformatted space using it as is:

Note:  The unformatted space you wish to restore to will automatically be formatted as part of the restore process.


Related Topics

  Procedures

  Start the recovery Process

  To restore using the existing partition information as is

  To restore using new partitions or modified partitions


Setting Up Disaster Recovery on a NetPC

This version of Disaster Recovery supports NetPC's and protects them.  It takes advantage of the fact that a NetPC can boot up remotely, to eliminate the need of diskettes and CD-ROM for performing a Disaster Recovery.

The first step to enable this process is to have Unicenter TNG installed and running.  To accomplish Disaster Recovery on a NetPC, the ManagedPC feature of TNG needs to be installed.

ARCserve backs up and restores a NetPC machine, and can perform a smooth, remote Disaster Recovery.

In order for Disaster Recovery to optimize performance, we recommend that you use two servers:

A Windows NT 4.0 Server running ARCserve

A Unicenter TNG Server with ManagedPC Option installed

Pre-requisites	ARCserve or above must be installed and running. The NetPC machine prepared for disaster recovery should have a full backup performed by the ARCserve server.  Additionally, if any hardware configuration is changed, a full backup by ARCserve is required. Unicenter TNG Framework 2.2 or above or TNG 2.2 and above must be installed, set up, and configured by the system administrator.  Please refer to the Unicenter TNG Framework ManagedPC OEM Kit for a complete walk through of the wizards and utilities system used to complete the installation, setup, and configuration processes.
System Requirements	Unicenter TNG FW 2.2 or TNG 2.2 Windows NT 4.0 or above on the NetPC ARCserve or above


Related Topics

  Install Disaster Recovery on a NetPC Machine


MBO Basics

The Mainframe Backup Option (MBO) is an option to ARCserve.  MBO uses Mainframe host machines as a final, centralized repository for backup and archived data, leveraging existing investments in mainframe hardware, software, procedures and personnel.  Once the Mainframe Backup Option is installed, data backed up or archived by ARCserve may be directed to either local tape drives at the server, or to MBO which will ultimately store and maintain that data on mainframe tape and/or DASD as you define.

In a word, MBO maximizes network bandwidth for both backup and restore operations through two unique mechanisms:  BOB (Binary OBject) technology and Local Cache Backup (LCB).

BOB technology is a patent pending technology that allows MBO to identify data which has already been backed up, either locally or remotely to an MBO host.  Unlike other backup products, which use file names and attributes in an attempt to identify duplicated or changed data, MBO BOB technology condenses the actual contents of files down to 128-bit BOB IDs which are unique to the data itself.  MBO can actually eliminate the need to send duplicate data to the Mainframe over and over again.  Once data has been sent to MBO, future backups of the same file or backups of the same data duplicated on other servers or workstations will not result in that data being sent over your network again.

MBO also has another unique feature which both maximizes your network bandwidth, while speeding up restore times.  That feature is called Local Cache Backup (LCB).  Actually, MBO utilizes a 2-stage backup philosophy.  The first stage of any MBO backup is to compress and store new backup data on local server disk storage or local cache.  Once a file has been stored in local cache storage it is considered, "backed up" and is therefore capable of being "restored."  The transmission of this new data from LCB to the Mainframe host is a task which happens in the background.  Clearly, from a disaster recovery standpoint, data is not "safe" until it resides at the MBO host, but from a simple restore stand point, once data is in local cache it is available for restores.

The uniqueness of MBO is that MBO "manages" LCBs by keeping your data in local cache even after it has been transmitted to the MBO host.  This means that restore requests will rarely require that data be brought back from the MBO host.  You set limits on how much local server disk storage can be used as LCB, but the ability of MBO to manage LCB gives you total control over  how much or how little local disk space may be used for this purpose.  If restore speed is a high priority, you may configure large amounts of cheap server DASD for LCB usage.  If restore speed is not an issue, and the frequency of restores does not adversely impact available network bandwidth, then only minimal local server DASD need be set aside for LCB.

By investing in an adequate amount of inexpensive server DASD, MBO can perform most, if not all restores by pulling data from its local LCB, never having to access the MBO host at all.  This eliminates the impact of adhoc restores on networks during peak hours while at the same time providing restores at local LAN speeds.  A quick and cheap option which can only be achieved effectively because of our use of BOB technology.  For further information on BOB technology, see Appendix A.


MBO Functionality

Some common facts about MBO:

MBO acts as a virtual tape device to ARCserve, referred to as the MBO media

One MBO media is created per job

MBO media cannot be appended

There may be multiple sessions per MBO media, as each drive (node) is a session

Each MBO session has a unique, numeric id

MBO supports the following features:

Simple/GFS rotation

Agents to back up your Windows NT, Windows 95, UNIX, NetWare and NT Oracle database machines

Registry file backup


Benefits of MBO

The following are benefits of using MBO:

Leverages existing investments in data center hardware, software, personnel, policies and procedures relative to backup and disaster recovery.

Enables use of the data center as a manageable focal point for corporate-wide disaster recovery of widely distributed computing environments.

Eliminates network transmission of duplicated data across the enterprise, making MBO the first and only scalable enterprise backup product offering.

The server does not need to be stopped to perform the backup.  This is ideal for businesses that cannot tolerate any down time.

Working tightly with ARCserve, MBO gives you backup and restore options that until now have not been feasible, such as the ability to backup to both local tape and to MBO in one operation.  This means there is no need to manage local tape for the purposes of disaster recovery.


How MBO Works with ARCserve

The MBO runs on a server where ARCserve is installed.  It acts as a transport agent to move the data from the server to the MBO host directly.  The MBO works with ARCserve to ensure that you get a reliable backup of your files.

All MBO backups consist of four major stages:

Identify new and unique data by intercepting backup data as it streams through the ARCserve backup engine, then calculates the BOB ID for this data and checks the BOB ID against the MBO BOB database.

As new and unique data is encountered, the data is  compressed and stored as BOBs in local storage.  MBO uses server disk space on the LAN, known as MBO's Local Cache Backup (LCB), to cache the backed up files.  MBO uses LCB as both a quick access staging area before sending the data to MBO and as a local repository from which data may be restored.

Transmitting the compressed files as BOBs to the MBO host.  After MBO stores a compressed BOB into LCB, it must be transmitted for storage on the MBO host.  MBO first sends a list of BOB IDs to be transmitted to the Central Site Processor (CSP) for purposes of enterprise-wide duplicate elimination.  CSP performs this enterprise-wide duplicate elimination by returning to MBO a list of BOB IDs that do not already reside on the mainframe.  MBO then sends those BOBs only to the CSP.

Storing the data at the mainframe.

These stages overlap to improve performance.  For example, MBO transmits compressed BOBs to the mainframe while other files are broken into BOBs and compressed.

The data flow of the backup process that takes place between the MBO server and the ARCserve server is described below:

1.	The ARCserve server (or the ARCserve agent for workstation backups) determines which files to back up.

2.	ARCserve (or its agents) also performs the function of reading the backup data, protecting MBO from platform and application dependencies and exploiting ARCserve agent push technology.

3.	When MBO is the target backup device, the data read in by the ARCserve server (or its agents) is presented directly to an MBO backup API which runs as an integrated component of the ARCserve Job Engine.  This MBO component performs the BOB ID calculation, local server duplicate elimination, compression, and the writing of BOBs out to LCB storage.  The MBO product, running external to ARCserve, is told of new LCB BOBs as they are written, causing MBO to schedule the transmission of these BOBs to the MBO host.


Performing an MBO Backup

All MBO backups consist of five major stages:

Segmenting files into BOBs and calculating BOB IDs

Compressing new or modified BOBs

Storing new compressed BOBs in server local storage

Transmitting new BOBs (not known to CSP) to the MBO host

Storing the data at the MBO host into long-term storage media

All these stages overlap (run asynchronously) to improve performance and throughput.  For example, MBO transmits compressed BOBs to the MBO host while other files are being segmented into BOBs and compressed.

MBO has three available backup functions:

Backup Files to MBO

Copy Media to MBO

Copy Media to MBO after Backup


Backup Files to MBO

This option copies the files from the source directory to the mainframe.  This is one example of  submitting a backup job, for additional backup and filter options, refer to your ARCserve Administrator Guide.

1.	Start ARCserve and open the Backup Manager from Quick Access.

2.	Select the Source tab.  Select the machine, directories and/or files you want to back up.

3.	Select the Destination tab.

Check the Backup files to MBO check box.

Enter the media name to default to "MBO" plus data.  For example, "MBO 04/01/00"  Note:  If this field is blank, the job will not start.

4.	Select the Schedule tab.

Click on Custom Schedule or Use Rotation Scheme to set the day and the time the job will run.  Then click on the traffic light to submit the job.  For further information regarding customizing your job, please refer to your ARCserve Administrator Guide.


Copy Media to MBO

This option copies the files from a given media to the mainframe.

1.	Start ARCserve and open the Manager menu.  Click on Utilities, then on Copy Media to MBO.

The ARCserve Backup Source tab appears.

2.	Select the media and session (or all sessions) you want to copy to MBO.

Note:  When "Copy All Sessions" is selected, the data copied to MBO successfully is saved in a file called SAVESESS.TXT in the TEMP directory beneath the ARCserve home directory.  If another job is ran, only the sessions which have not been copied will be copied to MBO.  This file can be deleted if you want to copy all the sessions again.

If the previous "Copy All Sessions" job was not complete, the current "Copy All Sessions" job will only copy the sessions which were not copied in the previous job (instead of copying all of the sessions again). If the previous "Copy All sessions" job is complete, the current "Copy All Sessions" job will copy all the sessions.

3.	Select the Backup menu and click on Options.

Choose from four tabs to configure the backup environment:

Operation:  Set the backup to scan files with CRC verification and define database reporting criteria.

Pre/Post:  Define actions to take place before or after a backup job is active.

Log:  Define criteria for the activity log.

Alert:  Define Alert criteria.

4.	Select the Schedule tab.

Click on Custom Schedule or Use Rotation Scheme to set the day and time the job will run.  Then click the traffic light to submit the job.


Copy Media to MBO after Backup

This option backs up to media, then copies the files from the media to the mainframe.

1.	Start ARCserve and open the Backup Manager from the Classic Quick Access tab.

2.	Select the Source tab.  Select the machine, directories and/or files you want to back up.

3.	Select the Destination tab.

Uncheck the Backup file to MBO computer box.

Enter the media name or an asterisk "*" for a default name.  Note:  If this field is blank, the job will not start.

4.	Select the Backup pull-down menu and click on Options.  The Operation tab appears:

Select "Copy Media to MBO after Backup".  Only the sessions selected in the backup will be copied to the mainframe.  The MBO media will have the same name as the physical tape.

5.	Select the Schedule tab.

Click on Custom Schedule or Use Rotation Scheme to set the day and time the job will run.  Then click the traffic light to submit the job.  For further information regarding customizing your job, please refer to your ARCserve Administrator Guide.


Restoring from MBO

Files will be restored in the most efficient order.  This means the MBO will search for the data in the local cache first.  If the file does not exist in local cache, then it will send a list of BOB ID's to the CSP.  During a restore, ARCserve requests the session header first and then the requested data directories/files from  the MBO server.

The following is one example of  submitting a restore job, for additional restore options, refer to your ARCserve Administrator Guide.

1.	Start ARCserve and open the Restore Manager.

2.	In the Source tab, select the restore method.

The Restore methods supported by MBO are:

Restore by tree:  Displays the tree structure of the machines that can be seen from your computer.  Select the directories you wish to restore.

Restore by session:  Displays the media that were backed up.  Click on the session, directory and/or files you wish to restore.

Note:  The icon appears different for MBO media.

Restore by query:  You can choose the file and/or directories you wish to restore by specifying a search pattern to find the files that you require.

3.	Select the Destination tab.

Choose the destination directory.  The default is Restore files to their original location.  Uncheck the box to display currently attached drives in order to choose a new destination path.

4.	Select the Restore  menu and click on Options.

Each tab will modify your restore environment.  Click on the Operation tab.  Check the Restore Registry Files box to restore your registry files.

5.	Select the Schedule tab.

Click on Custom Schedule or Use Rotation Scheme to set the day and time the job will run.  Then click on the traffic light to submit the job.


Profile Manager

ARCserve's Profile Manager allows the ARCserve root user to customize user access to ARCserve.  The user profile scheme is includes:

Group: defines a collection of privileges.

User: object associated with a group.

As the default, when you install ARCserve, the arcroot user profile is set up with the administrator group assigned to it.  In general, each ARCserve user is assigned to only one group containing a profile of access rights.

Group definitions

You can select from the following groups:

Group	Rights/Restrictions
Administrator	Provides control over all ARCserve functions operating within a given ARCserve domain.  Associated with the arcroot profile.
Operator	Provides the same set of privileges as the Administrator, minus the ability to add and modify user-related information.
User	Provides control over all functions required by a user to manage and manipulate jobs owned by that user.  Restrictions:  Profile Manager - can change his/her own password  Device Configuration  Control over ARCserve daemons  No Media Pool modification  Adding of clients  Note:  Profile Manager uses distributed authentication services within the ARCserve domain, and since these authentication services are replicated through asynchronous coordination, there will be window of inconsistency between different ARCserve Hosts.

Related Topics:

  Changing a User's Assigned Group

  Changing a User's Password

  Creating an ARCserve User

  Deleting a User Profile

  Refreshing the Profile Manager Window


The "arcroot" User Profile

ARCserve is designed with the arcroot super user profile that is automatically assigned root privileges for all ARCserve functions.  The password for the arcroot profile can be set during the set up of the program or afterwards via ARCserve's Profile Manager.  Additional user profiles can be created (possessing their own set of rights), via the Profile Manager as well.

ARCserve User Names only control access to ARCserve related functions, and should not be confused with the operating system required log in name and password.

Related Topics:

  Changing a User's Assigned Group

  Changing a User's Password

  Creating an ARCserve User

  Deleting a User Profile

  Refreshing the Profile Manager Window


The Profile Manager

The Profile Manager provides access to all ARCserve User profiles.  Profiles can be created, viewed, and modified.

To open the Profile Manager, click the Profile icon from the ARCserve server's home page.  The Profile Manager opens.

Note:  When ARCserve is installed, the arcroot user profile is assigned to the Administrator group by default.  All additional ARCserve users that are created can only be assigned to one group at a time.

Related Topics:

  Changing a User's Assigned Group

  Changing a User's Password

  Creating an ARCserve User

  Deleting a User Profile

  Refreshing the Profile Manager Window


Media Exporting

This feature allows you to export a tape at the end of a backup job.  It allows you to move it out of the library or to an off site location for safe storage.  If the job does verification, the export is done at the end of the verification.  This feature is available for regular and rotation jobs and supported on tape and optical libraries and RAID.  The options available are:

None:  No tape exporting will take place at the end of a backup job.

Export RAID 1 Duplicate Tape After Job: This option is for RAID 1 support.  ARCserve will export the duplicate tapes for the related backup.  If the job spanned to multiple tapes, all the duplicate tapes used in this job will be exported.

Export All Tapes After Job: ARCserve will export all of the tapes for the related backup.  If the job spanned to multiple tapes, all of the tapes used in this job will be exported. In case of RAID tape sets, all the tapes in the tape sets for this job will be exported.  ARCserve retries a few times to check if the mail slot is empty to move the next tape to the mail slot.  If there are not enough mail slots to export all the tapes, the tapes that could not be exported will be moved back to the original home slot.  If the operator does not remove the tape from the mail slots then ARCserve will write this information in the activity log.


None, Media Exporting
None

No tape exporting will take place at the end of a backup job.


Export Duplicate Tape After Job
Export RAID 1 Duplicate Tape After Job

This option is for RAID 1 support.  ARCserve will export the duplicate tapes for the related backup.  If the job spanned to multiple tapes, all the duplicate tapes used in this job will be exported.


Export All Tapes After Job

ARCserve will export all of the tapes for the related backup. If the job spanned to multiple tapes, all of the tapes used in this job will be exported. In case of RAID tape sets, all the tapes in the tape sets for this job will be exported.


Replication

ARCserve has been integrated with SurviveIT and the ARCserve Replication option.  These products provide High Availability for data and applications by copying data in real-time from a Primary server to a Secondary server.  When ARCserve is backing up a server which is acting as a Secondary for a running Replication task, then it can identify which data is replicated and is guaranteed to be identical to the corresponding live data on the Primary.  ARCserve can be configured to separately handle replicated and non-replicated data.  A separate session can be used to store the replicated data.  This session will be configured so that the data will appear as if it had been backed up directly from the Primary server.  The options available are:

Back Up Replicated Data: This option will distinguish between replicated and non-replicated data and will create separate sessions for the two types.  The replicated data sessions will appear to have been backed up from the Primary server.

Skip Replicated Data: This option will distinguish between replicated and non-replicated data and will only back up non-replicated data.

Ignore Replication: This option will not distinguish between replicated and non-replicated data.  All data will be backed up as if it belonged to the Secondary.  Note that this option will not affect the way that data is backed up on a primary server.


Back Up Replicated Data

This option will distinguish between replicated and non-replicated data and will create separate sessions for the two types.  The replicated data sessions will appear to have been backed up from the Primary server.


Skip Replicated Data

This option will distinguish between replicated and non-replicated data and will only back up non-replicated data.


Ignore Replication

This option will not distinguish between replicated and non-replicated data.  All data will be backed up as if it belonged to the Secondary.  Note that this option will not affect the way that data is backed up on a primary server.


Windows 2000

The options in this dialog allow you to determine how ARCserve will handle the file system extensions during a backup.

The options available are:

Traverse Directory Junctions and Volume Mount Points: Selection of this option causes the backup job to traverse the volume or the directory being referred to and take a backup of it. At the time of restore of this session, you can restore files and directories contained in the referred to volume or directory.  When this option is not selected the backup job does not backup the volume or the directory being referred to by the volume mount point or the directory junction respectively. Thus at the time of restore you will not be able to restore a file or directory contained in the referred to volume or directory.

Backup Mount Points as part of the volume that they are mounted on: Selection of this options causes the volume(s) referred to by the Volume Mount Points to be backed up as part of the same session as the Volume Mount Points.  When this option is not selected the volume(s) referred to by the Volume Mount Points are backed up as separate sessions. Note that this option is enabled only when the previous option, Do not traverse Directory Junctions and Volume Mount Points, in not selected.

Restore file hard links: Selection of this option causes the hard link to be backed up, but not the file being referred to. When this option is not selected the file referred to by the hard link is backed up.


Traverse Directory Junctions and Volume Mount Points

Select this option if you do not want the Directory Junctions and Volume Mount Points to be traversed at the time of backup.


Backup Mount Points as part of the volume that they are mounted on

Select this option to back up the volume(s) referred to by the Volume Mount Points as part of the same session as the Volume Mount Points. If this option is not selected the volume(s) referred to by the Volume Mount Points being backed up are to be included in separate session(s). Note that this option is enabled only when the previous option, Do not traverse Directory Junctions and Volume Mount Points, in not selected.


Restore file hard links

The file hard links that are included with the backup job will be restored.


DIALOGS


Backup basics

Use the Backup Manager to configure and submit backup jobs to back up your data.

To learn more about backup jobs, see:

Backing up data on your network

Submitting a backup job

Selecting a backup method

Specifying media overwrite/append rules

Specifying a password for your backup job

Verifying your data on media

Specifying pre/post commands

Backing up network machines

Options for backup jobs


Options for backup jobs

Using ARCserve's advanced backup features, you can specify the following types of job options:

Backup Media  - specify options for first backup media, additional media, and session/encryption password.

Verification - select how ARCserve will ensure that the data on the media is readable after the files are backed up.

Retry - how to back up files that are being used by other users.

Operation - select whether to record the source file paths in the database, eject the media from the drive, or delete the source files after they are backed up.

Pre/post - run commands or batch files before the backup job runs and/or after it finishes.

Log - allows you to determine the level of detail you want recorded into the Job Queue's Log.

Virus - scan files for viruses before they are backed up.

Alert - send messages about events in your backup operation.

Replication - allows you to back up replicated data from a Secondary as if it came from a Primary server.

Media Exporting - export media at the end of a backup job.

Windows 2000 - specify options specific to the Windows 2000 operating system.


Related Topics

  Access the Options for Backup Jobs

  Applying job options


Backup Local Option Screen

The Backup Local Option screen allows you to select a verification option for a particular machine.


Backup Local Option Screen

None:  No verification will be done on the data backed up from this machine.

Scan Backup Media Contents:  Scan the media and check that the header for each file backed up from this machine is readable.

Compare Backup Media to Disk:  Read blocks from the media and compare, byte for byte, the data on the media against the files on this machine.

Session/Encryption Password:  Enter a password for your backup job (optional).

Note:  The Session/Encryption Password will be used as the encryption key, which allows you to "unlock" the code, restoring it to its original form.

Compression/Encryption:  Allows you to compress and/or encrypt your files before running your backup job.

OK:  Click this button when you are done.


None

No verification will be done on the data backed up from this machine.


Scan Backup Media Contents

Scan the media and check that the header for each file backed up from this machine is readable.


Compare Backup Media to Disk

Read blocks from the media and compare, byte for byte, the data on the media against the files on this machine.


Session/Encryption Password

Enter a password for your backup job (optional).

Note:  The Session/Encryption Password will be used as the encryption key, which allows you to "unlock" the code, restoring it to its original form.


Compress Files Before Backup

Allows you to compress your files before running your backup job.


Encrypt Files Before Backup

Allows you to encrypt your files before running your backup job.


RESTORE


Restore basics

Use the Restore Manager to submit a restore job to restore your data from media.

To learn more about submitting a restore job:

Submitting a restore job

Selecting data from media

Selecting a destination for your restored data

Options for restore jobs

Recovering from a disaster


Options for restore jobs

ARCserve provides several types of advanced restore options:

Backup Media options - specify media options for the restore job such as the media timeout period

Destination options - specify destination options for the restore job such as how to create the directory structure

Operation options - specify some general options for the restore job such as whether or not to include registry files

Pre/post job options - run commands or batch files before the restore job runs and/or after it finishes

Log options - allow you to determine the level of detail you want recorded into the Job Queue's Log

Virus Options - automatically scan for viruses before restoring files.

Alert options - send messages about events in your restore operation


Related Topics

  Applying job options


Search

Use the Search feature to have ARCserve quickly and automatically locate files and directories whose name or location you are unsure or unaware of.

Note:  You can only use this feature with the Restore by Tree source view.


Related Topics

  Use the Search Feature


Version History

Use the Version History feature to help you select the version of the file, directory, or drive you want to restore.

Note:  You can only use this feature with the Restore by Tree source view.


Related Topics

  Use the Version History Feature


Search Screen

The Search screen allows you to specify a search pattern.  ARCserve will search its database for all files and directories that match the pattern.

Search for: Provide the search pattern.

Search: Click this button to start searching ARCserve's database.

Go to: After searching the database, highlight an entry, and click this button to return to the Restore Manager with the entry selected.


Version History Screen

The Version History screen allows you to select a specific version of the file, directory, or drive to restore.

(List): Select the version you want from the list.  Information such as the media name and id, session number, source drive, etc., is displayed for each version.

OK: Click this button when you are done.


Session List Screen

The Session List screen lists the media you will need to restore the data you want.

Enter Password: If a media session has a password on it, highlight the media, then click this button to enter the session password.

OK: Click this button when you are done.


Password Screen

The Password screen allows you to enter the media session password, if required.  If the data was backed up with a session password, you need to enter the password here in order to restore it.

Password: Enter the session password here.

OK: Click this button when you are done.


Enter Password Screen

The Password screen allows you to enter the media session password, if required.  If the data was backed up with a session password, you need to enter the password here in order to restore it.

Password: Enter the session password here.

OK: Click this button when you are done.


MANAGING DATA


Copy basics

The Copy Manager allows you to copy (or move) files from one hard disk to another.  For example, you can run a copy job on your local machine to store files and directories on another machine that is going to be backed up to media.  Or, you might want to copy files when your hard disk space is running low.


Related Topics

  How to copy files

  Options for copy jobs


Options for copy jobs

ARCserve provides several types of advanced copy options:

Retry options - specify the action ARCserve should take if it comes across an open file.

Operation options - specify some general options for the copy job such as whether or not to create a mirrored version of the source.

Destination options - specify destination options for the copy job such as how to create the directory structure.

Pre/post job options - run commands or batch files before the  job runs and/or after it finishes.

Log options - allow you to determine the level of detail you want recorded into the Job Queue's Log.

Virus options - scan files for viruses before they are copied.

Alert options - send messages about events in your operation.


Related Topics

  Applying job options


Recover Database

The Recover Database window allows you to recover the ARCserve database by scanning media containing data that was stored by ARCserve.


Related Topics

  Recovering the ARCserve database

  How to recover a database

  Recover Database Options


Merge media

The Merge window allows you to merge information from media into the ARCserve database.


Related Topics

  Merging Media Information

  How to merge media

  Merge Media Options


Scan media

The Scan Tape window allows you to scan media for information on your backup sessions.


Related Topics

  Scanning Media

  Scan Media Options


Compare Media

The Compare window allows you to compare the contents of media to the files on your machine.


Related Topics

  Comparing Tapes

  Compare Media Options


Count

The Count window allows you to count the files and directories on a machine.


Related Topics

  Counting files

  Count Options


Purge

The Purge window allows you to purge (or delete) files from a machine.


Related Topics

  Purging (Deleting) Files

  Purge Media Options


Filter Screen

The Filter screen allows you to include or exclude files and directories from your jobs.


Filter Screen

Add:	Click this button to add a new filter to your job.

Modify:	After making changes to a particular filter, click this button to save those changes.

Delete:	Click this button to delete the selected filter.

Condition:	Using the drop-down box in the upper-left corner of the screen, select to include or exclude files.

Variable:	Using the second drop-down box, select the type of filter you want.

Values:	Using the last few drop-down boxes, enter the criteria for the filters.  These fields will vary depending on the type of filter you are adding.

OK:	Click this button when you are done.


Condition

Using the drop-down list box in the upper-left corner of the screen, select to include or exclude files.


Variable

Using the second drop-down list box, select the type of filter. A description of the filter displays at the bottom of the dialog.


Value

Enter criteria for the filter. This field may vary depending on the type of filter you are adding.


File Attributes

Files that match the attributes specified here will be included/excluded.


Related Topics

  About filtering


MANAGING JOBS


Job Status Manager

The Job Status Manager provides an intuitive way to centrally manage ARCserve Servers enterprise-wide.

To learn about Job Manager basics:

Introduction to the Job Status Manager

Accessing and using pop-up menus

To learn about the tasks you can perform with the Job Status Manager:

Managing Servers in the Job Status Manager  View all available ARCserve servers, job queues and activity logs.

Managing jobs in the queue -- add/delete/modify/reschedule job.

Monitor progress of active jobs

Displaying Job Detail and Job Log

View activity and tape logs


Save Job Script Screen

The Save Job Script screen allows you to save your job settings in a script file.


Save Job Script Screen

Save In:	Specify the path for the script file.  By default, the script will be saved to your ARCserve home directory.

File Name:	Enter a name for the job script.  By default, it will be saved with a .asx extension.

Save as type:	To save the job script in another file format, select the file format you want.

Job

Information:	Enter a brief description of the job.

Save:	Click this button to save the script.

Cancel:	Click this button to terminate the dialog with no further action.


Open Job Script/Add Job Screen

The Open Job Script/Add Job screen allows you to open an existing script or add a job script to the Job Queue.


Open Job Script/Add Job Screen

Script Name:	Select the job script you want to add to the queue.

List Files of Type:	By default, *.asx will appear in this field, since ARCserve scripts are saved with a .asx extension.

Directories:	Select the directory path where the job script can be found.

Drives:	Select the drive where the job script can be found.

Network:	Click this button for network options.

OK:	Click this button when you are done.


Add Job Screen

The Add Job screen allows you to open an existing script or add a job script to the Job Queue.


Add Job Screen

Script Name:	Select the job script you want to add to the queue.

List Files of Type:	By default, *.asx will appear in this field, since ARCserve scripts are saved with a .asx extension.

Directories:	Select the directory path where the job script can be found.

Drives:	Select the drive where the job script can be found.

Network:	Click this button for network options.

OK:	Click this button when you are done.


Reschedule Job Screen

The Reschedule Job screen allows you to change a job's status, execution date, or execution time.


Reschedule Job Screen

Job Status:	Select Ready or Hold.  If you select Hold, the job will not take off until its status is changed in the Job Queue .

Execution Date:	Indicate when this job should run.

Execution Time:	Indicate the time this job should run.

OK:	Click this button when you are done.


Related Topics

  Job Queue


DEVICES


Group Configuration Screen

The Group Configuration screen allows you to manage media groups on your machine.  You may also configure library groups.


Group Configuration Screen

Groups:	List of group names and the devices configured to each group.

Available Devices:	List of devices not assigned to a group.

Assign:	Click this button to assign an available device to a group.

Remove:	Click this button to remove a device from a group, and place it in the Available Devices list.

New:	Click this button to create a new device group.

Rename:	Select a device group name and click this button to give the group a new name.

Delete:	Select a device group and click this button to delete it.

Properties:	Select a device group and click this button to view the properties of the group.

OK:	Click this button when you are done.


Related Topics

  Configure Library Groups


New Group Screen

The New Group screen allows you to set up a new media group.


New Group Screen

Group Name:	Enter the name of the media group you want to set up.

OK:	Click this button when you are done.


Rename Group Screen

The Rename Group screen allows you to give an existing media group a different name.


Rename Group Screen

Change to:	Specify the name you want the media group to be changed to.

OK:	Click this button when you are done.


Format Screen

The Format screen allows you to specify a media name and expiration date when the media is formatted.


Format Screen

New Media Name:	Enter a name for the media.

Expiration Date:	Specify a date when the media should be retired.

Use Media Rotation:	Select this option to use a media rotation scheme—automatically assign the media to a media pool.

Media Pool:	Select a Media Pool for your media rotation.

OK:	Click this button when you are done.


Erase Screen (Media)

The Erase screen allows you to specify the type of erase ARCserve should perform on the media.


Erase Screen (Media)

Quick Erase:	Erase the media label only.

Quick Erase Plus:	Erase the media label and serial number.

Long Erase:	Remove all the data on the media completely.

OK:	Click this button when you are done.


Erase Screen (Removable Media)

The Erase dialog allows you to specify the type of erase ARCserve should perform on the removable media.

Quick Erase:	Erase the media label only.

Quick Erase Plus:	Erase the media label and serial number.

Long Erase:	Remove all the data on the media and format with FAT/NTFS.

OK:	Click this button when you are done.


Erase Screen (Optical Library)

The Erase function allows you to specify the type of erase ARCserve should perform on the optical disks in an optical library.


Erase Screen (Optical Library)

Quick Erase:	Erase the media label only.

Quick Erase Plus:	Erase the media label and serial number.

Long Erase:	Remove all the data on the media and format with FAT/NTFS.

OK:	Click this button when you are done.


Library: Format Screen

The Format screen allows you to format media within a range of slots at one time.


Library: Format Screen

Slot:	Select the slot which contains the media you want to format.

New Media Name:	Enter a name for the media.

Expiration Date:	Specify a date when the media should be retired.

Use Media Rotation:	Check this option to use a media rotation scheme.

OK:	Click this button when you are done.


Library: Erase Screen

The Erase screen allows you to erase media within a range of slots at one time.


Library: Erase Screen

Slot:	Select the slot which contains the media you want to erase.

Quick Erase:	Select this option to erase the media label.  A Quick Erase takes much less time than a Long Erase.

Quick Erase Plus:	Erase the media label and serial number.

Long Erase:	Select this option to remove the data on the media completely.  After a Long Erase, the media is considered blank, as if it were just formatted.

OK:	Click this button when you are done.


Library: Inventory Slots Screen

The Inventory Slots screen instructs the library to inventory media within a range of slots.  After you manually insert, remove, or exchange media from the library magazine, use this function to update the slot information.  This is generally used only when a you are manually changing a limited amount of media.  If you are updating the whole magazine, it is easier to use the Mount Magazine Command.


Library: Inventory Slots Screen

Slot:	Select the slots you want to inventory.

Quick Inventory:	Select this option to retrieve media from database.

Regular Inventory:	Select this option to read all media information.

OK:	Click this button when you are done.

Note:  You can use the SHIFT key to select multiple contiguous media.  Use the CONTROL key to select multiple non-contiguous media.


Mount/Dismount Magazine Screen

The Mount/Dismount Magazine screen allows you to take inventory of the whole magazine (mount), or move the magazine into place for removal, if necessary, and mark the whole magazine as empty (dismount).


Mount/Dismount Magazine Screen

Magazines:	Select a magazine to mount or dismount.

Mount:	Click this button to mount the magazine you selected.

Dismount:	Click this button to dismount the magazine you selected.


Library: Clean Drive Screen

The Clean Library Drive screen allows you to clean the heads of the selected library.  After cleaning the drive, the cleaning tape is moved back to its slot.  This function is enabled only if you assigned a cleaning tape slot.


Library: Clean Drive Screen

Device Name:	Select from the list of libraries.

OK:	Click this button when you are done.


Import/Export Media Screen

The Import/Export Media screen allows you to add a new media to a large capacity library by specifying an empty slot to which the media can be imported (import), or remove a media from a large capacity library (export).  When you import media, the library reads the media and adds it to its inventory.  Exporting makes it easy to remove a media for off-site storage, or to remove a media you suspect is bad.


Import/Export Media Screen

Slot:	Select an empty slot to import a media, or a slot which contains the media you want to export.

Import:	Click this button to import media.

Export:	Click this button to export the media.

OK:	Click this button when you are done.


Modify Screen

The Modify screen allows you to keep track of the location of your media.


Modify Screen

Media Name:	This is the name of the media you selected.

Media ID:	This id the ID of the media you selected.

Sequence No.:	This is the sequence # of the media you selected.

Location:	Enter a description of where this media is kept.

Previous:	Click this button to move to the previous media.

Next:	Click this button to advance to the next media.

Update:	Click this button when you are done.


Modify Screen (Media Records)

The Modify screen allows you to keep track of the location of your media.


Modify Screen (Media Records)

Media Name:	This is the name of the media you selected.

Media ID:	This id the ID of the media you selected.

Sequence No.:	This is the sequence # of the media you selected.

Location:	Enter a description of where this media is kept.

Previous:	Click this button to move to the previous media.

Next:	Click this button to advance to the next media.

Update:	Click this button when you are done.


REPORTING


Reports basics

The Reports Manager allows you to view or print a variety of reports based on the information contained in the ARCserve database.


Related Topics

  Viewing reports in the Report Manager

  Viewing and printing reports


Report Filter Screen

The Report Filter screen allows you to select which media device you'd like information about.


Report Filter Screen

Report on all devices:	Select this option to include all of your storage devices.

Report on selected devices:	Select this option to pick a specific storage device.

(List):	Highlight the storage devices you want more information about.

OK:	Click this button when you are done.


Report Filter Screen (Media Session)

The Report Filter screen allows you to select which storage device you'd like information about.


Report Filter Screen (Media Session)

Report on all devices:	Select this option to include all of your storage devices.
Report on selected devices:	Select this option to pick a specific storage device.
(List):	Highlight the storage devices you want more information about.
OK:	Click this button when you are done.


Report Filter Screen (Storage Device)

The Report Filter screen allows you to select which storage device you'd like information about.


Report Filter Screen (Storage Device)

Report on all devices:	Select this option to include all of your storage devices.
Report on selected devices:	Select this option to pick a specific storage device.
(List):	Highlight the storage devices you want more information about.
OK:	Click this button when you are done.


Report Filter Screen (Session Detail)

The Report Filter screen allows you to select which storage device you'd like information about.


Report Filter Screen (Session Detail)

Report on all devices:	Select this option to include all of your storage devices.
Report on selected devices:	Select this option to pick a specific storage device.
(List):	Highlight the storage devices you want more information about.
OK:	Click this button when you are done.


Session User Name and Password

You can enter, change, or verify the username and password for the destination machine for each media session.  If a session password has been assigned, enter the session password as well.

To enter or change the security information for a session, select the session and click the Edit button.


Related Topics

  Enter User Name and Password


Enter Network Password

Enter or modify the security information for the session you selected and click the OK button when you are finished.  To cancel this operation, click the Cancel button.


Enter User Name and Password (Restore)

Enter or modify the security information for the session you selected and click the OK button when you are finished.  To cancel this operation, click the Cancel button.


Purge Logs

The Purge screen allows you to delete Activity Log entries.  (The Activity Log is displayed in the Job Status manager).  You can select to delete the entire log or parts of the log based on the record date.  To delete parts of the log, click on either Older than or Between and use the spin buttons to select the appropriate dates.


Security and Agent Information

This dialog box displays the security and agent information for each machine and/or share that is selected as a source.  To change this information, select the machine, then select either the Security button or the Agent button.


Security and Agent Information Description

This dialog box displays the security and agent information for each machine and/or share that is selected as a source.


Related Topics

  Security Screen

  Agent Information


Security Information

This dialog box displays the security information for each machine and/or share that is selected as a source.  To change this information, select the machine, then select the Security button.


Security Screen

The Security screen allows you to provide a valid username and password to access a remote machine.


Security Screen

User Name:	Enter a login name for the machine.

Password:	Provide the password for the login name.

OK:	Click this button when you are done.


User Name

Enter a login name for the machine.


Password

Provide the password for the login name.


Select ARCserve Server

You can select an ARCserve Server from any Manager window that submits job requests to a server, such as the Backup window or the Restore window.  You can select a different server from each open Manager window.


Related Topics

  Select an ARCserve Server


Add Object - Preferred Shares

The Preferred Shares are a collection of your favorite backup shares.  (A share is a shared drive or directory.)  You can manually add individual share points to the Preferred Shares tree; the share point is remembered and displayed regardless of the status of the network connection.  This provides a quick access to commonly used shares on your machines. You can also setup preferred machines, which enables you to browse, backup, or restore all of the shared drives on a machine under a single machine.

This feature can be used to back up share points provided by other operating systems that are capable of creating "shares" in a network, such as UNIX NFS or OS/2 LAN Server shares.

This feature is also useful for users that frequently back up "shares" within a network, instead of "machines".  Shares are considered "named" short-cuts or aliases to machine drives and directories on the network.  Shares perform the same function as drive mappings, with the advantage of allowing the user to provide a descriptive name to the share.


Related Topics

  Add a Preferred Share to the Machine Tree


NEW


Job Status: Add Member Dialog

To add a server to the Job Status window:

Select a server from the Available Servers list and click Add.

To view recently attached computers in the Available Servers list:

Click Refresh.

To view the properties of the selected server:

Click Properties

The Available Servers list has the following columns:

Server: an attached server.

Assigned Groups: the job status groups to which the server is currently assigned.  You can assign the server to more than one group.

Domain: the domain to which the server belongs.


Job Status: Server Properties Dialog

View properties of the selected server.  Click OK when done.

Server name:

Name of the selected server.

Domain name:

Domain to which the server belongs.

IP address:

IP address for this server.

Latest response time:

Time of the last communication with the ARCserve autodiscovery feature.  The autodiscovery feature routinely surveys the attached servers for their status.


Pre/Post Options-Machine

Enter the pre/post commands for this machine.  See the following topics:

  Specifying pre/post commands

  Pre/Post Options


Preferred Server in Enterprise Report Dialog Box

This dialog box specifies which servers to include in your Enterprise Job Status Report.

Use this dialog box to:

Include servers in a report by selecting servers in the "Available Servers:" window, then clicking on the "<<Add" button.

Remove servers from a report by selecting servers in the "Preferred Servers:" window, then clicking on the "Delete>>" button.

Run the Enterprise job status report by clicking on the "OK" button.


Report Manager: Date Range Dialog

This dialog box specifies the GFS rotation backup jobs used to generate a GFS Media Prediction Report and the number of days to be included in the report.

Use this dialog box to:

Select a job used to generate a report in the "Job(s) List" window

Select the number of days to include in your GFS Media Prediction Report by clicking on the "Days from present time" spin box.

Select the "OK" button to run the report.


Report Manager: Media Pool Report Dialog

Select the media pool(s) for your report.


Report Manager: GFS Profile Report Dialog

Select the media pool(s) for your report.


Media Properties: Media Dialog

View the Media properties of the selected media.

Click OK when done.


Related Topics

  Media Pooling


Media Properties: Status Dialog

View the Media properties of the selected media.

Click OK when done.


Related Topics

  Media Pooling


Media Properties: Location Dialog

View or change the location of the selected media.

Click OK when done.


Related Topics

  Media Pooling


Media Properties: Sender Dialog

View the sender information of the selected media.

Click OK when done.


Related Topics

  Media Pooling


Location Property: Sender Dialog

To specify the sender information for the new location:

1.	Enter the sender information in the fields provided.

2.	2.	Click OK when done.


Related Topics

  Media Pooling

  Performing Location Maintenance


DBagent Backup Option Dialog 1

Select a backup method.


DBagent Backup Option Dialog 1

Normal (Full) Backup:  Backup the entire mailbox.

Incremental Backup:  Backup only the changes made since the last backup.

Time-Based Backup:  Allows you to base the backup on a specific date.

Backup mailbox contents after:  The backup will be based on this date.


Normal (Full) Backup

Selection of this option will backup the entire mailbox.


Incremental Backup

Selection of this option will cause the backup to include only changes made since the last backup.


Time-Based Backup

Select this option to base the backup on a specific date.


Backup mailbox contents after:

The backup will be based on the date entered in this field when Time-Based Backup is selected.


DBagent Backup Option Dialog 2

Select a backup method.


DBagent Backup Option Dialog 2

Normal (Full) Backup:  The entire database and the associated logs will be backed up when this option is selected.  In addition, log files that are no longer needed will be purged.

Copy Backup:  This function will perform the same operation as Normal Backup except that the log files will not be purged.

Incremental Backup:  Only the log files will be backed up.  In addition, log files that are no longer needed will be purged.

Differential Backup:  This function will perform the same operation as Incremental Backup except that the log files will not be purged.

Generate a CRC Check:  During restoration data will be verified with a CRC check.


Normal (Full) Backup

The entire database and the associated logs will be backed up when this option is selected.  In addition, log files that are no longer needed will be purged.


Copy Backup

The entire database and the associated logs will be backed up when this option is selected.


Incremental Backup

Only the log files will be backed up.  In addition, log files that are no longer needed will be purged.


Differential Backup

Only the log files will be backed up.


Generate a CRC Check

During restoration data will be verified with a CRC check.


Agent Information

Note: Before enabling the Client Agent, you must load it on each machine you will be accessing.  Be sure to note the address of the source machine (the machine the Agent is loaded on) when loading the Client Agent.


Fields_Agent_Information
Agent Information

Use Agent:  Select this option if the target machine has an agent installed on it.

IPX/SPX:  When choosing this option, enter the IPX internal network number for the agent machine.

TCP/IP:  Specify a TCP/IP address for the agent machine, or check the Use Computer Name Resolution option to automatically search for the correct IP address each time you connect to this computer.

Use Computer Name Resolution:  Use this option if it is necessary to automatically search for the correct IP address each time you connect to this computer.  Use this option if the IP address for the computer is not constant.

Enter IP address:  Specify a TCP/IP address for the agent machine.


Use Agent

Select this option if the target machine has an agent installed on it.


IPX/SPX

When choosing this option, enter the IPX internal network number for the agent machine in the appropriate text boxes.


IPX Internal Network Number 1
IPX Internal Network Number

Enter the first portion of the IPX internal network number for the agent machine.


IPX Internal Network Number 2
IPX Internal Network Number

Enter the second portion of the IPX internal network number for the agent machine.


TCP/IP

Select this option and specify a TCP/IP address for the agent machine, or check the Use Computer Name Resolution option to automatically search for the correct IP address each time you connect to this computer.


Use Computer Name Resolution

Use this option if it is necessary to automatically search for the correct IP address each time you connect to this computer.  Use this option if the IP address for the computer is not constant.


Enter IP address

Specify a TCP/IP address for the agent machine.


Related Topics

  Use the Installed Client Agent to Back Up This Machine


Agent: Computer Type Dialog

ARCserve is unable to determine the operating system of the remote computer.

Select an operating system and click OK.


OS/2

The operating system of the remote computer is OS/2.


Windows 95

The operating system of the remote computer is Windows 95.


Windows NT

The operating system of the remote computer is Windows NT.


Windows for Workgroups

The operating system of the remote computer is Windows for Workgroups.


Agent: Local Option for UNIX Agent

Select a local option for this UNIX Agent.

For more information:

Refer to you Client Agent for UNIX User Guide.


Job Summary Dialog

Perform one of the following actions:

Click OK to submit this job.

Click Save to save the job to a script file.

Click Cancel to cancel this operation.

Click Source Priority to set the priority order in which the job sessions will initiate.

Note:  This action is only available for a Copy or Backup Job.


Field Job Summary Dialog
Job Summary Dialog

Select from the following options:

Job Description:  This area shows details on the jobs that are scheduled to run.

Run Now:  Execute the job now.

Schedule On:  Select this option to have the job run on a specified date at a specified time.

Submit on Hold:  The job will be submitted to the queue but will not run until its status is changed in the Job Queue.

Description:  Enter a description in this field and it will display with the job in the Job Queue.


Job Description

This area shows details on the jobs that are scheduled to run.


Run Now

Execute the job now.


Run On

Select this option to have the job run on a specified date at a specified time.


Submit on Hold

The job will be submitted to the queue but will not run until its status is changed in the Job Queue.


Description

Enter a description in this field and it will display with the job in the Job Queue.


Related Topics

  Creating Scripts for Your Jobs


Device Manager: Rebuild Dialog

Rebuild a lost or damaged media from a Level 5 RAID.

REBUILD feature of ARCserve RAID option allows the user to rebuild a missing or bad tape in a Level 5 RAID tape set.  This feature is supported for Tape Drive RAID as well as Tape Library RAIDs.

RAID 5 facilitates continuation of backup jobs even if one of the tapes or tape drives fail.  It is preferable that after replacing the faulty tape (or tape drive) that you rebuild the missing tape to keep the RAID set complete, so that future failures can be tolerated.  (Please note that RAID 5 can only support one drive failure).

The REBUILD process has been simplified from previous versions.  Now you do not have to choose the source or target drives.  Just insert the incomplete RAID set and a BLANK tape to the tape drives and choose REBUILD from the Device Manager.  For Library RAIDs a blank tape should be available in the library.


Related Topics

  Procedure to Rebuild Tape Drive RAID and Library RAID Sets


Import Export Dialog Box
Import/Export Dialog Box

Import media from mail slots to empty slots in your library or export media from your occupied slots to your mail slots.

Note:  The "Import/Export" dialog box has two forms.  To toggle from the Import dialog box to the Export dialog box, click on the "Export" option button.

Use the "Import" dialog box to:

View all the available slots in the library device in the "Slots in library:" window.

Assign media to an available slots(s) by selecting a mail slot(s) and clicking on the "Assign>>" button.

Import the media to the library by clicking on the "OK" button.

Use the "Export" dialog box to:

View all the occupied slots in the library in the "Slots in library" window.

Remove the media from slots in the library to mail slots by selecting mail slots, selecting media in the "Slots in library:" window, then clicking on the "<<Remove" button.

Export the media from the library by clicking on the "OK" button.


Tape Rotation: Calendar Property Dialog
Media Rotation: Calendar Property Dialog

Specify the following backup information for the selected day:

Backup Method

Media Name

Execute Time

Click OK when done.


Media Rotation: Calendar Configuration Dialog

Specify the following backup information for the calendar:

Backup Method

Media Name

Execute Time

Click OK when done.


Media Rotation: Calendar Exceptions Dialog

Specify the following backup information for this exception:

Backup Method

Media Name

Execute Time

Click OK when done.


Alert: Methods and Recipients Dialog

ARCserve allows you to define configurations for your methods and recipients used in the Alert notification system.  A Method and Recipients Configuration is set of available methods (for example, Printer) and their respective recipients (the printers on your network which will receive the alert notification).

Note: The first time you open the Methods and Recipients dialog box, an untitled configuration tree is displayed in the browser at the left of the dialog.  If you modify this configuration, you will be prompted to enter a new name for it.


Configuration

A Method and Recipients Configuration is set of available methods (for example, Printer) and their respective recipients (the printers on your network which will receive the alert notification).

Make a selection from the drop down list-box or do one of the following:

add a method using the New button

remove a method using the Delete button

rename a method by using the Rename button


Configuration Tree

This list displays the methods and respective recipients for the configuration selection.

Note: The first time you open the Methods and Recipients dialog box, an untitled configuration tree is displayed in the browser at the left of the dialog.  If you modify this configuration, you will be prompted to enter a new name for it.


Related Topics

  Alert Options

  Add or Modify a New Methods and Recipients Configuration

  Add or Modify a Recipient


Alert: Modify Broadcast Recipient Dialog

Alert broadcasts can be sent to specific network users or groups.

To add broadcast recipients:

1.	1.	In the Alert option, click broadcast.

2.	2.	Browse and highlight the group/machine you want.

3.	3.	Click the Add button.


Alert: Add Pager Recipient

The pager option is used to a send an alphanumeric pager message. When you click the Pager tab, the current list of recipients appears:

To add pager recipients, you first need to configure your communications ports for Alert if you have not already done so.

To configure your communications ports:

Refer to the ARCserve user guide.  You must configure your ports using the Alert Manger.


Related Topics

  Add Pager Recipients and Interpret Pager Messages


Alert: Add SNMP Recipient Dialog

The SNMP option is used to send an SNMP 'trap' (message) to an SNMP manager.

An example of an SNMP manager includes Computer Associates Unicenter TNG (The Next Generation).

This section explains the SNMP fields on the SNMP Configuration screen.

When you click the SNMP tab, the current list of managers appears:


Related Topics

  Add SNMP Recipients


Alert: Modify Event Recipient Dialog

To add event recipients:

1.	Highlight the group/machine you want.

2.	Press the Add button.


Alert: Modify Printer Recipient Dialog

Print recipients are used to alert users through a printed document.  (These recipients are called Trouble Tickets in the Alert Manger.)

To configure the Printer recipient:

Enter the following:

Company Name - Enter your company name.

Location - Enter the location of your company.

Trouble Ticket Header - Enter the information that should appear at the top of each Trouble Ticket.

To choose a printer:

1.	1.	Choose a printer from the Print Queue List by highlighting it.

2.	2.	Click the Add button to move the printer to the Recipients column.


Alert: Modify E-mail Recipient

The E-mail option is used to send E-mail messages to specific users.

NOTE:  Microsoft Mail or Microsoft Exchange Client must be installed on your computer in order to be able to send messages or to enter configuration data on this screen. Consult your Windows NT manual for instructions about how to set up your E-mail account.


Related Topics

  Add E-mail Recipients


Add Object


Adding objects to the machine tree

You can add objects to the machine tree that are unavailable when you set up a job.  For example, you can add a machine that is temporarily unavailable and schedule a backup/restore for the machine.

You can add the following types of objects to the machine tree:

Microsoft Networks domains or workgroups, machines, or shares

NetWare servers and volumes


Related Topics

  View an Example


OLD STUFF


Scheduling jobs

See Scheduling a job


Schedule option

See Scheduling a job


Creating scripts

Creating scripts for your jobs


OLD DISASTER RECOVERY


Maintaining your system

Make sure you back up ARCserve's databases

Whenever you back up your entire network machine, ARCserve's databases are backed up as well.  Always maintain a current backup of your ARCserve database files so that recovering from a disaster is made easier.

Always maintain current backups

The most important thing you can do to ensure  against data loss is to maintain current backups of all your network machines.   If you do not have these backups, then ARCserve is limited in its ability to recover against data loss or disaster.  Be sure to create a media rotation scheme using different backup methods and scheduling as a means of maintaining current backups.

If something happens to any machine between full backups, then you can recover using the last full backup made and the most recent differential backup (which contains all the modifications to the data since the last full backup).  Refer to Backing up data on your network for details on backing up and creating a media rotation scheme.

The following books will be useful in the following sections should you need to use ARCserve to recover a network machine:

Operating Systems Manuals - If you need to install the operating system

ARCserve Installation Guide - If you need to re-install ARCserve on your machine

In addition, you should have the appropriate installation disks/media with you.


Related Topics

  Backing Up Data on your Network


Restoring an ARCserve Machine

Recovering from a disaster


Recovering the database

Recovering the ARCserve database


OLD REPORTING STUFF


Getting information from ARCserve

See Viewing and printing reports


Job Report

See Viewing and printing reports


Media Report

See Viewing and printing reports


Media Session Report

This report provides information about all of the backup sessions that are on media.  (Each source you select to back up is saved on media as an individual session.)  The report contains the session information that is found in the Database Manager on the Job Records or Media View window when you highlight a record and click the Session tab.  When you go to view this report you will be asked if you want the report to include all media or just one that you select.

For each media session, this report includes the following:

Session number

Start time

End time

Total files in the session

Session method

Status

When you go to view this report you will be asked if you want the report to include all media or just one that you select.

Why would you need to view this report?

You can view this report to get a general idea of what is backed up on media when you need to restore files.


Media Session Detail Report

This report includes all of the information found in the Media Session Report and also lists every file that was backed up in each session.  The report contains the session information that is found in the Database Manager on the Job Records or Media View windows when you highlight a record and click the Files tab.  When you go to view this report you will be asked to select media and a session from that media.

Why would you need to view this report?

You can view this report if you need to know which files are backed up in each backup session.  This is useful when you need to restore files.


Storage Device Report

This report provides information about all of the storage devices you are using with ARCserve.  It contains the information that is found in the Database Manager on the Device View window.  This report gives you a convenient way of getting a hard copy printout of your Device View information.  When you go to view this report you will be asked to select a storage device.

For each storage device, this report includes the following:

Device type

Vendor

SCSI ID

Firmware revision

Amount of usage

Last head cleaning date

Head cleaning count

Media errors

Why would you need to view this report?

You may need to view this report if you are experiencing problems with a storage device.  It can indicate if it is time to clean the heads, or if you have the wrong firmware installed.


Job Queue Log/Reporter option

See Viewing and printing reports


Date Range Dialog Box

This dialog box allows you to view a report of a selected backup job and review, day by day, which media will be used within the library.  You can also predict how many tapes/media you will need for the job, based on the time parameter you set.


Related Topics

  View a Job List for a Specific Time Period


Device Group Properties

The Device Group Properties Dialog allows you to choose whether or not to allow Data Migration and/or the ProActive Backup Option to the device group.

Data Migration

When volumes become full on servers, network administrators used to have two choices:

Delete data and archive it

Add more storage capacity to the servers

Neither of these solutions is ideal.  Users do not want their data archived away, requiring intervention from administrative personnel to restore it.  The cost of adding additional storage hardware to existing systems is high and requires administrative resources.  The increased memory requirements and risks associated with modifying the hardware of production servers must be taken into consideration.  The greatest expense incurred when installing new storage devices on existing servers is the requirement for additional personnel to manage and backup the new storage hardware.

The cost of managing storage hardware is extremely high per megabyte of storage.  Data migration is one solution to the dilemma of managing your data.

With Data Migration, the part of the file containing data is moved from the volumes of your NT machines to a hierarchy of less expensive storage media.  Migrated files will continue to display the same characteristics they did prior to migration and can still be viewed through the Windows Explorer or File Manager.  In the Data Migration strategy, data migrates from the fastest and costliest media to slower, cheaper media as the files age and are less frequently used.  Thus, this scheme is commonly referred to as Hierarchical Storage Management or "HSM".

ProActive Backup Option

The Proactive Backup option allows you to submit node level or volume level backups from the Client Agent side.  Also, if the option was enabled and it was well configured and tested, an automated backup will be submitted to the remote ARCserve server whenever a hardware alert message is generated by the system. This alert will notify the Client Agent that the drive status is degraded or is predicted to be degraded.

Once you have completed the ProActive Backup configuration, the Client Agent is set to submit backup jobs in the event that a hardware alert message is received by the system.


NetWare or Compatible Network - Add Object

To add an object:

1.	Enter the object name and click Add.


Microsoft Windows Network - Add Object

To add an object:

Enter the object name and click Add.


Image Backup Options Dialog

To enable high-speed image backups:

1.	1.	Select Enable image backup for all drives that apply.

2.	2.	Check the appropriate options.

3.	3.	Click OK.


Media Pool: Media Assignment Dialog Box

To assign media to save sets and scratch sets of media pools:

1.	1.	Expand the media pool in the Media Pool list by clicking on it.

2.	2.	Select the save set or scratch set to which you want to assign a device.

3.	3.	Select the storage medium by clicking on it in the Available Media list.

4.	4.	Click on the <<Assign button to assign the media to the selected subset of the Media Pool.

5.	5.	Click OK.

To remove media from save sets and scratch sets of media pools:

1.	1.	Expand the media pool in the Media Pool list by clicking on it.

2.	2.	Expand the save set or scratch set from which you want to remove a device.

3.	3.	Select the storage device you want to remove, click the >>Remove button.

4.	4.	Click OK.


Media Pool Configuration Dialog

For existing media pools, see Overview of Media Pooling

To configure a new media pool:

1.	Enter the Pool Name, Minimum # of media in Save Set, and Retention Time.

The three Serial Number fields contain default values that you can change if desired.

2.	Click OK.


Related Topics

  Creating a Media Pool

  Overview of Media Pooling


Media Operation Dialog

To move media from one set to another:

1.	Select the media you want to move and click the appropriate Move button.

The media are moved in the direction you select.

2.	When you're finished, click OK.

Note:  You can also move media from Scratch Set to Save Set and vice versa by dragging and dropping the media icon in the left panel of the Media Pool Manager.

The media you've moved appear in their new locations in the left pane.


Related Topics

  Media Pooling

  Moving Media


Media Pool: Location Maintenance Dialog

To perform location maintenance:

1.	From the Media menu, select Location Maintenance.

The Location Maintenance dialog box appears.  The upper scroll box displays the list of existing locations.  The lower scroll box displays a list of media.

To enter information about a new location, click New.  A dialog box appears, enabling you to enter information about the location.

To modify information about an existing location, click Modify.  A dialog box appears, enabling you to modify information about the location.

To assign media to a location, highlight the media, highlight the location, and then click Assign.

2.	When you've finished, click OK.

Revised information about media location is stored.


Related Topics

  Media Pooling


Location Propety: Location Dialog
Location Property: Location Dialog

To add a new location for storing your media pools:

1.	Enter the new location information in the fields provided.

2.	Click OK when done.


Related Topics

  Media Pooling

  Performing location maintenance


Agent: Add Object Dialog

To add a new Client Agent:

1.	Enter the Host Name for the machine.

2.	If using TCP/IP protocol:

Specify a TCP/IP address for the agent machine, or check the Use Computer Name Resolution option to automatically search for the correct IP address each time you connect to this computer.  Use this option if the IP address for the computer is not constant.

3.	If using IPX/SPX protocol:

Enter the IPX internal network number for the agent machine.

4.	Click Add.


Agent: Add Object Dialog
Host Name

The Host Name of the machine that has the Client Agent on it


Related Topics

  Enabling the Client Agent


Agent: Add Object using Auto-Discovery

Note:  Auto Discovery is available for Windows 95/98 and NT Agents only.

To add a new client agent using the Auto-Discovery Service:

1.	Highlight the Machine Name in the Agent Select dialog list.

2.	Click Add.  Machine name will be removed from the Agent Select list when added.

3.	Click Close to close Agent Select dialog.

The Agent Select dialog is created using the Auto-Discovery Service feature which automatically generates a list of available agents.  The Auto Discovery Service will only display client agents that are up and running on the remote machine when the list is generated.

Note:  It is strongly recommended that the Auto-Discovery Service settings be checked and verified if an agent you want to use is not shown in the generated list of available agents.  For this purpose ARCserve provides the Discovery Configuration utility(dsconfig.exe) located in its home directory.

In the Discovery Configuration dialog, the Subnet tab and the Subnet Mask tab displays the IP subnet addresses and IP subnet masks discovered by Discovery Service.  You must verify that:

1.	The local subnet mask shown in Subnet Mask tab is correct

2.	The subnet address and correct relative subnet mask for the machine where questionable agent resides is listed in Subnet tab

Note:  The subnet mask for the remote subnet could be different from the local subnet mask listed within the Subnet Tab.

You can manually add/modify any subnet address or subnet mask in Subnet tab or Subnet Mask tab and then initiate discovery process again(use Discover Now button).

Please refer to the Discovery Configuration Help for more information.


List

This area displays the list of available agents.


Related Topics

  Agent: Add Object Dialog


NDS Option Dialog Box

If you want to backup an NDS tree:

1.	Check Backup NDS

2.	Enter the NDS Tree name.

3.	Enter the Login name for the NDS Tree.

4.	Enter the password for NDS Tree.

5.	Enter the name of the server on which the NDS tree resides.

6.	Click OK.


Source Priority

The Source Priority dialog is used to change the priority order of jobs.

Use the Top, Up, Down and Bottom buttons to change the priority order in which the jobs will be processed.  You can also click and drag the Group to another data stream.


Tree Node

This tree displays the order in which the jobs will be processed.


Prune Activity Log Settings

This dialog allows you to prune the events in the Activity Log.


Fields Prune Activity Log Settings
Prune Activity Log Settings

Select from the following options:

Enable Auto-Pruning of the Activity Log:  Select this option to control the size of the Activity Log by allowing ARCserve to configure at what point the log should be pruned.  This will take effect the next time you run the DBPrune Job.

Prune Entire Activity Log:  Select this option to have the entire ARCserve Activity Log pruned.

Prune Entire Activity Log that is:  Allows you to configure a specific interval at which the ARCserve Activity Log will be pruned.  For example, older than one day.

Older than:  This field is used in conjunction with the Time Unit drop-down list box.

Time Unit:  Select the time interval that will be used to determine when the ARCserve Activity Log is pruned.


Enable Prune of the Activity Log

Select this option to control the size of the Activity Log by allowing ARCserve to configure at what point the log should be pruned.  This will take effect the next time you run the DBPrune Job.


Prune Entire Activity Log

Select this option to have the entire ARCserve Activity Log pruned.


Prune Entire Activity Log that is

Allows you to configure a specific interval at which the ARCserve Activity Log will be pruned.  For example, older than one day.


Older than

This field is used in conjunction with the Time Unit drop-down list box.


Time Unit

Select the time interval that will be used to determine when the ARCserve Activity Log is pruned.


Settings

This dialog allows you to configure settings for the Activity Log.

The Advanced Options button allows you to enable debugging messages to display in the ARCserve Activity Log.


Fields_Settings
Settings

Set Job Queue Refresh Rate to:  Specify a time, in seconds, for periodic update of the Job Status Manager.

Set Device Manager Refresh Rate to:  Specify a time for periodic update of the Device Manager.

Set Animated Speed to:  Specify a speed at which the tape bitmap will rotate if animation is selected for the Device or Backup Manager.

Show Removable Drive:  Removable drives will display, for example, a floppy drive under My Computer.

Show Virtual Drive:  Virtual drives will display under My Computer.

Show CDROM Drive:  CD ROM drives will display under My Computer.

Show File in Source Tree:  All directories and files will display under My Computer.

Auto Start All Engines:  All ARCserve engines will start automatically when the Manger is started.

Show Remote Drive:  Mapped drives will display under My Computer.


Set Job Queue Refresh Rate to

Specify a time, in seconds, for periodic update of the Job Status Manager.


Set Device Manager Refresh Rate to

Specify a time for periodic update of the Device Manager.


Set Animated Speed to

Specify a speed at which the tape bitmap will rotate if animation is selected for the Device or Backup Manager.


Show Removable Drive

Removable drives will display, for example, a floppy drive under My Computer.


Show Virtual Drive

Virtual drives will display under My Computer.


Show CDROM Drive

CD ROM drives will display under My Computer.


Show File in Source Tree

All directories and files will display under My Computer.


Auto Start All Engines

All ARCserve engines will start automatically when the Manger is started.


Show Remote Drive

Mapped drives will display under My Computer.


Library Filter

This feature applies only on the changers wherever the devices or groups hierarchy is displayed (for example, in the Backup Manager under the Destination tab or in the Device Manager view).

This filter allows the option of seeing the empty slots and manipulating the preferred range of slots.

It is recommended to use this feature if a large library is attached to the system.


Show Empty Slots

Select this option to view the empty slots in the library.


Show Slots Between

Specify a range of slots to view by inserting the minimum and maximum number of slots allowed.


System State

System State is a feature of Windows 2000.  ARCserve treats the system files and certain databases as a single entity.  A new session named System State is created in addition to the existing sessions that are in ARCserve.  System State can be backed up and restored at the same time.  The System State consists of the following components.

Boot and System Protected Files

Active Directory

Sys Volume

COM+ Database

Cluster Database

Certificate Server Information

Registry

Active Directory and Sys Volume will be backed up only when the machine is a Domain Controller.  The Cluster Database and Certificate server backup only applies when either the cluster server or certificate server are installed.

Backing up System State is done locally.  Using the ARCserve NT Client Agent, ARCserve is able to backup System State on any machine in the network.  Only full backup of System state is supported.  There is no incremental or differential backup of System State.  Also, restoration of System State can only be done using either the Restore by Tree method or Restore by Session method.

Active Directory

The Active Directory is a directory service that provides a way to allocate user and resource information in the enterprise computing environment.  ARCserve can perform a backup of the Active Directory only when the service is online.  Restoration of the Active Directory can only be performed in Directory Service Restore mode (in which the Directory Service is offline).

There are two ways to restore the Active Directory, authoritative and non-authoritative.  The default restoration of the Active Directory is non-authoritative.  If an authoritative restore is preferred, ARCserve has an option to handle it automatically.  To invoke this functionality, right-click in the System State session and choose Option.  The System State Restore Options dialog appears.  Select the check box Make the Restored Copy of the Active Directory Authoritative to make the Active Directory restore authoritative.  Your system must be rebooted after the restore job finishes.


System State Restore Options

This dialog displays when the restored session is a System State session.  By right clicking on the session, this dialog will be invoked (for restore by tree as well as restore by session)

Make the Restored Copy of the Active Directory Authoritative  ARCserve makes the Activity Directory restore authoritative.

Stop the Cluster if Necessary to Restore the Cluster Database  Restoring the cluster database requires that the cluster service be stopped. This check box gives ARCserve permission to stop a cluster service in order to restore the cluster database. This is required only in case of Windows 2000 Advanced Servers.

Enable Quorum Drive Selection When Quorum Location Change  Provide the new drive letter of the quorum.  If it is not provided, the restore will fail.

Select the drive letter in case the Quorum location has changed since this Backup  Specify the drive letter that is currently being used by the quorum resource of the cluster.

Do Not Stop WWW Service  In order to successfully restore the Certificate Server database the WWW service needs to be stopped. If this checkbox is selected the WWW service would not be stopped and the Certificate Server database may not be restored successfully.


Make the Restored Copy of the Active Directory Authoritative

ARCserve makes the Activity Directory restore authoritative.


Stop the Cluster if Necessary to Restore the Cluster Database

Restoring the cluster database requires that the cluster service be stopped. This check box gives ARCserve permission to stop a cluster service in order to restore the cluster database. This is required only in case of Windows 2000 Advanced Servers.


Enable Quorum Drive Selection When Quorum Location Change

Provide the new drive letter of the quorum.  If it is not provided, the restore will fail.


Select the Drive Letter in Case the Quorum Location has Changed Since this Backup

Specify the drive letter that is currently being used by the quorum resource of the cluster.


Do not Stop WWW Service

In order to successfully restore the Certificate Server database the WWW service needs to be stopped. If this checkbox is selected the WWW service would not be stopped and the Certificate Server database may not be restored successfully.


ARCserve Library Option

What are the ARCserve Library Options?

Tape Library Option - allows you to back up large amounts of data to tape libraries.

Optical Library Option - allows you to back up large amounts of data to optical libraries.

Both options provide the same basic functionality.  Differences between the Tape and Optical Library option are noted where appropriate.

What is a library?

A library is a device containing one or more tape or optical drives with an automated media delivery system such as a robotic picker which allows large amounts of data to be backed up without manual intervention.  A library consists of:

a magazine or bin, where one or more groups of storage media (such as tape or optical media) are stored.

a robotic picker which moves the media units between the magazine slots and the drives.

one or more drives, which transfer (back up or restore) data between your computer and the storage media.

A library can contain one or more storage drives, and from one to several hundred magazines.  Smaller libraries are sometimes referred to as autochangers or changers.  We use the term "library" to refer to libraries of any size.


Related Topics

  What are the advantages of using a library?

  Built-in Changer support

  How many SCSI IDs does a library have?

  Library Option Features

  Device management functions

  About Barcodes

  Backing Up Data to a Library


Advantages of using a library

Some of the advantages of using a library are:

Automation – no manual intervention is necessary during backup and restore operations.

Capacity - libraries can contain multiple storage devices and over a hundred media.

Note:  ARCserve does not support stackers.  (Libraries allow random access of media slots, while stackers do not).


How many SCSI IDs does a library have?

Working with a library is very similar to working with a single storage drive.  One of the primary differences is that a library typically uses at least two SCSI IDs:  one for the library itself and one SCSI ID for each of the library's drives.

Some libraries use a single SCSI ID.  When a library uses only one SCSI ID, the library and the library drive are each assigned a Logical Unit Number (LUN) to differentiate between commands for each device.  A single SCSI ID is, in effect, split into two IDs.


Library Option
Library Option Features

Using Device Manager with Libraries

Viewing Information

Library Device Management Functions

Configuring Library Groups

Backing Up to a Library

Restoring from a Library

Troubleshooting

Definitions


Library Option Features

The ARCserve Library Option contains the following major features:

Built-in Changer support

Multiple drive support

Multiple library support

Quick Initialization

Concurrent drive initialization

Multiple, concurrent, device management functions

Barcode labeling for faster media identification

Grouping by slots

Single-step library group spanning

Continuous operation with a defective drive (Fault tolerance)

Multiple, concurrent, group access (Tape Library Option only)

Find Media or Slot

Big Library Support


Built-in Changer support

For the Windows NT platform, ARCserve will have a built-in changer that will consist of one tape drive with an unlimited number of slots.

In addition, the Windows NT platform will offer a separate option offering a larger changer with multiple drives.


Multiple drive support

ARCserve supports libraries with multiple drives as well as those with single drives.


Multiple drive support
Multiple library support

ARCserve supports multiple libraries.  The number of libraries that can be installed on one computer is limited by the computer's available resources and system performance..


Quick Initialization

After the installation is complete and ARCserve's Tape Engine is started for the first time, the entire library is inventoried.  For all subsequent starts, the normal inventory process can be skipped by enabling the Library Quick Initialization feature either during installation or through Library Setup.  The Library Quick Initialization feature assumes that no media has been moved, added, removed, or swapped since the last shutdown.  If media has been moved, added, removed, or swapped, you should either manually inventory the entire library or the specific slots whose status has changed.

When the Library Quick Initialization feature is disabled, the entire library is inventoried the next time ARCserve is started.


Concurrent drive initialization

Use the ARCserve Device Manager to track the initialization process before the library is completely initialized.  For multiple drive libraries, the Tape Engine uses all of the drives for the initialization process.


Device management functions

ARCserve supports the following library device management functions:

Format Slot Range

Erase Slot Range (Both Quick and Long)

Eject Media from a library drive and return it to its home slot for removal

Inventory Slots   Includes a Quick Inventory option for libraries supporting barcode recognition

Mount Magazine

Dismount Magazine

Clean Library Drive (for Tape Library Option only)


Grouping by slots

Library groups employ the same concept as device groups, however, library groups are based upon slots.  Any of the slots inside a library can be selected to form a library group.  This makes it possible for one-drive libraries to have more than one library group.  For example, slots can be configured into groups according to tasks or departments.  For more information on library groups, see the Configuring Library Groups section.

Note:  To optimize your backups, you should plan your library groups in advance.


Single-step library group spanning

ARCserve supports single-step group spanning, also known as the open door condition.  This feature allows you to insert new media into a library group and then continue the backup or restore operation without first executing any Device Management commands.  To insert new media into a library, you must open the door of the library.  Although the Tape Engine does not automatically inventory the library when the library door is opened and closed, it does inventory the slots in the library group, specifically when you are prompted to insert media to complete the backup job.

Note:  If your library has multiple drives, do not attempt media spanning unless you are sure that no additional jobs are being submitted to the same group on a separate drive.


Continuous operation with a defective drive

If a drive in a multiple drive library becomes defective, it can be marked as offline.  This enables the Tape Engine to continue to operate using the remaining non-defective drives in the library.


Using Device Manager with Libraries

The Device Manager is used for all storage device operations, including library slot monitoring and maintenance operations.  The Device Manager is shown below.  Each device option is discussed in more detail throughout the rest of this section.


Related Topics

  Device Manager Basics

  Access the Device Manager


Viewing Information

Using the Device Manager you can view a variety of information about the media you use, as well as the libraries and drives connected to your system.


Related Topics

  Adapter Cards

  Libraries

  Library drives

  Media


Viewing Information about Library Drives

When you highlight a library drive, you can see two types of information:  summary and detail.

Since a library drive is considered an integral part of the library, and a library is slot-based as opposed to device-based, the Eject option is the only option available when a library drive is highlighted.  Therefore, the only operation you can perform when a library drive is highlighted is ejecting media from the library drive so that it can be returned to its home slot for removal.

Summary information

Selecting the Summary tab displays general information about the library drive, such as its vendor, product name, firmware version, and SCSI compliance.

Detailed information

Selecting the Detail tab displays detailed information about the library drive, such as its group name, cartridge type, format code, compression, block size, and device status.

The Media Information panel indicates which media is currently located in the library drive.


Related Topics

  View Summary or Detail Information for a Library Drive


Viewing Information about Media

When you highlight a slot, you can see two types of information about the media in the selected slot:  summary and detail.

Summary information

Selecting the Summary tab displays general information about the media in the selected slot, such as the media name, sequence number, ID, and whether or not it is write protected.  Media characteristics are also displayed.

Detailed information about media in a slot

Selecting the Detail tab displays detailed information about the media in the slot, such as the expiration date, first format date, last format date, and the number of times formatted.  Media usage and error count information is also displayed.

Note:  In the Error Count panel, a soft error means that the drive detected a problem when it was trying to read from/write to the media but was able to correct the problem by retrying the operation (or, in the case of a read, correcting the data through the use of its Error Correction Code).  Use these fields to determine the "quality" of your media.  Remember, it is normal for a drive to always generate a certain number of soft read/write errors.  However, you should be concerned if the number of errors is very high in relation to the amount of data being read/written.


Related Topics

  View Summary or Detail Information for Media in a Slot


Library Device Management Functions

Using ARCserve's Device Manager, you can perform the following functions:

Format Slot Range

Erase Slot Range (Both Quick and Long)

Eject media from a library drive and return it to its home slot for removal

Inventory  Slots

Mount Magazine

Dismount Magazine

Clean Library Drive (for Tape Library Option only)

Import/Export

Configuring Library Groups

Note:  These functions are library-specific, and are enabled after the Library Option is installed.

The Library Option is slot based, not device based.  When you insert media into a magazine slot or remove media from a slot, you must either inventory this slot or remount the magazine.  Always insert media into slots, never into library drives.


Formatting Media

Format your media before you use them

Although ARCserve automatically formats blank media, you can use this function to manually format media.  Formatting writes a new label at the beginning of the media, effectively destroying all existing data on the media.

Low level formatting is not required for ARCserve supported drives.

Optical media do not require formatting.  If the format option is used for optical media, the media is erased and all files are deleted.

Note:  Use this feature with care!  Once you format media, the data it contained (if any), and any job sessions associated with this media, cannot be retrieved.


Related Topics

  Format Media


Expiration date

The expiration date tracks how long a media should be in service.  A media's life is generally based on "passes".  A pass is defined as the drive head "passing" over a given point on the media.  For example, a backup without verification constitutes one pass, whereas a backup with verification constitutes two passes.

Manufacturers rate their media's useful live from about 500 to 1500 passes.  This does not mean that the media is unusable after it reaches the maximum number, just that it is more susceptible to errors at this point.

You should choose an expiration date based on how you will use the media.  If you plan to use the media often, say, a few times a week, you should set the expiration date to a year from now, maybe even sooner than that.  On the other hand, if you plan to use the media only once or twice a month, you can set the expiration date to two or three years from the current date.

When media reaches its expiration date, you will still be able to use it, but when you make a backup, for example, a note is made in the Activity Log that this media is expired.

The expiration date is a way of tracking how long media has been in service so you can stop using it before it reaches the end of its useful life.

Note:  If you are formatting new, blank media, the default expiration date will be one year from the current date.  If you are reformatting media, the expiration date that appears will be the date you specified the first time the media was formatted.


Erasing Media

Use this function to erase all data from a single media or from multiple media.  ARCserve also erases all references to the contents of this media (if any) from the database.  When and if you re-format this media, its physical history (read and write passes, etc.) will be carried over.

Note:  Use this feature with care!  Once you erase data on media, the data cannot be retrieved.


Related Topics

  Format Media

  There are three erase options from which you can choose: Quick Erase , Quick Erase Plus and Long Erase.

  Erase Media


Quick Erase

A Quick Erase is an operation that ARCserve uses to cause a tape to become effectively erased.  It avoids the time a Long Erase would take (minutes to hours), by overwriting the media label.  The history of the media is still available to ARCserve for tracking purposes.


Long Erase

A Long Erase completely removes all data from a media.  It takes much longer than a Quick Erase, but the media is literally blank.  For security reasons, if you want to make sure that the data on a media is erased completely, use Long Erase.  (For optical media, the Long Erase option is the equivalent of formatting the optical platter).


Ejecting Media from a Library Drive

Use this function to eject media from a library drive and return it to its home slot.  A home slot is the slot with which it became associated during the inventory process.

Note:  Since a library drive is considered an integral part of the library, and a library is slot-based as opposed to device-based, the Eject option is the only option available when a library drive is highlighted.


Related Topics

  Eject Media from your Drives


Inventorying Slots

This option checks library slots to see if they are occupied, reads the media headers of any media it finds, then associates the media header of each media with the slot in which it was found.  The slot in which each media was found is its home slot.  Therefore, you should use this option to inform the Tape Engine of any alterations made to the media in the library (media added or removed from a magazine or moved to a different slot).

Note:  You should only add and remove media when the Tape Engine is running so you can immediately inventory your slots.


Related Topics

  Inventory your Slots


Barcodes

The barcode feature allows the library to quickly recognize and differentiate one media from the next.  Barcode recognition is a library-specific feature.  Each media comes, from its manufacturer, with a barcode label affixed to the outer edge of the media cartridge.  This label has a predefined serial number in numerals using barcodes.

Each media you load into the storage drives, in the libraries, must have a unique serial barcode number.  If you happen to purchase two media with the same serial number, put one of the duplicates aside for another backup session.  ARCserve will automatically detect if the library supports barcode and enable the barcode support check box in the Properties window of Device Configuration.


Mounting/Dismounting a Magazine

Use this function to load or remove a magazine from the library.  Mounting a magazine initiates an inventory of the slots in the magazine.  Dismounting a magazine returns all media to their home slots and prepares the magazine for removal.  The time this process takes will vary according to the number of media in the magazine you are mounting or dismounting.

Note:  Magazines must be mounted for library operations to commence.  Magazines should be dismounted before you physically remove them.


Related Topics

  Mount or Dismount a Magazine


Cleaning Tape Drive Heads (Tape Library Option only)

Use this option to clean the heads of any drive in your library.  You must have a cleaning tape installed in the tape cleaning slot you specified during setup to utilize this option.


Related Topics

  Clean Library Drive Heads


Configuring Library Groups

ARCserve uses the concept of "groups"

ARCserve allows you to separate the slots in your library into "groups".  Grouping slots allows you to take advantage of parallel streaming.  Additionally, if you have several slots in a group, you can also take advantage of "automated" media spanning.

By default, the first time ARCserve's Tape Engine is started, all of the slots in each library that you have attached to your machine are automatically assigned to a library group.  For example, if you have two libraries attached to your machine, you will have two library groups.  All of the slots in the first library will be assigned to GROUP0, and all of the slots in the second library will be assigned to GROUP1.  You can keep these library group names, or, you can regroup and rename them.  Since each slot in a library is viewed as a virtual storage drive, each slot can be assigned its own group.

Note:  If you are using a standalone drive in addition to your library, the standalone drive is not automatically assigned to a group.  It must be assigned to a group manually.  A standalone drive cannot be assigned to any library group.  You cannot assign slots in different libraries to the same group.


Related Topics

You can use the Device Manager to:

  Create a New group

  Assign a Slot to a Group

  Remove a Slot from a Group

  Delete or Rename a Group


Backing Up Data to a Library

Since backup and restore do not distinguish between a library group and a regular device group, you can submit backup jobs to library media from ARCserve's Backup Manager in the same manner that you submit backup jobs to a standalone storage drive.

For more information on how to perform a backup using ARCserve , see the Backup basics section.

Note:  Right-clicking a media name permits you to access all of the Device Management functions without returning to the Device Manager.  Use this feature to change group assignments, format and erase media, or perform any other Device Management function.


Related Topics

  Multiple, concurrent group access

  Backup's Eject feature

  Single-step spanning

  Adding media during single-step spanning

Examples of single-step spanning:

  Adding media to an empty slot in a magazine during media spanning

  Adding a magazine with additional media during media spanning

  Swapping media that is full for new media during media spanning


Backup's Eject feature

Backup's Eject feature, accessed through the Operation tab under Options, operates differently with a library.  Instead of simply ejecting media from a drive, it ejects media from a library drive and returns it to its home slot for removal.


Restoring Data from a Library

Since backup and restore do not distinguish between a library group and a regular device group, you can submit restore jobs from ARCserve's Restore Manager in the same manner that you submit restore jobs from a standalone storage drive.

Therefore, performing a restore job using the Library Option is essentially the same as performing a regular restore job using a standalone drive.

For more information on how to perform a restore job using ARCserve , see the Restore basics section.


Related Topics

  Multiple, concurrent group access

  Single-step spanning

  Adding media during spanning

Example of single-step spanning:

  Adding media to an empty slot in a magazine during media spanning


Troubleshooting

In this section, you will learn about:

Installation/Setup troubleshooting

Initialization troubleshooting

Tape Engine troubleshooting

Device Management troubleshooting

Backup troubleshooting

Note:  For information on error messages related to libraries, see the Library error messages section.

Some of the problems that you might encounter will be hardware related.  Three important points to consider when tracking down hardware problems are:

Make sure your hardware is functional.  This includes the host adapter card, the cables, the library, and the drive.  If you can, test your hardware by connecting it to a system that you know works.

Make sure the hardware is configured properly.  This includes setting the proper switches on the controller card (according to the manufacturer's instructions) and making sure the SCSI bus is terminated properly at both ends.

For multi-drive libraries, make sure the library drives are assigned in the correct order.


Installation/Setup

Click on any of the following problems to see possible solutions:

I ran the Library Setup, but ARCserve cannot find the library

The Library Option failed to install

The Library Option complains that there is not enough disk space

Library Setup complains that it is unable to copy certain files


Example

HKEY_LOCAL_MACHINE

HARDWARE

DEVICEMAP

SCSI

SCSI PORT 0

SCSI Bus 0

Target ID 0

Logical Unit ID 0

Identifier: REG_SZ: CHANGER DRIVE

Type : REG_SZ : TapePeripheral

Target ID 1

Logical Unit ID 0

Identifier: REG_SZ: CHANGER

Type:REG_SZ: MediumLibraryPeripheral

Click here to return to the troubleshooting window.


The Library Option failed to install.

Make sure you installed ARCserve first.

If you still have difficulty installing, reinstall ARCserve and then reinstall the Library Option.


The Library Option complains that there is not enough disk space.

Make sure you selected the correct drive and directory.

Make sure there is enough space.


Library Setup complains that it is unable to copy certain files.

Make sure there are no components of ARCserve that are open.

ARCserve may require you to update certain files that are used by other components of ARCserve.  ARCserve will shut down any Service that is running, but it will not be able to close any of the Managers.  Therefore, you must make sure you do not have any ARCserve Managers open while you are setting up the Library Option.


Initialization

Click on any of the following problems to see possible solutions:

After setup my library is not initializing correctly. -OR- The library is not reading in the media. -OR- The library is jamming the media into the library drive or not picking up the media from the library drive.

After the library is initialized, all of the library slots indicate "Dismounted".

I have enabled the Quick Initialization feature and ARCserve is displaying the wrong information for the slots.

The Quick Initialization Option is enabled but the library still reads all the media during initialization.


After setup my library is not initializing correctly. -OR- The library is not reading in the media. -OR- The library is jamming
After setup my library is not initializing correctly. -OR- The library is not reading in the media. -OR- The library is jamming the media into the library drive or not picking up the media from the library drive.

The library may not have a drive assigned.  Run Library Setup and make sure that a library drive is attached to your library.

If you have a multi-drive library, you may not have assigned the drives in the correct order.  Run Library Setup to make sure you have assigned your library drives in the correct order.  Refer to the documentation supplied with your library for more information.

This may be a hardware problem.


After the library is initialized, all of the library slots indicate "Dismounted".

Check to see if the library door is open.  Check the ARCserve activity log for any error message.

The library may be full.  The maximum number of media that a library can hold is equal to the number of library slots.  If the library magazine is completely filled with media, make sure that the library drive(s) does not contain media.

This may be a hardware problem.


I have enabled the Quick Initialization feature and ARCserve is displaying the wrong information for the slots.

Quick Initialization requires user awareness.  If you often have the need to swap media after shutting down the Tape Engine, you should consider leaving this feature disabled.  This feature presumes that the user will inventory the library's slots or remount the magazine after any modification to the slots.


The Quick Initialization Option is enabled but the library still reads all the media during initialization.

The library has not been successfully initialized.  Quick Initialization is activated only after a successful initialization of the library.

The library's hardware configuration has been changed.  After any change in the library's hardware configuration, Quick Initialization is disabled until another successful initialization.

The CHANGER.CFG file is deleted or overwritten.  CHANGER.CFG contains information that is used by Quick Initialization, so if it is deleted or overwritten, Quick Initialization is disabled.


Tape Engine

Click on any of the following problems to see possible solutions:

I cannot see the media I just added to the library. -OR- I still see the media that I just removed from the library. -OR- I move media to another slot but ARCserve still shows the media as being in the original slot.

A home slot is changed.

After cleaning a library drive, the cleaning media is not returned to its home slot immediately.

ARCserve indicates that it does not have a free slot to return media to from a library drive.

The Tape Engine times out.


I cannot see the media I just added to the library. -OR- I still see the media that I just removed from the library. -OR- I mov
I cannot see the media I just added to the library. -OR- I still see the media that I just removed from the library. -OR- I move media to another slot but ARCserve still shows the media as being in the original slot.

When media are manually added, removed, or moved, the user must inventory the slots or mount the library magazine to update ARCserve.


A home slot is changed.

Media is in a library drive and another media is placed in the first home slot.  Be careful not to insert media into the home slot of another media.  When ARCserve detects that the home slot of media is occupied by another media, it moves the media to the first available non-cleaning slot.

Media is in a library drive and CHANGER.CFG file is deleted or overwritten.  CHANGER.CFG contains information about media's home slot, so that if at startup media is in a library drive, it is returned to the proper home slot.


After cleaning a library drive, the cleaning media is not returned to its home slot immediately.

The cleaning cartridge may be completely used.  If the cleaning cartridge is ejected out of the library drive only after a few seconds, you should check whether or not the cleaning cartridge is completely used.  If the library drive does not support reporting of media cleaning, the cleaning media is returned to its home slot after about two minutes.  If the library drive supports the reporting of media cleaning, the cleaning media is returned to its home slot immediately after cleaning.


ARCserve indicates that it does not have a free slot to return media to from a library drive.

Another media is in the home slot and there is not an available free slot.  If you see an empty slot, this slot is probably assigned as a cleaning slot.


The Tape Engine times out.

Make sure that your library is turned on.

See if the library unit is moving when the initialization takes place.

Reboot the library and machine.


Device Management

Click on the following problem to see a possible solution:

ARCserve indicates "Media MisCompare" Error for Format or Erase


ARCserve indicates "Media MisCompare" Error for Format or Erase.

The media read does not match the media shown by ARCserve.  ARCserve does not erase or format media unless it matches what is shown.  This error occurs when media is changed manually and not inventoried to update ARCserve.  When media is manually added, removed, or moved, the user must inventory the slots or mount the library magazine to update ARCserve.


Backup

Click on any of the following problems to see possible solutions:

When I am running one job, I am unable to submit another job.

A backup or restore job causes the library to automatically inventory slots after I manually add additional media.

While spanning two groups in the same multi-drive library, only one job inventories its slot group and continues after the media is replaced in both the groups.


When I am running one job, I am unable to submit another job.

If you are trying to run a Run-Now job, try scheduling the job instead.  ARCserve is able to run a job when there is a free library drive.

Only one activity can occur in a group at a time.  Therefore, you cannot run two jobs using the same group at the same time.


A backup or restore job causes the library to automatically inventory slots after I manually add additional media.

After ARCserve prompts you to manually insert additional media to complete a backup/restore job, ARCserve automatically inventories the media in the particular backup/ restore group.  After the inventory of the particular group is completed, the job will then continue.


While spanning two groups in the same multi-drive library, only one job inventories its slot group and continues after the medi
While spanning two groups in the same multi-drive library, only one job inventories its slot group and continues after the media is replaced in both the groups.

The solution is to wait until the first job is completed and then open and close the library and then direct the second job to continue.


Definitions

This sections contains definitions necessary to understand the ARCserve Library Option.

Concurrent Drive Initialization - The process where two or more library drives work in parallel to read in the media in the library.

Dismount - Prepares the selected library magazine for removal.  All media in the selected library magazine are marked as "Dismounted".  Further operations with media within the magazine are disabled.

Group - Consists of storage device(s), or library slot(s).

Home Slot, Original Slot - The slot where media was originally placed.

Inventory - Instructs the library to update the actual status of the selected slots.  If media is present in a slot, it is read.

Library, JukeBox - These terms are used to describe a device comprised of a library unit and library drive.  In this help file the device is referred to as "library".

Library Drive - A drive that is located within the library.  This drive works as part of the library.

Library Group - A group consisting of library slots, rather than storage devices.

Magazine - A removable container in the library for holding a set of media.

Mount - Prepares the selected library magazine for use by ARCserve.  All of the slots in the magazine are checked for media, and all of the media found are read.

Picker - The component of the library that moves the media in and out of the slots and library drive.  Also known as 'arm'.

Quick Initialization - This feature assumes that no media has been moved, added, removed, or swapped since the last shutdown.  If media has been moved, added, removed, or swapped, you should either manually inventory the entire library, or the specific slots whose status has changed.  When the Library Quick Initialization feature is disabled, the entire library is inventoried the next time ARCserve is started.

Slot - Also known as Library Slot.  A compartment in the magazine for storing media.

Tape Engine - One of the three components of the ARCserve Servers.  Tape Engine is a service that controls storage devices as well as libraries.  The Library Option runs as part of this service.


Barcode labeling

Barcode labeling allows ARCserve to quickly identify individual media by reading barcode labels which can be affixed to the media.


Multiple, concurrent group access (for Tape Library Option only)

ARCserve takes advantage of all available drives when assigning jobs. If a library has more than one physical drive, the additional drives are used to assign new jobs to the same or a different group.  For example, if a library has two drives, and Drive 1 is being used to process a job for GROUP_1, a second job for GROUP_1 can be processed simultaneously by Drive 2.

Note:  Do not attempt media spanning unless you are sure that no additional jobs are being submitted to the same group on a separate drive.


Quick Erase Plus

Same as Quick Erase, but also erases the Barcode/serial number if this feature is enabled.  (For more information on Barcode/serial number cataloging refer to the 'Inventorying slots' section in this chapter.)  The media is no longer traceable by ARCserve and information such as the expiration date is no longer carried forward.


Multiple, concurrent group access

(For Tape Library Option only)

For libraries with multiple storage drives, the Tape Library Option takes maximum advantage of all available drives.  When a job is submitted, or a device management option is selected, ARCserve checks for available drives in the library.  If a drive is available, the job or device management feature is performed.

You can submit additional jobs to the same group or different group.  If a job is being performed for a group, GROUP0 for example, ARCserve will begin additional backup or restore jobs for the group as long as additional drives are available.


Configuring device groups

ARCserve uses "device groups"

ARCserve provides the concept of "device groups".  ARCserve allows you to separate your storage devices into groups.  Grouping devices allows you to take advantage of parallel streaming.  And, if you have several devices in a group, you can also take advantage of "automated" media spanning.

One rule for grouping multiple devices in a group

Note:  If you want to have several devices in a group, each device in the group must be the same make and model.

When ARCserve's Tape Engine is started, each storage device that you have is automatically placed in a device group.  Identical drives are grouped together and differing drives are separated into different groups.  For example, if you have five drives attached to your machine, three of which are identical, you will have three groups:  GROUP0, GROUP1, and GROUP2.  The three identical drives will be in one group and the remaining two, since they are different from all others, are each placed in their own individual group.

Since ARCserve automatically groups your storage devices, you can keep these device group names or you can regroup and rename them.  After you start ARCserve, you can use the Device Manager and the instructions in the following sections to:


Related Topics

  Create a new device group

  Assign a device to a device group

  Remove a storage device from a device group

  Rename a device group


Removable drive support

ARCserve supports SCSI removable devices allowing you to back up data, restore data, scan sessions, merge removable sessions, and manage removable media on your removable devices.  The ARCserve Manager identifies and treats the removable media as tape media.

Note:  For the most up-to-date list of certified devices, go to the Computer Associates web site:

http://www.cai.com/

Before you can back up to removable media, you must:

Enable your removable device

Format your removable storage media

Configure removable device groups

Note:  You cannot turn on a removable device after Windows NT boots up because no drive letter is assigned to the removable device.

For removable drive support to function properly, you must use Service Pack 4 or greater for Windows NT 3.51 and Service Pack 2 or greater for Windows NT 4.0.


Formatting Removable Media

After your device is recognized by ARCserve, you must format your removable storage media as an ARCserve storage media.  In ARCserve's graphical user interface, removable media is represented as if it were tape media.  This is not an error.  ARCserve treats removable media in the same manner as tape media.

Note:  Before formatting removable media, you must partition the media using the Windows NT WINDISK.EXE utility.


Related Topics

  Format your Removable Media


Erasing Removable Storage Media

You may need to reuse or regroup your removable media.  You can use the Erase Utility for Removable drives to do the following:

Quick Erase - deletes the media label

Quick Erase Plus - destroys the media label and serial number

Long Erase Plus - destroys all data and formats the removable media in FAT or NTFS

Note:  Formatting and erasing the removable media will delete the sessions on the media, not the user data.


Related Topics

  Erase Removable Media


Device Group Configuration for Removable Devices

You configure removable device groups through ARCserve's Device Management window.  Creating or deleting new removable device groups, renaming removable device groups, and assigning or removing individual devices are done easily with ARCserve.


Related Topics

  Create Removable Device Groups and Assign Removable Devices to them


Find Media or Slot

This feature allows you to search for

a media name

a slot number

You are prompted to enter the media name, slot number, or other special options.  These special options allow finding a media that has a certain status (i.e. media is empty, blank, off-line or a cleaning tape).


Big Library Support

For a large library, with more than 1000 slots (refer to Release Notes to change this value ), the slots will be shown as an opened folder.  When this folder is selected, the slots will be shown on the right panel.  Slots can be displayed in four ways: large icons, small icons, details and list.


All Error Messages

Choose one of the following topics for an explanation of an error message and a possible solution:

UNIX Error Messages	(#'s 1000-1138)
Job Engine Error Messages	(#'s 1001-1309)
Job Runner Error Messages	(#'s 2001-2203)
Tasks Engines Error Messages	(#'s 3001-3998)
Database API Error Messages	(#'s 4001-4216)
Database Engine Error Messages	(#'s 5001-5210)
RAID Option Error Messages	(#'s 6600-6623)
Tape Engine Error Messages	(#'s 6000-6999)
Message Engine Error Messages	(#'s 7001-7238)
Changer Library Error Messages	(#'s 8000-8028)
Database Backup Agents Error Messages	(#'s 8501-8622)
Miscellaneous Error Messages	(#'s 9001-9004)
UNIX Agent Error Messages	(#'s 9030-9133)
MBO Error Messages	(#'s 9600-9999)
Image Option Error Messages	(#'s 11000-11055)
Serverless Backup Option Error Messages	(#s 11104-11107)
License Violation Error	(# 12002)

Return Codes:

Database Error Codes (db_error_code)

Queue Error Codes (queue_error_code)


Database Error Codes (db_error_code)

2	Record not found.

3	Duplicate key.  You attempted to create or modify a record that would have resulted in a duplicate of a unique key value.

-900	Disk space falls below minimum requirement.

-2008	NCP internal error.  An internal error occurred within the NCP.

-2009	The session disconnected.  This generally indicates some kind of network error. Be sure that the network is still alive.  Then try your application again.

-2013	This indicates that you attempted to log in to the server too many times and ran out of sessions.  Increase the maximum session limit using rdsadm.exe.


Queue Error Codes (queue_error_code)

11	Invalid queue.

12	Open failed.

13	Read failed.

14	Write failed.

15	Memory allocation failed.

18	Invalid queue job.

19	Create failed.

20	Invalid owner.

200	Invalid queue job type.

201	Invalid queue job signature.

202	Maximum jobs reached.


If your error suggests a media problem

1.	Use a cleaning cartridge/media to clean your storage device(s).

2.	Try a new media.

Maybe the media is bad and you just need to use a new one.

Always remember to use only the types of media recommended by the drive manufacturer.  Never use video tape.  These media have been shown to be unreliable for data.


If your error suggests a hardware problem

1.	Power the drive off, then on.

Turning the drive off, then on again may correct the problem.

2.	Check the terminators on the SCSI bus.

Are both ends of the SCSI bus terminated?

3.	Check the cables.

Do you have any loose connections?

4.	Make sure the controller board is properly seated.

You may have to re-seat the controller board.

5.	Try a different media.

The media may be the problem.  A new one should let you know.

6.	Call the vendor of your storage device.

7.	As a last resort, power down the entire machine, and power back up.

If the controller card was locked, only completely shutting off the computer will unlock it.  Do not warm boot.


Job Engine Error Messages

Error 1001	Error 1002	Error 1003	Error 1004
Error 1005	Error 1006	Error 1007	Error 1008
Error 1009	Error 1010	Error 1201	Error 1202
Error 1203	Error 1204	Error 1205	Error 1206
Error 1207	Error 1208	Error 1209	Error 1210
Error 1301	Error 1302	Error 1303	Error 1304
Error 1305	Error 1306	Error 1307	Error 1308
Error 1309


Job Runner Error Messages

Error 2001	Error 2002	Error 2003	Error 2004
Error 2005	Error 2006	Error 2007	Error 2008
Error 2009	Error 2101	Error 2102	Error 2103
Error 2104	Error 2105	Error 2106	Error 2107
Error 2111	Error 2112	Error 2113	Error 2114
Error 2115	Error 2116	Error 2117	Error 2121
Error 2122	Error 2131	Error 2132	Error 2133
Error 2201	Error 2202	Error 2203


Tasks Engines Error Messages

Error 3001	Error 3002	Error 3003	Error 3004
Error 3005	Error 3011	Error 3012	Error 3013
Error 3014	Error 3021	Error 3022	Error 3023
Error 3024	Error 3025	Error 3026	Error 3027
Error 3028	Error 3032	Error 3051	Error 3061
Error 3062	Error 3063	Error 3064	Error 3065
Error 3066	Error 3071	Error 3072	Error 3073
Error 3081	Error 3082	Error 3083	Error 3084
Error 3085	-	-	-
Error 3101	Error 3102	Error 3103	Error 3104
Error 3105	Error 3115	Error 3139	Error 3155
Error 3156	Error 3157	Error 3158	Error 3159
Error 3160	Error 3161	Error 3162	Error 3164
Error 3165	Error 3166	Error3167	Error 3168
Error 3169	Error 3170	Error 3171	Error 3172
Error 3173	Error 3174	Error 3179	Error 3180
Error 3182	Error 3183	-	Error 3201
Error 3202	Error 3203	Error 3204	Error 3205
Error 3203	Error 3204	Error 3205	Error 3301
Error 3204	Error 3205	Error 3250	Error 3251
Error 3252	Error 3253	Error 3254	Error 3255
-	Error 3260	Error 3262	Error 3263
Error 3270	Error 3271	Error 3301	Error 3302
Error 3303	Error 3304	Error 3311	Error 3312
Error 3313	Error 3314	Error 3315	Error 3316
Error 3321	Error 3330	Error 3331	Error 3401
Error 3401	Error 3402	Error 3403	Error 3404
Error 3404	Error 3405	Error 3406	Error 3407
Error 3408	Error 3409	Error 3411	Error 3412
Error 3413	Error 3414	Error 3415	Error 3416
Error 3421	Error 3422	Error 3423	Error 3424
Error 3425	Error 3426	Error 3431	Error 3432
Error 3441	Error 3442	Error 3451	Error 3452
Error 3453	Error 3501	Error 3502	Error 3503
Error 3504	Error 3511	Error 3512	Error 3521
Error 3522	Error 3530	Error 3531	Error 3532
Error 3533	Error 3534	Error 3535	Error 3536
Error 3537	Error 3538	Error 3539	Error 3540
Error 3541	Error 3542	Error 3543	Error 3544
Error 3545	Error 3701	Error 3702	Error 3703
Error 3704	Error 3705	Error 3711	Error 3712
Error 3713	Error 3714	Error 3715	Error 3716
Error 3717	Error 3801	Error 3802	Error 3803
Error 3811	Error 3812	Error 3813	Error 3814
Error 3815	Error 3816	Error 3821	Error 3822
Error 3823	Error 3824	Error 3825	Error 3826
Error 3827	Error 3828	Error 3831	Error 3832
Error 3833	Error 3841	Error 3842	Error 3851
Error 3852	Error 3853	Error 3854	Error 3855
Error 3856	Error 3860	Error 3861	Error 3862
Error 3863	Error 3864	Error 3871	Error 3881
Error 3882	Error 3883	Error 3884	Error 3901
Error 3902	Error 3903	Error 3904	Error 3905
Error 3906	Error 3921	Error 3931	Error 3932
Error 3921	Error 3931	Error 3932	Error 3933
Error 3934	Error 3935	Error 3936	Error 3941
Error 3942	Error 3951	Error 3952	Error 3961
Error 3962	Error 3963	Error 3964	Error 3965
Error 3971	Error 3972	Error 3973	Error 3974
Error 3975	Error 3977	Error 3978	Error 3979
Error 3983	Error 3986	Error 3987	Error 3988
Error 3989	Error 3990	Error 3991	Error 3992
Error 3993	Error 3994	Error 3995	Error 3996
Error 3997	Error 3998


Database API Error Messages

Error 4001	Error 4002	Error 4003	Error 4004
Error 4005	Error 4006	Error 4007	Error 4008
Error 4009	Error 4010	Error 4101	Error 4102
Error 4103	Error 4104	Error 4105	Error 4106
Error 4107	Error 4108	Error 4109	Error 4110
Error 4111	Error 4112	Error 4113	Error 4114
Error 4115	Error 4116	Error 4117	Error 4208
Error 4209	Error 4210	Error 4211	Error 4212
Error 4215	Error 4216	Error 4222


Database Engine Error Messages

Error 5001	Error 5002	Error 5003	Error 5004
Error 5005	Error 5006	Error 5007	Error 5008
Error 5009	Error 5201	Error 5202	Error 5203
Error 5204	Error 5205	Error 5206	Error 5207
Error 5208	Error 5209	Error 5210


Tape Engine Error Messages

Error 6000	Error 6001	Error 6002	Error 6003
Error 6004	Error 6005	Error 6006	Error 6007
Error 6008	Error 6009	Error 6010	Error 6011
Error 6012	Error 6013	Error 6014	Error 6015
Error 6016	Error 6017	Error 6018	Error 6019
Error 6020	Error 6021	Error 6022	Error 6023
Error 6024	Error 6025	Error 6026	Error 6027
Error 6028	Error 6029	Error 6030	Error 6031
Error 6032	Error 6033	Error 6034	Error 6035
Error 6036	Error 6037	Error 6038	Error 6039
Error 6040	Error 6041	Error 6042	Error 6043
Error 6044	Error 6045	Error 6046	Error 6047
Error 6048	Error 6049	Error 6050	Error 6051
Error 6052	Error 6053	Error 6054	Error 6055
Error 6056	Error 6057	Error 6058	Error 6059
Error 6060	Error 6061	Error 6062	Error 6063
Error 6064	Error 6065	Error 6066	Error 6067
Error 6068	Error 6069	Error 6070	Error 6071
Error 6072	Error 6073	Error 6074	Error 6075
Error 6076	Error 6077	Error 6078	Error 6079
Error 6080	Error 6081	Error 6082	Error 6083
Error 6084	Error 6085	Error 6086	Error 6087
Error 6088	Error 6089	Error 6090	Error 6091
Error 6092	Error 6093	Error 6094	Error 6095
Error 6096	Error 6097	Error 6098	Error 6099
Error 6100	Error 6101	Error 6102	Error 6103
Error 6104	Error 6105	Error 6106	Error 6107
Error 6108	Error 6109	Error 6300	Error 6301
Error 6302	Error 6303	Error 6304	Error 6305
Error 6306	Error 6330	Error 6331	Error 6332
Error 6333	Error 6401	Error 6402	Error 6500
Error 6501	Error 6502	Error 6503	Error 6504
Error 6505	Error 6506	Error 6614	Error 6615
Error 6616	Error 6617	Error 6620	Error 6624
Error 6625	Error 6626	Error 6627	Error 6628
Error 6629	Error 6630	Error 6631	Error 6632
Error 6633	Error 6634	Error 6635	Error 6636
Error 6637	Error 6638	Error 6900	Error 6901
Error 6902	Error 6903	Error 6904	Error 6905
Error 6906	Error 6907	Error 6908	Error 6909
Error 6910	Error 6911	Error 6912	Error 6913
Error 6914	Error 6915	Error 6916	Error 6917
Error 6918	Error 6919	Error 6920	Error 6921
Error 6922	Error 6923	Error 6924	Error 6925
Error 6965	Error 6995	Error 6996	Error 6997
Error 6998	Error 6999


Message Engine Error Messages

Error 7001	Error 7002	Error 7003	Error 7004
Error 7005	Error 7006	Error 7007	Error 7008
Error 7009	Error 7201	Error 7202	Error 7203
Error 7204	Error 7205	Error 7206	Error 7207
Error 7208	Error 7209	Error 7210	Error 7211
Error 7212	Error 7213	Error 7214	Error 7215
Error 7216	Error 7217	Error 7218	Error 7219
Error 7220	Error 7221	Error 7222	Error 7223
Error 7224	Error 7225	Error 7226	Error 7227
Error 7228	Error 7229	Error 7230	Error 7231
Error 7232	Error 7237	Error 7238


Changer Library Error Messages

Error 8000	Error 8002	Error 8003	Error 8004
Error 8006	Error 8007	Error 8008	Error 8009
Error 8010	Error 8011	Error 8012	Error 8013
Error 8014	Error 8015	Error 8016	Error 8020
Error 8021	Error 8022	Error 8023	Error 8024
Error 8025	Error 8026	Error 8027	Error 8028


Database Backup Agents Error Messages

Error 8501	Error 8502	Error 8511	Error 8512
Error 8521	Error 8522	Error 8523	Error 8524
Error 8525	Error 8531	Error 8532	Error 8533
Error 8601	Error 8602	Error 8603	Error 8604
Error 8605	Error 8606	Error 8607	Error 8608
Error 8609	Error 8610	Error 8611	Error 8612
Error 8613	Error 8617	Error 8618	Error 8619
Error 8621	Error 8622


Miscellaneous Error Messages

Error 9001	Error 9002	Error 9003	Error 9004
Error 9033	Error 9035	Error 9120


Image Option Error Messages

Error 11000	Error 11001	Error 11002	Error 11003
Error 11004	Error 11005	Error 11006	Error 11007
Error 11008	Error 11009	Error 11010	Error 11011
Error 11012	Error 11013	Error 11014	Error 11015
Error 11016	Error 11017	Error 11018	Error 11019
Error 11020	Error 11021	Error 11023	Error 11024
Error 11025	Error 11026	Error 11027	Error 11028
Error 11029	Error 11030	Error 11031	Error 11032
Error 11033	Error 11034	Error 11042	Error 11045
Error 11046	Error 11047	Error 11048	Error 11049
Error 11050	Error 11051	Error 11052	Error 11053
Error 11054	Error 11055


Serverless Backup Option Error Messages

Error 11104	Error 11105	Error 11106	Error 11107


RAID Option Error Messages

Error 6600	Error 6601	Error 6602	Error 6603
Error 6604	Error 6605	Error 6606	Error 6608
Error 6609	Error 6610	Error 6620	Error 6621
Error 6622	Error 6623


MBO Error Messages

MBO Error 9600

MBO Error 9601

MBO Error 9603

MBO Error 9604

MBO Error 9605

MBO Error 9606

MBO Error 9607

MBO Error 9608

MBO Error 9609

MBO Error 9610

MBO Error 9611

MBO Error 9612

MBO Error 9614

MBO Error 9615

MBO Error 9616

MBO Error 9617

MBO Error 9618

MBO Error 9619

MBO Error 9620

MBO Error 9621

MBO Error 9622

MBO Error 9623

MBO Error 9624

MBO Error 9625

MBO Error 9626

MBO Error 9627

MBO Error 9628

MBO Error 9629

MBO Error 9630

MBO Error 9631

MBO Error 9632

MBO Error 9633

MBO Error 9634

MBO Error 9636

MBO Error 9637

MBO Error 9638

MBO Error 9639

MBO Error 9640

MBO Error 9641

MBO Error 9642

MBO Error 9643

MBO Error 9644

MBO Error 9645

MBO Error 9646

MBO Error 9647

MBO Error 9648

MBO Error 9649

MBO Error 9650

MBO Error 9651

MBO Error 9652

MBO Error 9653

MBO Error 9654

MBO Error 9655

MBO Error 9656

MBO Error 9657

MBO Error 9658

MBO Error 9659

MBO Error 9660

MBO Error 9661

MBO Error 9662

MBO Error 9663

MBO Error 9664

MBO Error 9665

MBO Error 9666

MBO Error 9667

MBO Error 9668

MBO Error 9669

MBO Error 9670

MBO Error 9671

MBO Error 9673

MBO Error 9674

MBO Error 9675

MBO Error 9676

MBO Error 9677

MBO Error 9678

MBO Error 9679

MBO Error 9680

MBO Error 9681

MBO Error 9685

MBO Error 9700

MBO Error 9701

MBO Error 9702

MBO Error 9703

MBO Error 9704

MBO Error 9705

MBO Error 9706

MBO Error 9707

MBO Error 9708

MBO Error 9709

MBO Error 9750

MBO Error 9751

MBO Error 9752

MBO Error 9753

MBO Error 9754

MBO Error 9755

MBO Error 9756

MBO Error 9757

MBO Error 9758

MBO Error 9759

MBO Error 9760

MBO Error 9761

MBO Error 9762

MBO Error 9780

MBO Error 9781

MBO Error 9782

MBO Error 9783

MBO Error 9784

MBO Error 9785

MBO Error 9786

MBO Error 9787

MBO Error 9788

MBO Error 9789

MBO Error 9790

MBO Error 9800

MBO Error 9801

MBO Error 9802

MBO Error 9803

MBO Error 9804

MBO Error 9805

MBO Error 9806

MBO Error 9807

MBO Error 9808

MBO Error 9809

MBO Error 9810

MBO Error 9811

MBO Error 9812

MBO Error 9813

MBO Error 9814

MBO Error 9815

MBO Error 9816

MBO Error 9817

MBO Error 9818

MBO Error 9819

MBO Error 9820

MBO Error 9821

MBO Error 9822

MBO Error 9823

MBO Error 9824

MBO Error 9825

MBO Error 9826

MBO Error 9827

MBO Error 9828

MBO Error 9829

MBO Error 9830

MBO Error 9831

MBO Error 9832

MBO Error 9833

MBO Error 9834

MBO Error 9900

MBO Error 9901

MBO Error 9902

MBO Error 9903

MBO Error 9904

MBO Error 9905

MBO Error 9906

MBO Error 9907

MBO Error 9908

MBO Error 9909

MBO Error 9910

MBO Error 9911

MBO Error 9912

MBO Error 9913

MBO Error 9914

MBO Error 9915

MBO Error 9916

MBO Error 9917

MBO Error 9918

MBO Error 9919

MBO Error 9920

MBO Error 9921

MBO Error 9922

MBO Error 9923

MBO Error 9924

MBO Error 9925

MBO Error 9926

MBO Error 9927

MBO Error 9928

MBO Error 9929

MBO Error 9930

MBO Error 9931

MBO Error 9932

MBO Error 9933

MBO Error 9934

MBO Error 9935

MBO Error 9936

MBO Error 9937

MBO Error 9938

MBO Error 9939

MBO Error 9940

MBO Error 9941

MBO Error 9942

MBO Error 9943

MBO Error 9944

MBO Error 9945

MBO Error 9950

MBO Error 9951

MBO Error 9952

MBO Error 9953

MBO Error 9954

MBO Error 9955

MBO Error 9957

MBO Error 9958

MBO Error 9959

MBO Error 9960

MBO Error 9961

MBO Error 9962

MBO Error 9963

MBO Error 9964

MBO Error 9965

MBO Error 9966

MBO Error 9967

MBO Error 9968

MBO Error 9969

MBO Error 9970

MBO Error 9971

MBO Error 9972

MBO Error 9973

MBO Error 9974

MBO Error 9975

MBO Error 9976

MBO Error 9977

MBO Error 9978

MBO Error 9979

MBO Error 9980

MBO Error 9981

MBO Error 9982

MBO Error 9983

MBO Error 9984

MBO Error 9985

MBO Error 9986

MBO Error 9987


UNIX Error Messages

UNIX Error E1000	UNIX Error E1003	UNIX Error E1005	UNIX Error E1007
UNIX Error E1008	UNIX Error E1009	UNIX Error E1010	UNIX Error E1014
UNIX Error E1015	UNIX Error E1016	UNIX Error E1018	UNIX Error E1026
UNIX Error E1031	UNIX Error E1035	UNIX Error E1036	UNIX Error E1038
UNIX Error E1042	UNIX Error E1048	UNIX Error E1053	UNIX Error E1054
UNIX Error E1058	UNIX Error E1061	UNIX Error E1063	UNIX Error E1065
UNIX Error E1073	UNIX Error E1075	UNIX Error E1081	UNIX Error E1100
UNIX Error E1101	UNIX Error E1102	UNIX Error E1103	UNIX Error E1104
UNIX Error E1105	UNIX Error E1106	UNIX Error E1107	UNIX Error E1108
UNIX Error E1109	UNIX Error E1110	UNIX Error E1111	UNIX Error E1112
UNIX Error E1113	UNIX Error E1114	UNIX Error E1116	UNIX Error E1117
UNIX Error E1118	UNIX Error E1119	UNIX Error E1120	UNIX Error E1121
UNIX Error E1122	UNIX Error E1123	UNIX Error E1124	UNIX Error E1125
UNIX Error E1126	UNIX Error E1127	UNIX Error E1128	UNIX Error E1129
UNIX Error E1130	UNIX Error E1131	UNIX Error E1132	UNIX Error E1133
UNIX Error E1134	UNIX Error E1135	UNIX Error E1136	UNIX Error E1138


Error 1001

1001 Unable to create the ARCserve Job Queue. (HOMEDIR=directory, EC=queue_error_code)

Module:

Job Engine

Explanation:

The Job Engine was unable to create the Job Queue directory in the ARCserve home directory.

Cause/Solution:

The ARCserve home directory may be invalid. Check whether the home directory is a proper DOS format (8.3) directory. If applicable, check whether the drive letter in the home directory exists.


Error 1002

1002 Unable to register Job Engine service. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module could not register with the Service Control Manager.

Cause/Solution:

Check the ms_error_code.


Error 1003

1003 Unable to set service status for Job Engine. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module could not notify the Service Control Manager to reflect its current status.

Cause/Solution:

Check the ms_error_code.


Error 1004

1004 Unable to start service control dispatcher for Job Engine. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module failed to initialize with the Service Control Manager.

Cause/Solution:

Check the ms_error_code.


Error 1005

1005 Unable to open Service Control Manager. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to open a handle to the Service Control Manager.

Cause/Solution:

Check the ms_error_code.


Error 1006

1006 Unable to open Service. (SERVICE=service, EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to open a handle to the specified service.

Cause/Solution:

Check the ms_error_code.


Error 1007

1007 Unable to start Service. (SERVICE=service, EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to start the specified service.

Cause/Solution:

Check the ms_error_code.


Error 1008

1008 Unable to query service status. (SERVICE=service, EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to obtain status information from the specified service.  Examples of status information obtained from a service are:

SERVICE is...

    START PENDING

    STARTED

    STOP PENDING

    STOPPED

    PAUSE PENDING

    PAUSED

    RESUME/CONTINUE PENDING

Cause/Solution:

Check the ms_error_code.


Error 1009

1009 Unable to send control to Service. (SERVICE=service, EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to send control commands to the specified service.  Examples of control commands sent to a service are:

START, STOP, PAUSE, CONTINUE.

Cause/Solution:

Check the ms_error_code.


Error 1010

1010 Unable to set service security. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to set security information for

the specified service.

Cause/Solution:

Check the ms_error_code.


Error 1201

1201 Unable to create a Process object. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to spawn ASRUNJOB.

ASRUNJOB is used to run BACKUP, RESTORE, COPY, etc. operations.

Cause/Solution:

Check the ms_error_code.


Error 1202

1202 Unable to create a Thread object. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to create a Thread object.  Threads are created by this module to regularly scan the ARCserve Job Queue for jobs ready to be executed and for Job Queue cleanup and maintenance.

Cause/Solution:

Check the ms_error_code.


Error 1203

1203 Unable to create an Event object. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to create an Event object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 1204

1204 Unable to initialize Security Descriptor. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to initialize a Security Descriptor.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 1205

1205 Unable to set Security Descriptor. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to change a Security Descriptor.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 1206

1206 Unable to create a File Mapping object. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to create a File Mapping object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 1207

1207 Unable to map view file. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to create a map view to a File Mapping object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 1208

1208 Unable to load Job Handler DLL. (DLL=file, EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to find, load, or register a task DLL file.

Cause/Solution:

Check the ms_error_code.


Error 1209

1209 Unable to free Job Handler DLL. (DLL=file, EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to free a previously loaded task DLL.

Cause/Solution:

Check the ms_error_code.


Error 1210

1210 Unable to get Job Handler entry point. (EC=ms_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to obtain or execute a Job Handler entry point. Each Task DLL that is registered with the Job Engine will set a task function entry point that is called when the ASRUNJOB process runs.

Cause/Solution:

Check the ms_error_code.


Error 1301

1301 Unable to get Queue information. (QUEUEID=queue_id, EC=queue_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to obtain information about the Job Queue.

Cause/Solution:

Check the queue_error_code.


Error 1302

1302 Unable to complete Queue maintenance. (EC=queue_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to start or complete maintenance on the Job Queue. Job Queue maintenance is run periodically to ensure that DONE jobs are cleaned up and any corrupt or invalid jobs in the Job Queue are fixed.

Cause/Solution:

Check the queue_error_code.


Error 1303

1303 Unable to get Job information. (QUEUEID=queue_id, JOBID=job_id, EC=queue_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to obtain information about a job in the Job Queue.

Cause/Solution:

Check the queue_error_code.


Error 1304

1304 Unable to get Job Handler information. (EC=queue_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to obtain Job Handler information.

Cause/Solution:

Check the queue_error_code.


Error 1305

1305 Unable to modify Job information. (QUEUEID=queue_id, JOBID=job_id, EC=queue_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to modify information for a job in the Job Queue.

Cause/Solution:

Check the queue_error_code.


Error 1306

1306 Unable to connect to the Media Engine. (EC=media_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to connect to the Media Engine.

Cause/Solution:

Check the media_error_code.


Error 1307

1307 Unable to get Device Group status. (DEVGROUP=group, EC=media_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to get Device Group status from the Media Engine.

Cause/Solution:

Check the media_error_code.


Error 1308

1308 Unable to reserve Device Group. (DEVGROUP=group, EC=media_error_code)

Module:

Job Engine

Explanation:

The JOBENG.EXE module was unable to reserve a Device Group from the Media Engine.

Cause/Solution:

Check the media_error_code.


Error 1309

1309 ARCserve Live Trial has expired.

Module:

Job Engine

Explanation:

ARCserve Live Trial has expired.


Error 2001

2001 Invalid parameters. (PARAM=parameters)

Module:

Job Runner

Explanation:

The parameters passed to ASRUNJOB are invalid.

Cause/Solution:

ASRUNJOB can be passed:

     a) a script name

     or

     b) a queue ID and job ID

Anything else is invalid.


Error 2002

2002 Failed to load library. (FILE=file, EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot find the .DLL associated with this job.

Cause/Solution:

Check that the .DLL file is in the ARCserve directory.


Error 2003

2003 Unable to get proc address. (EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot access the .DLL's functions.

Cause/Solution:

Check the error code.  The .DLL file may be damaged or belong to a different application.


Error 2004

2004 Unable to init application. (EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot start properly.

Cause/Solution:

Check the error code.  There may not be enough memory for ASRUNJOB to start.  Close any other applications and retry.


Error 2005

2005 Unable to init instance. (EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot start properly.

Cause/Solution:

Check the error code.  There may not be enough memory for ASRUNJOB to start.  Close any other applications and retry.


Error 2006

2006 Unable to find job file. (FILE=file, EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot find the job file.

Cause/Solution:

Check that the file is in the specified directory.


Error 2007

2007 Unable to read job file. (FILE=file, EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot read the job file.

Cause/Solution:

Check that the file is not damaged or is zero length.


Error 2008

2008 Unable to find job type. (TYPE=type)

Module:

Job Runner

Explanation:

ASRUNJOB cannot find the type associated with this job.

Cause/Solution:

Make sure the Job Engine is running.


Error 2009

2009 This trial copy of ARCserve has expired.

Module:

Job Runner

Explanation:

The trial version can only be used for a certain number of days after installation.

Cause/Solution:

Call Computer Associates Sales.


Error 2101

2101 Unable to allocate memory for thread info. (SIZE=size)

Module:

Job Runner

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory.  Close any other applications and retry.


Error 2102

2102 Unable to create thread. (EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot create a thread for the job.

Cause/Solution:

Check the error code.  There may not be enough memory to create the thread. Close any other applications and retry.


Error 2103

2103 Unable to get queue job. (EC=queue_error_code)

Cause/Solution:

ASRUNJOB is unable to find the job in the queue.

Module:

Job Runner

Explanation:

Check that the job has not been deleted from the queue.


Error 2104

2104 Unable to allocate memory for job. (SIZE=size)

Module:

Job Runner

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory. Close any other applications and retry.


Error 2105

2105 Unable to load job. (SIZE=size, EC=queue_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB is unable to load the job from the queue.

Cause/Solution:

Check that the job has not been deleted from the queue.


Error 2106

2106 Unable to load script. (SIZE=size, EC=queue_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB is unable to load the script.

Cause/Solution:

Check that the script has not been deleted.


Error 2107

2107 Unable to get file size. (FILE=file, EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot find the size of the job/script file.

Cause/Solution:

Check the error code.  Check that the file is in the specified directory.


Error 2111

2111 No job specified.

Module:

Job Runner

Explanation:

Internal ASRUNJOB error.


Error 2112

2112 Unable to allocate memory for job control block. (SIZE=size)

Module:

Job Runner

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory.  Close any other applications and retry.


Error 2113

2113 Unable to allocate memory for filter control block. (SIZE=size)

Module:

Job Runner

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory.  Close any other applications and retry.


Error 2114

2114 Unable to allocate memory for report control block. (SIZE=size)

Module:

Job Runner

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory.  Close any other applications and retry.


Error 2115

2115 Unable to allocate memory for media control block. (SIZE=size)

Module:

Job Runner

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory. Close any other applications and retry.


Error 2116

2116 Unable to allocate memory for volume control block. (SIZE=size)

Module:

Job Runner

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory. Close any other applications and retry.


Error 2117

2117 Unable to allocate memory for task control block. (SIZE=size)

Module:

Job Runner

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory. Close any other applications and retry.


Error 2121

2121 Unable to create monitor. (EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot create the job monitor memory-mapped file.

Cause/Solution:

Check the error code.  There may not be enough memory to create the memory-mapped file. Close any other applications and retry.


Error 2122

2122 Unable to view monitor. (EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot create a view to the memory-mapped file.

Cause/Solution:

Check the error code.  There may not be enough memory to create the view of the memory-mapped file. Close any other applications and retry.


Error 2131

2131 Unable to allocate memory for security descriptor. (SIZE=size)

Module:

Job Runner

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory. Close any other applications and retry.


Error 2132

2132 Unable to initialize security descriptor. (EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot initialize the security descriptor.

Cause/Solution:

Check the error code.  Check the account used by the Job Engine.  Setup creates a Local System account for use by the Job Engine. This can be checked by using the Control Panel's Service and checking the Startup settings for the ARCserve Job Engine.


Error 2133

2133 Unable to set access control list. (TYPE=access_type, EC=ms_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB cannot set the access control list.

Cause/Solution:

Check the error code.  Check the account used by the Job Engine. Setup creates a Local System account for use by the Job Engine. This can be checked by using the Control Panel's Service and checking the Startup settings for the ARCserve Job Engine.


Error 2201

2201 Unable to get job. (EC=queue_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB is unable to find the job in the queue.

Cause/Solution:

Check that the job has not been deleted from the queue.  Check the queue using the Job Status Manager.


Error 2202

2202 Unable to delete job. (EC=queue_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB is unable to remove the job from the queue.

Cause/Solution:

Check that the job has not already been deleted from the queue. Check the queue using the Job Status Manager.


Error 2203

2203 Unable to modify job. (EC=queue_error_code)

Module:

Job Runner

Explanation:

ASRUNJOB is unable to update the job in the queue.

Cause/Solution:

Check that the job has not been deleted from the queue. Check the queue using the Job Status Manager.


Error 3001

3001 Invalid job type.

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3002

3002 Invalid source disk. (DISK=disk)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3003

3003 Invalid source media. (MEDIA=media_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3004

3004 Invalid destination disk. (DISK=disk)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3005

3005 Invalid destination media. (MEDIA=media_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3011

3011 Source is not a disk. (NODE=node_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3012

3012 Source is not a media. (NODE=node_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3013

3013 Destination is not a disk. (NODE=node_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3014

3014 Destination is not a media. (NODE=node_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3021

3021 No valid source.

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3022

3022 No valid destination.

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3023

3023 No disk selected. (NODE=node_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3024

3024 No media selected. (NODE=node_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3025

3025 Too many sources.

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3026

3026 Too many destinations.

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3027

3027 Too many disks. (NODE=node_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3028

3028 Too many media. (NODE=node_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3032

3032 Compression is disabled due to hardware data compression

Module:

Tasks Engines

Explanation:

The software compression is automatically disabled when the backup hardware device is compression-enabled.


Error 3051

3051 No database sessions found.

Module:

Tasks Engines

Explanation:

Recover database cannot find a database session on the media specified.

Cause/Solution:

Try another media.


Error 3061

3061 Unable to allocate memory for anti-virus control block.  (SIZE=size)

Module:

Tasks Engines

Explanation:

ASRUNJOB cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory.


Error 3062

3062 Unable to find anti-virus DLL.  (EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASRUNJOB cannot find the AVH32DLL.DLL.

Cause/Solution:

ASRUNJOB cannot find the AVH32DLL.DLL.


Error 3063

3063 Unable to find anti-virus procedures.

Module:

Tasks Engines

Explanation:

ASRUNJOB cannot access the AVH32DLL.DLL's functions.

Cause/Solution:

The AVH32DLL.DLL file may be damaged or be from an earlier version of InocuLAN or ARCserve.


Error 3064

3064 Unable to initialize anti-virus.  (EC=inoculan_error_code)

Module:

Tasks Engines

Explanation:

ASTASK was not able to initialize the anti-virus data.

Cause/Solution:

The AVH32DLL.DLL and/or VIRSIG.DAT files may be damaged or be from an earlier version of InocuLAN or ARCserve.


Error 3065

3065 Unable to set anti-virus flags.  (EC=inoculan_error_code)

Module:

Tasks Engines

Explanation:

ASTASK was not able to set the anti-virus flags.

Cause/Solution:

The AVH32DLL.DLL and/or VIRSIG.DAT files may be damaged or be from an earlier version of InocuLAN or ARCserve.


Error 3066

3066 Unable to load anti-virus data.  (EC=inoculan_error_code)

Module:

Tasks Engines

Explanation:

ASTASK was not able to load the anti-virus data.

Cause/Solution:

The AVH32DLL.DLL and/or VIRSIG.DAT files may be damaged or be from an earlier version of InocuLAN or ARCserve.


Error 3071

3071 Unable to find advanced API DLL.  (EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASRUNJOB cannot find the ADVAPI32.DLL.

Cause/Solution:

Check that the ADVAPI32.DLL file is in the Windows directory.


Error 3072

3072 Unable to find advanced API procedures.

Module:

Tasks Engines

Explanation:

ASRUNJOB cannot access the ADVAPI32.DLL's functions.

Cause/Solution:

The ADVAPI32.DLL file may be damaged or be from an earlier version of Windows NT.


Error 3073

3073 Unable to logon as user.  (USER=user, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot logon as the specified user.

Cause/Solution:

Check the error code.  Check the user name and password specified in the Server Admin.


Error 3101

3101 Disk is full. (DISK=disk)

Module:

Tasks Engines

Explanation:

The specified disk is full.

Cause/Solution:

Delete any unnecessary files from the specified disk.


Error 3102

3102 Volume is full. (VOLUME=volume)

Module:

Tasks Engines

Explanation:

The specified volume is full.

Cause/Solution:

Delete any unnecessary files from the specified volume.


Error 3103

3103 Unable to access disk. (DISK=disk, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot access the specified disk.

Cause/Solution:

Check the error code.  The disk may have been dismounted or removed.


Error 3104

3104 Path is too long. (PATH=path)

Module:

Tasks Engines

Explanation:

The specified path exceeds the maximum allowed by Windows NT.

Cause/Solution:

ARCserve allows for a 260 character path.  This includes the drive letter or network server and share names.


Error 3105

3105 Retrying file. (FILE=file)

Module:

Tasks Engines

Explanation:

ASTASK is retrying a skipped file at the end of the session.

Cause/Solution:

This is simply a note.


Error 3115

Module:

DMO

Explanation:

DMO RPC failure.

Cause/Solution:

Make sure the DMAgent service is running.  Consult Microsoft documentation for specific RPC error.


Error 3139

3139:   Data Migration Error

Module:

DMO

Explanation:

Specific information is contained in the message in the activity log.

Cause/Solution:

There was some error encountered in the Data Migration Option.

You may contact tech support for more details.


Error 3201

Failed to detect if ARCServe needs to restore SIS common store file for the file restored. (PATH:%s, EC:%x)

Explanation:

ASTASK is unable to get the name of the SIS common store file, that requires to be backed up along with the link

Cause/Solution:

Please check the installation and ensure that the volume is SIS enabled or if the SIS Common Store folder exists in the volume.


Error 3202

3202 Failed to create SIS structure, SIS common store files required, if any, will not be backed up/restored. (EC:%x)

Explanation:

ASTASK is unable to initialize the SIS structures.

Cause/Solution:

Please check the installation and ensure that the volume is SIS enabled or if the SIS Common Store folder exists in the volume.


Error 3203

3203  Failed to get SIS common store file required for %s. (CASE: [case number], EC:%[error code])

Explanation:

ASTASK is unable to get the name of the SIS common store file that requires to be backed up along with the link.

Cause/Solution:

Check the case number:

1.   Insufficient memory.

2.   Unable to open file to get the reparse point data.

3.   Unable to get reparse point data after opening file.

4.   Unable to use reparse point data to get the SIS common store file required.

Please check the installation and ensure that the volume is SIS enabled or if the SIS Common Store folder exists in the volume.


Error 3204

3204 No shares found on server.  (SERVER=server)

Module:

Tasks Engines

Explanation:

ASTASK cannot find any shares on the server.

Cause/Solution:

Check the user name and password specified in the job.  Check that the user has access rights to the server.


Error 3205

3205 No servers found in domain.  (DOMAIN=domain)

Module:

Tasks Engines

Explanation:

ASTASK cannot find any servers in the domain.

Cause/Solution:

Check the user name and password specified in the job.  Check that the user has access rights to the domain.


Error 3301

3301 Unable to find directory. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified directory.

Cause/Solution:

Check the error code.  Check that the directory still exists.  Check the user account being used has access rights to this directory.


Error 3302

3302 Unable to create directory. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot create the specified directory.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3303

3303 Unable to remove directory. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot remove the specified directory.

Cause/Solution:

Check the error code.  Check that the directory is empty.  Check your access rights.


Error 3304

3304 Unable to open directory. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot open the specified directory.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3311

3311 Unable to reset directory access date. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot reset the access date for the specified directory.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3312

3312 Unable to set directory information. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the information for the specified directory.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3313

3313 Unable to set directory owner. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the owner for the specified directory.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3314

3314 Unable to set directory group. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the group for the specified directory.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3315

3315 Unable to set directory access control list. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the access control list for the specified directory.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3316

3316 Unable to set directory system access control list. (DIR=directory, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the system access control list for the specified directory.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3321

3321 Directories overlap. (SOURCE=directory, DEST=directory)

Module:

Tasks Engines

Explanation:

The two directories overlap.

Cause/Solution:

ASTASK cannot copy a source that overlaps the destination.


Error 3330

C3330: Operation disabled due to insufficient disk space.

Module:

Tasks Engines

Explanation:

Operation disabled due to insufficient disk space.

Cause/Solution:

C3330 is generated if the free space on the volume used by BAOF for its Preview Data Cache (any data being written to a file while it is being backed up has its old data copied into temporary storage so that ARCserve gets the original data) goes below a configurable limit.  This limit can be changed via OFAWIN.


Error 3331

C3331: Operation disabled due to license violation.

Module:

Tasks Engines

Explanation:

Operation disabled due to license violation.

Cause/Solution:

Reinstall product using different CD-key.  Call for support if necessary.


Error 3401

3401 Unable to find file. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified file.

Cause/Solution:

Check the error code.  Check that the file still exists.


Error 3402

3402 Unable to create file. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot create the specified file.

Cause/Solution:

Check the error code. Check if the file was opened by another user.  Check your access rights.


Error 3403

3403 Unable to delete file. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot delete the specified file.

Cause/Solution:

Check the error code.  Check if the file was opened by another user.  Check your access rights.


Error 3404

3404 Unable to open file. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot open the specified file.

Cause/Solution:

Check the error code. Check if the file was opened by another user.  Check your access rights.


Error 3405

3405 Unable to close file. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot close the specified file.

Cause/Solution:

Check the error code.


Error 3406

3406 Unable to read file. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot read from the specified file.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3407

3407 Unable to write file. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot write to the specified file.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3408

3408 Unable to create unique file. (FILE=file)

Module:

Tasks Engines

Explanation:

ASTASK cannot create a unique file.

Cause/Solution:

ASTASK needs to create a unique temporary file.  Check if there are old temporary files in the specified path and remove them.


Error 3409

3409 Unable to replace the active file. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot replace the active file the next time the machine is started.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3411

3411 Unable to reset file access date. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot reset the access date for the specified file.

Cause/Solution:

Check the error code. Check if the file was opened by another user.  Check your access rights.


Error 3412

3412 Unable to set file information. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the information for the specified file.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3413

3413 Unable to set file owner. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the owner for the specified file.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3414

3414 Unable to set file group. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the group for the specified file.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3415

3415 Unable to set file access control list. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the access control list for the specified file.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3416

3416 Unable to set file system access control list. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot set the system access control list for the specified file.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3421

3421 Unable to open the registry key. (KEY=registry_key, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot access the specified registry key.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3422

3422 Unable to save the registry key. (KEY=registry_key, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot save the specified registry key.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3423

3423 Unable to replace the registry key. (KEY=registry_key, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot replace the specified registry key.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3424

3424 Unable to create the registry key. (KEY=registry_key, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot create the specified registry key.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3425

3425 Unable to load the registry key. (KEY=registry_key, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot load the specified registry key.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3426

3426 Unable to restore the registry key. (KEY=registry_key, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot restore the specified registry key.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3431

3431 Unable to back up the event log. (KEY=registry_key, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot back up the specified event log.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3432

3432 Unable to replace the event log. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot replace the specified event log.

Cause/Solution:

Check the error code.  Check your access rights.


Error 3441

3441 Unable to open linked file. (FILE=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot open the specified linked file.

Cause/Solution:

Check the error code.  Check that the file exists.


Error 3442

3442 Unable to link file. (FILE=file, LINK=file, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot link the specified files.

Cause/Solution:

Check the error code.


Error 3451

3451 Unable to write stream ID. (FILE=file, ID=stream_id, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot write the stream ID for the specified file.

Cause/Solution:

Check the error code.


Error 3452

3452 Unable to write stream name. (FILE=file, ID=stream_id, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot write the stream name for the specified file.

Cause/Solution:

Check the error code.


Error 3453

3453 Unable to write stream data. (FILE=file, ID=stream_id, EC=ms_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot write the stream data for the specified file.

Cause/Solution:

Check the error code.


Error 3501

3501 Unable to add job to database. (EC=db_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot add a new job to the database.

Cause/Solution:

Make sure the Database Engine is running.  This message may have been preceded by an error message from the Database Engine.


Error 3502

3502 Unable to add session to database. (EC=db_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot add a new session to the database.

Cause/Solution:

Make sure the Database Engine is running.  This message may have been preceded by an error message from the Database Engine.


Error 3503

3503 Unable to add directory to database. (DIR=directory, EC=db_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot add the directory to the database.

Cause/Solution:

Make sure the Database Engine is running.  This message may have been preceded by an error message from the Database Engine.


Error 3504

3504 Unable to add file to database. (FILE=file, EC=db_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot add the file to the database.

Cause/Solution:

Make sure the Database Engine is running.  This message may have been preceded by an error message from the Database Engine.


Error 3511

3511 Unable to begin database backup. (EC=db_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot start the database backup.

Cause/Solution:

Make sure the Database Engine is running.  This message may have been preceded by an error message from the Database Engine.


Error 3512

3512 Unable to end database backup. (EC=db_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot end the database backup.

Cause/Solution:

Make sure the Database Engine is running.  This message may have been preceded by an error message from the Database Engine.


Error 3521

3521 Unable to begin database restore. (EC=db_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot restore the database.

Cause/Solution:

Make sure the Database Engine is running.  This message may have been preceded by an error message from the Database Engine.  You cannot restore the database while other jobs are using the database.


Error 3522

3522 Unable to end database restore. (EC=db_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot restore the database.

Cause/Solution:

Make sure the Database Engine is running.  This message may have been preceded by an error message from the Database Engine.


NEW TASK MSG


Error 3530

Failed to login to database.(EC=Error Code)

Module:

Tasks Engines

Explanation:

ASTASK cannot login to ARCserve database engine.

Cause/Solution:

ARCserve database engine may not be running. Restart ARCserve database engine.


Error 3531

Invalid or no media pool name.

Module:

Tasks Engines

Explanation:

There is no media pool name.

Cause/Solution:

Job in queue may be corrupted. Resubmit the job with media pool name.


Error 3532

Failed to create media pool.(Pool Name, EC=Error Code)

Module:

Tasks Engines

Explanation:

ASTASK cannot create media pool in registry.

Cause/Solution:

The current user may not have enough privilege or the registry database may be corrupted. Check the integrity of registry database or login as different user.


Error 3533

Failed to get rotation media name.(Pool Name Prefix, EC=Error Code)

Module:

Tasks Engines

Explanation:

ASTASK cannot get simple rotation media name from job.

Cause/Solution:

Job in queue may be corrupted. Resubmit the job with 7 media names.


Error 3534

Failed to connect to the registry.(Machine name,EC=Error Code)

Module:

Tasks Engines

Explanation:

ASTASK cannot connect to the remote registry database.

Cause/Solution:

The current user may not have enough privilege or the remote machine may be NT 4.0 or corrupted. Retry with different user.


Error 3535

Unable to get media information.(EC=Error Code)

Module:

Tasks Engines

Explanation:

ASTASK cannot get media information from ARCserve database.

Cause/Solution:

ARCserve database engine may not be running. Restart ARCserve database engine.


Error 3536

Insufficient memory is available.

Module:

Tasks Engines

Explanation:

ASTASK cannot allocate memory.

Cause/Solution:

The system may be overloaded. Terminate any unnecessary applications.


Error 3537

Failed to connect to media.(Media Name, Sequence,EC=Error Code)

Module:

Tasks Engines

Explanation:

ASTASK cannot connect to the media in storage device.

Cause/Solution:

Media engine may not be running or cable is disconnected.  Check the physical device connection or restart media engine.


Error 3538

Failed to read media header.(EC=Error Text)

Module:

Tasks Engines

Explanation:

ASTASK cannot read media header from the media in the storage device.

Cause/Solution:

Media in device may be bad or storage device header needs to be cleaned.  Clean storage device header or try new media.


Error 3539

Unable to set Rotation job backup flag.

Module:

Tasks Engines

Explanation:

ASTASK cannot set backup flag for rotation media.

Cause/Solution:

ARCserve database engine may not be running. Restart ARCserve database engine.


Error 3540

Unable to get execution time for the next job.(EC=Error Code)

Module:

Tasks Engines

Explanation:

ASTASK cannot get the next execution time from job.

Cause/Solution:

Job in queue may be corrupted. Resubmit the job or modify job.


Error 3541

Unable to get media list.

Module:

Tasks Engines

Explanation:

ASTASK cannot get media list from ARCserve database.

Cause/Solution:

ARCserve database engine may not be running. Restart ARCserve database engine.


Error 3542

 Not used

Failed to start enumerating media.(EC=Error Code)

Module:

Tasks Engines

Explanation:


Error 3543

Failed to repair an incomplete session.(EC=Error Code)

Module:

Tasks Engines

Explanation:

ASTASK cannot repair an incomplete session.

Cause/Solution:

Media in device may be bad or storage device header need to be cleaned.  Clean storage device header or try new media.


Error 3544

Unable to get media list from pool.(Pool Name)

Module:

Tasks Engines

Explanation:

ASTASK cannot get media list from ARCserve database for rotation job.

Cause/Solution:

ARCserve database engine may not be running. Restart ARCserve database engine. ASTASK may use BLANK media instead


Error 3545

Unable to get media information from pool. (Media Name,Media ID,Sequence,Pool Name,EC=Error Code)

Module:

Tasks Engines

Explanation:

ASTASK cannot get media information from ARCserve database.

Cause/Solution:

ARCserve database engine may not be running. Restart ARCserve database engine.


Error 3701

3701 Unable to connect to media engine. (EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot connect to the Media engine.

Cause/Solution:

Make sure the Media engine is running.


Error 3702

3702 Unable to connect to group. (GROUP=group, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot connect to the specified group.

Cause/Solution:

Check the error code.  Check if the group is busy or in use.  Check if the group was deleted or renamed since the job was scheduled.


Error 3703

3703 Unable to open media. (MEDIA=media_name, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot open the specified media.

Cause/Solution:

Check the error code.  Check that the correct media is in the drive.


Error 3704

3704 Unable to close media. (MEDIA=media_name, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot close the specified media.

Cause/Solution:

Check the error code.


Error 3705

3705 Unable to format media (MEDIA=media_name, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot format the specified media.

Cause/Solution:

Check the error code.  Check that the media is not write-protected.


Error 3711

3711 Unable to open session. (EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot open a session.

Cause/Solution:

Check the error code.  Check that the media is not full.


Error 3712

3712 Unable to close session. (EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot close the current session.

Cause/Solution:

Check the error code.


Error 3713

3713 Unable to read from media. (MEDIA=media_name, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot read from the specified media.

Cause/Solution:

Check the error code.  Check that the media is in the proper storage device.  The media may be damaged or the storage device's heads may need cleaning.


Error 3714

3714 Unable to write to media. (MEDIA=media_name, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot write to the specified media.

Cause/Solution:

Check the error code.  Check that the media is in the proper storage device.  The media may be damaged or the storage device's heads may need cleaning.


Error 3715

3715 Unable to read continuation block. (EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the continuation block.

Cause/Solution:

Check the error code.  This is not a critical error.  Some storage devices do not warn before reaching the end of media.


Error 3716

3716 Unable to write continuation block. (EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot write a continuation block to the media.

Cause/Solution:

Check the error code.  This is not a critical error.  Some storage devices do not warn before reaching the end of media.


Error 3717

3717 Unable to go to cluster. (CLUSTER=cluster_number, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot go to the specified cluster on the media.

Cause/Solution:

Check the error code.  This is usually a media error.  The media may be damaged or the storage device's heads may need cleaning.


Error 3801

3801 Invalid session header signature. (SIG=signature)

Module:

Tasks Engines

Explanation:

ASTASK has found an invalid session header signature.

Cause/Solution:

There may be a problem in the connection between the storage device and the host adapter.  The media may be damaged or the storage device's heads may need cleaning.


Error 3802

3802 Invalid file header signature. (SIG=signature)

Module:

Tasks Engines

Explanation:

ASTASK has found an invalid file header signature.

Cause/Solution:

There may be a problem in the connection between the storage device and the host adapter.  The media may be damaged or the storage device's heads may need cleaning.


Error 3803

3803 Invalid file trailer signature. (SIG=signature)

Module:

Tasks Engines

Explanation:

ASTASK has found an invalid file trailer signature.

Cause/Solution:

There may be a problem in the connection between the storage device and the host adapter.  The media may be damaged or the storage device's heads may need cleaning.


Error 3811

3811 Unable to read compressed sessions.

Module:

Tasks Engines

Explanation:

ASTASK has found a compression session.

Cause/Solution:

ARCserve cannot restore compressed sessions created by ARCsolo for DOS or ARCsolo for Windows.


Error 3812

3812 Unable to read Macintosh sessions.

Module:

Tasks Engines

Explanation:

ASTASK has found a Macintosh session.

Cause/Solution:

ARCserve cannot restore sessions created by ARCserve for Macintosh.


Error 3813

3813 Unable to read UNIX sessions.

Module:

Tasks Engines

Explanation:

ASTASK has found a UNIX session.

Cause/Solution:

ARCserve cannot restore sessions created by ARCserve UNIX.


Error 3814

3814 Invalid session password.

Module:

Tasks Engines

Explanation:

The password specified by the user does not match the password on media.

Cause/Solution:

Please enter the correct password.


Error 3815

3815 Invalid media format code. (FC=format_code)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.


Error 3816

3816 Unable to read Directory Services sessions.

Module:

Tasks Engines

Explanation:

ASTASK has found a Directory Services session.

Cause/Solution:

ARCserve cannot restore Directory Services sessions created by ARCserve for NetWare.


Error 3821

3821 Unable to find media. (MEDIA=media_name)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified media.

Cause/Solution:

Place the media in one of the drives belonging to the active group.  The media may be damaged or the storage device's heads may need cleaning.


Error 3822

3822 Unable to find media. (MEDIA=media_name, SEQ=sequence_number)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified sequence of the media.

Cause/Solution:

Place the media in one of the drives belonging to the active group.  The media may be damaged or the storage device's heads may need cleaning.


Error 3823

3823 Unable to find media. (MEDIA=media_name, ID=media_id, SEQ=sequence_number)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified media.

Cause/Solution:

Place the media in one of the drives belonging to the active group.  The media may be damaged or the storage device's heads may need cleaning.


Error 3824

3824 Unable to find this media. (MEDIA=media_name)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified media.

Cause/Solution:

Place the media in one of the drives belonging to the active group.  The media may be damaged or the storage device's heads may need cleaning.


Error 3825

3825 Unable to find this media or a blank media. (MEDIA=media_name)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified media or a blank media.

Cause/Solution:

Place the media in one of the drives belonging to the active group.  The media may be damaged or the storage device's heads may need cleaning.


Error 3826

3826 Unable to find the first sequence of this media. (MEDIA=media_name)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the first sequence of the specified media.

Cause/Solution:

Place the media in one of the drives belonging to the active group.  The media may be damaged or the storage device's heads may need cleaning.


Error 3827

3827 Unable to find the last sequence of this media. (MEDIA=media_name)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the last sequence of the specified media.

Cause/Solution:

Place the media in one of the drives belonging to the active group. The media may be damaged or the storage device's heads may need cleaning.


Error 3828

3828 Unable to find this media or a blank media. (MEDIA=media_name, SEQ=sequence_number)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified media or a blank media.

Cause/Solution:

Place the media in one of the drives belonging to the active group.  The media may be damaged or the storage device's heads may need cleaning.


Error 3831

3831 Unable to find any Computer Associates media.

Module:

Tasks Engines

Explanation:

ASTASK cannot find a Computer Associates media.

Cause/Solution:

Place the media in one of the drives belonging to the active group.  The media may be damaged or the storage device's heads may need cleaning.


Error 3832

3832 Unable to find a blank media.

Module:

Tasks Engines

Explanation:

ASTASK cannot find a blank media.

Cause/Solution:

Place the media in one of the drives belonging to the active group.  The media may be damaged or the storage device's heads may need cleaning.


Error 3833

3833 Unable to find an unprotected media.

Module:

Tasks Engines

Explanation:

ASTASK cannot find an unprotected media.

Cause/Solution:

Make sure the current media is not write protected.


Error 3841

3841 Unable to find session number. (MEDIA=media_name, SESSION=session_number, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified session on the media.

Cause/Solution:

Check the session number and media.  The media may be damaged or the storage device's heads may need cleaning.


Error 3842

3842 Unable to find file. (FILE=file, MEDIA=media_name)

Module:

Tasks Engines

Explanation:

ASTASK cannot find the specified file on the media.

Cause/Solution:

Check the file name and media.  The media may be damaged or the storage device's heads may need cleaning.


Error 3851

3851 Media is full. (MEDIA=media_name)

Module:

Tasks Engines

Explanation:

This media is full and cannot be appended to.

Cause/Solution:

Select a different media or format a new media.


Error 3852

3852 Media has reached the maximum number of sessions. (MEDIA=media_name, SESSIONS=sessions)

Module:

Tasks Engines

Explanation:

This media cannot store any additional sessions.

Cause/Solution:

Select a different media or format a new media.


Error 3853

3853 Session was truncated. (SESSION=session_number)

Module:

Tasks Engines

Explanation:

This session was truncated.

Cause/Solution:

This is not an error.


Error 3854

3854 Unable to repair session. (MEDIA=media_name, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK was unable to repair the last session on the media.

Cause/Solution:

Check the error code.  The media may be damaged.


Error 3855

3855 Unable to position media. (MEDIA=media_name, EC=media_error_code)

Module:

Tasks Engines

Explanation:

ASTASK was unable to position to the desired session on the media.

Cause/Solution:

Check the error code.


Error 3856

3856 Media has reached the maximum sequence number.  (MEDIA=media_name, SEQ=sequence_number)

Module:

Tasks Engines

Explanation:

This media has reached the maximum sequence number and cannot span to an additional media.

Cause/Solution:

Format a new media.


Error 3860

3860 Unable to find directory/file. (CLUSTER1=cluster_number, OFFSET1=offset, CLUSTER2=cluster_number, OFFSET2=offset)

Module:

Tasks Engines

Explanation:

ASTASK was unable to position to the desired file on the media.

Cause/Solution:

Check the error code.


Error 3861

3861 Unable to find directory/file: already passed it. (FILE=file)

Module:

Tasks Engines

Explanation:

ASTASK has already passed the desired file on the media.

Cause/Solution:

Check the error code.


Error 3862

3862 Unable to find directory/file: names do not match. (NAME1=name, NAME2=name)

Module:

Tasks Engines

Explanation:

The name on the media does not match the name given to restore.

Cause/Solution:

Check that the media name and session number are correct.


Error 3863

3863 Unable to find directory: types do not match. (DIR=directory)

Module:

Tasks Engines

Explanation:

A file was found where a directory was expected.

Cause/Solution:

Check that the media name and session number are correct.


Error 3864

3864 Unable to find file: types do not match. (FILE=file)

Module:

Tasks Engines

Explanation:

A directory was found where a file was expected.

Cause/Solution:

Check that the media name and session number are correct.


Error 3871

3871 Invalid file stream ID. (FILE=file, ID=stream_id)

Module:

Tasks Engines

Explanation:

The stream ID on the media is invalid.

Cause/Solution:

Check that the media is in the proper storage device.  The media may be damaged or the storage device's heads may need cleaning.


Error 3881

3881 Invalid file link ID. (FILE=file, ID=link_id)

Module:

Tasks Engines

Explanation:

The NTFS hard link cannot be restored.

Cause/Solution:

Check that the media is in the proper storage device.  The media may be damaged or the storage device's heads may need cleaning.


Error 3882

3882 Invalid file link size. (FILE=file, SIZE=size)

Module:

Tasks Engines

Explanation:

The NTFS hard link cannot be restored.

Cause/Solution:

Check that the media is in the proper storage device.  The media may be damaged or the storage device's heads may need cleaning.


Error 3883

3883 Unable to find linked file. (FILE=file, LINK=file)

Module:

Tasks Engines

Explanation:

The NTFS hard link cannot be restored.

Cause/Solution:

ASTASK cannot find the first file to link to.  Check that the file exists.


Error 3884

E3884 Unable to position media catalog file.

Module:

Tasks Engines

Explanation:

During merge, ARCserve will try to position to the catalog file that is located in the end of the session, then merge the session through the catalog file.

Cause/Solution:

This error could be caused by:

•	?	Bad tape media

•	?	Tape drive does not support tape catalog

•	?	Catalog file is corrupted or missing for that backup session


Error 3901

3901 Skip machine - Type not supported. (TYPE=type, MACHINE=machine_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.

Cause/Solution:

Check the script using the Detail tab in the Job Status Manager.


Error 3902

3902 Skip server - OS not supported. (SERVER=server_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.

Cause/Solution:

Check the script using the Detail tab in the Job Status Manager.


Error 3903

3903 Skip workstation - OS not supported. (WS=workstation_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.

Cause/Solution:

Check the script using the Detail tab in the Job Status Manager.


Error 3904

3904 Skip remote workstation - Not supported. (WS=workstation_name)

Module:

Tasks Engines

Explanation:

Internal ASTASK error.

Cause/Solution:

Check the script using the Detail tab in the Job Status Manager.


Error 3905

Error 3905  Skip Node or Agent  - Not supported in this Edition.

Module:

Tasks Engines

Explanation:

Cross Edition products cannot function together (i.e. Enterprise to Workgroup/Advanced).  ARCserve can only backup client agents of the same edition.

Cause/Solution:

The specified agent is not supported by this edition.  You cannot mix Advanced or Workgroup agents with Enterprise Servers, or vice versa.


Error 3906

Error 3906  Skip agent - Not supported in this Edition.

Module:

Tasks Engines

Explanation:

The database agent or client agent backup is not supported by MBO.

Cause/Solution:

Contact support services.


Error 3921

3921 Skip directory. (DIR=directory)

Module:

Tasks Engines

Explanation:

Skip this directory.

Cause/Solution:

ASTASK is skipping the directory.  Check for a preceding error.


Error 3931

3931 Skip file. (FILE=file)

Module:

Tasks Engines

Explanation:

Skip this file.

Cause/Solution:

ASTASK is skipping the file.  Check for a preceding error.


Error 3932

3932 Skip file - Too large. (FILE=file)

Module:

Tasks Engines

Explanation:

This file is too large and was skipped.

Cause/Solution:

ASTASK can optionally skip files larger than 2 GB.


Error 3933

3933 Skip file - Execute only. (FILE=file)

Module:

Tasks Engines

Explanation:

This file is marked for execution only and cannot be copied.

Cause/Solution:

NetWare files can be marked for execution only and cannot be backed up.


Error 3934

3934 Skip file - Migrated. (FILE=file)

Module:

Tasks Engines

Explanation:

This file is marked as migrated and should not be backed up.

Cause/Solution:

NetWare files can be marked as migrated and should not be backed up.


Error 3935

3935 Skip file - Registry file. (FILE=file)

Module:

Tasks Engines

Explanation:

This file is a registry file and cannot be compared.

Cause/Solution:

Registry files cannot be compared since they are active and normally change.


Error 3936

3936 Skip file - Event log. (FILE=file)

Module:

Tasks Engines

Explanation:

This file is an event log and cannot be compared.

Cause/Solution:

Event logs cannot be compared since they are active and normally change.


Error 3941

3941 Skip file - Marked as invalid. (FILE=file)

Module:

Tasks Engines

Explanation:

This file is marked as invalid on the media.

Cause/Solution:

There was some error while backing up this file and ARCserve marked the file as invalid.  This file cannot be restored with any degree of confidence.


Error 3942

3942 Skip file - Confirm overwrite selected for scheduled jobs. (FILE=file)

Module:

Tasks Engines

Explanation:

This file was skipped because the user selected the confirm overwrite option but scheduled the job.


Error 3951

3951 The directory cannot be found. (DIR=directory)

Module:

Tasks Engines

Explanation:

The directory on media cannot be found on the disk.

Cause/Solution:

Check if the directory still exists.


Error 3952

3952 The directory attributes have changed. (DIR=directory, MEDIA=attributes, DISK=attributes)

Module:

Tasks Engines

Explanation:

The directory attributes on media do not match those on disk.


Error 3961

3961 The file cannot be found. (FILE=file)

Module:

Tasks Engines

Explanation:

The file on media cannot be found on the disk.

Cause/Solution:

Check if the file still exists.


Error 3962

3962 The file attributes have changed. (FILE=file, MEDIA=attributes, DISK=attributes)

Module:

Tasks Engines

Explanation:

The file attributes on media do not match those on disk.


Error 3963

3963 The file contents have changed. (FILE=file)

Module:

Tasks Engines

Explanation:

The contents of the file on media do not match those on disk.


Error 3964

3964 The file size has changed. (FILE=file, MEDIA=size, DISK=size)

Module:

Tasks Engines

Explanation:

The size of the file on media does not match those on disk.


Error 3965

3965 The file date and time have changed.  (FILE=file, MEDIA=date&time, DISK=date&time)

Module:

Tasks Engines

Explanation:

The date and time of the file on media do not match those on disk.


Error 3971

3971 Virus detected - File skipped.  (FILE=file)

Module:

Tasks Engines

Explanation:

A virus was detected in the specified file.

Cause/Solution:

The file has been skipped.  You may be able to cure the file with InocuLAN.


Error 3972

3972 Virus detected - File deleted.  (FILE=file)

Module:

Tasks Engines

Explanation:

A virus was detected in the specified file.

Cause/Solution:

The file has been deleted.


Error 3973

3973 Virus detected - File renamed.  (FILE=file)

Module:

Tasks Engines

Explanation:

A virus was detected in the specified file.

Cause/Solution:

The file has been renamed.  You may be able to cure the file with InocuLAN.


Error 3974

E 3974 ARCserve Mainframe Backup Option Service is not running

Modules:  Tasks Engines

Explanation:  To run any backup to Mainframe Backup Option or restore from Mainframe Backup Option job, ARCserve Mainframe Backup Option service has to be started first.

Cause/Solution:  Start the ARCserve Mainframe Backup Option service


Error 3975

E 3975  Failed to load MBO_API.DLL

Modules:  Tasks Engines

Explanation:  Failed to load MBO_API.DLL to start the MBO job.

Cause/Solution:  Probable insufficient memory.


Error 3977

E 3977 Unable to allocate memory for backup to Mainframe Backup Option job.

Modules:  Tasks Engines

Explanation:  Not enough memory to continue job

Cause/Solution:  Not enough memory/Close some applications or add more memory and retry


Error 3978

E 3978 Invalid backup to Mainframe Backup Option job handle

Modules:  Tasks Engines

Explanation:  Each backup to Mainframe Backup Option job gets a job handle from ASMBO.DLL. A function in ASMBO.DLL was called with an invalid handle.

Cause/Solution:  Probable logic error – call for support


Error 3979

E 3979  No data to process

Modules:  Tasks Engines

Explanation:  There is no more data to restore and ARCserve still tries to get data from Mainframe Backup Option.

Cause/Solution:  Probable logic error – call for support.


Error 3983

E 3983 Failed to complete job, [MBO error message ]. (EC:[error code], Reason: [reason code], Command:[command Number])

Modules:  Tasks Engines

Explanation:  Error occurred when a MBO API was called

Cause/Solution:  Check the help text for MBO error messages


Error 3986

E 3986 Failed to initiate backup to LCB job, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Can not start a backup to LCB job

Cause/Solution:  Check the help text for MBO error messages


Error 3987

E 3987 Failed to initiate Mainframe Backup Option restore job, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Can not start a restore from Mainframe Backup Option job

Cause/Solution:  Check the help text for MBO error messages


Error 3988

E 3988 Failed to initiate Mainframe Backup Option full session restore job, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Can not start a full session restore from Mainframe Backup Option job

Cause/Solution:  Check the help text for MBO error messages


Error 3989

E 3989 Failed to initiate Mainframe Backup Option ordered restore job, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Can not start a ordered restore from Mainframe Backup Option job

Cause/Solution:  Check the help text for MBO error messages


Error 3990

E 3990 Failed to initiate Mainframe Backup Option scan job, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Can not start a Mainframe Backup Option scan job

Cause/Solution:  Check the help text for MBO error messages


Error 3991

E 3991 Failed to create file in LCB, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Failed to create name file and write the file header to LCB

Cause/Solution:  Check the help text for MBO error messages


Error 3992

E 3992 Failed to write data to LCB, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Failed to write file data to LCB

Cause/Solution:  Check the help text for MBO error messages


Error 3993

E 3993 Failed to finish writing a file to LCB, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Failed to write file trailer to LCB

Cause/Solution:  Check the help text for MBO error messages


Error 3994

E 3994  Failed to terminate job, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  An error occurred during the termination of a Mainframe Backup Option job

Cause/Solution:  Check the help text for MBO error messages


Error 3995

E 3995  Failed to read data from Mainframe Backup Option backup session, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  In a restore or scan operation, ARCserve fails to get data from the Mainframe Backup Option backup session.

Cause/Solution:  Check the help text for MBO error messages


Error 3996

E 3996  File restore request to Mainframe Backup Option backup session failed,  [MBO error message ]. (EC:[error code], Reason: [reason code], File ID: [id1, id2])

Modules:  Tasks Engines

Explanation:  In a point/select restore job, ARCserve needs to send the file IDs of all the files/directories to be restored to Mainframe Backup Option one by one first. This message indicates that one of the request failed.

Cause/Solution:  Probably that the file ID does not exist in the MBO database. Check the help text for MBO error messages


Error 3997

E 3997 Failed to make Mainframe Backup Option job reservation, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Any Mainframe Backup Option related backup, restore and scan operation needs to make job reservation. This message indicates that the job reservation request failed.

Cause/Solution:  Check the help text for MBO error messages


Error 3998

E 3998 Failed to start attribute stream, [MBO error message ]. (EC:[error code], Reason: [reason code])

Modules:  Tasks Engines

Explanation:  Failed to ask ARCserve Mainframe Backup Option service to end the current BOB and start the backup of attribute data.

Cause/Solution:  Check the help text for MBO error messages


Variable MBO Error Messages

"MBO is not active"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  The MBO service is not active

Action:  Start the ARCserve Mainframe Backup Option service

"MBO is shutting down"

Modules: MBOAPI.C [MBO_API.DLL], MBOMSGDM.C [MBOSVC.EXE]

Reason:  The MBO service is in the process of shutting down

Action:  Restart the ARCserve Mainframe Backup Option service and retry the job

"MBO is busy and cannot accept more work"

Modules: MBOMSGDM.C [MBOSVC.EXE]

Reason:  MBO has reached the maximum number of backup or restore jobs, and cannot allow a new backup or restore job to start

Action:  Retry after one or more backup or restore jobs have terminated

"MBO API call was made out of sequence"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  An MBO API call was made out of sequence (i.e. an MBO_GetFile() call was made after an MBO_Read())

Action:  Probable Logic Error - Call for Support

"Unknown API message was issued to MBO"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  An MBO API call was made out of context (i.e. an MBO_Open() call was made under a Restore session)

Action:  Probable Logic Error - Call for Support

"MBO was unable to fork the required process"

Modules: MBOAPIDM.C [MBOSVC.EXE]

Reason:  MBO was unable to create a new process to service the backup or restore request

Action:  Probable OS Error - Call for Support

"A reserved MBO Block Number has been specified"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  An MBO_Open call was made using an internally reserved Block Number value

Action:  Probable Logic Error - Call for Support

"An attempt to send an API message to MBO failed"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  An attempt to send an internal MBO message failed

Action:  Probable Logic Error - Call for Support

"An MBO Control message was received indicating an abnormal event"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  An internal MBO control message was received unexpectedly

Action:  Normally indicates that an MBOBCC or MBORST process has terminated abnormally during a backup or restore job respectively

"The response from MBO was not the expected response"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  The response to an internal MBO message was not the expected response

Action:  Probable Logic Error - Call for Support

"The response from MBO was too small to be a valid response"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  The response to an internal MBO message was not large enough to be a valid, expected response

Action:  Probable Logic Error - Call for Support

"The response from MBO had an invalid response queue"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  The response to an internal MBO message did not contain a valid response queue id

Action:  Probable Logic Error - Call for Support

"The decompression routine has failed"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  The decompression of an LCB Sfile failed

Action:  Probable Logic Error - Call for Support

"Virtual Storage is constrained"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  An MBO Reservation was requested and being denied due to a shortage of server virtual storage

Action:  Retry later after jobs/processes have terminated

"Init_Independent failed"

Modules: MBOAPI.C [MBO_API.DLL]

Reason:  The MBO Backup Manager thread failed to connect to the MBO service

Action:  Probable Logic Error - Call for Support


Error 4001

4001 Unable to create new process. (MODULE=file, EC=ms_error_code)

Module:

Database API

Explanation:

ARCserve failed to create a process.


Error 4002

4002 Unable to initialize Security Descriptor. (MODULE=file, EC=ms_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4003

4003 Unable to set Security Descriptor. (MODULE=file, EC=ms_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4004

4004 Unable to create file mapping. (MODULE=file, EC=ms_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4005

4005 Unable to map view file. (MODULE=file, EC=ms_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4006

4006 Unable to open registry key. (MODULE=file, KEY=registry_key, EC=ms_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4007

4007 Unable to query registry value. (MODULE=file, KEY=registry_key, EC=ms_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4008

4008 Invalid registry value. (MODULE=file, KEY=registry_key, VALUE=registry_key_value)

Module:

Database API

Cause/Solution:

The registry value is invalid.


Error 4009

4009 Wait on object error. (MODULE=file, OBJECT=object_name, EC=ms_error_code)

Module:

Database API

Cause/Solution:

Check the error code. (258=TIME OUT)


Error 4010

4010 The disk is almost full.

Module:

Database API

Cause/Solution:

The free disk spaces reached the threshold.

The default threshold is 5MB, and it is configurable.

Delete unnecessary files


Error 4101

4101 Unable to login to database engine. (DATABASE=database_engine_name, EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4102

4102 Unable to open database. (DATABASE=database_name, EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4103

4103 Unable to put database in normal mode. (MODULE=file, DATABASE=database_name, EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4104

4104 Unable to insert a record. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4105

4105 Unable to get job id. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4106

4106 Unable to add job record. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4107

4107 Unable to update job record. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4108

4108 Unable to get session id. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4109

4109 Unable to add session record. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4110

4110 Unable to update session record. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4111

4111 Unable to read session record. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4112

4112 Unable to delete session record. (MEDIA=media_name, ID=media_id, SEQ=sequence_number, EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4113

4113 Unable to delete detail record. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4114

4114 Unable to add detail record. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4115

4115 Unable to register media. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4116

4116 Unable to begin database backup. (EC=db_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4117

4117 Unable to end database backup. (EC=ms_error_code)

Module:

Database API

Cause/Solution:

Check the error code.


Error 4208

4208: Failed to load.  Last error = %d

Module:

Database API

Explanation:

ARCserve failed to load the DLL into memory.

Cause/Solution:

The DLL may not be in ARCserve home directory or ARCserve internal error.


Error 4209

4209 Failed to load function

Module:

Database API

Explanation:

This is a internal error.  ARCserve tried to load the function into memory but failed because The DLL could not be loaded.

Cause/Solution:

The DLL may not be in ARCserve home directory.


Error 4210

4210 Failed to call computer:  (Function: %s. Status=%d)

Module:

Database API

Explanation:

ARCserve failed to call the function from the remote machine.

Cause/Solution:

The status is the system return error.


Error 4211

4211 Login to computer:

Module:

Databse API

Explanation:

This message confirms that ARCserve has logged into the database in the remote machine.


Error 4212

4212  Logout from computer:

Module:

Database API

Explanation:

This message confirms that ARCserve has logged out from the database in the remote machine.


Error 4215

W4215 Unable to get tape record.

Reason:  SQL database was unable to get the tape record.

Solution:

1.	1.	Please make sure you have the correct login id and password.  You can use the ARCserve Server Admin to change the userid and password.

2.	2.	Run a Database base consistency check (run DBCC in SQL enterprise manager) on the SQL database.

3.	3.	Please make sure you have enough connections to your MS SQL server.  Every ARCserve job needs a connection.  Go to SQL Enterprise manager Server menu, SQL Server configuration pull down menu and check the connection.


Error 4216

W4216 Unable to update tape record

Reason:  SQL database was unable to update the tape record.

Solution:

1.	1.	Please make sure you have the correct login id and password.  You can use the ARCserve Server Admin to change the userid and password.

2.	2.	Run a Database base consistency check (run DBCC in SQL enterprise manager) on the SQL database.

3.	3.	Please make sure you have enough connections to your MS SQL server.  Every ARCserve job needs a connection.  Go to SQL Enterprise manager Server menu, SQL Server configuration pull down menu and check the connection.

4.	4.	Please make sure you do not run out of log space.  You can check the log size at SQL enterprise manager.


Error 4222

Module:

Database API

Cause/Solution:

RPC call failure to the remote computer.

Please make sure that the ARCserve message engine and database engine are running on the remote computer.


Error 5001

5001 Unable to register Database Engine service. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module could not register with the Service Control Manager.

Cause/Solution:

Check the ms_error_code.


Error 5002

5002 Unable to set service status for Database Engine. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module could not notify the Service Control Manager to reflect its current status.

Cause/Solution:

Check the ms_error_code.


Error 5003

5003 Unable to start service control dispatcher for Database Engine. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module failed to initialize with the Service Control Manager.

Cause/Solution:

Check the ms_error_code.


Error 5004

5004 Unable to open Service Control Manager. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to open a handle to the Service Control Manager.

Cause/Solution:

Check the ms_error_code.


Error 5005

5005 Unable to open Service. (SERVICE=service, EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to open a handle to the specified service.

Cause/Solution:

Check the ms_error_code.


Error 5006

5006 Unable to start Service. (SERVICE=service, EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to start the specified service.

Cause/Solution:

Check the ms_error_code.


Error 5007

5007 Unable to query service status. (SERVICE=service, EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to obtain status information from the specified service.  Examples of status information obtained from a service are:

SERVICE is...

    START PENDING

    STARTED

    STOP PENDING

    STOPPED

    PAUSE PENDING

    PAUSED

    RESUME/CONTINUE PENDING

Cause/Solution:

Check the ms_error_code.


Error 5008

5008 Unable to send control to Service. (SERVICE=service, EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to send control commands to the specified service. Examples of control commands sent to service are:

START, STOP, PAUSE, CONTINUE.

Cause/Solution:

Check the ms_error_code.


Error 5009

5009 Unable to set service security. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to set security information for the specified service.

Cause/Solution:

Check the ms_error_code.


Error 5201

5201 Unable to create a Process object. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to create a Process object.  A process called RDS is created for all database processing.

Cause/Solution:

Check the ms_error_code.


Error 5202

5202 Unable to create a Thread object. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to create a Thread object.

Cause/Solution:

Check the ms_error_code.


Error 5203

5203 Unable to create an Event object. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to create an Event object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 5204

5204 Unable to initialize Security Descriptor. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to initialize a Security Descriptor.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 5205

5205 Unable to set Security Descriptor. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to change a Security Descriptor.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 5206

5206 Unable to create a File Mapping object. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to create a File Mapping object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 5207

5207 Unable to map view file. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to create a map a view to a File Mapping object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 5208

5208 Unable to load a DLL module. (DLL=file, EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to find, or load a DLL file.

Cause/Solution:

Check the ms_error_code.


Error 5209

5209 Unable to free a DLL module. (DLL=file, EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable to free a previously loaded task DLL.

Cause/Solution:

Check the ms_error_code.


Error 5210

5210 Unable to get function entry point. (EC=ms_error_code)

Module:

Database Engine

Explanation:

The DBENG.EXE module was unable get a function entry point.

Cause/Solution:

Check the ms_error_code.


Error 6000

6000 Error Formatting: [ARCserve error description]

Module:

Media Engine

Explanation:

If you get this error, it is usually due to the following:

1.	An UDE (Unrecoverable Data Error)

2.	Hardware error

Cause/Solution:

First, perform the steps for media errors, then perform the steps under hardware errors.


Error 6001

6001 Error Erasing: [ARCserve error description]

Cause/Solution:

First, perform the steps for media errors, then perform the steps under hardware errors.


Error 6002

6002 Error Copying: [ARCserve error description]

Cause/Solution:

First, perform the steps for media errors, then perform the steps under hardware errors.


Error 6003

6003 Error Retensioning: [ARCserve error description]

Cause/Solution:

First, perform the steps for media errors, then perform the steps under hardware errors.


Error 6004

6004 Error Setting Compression: [ARCserve error description]

Cause/Solution:

First, perform the steps for media errors, then perform the steps under hardware errors.


Error 6005

6005 Device will not become ready - initialization required

Module:

Media Engine

Explanation:

There is some problem with the storage device.

Cause/Solution:

Power off the drive, then power back on.

Check the SCSI terminators.

Check the cables connecting your storage devices.


Error 6006

6006 Logical unit does not respond to selection

Module:

Media Engine

Explanation:

There is some problem with the storage device.

Cause/Solution:

Power off the drive, then power back on.

Check the SCSI terminators.

Check the cables connecting your storage devices.


Error 6007

6007 Logical unit failure

Module:

Media engine

Explanation:

There is some problem with the storage device.

Cause/Solution:

Power off the drive, then power back on.

Check the SCSI terminators.

Check the cables connecting your storage devices.


Error 6008

6008 Device communication failure

Cause/Solution:

This is a hardware error.


Error 6009

6009 Device communication parity error

Module:

Media engine

Explanation:

A SCSI parity error occurred.

Cause/Solution:

This is a hardware error.


Error 6010

6010 Track following positioning error

Cause/Solution:

This is a hardware error.


Error 6011

6011 Error log overflow

Cause/Solution:

Rare Media Hardware Error


Error 6012

6012 Write error - head sync error during write

Cause/Solution:

This is a hardware error.


Error 6013

6013 Unrecovered read error

Module:

Media engine

Explanation:

A command failed because a media read failed. Most likely due to bad media, but it could result from a hardware error.

Cause/Solution:

First, perform the steps for media errors, then perform the steps under hardware errors.


Error 6014

6014 Uncorrectable block encountered during read

Cause/Solution:

This is a media error.


Error 6015

6015 Error too long to correct

Cause/Solution:

This is a media error.


Error 6016

6016 Too many permanent read errors - cannot re-synchronize

Cause/Solution:

This is a media error.


Error 6017

6017 Incomplete block read (postamble not found)

Cause/Solution:

This is a media error.


Error 6018

6018 Recorded entity not found or basic media error

Cause/Solution:

This is a media error.


Error 6019

6019 Filemark or setmark not found

Cause/Solution:

Media Error or Media Hardware Error


Error 6020

6020 End of data not detected - corrupt format

Module:

Media engine

Explanation:

This media is bad.

Cause/Solution:

You can no longer use this media.


Error 6021

6021 Block sequence error

Cause/Solution:

This is a media error.


Error 6022

6022 Mechanical positioning error

Module:

Media engine

Explanation:

This is set whenever the drive has performed a mechanism retry in successfully completing a command.


Error 6023

6023 Servo - Mechanical positioning error

Cause/Solution:

This is a hardware error.


Error 6024

6024 Positioning error detected by read, space, or locate

Module:

Media engine

Explanation:

The command failed to complete successfully, or the logical position has been lost.

Cause/Solution:

This is a media error.


Error 6025

6025 Recovered with no ECC applied

Cause/Solution:

The system recovered successfully from a soft error while completing a command.


Error 6026

6026 Recovered with retries

Cause/Solution:

One or more frames has to be rewritten by the drive in order to complete a command successfully.


Error 6027

6027 Recovered with ECC applied

Cause/Solution:

The system had to use ECC to successfully complete a command.  This means that there was a bad block, but the drive successfully rewrote to another block.


Error 6028

6028 Mode select parameter error

Cause/Solution:

This is an internal error.  Please contact your reseller or Computer Associates Technical Support.


Error 6029

6029 Synchronous data transfer error

Module:

Media engine

Explanation:

An error has occurred between the controller card and the storage device.

Cause/Solution:

Disable Synchronous transfer or negotiation.  Depending on the drive, you may have to alter the settings on the board.


Error 6030

6030 Invalid command operation code

Cause/Solution:

This is an internal error.  Please contact your reseller or Computer Associates Technical Support.


Error 6031

6031 Logical block is out of range

Cause/Solution:

Rare Media Hardware Error


Error 6032

6032 Invalid element address - library

Cause/Solution:

This is an internal error.  Please contact your reseller or Computer Associates Technical Support.


Error 6033

6033 Invalid field in CCB

Cause/Solution:

This is an internal error.  Please contact your reseller or Computer Associates Technical Support.


Error 6034

6034 LUN not supported

Cause/Solution:

LUNs (Logical Unit Number) are not supported by CSI.  Libraries and stackers are supported.


Error 6035

6035 Parameter not supported - flash eeprom problem

Module:

Media engine

Explanation:

This is a firmware error.

Cause/Solution:

Call your storage device vendor.


Error 6036

6036 Write buffer permanent value invalid

Cause/Solution:

Rare Media Hardware Error


Error 6037

6037 Threshold parameters not supported

Cause/Solution:

Rare Media Hardware Error


Error 6038

6038 Not ready to ready transition

Cause/Solution:

This is a hardware error.


Error 6039

6039 Power on reset occurred

Cause/Solution:

Someone powered-on, or reset the storage device.  Another possibility is that power was lost.


Error 6040

6040 Parameters have changed

Cause/Solution:

Rare Media Hardware Error


Error 6041

6041 Mode select parameters have changed

Cause/Solution:

Rare Media Hardware Error


Error 6042

6042 Log parameters have changed

Cause/Solution:

Rare Media Hardware Error


Error 6043

6043 Copy cannot execute - host cannot disconnect

Cause/Solution:

This is an internal error.  Please contact your reseller or Computer Associates Technical Support.


Error 6044

6044 Command sequence error

Cause/Solution:

Rare Media Hardware Error


Error 6045

6045 Overwrite error on update in place

Cause/Solution:

Rare Media Hardware Error


Error 6046

6046 Tagged commands cleared by another initiator

Cause/Solution:

Rare Media Hardware Error


Error 6047

6047 Incompatible medium installed

Module:

Media engine

Explanation:

Incompatible medium installed

Cause/Solution:

Only use media that are approved by the storage device manufacturer.


Error 6048

6048 Cannot read medium - unknown format

Module:

Media engine

Explanation:

An unknown media format was used.

Cause/Solution:

Only use media that are approved by the storage device manufacturer.


Error 6049

6049 Medium format is corrupted - DDS bad at group level

Module:

Media engine

Explanation:

This media is bad.

Cause/Solution:

You need to use a new media.


Error 6050

6050 Media length error - too short to partition

Cause/Solution:

Rare Media Hardware Error


Error 6051

6051 Saving of parameters not supported

Cause/Solution:

Rare Media Hardware Error


Error 6052

6052 Sequential positioning error

Cause/Solution:

This is a media error.


Error 6053

6053 Media position error at beginning of media

Cause/Solution:

This is a media error.


Error 6054

6054 Physical end of media encountered-media position error at EOM

Module:

Media Engine

Explanation:

The storage device failed to generate an Early Warning.

Cause/Solution:

This is a hardware error.


Error 6055

6055 Reposition error

Cause/Solution:

This is a media error.


Error 6056

6056 Read past of end of medium

Module:

Media Engine

Explanation:

The storage device failed to generate an Early Warning.

Cause/Solution:

This is a hardware error.


Error 6057

6057 Illegal bit set in identify message

Cause/Solution:

Rare Media Hardware Error


Error 6058

6058 Device has not self configured yet

Module:

Media Engine

Explanation:

This is a media hardware error.

Cause/Solution:

It is not possible to send commands to the drive because mechanism tests are being executed.


Error 6059

6059 Internal ram or diagnostic failure

Cause/Solution:

This is a media hardware error.


Error 6060

6060 Diagnostics failure. Vendor unique

Cause/Solution:

This is a media hardware error.


Error 6061

6061 Unspecified fatal error

Cause/Solution:

This is a media hardware error.


Error 6062

6062 Timeout error

Cause/Solution:

This is a media hardware error.


Error 6063

6063 SCSI Message error

Cause/Solution:

This is a media hardware error.


Error 6064

6064 Internal software (firmware) error.

Cause/Solution:

This is a hardware error.


Error 6065

6065 Unexpected selection interrupt from hardware

Cause/Solution:

Rare Media Hardware Error


Error 6066

6066 EDC error detected by port

Cause/Solution:

Rare Media Hardware Error


Error 6067

6067 Select – re-select failure

Cause/Solution:

Rare Media Hardware Error


Error 6068

6068 Unsuccessful soft reset

Cause/Solution:

Rare Media Hardware Error


Error 6069

6069 SCSI parity error detected

Module:

Media Engine

Explanation:

This is a firmware error.

Cause/Solution:

You can check the cables.  If the cables are OK, contact your reseller or Computer Associates Technical Support.


Error 6070

6070 Initiator detected error message received

Cause/Solution:

Rare Media Hardware Error


Error 6071

6071 Invalid message error

Cause/Solution:

Rare Media Hardware Error


Error 6072

6072 Command phase error

Module:

Media Engine

Explanation:

Too many parity errors have occurred during an attempted Command phase.

Cause/Solution:

This is a hardware error.


Error 6073

6073 Data phase error

Module:

Media Engine

Explanation:

Too many parity errors have occurred during the Data-In and Data-Out phases of an operation.

Cause/Solution:

This is a hardware error.


Error 6074

6074 Logical unit failed self-configuration

Cause/Solution:

This is a media hardware error.


Error 6075

6075 Overlapped commands attempted

Cause/Solution:

Rare Media Hardware Error


Error 6076

6076 Write append error

Module:

Media Engine

Explanation:

If a WRITE or WRITE FILEMARKS command fails because the append point was unreadable, this error occurs.

Cause/Solution:

This is a media error.


Error 6077

6077 Write append position error - retry limit exhausted

Cause/Solution:

This is a media error.


Error 6078

6078 Timer position error

Cause/Solution:

Rare Media Hardware Error


Error 6079

6079 Erase failure

Module:

Media Engine

Explanation:

When an ERASE command fails to erase the area specified.

Cause/Solution:

This is a hardware error.


Error 6080

6080 Cassette fault

Module:

Media Engine

Explanation:

This error occurs if the drive thinks there is something wrong with the cassette, such as the media breaking.

Cause/Solution:

This is a media error.


Error 6081

6081 Media load or eject failed

Module:

Media Engine

Explanation:

The drive failed to load or eject a media.

Cause/Solution:

This can be either a medium, or a hardware error


Error 6082

6082 Unload media failure

Module:

Media Engine

Explanation:

The drive failed to load or eject a media.

Cause/Solution:

This can be either a medium, or a hardware error


Error 6083

6083 Media removal prevented

Cause/Solution:

Rare Media Hardware Error


Error 6084

6084 Drive hardware error - servo or sensor

Cause/Solution:

This is a media hardware error.


Error 6085

6085 Log exception

Cause/Solution:

Rare Media Hardware Error


Error 6086

6086 Threshold condition met

Cause/Solution:

Rare Media Hardware Error


Error 6087

6087 Log list codes exhausted

Cause/Solution:

Rare Media Hardware Error


Error 6088

6088 Mode mismatched fixed - variable

Cause/Solution:

Rare Media Hardware Error


Error 6089

6089 Excessive dryness

Cause/Solution:

The relative humidity is too low.


Error 6090

6090 Mode select failed because the media is not at LBOT

Cause/Solution:

This is an internal error.  Please contact your reseller or Computer Associates Technical Support.


Error 6091

6091 Incorrect block length

Cause/Solution:

This is a hardware error.  Please contact your reseller or Computer Associates Technical Support.


Error 6092

6092 Fatal - Uncorrectable error

Cause/Solution:

This is a hardware error.


Error 6093

6093 Possible firmware error or catastrophic drive failure

Cause/Solution:

This is a media hardware error.


Error 6094

6094 SCSI Bus Parity Error

Cause/Solution:

This is a media hardware error.


Error 6095

6095 Formatted Buffer Parity Error

Cause/Solution:

This is a media hardware error.


Error 6096

6096 media error

Cause/Solution:

This is a media error.


Error 6097

6097 Error Counter Overflow

Cause/Solution:

The maximum number of retries has been exhausted.


Error 6098

6098 Media Motion Error

Cause/Solution:

First, perform the steps for media errors, then perform the steps under hardware errors.


Error 6099

6099 Transfer Abort Error

Cause/Solution:

Rare Media Hardware Error


Error 6100

6100 Media Mark Detect Error

Cause/Solution:

This is a media error.


Error 6101

6101 Filemark Error

Cause/Solution:

This is a media error.


Error 6102

6102 Underrun Error

Cause/Solution:

This is a media error.


Error 6103

6103 Write Error 1

Cause/Solution:

This is a media error.


Error 6104

6104 Servo System Error

Cause/Solution:

This is a media hardware error.


Error 6105

6105 Formatter Error

Cause/Solution:

This is a media hardware error.


Error 6106

6106 Write Splice Error, Blank

Cause/Solution:

This is a media hardware error.


Error 6107

6107 Write Splice Error, Overshoot

Cause/Solution:

This is a media hardware error.


Error 6108

6108 No error bits are set

Cause/Solution:

Rare Media Hardware Error


Error 6109

6109 Unable to initialize list. Possibly out of memory.

Cause/Solution:

Free up machine memory.  Close any open applications.


Error 6300

6300 Windows NT SCSI PORT Error

Module:

Media Engine

Explanation:

Problem with sending a SCSI command to SCSI device.


Error 6301

6301 Media Engine Initialization Error

Module:

Media Engine

Explanation:

Check error code.


Error 6302

6302 Media Engine Running Already

Module:

Media Engine

Explanation:

Media Engine has already been started and is running.


Error 6303

6303 Communication Initialization Error

Module:

Media Engine

Explanation:

Check error code.


Error 6304

6304 Unexpected SCSI Sense Code

Module:

Media Engine

Explanation:

SCSI error, check error code.


Error 6305

6305 Problem with current SCSI port handle, forced to use the original port handle ABSL:adapter_number/bus_number/scsi_id/lun

Module:

Media Engine

Explanation:

Check error code.


Error 6306

6306 Can't open SCSI port handle ABSL:adapter_number/bus_number/scsi_id/lun

Module:

Media Engine

Explanation:

Check error code.


Error 6330

6330 Media S/an Thread Job Creation Error

Module:

Media Engine

Explanation:

Check error code. Maximum number of jobs may have been reached.


Error 6331

6331 Media Scan Thread Creation Error

Module:

Media Engine

Explanation:

Not enough resources.


Error 6332

6332 Library Scan Thread Job Creation Error

Module:

Media Engine

Explanation:

Not enough resources.


Error 6333

6333 Library Scan Thread Creation Error

Module:

Media Engine

Explanation:

Not enough resources.


Error 6401

6401 Library drive is missing

Module:

Media Engine

Explanation:

ARCserve does not detect a library drive.


Error 6402

6402 Session couldn't be repaired

Module:

Media Engine

Cause/Solution:

This is a media error or a media hardware error.


Error 6500

6500 Client connect to media failed.

Module:

Media Engine

Explanation:

Not enough resources.


Error 6501

6501 Job denied: media_error_code

Module:

Media Engine

Explanation:

Not enough resources.


Error 6502

6502 Find next session failed

Module:

Media Engine

Cause/Solution:

This is a media error or a media hardware error.


Error 6503

6503 Start session failed

Module:

Media Engine

Explanation:

Not enough resources.


Error 6504

6504 End session failed

Module:

Media Engine

Explanation:

Not enough resources.


Error 6505

6505 End job failed

Module:

Media Engine

Explanation:

Not enough resources.


Error 6506

6506 Suspend job failed

Module:

Media Engine

Explanation:

Not enough resources.


Error 6900

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6901

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6902

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6903

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6904

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6905

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6906

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6907

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6908

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6909

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6910

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6911

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6912

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6913

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6914

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6915

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6916

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6917

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6918

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6919

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6920

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6921

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6922

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6923

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6924

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6925

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6965

W6965 A library operation has been attempted that is invalid at this time.

Reason:  This is an alert message generated by media device.

Action:  Please contact the device vendor for more details.


Error 6995

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6996

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6997

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6998

Module:

Media Engine

Explanation:

This is a Media Alert specific error. Follow the instructions listed in the ARCserve Activity Log, or refer to your media device manual for more information.


Error 6999

6999 Unknown Error Code: media_error_code


Error 7001

7001 Unable to register Message Engine service. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module could not register with the Service Control Manager.

Cause/Solution:

Check the ms_error_code.


Error 7002

7002 Unable to set service status for Message Engine. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module could not notify the Service Control Manager to reflect its current status.

Cause/Solution:

Check the ms_error_code.


Error 7003

7003 Unable to start service control dispatcher for Message Engine. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module failed to initialize with the Service Control Manager.

Cause/Solution:

Check the ms_error_code.


Error 7004

7004 Unable to open Service Control Manager. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to open a handle to the Service Control Manager.

Cause/Solution:

Check the ms_error_code.


Error 7005

7005 Unable to open Service. (SERVICE=service, EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to open a handle to the specified service.

Cause/Solution:

Check the ms_error_code.


Error 7006

7006 Unable to start Service. (SERVICE=service, EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to start the specified service.

Cause/Solution:

Check the ms_error_code.


Error 7007

7007 Unable to query service status. (SERVICE=service, EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to obtain status information from the specified service.  Examples of status information obtained from a service are:

SERVICE is...

    START PENDING

    STARTED

    STOP PENDING

    STOPPED

    PAUSE PENDING

    PAUSED

    RESUME/CONTINUE PENDING

Cause/Solution:

Check the ms_error_code.


Error 7008

7008 Unable to send control to Service. (SERVICE=service, EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to send control commands to the specified service.  Examples of control commands sent to service are:

START, STOP, PAUSE, CONTINUE.

Cause/Solution:

Check the ms_error_code.


Error 7009

7009 Unable to set service security. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to set security information for the specified service.

Cause/Solution:

Check the ms_error_code.


Error 7201

7201 Unable to create a Process object. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to create a Process object.

Cause/Solution:

Check the ms_error_code.


Error 7202

7202 Unable to create a Thread object. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to create a Thread object.

Cause/Solution:

Check the ms_error_code.


Error 7203

7203 Unable to create an Event object. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to create an Event object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7204

7204 Unable to initialize Security Descriptor. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to initialize a Security Descriptor.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7205

7205 Unable to set Security Descriptor. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to change a Security Descriptor.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7206

7206 Unable to create a File Mapping object. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to create a File Mapping object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7207

7207 Unable to map view file. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to create a map a view to a File Mapping object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7208

7208 Unable to load a DLL module. (DLL=file, EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to find, or load a DLL file.

Cause/Solution:

Check the ms_error_code.


Error 7209

7209 Unable to free a DLL module. (DLL=file, EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to free a previously loaded task DLL.

Cause/Solution:

Check the ms_error_code.


Error 7210

7210 Unable to get function entry point. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable get a function entry point.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7211

7211 Unable to create a Named Pipe object. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to create a Named Pipe object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7212

7212 Unable to read from Named Pipe object. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to read from a Named Pipe object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7213

7213 Unable to write to Named Pipe object. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to write to a Named Pipe object.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


New ASLOG Messages


Error 7214

7214 Exception ms_error_code during Logon operation

Module:

Message Engine

Explanation:

The exception has occurred attempting to logon on the system.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7215

7215 Failed to open registry key <key name>. (EC=ms_error_code)

Where <key name> is the name of the ARCserve product.

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to open the registry key.

Cause/Solution:

Possible registry database corruption.

Try to reinstall relative product.


Error 7216

7216 Failed to enumerate registry key <key name>. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to enumerate values under <key name>.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7217

7217 There are no ARCserve Products installed.

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to find any ARCserve product.

Cause/Solution:

Reinstall ARCserve products.


Error 7218

7218 Unable to obtain a list of domains to broadcast to

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to enumerate Microsoft network.

Cause/Solution:

Check the ms_error_code.

Possible Windows NT network software or hardware problems.


Error 7219

7219 Unable allocate enough memory. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable allocate enough memory.

Cause/Solution:

Check the amount of available memory.  Close any other applications and retry.


Error 7220

7220 Failed to enumerate Microsoft Network resources. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to enumerate Microsoft Network resources.

Cause/Solution:

Check the ms_error_code.

Possible Windows NT network software or hardware problems.


Error 7221

7221 Microsoft Network is not found. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to find Microsoft Network.

Cause/Solution:

Check the ms_error_code.

Possible Windows NT network software or hardware problems.


Error 7222

7222 Unable to open enumeration of Microsoft network resources. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to open the handle to the Microsoft network resources.

Cause/Solution:

Check the ms_error_code.

Possible Windows NT network software or hardware problems.


Error 7223

7223 Failed to start up WINSOCK.DLL. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to load Winsock.dll.

Cause/Solution:

Check the ms_error_code.

Install Winsock.dll from your Windows NT distribution diskettes.


Error 7224

7224 Failed to create socket. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to create socket. This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7225

7225 Failed to bind socket. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to bind socket.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7226

7226 Failed to set socket option. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to set socket option.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7227

7227 Failed to create mailslot-server. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was failed to create the ARCserve mailslot server.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7228

7228 Failed to write to mailslot. (Domain Name=domain_name, EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility failed to send a message to the ARCserve mailslot server. This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7229

7229 Unable to send information using socket. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility was unable to send information using socket.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7230

7230 Failed to create mailslot-client. (Domain Name=domain_name, EC=ms_error_code)

Module:

Message Engine

Explanation:

The AutoDiscovery facility failed to create an ARCserve mailslot client.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7231

7231 Unable to get mailslot information. (EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to get mailslot information.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7232

7232 Failed to read from mailslot.	(EC=ms_error_code)

Module:

Message Engine

Explanation:

The MSGENG.EXE module was unable to read from mailslot.  This is an internal error.

Cause/Solution:

Check the ms_error_code.


Error 7237

7237 Potential License tampering has occurred.

Module:

Message Engine

Explanation:

The MSGENG.EXE module found CRC mismatch in the ARCserve product license information.

Cause/Solution:

Reinstall ARCserve product


Error 7238

7238 ARCserve License Violation!.

Module:

Message Engine

Explanation:

The MSGENG.EXE module found that the same serial number has been used by different ARCserve Servers.

Cause/Solution:

Reinstall ARCserve Server using different CD-key


Error 8000

8000 Critical Error, library must have at least one storage device assigned [Device:device number][library vendor description].

Module:

Library

Explanation:

Library has no storage device assigned.

Cause/Solution:

Go to Library Option Setup and assign a storage device to the library.


Error 8002

8002 Detected library with no magazine mounted [Device:device number][library vendor description].

Module:

Library

Explanation:

Initializing the library without a magazine.

Cause/Solution:

Install the library magazine.


Error 8003

8003 Media manually ejected from Drive [Device number], in library [Device:device number][library vendor description].

Module:

Library

Explanation:

ARCserve detected that a media was manually ejected from a library media drive.

Cause/Solution:

You  normally should not eject a media from the library drive.


Error 8004

8004 Media manually inserted in drive [Device number], in library [Device:device number][library vendor description].

Module:

Library

Explanation:

ARCserve detected that a media was manually inserted into a library storage device.

Cause/Solution:

You  normally should not insert a media into a library drive manually.


Error 8006

8006 Slot full, can't move media to home slot [Slot number] from drive [Device number] in library [Device:device number][library vendor description].

Module:

Library

Explanation:

ARCserve detects that a media's home slot is occupied.

Cause/Solution:

A  media was placed into the home slot of another media.


Error 8007

8007 Door is open while initializing library [Device:device number][library vendor description].

Module:

Library

Explanation:

Door is open.

Cause/Solution:

Close the door.


Error 8008

8008 Library Failure: Mechanical positioning [Device:device number][library vendor description].

Module:

Library

Explanation:

Hardware problem.

Cause/Solution:

Check Library and resolve any mechanical problem, shutdown, and reboot.


Error 8009

8009 Library Failure: Internal target [Device:device number][library vendor description].

Module:

Library

Explanation:

Hardware problem.

Cause/Solution:

Check Library and resolve any mechanical problem, shutdown, and reboot.


Error 8010

8010 Library Failure: component [Component number], [Device:device number][library vendor description].

Module:

Library

Explanation:

Hardware problem.

Cause/Solution:

Check Library and resolve any mechanical problem, shutdown, and reboot.


Error 8011

8011 Library Failure: Configuration [Device:device number][library vendor description].

Module:

Library

Explanation:

Hardware problem.

Cause/Solution:

Check Library and resolve any mechanical problem, shutdown, and reboot.


Error 8012

8012 Library Failure: Media load-eject [Device:device number][library vendor description].

Module:

Library

Explanation:

Hardware problem.

Cause/Solution:

Check Library and resolve any mechanical problem, shutdown, and reboot.


Error 8013

8013 Library Power on reset [Device:device number][library vendor description].

Module:

Library

Explanation:

Hardware problem.

Cause/Solution:

Check Library and resolve any mechanical problem, shutdown, and reboot.


Error 8014

8014 Library Failure: Manual intervention required [Device:device number][library vendor description].

Module:

Library

Explanation:

Hardware problem.

Cause/Solution:

Check Library and resolve any mechanical problem, shutdown, and reboot.


Error 8015

8015 Critical Error, no free slot available [Device:device number][library vendor description].

Module:

Library

Explanation:

Full library condition.

Cause/Solution:

The Library magazine has been completely filled and also has media in the library storage device.


Error 8016

8016 Destination slot is occupied, moving media to a free slot, [Device:device number][library vendor description].

Module:

Library

Explanation:

A media was inserted into a slot without subsequently doing an inventory.

Cause/Solution:

ARCserve is trying to move a media into a slot which is now full.


Error 8020

8020 Failed to inventory slot(s) (EC=error string)[Device:device number][library vendor description].

Module:

Library

Explanation:

Check error string.

Cause/Solution:

Solution varies.


Error 8021

8021 Failed to erase media in slot [Slot number] (EC=error string)[Device:device number][library vendor description].

Module:

Library

Explanation:

Check error string.

Cause/Solution:

Solution varies.


Error 8022

8022 Failed to format media in slot [Slot number] (EC=error string)[Device:device number][library vendor description].

Module:

Library

Explanation:

Check error string.

Cause/Solution:

Solution varies.


Error 8023

8023 Failed to mount magazine [Magazine number] (EC=error string)[Device:device number][library vendor description].

Module:

Library

Explanation:

Check error string.

Cause/Solution:

Solution varies.


Error 8024

8024 Failed to dismount magazine [Magazine number] (EC=error string)[Device:device number][library vendor description].

Module:

Library

Explanation:

Check error string.

Cause/Solution:

Solution varies.


Error 8025

8025 Failed to clean storage device [Device number] (EC=error string)[Device:device number][library vendor description].

Module:

Library

Explanation:

Check error string.

Cause/Solution:

Solution varies.


Error 8026

8026 Failed to return media from device [Device number] to slot (EC=error string)[Device:device number][library vendor description].

Module:

Library

Explanation:

Check error string.

Cause/Solution:

Solution varies.


Error 8027

8027 Failed to import media to slot [Slot number] (EC=error string)[Device:device number][library vendor description].

Module:

Library

Explanation:

Check error string.

Cause/Solution:

Solution varies.


Error 8028

8028 Failed to export media from slot [Slot number] (EC=error string)[Device:device number][library vendor description].

Module:

Library

Explanation:

Check error string.

Cause/Solution:

Solution varies.


Error 8501

8501 Failed to initialize the connection.  Make sure TCP/IP driver is installed.

Module:

Backup Agent

Explanation:

ASNT failed to initialize the TCP/IP socket for remote backup.  One of the possibilities is the absence of the TCP/IP driver.


Error 8502

8502 Failed to initialize the connection.  Make sure IPX/SPX driver is installed.

Module:

Backup Agent

Explanation:

ASNT failed to initialize the IPX/SPX socket for remote backup.  One of the possibilities is the absence of the IPX/SPX driver.


Error 8511

8511 Failed to connect with client agent.  (ADDRESS=Network address).

Module:

Backup Agent

Explanation:

ASNT cannot reach the agent at the specified address.  The address could be incorrect or the agent at the specifies address is not up.


Error 8512

8512 Invalid client agent address format.  (ADDRESS=Network).

Module:

Backup Agent

Explanation:

The format of the TCP/IP or IPX/SPX address is incorrect.


Error 8521

8521 Backup daemon failed to receive data from the client agent.  (EC=error code).

Module:

Backup Agent

Explanation:

Not used.


Error 8522

8522 Failed to receive data from the client agent.  (EC=error code).

Module:

Backup Agent

Explanation:

ASNT could not receive data because the socket could not be reset or timed out.


Error 8523

8523 Failed to send data to the client agent.  (EC=error code).

Module:

Backup Agent

Explanation:

ASNT could not send data because the socket could not be reset or it timed out.


Error 8524

8524 Received unrecognized command from the client agent.  (COMMAND=command id).

Module:

Backup Agent

Explanation:

ASNT received incorrect data from the agent.  Stop the job and retry the operation.


Error 8525

8525 Failed to process the volume list from the client agent.

Module:

Backup Agent

Explanation:

ASNT failed to process the volume list sent from the agent.  The backup operation will not be interrupted.  However, if backup with compare is performed, compare will not be performed.


Error 8531

8531 Request denied by the client agent.

Module:

Backup Agent

Explanation:

Client agent rejects the access request from ASNT.  Check the activity log in the client agent for the causes.


Error 8532

8532 Request denied by the client agent.  Client agent is busy.

Module:

Backup Agent

Explanation:

Client agent rejects the access request from ASNT because the agent is currently processing other jobs.


Error 8533

8533 Request denied by the client agent.  User or password is invalid.

Module:

Backup Agent

Explanation:

The Client Agent has rejected the access request from ASNT because the user account or password is incorrect.


Error 8601

8601 Failed to connect agent.  (AGENT=agent name, EC=error message/code)

Module:

Backup Agent

Explanation:

ARCserve Failed to connect Backup Agent since Backup Agent returned an error with one of the following reasons:

1.	Backup Agent DLL doesn't exist in the agent home directory.

2.	Failed to load the DLL into memory. It might be due to the insufficient virtual memory size.

3.	Invalid user id or password for the Backup Agent.

4.	Backup Agent RPC Server service is not running on the remote server.


Error 8602

8602 Failed to read from database.  (DBNAME=object name, EC=error message/code)

Module:

Backup Agent

Explanation:

The Backup Agent error (EC=error message/code) occurs while Backup Agent reads data stream in a backup object(DBNAME=object name) from Database server to ARCserve.

Check the Backup Agent Log file for details.


Error 8603

8603 Failed to write to database.  (DBNAME=object name, EC=error message/code)

Module:

Backup Agent

Explanation:

The Backup Agent error (EC=error message/code) occurs while Backup Agent writes data stream from ARCserve to a target object(DBNAME=object name) in Database server.

Check the Backup Agent Log file for details.


Error 8604

8604 Failed to start backup.  (DBNAME=object name, EC=error message/code)

Module:

Backup Agent

Explanation:

Failed to start backing up an object(DBNAME=object name) since:

1.	 Backup Agent failed to put a backup object in a backup mode or

2.	The security for Backup Agent doesn't have enough privilege to proceed a backup.


Error 8605

8605 Failed to start restore.  (DBNAME=object name, EC=error message/code)

Module:

Backup Agent

Explanation:

Failed to start restoring a backed up image to a target object(DBNAME=object name) since Backup Agent failed to put the target object in a restore mode.

Cause/Solution:

Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8606

8606 Failed to start striping backup.  (DBNAME=object name, EC=error message/code)

Module:

Backup Agent

Explanation:

Backup Agent failed to put a backup object(DBNAME=object name)  in striping backup mode.

Cause/Solution:

Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8607

8607 Failed to start striping restore.  (DBNAME=object name, EC=error message/code)

Module:

Backup Agent

Explanation:

Backup Agent failed to put the target object(DBNAME=object name) in striping restore mode.

Cause/Solution:

Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8608

8608 Failed to enumerate databases.  (EC=error message/code)

Module:

Backup Agent

Explanation:

Backup Agent failed to get the list of sub-objects (for example, table spaces, tables, or folders.. etc.) under the Database server.

Cause/Solution:

Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8609

8609 Failed to enumerate files.  (EC=error message/code)

Module:

Backup Agent

Explanation:

Backup Agent failed to get the list of files belongs to the backup object.

Cause/Solution:

Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8610

8610 Failed to get database information.  (EC=error message/code)

Module:

Backup Agent

Explanation:

Backup Agent failed to get the detail information such as file lists for the object, the last backup time, database size, log size, etc.

Cause/Solution:

Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8611

8611 Failed to enumerate dbagents.  (EC=error message/code)

Module:

Backup Agent

Explanation:

ARCserve failed to get the list of all the Backup Agents existing on the target server.

Check the Backup Agent Log file for details.


Error 8612

8612 DBagent RPC error.  (EC=error message/code)

Module:

Backup Agent:

Explanation:

Backup Agent got an error from RPC Server service. It could be a network problem.

Cause/Solution:

Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8613

8613 Failed to get all the excluded files.  (EC=error message/code)

Module:

Backup Agent

Explanation:

ARCserve failed to get the file lists which should be excluded in file system backup to avoid sharing violation error when the Database Server is running.

Cause/Solution:

Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8617

8617 Failed to end restore.  (DBNAME=object name, EC=error message/code)

Module:

Backup Agent

Explanation:

Backup Agent failed to recover the database after a restore job.

Cause/Solution:

Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8618

8618 Failed to verify.  (DBNAME=object name, EC=error message/code)

Module:

Backup Agent

Explanation:

Backup Agent found that backup image and restore image are different in terms of checksum.


Error 8619

8619	ASLE_DSA_WARNING_VERIFY  "Unable to verify. (DBNAME=object name, No checksum in the backup)"

Module:

Backup Agent

Explanation:

ARCserve is unable to verify if the backup image of DBNAME=object name is same to the restored image in terms of checksum since the checksum value was not generated in backup time.  The backup option "Generate a CRC check" should have been set when the backup job was submitted.


Error 8621

8621	ASLE_DSA_WARNING_XCHG_CLEANUP "Failed to clean up the connection with Database server. (AGENT=agent name)"

Module:

Backup Agent

Explanation:

Backup Agent=(agent name) was failed to close all the handles it grabbed during the backup/restore.  Internal error in Backup agent or Database server. Check Backup Agent log file for the detail.


Error 8622

8622	ASLE_DSA_WARNING_XCHG_DISCONNECT	"Failed to disconnect the connection with Database server. (AGENT=agent name)"

Module:

Backup Agent

Explanation:

Backup Agent(=agent name) was failed to close the connection with Database server after backup/restore was finished.  Internal error in Backup agent or Database server.  Check Backup Agent log file for the detail.


Error 9001

9001 Unable to allocate memory. (SIZE=size)

Module:

Miscellaneous error messages

Explanation:

ASTASK cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory.


Error 9002

9002 Unable to allocate memory. (BLOCKS=blocks, SIZE=size)

Module:

Miscellaneous error messages

Explanation:

ASTASK cannot allocate the needed memory.

Cause/Solution:

Check the amount of available memory.


Error 9003

9003 Unable to execute command. (CMD=command, EC=ms_error_code)

Module:

Miscellaneous error messages

Explanation:

ASTASK cannot execute the specified command line.

Cause/Solution:

Check the error code.


Error 9004

9004 Unable to create message box. (EC=ms_error_code)

Module:

Miscellaneous error messages

Explanation:

ASTASK cannot create a message box.

Cause/Solution:

Check the error code.


IMAGE OPTION


Error 11000

11000       The Source Drive is not a local hard drive. (Drive=DRIVE)

Module:

Image option

Cause/Solution:

Image Option can backup/restore only local hard drives.


Error 11001

11001       Cannot open drive.(Drive=DRIVE, Error=Error Code)

Module:

Image option

Cause/Solution:

Image Option is unable to open the hard drive for direct access. Close

   all applications running from the drive.


Error 11002

11002       GetPartition Type Error. (Error=Error Code)

Module:

Image option

Cause/Solution:

NT reports a partition type not supported by Image Option. Image option supports FAT & NTFS partition only.


Error 11003

11003       Source volume is empty

Module:

Image option

Cause/Solution:

There are no files/directory on source drive.


Error 11004

11004       Cannot Locate $FILE_NAME Attribute

Module:

Image option

Cause/Solution:

Unable to locate the $FILE_NAME attribute which contains the file details for a particular file(s). Possibly a corrupt disk. Run CHKDSK.


Error 11005

11005       IndexAllocError, Not enough memory

Module:

Image option

Cause/Solution:

NTFS traversal initialization failed, because of not enough memory. Close

   other running applications and try again.


Error 11006

11006       IndexAllocError,  Cannot Locate VCN=Virtual Cluster Number

Module:

Image option

Cause/Solution:

NTFS traversal initialization failed, cannot locate a VCN. Possibly a corrupt disk. Run CHKDSK.


Error 11007

11007       Invalid Index Allocation Header Signature

Module:

Image option

Cause/Solution:

NTFS traversal initialization failed, Invalid index allocation header signature. Possibly a corrupt disk. Run CHKDSK.


Error 11008

11008       Error SetFilePointer. (Error=Error Code)

Module:

Image option

Cause/Solution:

Error SetFilePointer.


Error 11009

11009       Can't Locate File Rec Segment

Module:

Image option

Cause/Solution:

NTFS traversal initialization failed, can't locate a file record segment

   in MFT. Possibly a corrupt disk. Run CHKDSK.


Error 11010

11010       Can't Locate SECURITY_ATTRIBUTE in FileRecSeg From AttrList

Module:

Image option

Cause/Solution:

The attribute that defines the security of a file couldn't be located in the file record segment. Possibly a corrupt disk. Run CHKDSK.


Error 11011

11011       Cannot Move File. (Source=File Name, Target=File Name, Error=Error Code)

Module:

Image option

Cause/Solution:

Restoring active file failed.


Error 11012

11012       Some inconsistencies detected on the volume, please run chkdsk

Module:

Image option

Cause/Solution:

Disk file structure is corrupted. Run CHKDSK.


Error 11013

11013       Can't Split a Compressed Fragment, or fragment < MissingClusters

Module:

Image option

Cause/Solution:

Failed to analyze a NTFS compressed file. Possibly a corrupt disk. Run CHKDSK.


Error 11014

11014       Cannot Open Dir to set compression.(Dir=Directory, Error=Error Code)

Module:

Image option

Cause/Solution:

Failed to set compression to the directory.


Error 11015

11015       Cannot set Compression for Dir. (Dir=Directory, Error=Error Code)

Module:

Image option

Cause/Solution:

Failed to set compression to the directory.


Error 11016

not used


Error 11017

11017       Cannot set volume label. (Drive=DRIVE, VolLabel=Volume Label)

Module:

Image option

Cause/Solution:

Failed to set the volume label. Possibly corrupt disk. Run CHKDSK.


Error 11018

11018       Target volume is smaller than source volume

Module:

Image option

Cause/Solution:

Attempt to restore an image backup of a drive bigger than the target drive. Select a drive bigger or same as the source drive.


Error 11019

not used


Error 11020

not used


Error 11021

11021       unknown File System : FILE SYSTEM

Module:

Image option

Cause/Solution:

Unknown file system. Possibly an unformatted partition or a corrupt disk. Run CHKDSK.


Error 11023

11023       Invalid Directory Structure Signature

Module:

Image option

Cause/Solution:

The Directory structure signature from the media doesn't match.


Error 11024

11024       Invalid Cluster Mapping Signature

Module:

Image option

Cause/Solution:

The Cluster Mapping structure signature from the media doesn't match.


Error 11025

11025       Invalid ACL List Signature

Module:

Image option

Cause/Solution:

The ACL list structure signature from the media doesn't match.


Error 11026

11026       Invalid ACL Audit List Signature

Module:

Image option

Cause/Solution:

The ACL Audit list signature from the media doesn't match.


Error 11027

11027       Cannot lock target volume

Module:

Image option

Cause/Solution:

Failed to lock a volume for exclusive access. Image mode restore requires all applications running from the target volume to be closed. Close all applications running from the target volume.


Error 11028

11028       The Volume was backed up without file scanning, Cannot do restore to NT volume

Module:

Image option

Cause/Solution:

Restore to NT system volume can be done only from the backup sessions that have file scan information.


Error 11029

11029       Error Setting Security. (Error=Error Code, File=File Name)

Module:

Image option

Cause/Solution:

Failed to set security for file. Check Error Code.


Error 11030

11030       DeCompressBuffer Error. (Error=Error Code, File=File Name)

Module:

Image option

Cause/Solution:

NTFS decompression algorithm failed. Check Error Code.


Error 11031

11031       Error Setting security. (File=File Name, Error=Error Code)

Module:

Image option

Cause/Solution:

Failed to set security for file. Check Error Code.


Error 11032

11032       Cannot Lock Target Volume.  Please Close all applications accessing the drive and try again.

Module:

Image option

Cause/Solution:

Failed to lock a volume for exclusive access. Image mode restore requires all applications running from the target volume to be closed. Close all applications running from the target volume.


Error 11033

11033       The Volume was backed up without file scanning, cannot merge session.

Module:

Image option

Cause/Solution:

The session doesn't have file scan information. Cannot merge session.


Error 11034

11034       The Volume was backed up without file scanning, cannot scan session.

Module:

Image option

Cause/Solution:

The session doesn't have file scan information. Cannot scan session.


Error 11042

11042       Image Session # is incomplete and unusable

Module:

Image option

Cause/Solution:

The image Session is incomplete. Cannot restore from an incomplete image session.


Error 11045

11045       Unable to access drive DRIVE

Module:

Image option

Cause/Solution:

Failed to access drive in direct mode. Close all applications running from the drive and try again.


Error 11046

11046       Invalid partition type for drive DRIVE

Module:

Image option

Cause/Solution:

NT reports a partition type not supported by Image Option. Image option supports FAT & NTFS partition only.


Error 11047

11047       Not enough space for restore. Free Space Required #KB, Available #KB

Module:

Image option

Cause/Solution:

While restoring an NT system drive or a drive that has ARCserve installed,  some extra free disk space is required. The target drive doesn't have enough free space to complete the restore operation.


Error 11048

11048       Error setting registry to delete files on reboot

Module:

Image option

Cause/Solution:

Failed to set registry to delete temporary files during next reboot.


Error 11049

11049       Read from drive failed (Error=Error Code)

Module:

Image option

Cause/Solution:

Failed to read from drive. Check Error Code.


Error 11050

11050       GetQueuedCompletionStatus failed. (Error=Error Code)

Module:

Image option

Cause/Solution:

GetQueuedCompletionStatus failed. Check Error Code.


Error 11051

11051       Source Drive is not a local hard drive. (Drive=DRIVE)

Module:

Image option

Cause/Solution:

Image Option can backup/restore only local hard drives.


Error 11052

11052       Write to drive failed (Error=Error Code)

Module:

Image option

Cause/Solution:

Failed to write to disk. Check Error Code.


Error 11053

11053       Cannot set volume label. (Drive=DRIVE, VolLabel=Volume Label)

Module:

Image option

Cause/Solution:

Failed to set volume label. Check Error Code.


Error 11054

11054   Failed to write to Dir Struct file. (Error=Error Code)

Module:

Image option

Cause/Solution:

Failed to create Directory structure file used for storing file scan information. Check Error Code.


Error 11055

11055  Failed to write to Cluster Mapping File. (Error=Error Code)

Module:

Image option

Cause/solution:

Failed to create Cluster Mapping File used. Check Error Code.


Error 6600

TSI_E6600  Formatting (RAID Device=RAID Device Number, Device=%d, Error Code=%d)

Module:

RAID option

Cause/Solution:

Usually a media or hardware problem.  Please check the media and hardware.


Error 6601

TSI_E6601  Erasing (RAID Device=RAID Device Number, Device=%d, Error Code=%d)

Module:

RAID option

Cause/Solution:

Usually a media or hardware problem.  Please check the media and hardware.


Error 6602

TSI_E6602  Ejecting (RAID Device=RAID Device Number, Device=%d, Error Code=%d)

Module:

RAID option

Cause/Solution:

Usually a hardware problem.  Please check the hardware.


Error 6603

TSI_E6603  Failed positioning (RAID Device=RAID Device Number, Device=%d)

Module:

RAID option

Cause/Solution:

Failed to position read/write head to the proper location to start an operation.   Usually due to media error or hardware error.  Please check the media and hardware.


Error 6604

TSI_E6604  Failed to write (RAID Device=RAID Device Number, Device=%d)

Module:

RAID option

Cause/Solution:

Failed to write data to media. Usually due to media error or hardware error.  Please check the media and hardware.


Error 6605

TSI_E6605  Failed to read (RAID Device=RAID Device Number, Device=%d)

Module:

RAID option

Cause/Solution:

Failed to read data from media.  Usually due to media error or hardware error.  Please check the media and hardware.


Error 6606

TSI_E6606  Failed positioning to link info (RAID Device=RAID Device Number, Device=%d)

Module:

RAID option

Cause/Solution:

Failed to position read/write head to the proper location to start read the link info.  Usually due to media error or hardware error.  Please check the media and hardware.


Error 6607

TSI_E6607  Failed reading link info (RAID Device=RAID Device Number, Device=%d)

Module:

RAID option

Cause/Solution:

Failed reading the link info.  Usually due to media error or hardware error. Please check the media and hardware.


Error 6608

TSI_E6608  Media length mismatch (RAID Device=RAID Device Number, Device=%d)

Module:

RAID option

Explanation:

RAID tape set has tapes with different amount of data on it.  This could happen if in a fault tolerant raid tape set, one tape was removed and a backup was done and the missing tape is brought in again.

Cause/Solution:

A media is shorter.

Usually due to a previous media error or hardware error.  Please check the media and hardware.  It is possible to recreate this media by using the REBUILD command.

One of the tape drives in the Level 1 RAID had failed during the last backup to the tape set, and, as a result, the data on one tape is less than the data on the other. ARCserve uses the tape with maximum data on it and continues the job.


Error 6610

TSI_E6610  Too many drive failures, operation aborted (RAID Device=RAID Device Number)

Module:

RAID option

Explanation:

More than one tape drive has failed in a RAID, the job cannot continue.

Cause/Solution:

Too many drive failure to continue the operation.

Usually due to a media error or hardware error.


Error 6611

TSI_E6611  "Cleaning Tape Expired.  Please replace cleaning tape"

Explanation:

Cleaning tape used has expired, please replace the cleaning tape.


Error 6612

TSI_E6612  "Tape drive requested cleaning"

Explanation:

The specified drive required cleaning, if automatic cleaning is enabled and a cleaning tape is installed ARCserve will perform an automatic cleaning.


Error 6614

TSI_E6614	Connection Lost To Primary Server

Explanation: The tape engine on the SANO distributed server cannot communicate to its primary server. Tape engine on the primary server may be down or there may be a network problem.


Error 6615

TSI_E6615	"Disabling tape drive, Tape drive requires cleaning, but unable to do automatic cleaning (Device=%d)"

Explanation: The specified tape drive has requested cleaning, but tape engine is unable to do an automatic cleaning either because there is no cleaning tape in the library or the cleaning tape has expired. Drive will be disabled until a manual cleaning is done on the drive.


Error 6616

TSI_E6616	"Please do a manual cleaning from the Device Manager to enable Tape drive"

Explanation: Tape drive is marked as disabled as the drive has requested cleaning, a manual cleaning has to be performed to enable the drive again.


Error 6617

TSI_E6617	"Enabling tape drive, Required tape cleaning successfully done (Device=%d)"

Explanation: User has done a manual cleaning on a tape drive that was disabled by tape engine because the drive had requested a cleaning. The tape drive has been made available.


Error 6620

SI_E6620  Non-tape or optical device assigned (RAID Device=RAID Device Number)

Module:

RAID option

Cause/Solution:

ARCserve RAID cannot have non-tape devices.

Please run RAID setup to reconfigure your RAID Devices.


Error 6621

 TSI_E6621  Incompatible device assigned (RAID Device=RAID Device Number)

Module:

RAID option

Cause/Solution:

A non-media or optical device assigned to the RAID Device.  Please run RAID setup to reconfigure your RAID Devices.


Error 6622

 TSI_E6622  No device assigned (RAID Device=RAID Device Number)

Module:

RAID option

Cause/Solution:

A RAID Device has no device assigned. Please run RAID setup to assign devices to the RAID Devices.


Error 6623

 TSI_E6623  Level has been changed from Level 5 to Level 0 (RAID Device=RAID Device Number)

Module:

RAID option

Cause/Solution:

Not enough devices to form a Level 5 RAID Device.  Level 5 requires a minimum of 3 devices. Usually due to a hardware failure.

When the ARCserve Tape engine initializes, it checks each RAID and make sure that all RAID devices are configured correctly. If it finds a RAID that is configured as Level 5 and it doesn't find a minimum of 3 drives required for level 5 in RAID, it automatically changes the level to 0.  (This can happen if by mistake one of the tape drives is not switched on when NT boots up. To access the devices switched on after NT boots up run any utility that re-scans the SCSI bus. WINDISK.EXE is one).


Error 6624

TSI_E6624	"ACSLS:acs_mount error "

Explanation: ACSLS mount command failed with an error


Error 6625

TSI_E6625	"ACSLS:Get response error "

Explanation: An ACSLS command has return an error response


Error 6626

TSI_E6626	"ACSLS:Please re-configure the Library for drive(s)"

Explanation:    ACSLS drive configuration is possibly incorrect, please run the NLO configuration and re-configure the drives.


Error 6627

TSI_E6627	"ACSLS:Please re-configure the Library for Media(s)"

Explanation:    ACSLS volume configuration is possibly incorrect, please run the NLO volume configuration and re-assign the volumes.


Error 6628

TSI_E6628	ACSLS:Media already in drive

Explanation: the requested media to be mounted is already in the tape drive. This can happen if the user manually mounts a media from the ACSLS administrative console.


Error 6629

TSI_E6629	ACSLS:Please re-configure the Library

Explanation:    ACSLS configuration is possibly incorrect, please run the NLO configuration and re-configure drives.


Error 6630

TSI_E6630	ACSLS:Library Failure has occurred. Please check the library

Explanation:  Library hardware failure.


Error 6631

TSI_E6631	ACSLS:acs_dismount error

Explanation: ACSLS dismount command failed with error


Error 6632

TSI_E6632	"ACSLS:Media not found. Please Re-inventory the library"

Explanation: ACSLS cannot locate the media that is being mounted/dismounted. This can happen if the user manually exported the media from the library from the ACSLS administrator console.


Error 6633

TSI_E6633	ACSLS:acs_query_server error

Explanation: ACSLS query server command failed with error


Error 6634

TSI_E6634	ACSLS:acs_query_port error

Explanation: ACSLS query port command failed with error


Error 6635

TSI_E6635	"ACSLS:acs_query_acs error "

Explanation: ACSLS query acs command failed with error


Error 6636

TSI_E6636	"ACSLS:acs_query_cap error "

Explanation: ACSLS query cap command failed with error


Error 6637

TSI_E6637	"ACSLS:acs_query_volume error "

Explanation: ACSLS query volume command failed with error


Error 6638

TSI_E6638	"ACSLS:acs_query_drive error "

Explanation: ACSLS query drive command failed with error


UNIX Error E1000

Description:  Failed to attach to job queue. Please check asqd daemon status.

Solution:  Use "arcserve -show" to see if asqd is up.  Use "arcserve -load asqd".


UNIX Error E1003

Description:  Failed to open Daily Log

Solution:  Use "arcserve –show" to see if asloggerd is up.  Use "arcserve-load asloggerd" to load asloggerd if necessary.


UNIX Error E1005

Description:  A process cannot be run by user.

Solution:  Do not run aprocess from the command line.


UNIX Error E1007

Description:  Failed to get job handle from asmediad.

Solution:  Check if device is busy.


UNIX Error E1008

Description:  Failed to get device group

Solution:  Use "as_devmgr-groupinfo" to see if target group exists.


UNIX Error E1009

Description:  Failed to connect to media server

Solution:  Use "arcserve –show" to see if asmediad is up.  Use "arcserve-load asmediad" to load asloggerd if necessary.


UNIX Error E1010

Description:  asdbd needs to be preset for merge job

Solution:  Make sure asdbd is up and running.  If not, use "arcserve -load asdbd" from shell prompt.


UNIX Error E1014

Description:  Failed to format media

Solution:  Need to check error code at the end of each message.  See list below:

A1 - illegal command

A2 - end of media

A3 - file mark deleted

A4 - no data detected

A5 - unrecoverable data error

A6 - cartridge not in place

A7 - controller failure

AA - early warning detected


UNIX Error E1015

Description:  Failed to read volume header of media

Solution:  Need to check error code at the end of each message.  See list below:

A1 - illegal command

A2 - end of media

A3 - file mark deleted

A4 - no data detected

A5 - unrecoverable data error

A6 - cartridge not in place

A7 - controller failure

AA - early warning detected


UNIX Error E1016

Description:  Failed to position media to session

Solution:  Need to check error code at the end of each message.  See list below:

A1 - illegal command

A2 - end of media

A3 - file mark deleted

A4 - no data detected

A5 - unrecoverable data error

A6 - cartridge not in place

A7 - controller failure

AA - early warning detected


UNIX Error E1018

Description:  Failed to locate media ID sequence

Solution:  Need to check error code at the end of each message.  See list below:

A1 - illegal command

A2 - end of media

A3 - file mark deleted

A4 - no data detected

A5 - unrecoverable data error

A6 - cartridge not in place

A7 - controller failure

AA - early warning detected


UNIX Error E1026

Description:  Failed to position media to the end of session.

Solution:  Need to check error code at the end of each message.  See list below:

A1 - illegal command

A2 - end of media

A3 - file mark deleted

A4 - no data detected

A5 - unrecoverable data error

A6 - cartridge not in place

A7 - controller failure

AA - early warning detected


UNIX Error E1031

Description:  Media sequence does not contain session

Solution:  Validate the session number.


UNIX Error E1035

Description:  Failed to connect to media

Solution:  Internal errors. Call Technical Support.


UNIX Error E1036

Description:  Failed to write to media

Solution:  Replace the media.


UNIX Error E1038

Description:  Failed to write volume header on media

Solution:  Need to check error code at the end of each message.  See list below:

A1 - illegal command

A2 - end of media

A3 - file mark deleted

A4 - no data detected

A5 - unrecoverable data error

A6 - cartridge not in place

A7 - controller failure

AA - early warning detected


UNIX Error E1042

Description:  Failed to start tape session

Solution:  Internal errors. Call Technical Support.


UNIX Error E1048

Description:  Failed to create job record of job in asdbd

Solution:  Make sure asdbd is up and running.  If not, use "arcserve-load asdbd" from shell prompt.


UNIX Error E1053

Description:  Failed to create Daily Log

Solution:  Use "arcserve-show to see if asloggerd is up".  Use "arcserve-load asloggerd" to load asloggerd if necessary.


UNIX Error E1054

Description:  Failed to resume job

Solution:  Internal errors. Call Technical Support.


UNIX Error E1058

Description:  Failed to read from media

Solution:  Need to check error code at the end of each message.  See list below:

A1 - illegal command

A2 - end of media

A3 - file mark deleted

A4 - no data detected

A5 - unrecoverable data error

A6 - cartridge not in place

A7 - controller failure

AA - early warning detected


UNIX Error E1061

Description:  Invalid disk node list is found.  Abort compare job!

Solution:  Internal errors. Call Technical Support.


UNIX Error E1063

Description:  Invalid session Password, job rejected!

Solution:  Use proper session password and rerun the job.


UNIX Error E1065

Description:  Failed to get online media list.

Solution:  Check and see if media group exists and if user has enough access rights.


UNIX Error E1073

Description:  Failed to get missed targets, not asdb connection!

Solution:  Make sure asdbd is up and running.  If not, use "arcserve -load asdbd" from shell prompt.


UNIX Error E1075

Description:  Failed to get last full backup date,

Solution:  Internal errors. Call Technical Support.


UNIX Error E1081

Description:  Failed to get recycle Media info. Blank Media will be used.

Solution:  Internal errors. Call Technical Support.


UNIX Error E1100

Description:  Failed to get job for service

Solution:  Use "arcserve -status" to make sure asqd is up and running.


UNIX Error E1101

Description:  Failed to validate logger access as user

Solution:  Job owner does not have proper rights to create log files.  Use Profile Manager to grant user enough rights.


UNIX Error E1102

Description:  Failed to start job monitoring,

Solution:  Might run out of share memory.  Make sure there is share memory available and no lingering share memory.


UNIX Error E1103

Description:  Failed to get tape device from queue

Solution:  Job is invalid.  Use Job Status Manager to check the job.  Make sure tape device is valid.


UNIX Error E1104

Description:  Failed to move media id sequence to save set

Solution:  Check if asdbd is up; check if the media pool exists.


UNIX Error E1105

Description:  Failed to move media ID sequence to save set

Solution:  Check if asdbd is up; check if the media pool exists.


UNIX Error E1106

Description:  Failed to enumerate media group

Solution:  Make sure asmediad is up.  Check and see if media group exists and if user has enough access rights


UNIX Error E1107

Description:  Failed to locate any media group.

Solution:  Make sure asmediad is up.


UNIX Error E1108

Description:  Failed to get tape node from job

Solution:  Job is invalid.  Use Job Status Manager to check the job.  Make sure tape device is valid.


UNIX Error E1109

Description:  Failed to connect to logger service.

Solution:  Use "arcserve –show" to see if asloggerd is up.  Use "arcserve-load asloggerd" to load asloggerd if necessary.


UNIX Error E1110

Description:  Failed to open activity log.

Solution:  Make sure asloggerd is up and running.


UNIX Error E1111

Description:  Failed to position media to leading session

Solution:  Media might be bad.  Try to scan whole set of tapes from sequence one.


UNIX Error E1112

Description:  Failed to connect to asdbd on __ as

Solution:  Make sure asdbd is up and running.  If not, use "arcserve-load asdbd" from shell prompt.


UNIX Error E1113

Description:  Failed to get tape info from job

Solution:  Job is invalid.  Use Job Status Manager to check the job.  Make sure tape device is valid.


UNIX Error E1114

Description:  Failed to locate disk node from job

Solution:  Job is invalid.  Use Job Status Manager to check the job.  Make sure tape device is valid.


UNIX Error E1116

Description:  Invalid media name prefix is found!

Solution:  Job is invalid.  Use Job Status Manager to check the job.  Make sure tape device is valid.


UNIX Error E1117

Description:  Failed to set next job time, illegal job units used.

Solution:  Job is invalid.  Use Job Status Manager to check the job.  Make sure tape device is valid.


UNIX Error E1118

Description:  Failed to get initial backup date of job

Solution:  Make sure asdbd is up and running.  If not, use "arcserve-load asdbd" from shell prompt.


UNIX Error E1119

Description:  Failed to signal asdbd for preparing backup media

Solution:  Make sure asdbd is up and running.  If not, use "arcserve-load asdbd" from shell prompt.


UNIX Error E1120

Description:  Failed to back up ARCserve database, invalid job.

Solution:  Internal errors. Call Technical Support.


UNIX Error E1121

Description:  Failed to back up ARCserve database, ARC_HOME/dbase is invalid.

Solution:  Internal errors. Call Technical Support.


UNIX Error E1122

Description:  Failed to back up ARCserve database, ARC_HOME/data is invalid.

Solution:  Internal errors. Call Technical Support.


UNIX Error E1123

Description:  Failed to start asdb backup, job invalid.

Solution:  Internal errors. Call Technical Support.


UNIX Error E1125

Description:  Failed to open file

Solution:  Use "arcserve-show to see if asloggerd is up".  Use "arcserve-load asloggerd" to load asloggerd if necessary.


UNIX Error E1126

Description:  Failed to convert job

Solution:  Internal errors. Call Technical Support.


UNIX Error E1129

Description:  Failed to open user error log

Solution:  Use "arcserve-show to see if asloggerd is up".  Use "arcserve-load asloggerd" to load asloggerd if necessary.  If error log still fails to open, please call technical support.


UNIX Error E1124

Description:  Failed to locate a blank media.

Solution:  A blank tape can't be found for job.  Make a blank tape available.


UNIX Error E1127

Description:  Failed to open SNMP device

Solution:  Check if the configured SNMP Manager Station address in ARC_HOME/config/aslogger.cfg exists.  Check if trap destination and community are set in SNMP configuration file.


UNIX Error E1128

Description:  Failed to access SNMP device

Solution:  Check if the configured SNMP Manager Station address in ARC_HOME/config/aslogger.cfg exists.


UNIX Error E1130

Description:  Failed to access printer on spooler

Solution:  Check if the configured spooler in ARC_HOME/config/aslogger.cfg exists.


UNIX Error E1131

Description:  Failed to prepare e-mail sending for user

Solution:  Check if the e-mail address is valid; check if ARCserve server has proper e-mail access.


UNIX Error E1132

Description:  Failed to open TNG device"

Solution:  Check if the configured TNG console in ARC_HOME/config/aslogger.cfg exists; Check if TNG is installed and running on the same machine where ARCserve is running


UNIX Error E1133

Description:  Failed to access TNG device

Solution:  Check if the configured TNG console in ARC_HOME/config/aslogger.cfg exists; Check if TNG is installed and running on the same machine where ARCserve is running


UNIX Error E1134

Description:  Valid connection to logger service is not present!

Solution:  Use "arcserve -show to see if asloggerd is up".  Use "arcserve -load asloggerd" to load asloggerd if necessary.


UNIX Error E1135

Description:  Failed to get last backup date

Solution:  Make sure asdbd is up and running.  If not, use "arcserve -load asdbd" from shell prompt.


UNIX Error E1136

Description:  Failed to seek to new session for backup on media

Solution:  Need to check error code at the end of each message.  See list below:

A1 - illegal command

A2 - end of media

A3 - file mark deleted

A4 - no data detected

A5 - unrecoverable data error

A6 - cartridge not in place

A7 - controller failure

AA - early warning detected


UNIX Error E1138

Description:  Failed to find media for job, timeout!

Solution:  Need to check error code at the end of each message.  See list below:

A1 - illegal command

A2 - end of media

A3 - file mark deleted

A4 - no data detected

A5 - unrecoverable data error

A6 - cartridge not in place

A7 - controller failure

AA - early warning detected


MBO Error Messages


Error E 9600

9600 E  MBOMSGTB: CAIGLBL0000 is not set

Format:  E9600 MBOMSGTB: CAIGLBL0000 is not set

Reason:  The MBO message table build process did not find the CAIGLBL0000 environment variable

Action:  MBO must be started under ARCserve , which will ensure that CAIGLBL0000 is set


Error E 9601

Format:  E 9601 MBOMSGTB: Smalloc failed (element) to acquire (bytes) bytes of memory

Insert:  element:  The internal element structure name being allocated at the time of the failure

Insert:  bytes:  The number of bytes of storage requested at the time of the failure

Reason:  The MBO message table build process issued a smalloc which failed

Action:  Call for support


Error E 9602

Format:  E 9602 MBOMSGTB: Invalid message number in message file (filename) (linenum)

Insert:  filename:  The name of the message file in error

Insert:  linenum:  The line number within the file which is in error

Reason:  The MBO message table build process encountered an invalid record.

Action:  Call for support.


Error E 9603

Format:  E 9603 MBOMSGTB: Premature end-of-file in message file (filename) (linenum)

Insert:  filename:  The name of the message file in error

Insert:  linenum:  The line number within the file which is in error

Reason:  The MBO message table build process encountered a premature EOF

Action:  Call for support


Error C 9604

Format:  C 9604 MBOSVC  : Unable to find American English message file

Reason:  Neither the specified message file nor the American English file could be found

Action:  Verify CAIGLBL0000 and install procedures


Error W 9605

Format:  W 9605 MBOSVC  : Language type "(languageid)" is not supported by this release

Insert:  languageid:  The two-character language file id

Reason:  The specified national language is not supported

Action:  Specify a supported national language code


Error W 9606

Format:  W9606 MBOSVC  : Server is too busy or is too low on <resource> to start backup jobs

Insert:  resource:  The resource which is constrained.

Reason:  Either there is insufficient virtual memory, or LCB space.

Action:  Close some applications, wait for other MBO jobs to complete, or reconfigure NT page space and/or add RAM.  When problem is corrected, try again.


Note N 9607

Format:  N9607 MBOSVC  : Mainframe Backup Option (version) Initialization In-progress

Insert:  version:  The version of MBO being initialized

Reason:  The MBO product has recognized a startup request

Action:  None


Error E 9608

Format:  E9608 MBOSVC  : Fork() failed for MBO Daemon, rc = (returncode)

Insert:  returncode:  The reported return code from the fork() service

Reason:  (Unix Only) An attempt to create the product Daemon process failed

Action:  See message number 9609 for the failure reason


Error E 9609

Format:  E9609 MBOSVC  : Reason = (reasoncode)

Insert:  reasoncode:  The reported reason code from the fork() service

Reason:  (Unix Only) An attempt to create the product Daemon process failed

Action:  Correct the error indicated by the reason and restart


Error E 9610

Format:  E9610 MBOSVC  : Initialization routine (routine) failed, rc=(returncode)

Insert:  routine:  The name of the failed initialization routine

Insert:  returncode:  The reported return code from the initialization routine

Reason:  An MBO initialization routine failed to complete

Action:  See message number 9611 for the failure reason


Error E 9611

Format:  E9611 MBOSVC  : Reason for failure:  (reason)

Insert:  reason:  The reported reason from the initialization routine

Reason:  An MBO initialization routine failed to complete

Action:  Correct the error indicated by the reason and restart


Error E 9612

Format:  E9612 MBOSVC  : Unknown initialization index (index)

Insert:  index:  The initialization routine index value which is not known to MBO

Reason:  The MBO initialization function has encountered an internal logic error

Action:  Note the unknown index value and call support services


Error E 9614

Format:  E9614 MBOMSRV : Fatal error in Message Server at line (line_no)

Insert:  line_no:  line number associated with the fatal error

Reason:  The MBO Message Server has encountered an unrecoverable error.

Action:  None


Error N 9615

Format:  N9615 MBODMON : Ready for Work - Site((site_name)) System((system_id))

Insert:  site_name:  The site name assigned to this MBO

Insert:  system_id:  The system identification assigned to this MBO

Reason:  The MBO server site name and system id is now ready to accept work

Action:  None


Error E 9616

Format:  E9616 MBODMON : Error processing configuration file (rc = (returncode))

Insert:  returncode:  The return code reported by the configuration processing routines

Reason:  The product config file (registry) contains an error

Action:  Look for other messages identifying the error


Note N 9617

Format:  N9617 MBODMON : Base Key override: (source):  (basekey)

Insert:  source:  The source of the override ("configuration file" or "execution parameter")

Insert:  basekey:  The overriding value of the MBO IPC base key

Reason:  The product base key value was overridden by the noted source

Action:  None


Error E 9618

Format:  E9618 MBODMON : Message Queue Key override is invalid

Reason:  The product base key override was invalid (must be greater than 256)

Action:  Correct the base key specification and restart


Note N 9619

Format:  N9619 MBODMON : Starting on (servername) : (operating_system) Version (osversion)

Insert:  servername:  The name of the server on which MBO is being started

Insert:  operating_system:  The name of the operating system running on the server

Insert:  osversion:  The version of the operating system running on the server

Reason:  The product has recognized the noted environment

Action:  None


Error E 9620

Format:  E9620 MBODMON : Execution environment not supported by this release

Reason:  The product does not support your operating system/level

Action:  Contact support services for an upgrade to MBO


Error E 9621

Format:  E9621 MBODMON : Semget for initialization semaphore key (keyvalue) failed:  (reason)

Insert:  keyvalue:  The numeric key value associated with the failing semaphore

Insert:  reason:  The reason for the failure

Reason:  A system error occurred in the semget function

Action:  Correct the error and restart


Error E 9622

Format:  E9622 MBODMON : Error in setting the initialization semaphore:  (reason)

Insert:  reason:  The reason for the failure

Reason:  A system error occurred in the semop function

Action:  Correct the error and restart


Error E 9623

Format:  E9623 MBODMON : Product is already active...startup aborted

Reason:  A copy of the product is already active with this base key

Action:  None


Error E 9624

Format:  E9624 MBODMON : Attach of Shared Memory Failed:  (reason)

Insert:  reason:  The reason for the failure

Reason:  The shmat function failed to attach shared memory

Action:  Correct the error and restart


Error E 9625

Format:  E9625 MBODMON : MBOPATH Environment variable too long ((length) characters)

Insert:  length:  The number of characters in the MBOPATH variable

Reason:  The MBOAPTH value is too long for MBO to support

Action:  Correct the error and restart


Error E 9626

Format:  E9626 MBODMON : Message Queue Key conflict for (component)

Insert:  component:  The name of the component whose Queue Key is in conflict

Reason:  The selected base key value has caused a conflict with another product

Action:  Correct the error and restart


Error E 9627

Format:  E9627 MBODMON : Unable to create Daemon Message Queue:  (reason)

Insert:  reason:  The reason for the failure

Reason:  The msgget function failed in created a message queue for the Daemon

Action:  Correct the error and restart


Error E 9628

Format:  E9628 MBODMON : TPP Database Initialization failed:  (reasoncode)

Insert:  reasoncode:  The reason code for the failure

Reason:  The initialization of the TPP databases failed

Action:  Correct the error and restart


Error E 9629

Format:  E9629 MBODMON : Fork failed for the (processname) process:  (reason)

Insert:  processname:  The name of the process which could not be started

Insert:  reason:  The reason for the failure

Reason:  An attempt to create a child process to the Daemon has failed

Action:  Correct the error and restart if necessary


Error E 9630

Format:  N9630 MBODMON : Initialization Completed

Reason:  Product initialization completed successfully

Action:  None


Note N 9631

Format:  N9631 MBODMON : Mainframe Backup Option (version) is now active

Insert:  version:  The MBO product version

Reason:  The MBO product is now active and ready for work

Action:  None


Error W 9632

9632 W  MBODMON : Invalid message in MBO Daemon

Format:  W9632 MBODMON : Invalid message in MBO Daemon (type = (messagetype), from Pid (processid))

Insert:  messagetype:  The unknown message type

Insert:  processid:  The process id which has sent the unknown message

Reason:  The MBO Daemon encountered an unknown message

Action:  Note the message type and report the problem to support services


Error N 9633

9633 N  MBODMON : Host communications (MBOTPP) have halted

Format:  N9633 MBODMON : Host communications (MBOTPP) have halted

Reason:  MBOTPP has shutdown

Action:  None


Error N 9634

Format:  N9634 MBODMON : Restart of host communications (MBOTPP) deferred for (deferTime) minutes

Insert:  deferTime:  The number of minutes before MBOTPP will be restarted

Reason:  MBOTPP has shutdown and will not be immediately restarted

Action:  None


Error I 9636

Format:  I 9636 MBODMON : (timeframe) since last response from process/thread:  (processid)/(threadid) - (component)

Insert:  timeframe:  The amount of time since the last time the process responded

Insert:  processid:  The process id which has not been responding

Insert:  threadid:  The thread id which has not been responding

Insert:  component:  The MBO component name which has not been responding

Reason:  The specified process has not responded to an internal PING and may be hung

Action:  If this persists, it may be necessary to kill the process or restart MBO


Error C 9637

Format:  C9637 MBODMON : MBO Components are not compatible (processid) - Shutting down

Insert:  processid:  The process id which is running incompatible code

Reason:  An MBO process was started and returned an incompatible version string

Action:  Check your install executable library - Call for Support if necessary


Note N 9638

Format:  N9638 MBODMON : Backup initiated - creating a new BCC processor

Reason:  A new backup request has been received

Action:  None


Note N 9639

Format:  N9639 MBODMON : MBODBKUP initiated - MBO Data Base Backup

Reason:  The time-triggered policy for DB backups has been executed

Action:  None


Note N 9640

Format:  N9640 MBODMON : MBODBKUP started   - MBO Data Base Backup

Reason:  The DB Backup process has started successfully

Action:  None


Note N 9641

Format:  N9641 MBODMON : Bobs are pending transmission to host

Reason:  A backup has started, meaning that Bobs are pending transmission

Action:  None


Note N 9642

Format:  N9642 MBODMON : Bobs are safe at host

Reason:  All Bobs are safely at the host

Action:  None


Note N 9643

Format:  N9643 MBODMON : Restore initiated [(jobid)] - creating a new RST processor

Insert:  jobid:  The job id associated with the restore request

Reason:  A new restore request has been received

Action:  None


Error W 9644

Format:  W9644 MBODMON : Unable to start (processtype) process - Max Tasks Exceeded

Insert:  processtype:  The type of process which was not started

Reason:  The maximum number of supported processes has been exceeded

Action:  Further requests will be accepted upon termination of an existing backup or restore session


Error W 9645

Format:  W9645 MBODMON : Unable to start (processtype) process - Invalid Reservation Ticket ((ticket))

Insert:  processtype:  The type of process which was not started

Insert:  ticket:  The reservation ticket which is found to be invalid

Reason:  A job tried to start without a valid job reservation ticket

Action:  Retry job, call for support if failure continues.


Error W 9646

Reason:  A message was sent to the MBO Daemon from an unauthorized source

Action:  The message is ignored


Error W 9647

Format:  W9647 MBODMON : Process (processname) terminated abnormally

Insert:  processname:  The name of the process which has terminated abnormally

Reason:  An MBO process has terminated abnormally

Action:  Note the process, and the information which follows this message and call support services


Error W 9648

Format:  W9648 MBODMON : (processname) stopped due to signal (signal)

Insert:  processname:  The name of the process which has stopped

Insert:  signal:  The signal value which has stopped the process

Reason:  An MBO process has terminated abnormally due to a signal

Action:  Note the process, and the information which follows this message and call support services


Error W 9649

Format:  W9649 MBODMON : (processname) exit reason: (reason)

Insert:  processname:  The name of the process which has exited

Insert:  reason:  The reason associated with the exit code

Reason:  An MBO process has terminated abnormally due to an exit call

Action:  Note the process, and the information which follows this message and call support services


Error W 9650

Format:  W9650 MBODMON : (processname) terminated due to signal (signal)

Insert:  processname:  The name of the process which has terminated

Insert:  signal:  The signal value which has terminated the process

Reason:  An MBO process has terminated abnormally due to a signal

Action:  Note the process, and the information which follows this message and call support services


Note N 9651

Format:  N9651 MBODMON : Restarting process (processname) ((restart_count))

Insert:  processname:  The name of the process being restarted

Insert:  restart_count:  The number of times the process has been restarted

Reason:  An MBO process has terminated abnormally and is being restarted

Action:  None


Note N 9652

Format:  N9652 MBODMON : Restarting Database and requeuing LCB Transmissions

Reason:  MBO has detected that LCB has stopped transmitting

Action:  None


Informational I 9653

Format:  I9653 MBODMON : MBO Daemon process encountered a signal ((signal)) - ignored

Insert:  signal:  The signal value being ignored

Reason:  The MBO Daemon encountered an unexpected signal, which is being ignored

Action:  None


Error E 9654

Format:  E9654 MBODMON : Process restart limit exceeded...Shutdown Initiated

Reason:  The maximum number of restart attempts for an MBO process has been exceeded

Action:  The system shuts down - if this problem persists, call for support


Note N 9655

Format:  N9655 MBODMON : Shutdown request received

Reason:  The MBO product has received a request to shutdown

Action:  The system shuts down


Note N 9656

Format:  N9656 MBODMON : MBO entering quiet mode due to inactivity

Reason:  No backup or restore requests have been processed for some time.

          Therefore, MBO is shutting down all non-essential processes.

Action:  None


Note N 9657

Format:  N9657 MBOSVC  : Termination In-progress

Reason:  The MBO product has begun termination

Action:  The system shuts down


Error W 9658

Format:  W9658 MBOSVC  : Termination routine (routine) failed, rc=(returncode)

Insert:  routine:  The name of the routine which has failed

Insert:  returncode:  The return code from the termination routine

Reason:  An MBO termination routine has failed

Action:  The system shut down continues


Error W 9659

Format:  W9659 MBOSVC  : Unknown termination index (index)

Insert:  index:  The unknown termination index

Reason:  An unknown termination index was encountered

Action:  The system shut down continues - call for support


Note N 9660

Format:  N9660 MBOSVC  : Termination Completed

Reason:  The MBO product shut down has completed

Action:  None


Informational I 9661

Format:  I9661 SMALLOC : Dumping the Smalloc Heap Table:

Reason:  The internal memory management heap table is being dumped

Action:  None


Informational I 9662

Format:  I9662 SMALLOC : Memory Address   = (address)

Insert:  address:  The address of the allocated memory block

Reason:  The address of an extent of allocated storage

Action:  None


Informational I 9663

Format:  I9663 SMALLOC :  Memory Size    = (size)

Insert:  size:  The size of the allocated memory block

Reason:  The size of an extent of allocated storage

Action:  None


Informational I 9664

Format:  I9664 SMALLOC :  Allocated by:  (module) @ line (lineno)

Insert:  module:  The module name which allocated the memory block

Insert:  lineno:  The line number within the module which allocated the memory block

Reason:  The file which allocated an extent of allocated storage

Action:  None


Informational I 9665

Format:  I9665 SMALLOC : Total Allocation = (size) in (count) extents

Insert:  size:  The total amount of allocated memory

Insert:  count:  The number of extents (blocks) of allocated memory

Reason:  The total allocation extents and size

Action:  None


Error E 9666

Format:  E9666 SMALLOC : Unable to obtain (size) bytes for (module) line (lineno)

Insert:  size:  The size of the allocation request

Insert:  module:  The module name requesting the allocation

Insert:  lineno:  The line number within the module requesting the allocation

Reason:  Memory management was unable to allocate storage

Action:  Note the error and call for support


Error W 9667

Format:  W9667 SMALLOC : Zero-length request from (module) ( line (lineno) )

Insert:  module:  The module name requesting the allocation

Insert:  lineno:  The line number within the module requesting the allocation

Reason:  Memory management was called with a request for zero-bytes of storage

Action:  Look for other failures and call for support if necessary


Error W 9668

Format:  W9668 MBOMSG  : Unable to allocate DSM_GetMessage buffer

Reason:  Memory management was unable to satisfy a request for a GetMessage buffer

Action:  Look for other failures and call for support if necessary


Error E 9669

Format:  E9669 MBOMSG  : Semaphore error in messaging for key (key), errno = (reasoncode)

Insert:  key:  The key value associated with the semaphore

Insert:  reasoncode:  The reason code associated with the failure

Reason:  A semaphore used by messaging has been erroneously deleted

Action:  Call for support


Error E 9670

Format:  E9670 MBOMSG  : An invalid message was encountered on an MBO message queue

Reason:  A message was read off of a message queue which had an invalid MBO header

Action:  Call for support


Error E 9671

Format:  E9671 MBOMSG  : Invalid PutGetMsg type for Queue (key) was encountered, type = (messagetype)

Insert:  key:  The key value associated with the message queue

Insert:  messagetype:  The message type associated with the error

Reason:  A PutGetMsg was issued with a bad message type

Action:  Call for support


Error E 9673

Format:  E9673 MBOCFG  : Invalid configuration keyword specified:  (keyword)

Insert:  keyword:  The invalid configuration keyword

Reason:  Initialization encountered an invalid keyword in the configuration file

Action:  Correct the problem and restart


Error W 9674

Format:  W9674 MBOPARSE: parse_open issued without intervening parse_close

Reason:  Internal logic error

Action:  Call for support


Error W 9675

Format:  W9675 MBOPARSE: Syntax error in parsing:  (statement)

Insert:  statement:  The configuration statement which is in error

Reason:  Initialization encountered a syntax error in the configuration file

Action:  Correct the problem and restart


Error W 9676

Format:  W9676 MBOPARSE: Missing delimiter character(;):  (statement)

Insert:  statement:  The configuration statement which is in error

Reason:  Initialization encountered a syntax error in the configuration file

Action:  Correct the problem and restart


Error W 9677

Format:  W9677 MBOPARSE: Missing ending quote:  (statement)

Insert:  statement:  The configuration statement which is in error

Reason:  Initialization encountered a syntax error in the configuration file

Action:  Correct the problem and restart


Error W 9678

Format:  W9678 MBOPARSE: Internal logic error in routine (routine)

Insert:  routine:  The routine which is reporting an error

Reason:  Internal logic error

Action:  Call for support


Error E 9679

Format:  E9679 MBOSVC:  CA License Check Denied (reason (reasoncode)) - New Work Suspended.

Insert:  reasoncode:  The reason code associated with the license check failure

Reason:  The Computer Associates License Check was denied

Action:  Call for support


Error W 9680

Format:  W9680 MBOSVC:   (Jobtype) job was stopped or failed during job initialization.

Insert:  Jobtype:  The type of job (Backup or Restore).

Reason:  A request was sent asking that a new backup or restore job be initiated, but that job terminated (was stopped or failed) before MBO could properly connect to that job.

Action:  If the job was not specifically stopped by the user, call for support.


Error E 9681

Format:  E9681 SLIDHUFD: Decompression failure (LCB=(sfile_name))

Insert:  sfile_name:  The path and name of the LCB file being decompressed at the time

Reason:  MBO Failed to properly decompress a compressed BOB

Action:  Call for support


Error W 9685

Format:  9685 W  MBOSVC:   WARNING: MBO version has been back leveled

Insert:  version:  The MBO version as indicated by the current registry values.

Reason:  The MBO version as defined in the registry is older than the oldest version number as defined by the current running copy of the MBO product.  This may indicate that your registry has been restored to an old level, and that this level may not be compatible with the current running copy of MBO.

Action:  Please call for support if necessary.


Informational I 9700

Format:  I9700 MBOAPI  : Backup for session id (sessionid) hitting Virtual Storage constraints

Insert:  sessionid:  The session id associated with the constraint

Reason:  An MBO Backup job has been suspended due to a shortage of Virtual Storage

Action:  It is normal for very large backup jobs to ultimately suspend for this reason.  This is due to the fact that MBO will read as much data as possible into look-ahead buffers backed by virtual storage.  Should this message appear for very small backup jobs, you should review your server's virtual storage configuration.  It may be necessary to add additional RAM and/or to increase your Page File size.


Error E 9701

Format:  E9701 MBOAPI  : Bad token from (messagetype) message response [(token)]

Insert:  messagetype:  The type of message for which a bad internal token was detected

Insert:  token:  The bad token value

Reason:  An MBO Backup job has encountered an internal logic error.

Action:  None.


Note N 9702

Format:  N9702 MBOAPI  : Bob is a duplicate: (file (pfileadr) bytes: (bobsize) offset: (boboffset))

Insert:  pfileadr:  The internal address of the pfile structure associated with the BOB

Insert:  bobsize:  The size of the BOB which is duplicated

Insert:  boboffset:  The offset into the file where the duplicate BOB begins

Reason:  Diagnostic message (only issued if the TRACE_BOBS environment variable is present)

Action:  None.


Note N 9703

Format:  N9703 MBOAPI  : Bob is a new Bob:  (file (pfileadr) bytes: (bobsize) offset: (boboffset))

Insert:  pfileadr:  The internal address of the pfile structure associated with the BOB

Insert:  bobsize:  The size of the new BOB

Insert:  boboffset:  The offset into the file where the new BOB begins

Reason:  Diagnostic message (only issued if the TRACE_BOBS environment variable is present)

Action:  None.


Error E 9704

Format:  E9704 MBOAPI  : Begin File Error:  (file (pfileadr) rc=(returncode) rs=(reasoncode) : (engineid) (sessionid) (blockno) (blockrba))

Insert:  pfileadr:  The internal address of the pfile structure associated with the error

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Insert:  engineid:  The Id which identifies the backup engine

Insert:  sessionid:  The session id associated with the backup

Insert:  blockno:  The block number identifying the start of the file within the backup

Insert:  blocknum:  The block RBA identifying the start of the file within the backup

Reason:  A backup job has attempted to backup the same file id multiple times

Action:  Call for support.


Note N 9705

Format:  N9705 MBOBCC  : An MBO BCC process has started for session id (sessionid).

Insert:  sessionid:  The session id associated with the backup

Reason:  This message is normal for startup. The version may be verified.

Action:  There is no action required, but a quiet celebration is allowed.


Note N 9706

Format:  N9706 MBOBCC  : MBO BCC has completed its processing for session id (sessionid).

Insert:  sessionid:  The session id associated with the backup

Reason:  This message is displayed for informational purposes only.

Action:  None.


Error E 9707

Format:  E9707 MBOBCC  : An MBO BCC process received a terminate signal for session id (sessionid). It will be shutting down.

Insert:  sessionid:  The session id associated with the backup

Reason:  A signal has been received for which the appropriate action is to shut down.

Action:  Call support to determine the source of the signal and a course of action to prevent recurrences.  When such action has been taken, start another backup to backup files not backed up when the backup failed.


Error W 9708

Format:  W9708 MBOAPI:  MBOAPI is running short of disk space.

Reason:  MBO requires disk space for running restores and backups. There is currently not enough available.

Action:  Attempt to free some disk space.


Error W 9709

Format:  W9709 MBOAPI:  Backup job starting with constrained virtual memory.

Reason:  A backup job is starting in an environment where there is already less free virtual storage than requested via the MBO configuration parameters.  The backup job will start, but throughput will be greatly reduced due to this constraint.

Action:  Close other application or increase the amount of RAM or Page Space on the server.


Error E 9750

Format:  E9750 MBORST:  MBORST failed to start. Failed in (routine). RC = (returncode); errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the failing routine

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  The MBO RST process did not start properly and will shutdown.

Action:  Call support to determine how to fix the problem. Fix the problem, then restart your restore with ASM2.


Note N 9751

Format:  N9751 MBORST  : MBORST has started correctly.

Reason:  This message is normal for startup.

Action:  There is no action required.


Note N 9752

Format:  N9752 MBORST  : MBORST has completed its shutdown.

Reason:  This message is displayed for informational purposes only.

Action:  None.


Note N 9753

Format:  N9753 MBORST  : MBORST is beginning a normal shutdown.

Reason:  This message is displayed for informational purposes only.

Action:  None.


Error E 9754

Format:  E9754 MBORST  : MBORST suffered a fatal error in (routine). RC = (returncode); errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the failing routine

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  An error has occurred from which recovery is not practical.

Action:  Call support to determine the cause of the problem and a course of action to correct the cause.  When this corrective action has been taken, start another restore to restore files not restored when the restore failed.


Error E 9755

Format:  E9755 MBORST  : MBORST received a signal (signal). Shutting down.

Insert:  signal:  The signal which has been received

Reason:  A signal has been received for which the appropriate action is to shut down.

Action:  Call support to determine the source of the signal and a course of action to prevent recurrences.  When such action has been taken, start another restore to restore files not restored when the restore failed.


Note N 9756

Format:  N9756 MBORST  : MBORST has registered restore (restore id) at the host. (bob count) bobs requested.

Insert:  restore id:  The special code identifying this particular restore.

Insert:  bob count:  The number of bobs requested from the host.

Reason:  This message is displayed for informational purposes only.

Action:  None.


Error W 9757

Format:  W9757 MBORST  : MBORST suffered an error in (routine). RC = (returncode); errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the routine encountering the error

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  An error has occurred from which the MBORST has recovered. One or more files may not be restored because of this error.

Action:  Call support to determine the significance of this error and a course of action to prevent recurrences.  If one or more files were not restored because of this error, take action to prevent recurrences and start another restore to restore files not restored when the error occurred.


Error W 9758

Format:  W9758 MBORST  : MBORST is running short of disk space.

Reason:  MBO requires disk space for running restores and backups. There is currently not enough available.

Action:  Attempt to free some disk space.


Error N 9759

Format:  N9759 MBORST  : MBORST host restore (restore id) has ended.

Insert:  restore id:  The special code identifying this particular restore.

Reason:  This message is displayed for informational purposes only.

Action:  None.


Error N 9760

Format:  N9760 MBORST  : MBORST received a Host Restore Response with a non-zero return code.  A new restore request is being sent to the host. RC = (returncode); REASON = (reasoncode);

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  MBORST received a Host Restore Response with a non-zero return code.

Action:  If this message occurs frequently and restores do not run call support to determine the cause of this message and a course of action to prevent recurrences.


Error E 9761

Format:  E9761 MBORST  : Restore cannot continue because backup was incomplete.

Reason:  Restore cannot continue because backup was incomplete.

Action:  Attempt to restore the data from a different session.  Run MBOMERGE for this session so that ARCserve will be aware of the restore limitations.


Error E 9762

Format:  E9762 MBORST  : Host restore (restore id) has ended but none of the (bobcount) bobs requested were restored.

Reason:  For reason or reasons unknown, no bobs were restored from the mainframe.

Action:  If this message occurs more than once in the course of a restore, the mainframe operator should be contacted to ascertain the cause of the problem, and to determine a course of action to remedy the problem. If no solution is found, support should be called.


Error E 9780

Format:  E9780 MBODRY  : MBODRY suffered a fatal error in (routine). RC = (returncode); errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the failing routine

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  An error has occurred from which recovery is not practical.

Action:  Call support to determine the cause of the problem and a course of action to correct the cause.  When this corrective action has been taken, start another restore to restore files not restored when the restore failed.


Note N 9781

Format:  N9781 MBODRY  : MBODRY has its restore registered at the host.

Reason:  This message is displayed for informational purposes only.

Action:  None.


Note N 9782

Format:  N9782 MBODRY  : MBODRY has started.

Reason:  This message is displayed for informational purposes only.

Action:  None.


Note N 9783

Format:  N9783 MBODRY  : MBODRY has restored generation (generation) of the MBO database.

Reason:  This message is displayed for informational purposes only.

Action:  None.


Note N 9784

Format:  N9784 MBODRY  : MBODRY is waiting for a response from the mainframe.

Reason:  This message is repeated regularly while MBODRY is waiting for a response from the mainframe.

Action:  There is no action required.


Error N 9785

9785 N  MBODBKUP : MBODBKUP has started correctly.

Format:  N9785 MBODBKUP   : MBODBKUP has started correctly.

Reason:  This message is normal for startup.

Action:  There is no action required.


Error N 9786

9786 N  MBODBKUP : MBODBKUP is waiting to begin.

Format:  N9786 MBODBKUP   : MBODBKUP is waiting to begin.

Reason:  The daemon tells MBODBKUP when to begin working.

Action:  There is no action required.


Error N 9787

9787 N  MBODBKUP : MBODBKUP is running.

Format:  N9787 MBODBKUP   : MBODBKUP is running.

Reason:  This message indicates that MBODBBKUP is backing up data.

Action:  There is no action required.


Error E 9788

Format:  E9788 MBODBKUP: MBODBKUP suffered a fatal error in (routine). RC = (returncode); errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the failing routine

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  An error has occurred from which recovery is not practical.

Action:  Call support to determine the cause of the problem and a course of action to correct the cause.  When this corrective action has been taken, start another restore to restore files not restored when the restore failed.


Error N 9789

9789 N  MBODBKUP : MBODBKUP has finished correctly.

Format:  N9789 MBODBKUP   : MBODBKUP has finished correctly.

Reason:  This message means that the backup of the file database to LCB has been successfully completed.

Action:  There is no action required.


Error E 9790

E9790 MBODBKUP   : MBODBKUP Does not have enough disk space to operate.

Format:  E9790 MBODBKUP   : MBODBKUP Does not have enough disk space to operate.

Reason:  MBODBKUP makes a copy of the MBODB data files, and backs up the copy.  There is not enough room to do this.

Action:  Calculate the amount of free space required.  This is the size of the files in the MBO\DATA directory less the size of the files in the MBO\TEMPDATA directory.


Error E 9800

Format:  E9800 MBODB   : MBODB failed to start. Failed in (routine). RC = (returncode); errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the failing routine

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  The MBODB process did not start properly and will shutdown.

Action:  MBODB will be restarted automatically.  Call support to determine the cause of the problem and a course of action to correct the cause.


Note N 9801

Format:  N9801 MBODB   : MBODB has started correctly. Version ((version)).

Insert:  version:  The version of MBODB

Reason:  This message is normal for startup. The version may be verified.

Action:  There is no action required, but a quiet celebration is allowed.


Error N 9802

Format:  N9802 MBODB   : MBODB has completed its shutdown.

Reason:  This message is displayed for informational purposes only.

Action:  None.


Note N 9803

Format:  N9803 MBODB   : MBODB is beginning a normal shutdown.

Reason:  This message is displayed for informational purposes only.

Action:  None.


Error E 9804

Format:  E9804 MBODB   : MBODB suffered a fatal error in (routine). RC = (returncode); errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the failing routine

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  An error has occurred from which recovery is not practical.

Action:  MBODB will be restarted automatically. Call support to determine the cause of the problem and a course of action to correct the cause.


Error E 9805

Format:  E9805 MBODB   : MBODB received a signal (signal). Shutting down.

Insert:  signal:  The signal which has been received

Reason:  A signal has been received for which the appropriate action is to shut down.

Action:  MBODB will be restarted automatically. Call support to determine the source of the signal and a course of action to prevent recurrences.


Error W 9806

Format:  W9806 MBODB   : MBODB suffered an error in (routine). RC = (returncode); errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the routine encountering the error

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  An error has occurred from which the MBODB has recovered.

Action:  Keep track of these errors. Call support to determine the significance of the errors and a course of action to prevent recurrences.


Error E 9807

Format:  E9807 MBODB   : A get BOB response had a return code of (returncode) and a reason code of (reasoncode).

Insert:  returncode:  The return code identifying the error

Insert:  reasoncode:  The reason code identifying the error

Reason:  This occurs whenever there is any difficulty getting a bob from the mainframe to the server.

Action:  Keep track of these errors. Call support to determine the significance of these errors. They may just indicate line trouble.


Error E 9808

Format:  E9808 MBODB   : A requested BOB was not found at the host. ( (BobId) )

Insert:  BobId:  The BOB Id associated with the error

Reason:  This means that the host and your server are not in agreement concerning which data is stored where. Your data may be lost.

Action:  Call support.


Error E 9809

Format:  E9809 MBODB   : A BOB was not found at the host. (BobId)

Insert:  BobId:  The BOB Id associated with the error

Reason:  A bobaudit has found an error in the database records concerning which BOBS are safe at the host.

Action:  Support should be notified.


Note N 9810

Format:  N9810 MBODB   : A host bob audit is starting.

Reason:  A verification is made between the LAN and the host.

Action:  No action required.


Error N 9811

Format:  N9811 MBODB   : A host bob audit has ended.  There were (newerrors) new errors and (olderrors) old errors.

Insert:  newerrors: The number of new errors detected.

Insert:  olderrors: The number of old errors not corrected.

Reason:  The verification between the LAN and the host has ended.

Action:  Investigate any errors.


Error W 9812

Format:  W9812 MBODB   : MBODB unable to close databases on shutdown.

Reason:  This message indicates a possible problem.

Action:  Support should be notified.


Error E 9813

Format:  E9813 MBODB   : MBODB suffered a fatal database error in (routine) called from (callingRoutine). errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the failing routine

Insert:  callingRoutine:  The routine name or descriptive name of the routine which has called the failing routine

Insert:  reasoncode:  The reason code identifying the error

Reason:  An error has occurred from which recovery is not practical.

Action:  MBODB will be restarted automatically. Call support to determine the cause of the problem and a course of action to correct the cause.


Error E 9814

Format:  E9814 MBODB   : MBODB suffered a fatal database error in (routine). errno = (reasoncode); (lineno)

Insert:  routine:  The routine name or descriptive name of the failing routine

Insert:  reasoncode:  The reason code identifying the error

Insert:  lineno:  The source code line number issuing the error

Reason:  An error has occurred from which recovery is not practical.

Action:  MBODB will be restarted automatically. Call support to determine the cause of the problem and a course of action to correct the cause.


Note N 9815

Format:  N9815 MBODB   : Beginning database rekey.

Reason:  Whenever there is a possibility that the database keys are out of synch with the database the keys are rebuilt.

Action:  None required. If this happens often call support to determine the cause.


Note N 9816

Format:  N9816 MBODB   : Finished database rekey.

Reason:  Whenever there is a possibility that the database keys are out of synch with the database the keys are rebuilt.

Action:  None required. If this happens often call support to determine the cause.


Note N 9817

Format:  N9817 MBODB   : Verifying LCB. This may take a while.

Reason:  Whenever there is a possibility that database records of LCB are out of synch with LCB the LCB is verified.

Action:  None required. If this happens often call support to determine the cause.


Note N 9818

Format:  N9818 MBODB   : Finished verifying LCB. This took (minutes) minutes.

Insert:  minutes:  The number of minutes

Reason:  Whenever there is a possibility that database records of LCB are out of synch with LCB the LCB is verified.

Action:  None required. If this happens often call support to determine the cause.


Error W 9819

Format:  W9819 MBODB   : MBODB an sfile has been transmitted, but the record for the sfile is missing. ((sfileid),(flags))

Insert:  sfileid:  The encoded Id which identifies the sfile

Insert:  flags:  The sfile status flags

Reason:  MBODB Removes records for sfiles when the BOBs are safe at CSP. This time the record has already been removed.

Action:  Support should be notified if these messages occur more than occasionally.


Error W 9820

Format:  W9820 MBODB   : MBODB an sfile has been transmitted, but the file could not be removed. ((sfileid),(flags))

Insert:  sfileid:  The encoded Id which identifies the sfile

Insert:  flags:  The sfile status flags

Reason:  MBODB Removes sfiles when the BOBs are safe at CSP. This time the sfile could not be removed.

Action:  Support should be notified.


Error W 9821

Format:  W9821 MBODB   : MBODB sfile (filename) with status ((flags)) is missing.

Insert:  filename:  The sfile file name

Insert:  flags:  The sfile status flags

Reason:  MBODB MBO stores vital information in sfiles. During a routine check for missing sfiles, an sfiles was missing.

Action:  Support should be notified.


Error W 9822

Format:  W9822 MBODB   : MBODB a drive ((driveid)) is FULL.

Insert:  driveid:  The drive letter which is unable to accept new sfiles

Reason:  MBODB MBO stores vital information in sfiles. There is no more room for sfiles on this drive.

Action:  Either make more room on the drive, or remove the drive from the list of drives that MBO uses for storing sfiles.


Note N 9823

Format:  N9823 MBODB   : All of the bobs for session id (sessionid) from server (server) are at CSP.

Insert:  sessionid:  The session Id associated with the Bobs

Insert:  server:  The name of the server

Reason:  Issued when all bobs for a session are reported transmitted.

Action:  None required. If data for a session is very critical, then if the MBO database files are now backed up to CSP, then the data is recoverable.


Informational I 9824

Format:  I9824 MBODB   : All bobs are now at CSP.

Reason:  This message is issued when all bobs known to MBO are reported transmitted.

Action:  None Required. This is an ideal time to back up the MBO database files.


Note N 9825

Format:  N9825 MBODB   : Sacrifice All left (count1) sfiles. (count2) of these were because all of the BOBS were not yet at CSP. (count3) BOBS were needed for restores.

Insert:  count1:  The number of sfiles left in LCB

Insert:  count2:  The number of sfiles left in LCB because they had not been sent to CSP

Insert:  count3:  The number of sfiles left in LCB because they are needed to satisfy a restore

Reason:  Standard message for Sacrifice all.

Action:  None Required.


Error E 9826

Format:  E9826 MBODB   :  No more space for the MBODB databases.

Reason:  The database subsystem could not acquire space to add new records.

Action:  If the disk containing the MBO\DATA directory is full, make more space on the disk. Otherwise call support.


Error N 9827

Format:  N9827 MBODB   : (kbytes) kbytes sacrificed from (directory).

Insert:  kbytes:  The number of kbytes removed from LCB.

Insert:  directory:   The LCB directory that the LCB was removed from.

Reason:  Allow the user to ascertain the efficacy of his sacrifice.

Action:  None Required.


Error N 9828

Format:  N9828 MBODB   : No directories found on drive (drive letter):.

Insert:  drive letter:    The drive the user specified.

Reason:  The user selected a drive that was not being used for LCB for a sacrifice command.

Action:  The user should select another drive.


Error W 9829

Format:  W9829 MBODB   : A host bob audit cannot be run. REASON = (reason); RC = (rc);

Insert:  reason: The reason code reported by MBOTPP.

Insert:  rc:     The return code reported by MBOTPP.

Reason:  The host was unable to send it's list of bobs.

Action:  Check that the host process is running, and that there are no communication problems with the host.


Error N 9830

Format:  N9830 MBODB   : Completed LCB resynchronization.

Reason:  This message is for informational purposes only.

Action:  None required.


Error N 9831

Format:  N9831 MBODB   : Sacrifice all left no sfiles.

Reason:  This message is for informational purposes only.

Action:  None required.


Error N 9832

Format:  N9832 MBODB   : (count) sfiles were left after Sacrifice_All.

Insert:  count:  The number of sfiles left in LCB.

Reason:  This message is for informational purposes only.

Action:  None required.


Error N 9833

Format:  N9833 MBODB   : (count) sfiles were not sacrificed because they are still needed for restore.

Insert:  count:  The number of sfiles left in LCB because they are still needed for restore.

Reason:  This message is for informational purposes only.

Action:  None required.


Error N 9834

Format:  N9834 MBODB   : (count) sfiles were not sacrificed because they are not yet at the mainframe.

Insert:  count:  The number of sfiles left in LCB because they are not yet at the mainframe.

Reason:  This message is for informational purposes only.

Action:  None required.


Error E 9900

Format:  E9900 MBOCLI  : Too few arguments to MBOCLI

Reason:  The MBO CLI processor encountered an invalid request

Action:  Check your command syntax and re-issue the command.


Error E 9901

Format:  E9901 MBOCLI  : Internal error connecting to MBO daemon, RC = (returncode)

Insert:  returncode:  The return code identifying the error

Reason:  The MBO CLI processor encountered an error trying to connect to your MBO system

Action:  Ensure MBO is active and re-issue the command.


Error E 9902

Format:  E9902 MBOCLI  : Unknown request type: (request)

Insert:  request:  The CLI request which is not known the CLI

Reason:  The MBO CLI processor encountered an unknown request type

Action:  Check your command syntax and re-issue the command.


Note N 9903

Format:  N9903 MBOCLI  : MBO Shutdown request issued.

Reason:  The MBO CLI processor encountered a shutdown request

Action:  The active MBO system is signaled to shutdown after quiescing activity.


Error E 9904

Format:  E9904 MBOCLI  : Internal error. Invalid daemon pid: (processId).

Insert:  ProcessId:  The process Id associated with the MBO Daemon process which is invalid

Reason:  The MBO CLI processor encountered an internal error

Action:  Retry.  If problem persists, call for support.


Error E 9905

Format:  E9905 MBOCLI  : MBO Stop Immediate failed. errno = (reasoncode).

Insert:  reasoncode:  The reason code associated with the error

Reason:  The MBO CLI processor encountered a stop immediate, which failed

Action:  Check ERRNO against system documented values and correct the problem.


Error N 9906

Format:  N9906 MBOCLI  : MBO Stop Immediate request issued.

Reason:  The MBO CLI processor has issued a stop immediate

Action:  The MBO subsystem should begin shutting down immediately.


Error E 9907

Format:  E9907 MBOCLI  : Internal error sending message to DB. RC = (returncode),errno = (reasoncode)

Insert:  returncode:  The return code associated with the error

Insert:  reasoncode:  The reason code associated with the error

Reason:  The MBO CLI processor failed in sending a message to the Data Base process (MBODB)

Action:  Check the return code and ERRNO and correct the problem.


Error E 9908

Format:  E9908 MBOCLI  : Invalid response msgtype from DB (GETSTAT). Type = (messagetype)

Insert:  messagetype:  The messagetype of the invalid response message

Reason:  The MBO CLI processor got an invalid response from the Data Base process (MBODB)

Action:  Call for support.


Note N 9909

Format:  N9909 MBOCLI  : Invalid response msgtype from DB (GETSTAT). Type = (messagetype)

Reason:  The MBO CLI processor has sent the Delete CSP Userid message

Action:  None.


Note N 9910

Format:  N9910 MBOCLI  : CSP Password (actionTaken).

Insert:  actionTaken:  "Set" or "Changed"

Reason:  The MBO CLI processor has sent the Set CSP Password message

Action:  None.


Error E 9911

Format:  E9911 MBOCLI  : Internal error setting CSP userid and password, rc = (returncode), errno = (reasoncode)

Insert:  returncode:  The return code associated with the error

Insert:  reasoncode:  The reason code associated with the error

Reason:  The MBO CLI processor failed in sending the Set CSP Userid message

Action:  Call for support.


Note N 9912

Format:  N9912 MBOCLI  : CSP Userid and Password set.

Reason:  The MBO CLI processor has sent the Set CSP Userid message

Action:  None.


Error E 9913

Format:  E9913 MBOCLI  : Must be root user to issue command. Cmd = (command),User = (user)

Insert:  command:  The command (action) requested

Insert:  user:  The current user Id

Reason:  The MBO CLI command requested is limited to the ROOT user (Unix only)

Action:  Login as ROOT and reissue the command.


Error E 9914

Format:  E9914 MBOCLI  : Environment variable not set (MBOPATH).

Reason:  The MBOPATH environment variable is not set.

Action:  Ensure MBO is properly installed.  Call for Support.


Error E 9915

Format:  E9915 MBOCLI  : Error opening MBOCLI help file (mbocli.hlp). errno = (reasoncode)

Insert:  reasoncode:  The reason code associated with the error

Reason:  The MBO CLI processes was unable to open the help file

Action:  Check the value of ERRNO and correct the problem.


Error E 9916

Format:  E9916 MBOCLI  : Internal error setting SHRMEM blk ptr. PTR = (pointer)

Insert:  pointer:  The value of the memory pointer which is not valid

Reason:  The MBO CLI processes failed to connect to the MBO Shared Memory

Action:  Ensure MBO is still active.  If problem persists, call for support.


Error E 9917

Format:  E9917 MBOCLI  : Internal error sending msg to daemon. rc = (returncode), errno = (reasoncode)

Insert:  returncode:  The return code associated with the error

Insert:  reasoncode:  The reason code associated with the error

Reason:  The MBO CLI processor failed in sending a message to the MBO Daemon

Action:  Ensure MBO is still active.  If problem persists, call for support.


Note N 9918

Format:  N9918 MBOCLI  : Tracing (actionTaken) for component (component).

Insert:  actionTaken:  The action which has been taken

Insert:  component:  The component name

Reason:  The MBO CLI processor successfully processed the TRACE command

Action:  None.


Error E 9919

Format:  E9919 MBOCLI  : Invalid # of arguments passed to the LEVEL command. Usage: MBOCLI LEVEL <0 | 1 | 2>.

Reason:  The MBO CLI command was entered with missing arguments

Action:  Check the command syntax and reissue the command.


Note N 9920

Format:  N9920 MBOCLI  : Tracing intensity level set.

Reason:  The MBO CLI processor successfully processed the LEVEL command

Action:  None.


Error E 9921

Format:  E9921 MBOCLI  : Invalid tracing level specified. Level = (level).

Insert:  level:  The tracing level value which is not valid

Reason:  The MBO CLI command was entered with an invalid Level specification

Action:  Check the command syntax and reissue the command.


Error E 9922

Format:  E9922 MBOCLI  : Invalid # of arguments passed to the TRACE command.

Reason:  The MBO CLI command was entered with missing arguments

Action:  Check the command syntax and reissue the command.


Error E 9923

Format:  E9923 MBOCLI  : Invalid Message Queue ((queueId)).

Insert:  queueId:  The queue Id which is not valid

Reason:  The MBO CLI processor failed in sending a message on the specified queue

Action:  Ensure MBO is still active.  If problem persists, call for support.


Error E 9924

Format:  E9924 MBOCLI  : Internal error sending message to TPP. RC = (returncode),errno = (reasoncode)

Insert:  returncode:  The return code associated with the error

Insert:  reasoncode:  The reason code associated with the error

Reason:  The MBO CLI processor failed in sending a message to the Communications process (MBOTPP)

Action:  Check the return code and ERRNO and correct the problem.


Error E 9925

Format:  E9925 MBOCLI  : Invalid component name specified on TRACE command:  (component).

Insert:  component:  The component name which is not valid

Reason:  The MBO CLI TRACE command was entered with an invalid component name.

Action:  Check the command syntax and reissue the command.


Error E 9926

Format:  E9926 MBOCLI  : Invalid # of arguments passed to the IDLE command.

Reason:  The MBO CLI command was entered with missing arguments

Action:  Check the command syntax and reissue the command.


Error E 9927

Format:  E9927 MBOCLI  : Invalid idle time specified. Time = (minutes) minutes.

Insert:  minutes:  The number of minutes requested which is not valid

Reason:  The MBO CLI command was entered with an invalid Level specification

Action:  Check the command syntax and reissue the command.


Note N 9928

Format:  N9928 MBOCLI  : Idle time ((minutes) minutes) has been set.

Insert:  minutes:  The number of minutes set

Reason:  The MBO CLI processor successfully processed the IDLE command

Action:  None.


Error E 9929

Format:  E9929 MBOCLI  : Unable to set Idle Time:  rc = (returncode) ((reason)).

Insert:  returncode:  The return code associated with the error

Insert:  reason:  The reason associated with the error

Reason:  The MBO CLI processor was unable to set the IDLE time

Action:  Correct the error and retry.


Error E 9930

Format:  E9930 MBOCLI  : Invalid # of arguments passed to the SETCONFIG command.

Reason:  The MBO CLI command was entered with missing arguments

Action:  Check the command syntax and reissue the command.


Error W 9931

Format:  W9931 MBOCLI  : SETCONFIG    failed:  (keyword)=(value):  (reason)

Insert:  keyword:  The configuration keyword being set

Insert:  value:  The configuration keyword value being set

Insert:  reason:  The reason associated with the error

Reason:  An error return code was received in response to this request

Action:  Correct the error and retry.


Note N 9932

Format:  N9932 MBOCLI  : SETCONFIG completed:  (keyword)=(value)

Insert:  keyword:  The configuration keyword being set

Insert:  value:  The configuration keyword value being set

Reason:  An error return code was received in response to this request

Action:  Correct the error and retry.


Note N 9933

Format:  N9933 MBOCLI  : (component) Bounce has been initiated

Insert:  component:  The name of the component being bounced

Reason:  The MBO CLI processor successfully issued the BOUNCE

Action:  None.


Note N 9934

Format:  N9934 MBOCLI  : (component) Stop has been initiated

Insert:  component:  The name of the component being stopped

Reason:  The MBO CLI processor successfully issued the STOP

Action:  None.


Note N 9935

Format:  N9935 MBOCLI  : (component) Start has been initiated

Insert:  component:  The name of the component being started

Reason:  The MBO CLI processor successfully issued the START

Action:  None.


Error W 9936

Format:  W9936 MBOCLI  : MBO must be restarted for change to take effect:  (keyword)=(value)

Insert:  keyword:  The configuration keyword being set

Insert:  value:  The configuration keyword value being set

Reason:  The configuration keyword is set but cannot be modified dynamically

Action:  Stop and restart MBO to activate this configuration change


Error E 9937

Format:  E9937 MBOCLI  : SHOWCONFIG   Failed

Reason:  The SHOWCONFIG command failed to gather configuration information

Action:  Check the command syntax and reissue the command.


Note N 9938

Format:  N9938 MBOCLI  : SETXMIT Completed

Reason:  The SETXMIT command has been processed

Action:  None.


Note N 9939

Format:  N9939 MBOCLI  : RESET_MBODRY

Reason:  The RESET_MBODRY command has been processed

Action:  None.


Note N 9940

Format:  N9940 MBOCLI  : BOB_AUDIT Initiated

Reason:  The START_BOBAUDIT command has been processed

Action:  None.


Note N 9941

Format:  N9941 MBOCLI  : LCB Sacrifice (scope) initiated

Insert:  scope:  The scope of the sacrifice

Reason:  The CLI sacrifice command has been issued

Action:  None.


Note N 9942

Format:  N9942 MBOCLI  : LCB re-synchronization initiated

Reason:  The CLI resynch_lcb command has been issued

Action:  None.


Note N 9943

Format:  N9943 MBOCLI  : Session Id (session_id) [0x(session_hex)] scratched

Insert:  session_id:   The session id scratched by the CLI

Insert:  session_hex:  The session id (in hexadecimal) scratched by the CLI

Reason:  The CLI scratched an MBO session id

Action:  None.


Error E 9944

Format:  N9943 MBOCLI  : Session Id (session_id) [0x(session_hex)] was not scratched (rc=(return_code))

Insert:  session_id:   The session id not scratched by the CLI

Insert:  session_hex:  The session id (in hexadecimal) not scratched by the CLI

Insert:  return_code:  The return code from the scratch function

Reason:  The CLI failed to scratch an MBO session id

Action:  Check the session id, ensure MBO is active and try again.


Note N 9945

Format:  N9945 MBOCLI  : LCB Sacrifice for drive (drive_letter) initiated

Insert:  drive_letter:  The LCB drive to be sacrificed

Reason:  The CLI sacrifice command has been issued

Action:  None.


Note N 9950

Format:  E9950 MBOTPP  : Required parameter (keyword) missing. MBOTPP is terminating.

Insert:  keyword:  The keyword parameter which is missing

Reason:  A required MBO configuration parameter has not been set

Action:  Set the required configuration parameter and restart


Informational I 9951

Format:  I9951 MBOTPP  : Main Loop Initialization in progress

Reason:  The MBO TPP mail loop is initializing

Action:  None


Informational I 9952

Format:  I9952 MBOTPP  : Message queue pre-processing complete

Reason:  The MBO TPP message queue pre-processing has completed

Action:  None


Note N 9953

Format:  I9953 MBOTPP  : MBOTPP is initializing

Reason:  The MBO TPP is beginning its initialization

Action:  None


Informational I 9954

Format:  I9954 MBOTPP  : Process initialization complete

Reason:  The MBO TPP initialization has completed

Action:  None


Error E 9955

Format:  E9955 MBOTPP  : Process initialization failure, code (reasoncode)

Insert:  reasoncode:  The reason code associated with the error

Reason:  The MBO TPP initialization has failed

Action:  Correct the problem.  Call for support if necessary.


Error W 9957

Format:  W9957 MBOTPP  : SNA subsystem inactive

Reason:  The requisite SNA Subsystem is not active

Action:  Start the SNA subsystem and restart


Informational I 9958

Format:  I9958 MBOTPP  : Entering startup mode - about to start first conversation

Reason:  MBO TPP has initialized and is attempting to start its first conversation

Action:  None


Informational I 9959

Format:  I9959 MBOTPP  : Leaving startup mode - about to start all conversations

Reason:  MBO TPP has initialized and is attempting to start its conversations

Action:  None


Informational I 9960

Format:  I9960 MBOTPP  : Checking Desired and Current conversation counts

Reason:  MBO TPP has initialized and is attempting to start its conversations

Action:  None


Informational I 9961

Format:  I9961 MBOTPP  : All required conversations active - entering normal mode

Reason:  MBO TPP has started all required SNA conversations

Action:  None


Error E 9962

Format:  E9962 MBOTPP  : CSP Version ((version)) Mismatch - initialization cannot continue

Insert:  version:  The version of CSP

Reason:  MBO TPP has determined a produce version mismatch situation

Action:  Ensure that TPP is being run out of the same directory as the primary MBO service


Error E 9963

Format:  E9963 MBOTPP  : Failed to initialize TPP Database. Failed in (routine). RC = (returncode); errno = (reasoncode);

Insert:  routine:  The routine name or descriptive name of the calling routine

Insert:  returncode:  The return code associated with the error

Insert:  reasoncode:  The reason code associated with the error

Reason:  The MBOTPP process did not start properly and will shutdown.

Action:  MBOTPP will be restarted automatically.  Call support to determine the cause of the problem and a course of action to correct the cause.


Informational I 9964

Format:  I9964 MBOTPP  : (conversation) : (message)

Insert:  conversation:  The conversation Id from which the message is being issued

Insert:  message:  The informational message text

Reason:  This is the general purpose Disp_Status message

Action:  None


Note N 9965

Format:  N9965 MBOTPP  : (conversation) : (message)

Insert:  conversation:  The conversation Id from which the message is being issued

Insert:  message:  The informational message text

Reason:  This is a status change Disp_Status message

Action:  None


Error W 9966

Format:  W9966 MBOTPP  : (conversation) : (message)

Insert:  conversation:  The conversation Id from which the message is being issued

Insert:  message:  The informational message text

Reason:  This is a warning Disp_Status message

Action:  None


Error E 9967

Format:  E9967 MBOTPP  : (conversation) : (message)

Insert:  conversation:  The conversation Id from which the message is being issued

Insert:  message:  The informational message text

Reason:  This is an error Disp_Status message

Action:  None


Error E 9968

Format:  E9968 MBOTPP  : Comm subsystem not initialized

Reason:  This SNA Subsystem is not active

Action:  Start the SNA subsystem and restart


Note N 9969

Format:  N9969 MBOTPP  : argv[(index)]=(ptr), num((numeric)), ptr((ptrval)), hex((hex)), string((string))

Insert:  index:  The argv[] index for the displayed values

Insert:  ptr:  The address of the argv[] value

Insert:  numeric:  The numeric (decimal) representation of the argv[] value

Insert:  ptrval:  The pointer representation of the argv[] value

Insert:  hex:  The hexadecimal representation of the argv[] value

Insert:  string:  The argv[] value printed as a string

Reason:  An MBO TPP thread has been started with incorrect arguments

Action:  Note values and call for support.


Error E 9970

Format:  E9970 MBOTPP  : ERROR:  "(filename)" truncated due to invalid ENTX header

Insert:  filename:  The name of an sfile which has been truncated

Reason:  While parsing through an Sfile, data was reached which did not have a properly formatted ENTX header structure.  This can occur following a partial disaster recovery where the MBO data base has been restored at a back level.  If this is not the case, this would indicate an internal logic error.  If a restore of the data base has occurred, this does not indicate an internal error, and may be ignored.

Action:  See reason text above.  Contact support if necessary.


Error E 9971

Format:  E9971 MBOTPP  : ERROR:  "(filename)" terminated prematurely

Insert:  filename:  The name of an sfile which has terminated prematurely

Reason:  While processing an Sfile, the data within the Sfile terminated prematurely, meaning that the last BOB is the Sfile has been corrupted and does not contain all of the data necessary for the BOB to be complete and whole.

Action:  Contact support.


Note N 9972

Format:  N9972 MBOTPP  : Shutdown message received

Reason:  MBO TPP received a shutdown request message

Action:  None


Note N 9973

Format:  N9973 MBOTPP  : Shutdown in progress

Reason:  MBO TPP is beginning its shutdown

Action:  None


Note N 9974

Format:  N9974 MBOTPP  : Main Loop processing complete

Reason:  MBO TPP main loop has terminated

Action:  None


Note N 9975

Format:  N9975 MBOTPP  : Entering shutdown mode due to receipt of signal code (signal)

Insert:  signal:  The signal value received

Reason:  MBO TPP entering shutdown due to a shutdown signal

Action:  None


Note N 9976

Format:  N9976 MBOTPP  : TPP monitor process has terminated

Reason:  MBO TPP has completed its shutdown

Action:  None


Informational I 9977

Format:  N9977 MBOTPP  : Entering stage 1 shutdown

Reason:  MBO TPP is entering the first stage of its shutdown process

Action:  None


Note N 9978

Format:  N9978 MBOTPP  : Escalating stage 1 shutdown

Reason:  MBO TPP is escalating its shutdown

Action:  None


Informational I 9979

Format:  I9979 MBOTPP  : Entering stage 2 shutdown

Reason:  MBO TPP is entering the second stage of its shutdown process

Action:  None


Note N 9980

Format:  N9980 MBOTPP  : Escalating stage 2 shutdown

Reason:  MBO TPP is escalating its shutdown

Action:  None


Informational I 9981

Format:  I9981 MBOTPP  : Entering stage 3 shutdown

Reason:  MBO TPP is beginning its third stage of shutdown

Action:  None


Error W 9982

Format:  W9982 MBOTPP  : Shutdown failed

Reason:  MBO TPP did not complete normal shutdown

Action:  None


Note N 9983

Format:  N9983 MBOTPP  : Shutdown Complete

Reason:  MBO TPP has completed its shutdown

Action:  None


Error W 9984

Format:  W9984 MBOTPP  : CSP Password will expire : (date)

Insert:  date:  The date when the CSP password is set to expire

Reason:  The Mainframe Backup Option password is set to expire at the stated date

Action:  None


Error E 9985

Format:  E9985 MBOTPP  : Communication failure with database process. file (sourcefile), line (lineno), status = (returncode); errno = (reasoncode)

Insert:  sourcefile:  The source file name

Insert:  lineno:  The source file line number issuing the error

Insert:  returncode:  The return code associated with the error

Insert:  reasoncode:  The reason code associated with the error

Reason:  MBO TPP failed in its data base I/O

Action:  Call for support


Error E 9986

Format:  E9986 MBOTPP  : Unexpected return from a conversation thread

Reason:  An MBO TPP thread has returned unexpectedly to main TPP code

Action:  Call for support


Error E 9987

Format:  E9987 MBOTPP  : Fatal error opening MBOTPP database - stop and restart MBO Service

Reason:  MBOTPP suffered a fatal error opening its database.  To ensure proper recovery, all backup and restore jobs must be stopped andthe MBO service must be shutdown and restarted.

Action:  Call for support


Error 12002

12002 E  License Violation Detected

Reason:  An attempt has been made to perform an operation that is not available under current license terms.  See error message for details.

Action:  Get a valid OLF file.  Call for support.


UNIX Agent Error Messages

UNIX Agent Error 9030	UNIX Agent Error 9032	UNIX Agent Error 9033	UNIX Agent Error 9034
UNIX Agent Error 9035	UNIX Agent Error 9040	UNIX Agent Error 9041	UNIX Agent Error 9042
UNIX Agent Error 9043	UNIX Agent Error 9101	UNIX Agent Error 9110	UNIX Agent Error 9112
UNIX Agent Error 9114	UNIX Agent Error 9120	UNIX Agent Error 9121	UNIX Agent Error 9122
UNIX Agent Error 9123	UNIX Agent Error 9124	UNIX Agent Error 9126	UNIX Agent Error 9127
UNIX Agent Error 9128	UNIX Agent Error 9129	UNIX Agent Error 9131	UNIX Agent Error 9133


UNIX Agent Error 9030

Format:  E9030 Failed to allocate filter buffer [number bytes]

Cause/Solution:

Contact support services.


UNIX Agent Error 9032

Format:  E9032 Failed to create file [filename]

Cause/Solution:

Contact support services.


UNIX Agent Error 9033

Format:  E9033 Failed to open file [filename]

Cause/Solution:

Contact support services.


UNIX Agent Error 9034

Format:  E9034 Failed to get free buffers

Cause/Solution:

Contact support services.


UNIX Agent Error 9035

Format:  E9035 Error reading file [filename]

Cause/Solution:

Contact support services.


UNIX Agent Error 9040

Format:  E9040 Failed to start database session, [number]

Cause/Solution:

Contact support services.


UNIX Agent Error 9041

Format:  E9041 Failed to add record to ARCserve database, [record number]

Cause/Solution:

Contact support services.


UNIX Agent Error 9042

Format:  E9042 Failed to end database session, [number]

Cause/Solution:

Contact support services.


UNIX Agent Error 9043

Format:  E9043 Failed to Locate [filename] at [undertermined]

Cause/Solution:

Contact support services.


UNIX Agent Error 9101

Format:  E9101 Invalid Filter [string] Ignored

Cause/Solution:

Contact support services.


UNIX Agent Error 9110

Format:  E9110 Unknown filter type – [number]

Cause/Solution:

Contact support services.


UNIX Agent Error 9112

Format:  E9112 Failed to write to destination directory, [directory number] rejected the request

Cause/Solution:

Contact support services.


UNIX Agent Error 9114

Format:  E9114 Failed to change uid on WS

Cause/Solution:

Contact support services.


UNIX Agent Error 9120

Format:  E9120 Failed to Access Directory [Directory Name]

Cause/Solution:

Contact support services.


UNIX Agent Error 9121

Format:  E9121 Failed to Compare [string1] [string 2]

Cause/Solution:

Contact support services.


UNIX Agent Error 9122

Format:  E9122 Failed to Lock File [filename]


Cause/Solution:

Contact support services.


UNIX Agent Error 9123

Format:  E9123 Failed to Read Symbolic Link File [filename]

Cause/Solution:

Contact support services.


UNIX Agent Error 9124

Format:  E9124 Failed to Restore Linked File [filename]

Cause/Solution:

Contact support services.


UNIX Agent Error 9126

Format:  E9126 Failed to Restore Special File [filename]

Cause/Solution:

Contact support services.


UNIX Agent Error 9127

Format:  E9127 Failed to Set [attributes] Attributes

Cause/Solution:

Contact support services.


UNIX Agent Error 9128

Format:  E9128 Failed to Set [date and time] Date & Time

Cause/Solution:

Contact support services.


UNIX Agent Error 9129

Format:  E9129 Failed to Write [string] data

Cause/Solution:

Contact support services.


UNIX Agent Error 9131

Format:  E9131 File [filename] is truncated on the WS

Cause/Solution:

Contact support services.


UNIX Agent Error 9133

Format:  E9133 File [filename] is Locked by Another Process

Cause/Solution:  Contact support services.


Error 3155

Unable to prepare for Active Directory restore.

Explanation:  ASTASK cannot prepare the Active Directory server for restore operation.

Cause/Solution:  	Make sure machine is booted in Directory Service Restore mode. Reboot into Directory Services

Restore mode and retry the System State session.


Error 3156

Unable to prepare for Active Directory backup.(EC:%u)

Explanation:  ASTASK cannot prepare the Active Directory server for backup operation.

Cause/Solution:  Check the error code and make sure machine is boot in normal mode.


Error 3157

Unable to backup Active Directory database, Active Directory is not running.

Explanation:  Active Directory can be backed up only when it is online.

Cause/Solution:  Make sure machine is boot in normal mode and Active Directory is properly installed.


Error 3158

Failed to read Active Directory file. (PATH:%s, EC:%u).

Explanation:  ASTASK cannot read Active Directory file.

Cause/Solution:  Check the error code


Error 3159

Failed to close Active Directory file. (PATH:%s, EC:%u).

Explanation:  ASTASK cannot close the Active Directory database file after backup of the file.

Cause/Solution:  Check the error code


Error 3160

Failed to register the Active Directory restore operation. (EC:%u).

Explanation:   ASTASK cannot register the files restored in Active Directory restore operation.

Cause/Solution:  Check the error code. After error is corrected, reboot in Directory Services Restore mode and restore System State session.


Error 3161

Failed to complete the Active Directory restore operation. (EC:%u).

Explanation:  ASTASK cannot register the completion of Active Directory restore operation.

Cause/Solution:  Check the error code. After error is corrected, boot in Directory Services Restore mode and restore System State session.


Error 3162

Failed to end Active Directory restore job. (EC:%u).

Explanation:  ASTASK cannot end the restore of Active Directory database.

Cause/Solution:  Check the error code. After error is corrected, boot in Directory Services Restore mode and restore System State session.


Error 3164

Unable to truncate Active Directory database logs, (EC:%u).

Explanation:  ASTASK cannot truncate Active Directory database log file after the backup of the file.

Cause/Solution:  Check the error code.


Error 3165

Unable to end Active Directory backup job, (EC:%u).

Explanation:  ASTASK cannot end Active Directory database backup operation.

Cause/Solution:  Check the error code.


Error 3166

Unable to get Active Directory database files (Node:%s).

Explanation:  ASTASK cannot retrieve the list of Active Directory database file names that need to be backed up.

Cause/Solution:  	Check the error code


Error 3167

Unable to get Active Directory database log files.

Explanation:  ASTASK cannot retrieve the list of Active Directory database log files which need to be backed up.

Cause/Solution:  Check the error code.


Error 3168

Failed to detect if Certificate Services is online. (EC:%u).

Explanation:  ASTASK cannot detect if Certificate Service is online. Certificate Service database can only be backed up when it is online and restored when offline.

Cause/Solution:  Check the error code and check if Certificate Service is installed properly.


Error 3169

Unable to backup Certificate Services database, Certificate Server is offline.

Explanation:  Certificate Service is currently offline. Certificate Service can be backed up only when it is online.

Cause/Solution:  Run 'Certificate Authority' utility under 'Start\Programs\Administrative Tools' to start the service and restart the backup job.


Error 3170

Failed to prepare for Certificate Services backup. (EC:%u).

Explanation:  ASTASK cannot prepare a Certificate Service server for backup.

Cause/Solution:  Check the error code and use 'Certificate Authority' utility under 'Start\Programs\Administrative Tools' to see if Certificate Service has been started properly.


Error 3171

Unable to get Certificate Services database file list.(EC:%u).

Explanation:  ASTASK cannot retrieve the list of Certificate Service database file names that need to be backed up.

Cause/Solution:  Check the error code and use 'Certificate Authority' utility under 'Start\Programs\Administrative Tools' to see if Certificate Service has been started properly.


Error 3172

Unable to get Certificate Services database log files. (EC:%u).

Explanation:  ASTASK cannot retrieve the list of Certificate Service database log file names which need to be backed up.

Cause/Solution:  Check the error code and use 'Certificate Authority' utility under 'Start\Programs\Administrative Tools' to see if Certificate Service has been started properly.


Error 3173

Unable to truncate Certificate Services database logs, (EC:%u).

Explanation:  ASTASK failed to truncate Certificate Service database log file after backup.

Cause/Solution:  Check the error code and use 'Certificate Authority' utility under 'Start\Programs\Administrative Tools' to see if Certificate Service has been started properly.


Error 3174

Unable to get Certificate Services database dynamic files. (EC:%u).

Explanation:  ASTASK cannot retrieve the list of Certificate Service dynamic file names which need to be backed up.

Cause/Solution:  Check the error code and use 'Certificate Authority' utility under 'Start\Programs\Administrative Tools' to see if Certificate Service has been started properly.


Error 3179

Failed to stop Certificate Services for restore operation. (EC:%u).

Explanation:  Certificate Service is currently online. ASTASK cannot stop the Certificate Service before the Certificate Service database restore operation.

Cause/Solution:  Check the error code and make sure the System State restore is performed in 'Directory Service Restore mode. Try stopping Certificate Service using 'Certificate Authority' utility under 'Start\Programs\Administrative Tools' and run restore job again.


Error 3180

 Failed to prepare for Certificate Services restore. (EC:%u).

Explanation:  ASTASK cannot prepare a Certificate Service server for the restore operation.

Cause/Solution:  Check the error code and make sure the System State restore is performed in 'Directory Service Restore mode'. After the restore of System State, the machine needs to be rebooted right away. If System State restore job runs more than once without reboot, this error may happen. If it is that is the case now, reboot to Directory Service Restore mode and run the System State restore job again and reboot.


Error 3182

Failed to register a Certificate Services Database restore operation. (EC:%u).

Explanation:  ASTASK cannot register the files restored in Certificate Service database during the restore operation.

Cause/Solution:  Check the error code.


Error 3183

Failed to end Certificate Services Database restore job. (EC:%u).

Explanation:  ASTASK cannot register the completion status of the Certificate Service restore operation.

Cause/Solution:  Check the error code. After error is corrected, reboot in Directory Services Restore mode and restore System State session.


Error 3263

 SYSVOL: %s (%d).

Explanation:  There was an error interaction with the SYSVOL functionalities in the system. Caused when interacting with SYSVOL as part of the backup or restore operation of the System State.

Cause/Solution:  Caused when the SYSVOL is locked by a previous operation. Please reboot the system and retry backup or the restore of the System State.


Error 3260

Error interacting with System Volume. (EC=%s).

Explanation:  Error while backing up or restoring SYSVOL as part of the system state.

Cause/Solution:  Indicates that there was a error interacting with SYSVOL. Error in conjunction with one or more 3263 errors.


Error 3262

Error processing SYSVOL files.

Explanation:  Error  while backing up the SYSVOL files to the tape

Cause/Solution:  Caused in conjunction with other device related errors


Error 3270

Error interacting with Com+ database. (EC=%s).

Explanation:  Error  while backing up or restoring COMPLUS as part of the system state

Cause/Solution:  Indicates that there was a error backing up or restoring the ComPlus database. Please reboot the system and try again


Error 3271

Error processing COM+ files.

Explanation:  Error  while backing up the COMPLUS files to the tape

Cause/Solution:  Caused in conjunction with other device related errors.


Error 3081

Unable to backup system state for remote machines. (MACHINE).

Explanation:  Backup and Restore of System State for remote machines can be done only via the Client agent for Windows NT/2000

Cause/Solution:  If the node was backed up using the Windows 2000 agent, Install Windows 2000 Agent on that remote machine Go through Client

Agents/Windows 2000 agents to select the System State of the remote machine and submit the restore job.


Error 3082

Unable to restore system state for remote machines. (MACHINE).

Explanation:  Backup and Restore of System State for remote machines can be done only via the Client agent for Windows NT/2000

Cause/Solution:  If the node was backed up using the Windows 2000 agent, Install Windows 2000 Agent on that remote machine.

Use the Client Agents to select the System State of the remote machine and submit the restore job.


Error 3083

Unable to restore system state to an alternate location. (PATH).

Explanation:  Restore of System State can be made only to the location from which it was backed up.

Cause/Solution:  Do not try to restore the System State to machines other than the one it was backed up from. Doing so can have unexpected results.


Error 3084

Unable to backup system state in Directory Service Repair mode.

Explanation:  Backup of the system is being attempted in the Directory Services Restore Mode.

Cause/Solution:  Reboot the machine into the normal mode and retry the operation.


Error 3085

Unable to restore system state to target other than Windows 2000. (MACHINE).

Explanation:  Restore of a System State session is being attempted on a non Windows 2000 machine.

Cause/Solution:  System State is a Windows 2000 feature and is not supposed to be restored to a Windows NT 4.0 machine.


Error 3250

Error interacting with cluster. (EC=%s).

Explanation:  Error interactiong with the cluster

Cause/Solution:  Can be caused due to an Improper installation of the cluster  services. Ensure that the cluster service is running.


Error 3251

No installation of Cluster detected.

Explanation:  Cluster not installed on this node

Cause/Solution:  Prompted when attempting to take a backup or a restore on a node that does not have cluster installed.


Error 3252

Cluster configured on this system, but not running.

Explanation:  Cluster was found on this system but not running.

Cause/Solution:  This is a normally displayed as a warning and indicates that the software found the cluster service not to be running. The node will be considered as any normal server for backup or restore operations.


Error 3253

Cluster service is currently online.

Explanation:  Cluster service was found to be running.

Cause/Solution:  Restore operation of the cluster database from a System State restore failed due to the above. Use the System State restore options to force ARCserve to stop the cluster and proceed with the restore.


Error 3254

Unable to find the cluster quorum.

Explanation:  Cluster quorum was not found.

Cause/Solution:  Restore operation of the cluster database from a System State restore failed. Restore did not find the quorum resource that was in use during the time of the backup. Use the System State restore options to indicate a different volume that ARCserve is to use as cluster quorum.


Error 3255

Error processing cluster files.

Explanation:  There was a error backing up the cluster related files on to the tape.

Cause/Solution:  This error would be in conjunction with other errors that may be device related.


Error 11104

Error occurred on the Serverless Backup Source Device.

Explanation:  ARCserve Tape Engine detects a SCSI check condition on the source device when running a job in Serverless Mode.

Cause/Solution:  Please check for the error code.  This type of error can be caused by device Power On Reset, or other hardware related errors.


Error 11105

Error occurred on the Serverless Backup Target Device.

Explanation:  ARCserve Tape Engine detects a SCSI check condition on the Target device when running a job in Serverless Mode.

Cause/Solution:  Please check for the error code.  This type of error can be caused by device Power On Reset, or other hardware related errors.


Error 11106

Error occurred on the Serverless Backup Data Mover.

Explanation:  ARCserve Tape Engine detects a SCSI check condition on the Data Mover when running a job in Serverless Mode.

Cause/Solution:  Please check for the error code.  This type of error can be caused by device Power On Reset, or other hardware related errors.


Error 11107

Extended Copy failed

Explanation:  ARCserve Tape Engine detects a SCSI check condition when running a job in Serverless Mode.

Cause/Solution:  Please check for the error code.  This type of error can be caused by device Power On Reset, or other hardware related errors.


Error 6609

Not enough tapes to do RAID Format.

Explanation:  Not enough tapes to do RAID Format.

Cause/Solution:  Tape missing from the RAID set. Add the missing tape.


Setting up volumes for Data Migration

Setting up your volumes properly is critical in Data Migration.

1.	You must first enable data migration  which includes defining Migration Routes, setting up watermarks, applying filters, and setting schedules and repeat cycles for your migration jobs.

2.	Once you have enabled data migration, you can customize volume Level Migration Criteria, as well as the directory and subdirectory level Migration Criteria.


Enable Data Migration

Once the DM Agent and the Migrated Data Storage Services have been installed, the system will guide you through a sequence of steps to enable Data Migration:

You must first define your migration routes, or the paths that data will migrate from volumes on your network machine to the individual DM storage devices in your hierarchy based on the usage and age of data.

Then you will set the watermark's of automatic migration, Watermarks are levels of data on a volume at which you specify priorities for migration.

Filters will be configured for your files. Including age, pattern, size, and attribute filters

You will then define a schedule for your migration jobs. And lastly,

You will define repeat cycles of your migration jobs.


Related Topics

  Step-by-Step Procedure for Enabling Data Migration

  Watermarks

  Filters


Watermarks for Data Migration

Watermarks are levels of data on a volume at which you specify priorities for migration.  There are three watermarks in the Data Migration Option for ARCserve, Low, High, and Critical.

Low - Scheduled migration stops at this level when the high watermark is reached and scheduled migration is initiated.

High - At this watermark, migration occurs according to the schedule.  If this watermark is not reached during the migration schedule, no data will be migrated.

Critical - When this level is reached, migration will be triggered immediately regardless of the schedule.  Data migrates until the high watermark is reached.

To modify the watermarks, right click on the volumes, then select Configure, then Watermarks.


Filters

There are several filters available in the DM Option:

File age filters - which let you selectively migrate data based on a file's age.  File age can be defined based the date of the creation date, last modification date, or last accessed date.

Directory/file pattern filters - which allow you to selectively include or exclude files by name or extension patterns (*.EXE, *.BIN, *.SYS, etc.) or files in a specific directory or subdirectory.  This type of filter can be created for directories and subdirectories.  You can use exact text or wildcards (* or ?) to specify files.

File size filters - which allow you to define filters for upper and lower size restrictions to the subdirectory-level.  Once you have specified the values, files with sizes outside of the specified size ranges will be excluded from migration jobs.

Defining File Attribute Filters - allow  you to define the attribute filters for including or excluding files by attribute (Read only, Archive, Hidden, System, and Compressed).


File Age Filters

File age filters let you selectively migrate data based on a file's age.  File age can be defined based the date of the creation date, last modification date, or last accessed date.

The file age filter can be set to the subdirectory-level.  Therefore, each subdirectory can have its own file age requirement for migration.  Only those files meeting the age requirement will be migrated regardless of volume usage.

For example, even when the volume usage reaches the critical watermark and triggers a critical migration, no files will be migrated if they do not meet the file age criteria.  However, you can set the option to migrate files that meet the file age criteria regardless of the watermark settings.  This option is set in the Advanced File Age Filter Options dialog box.


Related Topics

  Click here for the procedure.


Directory/file pattern filters

Directory/File Pattern Filters allow you to selectively include or exclude files by name or extension patterns (*.EXE, *.BIN, *.SYS, etc.) or files in a specific directory or subdirectory.  This type of filter can be created for directories and subdirectories.  You can use exact text or wildcards (* or ?) to specify files.

Files meeting the filter conditions will be included or excluded depending on the filter type.  Multiple filters can be specified for directories or subdirectories.


Related Topics

  Define Directory/File Pattern Filters for Migration Enabled Volumes


File Size Filters

You can define filters for upper and lower size restrictions to the subdirectory-level.  Once you have specified the values, files with sizes outside of the specified size ranges will be excluded from migration jobs.


Related Topics

  Reset File Size Filters for Migration Enabled Volumes


Defining File Attribute Filters

You can define the attribute filters for including or excluding files by attribute (Read only, Archive, Hidden, System, and Compressed).

File attribute filters are considered to be a match when at least the set of named attributes matches the existing attributes in the file.  However, the files can contain additional attributes not specified in the filter.

For example, a file with the -r and -s attributes and another file with the -r, -s, and -h attributes will both be considered a match to the filter which contains the -r and -s attributes.


Related Topics

  Reset File Attribute Filters for Migration Enabled Volumes


Customizing Migration Criteria

Most migration criteria, from volume-level to the lowest subdirectory-level can be customized.  This section describes each of the criteria, which are considered to be "properties" of the volume, or subdirectories. The available properties for the volume are slightly different than the subdirectories.

The criteria are broken up in the following directories:

Migration State

Migration Route

Watermarks

Filters

Migration Schedule


Migration Selection State

The migration selection state indicates if a directory (or an entire volume or file) is selected for migration.  This property is represented by the green box shown beside the file, volume or directory.  You can either set the property here, or simply click on the green box to set this property.  If a subdirectory is selected (fully green), it will be scanned for eligible files when migration is initiated.  If it is not selected, it will not be scanned at all.  However, even if a subdirectory is not selected, the subdirectories or files lower in the directory structure can still be selected for migration.

This property is useful if you want to select some directories for migration, or the other way around. This gives you the ability to control migration by directories. Of course, even when a directory is selected, the files in the directory are still subject to other criteria to specify whether or not they are eligible for migration.

Inheritance of migration selection state

Once a directory is selected for migration, all subdirectories below it are automatically selected, unless a subdirectory is specifically deselected.  In that case, all subdirectories below it are deselected for migration until otherwise specified.  Therefore, subdirectories inherit their immediate parent directory's migration selection state, unless it has been specifically defined.


Migration Route

You can define or redefine the migration route for volumes from the Data Migration tab of the Properties dialog box.

Defining the migration route allows you to select the target DM Storage on which you will migrate data from the current volume.  When you enabled the volume, the wizard for enabling migration set up the initial migration route.  However, you can change, add, or remove migration stages from the route, as needed.


Related Topics

  Redefine the Migration Route


Test Results

You can view the following reports in the Test Results ... dialog box:

The Summary tab contains the results of the communication test between all of the stages in the migration route.

The second tab, named after the source machine, reports the status of the for that machine.  In the following example, the status of "My Workstation" is displayed.

The remaining tabs, named after the machines on which the DM Storages in the migration route are located, report the status of the DM Storages in the hierarchy.  For example, the total media, space available, and space used for storing migrated data on the DM Storages in your migration route, and the hardware status of the storage devices is shown.


Define Media Set

Right-click on an optical or tape storage in your migration route and select Define Media Set... to select an existing media set to store migrated data for the volume.


General Properties
General Properties of the DM Agent

To view or edit the general properties of the DM Agent, do the following:

In the DM Admin's browser, right click on the DM Agent icon, then select Properties.

The Properties of the DM Agent dialog box appears.

You can view and/or edit the following:

Type the name of the new ARCserve host machine on which the default ARCserve job engine resides.

View the amount of time that the DM Engine and filter have been running.

View the status of the DM Agent.

Type of license for the DM Agent.


Configuring the DM Agent

This Configuration screen allows the DM Agent to record job activities in the event log.

Use the following procedure to configure the DM Agent to write job related activity to the Application Event Log:

In the tree of the DM Admin's browser, right click on the DM Agent icon below the DM Admin Components icon, then select the Properties menu option.

The Properties of DM Agent dialog box appears.

You can view and/or edit the following:

Which job activities you want to record in the event log.

The Critical Check Interval, which is an interval for checking the volume of data on DM Storages.

Choose if you wish to scan files for viruses prior to migration.


User Properties of the DM Agent

User Properties allows you  to set demigration restrictions for all users on a per-hour basis.


Related Topics

  Restrict Demigration


General Properties of the DM Storage

You can view or edit the following properties of your DM Storage devices by right clicking on the DM Storages node of the browser, then selecting the General tab of the Properties of ... dialog box.

You can view the following:

The version and build number of your DM Storage software.

The period of time in which the DM Storage service has been running.

The status of the DM Storage services.

The current storage capacity and space available on your DM Storages.

The total amount of migrated data stored on DM storage devices.

The total media available on optical or tape storage devices.

Or, you can Select to prevent the DM Storage from accepting any migrated data.  Only demigrations will be allowed.


Ad Hoc Demigration

Ad hoc migration allows you to demigrate files in an efficient manner.  Normally, files are automatically demigrated when users access the files.  However, user access normally comes in random order, which will cause multiple tapes to be rewound and media swapping.  If you are aware that specific data will be referenced, you can perform a demigration job ahead of time to avoid access delays.

When you initiate a demigration job, the system will sort the list of files to be demigrated to the best order according to the physical location of the migrated media.  Therefore, demigration jobs guarantee data retrieval for all selected files in a single pass loading all required media once with minimum tape rewinding.  In a demigration job, you can select to demigrate with a trace or to demigrate without a trace.

You initiate demigration using either the drag-and-drop or the right-click method.  However, the results are different depending on the method you use.


Related Topics

  Ad Hoc Demigration

  Demigrate with a Trace

  Demigrate without a Trace

  Drag-and-Drop Method

  Right-Click Method


Demigrating data with a trace

If you demigrate without a trace, a copy of the demigrated data is left on the DM Storage.  This file will be considered to be demigrated.  If a demigrated file is migrated again, the system will attempt to verify the file in the DM Storage.  If the file has changed, then a new copy will replace the older file on the DM Storage.  If the file has not changed, then the file will be converted back to a migrated entry and not data will be transferred.


Demigrating data without a trace

If you demigrate data without trace, the copy in the DM Storage will be discarded.  If the DM Storage is rewritable, then the copy will be deleted.  For non-rewritable media, including tape, the copy will be left orphaned, i.e. it will remain on the storage but no reference will be made to it.  The demigrated file will be treated as though it had never been migrated.


Ad Hoc Verification

All migrated files are verified immediately after migration before the files are converted to stub files on the primary volume.  However, if you want to confirm the data integrity on the DM storage media, you can perform an ad hoc verification for any directory or volume.

The verification process will actually read the each selected file and perform a CRC verification check to confirm that the CRC checksum still matches the original checksum when the file was migrated.


Related Topics

  Verify Specific Volumes or Directories


Migration Schedule

When you enable a volume for data migration, you define a default migration schedule with a repeat cycle .  You can later define a different migration schedule for subdirectories by right-clicking on a directory and selecting Configure\Migration Schedule.

Inheritance of migration schedules

When a volume is enabled for migration, a default volume-level schedule is defined.  However, you can define a schedule for each folder.  If a directory defines its own schedule, then the parent schedule no longer applies.  All subsequent subdirectories also use the current schedule.

All of the parameters described in this topic provide you with all of the necessary tools to set up automatic migration for a volume.  If you properly configure your migration parameters in accordance with the rate of your data accumulation in your system.  The appropriate data levels should be maintained by the data migration scheme.


Related Topics

  Repeat Cycle


Create Media Set

Type the name for the media set in the edit box, then select OK.

NOTE:   Each migration enabled volume can be configured to use either exclusive media or media belonging to a specific   media set.


Repeat Cycles

You can define system migration schedules for the volume or individual subdirectories.  A default schedule was set up when the volume was enabled for migration.


Primary Volume Properties Screen

You can analyze volume usage in the Properties of… dialog box.


Related Topics

  Analyze the Statistics of your Primary Volumes


Installing the Data Migration Option

The Distributed Data Migration Option's program files are installed locally when you install ARCserve.  You must propagate the various components throughout your network in the DM Admin, a browser-like graphical user interface similar to the Windows Explorer.

To setup the DM Option on your network, you must install three components:

DM Storages - You install DM Storages on network machines managing devices to which you want to store migrated data from primary volumes.

DM Agent - You install the DM Agent on the network machines from which you want to migrate data.

DM Shell Extension - You install the DM Shell Extension on the network machines which access the data on network machines which have migrated data to secondary storages.


Installing DM Storages

The DM Option supports three types of devices for storing migrated data:

Magnetic hard disks (NTFS format).

Optical drives and jukeboxes.

Tape devices and autochangers.

Each type of storage device has separate software for managing migrated data.  You must install this software on the appropriate machines on your network, which manage the devices.

NOTE:  The following topics contain ONLY the right-click navigation to install.  Once the installation option is selected, follow the setup procedure.


Setting up NT volumes for data migration

You install DM Storages on the target NT machine to configure its NT volumes from the DM Admin.  Since the NT volumes are magnetic hard disks and have a faster access time than an optical or tape storage devices, you should use the NT volume as your secondary storage device.


Related Topics

  Install NT Volume Software on an NT Machine


Setting up Tape DM Storages for data migration

Since tape devices have the slowest access time, and you should erase each tape when you no longer want to store migrated data on it to prevent tape devices from reading the entire tape contents when migrating or demigrating data.  Also, tape devices should comprise the last stage of your data migration storage hierarchy due to their slow access times and the need to manually erase demigrated data from them.  You can either store migrated data from a volume on its own tape, or you can create media sets for storing data from multiple volumes on an tapes.

Note:  You must import blank tape media to a tape device before you can migrate data to that device.


Related Topics

  Set up a Tape Device for Data Migration

  Create Media Sets


Setting up optical storage devices for data migration

You must install the DM Storage for managing migrated data on optical devices on the network machines which manage your optical devices.  You can either store migrated data from a volume on its own disk, or you can create media sets for storing data from multiple volumes on an optical disk.

Note:  You must import blank optical disks to an optical storage device before you can migrate data to that device.


Related Topics

  Install Optical DM Storages on NT Machines

  Create Media Sets


Installing the DM Agent

The DM Agent is the component which you must install on all of the volumes of network machines from which you want to migrate data.  The DM Agent uses the ARCserve job engine to process data migration, so the ARCserve job engine must be also be running to migrate data.  The DM Agent communicates with the DM Storages to migrate and demigrate data, stores the linkages between stub files and migrated data on DM storage devices.

When you install the DM Agent, the DM Shell Extension is automatically installed.  However, you can install the DM Shell Extension individually.

Note:  You must install your DM Storages before you install the DM Agent.

The DM Agent consists of three different services:

The Data Migration Engine (DMengine)

The Data Migration Provider (DMP)

File Monitor Filer Driver (FSM.SYS)


Related Topics

  Install the DM Agent


Installing the DM Shell Extension

To install the DM Shell Extension, you must have a license to install the DM Agent.

When you install the DM Agent, the DM Shell Extension is automatically installed.  However, you can install the DM Shell Extension individually.


Related Topics

  Install the DM Agent


Creating Media Sets

You can create media sets to allow multiple primary volumes to migrate data to the same media, such as one optical disk or tape.  Otherwise, each primary volume must have its own separate tape or optical disk.


Related Topics

  Create media Sets


Primary volumes

Primary volumes are volumes on your network servers or workstations from which you want to migrate data to increase performance and storage capacity.  Migration enabled volumes appear in the DMM with green squares next to them.


Data Migration

ARCserve comes with limited data migration options to further enhance your data management capabilities.  For further information, see:

General Properties

General Properties of the DM Storage

Installing the Data Migration Option

Installing DM Storages

Installing the DM Agent

Installing the DM Shell Extension

Once the DM Agent and the Migrated Data Storage Services have been installed, the system will guide you through a sequence of steps to enable Data Migration:

Customizing Migration Criteria

Enable Data Migration

Migration Route

Migration Schedule

Migration Selection State

Configuring the DM Agent


Ad Hoc Migration

You can initiate ad hoc migration using either the drag-and-drop or the right-click method.  However, the results are different depending on the method you use.

Using the right-click method:

Right click on a directory in the tree of the browser or file(s) in the window of the DM Admin, then select Migrate from the menu.

The Migrate wizard appears.

You can select whether or not to force migration.  If you force migration, all previously specified migration criteria are ignored.  All selected files will be migrated.  However, if you have a multi-stage hierarchy, the file age property will be used to distribution of the migrated data to the appropriate stage.

The following rules will apply:

All files meeting the respective stage's age requirement will be migrated to the appropriate stage.

All files not meeting any stage's age requirement will be migrated to the first DM Storage stage in the hierarchy.

If migration is not forced, all migration criteria apply and only the files meeting those criteria are migrated.

Once you have chosen your migration options, click on the Next button, to schedule your migration.

Using the drag-and-drop method:

Click on a directory in the DM Admin's browser and drag it to the DM extended storage icon or an icon immediately beneath the expanded DM Storages icon, then let the left mouse button go.

If you migrated data using the drag-and-drop method, the following rules apply:

If you drag the source files to the DM Extended Storage icon under the volume on the browser, the result will be identical to the right-click method.

If you drag-and-drop files to a specific storage's icon, the files will migrate to that stage only.  If migration is forced, then all selected files will be migrated to that stage.  If migration is not forced, then only the files meeting the migration criteria and the age requirement for that stage will be migrated.

Once you have chosen your migration options, click on the Next button.

The Schedule dialog box appears.


Related Topics

  Drag-and-Drop Method

  Right-Click Method

  Schedule Ad-Hoc Operations


Application Properties of the DM Agent

Use the following procedure to restrict the demigration of files accessed by specific applications:

1.	Click on the Applications tab of the Properties of the DM Agent dialog box.

2.	On the Applications tab, double click on the <Add Application> heading in the list window.

The Do not demigrate files accessed by... dialog box appears.

3.	Type the name of the application in to the Enter application name: edit box, click on the Allow read access to stub file check box if you want to allow the application read access to the stub files, then click OK.

NOTE:   Do not include an application's path when you specify its name.  You only enter the name of the application's executable file.

4.	In the Properties of the DM Agent dialog box, click OK, or the Apply button to configure other properties in the dialog.


Drive Property Statistics

You can view the space used and space available on your primary volumes.

To view the primary volume properties, do the following:

Right-click on a primary volume and select Properties.


Edit Selections

In the DM Admin, you can select files for migration, demigration, or verification based on their file patterns.

To select files with a specific pattern for migration, demigration, or verification, do the following:

1.	In the DM Admin, select Edit\Select.

The Select Items with pattern… dialog box appears.

2.	Type the extension preceded by a wildcard and select OK.

The files with that extension are selected.


Find Computer

To find specific DM Option components or computers on your network, do the following:

1.	In the DM Admin, select Tools\Find\Computer.

The Find Computer… dialog box appears.

2.	Do one of the following steps:

To find computers:

Select the Computer Name tab, type in the name of a computer you want to browse, then select OK.

The machine appears in the browser.

To find DM components:

Select the Data Migration tab, select the green marker box next to the type of component you want to locate, then select OK.

The available components appear next to the names of the machines on which they are installed in the Scanning Computers dialog.


Hardware Properties of the DM Storage

This allows you to view the NT Volume(s) current usage in terms of Space used and Space free, and to remove that NT volume as your DM Storage.

To remove a drive from the storage, drag the drive from the list to the garbage bin.

Click on the drive you want to remove and drag it to the wastebasket to remove it as an DM Storage device, then click on the OK button or the Apply button to configure other properties in the dialog.


Step 1 of 9

Choose whether to copy an existing configuration to your primary volume

If a migration configuration already exists on an volume, and you would like to use the same configuration on the current volume, select the configuration from the list provided, then click on the Next button.  The migration route and other migration parameters will be applied to the current volume.


Step 2 of 9

Define the migration route for your primary volume

Drag the DM storage devices for each consecutive stage in your hierarchy from the DM storages dialog box to area below the icon for the NT machine.

Once the newly defined migration route appears in the dialog box, click on the Next button.


Step 3 of 9

Set the watermarks by clicking on the pointer for a particular watermark setting and dragging it towards Empty or Full, then click on the Next button.

You apply or reset different watermark settings by clicking on the levers for the different watermarks, then dragging them to the appropriate level of data for your watermark settings.


Step 4 of 9

Define File Age Filters

For example, you might configure a file age filter to migrate files from a volume to an DM storage stage 90 days after the file is last modified by doing the following:

click on the Modified option button,

double click on the number of days appearing next to the storage stage to which you want to apply a file age filter,

toggle the value in the days spin box to 90 in the Migrate files "older" than... dialog box,

click OK.


Step 5 of 9

Define File Pattern Filters

Specify the files you want to include or exclude in data migration by performing one of the following steps:

If you want to include executable files in data migration, double click on <Add Filter>, then select Include\Files.

In the Include files with pattern… dialog box, enter *.EXE to specify executable files, then select the OK button.

Similarly, you can exclude a directory by double clicking  <Add Filter>, then selecting Exclude\Directories.  Specify the directories in the Exclude directories with pattern... dialog box.


Step 6 of 9

Define the File Size Filters

NOTE:  Do not enter a value of "0" in the KB spin box beneath the "do not migrate files larger than…" check box.  If you enter this value as the size limit for migrating any files, you will not be able to migrate any files from that volume.


Step 7 of 9

Define File Attribute Filters

In the "Define File Attribute Filters dialog box, do the following:

Double-click on <Add Filter> under the Condition heading in the list box.

Double click on Include or Exclude.

In the Include files that are…dialog box, click on the check boxes for the files with Read-only, Archive, Hidden, or System Attributes.


Step 8 of 9

Define schedule

This step will allow you to set up the volume migration schedule.  This allows you to set up your migration activities in a time frame that will not interfere with the normal network traffic.  It also allows you to the length of the time so migration will stop if it exceeded the time slot.  In addition, you can define a repeating cycle, so automatic migration will take off periodically.  When migration is started at the specified date/time, it will scan for files that meet all other criteria as described by the previous properties, and only those files will be migrated.

Note:  You can define the migration schedule as a volume-level property or a subdirectory-level property.  However, if you are defining the migration schedule for a volume in the wizard for enabling migration, you cannot inherit a schedule from a parent directory.


Step 9 of 9

Define a repeat cycle

Toggle the values in the months, days, hours, and minutes spin boxes to set the interval for the repeating job.

Select the days on which you want to run the job by clicking on the day in the Include Days group.


Step-by-step procedure for enabling Data Migration

In the DM Admin's browser, do one of the following:

Click on My Workstation to expand the browser's tree and expose the nodes for the volumes on the NT server, then right click on the drive you want to enable for migration.

Or…

Click on the Network Neighborhood node of the DM Admin's browser tree, double click on the Microsoft Network node, double click on the domain(s) containing the NT machines from which you want to migrate data, double click on the individual machine(s) on which you want to enable volumes, provide the security credentials, then right click on the volumes.

NOTE: You must have administrator rights to enable volumes on remote machines for data migration

Select the Enable Migration menu option, by double clicking the right mouse button.

1.	Choose whether to copy an existing configuration to your primary volume

If a migration configuration already exists on an volume, and you would like to use the same configuration on the current volume, select the configuration from the list provided, then click on the Next button.  The migration route and other migration parameters will be applied to the current volume.

2.	Define the migration route for your primary volume

Drag the DM storage devices for each consecutive stage in your hierarchy from the DM storages dialog box to area below the icon for the NT machine.

Once the newly defined migration route appears in the dialog box, click on the Next button.

3.	Set the watermarks by clicking on the pointer for a particular watermark setting and dragging it towards Empty or Full, then click on the Next button.

You apply or reset different watermark settings by clicking on the levels for the different watermarks, then dragging them to the appropriate level of data for your watermark settings.

4.	Define File Age Filters

For example, you might configure a file age filter to migrate files from a volume to an DM storage stage 90 days after the file is last modified by doing the following:

click on the Modified option button,

double-click on the number of days appearing next to the storage stage to which you want to apply a file age filter,

toggle the value in the days spin box to 90 in the Migrate files "older" than... dialog box,

click OK.

5.	Define File Pattern Filters

Specify the files you want to include or exclude in data migration by performing one of the following steps:

If you want to include executable files in data migration, double-click on <Add Filter>, then select Include\Files.

In the Include files with pattern… dialog box, enter *.EXE to specify executable files, then select the OK button.

Similarly, you can exclude a directory by double-clicking  <Add Filter>, then selecting Exclude\Directories.  Specify the directories in the Exclude directories with pattern... dialog box.

6.	Define the File Size Filters

NOTE: Do not enter a value of "0" in the KB spin box beneath the "do not migrate files larger than…" check box.  If you enter this value as the size limit for migrating any files, you will not be able to migrate any files from that volume.

7.	Define File Attribute Filters

In the Define File Attribute Filters dialog box, do the following:

Double-click on <Add Filter> under the Condition heading in the list box.

Double click on Include or Exclude.

In the Include files that are…dialog box, click on the check boxes for the files with Read-only, Archive, Hidden, or System Attributes.

8.	Define Schedule

This step will allow you to set up the volume migration schedule.  This allows you to set up your migration activities in a time frame that will not interfere with the normal network traffic.  It also allows you to the length of the time so migration will stop if it exceeded the time slot.  In addition, you can define a repeating cycle, so automatic migration will take off periodically.  When migration is started at the specified date/time, it will scan for files that meet all other criteria as described by the previous properties, and only those files will be migrated.

9.	Define a repeat cycle

Toggle the values in the months, days, hours, and minutes spin boxes to set the interval for the repeating job.

Select the days on which you want to run the job by clicking on the day in the Include Days group.

Once your Primary volume has been enabled for data migration, you will see a small green square that indicates to users that data migration has been enabled on that volume.  Furthermore, you will be able to view the DM extended storage icons representing the different DM storages, which were added to the migration route of the volume.


Usage properties of the DM Storage

You can view statistical information about the amount of migrated and deleted data on your DM Storages.  This information can be displayed in a chart or a table.

Use the following procedure to set the options for displaying usage statistics:

Click on the Usage tab of the Properties of (a DM Storage type) dialog box.

Click on the Topics button, then select the Stored vs. Deleted view or Stored vs. Deleted (Accumulative) view.

To set the options for displaying the statistics, click on the Options button.


Configuring the Display of DM Storage Usage

The options displayed in DMO are:

1.  Select the time interval displayed for the statistics:

last 30 days

last 12 months

2.  Select format of displayed data:

chart

table

3.  Select the unit you wish to view:

megabytes (disk space)

number of files


Related Topics

  Usage properties of the DM Storage


Scheduling Ad Hoc operations

When you finish selecting the source and target, you will be prompted to specify the schedule for executing the job.  If the job was initiated using the "right click" method, you can run the job by selecting "Now" or "Later".

If you select "Later", you can specify the date, start time, and duration of the job.  However, you cannot define a repeat cycle for the job, which will only run once.  If you initiate the job using the drag-and-drop method, the job will always be run "Now".


File Age Filters - Procedures

1.	In the DM Admin's browser tree, right click on the volume node/directory, then select the Properties menu option.

The Properties of ...dialog box  for volumes appears.

2.	Click on the Data Migration tab of the Properties of ... dialog box, click on the Properties button, then select the File Age Filter menu option.

3.	Click on the Advanced button to specify advanced file age filter options.

The Advanced File Age Filter Options dialog box appears.


Directory/file pattern filters - Procedures

Use the following procedure to define Directory/File Pattern Filters for migration enabled volumes:

1.	In the DM Admin's browser tree, right click on the volume node/directory, then select Configure\Directory\File Pattern filter.

A dialog box appears based upon the type of Directory/File Pattern Filter you want to apply.  For example, if you selected Exclude, then the Files menu option, the Exclude files with pattern dialog box would appear.

2.	After you define directory/file name filters for a subdirectory, you can select whether or not to inherit the parent directory's filters.  If you select to inherit the filters, then all of the parent's filters and the filters which the parent directory inherited will apply to the current directory in combination with the directory's own filters.  The total combination of filters will flow down to all of the subdirectories, unless they have the "Inherit filters from parent" check box deselected.


File Size Filters - Procedures

Use the following procedure to reset File Size Filters for migration enabled volumes:

1.	In the DM Admin's browser tree, right click on the volume node/directory, then select the Configure\File Size Filters.

The File Size Filter options on the Data Migration tab of the Properties of ... dialog box appears.

2.	After you define file size filters for a subdirectory, you can select whether or not to inherit the parent directory's filters.  If you select to inherit the filters, then the file size filters will be combined in the most restrictive manner.  For example, if the parent has a file size filter for files between 4 KB and 4 MB and the current directory has a file size filter for files between 16 KB and 16 MB, the resulting filter will only include files between 16 KB and 4 MB.  This combination of filters will flow down to all of the subdirectories, unless they have the "Inherit filters from parent" check box deselected.


Defining File Attribute Filters - Procedures

Use the following procedure to reset File Attribute Filters for migration enabled volumes:

1.	In the DM Admin's browser tree, right click on the volume node/directory, then select Configure\File Attribute Filters.

The File Attribute Filter options on the Data Migration tab of the Properties of... dialog box appears.

2.	After you define file attribute filters for a subdirectory, you can select whether or not to inherit the parent directory's filters.  If you select to inherit the filters, then all of the parent's filters and the filters which the parent directory inherited will apply to the current directory in combination with the directory's own filters.  The total combination of filters will flow down to all of the subdirectories, unless they have the "Inherit filters from parent" check box deselected.


Migration Route - Procedures

To redefine the migration route, do the following:

1.	Click on the Data Migration tab of the Properties dialog box, then select Migration Route.

2.	To add DM storage devices to the migration route, click on a device's icon in the DM Storages dialog box and drag it to the Properties of…dialog box.  To remove the DM storage devices, click on a device's icon in the Properties of…dialog box and drag it to the DM Storages dialog box.

NOTE: The order of the new stages will be rearranged automatically.

If you selected an optical or tape storage in your migration route, you can select to migrate your data to exclusive media or shared media sets.  If media sets were created for that storage, right-clicking on the storage icon will display all existing media sets created for that storage.  If you select a media set, all data from this volume will be migrated to that media set, which may be shared by other volumes.  If you do not select a media set, all data will be stored on media that are dedicated to this volume alone.

To select a media set, right-click on a storage stage, select Define Media Set..., then select a media set from the drop-down list in the Use Media from Media Set... dialog box

You can select to switch migrating data to a media or exclusive media at any time.  However, the following rules will apply:

If you are switching from exclusive set to a shared media set, the data will continue to migrate to the current exclusive media until the media is full.  Then the data will migrate to the media set.

If you are switching from a shared media set to an exclusive media, an exclusive media will be immediately allocated to store data from the volume.

3.	You can perform a test of the migration route by clicking on the Test button.

When you initiate the test, the DM Agent will send a test data packet down through the migration hierarchy triggering a DM Storages to test its local hardware, then trigger the same test on the following stage.  The status of the DM Storages is then reported to the DM Agent.

NOTE: Test results might be subject to hardware limitations, thus results might not always indicate a device's availability.


User Properties of the DM Agent - Procedures

Restricting demigration for all users:

1.	Click on the Users tab of the Properties of the DM Agent dialog box.

2.	Select the Restrict all users check box by clicking on it, set the number of demigrations-per-hour in the demigrations per hour spin box, then click on the OK button or the Apply button to configure other properties in the dialog.

Restricting Demigration for individual users:

1.	Click on the Users tab of the Properties of the DM Agent dialog box.

2.	In the list window, double click on the <Add User> heading.

The Restrict demigrations triggered by... dialog box appears.

•	In the Restrict demigrations triggered by... dialog box type the domain name in the Domain edit box,

•	type the user's name in the User Name: edit box,

•	specify the maximum number of demigrations per hour by clicking on the up and down arrows in the Maximum Demigrations spin box,

•	click OK .

3.	In the Properties of the DM Agent dialog box, click on the OK button or the Apply button to configure other properties in the dialog.


Ad Hoc Demigration - Procedures

Using the right-click method for demigration:

Right-click on the folder in the tree of the DM Admin's browser containing migrated files, then select Demigrate from the menu:

Right-click migration adheres to the following rules:

If you right hand click on files or directories in the primary volume area of the browser, and select Demigrate, all files in the subdirectory are migrated regardless of the DM Storage in which they are located.

If you right hand click on the specific storage area, then only those files located in that storage will be demigrated.

Once you select Demigrate, click on the Next button to specify the demigration schedule.

Using the drag-and-drop method for demigration:

In the browser of the DM Admin:

expand the DM Extended Storage icon.

click on the icon for the DM Storage device containing the data you want to demigrate.

select the folder you want to demigrate under the DM Extended Storage folder back to the original folder on your primary volume.

Note:  When you perform drag-and-drop demigration, you can only drop the selected items on the primary volume icon because items always demigrate back to the original directory.

Drag-and-drop migration adheres to the following rules:

When you perform drag-and-drop demigration, you will drag the entire DM Extended Storage icon back to the primary volume's icon in the browser, all migrated files on that volume will be demigrated.

If you drag the specific DM Storage's icon back to the primary volume, then all files which were migrated to that stage will demigrate back to that volume.

If you select specific directories or files in an expanded DM Storage's folder, then only those files in the storage will demigrate back to the volume.

Click on the Next button to specify the demigration schedule.

Using the Media-based method for demigration:

Media-based demigration allows you to demigrate data based on the physical media.

For example, if you suspect that a physical media might have been partially damaged, you might want to demigrate the data and replace the media.

To perform media-based migration use the following procedure:

1.	Determine the name of the media and the host computer on which the media is located.

2.	Using the DM Admin, go to the host computer and locate the media inside the DM Storage under the DM Components icon.

Click on the Next button to specify the demigration schedule.


Ad Hoc Verification - Procedures

Verifying specific volumes or directories:

1.	Right-click on the directory or volume you want to verify, then select Verify.

The Verification wizard appears.

2.	View the selected files, then click on the Next button.

3.	Select your verification schedule, as previously described, then click on the Finish button.

The job is submitted to the ARCserve job engine and will be processed accordingly.

Using the Media-based method for verification:

1.	Determine the name of the media and the host computer on which the media is located.

2.	Using the DM Admin, go to the host computer and locate the media inside the DM Storage under the DM Components icon.

Right-click on the media and select Verify to check all files on the media.  Notice that the media name is composed of the media name and the drive letter for the volume on which the folder exists.

Click on the Next button to specify the verification schedule.

3.	Select your verification schedule, then click on the Finish button.


right-click method

You can select the source by highlighting the entry and right clicking.  If you want to select multiple files or directories, you must expand a node of the browser, then click on multiple targets in the list window, while holding the control key.


drag-and-drop method

You can initiate ad hoc operations by dragging selected files or directories to the target's icon in the browser.  This method does not apply to ad hoc verification.


Primary Volume Properties Screen - Procedures

To analyze the statistics of your primary volumes, do the following:

1.	Right-click on a primary volume in the DM Admin, then select Properties.

The Properties of… dialog box appears.

2.	Select the Statistics tab.

3.	Select the following statistical views:

Volume Usage

Migrations vs. Demigrations

Migrations vs. Demigrations (Accumulative)

Job Triggered vs. Users Triggered Demigrations

Note:  Click on the Options… button to view options.


Setting up NT volumes for data migration - Procedures

Use the following procedure to install NT volume software on an NT machine:

1.	In the browser of the DM Admin, do one of the following:

Right click on My Workstation to install the DM Storages (NT volume type) on your local machine, then select DM NT Volume Storage from the sub-menu.

Double click on Network Neighborhood to expand and view all of the available domains and machines in the browser and window area of the DM Admin and double click on the domain containing your target NT machine, double click on the domain containing the remote NT machine connected to the NT volume(s) you want to use for storing migrated data, then right click on the NT machine on which you want to install the DM Storages for managing NT volumes.

The installation program starts the wizard for installing an NT volume and the Welcome dialog box appears.

1.	If you want to install the NT volume storage software on the server or workstation shown, select the Next button.  If not, select the Cancel button.

2.	Type a 20-digit CD Key code into the edit boxes in the license Information dialog box, then click on the Next button.

The Default Destination dialog box appears.

3.	View the target directory for the DM Storage software in the Destination edit box, then click on the Next button.

The Preparation dialog box appears.

4.	If the NT volume you want to configure as a DM storage is empty and uses the NTFS file structure format, click on the Next button.

The Setup Complete dialog box appears.

5.	Click on the Finish button.

Note:  You can store up to two gigabytes of data per NT volume.


Setting Up Tape DM Storages for Data Migration - Procedures

Use the following procedure to set up a tape device for data migration:

1.	In the browser of the DM Admin, do one of the following:

To install the DM Storages for managing tape devices on your local machine, right click on My Workstation.

Double click on Network Neighborhood to expand and view all of the available NT domains in your network in the browser and window area of the DM Admin, double click on the domain containing the target NT machine on which you want to install the DM Optical Storage service, then right click on the machine on which you want to install DM Storages for managing migrated data on tape devices.

The Welcome dialog box appears.

Note:  If you want to install a component of the DM Option remotely, you must have full administrator rights for that machine.

2.	If you want to install the Computer Associates Tape Storage Software on the selected machine, click on the Next button.

3.	The Default Destination Directory dialog box appears.

4.	Click on the Next button to install the DM Storages program files to the default directory shown in the list box.

The Preparation dialog box appears informing you that ARCserve must be installed on the target NT machine to start the Migrated Data Storage Service.

5.	Click on the Next button.

The Setup Complete dialog box appears.

6.	Click on the Finish button.


Setting up optical storage devices for data migration - Procedures

Use the following procedure to install optical DM storages on NT machines:

1.	In the browser of the DM Admin, do one of the following:

right click on My Workstation to install the DM Storages for optical media on your local machine

Double click on Network Neighborhood to expand and view all of the available domains in the browser and window area of the DM Admin, double click on the domain containing the remote NT machine connected to the optical storage device(s), then right click on the machine on which you want to install DM Storages for managing migrated data on optical media.

Note:  If you want to install a component of the DM Option remotely, you must have full administrator rights for that machine.

2.	Click on the Install menu option, then select DM Optical Storage from the sub-menu.

3.	The installation program starts the wizard for installing an optical device and the Welcome dialog box appears.

4.	Click on the Next button.

5.	The Default Destination Directory dialog box appears.

6.	Click on the Next button to confirm that the optical storage software should be installed into the directory displayed in the edit box.

7.	The Preparation dialog box appears.

8.	If ARCserve is installed in the directory specified in the Default Destination Directory dialog box, click on the Next button.

9.	The Setup Complete dialog box appears.

10.	Click on the Finish button to complete installing the program files for setting up a DM Optical storage device.


Installing the DM Agent - Procedures

Use the following procedure to install the DM Agent:

1.	Take one of the following steps to install the DM Agent on a local or remote NT machine:

To install the DM Agent services on a local machine from which you want to migrate data, right click on My Workstation.

Double click on Network Neighborhood to expand and view all of the available NT domains in your network in the browser and window area of the DM Admin, double click on the domain containing a remote NT machine from which you want to migrate data, then right click on the particular machine from which you want to migrate data.

2.	Click on the Install menu option, then select DM Agent from the sub-menu.

The Welcome dialog box appears prompting you to install the DM Agent's program files, which allow you to transfer files between primary volumes on your server or workstation, secondary storage devices, or tertiary storage devices..

3.	Click on the Next> button.

The License Information dialog box appears.

4.	In the License Information dialog box, type a 20-digit CD key into the edit boxes, then click on the Next button.

The Define Service Account dialog box appears.

5.	In the Define Service Account dialog box, you must log on to the NT server or workstation on which you want to install the DM Agent service by typing the account name in the Account list box, the password for the account in the Password list box, and the password again (for password verification) in the Confirm Password dialog box, then click on the Next button.


Creating Media Sets - Procedures

Use the following procedure to create media sets:

1.	In the DM Agent's browser tree, double-click on the DM Components icon, the DM Storages icon, then Tape icon.

2.	Right click on the Media Sets icon, then select the Create Set menu option.
The Create Media set... dialog box appears.

3.	Type the name for the media set in the edit box, then select the OK button.


ARCserve Online Help

This help system is sectioned into two parts:

ARCserve Online Help: Offers information to assist you in gaining a better understanding of the product.

ARCserve Online Procedures: Provides step-by-step instructions for using the product.