Beruflich Dokumente
Kultur Dokumente
Administration Guide
r16.5 SP1
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to
as the Documentation) is for your informational purposes only and is subject to change or withdrawal by Arcserve at any
time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without
the prior written consent of Arcserve. This Documentation is confidential and proprietary information of Arcserve and may not
be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and
Arcserve governing your use of the Arcserve software to which the Documentation relates; or (ii) a separate confidentiality
agreement between you and Arcserve.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may
print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your
employees in connection with that software, provided that all Arcserve copyright notices and legends are affixed to each
reproduced copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to Arcserve that all copies and partial copies of the Documentation have been returned to Arcserve or
destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, ARCSERVE PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY
OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL ARCSERVE BE LIABLE TO YOU OR ANY THIRD PARTY FOR
ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION,
LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF ARCSERVE IS EXPRESSLY
ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is Arcserve.
Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright 2014 Arcserve (USA), LLC and its affiliates and subsidiaries. All rights reserved. All trademarks, trade names,
service marks, and logos referenced herein belong to their respective owners.
Arcserve Backup
Contact Arcserve
The Arcserve Support team offers a rich set of resources for resolving your technical
issues and provides easy access to important product information.
https://www.arcserve.com/support
With Arcserve Support:
You can get in direct touch with the same library of information that is shared
internally by our Arcserve Support experts. This site provides you with access to our
knowledge-base (KB) documents. From here you easily search for and find the
product-related KB articles which contain field-tested solutions for many top issues
and common problems.
You can use our Live Chat link to instantly launch a real-time conversation between
you and the Arcserve Support team. With Live Chat, you can get immediate answers
to your concerns and questions, while still maintaining access to the product.
You can participate in the Arcserve Global User Community to ask and answer
questions, share tips and tricks, discuss best practices and participate in
conversations with your peers.
You can open a support ticket. By opening a support ticket online, you can expect a
callback from one of our experts in the product area you are inquiring about.
You can access other helpful resources appropriate for your Arcserve product.
Providing Feedback About Product Documentation
If you have comments or questions about Arcserve product documentation, please
contact us.
Documentation Changes
The following documentation updates have been made since the last release of this
documentation:
Added NetApp NAS Cluster Protection (see page 944). This section includes
information and limitations for supporting the Arcserve Backup NDMP NAS Option
and the NetApp Cluster running the Data ONTAP 8.2 version.
Updated Backing Up and Recovering Arcserve D2D Data (see page 769). This topic is
now updated with the migration of Arcserve D2D and arcserve Unified Data
Protection (UDP), where Arcserve D2D is now D2D/UDP.
Added Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP
Recovery Point Server (see page 791). This new topic describes how to back up and
recover Arcserve UDP nodes from Arcserve UDP Recovery Point Server.
The following topics have been updated to accommodate the new feature, Double
Tape Copy that is introduced in this release. Double Tape Copy lets you migrate
data from a disk staging device to two destinations simultaneously.
How to Use Disk Staging to Manage Backup Data (see page 202)
Tasks You Can Perform Using Disk Staging (see page 206)
Removed the alert option "Virus Detected" from the following topics:
Specify Alert Options for Disk and Tape Staging Backups (see page 217)
Updated Agent for Virtual Machines Options (see page 180). This topic now
includes the Transport Mode options.
Updated How to Find Files That You Want to Restore (see page 258). This topic now
includes another way of recovering a virtual machine by specifying a transport
mode.
16.5 changes:
Updated Specify Local Backup Options (see page 134). This topic now includes
information about how to enable the Windows Server 2012 NTFS Data
Deduplication function on local backups.
Updated Point in Time Restore Options (see page 159). This topic now contains
cross-references to how to enable this option.
Added NTFS Data Deduplication (see page 159). This new topic describes how you
can perform optimized backups for full backups on data-deduplication enabled
volumes. This new option is located on the Global Backup Options dialog under the
Advanced tab.
Added How NTFS Data Deduplication Works (see page 255). This new topic
describes how Arcserve Backup implements the Windows Server 2012 NTFS Data
Deduplication function.
Updated How Backup to Disk to Tape Works and How Backup to Tape to Tape
Works (see page 230). These topics now contain More Information links to topics
that describe how to leverage Disk Staging and Tape Staging to protect your backup
environment.
Updated Best Practices - How to Recover a Arcserve Backup Server from a Disaster
without Using the Disaster Recovery Option (see page 287). This topic includes a
note about having enough space in the System Reserved Volume and the
recommended volume size to have.
Added Implement Logical Block Protection (see page 438). This new topic describes
how to implement Logical Block Protection on stand-alone tape drives.
Updated Configure Cloud Connections (see page 478). This topic describes that you
cannot create a unique bucket name that ends with a period. This topic also
describes the new Proxy Settings button and the Do not use proxy option.
Added Arcserve Backup Cannot Perform a Hyper-V Backup Job That Contains Data
on SMB Shares (see page 884). This troubleshooting topic helps resolve failed
Hyper-V backup jobs that contain disks, configuration files, or both on SMB shares.
Added Arcserve Backup Cannot Perform a Hyper-V Writer or SQL VSS Writer Back
Up Job That Contains Data on SMB Shares (see page 884). This troubleshooting
topic helps resolve failed Hyper-V VSS writer and SQL Server VSS writer backup jobs
that contain data on SMB shares.
Added Unable to View All Job Logs for Rotation Backups After the Database is
Pruned (see page 906). This new troubleshooting topic describes how to configure
the database pruning jobs to retain all of the job logs associated with repeating and
rotation jobs.
Contents
Chapter 1: Introducing Arcserve Backup
23
Introduction ............................................................................................................................................................... 23
Arcserve Backup Functionality ................................................................................................................................... 23
How to Access Arcserve Backup Managers, Wizards, and Utilities..................................................................... 25
Arcserve Backup Utilities .................................................................................................................................... 30
Arcserve Backup Command Line Utilities ........................................................................................................... 35
Arcserve Backup Security .................................................................................................................................... 36
Enterprise Level Password Management Utility ................................................................................................. 38
Arcserve Backup Enterprise Module ................................................................................................................... 39
How to Protect Virtual Machine Environments .................................................................................................. 39
How Backup and Restore Operations Function on 64-bit Windows Platforms .................................................. 40
Using Arcserve Backup Documentation ..................................................................................................................... 41
Download the Bookshelf ..................................................................................................................................... 41
Configure the Documentation Location .............................................................................................................. 42
43
Contents 7
133
8 Administration Guide
Contents 9
257
301
10 Administration Guide
351
Contents 11
373
12 Administration Guide
491
Contents 13
14 Administration Guide
Microsoft Exchange Server 2010 Mailboxes Appear as Legacy Mailboxes After Recovering the Active
Directory ........................................................................................................................................................... 589
Reset Microsoft Exchange Server User Passwords After Recovering the Active Directory .............................. 589
Install and Uninstall Arcserve Backup Server Based Options ................................................................................... 590
Discovery Configuration ........................................................................................................................................... 591
How the Discovery Service Detects Other Computers ...................................................................................... 592
IP Subnets/Windows Domains Discovery ......................................................................................................... 593
Enable Discovery Using TCP/IP Subnet Sweep .................................................................................................. 594
Discovery Configuration for the SAN Option .................................................................................................... 597
Discover Client Agent Systems with Non-default IP Addresses ........................................................................ 597
Arcserve Backup Maintenance Notifications ........................................................................................................... 598
Disable Maintenance Notification Messages .................................................................................................... 599
Enable Maintenance Notification Messages ..................................................................................................... 600
Apply Arcserve Backup Component Licenses ........................................................................................................... 600
Managing Firewalls .................................................................................................................................................. 601
Allow Arcserve Backup Services and Applications to Communicate Through the Windows Firewall .............. 601
How to Configure Your Firewall to Optimize Communication .......................................................................... 602
603
Contents 15
How to Recover the Arcserve Database When the SQL Server Instance Hosting the Arcserve Database
is Not Functional ............................................................................................................................................... 649
How Arcserve Database Recovery Wizard Works ............................................................................................. 649
How the Catalog Database Works ............................................................................................................................ 650
Catalog Browsing............................................................................................................................................... 652
Catalog Database Pruning ................................................................................................................................. 652
How a Centralized Catalog Database Works ..................................................................................................... 653
Configure the Catalog Database ....................................................................................................................... 653
Move the Arcserve Backup Catalog Database to a Different Location ............................................................. 654
Using Microsoft SQL Server as the Arcserve Backup Database ................................................................................ 658
Microsoft SQL Server Database Considerations................................................................................................ 658
Remote Database Considerations ..................................................................................................................... 659
Specify ODBC Communication for Remote Database Configurations............................................................... 660
How to Calculate the Number of Required SQL Connections ........................................................................... 661
How to Enable TCP/IP Communication on Microsoft SQL Server Databases ................................................... 661
Database Consistency Checks ........................................................................................................................... 661
Specify a Arcserve Backup Database Application ..................................................................................................... 662
Configure Microsoft SQL Server as the Arcserve Backup Database .................................................................. 662
Move the Arcserve Backup Database to a Different System or Instance ......................................................... 664
Configure Microsoft SQL Server 2008 Express as the Arcserve Backup Database ............................................ 667
Arcserve Backup Logs and Reports .......................................................................................................................... 667
Activity Log Data ............................................................................................................................................... 668
Tape Log ............................................................................................................................................................ 668
Job Log .............................................................................................................................................................. 668
Report Manager ................................................................................................................................................ 669
Report Manager Reports................................................................................................................................... 671
Custom Report Job Scheduling ......................................................................................................................... 679
Create Custom Reports Using the Report Writer Utility ................................................................................... 680
Report Generation for Multiple Arcserve Backup Servers ................................................................................ 681
Arcserve Backup Diagnostic Utility ........................................................................................................................... 682
Diagnostic Utility Components.......................................................................................................................... 682
Configure Computers Running Windows Vista and Windows 7 Operating Systems to Communicate
with the Diagnostic Wizard ............................................................................................................................... 683
Create Reports Using the Express Mode Diagnostic Utility .............................................................................. 684
Create Reports Using the Advanced Mode Diagnostic Utility ........................................................................... 685
View Reports Using the Diagnostic Report Manager ........................................................................................ 686
Arcserve Backup Infrastructure Visualization .......................................................................................................... 687
Infrastructure Visualization Software Requirements ........................................................................................ 688
Infrastructure Visualization Operations ............................................................................................................ 688
Infrastructure Visualization Color Scheme ........................................................................................................ 689
Arcserve Backup Infrastructure Visualization Views ......................................................................................... 689
Dashboard Integration with Infrastructure Visualization ................................................................................. 703
16 Administration Guide
705
719
How the Arcserve Backup Central Agent Admin Works ........................................................................................... 719
Manage Agents ........................................................................................................................................................ 720
Modify Agents ................................................................................................................................................... 720
Configure Agent Security .................................................................................................................................. 720
Start or Stop Agent Services .............................................................................................................................. 721
Start Agent Deployment from the Central Agent Admin .................................................................................. 721
Configure Agents ...................................................................................................................................................... 721
Add Computers ........................................................................................................................................................ 723
Add Nodes ................................................................................................................................................................ 723
Manage Agent Logs .................................................................................................................................................. 725
Configure SRM PKI.................................................................................................................................................... 726
Configure SRM Exclude Paths .................................................................................................................................. 728
Configure Node Tiers................................................................................................................................................ 728
731
Contents 17
Chapter 13: Raw Backup and Restore of Physical Disks and Volumes
761
769
18 Administration Guide
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the
Arcserve UDP Recovery Point Server
791
Submit Backup Jobs of Arcserve UDP Nodes through the Arcserve UDP Recovery Point Server ............................ 791
Submit Static Backup Jobs Containing Arcserve UDP Data ...................................................................................... 793
Submit Dynamic Backup Jobs Containing Arcserve UDP Data ................................................................................. 795
Recover Arcserve UDP Data at File Level Granularity .............................................................................................. 797
Recover Arcserve UDP Data at Application Level Granularity .................................................................................. 799
Recover Arcserve UDP Data from Raw Sessions ...................................................................................................... 804
Configure Arcserve Backup to Generate Arcserve UDP Catalog Files ...................................................................... 807
809
843
How to License the Storage Area Network (SAN) Option ........................................................................................ 843
The SAN Environment .............................................................................................................................................. 844
How Arcserve Backup Works in a SAN .............................................................................................................. 844
Server Management in a SAN ........................................................................................................................... 846
Backup Plans ..................................................................................................................................................... 846
Benefits of Using the Option ............................................................................................................................. 846
Terminology ...................................................................................................................................................... 846
Install the SAN Option .............................................................................................................................................. 847
Operating System Compatibility ....................................................................................................................... 847
Contents 19
Appendix A: Troubleshooting
857
20 Administration Guide
Arcserve Backup Cannot Perform a Hyper-V Backup Job That Contains Data on SMB Shares ......................... 884
Arcserve Backup Cannot Perform a Hyper-V Writer or SQL VSS Writer Back Up Job That Contains Data
on SMB Shares .................................................................................................................................................. 884
Memory Usage Increases When Restoring Data From a Remote FSD Located on a Windows 2008 SP2
and Windows 2008 R2 Server ........................................................................................................................... 885
Restore Job Fails on MAC Agents ...................................................................................................................... 885
Media Problems ....................................................................................................................................................... 885
Tape Errors Occur When Backing Up or Restoring Data ................................................................................... 885
Arcserve Backup Cannot Detect RSM Controlled Devices on x64 Platforms .................................................... 887
Arcserve Backup Does Not Detect a Cleaning Tape .......................................................................................... 888
Hardware Does Not Function as Expected ........................................................................................................ 889
Autoloaders and Changers Appear Offline ....................................................................................................... 890
Catalog Database Log Files Consume a Large Amount of Disk Space ............................................................... 890
Unrecognized Vaults Appear in the Media Management Administrator ......................................................... 892
SAN Configuration Problems .................................................................................................................................... 892
Devices are Not Shared ..................................................................................................................................... 893
Devices are Not Shared and the Tape Engine is Running .................................................................................. 893
Shared Devices Appear as Unavailable or Offline ............................................................................................. 894
Shared IBM Devices Appear as Unavailable or Offline...................................................................................... 895
Backup Jobs Fail ................................................................................................................................................ 896
Cluster-based Backup and Restore Problems .......................................................................................................... 897
Prevent Job Failures .......................................................................................................................................... 897
Back Up MSCS Nodes on Remote Machines ..................................................................................................... 898
Back Up Arcserve Backup Database in a Cluster Environment ......................................................................... 899
Job Failure: Media Not Mounted ...................................................................................................................... 899
Miscellaneous Problems .......................................................................................................................................... 900
Discovery Service Does Not Function Properly ................................................................................................. 900
Arcserve Backup Servers and Agent Servers Cannot Communicate with Each Other ...................................... 900
SRM PKI Alert is Enabled by Default ................................................................................................................. 902
Job Queue Log Files Consume a Large Amount of Disk Space .......................................................................... 904
Unable to View all Job Logs for Rotation Backups after the Database is Pruned ............................................. 906
907
Contents 21
949
957
Overview of Protecting Hyper-V VMs Using the Hyper-V VSS Writer ...................................................................... 957
Prerequisite Components for Hyper-V VSS Writer Protection ................................................................................. 957
Configure Arcserve Backup to Detect Hyper-V VMs ................................................................................................ 959
How Back Up Using Saved State Works ................................................................................................................... 960
How Back Up Using Child Partition Snapshot Works ............................................................................................... 960
Back Up Hyper-V VMs Using the Hyper-V VSS Writer .............................................................................................. 960
Restore Data to Its Original Location ....................................................................................................................... 961
Glossary
963
Index
967
22 Administration Guide
Introduction
Arcserve Backup is a comprehensive, distributed storage management solution for
distributed and multiplatform environments. The application can back up and restore
data from all the machines on your network, (including machines running Windows,
UNIX, and Linux) using optional client agents. Arcserve Backup also provides media and
device management utilities.
Arcserve Backup offers control from one management console. It can support
small-scale and large-scale enterprise environments comprising of one machine or
many, across different platforms and organizations.
Home Page--Provides news and support that links you to tools you can use to help
solve problems with your computer. It also provides links to Quick Start,
Configuration, Wizards, and Utilities.
24 Administration Guide
Wizards--Simplifies the most common tasks of Arcserve Backup. You can access the
Device, Create Boot Kit, Job Scheduler, and Diagnostic Wizards.
Utilities--Offers several utilities that you can use to manage your database and
media. The utilities are Merge, Scan, Compare, Count, Copy, Purge, User Profile,
and Report Writer.
The following is a list of the components, the menu from which you can access the
component, and the functions they perform:
Quick Start Menu
Job Status Manager--Monitors all pending, completed, and active jobs from the Job
Status Manager window. You can schedule pending or completed jobs, submit new
jobs, delete jobs, and stop active jobs. Log information is provided for each
completed job.
Backup Manager--Backs up data to media. You can schedule and configure backups
of your computers and servers. Information about each backup job (such as the
path and name of each file, and the media used) is logged in the Arcserve Backup
database. Using the Backup Manager you can:
Specify the source (data that you want to back up) and the destination (media)
for your backup job.
Define your backup job to back up data on computers running other operating
systems such as UNIX, Linux, and Windows.
Find all the versions of the files that were backed up.
Server Admin--Allows you to modify the Arcserve Backup system account and
manage the core Arcserve Backup services: Job Engine, Tape Engine, and Database
Engine. The Configuration icon allows you to configure tasks for these services
including generating an alert and defining message logging. The Database Engine
tab allows you to configure the database pruning job.
Job Status Manager--Monitors all pending, completed, and active jobs from the Job
Status Manager window. You can schedule pending or completed jobs, submit new
jobs, delete jobs, and stop active jobs. Log information is provided for each
completed job.
26 Administration Guide
Backup Manager--Backs up data to media. You can schedule and configure backups
of your computers and servers. Information about each backup job (such as the
path and name of each file, and the media used) is logged in the Arcserve Backup
database.
Archive Manager--Lets you specify archive schedules and policies for the selected
Windows, UNIX, Linux, and MAC file system data.
Administration Menu
Server Admin--Allows you to modify the Arcserve Backup system account and
manage the core Arcserve Backup services: Job Engine, Tape Engine, and Database
Engine. The Configuration icon allows you to configure tasks for these services
including generating an alert and defining message logging. The Database Engine
tab allows you to configure the database pruning job.
Device Configuration--A tool that lets you configure backup devices, such as tape
libraries, RAID devices, virtual libraries, disk-based devices (for example, file system
devices), and Deduplication devices (DDD). It also lets you enable or disable devices
for Removable Storage Management (RSM), and register and unregister UNIX and
Linux data mover servers with the primary server.
Maximum number of FSDs and DDDs supported: 255 (only if the number of
physical devices configured is 0).
Device Group Configuration--A tool that lets you easily configure the device groups
in your Arcserve Backup environment and select the groups that you will use for the
staging of data.
User Profile Manager--Lets you assign roles privileges to Arcserve Backup user
accounts.
Central Agent Admin--Lets you view agent logs and event logs, configure agent
options and security information, specify debug levels for agent registry values,
configure node tiers, and run Agent Deployment.
Utilities Menu
Job Scheduler Wizard--Provides an easy way to package and submit jobs that you
would typically submit from the Command Prompt window. In addition to the
commands associated with Arcserve Backup, you can use this wizard for virtually
any executable.
28 Administration Guide
Merge Utility--Lets you take media that contains one or more backup sessions and
merge the information from the media into your Arcserve Backup database.
Media Assure & Scan Utility--Lets you collect information about your media backup
sessions and helps ensure that the sessions on the media are restorable.
Count Utility--Lets you count the number of files and directories on a computer.
Technical Support
Arcserve Backup on the Web--Links you directly to the website where you find
product information.
Understanding Your Support--Links you to Arcserve Support where you can learn
more about available support programs.
Registering for Support--Links you directly to the registration form for Arcserve
support.
Feedback--Links you to Get Satisfaction, where you can submit ideas and comments
about the product, ask questions, exchange tips with other users, report problems,
and provide praise.
Note: The Feedback button on the Navigation Bar also links to the Arcserve
Feedback dialog for Get Satisfaction.
Quick Reference
RSS
At the bottom of the screen, the RSS bar scrolls through the latest Arcserve Backup
news. Click a headline to link directly to Arcserve.com where you can view the complete
story.
You must have Internet access to view RSS news. If you did not use the Arcserve Backup
domain account to log on, you can provide credentials manually. Click the Refresh
button at the right corner of the RSS bar to access the credentials dialog and refresh the
news feed.
Note: After you install Arcserve Backup, the RSS bar communicates (by default) with
Arcserve.com. If you do not want the RSS bar to communicate with Arcserve.com, you
can stop the communication by closing the RSS bar. To close the RSS bar, click the View
menu from any Arcserve Backup manager, and then click News Bar.
Merge Utility
If you need to restore files to a Arcserve Backup server that you did not use to create
the backup, or if you removed information from your Arcserve Backup database that
you now need, you can use the Merge utility.
The Merge utility lets you take media that contains one or more backup sessions and
merge the information from the media into your Arcserve Backup database. The
database information from the media is appended to your existing database files.
Each time you run a backup job, Arcserve Backup records information in its databases
about the computers, directories, and files that have been backed up, and the media
that were used. This allows Arcserve Backup to locate files whenever you need to
restore them. This database information is backed up whenever you back up your
Arcserve Backup home directory.
30 Administration Guide
If you have media that has a backup session that is not included in the Arcserve Backup
database (for example, the backup was created using Arcserve Backup on a different
backup server), you can use the Merge Media option to get the media's information into
the database in the Arcserve Backup home directory.
Why would you need to use the Merge utility?
You can use the Merge utility when you need to restore files to a Arcserve Backup
server that you did not use to create the backup. You can also use the Merge utility if
you pruned (deleted) information from your Arcserve Backup database that you now
need.
All sessions
A single session
Merge Options:
If you select to merge all sessions, the tape containing Sequence number 1 must be
present for this operation to complete successfully.
If the tape containing Sequence number 1 is not present, you will be prompted that the
media could not be found and request that you continue (after inserting the proper
tape) or cancel the operation.
If you want to merge a session from a different tape other than the one containing
Sequence number 1, you can only do so by not selecting to merge all sessions, and
instead specify the session number or range of session numbers to be included.
If you want to merge a session that spans more than one tape, you must have the tape
on which the session header information is located.
For example, if a backup was created using Arcserve Backup on a different server, you
can use Merge to get the media information into the database in the Arcserve Backup
home directory. This will allow you to restore media backed up from another server at
the file level. This can be useful if detailed information has been pruned from the
database. By default, detailed job information is pruned 30 days after the backup to
conserve database space. This can be configured in the Server Admin Manager.
Note: By default, all newly merged session details are preserved for one week (7 days)
in the Arcserve Backup database, even if the newly merged session details are older
than the prune retention time.
The available global merge options are listed below:
Backup Media--Specify media options for the job such as the media timeout period.
Pre/Post--Run commands or batch files before the job runs and/or after it finishes.
Job Log--Enables you to determine the level of detail you want recorded into the
Job Queue Log.
Database--Specify whether you want to record detailed information about the jobs,
or job and session-level details only.
Merge Detail Information--Lets you merge all details, including job and session
information.
Merge Session Headers Only--Lets you merge only header information, such as job
and session data.
32 Administration Guide
The results of the Scan job display in the Job Queue. You would need to do this if you
are trying to recover a Arcserve Backup server and you need to identify the most recent
backup of the Arcserve Backup database so that you can restore it.
If you would like a Scan job to produce a detailed listing of your media contents, use the
Log All activity feature on the scan options tab. You can also use the Media Assure &
Scan utility if you want a list of the files that were backed up.
Arcserve Backup provides several types of advanced scan options:
Operation--Specifies general options for the job such as to scan files with CRC
verification or to enable database recording.
Job Log--Determines the level of detail you want recorded in the Job Queue Log.
Compare Utility
Compare the contents of a media session to files on a machine. Results of the Compare
job can be seen in the Job Queue. You could use this option after a backup to verify that
the backup copied all of the files to media without error.
Arcserve Backup provides several types of advanced compare options:
Job Log--Determine the level of detail you want recorded in the Job Queue Log.
Count Utility
The Count utility counts the number of files and directories on a machine. Results of the
Count job can be seen in the Job Queue. You could use this option after a Copy job to
verify that the Copy function copied all of the files from one disk to another without
error.
Arcserve Backup provides several types of advanced count options:
Job Log--Determine the level of detail you want recorded in the Job Queue Log.
Copy Utility
The Copy utility allows you to copy files from one location 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.
Copy options determine related actions that occur during or after the copy operation:
Job Log--Determine the detail you want recorded in the Job Queue Log.
Purge Utility
The Purge utility allows you to delete files and directories from a machine. Results can
be seen in the Job Queue.
Arcserve Backup provides several types of advanced purge options:
Operation--Specify some general options for the job such as to remove directories
or enable database recording.
Job Log--Determine the level of detail to record in the Job Queue Log.
34 Administration Guide
Submit and delete jobs in local or remote Arcserve Backup job queues from the
command line.
Use job scripts created in the Arcserve Backup Manager or in a text file created
using the cabatch Job Information Template in the Arcserve Backup home directory.
For more information on the cabatch utility, see the Command Line Reference Guide.
Add a user.
Delete a user.
36 Administration Guide
Ease of command line usage--As you create equivalence for a Windows user, the
equivalence performs an implicit login on behalf of the logged-in user whenever a
command line function requires authentication. This behavior lets the command
line utilities run without requiring the user to enter a user name and password each
time a command is submitted.
System Account
The Arcserve Backup services require a valid Windows system account that has
Administrator and Backup Operator privileges on the local machine. The services use
this account to access local resources, such as the hard drive and the local network.
You are given the option of entering a Windows system account when you first install
Arcserve Backup. If you enter a Windows account during installation, Arcserve Backup
automatically grants this account Administrator and Backup Operator privileges. If you
select Skip during installation, you must enter a valid Windows system account using the
Arcserve Backup Administrator and grant it the required privileges manually.
Note: A user in the Backup Operator Group does not have rights to access the Arcserve
Backup database. As a result, member servers are not visible to the user in the Backup
Manager.
You can change the system account information at any time using the Arcserve Backup
Server Admin or the Server Configuration Wizard.
Although the System Account and the caroot user profile perform different functions, in
order for Arcserve Backup to run all of its jobs successfully, you must grant the System
Account equivalency to caroot. For example, if the System Account is named
BackupAdmin, and the local machine name is BAB01, use the following ca_auth
command to give the account equivalency to caroot:
Note: The caroot password can consist of any combination of alphanumeric and special
characters, but may not exceed 15 bytes. A password totaling 15 bytes equates to
approximately 7 to 15 characters.
For more information on security, see "Administering the Backup Server" or the
Command Line Reference Guide.
Syntax
ca_jobsecmgr [server arguments] <current security> <new security>
Options
For a complete description of the options for this command, see the Command Line
Reference Guide.
38 Administration Guide
Disk staging backups and tape staging backups with multistreaming and transmit
two or more (up to 32) streams of backup data.
Note: If you do not license the Enterprise Module, Arcserve Backup lets you
transmit two streams of backup data for disk staging and tape staging backup jobs.
For more information, see How Backup to Disk to Tape Works, and How Backup to
Tape to Tape Works (see page 230).
Arcserve Backup for Windows Enterprise Option for VSS Hardware Snap-Shot
Note: For more information, see the Microsoft Volume Shadow Copy Service Guide.
In addition, the Arcserve Backup Enterprise Module is a prerequisite component for the
following Arcserve Backup options:
Image Option
Note: For more information about the above options, see the Enterprise Module Guide.
Arcserve Backup Agent for Virtual Machines--The Agent for Virtual Machines lets
you protect environments that rely on virtual machines (VMs) residing in Windows
Server Hyper-V systems, VMware ESX/ESXi Host systems, and VMware vCenter
Server systems to protect data.
For VMware-based systems, VMware provides a mechanism called Virtual Disk
Development Kit (VDDK) that lets you protect the files and data stored in the VMs in
VMware ESX Host systems and VMware vCenter Server systems. To integrate
Arcserve Backup with VMware VDDK and Windows Server Hyper-V systems, you
install and license the Agent for Virtual Machines.
Note: For information about system requirements and supported platforms, see
the readme file. For information about installing and configuring the agent, see the
Agent for Virtual Machines Guide.
Install Arcserve Backup Agents on the VM--To back up and restore data that
resides in your VMs, you can install the Arcserve Backup agents that correspond
with the guest operating systems and the applications that are running in your VMs.
40 Administration Guide
Open the Arcserve Support online bookshelf by clicking Start, Programs, CA,
ARCserve Backup, Documentation.
The Arcserve Support documentation bookshelf opens.
2.
Click the Download this Bookshelf link to download the bookshelf to your Arcserve
Backup server.
Note: You can also click the Download Help link on the Documentation
Configuration dialog.
The File Download dialog appears for the file.
Example: Arcserve Backup Backup r16 5-ENU.zip (English version).
3.
Click Save.
The Save As dialog appears.
4.
Save in--enter the folder where you want to save the zip file.
The Download complete dialog appears and the zip file is saved.
5.
6.
Extract the contents of the zip file to the location specified above where the zip file
was saved.
Note: If the extraction utility contains an overwrite existing files option, you should
enable the option. However, if the extraction utility prompts you to overwrite the
files in the destination directory, click Yes to All.
The documentation bookshelf is downloaded, installed in the local directory, and
updated to the latest version.
7.
If you wish to view the documentation bookshelf locally, then you must configure
the documentation to use the local help as the source on the Documentation
Configuration dialog. For more information, see Configure the Documentation
Location (see page 42).
2.
Use local Help as source--select this option if you want to use a local version of
the downloaded documentation or if you do not have an internet connection.
Important: If you select this option, you must first download the bookshelf to
a local directory. Then you must enter a valid help location or click Browse to
locate a valid location in the Help Location field. This location must contain the
file Bookshelf.html.
3.
4.
Click OK.
The documentation is configured.
42 Administration Guide
44 Administration Guide
Central Management
Central Management
The Central Management Option allows you to manage one or more Arcserve servers
through a single central system. Within an Arcserve domain, this central system is called
the primary server and the other (subordinate) servers are called member servers.
Primary Server
A primary server provides you with a single point to manage the primary server and
one or multiple member servers in an Arcserve domain. From the primary server
you can centrally manage and monitor jobs that run locally on that primary server
and jobs that run remotely on one or more of the member servers in the domain.
There can be only one primary server within an Arcserve domain.
Note: You can designate any Arcserve Backup server as the primary server.
However, because the primary server is responsible for managing and initializing
the shared member servers, you should use your most reliable server as the
primary server.
Member Server
A member server executes jobs that are dispatched from the primary server. Within
an Arcserve domain, member servers can only belong to one primary server.
Central Management
Arcserve Domain
An Arcserve domain is a logical grouping of a primary and one or more member
servers that allows easier monitoring and managing of Arcserve Backup servers and
users. Within an Arcserve domain, there can only be one primary server and there
can be multiple member servers that are controlled by the primary server. An
Arcserve domain allows you to manage the domain and select any server from
within the domain to perform Arcserve Backup tasks without being required to log
in to each server separately.
The Arcserve database (ASDB) can be installed on a primary server or on any
remote system in your environment. Be aware that to install the ASDB on a remote
system, you must host the ASDB instance using Microsoft SQL Server.
The primary and member servers may or may not be connected through a Storage
Area Network (SAN). If the member servers are located on a SAN, the primary
server must also be on the SAN.
Note: A SAN environment within an Arcserve domain is an environment where
multiple Arcserve servers can share one or more devices (for example, tape
libraries).
46 Administration Guide
Central Management
Central Management
48 Administration Guide
Central Management
Central Management
Central Logging
With central logging, Activity Logs and Job Logs for all Arcserve Backup servers in a
domain (primary and members) are stored in a central database, allowing you to view
the logs from one central location.
Central logging also helps you to perform troubleshooting. You can use the various
filters (such as Keywords, Job ID, Job status, Message type, and so on) to isolate the log
information to display everything that happened for a specific condition. For example,
you can specify to only display the logs for failed jobs, or only display logs that contain a
certain keyword in a message or job name, or only display logs for certain job names.
Central logging allows you to perform these functions for all Arcserve Backup servers
within a domain from one central location.
Central Reporting
With central reporting, you can launch and create scheduled reports for all Arcserve
Backup servers in a domain from the primary server. Different reports are generated
based on the backup activity stored in the Arcserve Backup database. Central reporting
provides the capability to preview a report, print a report, send email, and schedule
when to generate a report for all domain servers from the primary server.
50 Administration Guide
Central Management
For example, from the primary server you can create a report that identifies the agents
that failed the most consecutive times, or the agents with the most failed backup
attempts, or the agents with the most partial backups. You can find the percentage of
successful, incomplete, or failed backup attempts. You can also find the number of
errors and warnings generated for the backup job for each agent which helps in
determining the agents with most number of errors.
Central Alerting
Arcserve Backup integrates with Alert Service to deliver alerts via emails, broadcasts,
event, pagers and printers. This is accomplished by the central alerting feature. Central
Alerting is a mechanism for gathering all alerts from all servers in the domain.
When a job executes, on any server in the domain, the event is recorded in the Arcserve
database. The job level alert is forwarded to the Alert Service on the Primary server. The
Alert Service then generates a system wide alert according to previously established
configurations. For more information on establishing service account configuration, see
Alert Manager Configuration (see page 709).
Central Management
52 Administration Guide
Central Management
SAN Auto-Configuration
SAN configuration is now tied to Arcserve Backup domain configuration, eliminating
the need to run SAN configuration. Libraries are automatically detected as shared
on the fly at the Arcserve Backup domain primary server. Domain primary servers
can have both SAN and non-SAN domain member servers.
FSD Auto-Configuration
From a central location on the primary server you can create an FSD on any
member server without having to stop and start the tape engine.
Central Management
With central license management, the license allocation is server based. This means that
when a license is allocated to a server, central license management will record this
allocation and keep this license exclusively used for that server. Future license requests
from the same server will always succeed, and requests from other servers will cause a
new license to be allocated to the new server. When all available licenses are allocated,
license checking places jobs that are running from an Arcserve Member server into a
Hold status, and fails jobs associated with a server that is running an Arcserve agent. For
all scenarios, when there are no licenses available, you will get an activity log message
warning you that the license is a problem.
Through the use of central licensing, you can easily remove license rights to allow other
member servers to gain license privileges. From the Server Admin Manager screen on
the primary server, you can access the License Management dialog to view the active
license counts for each component and also manage which licenses are applied to which
servers.
54 Administration Guide
Central Management
Arcserve Backup licenses are installed on and checked centrally on the Arcserve Backup
primary server. However, the following agents must be licensed on the servers where
you are installing the agents:
Arcserve Backup for Windows Enterprise Option for SAP R/3 for Oracle
More information:
Manage Arcserve Backup Component Licenses (see page 523)
Release Licenses from Servers (see page 525)
Central Management
You can also view information about the device and the media that were used for the
backup job. In addition, central job history is helpful in troubleshooting because any
errors or warnings that were generated during each job on any server (primary or
member) are also displayed from one central location.
Note: On the Job History tab, the MB/Minute field displays the ratio of megabytes per
minute for the entire job. In addition to transferring data from the source location to
the destination storage area, a job can include media management activities, pre- and
post- scripts, and so on. As a result, the value displayed in the MB/Minute field can be
different than the actual throughput. To view the actual throughput for the job, click the
Activity Log tab, locate the job, expand Logs for the Master Job, and locate the log entry
for Average Throughput.
56 Administration Guide
Central Management
Job View
The Job view displays all executions of a job. Each execution shows all of the hosts that
were backed up. You can also drill down on a host and see the sessions that were
backed up.
For each job entry, you also see the following summary information:
Central Management
Last Result
The last result is determined from the following criteria:
The status is marked as failed if any of the sessions in the job fail.
The status is marked as incomplete in any of the sessions are incomplete even
if some are successful.
MB
The amount of data backed up for the job.
Files
The number of files backed up for the job.
Missed
The number of files missed during the backup.
Note: Use Arcserve Backup Agent for Open Files to backup open files to avoid
missed files during a backup.
58 Administration Guide
Central Management
MB/Minute
At the Job level, MB/Minute indicates the ratio of megabytes and the elapsed
time for the entire job, including pre and post scripts, if any, media
management activities, and so on. For average master job throughput, refer to
the Activity Log.
At the Host level, MB/Minute indicates the ratio of megabytes and the elapsed
time for the entire job, including pre and post scripts, if any, media
management activities, and so on for a single host.
At the Session level, MB/Minute indicates the ratio of megabytes and the
elapsed time for a specific volume and its folders, which comprise a single
session.
Note: If little or no data is backed up by the backup job, a value of N/A appears in
the MB/Minute field.
Time Used
At the Job level, Time Used indicates the elapsed time for the entire job
including pre and post scripts, if any, media management activities, and so on.
At the Host level, Time Used indicates the elapsed time for the entire job
including pre and post scripts, if any, media management activities, and so on
for a single host.
At the Session level, Time Used indicates the elapsed time for the backup of a
specific volume and its folders, which comprise a single session.
Job ID
Identifies the specific execution of the job.
Job No.
Identifies the job.
Session Number
Identifies the session number of the session that contains the backup data.
Subsession Number
Identifies the subsession number of the session contains the backup data.
Compression Ratio
The amount of actual data to be stored divided by the amount of data stored after
deduplication expressed as a ratio or percentage.
Central Management
60 Administration Guide
Central Management
Summary
Execution Time
The start time and end time of the selected node.
Total Sessions
The number of sessions that were backed up for the host.
Total Migrations
The number of sessions migrated in a disk or tape staging job.
Central Management
62 Administration Guide
Central Management
Session Detail
Execution Time
Indicates the start time and end time of the selected session.
Number
Indicates the session number.
Type
Indicates the type of session backed up.
Path
Indicates the root path of the session.
Central Management
Status
Indicates the result of the backup session.
Start time
Indicates the start time of the session.
End time
Indicates the end time of the session.
Method
Indicates the type of backup method used for the session.
Flags
Indicates the internal flags created by Arcserve Backup to identify the session.
MB
Indicates the amount of data backed up for the session.
Files
Indicates the number of files backed up for the session.
Missed
Indicates the number of files not backed up during the session.
Device and Media
Device
Indicates the tape drive or file system device used during the backup of the
session.
Media Used
Indicates the media that was used during the backup of the session.
Error and Warning
Displays the errors and warnings that are generated during the back up of a session.
Host View
The Host view displays all of the hosts that were backed up and their status each time a
job has backed it up. You can also drill down on a host and see the sessions that were
backed up. For each host entry, you also see the following summary information:
Number of job execution
Indicates the number of times the host was attempted to be backed up or backed
up by a job.
Number of jobs finished
Number of times the host was backed up successfully.
64 Administration Guide
Central Management
Central Management
Last Result
The last result is determined from the following criteria:
The status is marked as failed if any of the sessions in the host fail.
The status is marked as incomplete in any of the sessions are incomplete even
if some are successful.
MB
The amount of data backed up for the host.
Files
The number of files backed up for the host.
Missed
The number of files missed during the backup job.
Note: Use Arcserve Backup Agent for Open Files to avoid missed files during a
backup job.
MB/Minute
At the Job level, MB/Minute indicates the ratio of megabytes and the elapsed
time for the entire job, including pre and post scripts, if any, media
management activities, and so on. For average master job throughput, refer to
the Activity Log.
At the Session level, MB/Minute indicates the ratio of megabytes and the
elapsed time for a specific volume and its folders, which comprise a single
session.
Time Used
66 Administration Guide
At the Job level, Time Used indicates the elapsed time for the entire job
including pre and post scripts, if any, media management activities, and so on.
At the Session level, Time Used indicates the elapsed time for the backup of a
specific volume and its folders, which comprise a single session.
Central Management
Job ID
Identifies the specific execution of the job.
Job No.
Identifies the job.
Session Number
Identifies the serial number of a session on a media. For example, session number
4, this is the fourth session on the media.
Identifies session number of the session that contains the backup data.
Subsession Number
Identifies the serial number of the logical session in a physical session when a
virtual machine (VM) is backed up by the Agent for Virtual Machines. If Arcserve
Backup backs up a VM using the Agent for Virtual Machines, Arcserve Backup backs
up all volumes and components into a single session. Each volume or component is
backed up in a logical session. This logical session contains the serial number, which
is the subsession number.
Compression Ratio
The amount of actual data to be stored divided by the amount of data stored after
deduplication expressed as a ratio or percentage.
In the bottom pane, the following information is displayed:
Summary
Total Sessions
The number of sessions that were backed up for the host.
Total Migrations
The number of sessions migrated in a disk or tape staging job.
Device and Media
Device
The tape drive or file system device used during the backup job. Multiple tape
drives can also be used for the same host in a single job execution if the job is a
multi streaming job.
Media Used
The media that was used during the backup of the host. Multiple media can
also be used for the same host in a single job execution if the job is a multi
streaming job.
Error and Warning
Displays the errors and warnings that are generated during the backup of a host.
Central Management
Session Detail
Execution Time
Indicates the start time and end time of the selected session.
Number
Indicates the session number.
Type
Indicates the type of session backed up.
Path
Indicates the root path of the session.
68 Administration Guide
Central Management
Status
Indicates the result of the backup session.
Start time
Indicates the start time of the session.
End time
Indicates the end time of the session.
Method
Identifies the type of backup method used for the session.
Flags
Indicates the internal flags created by Arcserve Backup to identify the session.
MB
Indicates the amount of data backed up for the session.
Files
Indicates the number of files backed up for the session.
Missed
Indicates the number of files not backed up during the session.
Device and Media
Device
Indicates the tape drive or file system device used during the backup of the
session.
Media Used
Indicates the media that was used during the backup of the session.
Error and Warning
Displays the errors and warnings that are generated during the back up of a session.
Central Management
70 Administration Guide
Central Management
The status is marked as failed if any of the sessions in the job fail.
The status is marked as incomplete in any of the sessions are incomplete even
if some are successful.
MB
Indicates the amount of data backed up for the job.
Files
Indicates the number of files backed up for the job.
Missed
Indicates the number of files missed during the backup.
Note: Use Arcserve Backup Agent for Open Files to back up open files to avoid
missed files during a backup.
Central Management
MB/Minute
At the Job level, MB/Minute indicates the ratio of megabytes and the elapsed
time for the entire job, including pre and post scripts, if any, media
management activities, and so on. For average master job throughput, refer to
the Activity Log.
At the Host level, MB/Minute indicates the ratio of megabytes and the elapsed
time for the entire job, including pre and post scripts, if any, media
management activities, and so on for a single host.
At the Session level, MB/Minute indicates the ratio of megabytes and the
elapsed time for a specific volume and its folders, which comprise a single
session.
Note: If little or no data is backed up by the backup job, a value of N/A appears in
the MB/Minute field.
Time Used
At the Job level, Time Used indicates the elapsed time for the entire job
including pre and post scripts, if any, media management activities, and so on.
At the Host level, Time Used indicates the elapsed time for the entire job
including pre and post scripts, if any, media management activities, and so on
for a single host.
At the Session level, Time Used indicates the elapsed time for the backup of a
specific volume and its folders, which comprise a single session.
Job ID
Identifies the specific execution of the job.
Job No.
Identifies the job.
Compression Ratio
The amount of actual data to be stored divided by the amount of data stored after
deduplication expressed as a ratio or percentage.
In the bottom pane, the following information is displayed:
Summary
Total Sessions
Indicates the number of sessions that were backed up by the selected job.
Total Migrations
Indicates the number of sessions migrated in a disk or tape staging job.
72 Administration Guide
Central Management
Session Detail
Execution Time
Indicates the start time and end time of the selected session.
Number
Indicates the session number.
Type
Identifies the type of session backed up.
Path
Indicates the root path of the session.
Central Management
Status
Indicates the result of the backup session.
Start time
Indicates the start time of the session.
End time
Indicates the end time of the session.
Method
Indicates the backup method used for the session.
Flags
Indicates the internal flags created by Arcserve Backup to identify the session.
MB
Indicates the amount of data backed up for the session.
Files
Indicates the number of files backed up for the session.
Missed
Indicates the number of files not backed up during the session.
Device and Media
Device
Indicates the tape drive or file system device used during the backup of the
session.
Media Used
Indicates the media that was used during the backup of the session.
Error and Warning
Displays the errors and warnings that are generated during the back up of a session.
74 Administration Guide
Central Management
2.
Show jobs with the status--Lets you filter jobs based on the job status.
Show done jobs with the results--Lets you filter done jobs based on the jobs
status
In--Used in conjunction with Keywords, lets you specify whether the keyword is
contained within the Backup Server Name or the Job Name.
Show jobs owned by other users--Lets you view all jobs or only the jobs that
you own.
Show jobs by selected types--Lets you view jobs based on the type of job. For
example, a backup job, a restore job, a migration job, and so on. To specify the
types of jobs that you want to view, click Select Types.
Click Update.
The filter options are applied.
Group by--Specify the type of group to sort by. The options are by job, host, or
source group.
Show history in last xx days--Specify the number of days of job history you
need. The range is from 1 to 100 days.
Show groups with the most recent result--Specify what type of result history
you want to view. You can specify one, all or any combination of options. The
options include active, finished, incomplete, failed, and canceled.
Note: The header bar turns yellow when there is a change made to the type of
result history you want to view indicating that the advanced filter was used.
Keywords--Specify the keywords that you want to use in the sorting of the job
history by Job Name or Host Name.
Note: The header bar turns yellow when a keyword is specified indicating that
the advanced filter was used.
In--Specify a Job Name or Host Name. The keywords are used to identify jobs in
the chosen category.
Central Management
2.
Click Update.
The filter options are applied.
2.
3.
Host
Job
Source Group
Depending upon your selection, the job history appears in either Host View or Job
View.
4.
Click Update.
The Properties panel displays the job history.
Important! Quick Search will only search items displayed on the user interface. It will
not search for particular data stored on a tape.
Note: To enhance Quick Search performance, you can filter the Activity Log to reduce
the number of items displayed and queried prior to using Quick Search. For more
information about filtering the Activity Log, see Set Activity Log Queries (see page 331).
76 Administration Guide
Central Management
Press CTRL+F to open the Quick Search dialog from any tree or list view on the
Arcserve Backup user interface.
For a list of where and how you can access the Quick Search feature using Ctrl+F
from the user interface and a sample of the kind of items that can be searched, see
Quick Search Accessibility (see page 78).
Note: You can also launch Quick Search from the context menu of a tree or list view
when you right-click and select Quick Search.
2.
3.
(Optional) Click the plus sign icon to expand the Search options field and choose the
options that apply.
Match case
Search using case-sensitive capitalization.
Match whole word
Search using whole word matches and not part of a word.
4.
5.
Central Management
6.
7.
To close the Quick Search dialog, press ESC or click the X button to close.
Manager
Location
Tree/List View
Searchable Items
Job Status
Tree
Domain, Server
List
Job
List
List
Source Tab
Tree
Machine, Folder
List
Tree
Server, Group
List
Tree
Server, Group
List
Tree
List
Tree
Machine, Folder
List
Machine, Folder
Tree
Server, Device
List
Media Pool
Manager
Tree
Media Pool
List
Database Manager
Tree/List
Backup Manager
Destination Tab
Restore Manager
Source Tab
(By Tree, By Session,
By Image, By
Backup Media)
Destination Tab
Device Manager
78 Administration Guide
Manager
Merge, Media
Assure & Scan,
Compare, Copy,
Count, Purge
Location
Tree/List View
Searchable Items
Tree/List
From the Job Status Manager, select the Job Queue tab.
2.
3.
4.
80 Administration Guide
5.
6.
(Optional) Enter the number of days that must elapse before you need to change
the password.
From the Backup Manager, select the Options button on the toolbar.
The Global Options dialog opens.
2.
3.
Select the option Save Current Session Encryption Password into Database.
4.
(Optional) Enter the number of days that must elapse before you need to change
the password.
5.
Select the Submit button on the toolbar to submit the backup job and save the
session encryption password to the Arcserve Backup database.
Using the User Profile Manager, Arcserve Backup supports the following management
functions for users and roles:
Add a user.
Delete a user.
You can assign a user multiple roles, providing the user with a variety of permissions.
The following diagram illustrates a user with multiple roles:
82 Administration Guide
Permission
Role
Admin
Backup
Restore
Device
Monitor
Report
Tape
Submit Jobs
Job
Log
Reports
Service
Media Pools
Database
Dashboard
MMO
Other
X
X
Role
Admin
Backup
Restore
Backup
Restore
Compare
Scan
Role
Admin
Backup
Restore
Merge
Generic*
Count
Purge
Copy
X
* Note: This is a job created using the Job Scheduler Wizard.
Role
Admin
Backup
Restore
Device
Monitor
Tape
View
Format/Erase
Config FSD
Config Groups
Config DDD
DDD Groups
Retention
Compression
Eject
Rebuild
Mount
Import/Export
Clean
Rescan
View Properties
84 Administration Guide
Role
Admin
Backup
Restore
Device
Monitor
Tape
Job Operations
Role
Admin
Backup
Restore
Device
Monitor
Tape
Add
Modify
Reschedule
Run/Stop
Delete
Modify Username
Run PFC
Modify password
Role
Admin
Backup
Restore
Device
Monitor
Tape
Role
Admin
Backup
Restore
Device
Monitor
Tape
Report Operations
Role
Admin
Backup
Report
Tape
View/Create
Design
Service Operations
Role
Admin
Backup
Restore
Device
Monitor
Tape
Start/Stop specified
services
86 Administration Guide
Service Operations
Role
Admin
Add/View Licenses
Manage Licenses
Install/Uninstall options
Backup
Restore
Device
Monitor
Tape
Role
Admin
Backup
Restore
Device
Monitor
Tape
Database Operations
Role
Admin
Backup
Restore
Monitor
Database Operations
Role
Admin
Backup
Restore
Monitor
MMO Operations
Role
Admin
Backup
Other Operations
Role
Admin
Backup
Restore
Device
Monitor
Report
Tape
Configure Alert
Manager
Use Diagnostic
Manager
88 Administration Guide
Extended Permissions
The User Profile Manager includes the following extended permissions:
Note: To help ensure that a Windows user account with a blank password can log in to
Arcserve Backup successfully, you must configure a Windows Security Setting Option
(see page 90).
To help ensure that users that are logged in to Arcserve Backup with a Windows user
account that has Arcserve Backup administrative privileges can access database related
activities (for example, view the Activity Log, view the Audit Log, monitor jobs, and so
on), the Windows user account must be configured as follows:
The Windows user account must be able to log in to Microsoft SQL Server or
Microsoft SQL Server Express databases.
The Windows user account must be assigned the Microsoft SQL Server or Microsoft
SQL Server Express SysAdmin role.
2.
3.
4.
Double-click the Accounts: Limit local account use of blank passwords to console
logon only option.
5.
90 Administration Guide
To access a server running this release of Arcserve Backup, click the Windows
Start button, point to Programs, CA, ARCserve Backup, and click Manager.
Double-click ARCserveMgr.exe.
To change the default server or specify a different server, select a server from the
Arcserve Backup Primary Server list. If the target server does not appear in the
drop-down list, you can input the host name or IP address of the server in the
Arcserve Backup Primary Server list.
3.
4.
Enter caroot in the User Name field, the appropriate password in the Password
field, and click OK.
The first time you log in to Arcserve Backup, a tutorial, called My First Backup,
appears. This tutorial lets you become familiar with the basics of backing up and
restoring data in a controlled and directed way. This tutorial appears automatically
only the first time you log in. However, you can access My First Backup from the
Help menu.
92 Administration Guide
2.
To change the default server or specify a different server, select a server from the
Arcserve Backup Primary Server list. If the target server does not appear in the
drop-down list, you can input the host name or IP address of the server in the
Arcserve Backup Primary Server list.
3.
4.
Enter caroot in the User Name field, the appropriate password in the Password
field, and click OK.
The first time you log in to Arcserve Backup, a tutorial, called My First Backup, appears.
This tutorial lets you become familiar with the basics of backing up and restoring data in
a controlled and directed way. This tutorial appears automatically only the first time you
log in. However, you can access My First Backup from the Help menu.
2.
3.
4.
On the General tab, select Windows Authentication and enter the following
information:
5.
Click OK.
The Windows user is added to the Arcserve Backup database.
Any valid Windows user can be added to Arcserve Backup from the User Profile
Manager.
Only the Arcserve Backup Administrator with a Security Administrator role can add
a user.
Note: To make sure a Windows user with a blank password will not fail to log on to
Arcserve Backup, you must configure a Windows Security Setting Option (see
page 90).
2.
94 Administration Guide
3.
4.
On the General tab, select Arcserve Backup Authentication and enter the following
information:
Username--Enter the new user name. You cannot use the "\" character.
5.
Click OK.
The Windows user is added to the Arcserve Backup database.
Any valid Windows user can be added to Arcserve Backup from the User Profile
Manager.
Only the Arcserve Backup Administrator with a Security Administrator role can add
a user.
2.
3.
4.
Click OK on the message dialog and restart all Arcserve Backup Managers that are
connected to the server.
2.
3.
4.
Description--Lets you add information in the description field about the user.
On the Role tab, add or delete the roles assigned to the user.
2.
3.
4.
96 Administration Guide
On the Role tab, add or delete the roles assigned to the user.
Delete a User
Use the following steps when you want to delete a user from Arcserve Backup.
To delete a user
1.
2.
Select the user you want to delete and click the Delete button on the toolbar.
The delete confirmation box appears.
3.
Select Yes.
The user is deleted
Only the Arcserve Backup Administrator with a Security Administrator role can
delete a user.
2.
3.
4.
5.
Select a user and click OK. Alternately, you can double click a user.
The Role Properties dialog re-opens.
6.
Click OK.
The user is added to the role.
2.
3.
4.
5.
6.
Click OK.
The user is deleted from the role.
98 Administration Guide
Event Types--Specify the type of event to sort by. The options are Success audit
and Failure audit.
Event--Specify what event you want to view. You can choose a specific user
task or All user tasks.
Note: The header bar will turn yellow if there is a change made to the type of
event you want to view, indicating that the advanced filter was used.
User--Specify the user whose audit log you want to view. The default is All.
Note: The header bar will turn yellow if a user is specified, indicating that the
advanced filter was used.
2.
From--Specify the start day and time of an event. The option includes First
Event and Events On.
To--Specify the end day and time of an event. The option includes First Event
and Events On.
Click Update.
The filtered results are displayed in the Properties panel.
2.
2.
3.
4.
Right click and select Properties. Alternately, double click the record.
The Audit Record Properties dialog opens.
5.
6.
On the Audit Record Properties dialog the following options are available:
Click OK.
The Audit Record Properties dialog closes.
2.
3.
4.
5.
2.
From the domains directory tree, click the Arcserve Backup primary server
containing the audit log that you want to export.
The Job Queue, Job History, Activity Log, and Audit Log tabs appear.
3.
4.
5.
In the Save As dialog, specify a location and file name for the file.
Click Save.
The audit log is exported to a text file.
2.
From the domains directory tree, click the Arcserve Backup primary server
containing the audit log that you want to print.
The Job Queue, Job History, Activity Log, and Audit Log tabs appear.
3.
4.
5.
Click OK.
The Audit Log is printed.
2.
3.
4.
5.
Older than--Enter a specific time based on the following criteria: 1 to 365 days,
1 to 54 weeks, 1 to 12 months, and 1 to 10 years.
Click OK.
The Audit Log records are deleted.
From the Sever Admin, select the Configuration button on the toolbar.
The Configuration dialog opens.
2.
3.
Select the Enable messages logging into Windows Event Log checkbox.
The Audit Log information is included in the Windows Event Log.
More information:
Event Log Configuration (Windows Servers) (see page 508)
You can use all of the devices or you can specify a single group of devices. If the
Arcserve Backup Tape Library Option is installed and the group with the library is
selected, multistreaming uses all library devices. If the Arcserve Backup Tape Library
Option is not installed, you can put devices into separate groups. For a changer, the
total number of streams (child jobs) that are created depends on the number of tape
devices. For a single tape drive device, the total number of streams depends on the
number of device groups.
Multistreaming is performed at the volume level for regular files (two volumes can run
simultaneously on two separate devices), and at the database level for local database
servers. Multistreaming is performed at the node level for the Preferred Shares folder,
remote database servers, and Windows Client Agents.
You can have only as many jobs running simultaneously as the number of devices or
groups that are on the system. With multistreaming, one parent job is created that will
trigger child jobs for as many volumes as you have. When a job is finished on one
device, another job is executed until there are no more jobs to run.
Some characteristics and requirements of multistreaming are as follows:
Each client machine can have multiple source streams, depending on the number of
agents being backed up.
Each agent can have a separate stream (one stream per agent).
Multistreaming always requires a media pool selection to prevent the tapes from
being overwritten.
Separate tape devices should be configured in separate groups for regular drives,
however for changers, they can be configured to be in the same group.
Canceling the parent job cancels all of the child jobs. For Windows, canceling and
monitoring is checked between jobs for performance considerations.
If a job spawns child jobs, the number of child jobs spawned will not exceed the
number of streams specified for the job. However, if a job spawns child jobs and
you do not specify a number of streams to use, the child jobs will be created and
backed up in one continuous stream.
In the Job Status Manager, each child job has a default job description with this
pattern:
JOB[ID][Servername](Multistream subjob [SID])[Status][Start time - End time][JOB
No.]
The multistreaming option is ignored if the groups you choose have only one
device, or if only one object (volume, database, or remote node) backup is
submitted.
You should use the same types of tape devices for multistreaming jobs. In order to
achieve the optimum performance with your multistreaming jobs, you should use a
high-end server machine with multiple processors and at least 256 MB memory per
processor.
Supported
Not Supported
If a local backup does not contain any VSS writers, the job can be a multistreaming
job.
If a local backup contains VSS writers, and both the following global options are
unchecked, then the job can be a multistreaming job:
If a local backup contains VSS writers, and any of the following global options are
checked, then the job cannot be a multistreaming job:
When a job that has multiple sources is submitted with the multiplexing option enabled,
it is broken into child jobs with one for each source. These child jobs write data to the
same media simultaneously. The number of child jobs spawned will, at most, be equal
to the number of streams specified for multiplexing. However, if a job spawns multiple
child jobs and the value specified for the Multiplexing Max # of Streams option is one,
the child jobs will be created and backed up in one continuous stream (the default Max
# Stream is 4).
Note: When using multiplexing, you can select the maximum number of streams that
can write to a tape at the same time. For more information, see Specify Multiplexing
Options (see page 190).
Multiplexing is useful when your tape drive throughput is faster than the rate at which
data can be extracted from the source. Factors that can affect backup throughput are as
follows:
The kind of data being backed up. For example, backing up large number of small
files reduces backup throughput because of the larger number of necessary file
system operations (file open and close).
The server resources like CPU speed, memory size, page file size, network card, and
amount of other activities on the server.
When data is backed up over the network from multiple sources, most of the previous
factors are involved, which reduces the throughput and increases the amount of time it
takes to perform a backup. In addition, if the tape drive is not consistently streamed, the
life of the tape drive is reduced drastically because of the "shoe shine" effect: when data
is written intermittently, the drive has to stop, and then go back and forth on the media
to adjust to the new position from where it has to write again. With multiplexing, data is
continuously available and tape drives are constantly streaming. This behavior
decreases the amount of time it takes to perform a backup while increasing the life of
the hardware.
Multiplexing is performed at the volume level for regular files, two volumes can run
simultaneously as two separate child jobs, and at the database level for local database
servers. Multiplexing is performed at the node level for the Preferred Shares folder,
remote database servers, and Windows Client Agents.
In the Job Status Manager, each child job has a default job description with this pattern:
JOB[ID][ServerName](Multiplexing subjob [SID])[Status][Start time - End time][JOB
No.]
Supported
Not Supported
Disaster recovery.
If you choose to encrypt your data during backup to a disk or tape, the algorithms
used to encrypt this data will be FIPS-compliant.
During backup time, the username and password will be sent to the Arcserve
Backup server agent (running on the server to be protected). This username and
password will be encrypted using FIPS-compliant algorithms and transferred to the
agent.
Arcserve Backup also supports tape drives (from external third-party vendors) that
provide FIPS-compliant hardware encryption. This is in addition to FIPS-compliant
tape or disk encryption provided by the Arcserve Backup software.
Arcserve Backup provides additional agents and options that also use
FIPS-compliant algorithms to support data encryption. These agents and options
include: Agent for Microsoft Exchange Server, Agent for Microsoft SQL Server,
Agent for Microsoft SharePoint Server, and Arcserve Replication.
Run the cstop.bat script to stop all services before making the change.
ProgramFiles\CA\ARCserve Backup\cstop.bat
2.
Change the current encryption algorithm value to one of the candidate values.
ProgramFiles\CA\SharedComponents\ARCserve Backup\CryptoConfig.cfg
3.
4.
Run the cstart.bat script to start all services after making the change.
ProgramFiles\CA\ARCserve Backup\cstart.bat
Encryption at the agent server (or source) prior to the backup process
Encryption at the Arcserve Backup server during the migration process (for a staging
job)
These encryption options are accessible from the Encryption/Compression tab on the
Global Options dialog for the Backup Manager. From this dialog you can choose to
encrypt the data at the agent, at the backup server (during backup), or at the backup
server (during migration).
You can also create a session encryption password that is saved to the Arcserve Backup
database. This password is used to encrypt session data. For more information about
passwords, see the topic How Password Management Works (see page 79).
Note: Arcserve Backup will only encrypt data that is not already encrypted. If at any
stage in the process Arcserve Backup detects that the data has already been encrypted,
it will not attempt to encrypt it again. Since data deduplication is a form of encryption,
you cannot encrypt data saved to a deduplication device.
In addition, there are also two basic methods for encrypting data; hardware encryption
and software encryption. The advantages of hardware encryption are speed and
improved CPU performance. Encryption using software is slower than encryption using
hardware and can result in a larger backup window. By using hardware encryption, you
can also avoid unnecessary CPU cycles on either the agent server or the backup server
and the drive can compress the data before encrypting.
If you select to have your data encrypted during the backup or migration process,
Arcserve Backup has the ability to detect if the final destination media (tape) is capable
of hardware encryption and by default will automatically choose that hardware method
if available.
Not all Arcserve Backup agents have the capability to encrypt data prior to transferring
it to the Arcserve Backup server.
The following Arcserve Backup agents support at the agent server data encryption:
The following Arcserve Backup agents do not support at the agent server data
encryption:
If Arcserve Backup detects that the final destination media is not capable of hardware
encryption, it will then perform software encryption of the data prior to migration to
the final destination media.
From the Administration menu in the Navigation Bar on the Home Page, click
Device Wizard.
The Device Wizard Welcome screen appears.
2.
Click Next.
The Login dialog appears.
3.
Enter or select the server you want the device command to operate on, enter your
user name and password, and click Next.
4.
Select the device you want to target. Click More Information to view more
information about the device.
5.
6.
7.
Enter a new media name and expiration date for the media Arcserve Backup is
about to format, and click Next.
8.
The schedule screen that appears lets you choose to run the device command
immediately or schedule it for a later date and time. Select Run Now, and click Next
to run the job immediately.
To schedule your job for a later time, select the Schedule option, and enter a date
and time for the job to run.
9.
10. You are prompted to confirm the action you are about to take. Click OK to start the
device operation and display its status.
11. A message appears to notify you that Arcserve Backup has completed the device
operation. Click Next to work with another device, or click Exit to close the Device
Wizard.
If you have more than one storage device connected to your network machine, Arcserve
Backup lets you group the devices. This allows you to have one group perform a backup,
while another group performs a restore operation, in a process known as parallel
streaming.
If you have several devices in a group, and your job spans more than one media, the
Device Manager can automatically span the media for you. You can then submit large
backup jobs to Arcserve Backup and automatically span multiple media until the jobs are
complete.
For example, if you have two media groups, GROUP1 (consisting of one storage device)
and GROUP2 (consisting of two storage devices), and you have a large backup job that
requires more than one media, you can insert blank (formatted) media into each
GROUP2 drive and Arcserve Backup automates the media spanning for you. Without
media spanning, you must change the media manually.
Note: For deduplication, device groups can contain only one deduplication device.
In the Device Manager, click Configure Groups to open the Device Group
Configuration dialog.
2.
3.
4.
Enter a name for the new group, and click OK. The new group appears in the
Groups field.
5.
Highlight both the device and the new group, and click Assign to assign the device
to the new group.
6.
Click OK.
What is the server and data growth you anticipate over the next year?
How do you want to manage the media you are using for backup?
How do you plan to store your data? Are you using magnetic tape or does the
stability of WORM media better suit your needs?
From the Source tab on the Backup Manager window, right-click the Preferred
Share/Machines object and select Add Object from the pop-up menu
The Add Preferred Shares dialog opens.
2.
3.
4.
Full Backup--Backs up all of your files. This backup method requires more time to
process compared to incremental or differential backups. However, because all of
your data is backed up, this strategy requires only the last backup media to restore
your data completely.
Incremental Backup--Backs up only those files that have changed since the last full
or incremental backup was performed. Since this strategy backs up only new or
newly changed files, incremental backups require less time to process. However,
this strategy requires the full media set and every incremental set, including the
latest set, to fully restore your data after a disaster.
Differential Backup--Backs up only those files that have changed since the last full
backup was performed. Since files that were backed up in the last differential job
are backed up again, differential backup jobs require more time to process than
incremental backup jobs. However, this strategy requires only two sets of media to
restore a differential backup, the full media set, and the differential media set.
Note: For any rotation scheme that you use, you should include at least one full backup
per week.
The Media Pool Manager lets you create and maintain the Arcserve Backup media
pools. Each media pool is assigned a name, and is organized according to serial
numbers. The serial numbers assigned are permanent. If you use a device with a bar
code reader, the bar code labels are used as the serial number of the media. Media
pools are organized by the range of serial numbers of the media they contain. Media
pools apply to every media, regardless of which backup or archive type and method
were selected.
You should perform a full backup at least once a week. On all other days, you can
perform full or partial backups or no backup at all. The advantage of setting up a GFS
rotation scheme is that once it is configured, you need only make sure the right media is
in the drive for each day of the week.
From that time on, GFS tells you which media to use and manages the backups for you.
A full backup is performed at least once a week. The last full backup of the week is
the Father media
The last full backup of the month (monthly backup) is the Grandfather media
Note: Monthly backups are saved throughout the year and the media on which they are
stored should be taken off-site for safekeeping. You can track these media using the
Media Management Admin.
Important! GFS rotations create three media pools--daily, weekly, and monthly pools.
You cannot entirely customize this rotation and the media used for the rotation scheme
must be named automatically. Custom rotation schemes allow you to configure the
properties of the scheme, such as the pool or pools involved, the days to back up, and
other properties. Deduplication devices are an exception: even though deduplication
devices cannot be assigned to media pools, you may still set up GFS rotations. For more
information, see GFS Rotation Jobs on Deduplication Devices (see page 756).
You back up your data on a separate tape every working day. You should use a
different tape for every daily backup. For example, if your backup cycle is based on
a five-day workweek, you will need four "Daily" tapes before you use a weekly tape.
(Maybe label the daily tapes Monday, Tuesday, Wednesday, and Thursday or Daily
1 through Daily 4, and so on.). You can perform Full, Incremental, or Differential
backups for your daily backups. After the fourth day, the first daily tape used is then
re-cycled and can be overwritten with the next scheduled daily backup.
Remember, because the daily tapes are used more frequently than the weekly and
monthly tapes, you will need to replace them more often.
On the fifth day, instead of using another daily tape, you will use a "Weekly" tape.
You should always perform a Full backup for your weekly backups. You should also
use five weekly tapes before you use a monthly tape. (Maybe label the weekly
tapes Week 1 through Week 5). After the fifth week, the first weekly tape used is
then re-cycled and can be overwritten with the next scheduled weekly backup.
At the end of the third week, instead of using another weekly tape, you will use a
"Monthly" tape. You should also perform a Full backup for your monthly backups.
You should have 12 monthly tapes to safely backup a full year of data. (Maybe label
the monthly tapes January through December or Month 1 through Month 12, etc.).
After twelfth month, the first monthly tape used is then re-cycled and overwritten
with the next monthly backup.
The following diagram shows an example of how a typical 5-day GFS rotation policy can
be implemented to provide you with a safe and reliable method to perform data
backups for an entire year while using a minimum amount of backup media:
Note: A five-day GFS rotation policy would require approximately 21 tapes per year,
while a seven-day policy would require approximately 23 tapes per year (adding two
additional daily tapes). For both of these schedules, the amount of media needed can
vary depending upon your specified retention criteria and the quantity of data that you
are backing up. Additionally, the amount of media needed in each schedule can also be
affected by the use of multistreaming and if you are appending backup sessions to your
media.
Agent Checks--These include checking the connection and credentials for any client
and database agents needed for the job.
Note: The Preflight Check utility does not validate login credentials for the following
database agents:
Media Checks--These include checking the availability of media in the scratch set (if
a media pool is specified for the job), checking the media expiration dates, and
checking for source and destination conflicts for File System Devices.
The optimum time to run this command is a couple of hours before your jobs are
scheduled to run so that you can have ample time to correct any problems that may
appear in the PFC report. For more information on the PFC utility and its associated
options, see the Command Line Reference Guide.
Before submitting a job, you can run a Preflight Check clicking the Preflight Check button
on the Submit Job dialog.
2.
If Arcserve D2D is not installed on the backup server, the Arcserve D2D Server
Information dialog opens. From the Arcserve D2D Server Information dialog,
you can log in to a remote Arcserve D2D server, or download and install
Arcserve D2D.
If Arcserve D2D is installed on the backup server, the Log in to Arcserve D2D
screen opens.
User Name--Specify the User name required to log in to the Arcserve D2D
domain.
2.
Because Arcserve Backup separates and lists Windows machines by the domain or
workgroup to which they belong, you can easily back up all the machines belonging to a
specific domain or workgroup, by selecting the name of the domain or workgroup.
The optional Arcserve Backup Client Agents allow you to communicate with remote
workstations in various environments. This provides complete system backups,
including system information from non-Windows systems, such as UNIX.
Similarly, the optional Backup Agents allow Arcserve Backup to back up and restore
online databases such as Microsoft Exchange Server, Lotus Domino, Microsoft SQL
Server, Oracle, and IBM Informix.
Important! When setting local options, you must select drives individually as your
source even if you want to back up an entire server. You cannot click the green box
next to the server name, and then customize local backup options for individual
drives.
2.
Scan Backup Media Contents--If you select this, Arcserve Backup scans the
media and check that the header is readable for each file that is backed up.
More information:
Local Backup Options for UNIX and Linux Agents (see page 152)
From the Backup Manager, select the Start (see page 139), Source (see page 140),
Destination, and Schedule (see page 152) tabs to specify the options that you
require for the job.
Click the Options toolbar button to specify global options that you require for the
job. For more information, see Global Backup Options (see page 154).
Click the Submit toolbar button to submit your job.
The Security and Agent Information dialog opens.
2.
On the Security and Agent Information dialog, edit or confirm the security and
agent information for your job, and click OK.
3.
When the Submit Job dialog opens, select Run Now to run the job immediately, or
select Run On and select a date and time when you want the job to run.
Note: For more information about the Run Now option, see Job Queue Tab.
4.
5.
If you selected multiple sources to back up and want to set the priority in which the
job sessions initiate, click Source Priority. Use the Top, Up, Down, and Bottom
buttons to change the order in which the jobs are processed. When you finish
setting priorities, click OK.
Backup Manager
6.
To save the job as a Arcserve Backup job script, click the Save Job button.
7.
8.
To preflight check the job, click the Preflight Check button. If the preflight check
failed, click the Cancel button to modify the job settings.
9.
More information:
How to Manage Jobs Using the Job Queue Tab (see page 323)
Backup Manager
The Backup Manager lets you customize your backup jobs using filters, options, and
scheduling.
You can use the Backup Manager to:
Use filters to selectively exclude or include directories and files from backup jobs.
Apply filters to local source objects (such as volumes and nodes) or globally to the
entire backup job, or to both at the same time.
Backup Manager
Arcserve Backup allows you to back up the Windows registry as well as the system state
for Windows systems. Each backup job requires a source and a destination (media). The
Backup Manager screen provides tabs to customize your backup job:
Source--Lets you specify the data that you want to back up.
Schedule--Lets you specify a schedule, repeat method, or rotation scheme for the
job.
Destination--Lets you specify the location where you want to store your backup
data.
The topics that follow provide full details about the options available on each tab.
This section contains the following topics:
Options on the Backup Manager Start Tab (see page 139)
How to Specify Source Data Using the Classic View and the Group View (see page 140)
Backup Manager Destination Options (see page 149)
Backup Job Schedules and Rotations (see page 152)
Backup Manager
Deduplication backup--Deduplication backup lets you save only unique data chunks
to disk, allowing you to fit more backup sessions on media, retain backups for
longer periods of time and speed up data recovery. For more information about
submitting deduplication backup jobs, see Back Up Data with Deduplication. (see
page 740)
For each backup type, you must click the Source (see page 140), Schedule (see
page 152), and Destination tabs to complete backup job configuration.
You may also Enable Staging (see page 200). Staging operations allow you to back up
data to a staging device and then migrate the backed up data to a final destination
(usually a tape). You can choose to Enable Staging on Normal, Deduplication, or Data
Mover backup jobs.
You can also select Enable Synthetic Full Backup (see page 810). A synthetic full backup
lets you synthesize a previous full session and its subsequent incremental sessions to a
full session. You can choose to enable synthetic full backups on Normal backup with
staging option, Deduplication backup with staging option, or Deduplication backup jobs.
In addition to completing backup job information on the Source, Schedule, and
Destination tabs, ensure you complete the information on the Staging Location tab and
define a synthetic schedule on the Schedule tab.
Backup Manager
How to Specify Source Data Using the Classic View and the Group View
The source is the path to the data that you want to back up. You can easily find the files
you want to back up by browsing through the Backup Manager directory to select the
user-shared drives and directories.
Arcserve Backup lets you browse and specify the source data using the following views:
Classic View--This is traditional source view. Machines are listed first, allowing you
to expand and then select specific data sources. With the Classic View, Arcserve
Backup categorizes source computers based on the platform that is running on the
computer. For example, Windows systems, UNIX/Linux systems, and Hyper-V
systems.
Group View--This view categorizes source computers based on the Arcserve Backup
agent that is installed on the computer. The agents are listed as branches on the
source tree. Within each branch, the computers that contain the specified agent are
listed.
You may also create customized groups that allow you to group machines according
to your own criteria. For example, using the Group view is effective approach to
specifying source when you want to back up database files such as Microsoft SQL
Server, Microsoft Exchange Server, and Microsoft SharePoint Server data that
reside on a large quantity of machines, without having to expand each machine and
then select the database node.
Note: The Agent for Microsoft Exchange Server 2010/2013 appears only in the
Exchange Organization object. You cannot add Agent for Microsoft Exchange Server
2010/2013 systems to the Microsoft Exchange Server group.
an entire application
an entire server
To select individual drives, directories, and files to back up, expand a server name
and click the green boxes next to each drive, directory, and file.
To select an entire source group, click the green box next to the group name. When you
do this, all the servers, nodes, volumes, drives, directories, and files included in the
source group are automatically selected.
Backup Manager
The view that you specify when you submit a job cannot be modified.
For example, you submit a job using the Classic View. Subsequently, you want to
modify the source selections for the job. When you modify the job and click the
Backup Manager, Source tab, the view drop-down menu is disabled. The following
screen illustrates this behavior.
Green marker--Lets you control the extent of the backup for an object directly. Click
a marker to exclude an object from a backup or to indicate that you want the
backup for the object to be full or partial. As you click the marker, you fill or empty
the marker of color, indicating the extent of the backup.
Gray marker--These markers are associated with objects that are not real and that
you cannot back up/restore. Typically, these items serve as placeholders under
which other objects are grouped and displayed. As you click the green markers
under a gray marker item, the fill proportion of the gray marker changes
automatically from empty to partial to full depending on the proportion of files you
have chosen to back up.
Backup Manager
The following table describes the different marker configurations and corresponding
backup levels:
Marker
Description
Full backup.
Partial backup.
Note: Gray marker configurations follow the same pattern as green marker
configurations, but reflect the proportion of files under them that are selected for
backup.
The fill proportion of a marker at a higher level of the directory tree depends on the fill
proportions of the markers of the objects at the lower levels.
If you click a marker at a higher, parent level so that it is completely filled, all the
markers at the lower, child levels are automatically filled completely.
If you click all the markers at the lower, child levels so that they are completely
filled, then the marker at the higher, parent level is automatically partially filled.
If the markers at the lower, child levels are a mix of completely filled and partially
filled, the marker at the higher, parent level is automatically partially filled.
Backup Manager
How Arcserve Backup Lets You Browse a Large Number of Items in the Backup Manager
Arcserve Backup lets you pause the process of loading items in the Backup Manager
when you browse a large number of directories, files, and so on. The steps that follow
describe how Arcserve Backup lets you browse a large number of items in the Backup
Manager window.
1.
When you select a directory in the Backup Manager, Source tree, Arcserve Backup
displays a Loading dialog to inform you that a large number of items need to be
retrieved and loaded into the Backup Manager window. You cannot click Cancel
while Arcserve Backup is retrieving the list of items to display in the Backup
Manager window.
2.
After Arcserve Backup retrieves the list of items to display in the Backup Manager
window, the Loading dialog then displays the percentage of items that are loaded
into the Backup Manager. If there are a large number of items to display, you can
click Cancel to pause the loading process.
Backup Manager
3.
After you pause the Loading process, you can continue the Loading process by
right-clicking target directory and selecting Show More from the pop-up menu.
4.
If you pause the loading process, the icon for the target directory appears as
follows:
5.
You can pause and continue the loading process as often as necessary. To load
more items, right-click the target directory and click Show More from the pop-up
menu.
6.
When the loading process is complete, the icon for the target directory displays as
follows:
Open the Backup Manager and specify a target directory from the Source tree.
The Loading message box appears, Arcserve Backup retrieves a list of items to
display in the Backup Manager Window, and then Arcserve Backup loads the files
into the Backup Manager window.
Backup Manager
2.
From the Loading message box, click Cancel to stop the loading process.
If Arcserve Backup did not load all items, the To show more objects, right-click the
target directory and select Show More from the pop-up menu warning message
appears.
Note: The message only appears the first time you click Cancel on the Loading
message box.
3.
From the Source tree, right-click the target directory and click Show More from the
pop-up menu.
The Loading message box appears and Arcserve Backup continues loading the
items.
4.
You can pause and continue the loading process as often as necessary until
Arcserve Backup loads all items in the target directory.
If you pause the loading process, the icon for the target directory displays as
follows:
When the loading process is complete, the icon for the target directory displays as
follows:
Backup Manager
2.
Expand the computers in the source tree. If prompted, you must provide the
required security information.
The following screen illustrates the computers available in Group View for the
Client Agent for Windows.
Note: If you want to customize the groups that appear in the Source tree, click
Customize Group. For more information, see Configure Customized Groups in
Group View (see page 147).
3.
In the source tree, search for the desired agent type and expand it to view a list of
computers.
Backup Manager
4.
(Optional) Search for a computer using global filters that are saved when you exit
Backup Manager and remain set until changed.
Server Name--Lets you filter source computers by the string you enter.
Agent type--Lets you filter computers by agent type. In Group and Classic
Views, the Agent Type filter lets you view only the agent groups that
correspond to the agent selected. For more information, see Filter Nodes (see
page 339).
Job History also lets you view results by source group. For more information, see
How to Analyze Jobs Using Group View. (see page 328)
2.
3.
b.
Click OK.
The new group is added to the list of groups on the left.
4.
Backup Manager
5.
From the list of servers on the right, click a server to add to the group and click
Assign.
The server appears below the group.
Repeat this step, as required, to add more servers to the group.
6.
2.
Backup Manager
3.
To reassign servers, select a server that you want to remove from the left side
of the dialog and click Remove.
The server is added to the list of available servers on the right. From the list of
available servers, choose a server to add. Click Assign. The server is added to
the group.
4.
Click OK when done managing customized groups to save settings and exit
Customized Group Configuration.
Note: Multiplexing is not supported for UNIX/Linux Data Mover backup jobs.
Multistreaming
The Multistreaming option lets you split single backup jobs into multiple jobs and use all
of the available tape devices in your system to complete the backup. For more
information, see Multistreaming (see page 103).
Group and Media field
Use the Group and Media field to specify the device group that you want to use for
the backup job.
Place an asterisk in the Group or Media field to use the first available drive and
media in the group.
If you want to use any available group, click the Use Any Group option.
Backup Manager
Media Pool
Select this option if you want to use a specific media pool for the backup job.
Be aware of the following:
If you select a Media Pool, Arcserve Backup automatically checks that the other
destination and backup options you selected to verify that no restrictions or
conflicts occur when you run the job. If Arcserve Backup detects a conflict, a
warning dialog opens.
Server
This field displays the name or the primary server and member servers in your
Arcserve Backup domain.
Note: If you did not install the Central Management Option, the name of the
current server displays in this field.
With Enable Staging checked:
Deduplication Policy
Click this button to open the Deduplication Purge Policies dialog. This dialog lets
you set the purge policy for full and differential/incremental backups.
Create Duplicate in-line
Select this check box to enable the Group, Duplicate Media prefix, and Duplicate
Media pool prefix fields. These fields enable you to perform a Double Tape Copy,
where you can migrate the data to two final destinations at the same time. To
ensure that the migration job continues when one of the devices become
unavailable, you can set a timeout value for additional backup media to continue
the migration job in another device. If you do not set a timeout value, then the data
migration job fails after the first backup media timeout completes. For more details
about setting the timeout value, see Backup Manager Backup Media Options (see
page 164).
Note: Ensure that a Disk Staging device is configured on your environment to
perform a Double Tape Copy.
Group
Select a device group from the drop-down to determine where the duplicate is
created.
Note: Tape/Changer groups and File System Device (FSD) groups are the only device
groups available. When the backup job is submitted and the same device group is
selected for both the final destination and the duplicate destination, the application
will verify that there are two or more drives.
Duplicate Media prefix
This field lets you specify a prefix for the media name you want to duplicate. For
example, "CPY_<media name>".
Backup Manager
Full (Keep Archive Bit)--Performed each time the job is repeated and keeps the
archive bit.
Full (Clear Archive Bit)--Performed each time the job is repeated and clears the
archive bit.
Incremental backup--Backs up only those files whose archive bits have been set
since the last full or incremental backup was performed. After each backup, archive
bits are reset so that they are not backed up during the next incremental backup
job.
Differential backup--Backs up only those files whose archive bits have been set
since the last full backup was performed. Because differential backup jobs do not
clear a files archive bit, the files that were backed up in the last differential job are
backed up again. It takes longer to process backup jobs using this method.
However, this strategy requires only two sets of media to restore a differential
backup; the full media set, and the differential media set. In the case of an
incremental backup, you require the full media set and every incremental set until
the latest set. For a synthetic full backup job, if the agent supports synthetic full
backups, the differential backup job is converted to an incremental backup job.
Note: The above-described backup methods do not apply to the Linux Client Agent.
For a description of detailed job scheduling features, see Customizing Jobs (see
page 301).
Traverse Symbolic Link File--Arcserve Backup follows symbolic links and backs up
the linked files.
Estimation Off--Disables the estimation of the number of files and the amount of
data to be backed up that takes place at the beginning of the backup job. Selecting
this option decreases the time it takes to perform the backup.
Preserve File Access Time--This option directs Arcserve Backup to preserve the last
access time of files when a backup is performed.
Note: The Access Time of a file is automatically updated by the operating system
whenever a file is accessed (read or write). However, after a compare is performed,
the Access Times of all the backed up files are also updated. Therefore, if you want
to track whether or not a file has actually been accessed (and not just compared),
you need to preserve the original access time.
If this option is selected (check in box), Arcserve Backup preserves the last file
access time of any files that are backed as the original value that was present
before the backup was performed (Change Time will be updated). This is the
default setting.
If this option is not selected (no check in box), the last file access time of any
files that are backed up is updated to the new value that is present when the
backup is completed (Change Time will not be updated).
Note: For Windows based agents, you must apply this option globally. For more
information, see Global Backup Options.
Media format to use for backup
Posix tar format--This is a Standard Posix Tar format. When you select this option,
Arcserve Backup creates a backup image in Posix Tar format. Arcserve Backup or
any tar utility can be used to restore data from an image created in this format.
Using Arcserve Backup format is recommended.
Posix cpio format--This is a Standard Posix CPIO format. When you select this
option, Arcserve Backup creates a backup image in Posix CPIO format. Arcserve
Backup or any CPIO utility can be used to restore data from an image created in this
format. Using Arcserve Backup format is recommended.
More information:
Global Backup Options (see page 154)
Specify Local Backup Options (see page 134)
Virus Detected--A virus was detected in one of the files to be backed up. See Virus
options (Backup, Copy, Count).
Media not Available--Media was not available during the execution of a job.
Note: The backup media must be tape media.
Format Blank Tape--A tape was formatted during the execution of a job.
Choose one or more of the defined Alert configurations. The <default> configuration
means that you will use whatever is configured in Alert Manager. Click Configure to
define further configurations. Arcserve Backup provides the following defined Alert
configurations:
Broadcast
Pager
Note: Pager options are not supported on Japanese versions of Arcserve Backup.
SMTP
SNMP
Event
Printer
Lotus Notes
Unicenter TNG
Attach Job Log--Lets you include the job log information in the Alert message. (This
option applies for Trouble Tickets and Mail only.)
Note: The list you create using Alert Options is saved with the Job Script and the
configuration defined using the Configuration button.
Send alert messages only for master jobs--Lets Arcserve Backup send you alerts
that reference only the master job number in the Alert message. The alert
messages will not reference child and subjob numbers. You can specify this option
on all jobs, including multiplexing and multistreaming jobs.
None--No media exporting will take place at the end of a backup job.
Export RAID1 Duplicate Tape After Job--If the job spanned to multiple media, all
the duplicate media used in this job is exported.
Note: This option is for RAID 1 support with libraries and mail slots only.
Export All Tapes After Job--Arcserve Backup exports all the media for the related
backup. If the job spanned to multiple media, all the media used in this job is
exported. If there are not enough mail slots to export all the media, the media that
could not be exported is moved back to the original home slot. In single mail slot
libraries, Arcserve Backup retries a few times to check if the mail slot is empty to
move the next media to the mail slot. If the operator does not move the media,
Arcserve Backup writes this information in the activity log.
Note: This option is for RAID 1 support with libraries and mail slots only.
For staging backup jobs, media exporting options are only effective during the
migration phase of the job.
Media exporting options are functional only for regular and rotation jobs and are
supported on media libraries and Tape RAID.
Media exporting options are not supported when you are performing tape staging
(B2T2T) backups and the staging device or the final destination device is a RAID
device.
If the job includes verification, the export is done at the end of the verification.
Backup Mount Points as Part of the volume that they are mounted on--If you
select this, the volumes referred to by the Volume Mount Points will be backed up
as part of the same session as the Volume Mount Points. When this option is not
selected, the volumes referred to by the Volume Mount Points are backed up as
separate sessions. This option is available only when the previous option, Traverse
Directory Junctions and Volume Mount Points, is selected.
Preserve File Hard Links--If you enable this, Arcserve Backup preserves hard links
during a restore.
Note: When you apply the Traverse Directory Junctions and Volume Mount Points and
Backup Mount Points as Part of the volume that they are mounted on options to named,
mounted volumes that contain virtual hard disks (VHDs), Arcserve Backup creates
separate backup sessions for mounted volumes that contain VHDs.
Example: Mounted Volumes that Contain VHDs
A server contains physical disk (C:\) that contains VHDs D:\ and E:\. VHD files (D.vhd and
E.vhd) that reside in C:\ are mounted as drive D:\ and drive E:\. Drive D:\ is mounted to
C:\MountD, and drive E:\ is mounted to C:\MountE.
If you back up C:\MountD and specify the Traverse Directory Junctions and Volume
Mount Points option, and the Backup Mount Points as Part of the volume that they are
mounted option is enabled or disabled, Arcserve Backup creates separate backup
sessions for drive D:\ and C:\MountD.
Do not apply Scheduled Job Method or Rotation Phase to Microsoft SQL Server
databases--Lets you exclude the backup method specified on the Backup Manager,
Schedule tab. With this option specified, Arcserve Backup behaves as follows:
Arcserve Backup ignores the custom schedule, rotation, and GFS rotation
method that was specified for the job.
Arcserve Backup converts the backup method specified on the Schedule tab to
Full backup, only if the logic for database level backups and global backup
options requires the backup method specified on the Schedule tab.
Note: For more information about backing up and restoring Microsoft SQL Server
databases, see the Agent for Microsoft SQL Server Guide.
Enable Point in Time Restore (PIT Restore)--With this option specified, Arcserve
Backup executes point in time, incremental backups on all daily backup executions
except for the days that full backups are scheduled to execute. You can specify the
point in time restore option to all scheduled jobs that apply to Arcserve Backup file
system agents.
For jobs with this option specified, Point in Time Incremental appears as the Backup
Method in the Activity Log and as the Session Method in the Restore by Session
window. However, in the Backup Manager window, the Backup Method appears as
Incremental.
Important! The Enable Point in Time Restore option applies to only synthetic full
backup jobs.
If you specify encryption and compression options, and the backup destination is a
drive that does not support compression, Arcserve Backup encrypts the backup
data and does not compress the backup data.
The following options define how Arcserve Backup processes backup data during a
backup job and during the migration phase of a staging backup job.
Session/Encryption Password
Merge and Scan operations where the encryption, compression, or both were
processed at the backup server. (You do not need to specify the password to
perform Merge and Scan operations where the encryption, compression, or
both operations were processed at the agent.)
Note: The Session/Encryption password is not required when you Merge or
Scan only the session headers.
Encryption/Compression methods
Encrypt data--Use this option to encrypt the backup data. You can specify one of
the following options:
At agent--Select this option to encrypt the backup data prior to the actual
backup process. For more information about this option, see Data Encryption
at the Agent Server (see page 113).
At backup server during backup--Select this option to encrypt the backup data
at the backup server during the backup process. For more information, see
Data Encryption During Backup (see page 114).
If you encrypt data during the backup phase, Arcserve Backup will not encrypt the
data again during the migration phase of the staging backup operation.
Compress data--Use this option to compress the backup data. You can specify one
of the following options:
At agent--Select this option to compress the backup data on the system where
the agent is installed and running.
Note: Arcserve Backup does not support data compression at the agent system
when the backup source consists of UNIX, Oracle RMAN data.
You must specify either Encrypt data at backup server during backup or
Encrypt data at backup server during migration to enable compression at
backup server.
With the Compress data, At backup server options specified, and the
Encrypt data at backup server during backup option, or the Encrypt data at
backup server during migration option specified, Arcserve Backup uses
software compression to compress the data at the backup server before
the data is encrypted at the backup server.
If the storage device associated with the job does not support hardware
compression, Arcserve Backup ignores the setting Compress data, At
backup server.
2.
b.
Check Encrypt data and select at Backup Server during migration option
c.
3.
Click OK.
The encryption and compression options are applied.
Use VSS--Directs Arcserve Backup to use VSS to handle the backup of open files.
If this check box is not selected, VSS support is not used and the Arcserve Backup
Agent for Open Files (if available) is used to handle open files. If the Arcserve
Backup Agent for Open Files is not available and Use VSS is not selected, a
traditional backup is performed. However, the backup will be incomplete if there
are any open files that cannot be backed up.
If the Agent for Open Files is installed and licensed on the source computer,
Arcserve Backup uses the agent to handle open files when this option is
specified and the VSS backup fails.
If the Agent for Open Files is not installed or not licensed on the source
computer, Arcserve Backup processes VSS backups as traditional backups,
regardless of whether this option is specified.
The Writers and Components group box lets you specify how you want Arcserve Backup
to treat Writers and Components. These global options affect all Writers, except for
those with Writer-specific options in place. For more information about setting
Writer-specific options, see the Microsoft Volume Shadow Copy Service Guide.
Files included by a writer will be excluded from file system backups--Prevents files
that belong to a Component from being backed up by a traditional file system
backup. This option offers the following advantages:
By excluding files from traditional backups, fewer files are processed, and
traditional backups take less time to complete.
Files excluded by a writer will be excluded from file system backups--Prevents files
that have been excluded from being backed up by a Component from being backed
up by a traditional file system backup.
There may be files associated with an application that should never be backed up
(for example, the Windows page file). Each Writer is aware of whether its
associated application maintains any such files. Selecting this option allows
Arcserve Backup to use this information when performing traditional backups.
If a component file fails to backup the writer, the backup will terminate--Cancels
the backup of a Writer if the backup of any of the Components fail. The backup of a
Component fails if one or more of its files cannot be successfully backed up.
Selecting this option ensures that any backup is consistent and that all of the files
associated with a Writer are backed up before the backup is considered successful,
regardless of how many components are associated with the Writer.
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 Backup 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 Backup
checks to see if the media in the drive is the one specified for the job. If it is not,
Arcserve Backup checks to see if the media is blank. If the media is not blank either,
Arcserve Backup reformats whatever media it finds in the device and starts backing
up files at the beginning of the media.
The deduplication device does not support Overwrite Same Media Name. The
backup job will always append to the deduplication device even if Overwrite Same
Media Name, or Blank Media or Overwrite Same Media Name, or Blank Media
First, then Any Media is selected.
Arcserve Backup ignores the First Backup Media options that you specified when
the Append days option is specified as a custom job option. For more information,
see Repeat Method Options.
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 Backup remembers the name and ID of the job's first media. When the job
requires additional media, Arcserve Backup 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 Backup reformats the media, giving it the same name and ID as the first
media. The sequence number changes.
Note: To overwrite media based on its name only, select the Distinguish Media by
Name Only option.
Overwrite Same Media Name, or Blank Media First, then Any Media--Overwrites
any media found in the device (as long as it has a different ID from the first media's
ID). If neither of these conditions are met, Arcserve Backup reformats whatever
media it finds in the drive and starts backing up files at the beginning of the media.
All subsequent media are reformatted with the same name and ID as the first
media. Only the sequence number changes.
Note: To overwrite media based on its name only, select the Distinguish Media by
Name Only option.
Scan Backup Media Contents--Check the proprietary Arcserve Backup data area
(the header) of each file on the backup media. If it is readable, Arcserve Backup
assumes the data is reliable. If it is not readable, the Activity Log is updated with
this information. This is the fastest verification method.
If you selected Calculate and Store CRC Value on Backup Media on the Operation
tab, Arcserve Backup automatically performs CRC verification. This method assigns
a value to the data that you copied to media and compares it to the value assigned
to the data that you backed up. This enables you to identify the individual data
packets that were backed up.
Compare Backup Media to Disk--Data from the backup media is read and
compared byte for byte against the source files. This option takes time, but ensures
that all data on the backup media are exactly as on the disk. If Arcserve Backup
finds a mismatch, the errors are recorded in the Activity Log.
Catalog files--This option allows you to back up the related Arcserve Backup
database catalog files when the backup job is complete.
Job scripts--This options allows you to back up the related job scripts when the
backup job is complete.
SQL Server Disaster Recovery Elements for the Arcserve Backup Database--This
option ensures that the elements required to recover a SQL Server database from a
disaster are backed up after jobs are complete.
Operation Options
The following options affect only backup operations.
If you are in a Novell server environment and you select Disable File Estimate
from the Operations tab of the Global Options dialog, when you look at the
View Job Queue/Statistics window from the back-end, there is no status bar at
the bottom of the window.
Calculate and Store CRC Value on Backup Media--Calculating and storing the CRC
value on the backup media will enable Arcserve Backup to perform CRC verification
during the backup job. To instruct Arcserve Backup to use the CRC value stored on
media, see the Backup Options, Verification tab.
Delete Source Files After Backup to Media (use with caution)--This argument
deletes the files from the hard disk after the file backup is completed. Select this
option if you want to delete source files from the source machine after they have
been backed up to media. This option deletes only the files from the specified
unprotected folder. It does not delete the empty folder itself.
You can use this option to perform disk grooming. For example, if you set up a
backup job with a filter to back up files that haven't been accessed for a certain
period of time, you could then include this option to delete those files from the
source disk.
Be aware of the considerations that follow:
On Windows computers, protected system files and files that are excluded
from the backup by other filters are not deleted. For a remote backup job or a
64-bit operating system local backup job or a Windows Server 2008 local
backup, the Windows Client Agent backs up the files. After the backup, this
option deletes only the files from the specified unprotected folder. It does not
delete the empty folder itself. Boot files, however, are not protected and can
be deleted.
On Linux/UNIX and Mac computers, all files that are backed up are deleted,
except for those in protected directories, such as /bin, /etc, and /lib. To
designate additional directories as protected, add them to the groom.cntl file
on the client agent machine.
Note: As a best practice, you should specify Verification options when using Delete
Source Files After Backup to Media. With verification options, Arcserve Backup
compares the source files to the backup data to ensure that backup data is identical
to the source data. For more information, see Backup Manager Verification Options
(see page 166).
Preserve File Access Time (Used for Windows file system only)--This option directs
Arcserve Backup to preserve the last access time of files when a backup is
performed.
Note: The Access Time of a file is automatically updated by the operating system
whenever a file is accessed (read or write). However, after a compare is performed,
the Access Times of all the backed up files are also updated. Therefore, if you want
to track whether or not a file has actually been accessed (and not just compared),
you need to preserve the original access time.
If this option is not selected (no check in box), the last file access time of any
files that are backed up is updated to the new value that is present when the
backup is completed. This is the default setting.
If this option is selected (check in box), Arcserve Backup preserves the last file
access time of any files that are backed as the original value that was present
before the backup was performed.
Note: For UNIX based agents, you must apply this option locally. For more
information, see Local Backup Options for UNIX Agents (see page 152).
Reset Archive bit for backup to deduplication device--Select this option for custom
backup jobs in which optimization is enabled to reset the archive bit on all files
included in the job after the job completes. Optimization deduplicates only files
that have changed since the last backup job, indicated by archive bits with a value
of 1. Archive bits must be reset back to 0 so that subsequent backup jobs in which
optimization is enabled can deduplicate only changed files. If you do not select this
option with optimization-enabled jobs, files that have not changed since the
previous backup could be included in subsequent jobs, resulting in significant
performance reductions.
Back up deduplication device data--Select this option if you want to forcibly include
deduplication device files (index, reference and data files) in the backup job. These
files are normally skipped in local backups. If you select this option, you should also
enable the Use VSS option and disable the Revert to traditional backup if VSS fails
option, both on the Volume Shadow Copy Service tab. If you forget to enable the
Use VSS option and disable the Revert to traditional backup if VSS fails option, then
the backup job automatically enables this option when the backup job runs.
Use Default Device Setting--Select this if you want to use the setting you
selected during library configuration.
Eject Media--Select this if you want to eject media from the drive after the job
finishes. This helps prevent any other job from overwriting information on this
media. If you select this, it overrides the setting you selected during library
configuration.
Do not Eject Media--Select this if you do not want to eject media from the
drive after the job finishes. If you select this, it overrides the setting you
selected during library configuration.
Note: For more information on library configuration, see Tape Cleaning and
Changing Configuration Details.
File system backups--If the backup job requiring a makeup job consists of
file system backups, and the file system contains directories that reside in
different volumes, the makeup job backs up only the failed volumes or
directories. The makeup job does not back up the entire file system if it
contained successful volume or directory backups.
Child jobs--The child makeup jobs (makeup of makeup jobs) run based on
the value specified for After Job Finishes.
Microsoft SQL Server backups--If the backup job requiring a makeup job
consists of Microsoft SQL Server instance backups, the makeup job backs
up only the failed databases. The makeup job does not back up the entire
instance if it contained successful database backups.
More information:
Local Backup Options for UNIX and Linux Agents (see page 152)
You can use the Pre option to stop the application that owns the data you are about
to back up, and then use the Post option to restart the application after the backup
is complete.
You can use the Pre option to defragment a disk before a backup job starts.
You can use the Post option to delete files from a disk after that backup is
complete.
Be aware of the following behavior when using Pre and Post options:
Arcserve Backup does not support running commands with executables that reside
on remote systems.
Using a Pre option and specifying an exit code prevents the backup operation from
starting until after the Pre option process is complete.
Using a Pre option and specifying an exit code and the Skip Operation option causes
Arcserve Backup to skip the backup operation and, if specified, prevents the Post
option process from starting.
Post option processes start unless the following conditions are present:
An exit code is specified, the Skip Post Application option is specified, and the
result exit code is equal to the exit code specified.
The result of the backup operation is equal to the value specified for the Do not
run Command if option.
Pre and Post options specified as global options run commands before a job starts
or after a job finishes. Pre and Post options specified as node-level (local) options
run commands before a node is backed up or after a node is backed up.
For example, a user submits a backup job consisting of nodes A and B. A Pre option
is specified as a global option and a Pre option is specified for node B. Immediately
before the job runs, the global Pre option executes. While the job is running, the
Pre option specified for node B executes before node B is backed up.
On Exit Code--Arcserve Backup detects exit codes of other programs. You can
specify the following options for a particular exit code:
Run Job Immediately--The job runs immediately if the selected exit code is
returned.
Skip Job--The job does not run if the appropriate exit code is detected.
Skip Post Application--Skip any commands specified to run after the job if
the appropriate code is detected.
Agent Options/Database Level Options--These are agent backup options and apply
to only the selected database. They can either extend or override the Global Agent
options. Access Database Level Options by right-clicking the database object and
selecting Agent Option from the shortcut menu.
Global Options/Agent Options--These options let you specify default job options
for all selected objects in the Agent type. Global Agent Options are not supported
by releases of the Agent prior to r12.5. Access Global Agent Options from the Agent
Options tab of the Global Options dialog.
Global Agent Options applied at a global level let you specify default job options for all
databases for the Agent selected. Options selected for a specific object at the database
level can either extend or override the options specified as a global option. As a general
rule, options applied at the global level will extend or override options that you specify
on the Job Schedule tab.
Certain options are available from only one Agent Option dialog; they are noted.
Note: The agent combines options that you specify at the database level for a specific
database with the appropriate global agent options.
You can specify Global Agent Options for the Arcserve Backup components that follow:
Agent for Microsoft SQL Server (see page 174)--Includes the Agent for Arcserve
Backup Database, which is supported by Arcserve Backup Agent for Microsoft SQL
Server, r12.5 and later.
Agent for Virtual Machines--Supported by the Arcserve Backup Agent for Virtual
Machines, r12.5 and later.
Agent for Microsoft Exchange Server (see page 183) - Includes Microsoft Exchange
Server Database Level and Document Level options.
Consider the behavior that follows when packaging jobs using the above-described
agents:
Global agent options are not supported by releases of the above-described agents
prior to Arcserve Backup r12.5, nor are they applied if you use any other agent to
back up Microsoft SQL or Exchange Server databases.
When you upgrade an older agent to Arcserve Backup r12.5 or later, the agent
applies both any pre-existing local options and all global options that apply and do
not conflict with the database level (local) options.
For jobs packaged using older agents, local options are carried over as local options.
The Full job method will result in a Full backup of the database.
The Differential job method will result in a Differential backup of the database,
unless this database has not yet had a Full backup.
The Incremental job method will result in a Transaction Log backup With
Truncation for databases using the Full and Bulk-Logged Recovery Models, and
a Differential backup of databases using the Simple Recovery Model, unless this
database has not yet had a Full backup.
The three main System databases are exempt from the Job Method and from
the Backup Method in the Global Agent Options; selecting this option for
databases master, model, or msdb will always result in a Full backup.
Full--A Full backup is performed. All files included in the Database Subset selected
will be backed up in their entirety.
Differential--Backs up only data that has changed since the last Full backup. For
example, if you ran a complete backup of your database on Sunday night, you can
run a differential backup on Monday night to back up only the data that changed on
Monday.
Note: When selected in the Global Agent Options, this option is ignored by system
databases. Databases that have not received a Database Full Backup will revert to a
Full Backup.
Back up Transaction Log After Database--Backs up only the Transaction log. This
option is only available for databases using the Full and Bulk-Logged Recovery
Models. For databases using the Simple Recovery Model, Arcserve Backup performs
a Differential backup when you select Transaction Log Only from the Global Agent
Options tab.
Note: When selected in the Global Agents Options, this option is ignored by system
databases. Databases that have not received a Database Full Backup will revert to a
Full Backup.
The backup method selected on the Global Agent Options tab overrides the selection
made in a job's global backup method or rotation phase in the Job Scheduler. If you
select the backup method using the Global Agent Options tab, note the following:
The three system databases (master, model, and msdb) are exempt from the
Backup Method in the Global Agent Options tab.
For databases that have not yet received a Database Full backup, Arcserve Backup
ignores the backup method set in the Global Agent Options tab and performs a full
backup by default.
For databases using the Simple Recovery Model, Arcserve Backup performs a
Differential backup when you choose Transaction Log Only on the Global Agent
Options tab.
Because any selection other than Use Global or Rotation Method for a database
overrides the selection in the Global Agent Options dialog, the Backup Method is not
affected by the Override Global Options setting on the database's Agent Options
(database level) dialog.
Database Subset
Database Subset options let you define the types of database components that you
want to back up. You can use this option to choose between the entire database, or a
selection of files and FileGroups contained within the database, when the size of the
database and performance requirements do not allow you to back up the entire
database.
Database Subset options are disabled if the selected Backup Method for a database is
Transaction Log Only.
Important! Of the following Database Subset options, only the Back up Transaction Log
After Database option is available on the Global Options/Agent Options dialog.
Files and FileGroups--Backs up selected files in a database. Use this option to back
up a file or FileGroup when the database size and performance requirements make
it impractical to perform a full database backup. This option is only available for
databases using the Full and Bulk-Logged Recovery Models.
Note: For Microsoft SQL Server 7.0 databases, Arcserve Backup performs a Files and
FileGroups Full backup if you set the database subset to Files and FileGroups for the
database level and backup method to Differential on the Global Agent Options tab.
Back up Transaction Log After Database--Backs up the Transaction Log after the
database, partial database, or selected set of data files is backed up. This allows you
to perform a Full backup or Differential backup and a Transaction Log backup in the
same job. This option is only available for databases using the Full and Bulk-Logged
Recovery Models and is ignored for databases using the Simple Recovery Model if
set in the Global Agent Options dialog.
Be aware of the following behavior:
If you select this option on the Global Options/Agent Options tab and specify
Incremental backup method using the Job Scheduler, Arcserve Backup
performs only one transaction log backup on the database and uses the
Transaction Log Truncation Options from the Global Agent Options tab instead
of the Incremental backup's default behavior (truncate the transaction log).
If you select this option using the Database Level Agent options, set the backup
method at the database level to Use Global or Rotation, and set the backup
method in the Global Agent Options to Transaction Log Only, Arcserve Backup
performs only one transaction log backup on the database and uses the
Transaction Log Truncation Options set from the database level.
If you select this option in the Global Agent Options dialog and specify
Transaction Log Only in Database Level Options, this option and the
accompanying global Log Truncation Options setting is ignored for that
database.
Do not remove inactive entries from transaction log, after backup--(No truncation)
Retains backed up log entries after backup. These entries will be included in the
next Transaction log backup.
Back up only the log tail and leave the database in unrecovered mode--(No
recovery) Backs up the log and leaves the database in a restoring state. This option
is available for Microsoft SQL Server 2000 or later. Use this option to capture
activity since the last backup and take the database offline prior to restoring or
repairing it.
The Log Truncation Options are available only when the selected Backup Method is
Transaction Log, or when the Backup Transaction Log After Database option is
checked.
Important! Do not use the "Backup only the log tail and leave the database in
unrecovered mode" log truncation option to back up the ARCserve Database.
Performing a backup with this option causes the database to be placed in an offline
status, and you can lose the ability to find the backups of the ARCserve Database in
order to perform a restore and bring the database online. If you perform a backup
of the ARCserve Database using this option, you can use ARCserve Database
Recovery Wizard to recover the Arcserve Backup database and bring it back online.
Log Truncation Options are not affected by the Override Global Options setting on the
Database Level Agent Options dialog. If Transaction Log or Backup Transaction Log After
Database is selected for the database, the database Log Truncation Options are used.
Check only the physical consistency of the database--Detects torn pages and
common hardware failures, but does not check the data against the rules of the
database schema. It still checks the integrity of the physical structure of the page
and record headers, and the consistency between the pages object ID and index ID.
This option is available for Microsoft SQL Server 2000 or later. If this option is
selected from the Global Agent Options tab, it is ignored for SQL Server 7.0
databases.
All error messages that are generated during the DBCC are recorded in the Agent for
Microsoft SQL Server log file called sqlpagw.log. The log is located in the Backup Agent
directory.
Example: How DBCC Options Work
The following example illustrates how DBCC options work in conjunction with Override
Global Options on the Agent Backup Options dialog.
With Override Global Options specified, the DBCC options selected at the database
level will be the only DBCC options specified.
With Override Global Options not specified, all of the DBCC options specified for the
database and all of the DBCC options selected in the Global options will be applied
together.
On the Global Options/Agent Options tab, the Database Consistency Check options that
follow are specified:
After backup
On the Agent Backup Options dialog, Override Global Options is not selected and the
Database Consistency Check options that follow are specified:
Before backup
Note: To open the Agent Backup Options dialog, open the Backup Manager, click the
Source tab, browse to and expand the Arcserve Backup server, right-click the Arcserve
Backup database, and then select Agent Option from the pop-up menu.
When you submit the backup job, Arcserve Backup applies the DBCC options specified in
logical order: Perform the DBCC before the backup starts. If the DBCC fails, perform the
backup. After the backup is complete, do not check the indexes.
Other Options
From the Global Agent Options tab, you can specify the following additional options:
SQL Native Backup Compression--This option applies to only SQL Server 2008
(Enterprise) and later versions. If enabled, this option directs Arcserve Backup to
use SQL Server database backup compression settings, resulting in faster backup
times and smaller sessions.
From the local Agent Option dialog, you can choose to Override Global Options. This
setting lets you choose a backup method and database consistency check that applies to
only the database selected for this job.
File Mode--Lets you protect individual files and directories. File mode backup
lets you perform the tasks that follow:
Note: The elapsed time required to perform a file level backup of a full VM is
greater than the elapsed time required to perform a raw (full VM) level backup
of the same volume.
Raw Mode--Lets you protect entire systems for disaster recovery. Raw mode
backup lets you perform the tasks that follow:
Note: Raw mode does not let you restore data at file level granularity or filter
raw (full VM) data. Filters applied to raw mode (full VM) backups are ignored at
runtime.
Mixed Mode--Mixed mode is the default backup mode. Mixed mode lets you
perform the tasks that follow:
Perform GFS and rotation backup jobs that consist of weekly full backups
in full VM (raw) mode and daily incremental and differential backups in file
mode in a single backup job.
Note: Rotation and GFS rotation jobs are advantageous in that they contain
backup data that provides you with daily protection (file level backups) and
disaster recovery protection (raw, full VM backups) in a single backup job.
Allow file level restore--Lets you back up data using Raw Mode efficiency and
restore data with File level granularity. To perform granular file level restores
from raw (full VM) backups, you must specify the name of the Arcserve Backup
server on your VMs. For more information, see Specify the Name of the
Arcserve Backup Server.
Allow file level restore lets you perform the tasks that follow:
Restore data at file level granularity from Raw Mode (full VM) backups.
With the Allow file level restore option, Arcserve Backup demonstrates the
following behavior:
You can use the Allow file level restore option with all types of backups, including
custom backups, rotation backups, and GFS rotations that consist of full,
incremental, and differential backups. The full backups are captured in raw (full VM)
mode and the incremental and differential backups are captured in file level backup
mode. If you do not specify Allow file level restore, Arcserve Backup restores only
the incremental and differential backups. The full backup, which is captured in Raw
mode, is not included with the restore.
SAN--(Storage Area Network) This option lets you transfer backup data from
proxy systems connected to the SAN to storage devices using Fibre Channel
communication.
HOTADD--This option lets you back up virtual machines configured with SCSI
disks.
NBDSSL--(Network Block Device Secure Sockets Layer) This option lets you use
the Network File Copy (NFC) protocol to communicate. NBDSSL transfers
encrypted data using TCP/IP communication networks.
Note: If the specified transport mode is not available, the transport mode defaults
back to the Dynamic option.
Incremental / Differential Method for VMware VM Options
Lets you specify the communication method that Arcserve Backup will use to
transfer incremental and differential backup data on VMware VMs to the backup
proxy system.
Use VDDK--Lets Arcserve Backup use VMware Virtual Disk Development Kit to
transfer incremental and differential backup data to backup proxy systems. Use
this option when you want to reduce the load on your network.
Note: Use VDDK is the default setting.
Use Client Agent--Lets Arcserve Backup use Client Agent for Windows
communication to transfer incremental and differential backup data to backup
proxy systems. With this option specified, Arcserve Backup transfers data via
your network.
Copy backup--This option also backs up the entire database but does not purge log
files.
Incremental backup--This option backs up only the changes that have occurred
since the last backup, regardless of backup method.
Differential backup--This option backs up only the changes that have occurred since
the last full backup.
Back up from replica--This is the default setting and activates the Database
Availability Group options. If you choose to back up from a replica, you may
enable the option, Back up from active if there is no healthy replica available.
First Preferred
Last preferred
Incremental backup--This option backs up only the changes that have occurred
since the last backup, regardless of backup method.
Differential backup--This option backs up only the changes that have occurred since
the last full backup.
Log all activity--Record all of the activity that occurs while the job is running in the
Job Log.
Note: When you specify Log all activity, Arcserve Backup creates a log file named
JobLog_<Job ID>_<Job Name>.Log. With this log file, you can view detailed logging
information about the job. Arcserve Backup stores the log files in the following
directory:
C\Program Files\CA\ARCserve Backup\LOG
Log disabled--Do not record any information about this job in the Job Log.
386SPART.PAR
386SPART.TMP
SPART.PAR
WIN386.SWP
PAGEFILE.SYS
NETLOGON.CHG
NTUSER.DAT.LOG
CPL.CFG
EA DATA.SF
RDS.BAK
RDS.LOG
The above registry key is controlled by the Arcserve Universal Agent. The Arcserve
Universal Agent service runs under the Local System account. As a result, Arcserve
Backup will back up the files specified under FilesNotToBackup for the Windows
Administrator account. If you do not want to back up the files specified under the
Windows Administrator account, you must exclude the files explicitly under the
above registry key. Alternately, you can modify the Arcserve Universal Agent service
to run as the specific Windows Administrator account. To allow the Arcserve
Universal Agent service to run as the specific Windows Administrator account, do
the following:
1.
From the Control Panel, choose Administrative Tools and then choose Services.
2.
Click the Arcserve Universal Agent service from the Services list.
3.
4.
5.
On the Log On tab of the Properties dialog, click This Account and provide the
required credentials.
6.
Click OK.
7.
Files with the extensions *.ALT and *.LOG that are located in the paths listed in the
following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\hivelist
Cluster installation directory files (typically, the WINNT\cluster folder), files with no
extensions, and files with the extension *.LOG
\RECYCLER folder
If database agents are installed, all files backed up by the agents are skipped.
Database folders in the Arcserve Backup home directory are skipped during regular
file backup operations.
Agent for Oracle, Agent for SAP R/3 (r12.1 and earlier versions)
*.dbf
Control*.*
Red*.log
Arc*.001
*.nsf
*.ntf
Mail.box
*.000
2.
*.ldf
*.mdf
*.ndf
*.chk
*.log
Res1.log
Res2.log
*.edb
*.stm
*.dbf
Control*.*
Red*.log
Arc*.001
2.
2.
From the Source directory tree, select the system that you want to manage
remotely.
3.
If this server has the BAOF Engine installed, right-click the computer and select the
following menu items or simply click these items in the Additional Information
pane, on the bottom-right of the screen:
Configure Open File Agent--This displays the BAOF Configuration screen. From
here, you can set various global settings for BAOF on the selected computer.
Note: For more information about the General, File/Group, and Clients options,
see the Agent for Open Files Guide.
4.
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.
Click OK.
You have successfully applied the open file settings.
Multiplexing media (multiplexing media appear with a blue circle with an M next to
them)
Blank media
Media pool
Note: You cannot submit a multiplexing job to a tape library that has WORM media
unless you use the Virtual Library option to split the tape library into groups so that one
has WORM media and the other does not. If you do this, you can submit a multiplexing
job to the group that does not have WORM media. For more information about the
Virtual Library option, see Virtual Library Configuration Option.
More information:
Virtual Library Configuration Option (see page 380)
Open the Backup Manager window and select the Destination tab.
Note: If the job is a staging backup, click the Staging Location tab.
2.
3.
After you double-click the parent job, the child jobs appear in the Job Monitor screen as
illustrated by the following screen:
In addition, the status of the parent job is the highest severity status of a child job. For
example, if Child 1 is successful, Child 2 is incomplete, and Child 3 has failed, the parent
job will denote a FAILED status.
Location
HKEY_LOCAL_MACHINE\Software\Computer Associates\Arcserve
Backup\Base\task\backup
Value
Open the Backup Manager window and select the Destination tab.
2.
Note: If a backup job with multistreaming spawns child jobs, the actual number of
streams spawned will not exceed the number of streams specified for the job. However,
if a job spawns child jobs and you do not specify a number of streams to use, the child
jobs will be created and backed up in one continuous stream.
You can direct Arcserve Backup to back up a selected node and all of its contents
with a single click in the Backup Manager directory tree. Arcserve Backup backs up
all file systems, databases, and drives in the directory tree when you specify the
node.
You can create a single backup job for the entire node. Tracking several to many
backup jobs on a single node can become a difficult and time consuming
maintenance task.
You can modify the node without having to modify preconfigured backup jobs. For
example, if you add a drive to the node, Arcserve Backup detects the new drive
automatically and backs up the entire node when you run the backup job.
Set or change the User Name and Password for the database item selected in the
Security and Agent Information dialog.
2.
From the Source directory tree, select the node that you want to back up and click
Submit on the toolbar to submit the job.
If the node contains database files, the Security and Agent Information dialog opens
to display a list of all databases on the node, User Names, and Passwords.
Important! Client Agent Password Security is only supported for the Client Agent
for Windows, including the Agent for Open Files and VSS Writers. If Password
Security is enabled and any database, application, or messaging agent is installed on
the same machine as the Client Agent, whole node backup is not supported. System
Security is the default setting. If you have enabled Password Security on the primary
or stand-alone server, the automatically-generated Database Protection Job will fail
for the job queue and the Catalog Database. You must not enable Password
Security in the Agent Configuration on any machine running a database, application,
or messaging Agent before submitting the job.
3.
Optionally, to set or change a User Name or Password, click the Security button.
Enter the appropriate User Name and Password and click OK.
In the Security dialog, you must specify User Name and Password with backup
rights on that machine. For example, Administrator or root.
Note: Arcserve Backup does not support logging in to systems with passwords that
are greater than 23 characters. If the password on the system you are attempting to
log in to is greater than 23 characters, you must modify the password on the agent
system such that it is 23 characters or less, and then you can log in to the agent
system.
4.
Click OK.
The Submit dialog opens.
5.
Complete the fields are required for the job and click OK.
The backup job for the entire node is submitted.
More information:
Submit a Backup Job (see page 136)
Open the Backup Manager window by clicking Backup in the Quick Start menu.
The Backup Manager window opens and the Start, Source, Schedule, and
Destination tabs appear.
2.
3.
4.
From the Source tab, browse to and select the files you want to back up.
5.
6.
Select Use Rotation Scheme to use one of the pre-designed backup schemes.
You can choose a five or seven day schedule using incremental, differential, or
full backups.
To modify a rotation scheme, highlight the day you want to change and click
the Modify button.
For example, you might want to change a routine to initiate a full backup on
Saturday.
Make the necessary modification to your schedule, and click OK.
Use the calendar to review the backup plan you selected. Click the Calendar
View tab to see a calendar view of your rotation scheme.
You can also make or view changes to your backup schedule by clicking the
Exceptions tab. To make additional exceptions to your schedule, click the Add
button to open the Exceptions dialog. Click the Date drop-down menu to open
a calendar from which you can select the date you want to change.
8.
From the Destination tab, specify the (media) group where you want to back up
your data.
(Optional) In the Media Pool Used field, enter the name of the media pool that you
want to use for the rotation.
9.
When you are finished, click Submit on the toolbar to submit the job.
From the Backup Manager, select the Windows Systems object. Right-click, and
select Add Machine/Object from the pop-up menu.
The Add Agent dialog opens.
Note: Alternatively, you can add servers using the Add/Import/Export Nodes
method. For more information, see Add, Import, and Export Nodes Using the User
Interface (see page 334).
a
2.
Enter the host name of the remote server in the Host Name field.
Note: Arcserve Backup server names and Arcserve Backup domain names cannot
exceed 15 bytes. A name totaling 15 bytes equates to approximately 7 to 15
characters.
Check the Use Computer Name Resolution check box or specify the IP address of
the computer. Click Add to include the remote server for backup, and click Close.
Note: Arcserve Backup lets you treat the backup of multiple servers as one job. If
you choose this method, Arcserve Backup automatically submits the tasks in the job
queue as one job and backs up the servers one after the other. Alternatively, you
can select the Schedule tab and specify when each job should run to have Arcserve
Backup back up each machine as a separate job.
3.
Select the remote machine, and click the + to the left of it. The Security dialog
appears, prompting you for security and agent information.
Enter your user name and password. You must supply this information to verify that
you have sufficient rights to browse the machine and perform a backup. Click OK.
Note: Arcserve Backup does not support logging in to systems with passwords that
are greater than 23 characters. If the password on the system you are attempting to
log in to is greater than 23 characters, you must modify the password on the agent
system such that it is 23 characters or less, and then you can log in to the agent
system.
4.
5.
Choose the sources and a destination for each machine you want to include in the
backup.
Before you click Submit to submit the backup job, you can set up an Alert to send
you notification after the job runs.
2.
3.
b.
Right-click the computer and click Enable Static Backup on the pop-up menu.
The Static Backup option is applied to the computer, as illustrated by the following
screen:
Note: The Static Backup option remains applied to the specified computer until you
disable this option. You can repeat this step to disable the Enable Static Backup
option.
4.
Click the Schedule tab and specify the schedule that you want to use for the backup
job.
Note: For more information, see Rotation Schemes (see page 307) and Custom
Schedules (see page 318).
5.
6.
Specify the group that you want to use to store the backup data.
The storage group is applied.
7.
8.
9.
The disk staging method utilizes a disk as the staging area and is commonly referred
to as Backup to Disk to Tape (D2D2T).
The tape staging method utilizes a tape library or a virtual tape library as the staging
area and is commonly referred to as Backup to Tape to Tape (D2T2T).
Each staging method contains specific options to control the behavior of Arcserve
Backup during the backup process.
Backup Process--Arcserve Backup backs up data from the source to the staging
location. The staging location is a file system device (FSD).
Copy Process--Arcserve Backup copies or migrates the backup data from the staging
location to the final destination media. The final destination is usually tape media,
but can be another FSD.
Note: When you back up data from a disk staging location to the final destination,
you are then able to perform a Double Tape Copy. Double Tape Copy lets you
migrate (copy) the data to two destinations simultaneously. Using this feature
writes to the destinations in parallel to save time.
To ensure that the migration job continues when one of the devices become
unavailable, you can set a timeout value for additional backup media to continue
the migration job in another device. If you do not set a timeout value, then the data
migration job fails after the first backup media timeout completes. For more details
about setting the timeout value, see Backup Manager Backup Media Options (see
page 164).
Note: Arcserve Backup lets you transmit up to 32 streams of data using multistreaming.
To back up data using multiple streams and transmit more than two streams of backup
data, you must license the Arcserve Backup Enterprise Module (see page 39).
Using disk staging you can back up data to file system devices (FSD) that are used as
a temporary staging area. A staging job can divide your backup job into several
subjobs that run simultaneously. Disk staging lets you use simultaneous streaming
to send multiple streams of data to the FSD. Since the data is split among several
different streams, backup jobs with simultaneous streaming enabled can be
completed significantly faster than regular backup jobs.
You can then migrate (copy) the data from the FSD to a final storage media (or from
disk to tape). As a result, the tape drive can be kept streaming, thereby minimizing
the shoeshine effect (starting, stopping, and repositioning the tape), and increasing
both the life expectancy and efficiency of the tape drive. While the backup image is
still on the FSD, data can be restored directly from the FSD. The restore time is
significantly reduced because restoring data from disk is generally faster than
restoring from a tape (no delays due to tape load and seek latency).
Note: When you back up data from a disk staging location to the final destination,
you are then able to perform a Double Tape Copy. Double Tape Copy lets you
migrate (copy) the data to two destinations simultaneously which writes to the
destinations in parallel to save time. To use this feature, it is required to configure a
Disk Staging device to your environment. See Device Configuration (see page 383)
for more details.
To ensure that the migration job continues when one of the devices become
unavailable, you can set a timeout value for additional backup media to continue
the migration job in another device. If you do not set a timeout value, then the data
migration job fails after the first backup media timeout completes. For more details
about setting the timeout value, see Backup Manager Backup Media Options (see
page 164).
During the backup-to-FSD process, if the FSD gets full or reaches the specified
maximum threshold, Arcserve Backup lets you create makeup jobs which would
then back up the data directly to the final destination after the staging backup job
fails. This increases the success rate of backups. In addition, if there are any errors
during the copy-to-final destination process, Arcserve Backup lets you create
makeup jobs.
Note: Under disk full conditions, the makeup job created to back up the data to
tape will always try to use a blank tape or a media from a scratch set. It will never
try to append to an existing media.
The backup images are kept on the FSD until the retention time expires (as
determined by the specified purge policy). At that time, Arcserve Backup
automatically purges the data from the FSD, and reclaims disk space so that
backups can continue.
For rotation jobs or GFS rotation jobs, Arcserve Backup lets you specify policies that
disable staging for any particular day. This feature is helpful in situations where the
FSD is full, is scheduled for maintenance, or has a problem.
More information:
How to Use Tape Staging to Manage Backup Operations (see page 232)
Ensures that Arcserve Backup does not use the full capacity of a disk--A backup job
will fail when writing to a file system device if the total disk space used exceeds the
maximum threshold.
Important! File System Devices (FSD) that are part of a staging group cannot be
erased or formatted using the corresponding utility from the Device Manager
window. To prevent accidental erasing or formatting of an FSD prior to the staged
data being migrated to a final destination media, the Erase and Format toolbar
buttons on the Device Manager window are disabled. If you want to erase or format
the FSD, you can either use the command line (ca_devmgr) or disable the staging
option for the selected FSD.
Increases your overall backup success rate--You can define staging policies that let
you create makeup jobs that back up directly to tape if an exceeds maximum
threshold condition occurs or to create a makeup job on hold if a data migration
failure occurs.
Pause Data Migration--Arcserve Backup lets you pause the migration of data from
the FSD to the final destination (tape) by enabling the Pause Data Migration option.
This feature allows you to continue backing up to the FSD, but pause the migration
from the FSD to the final destination in case the tape library is scheduled for
maintenance or has hardware problems.
Flexible Restore Options--During the time period that the backed-up data is located
both on the final destination media (tape) and on the FSD (prior to purging),
Arcserve Backup provides you with a choice for selecting the source for restoring
the data. If the backup image is located on both the FSD and the final destination,
you can choose where to restore it from.
Command Line Support--Arcserve Backup lets you create backups to FSDs using
either the graphical user interface (GUI) or the command line utility. In the event
that a copy-to-tape operation fails, you can use the Query tool to analyze the file
and session contents on the FSD. If you need to purge sessions from the FSDs, you
can use the Purge tool to remove data and free extra space on the FSDs.
Disk Staging Reports--Arcserve Backup lets you generate reports that are dedicated
to disk staging backups. Using these reports you can find the status of backup
sessions, whether a session was copied, when the session was copied, where the
session was copied, whether the session was SnapLocked, when the session will be
purged from the FSD, and other valuable information.
Specify and configure file system devices, tape libraries, and virtual tape libraries.
Define policies for managing backup, data migration, data security, data purge, alert
messages, and postscript operations.
Disable staging in rotation and GFS rotation backup jobs on any specified day of the
week.
View the status of master and child jobs in the Job Status Manager. The Job Status
Manager displays a tree view of all master jobs and their corresponding child jobs
for backup and migration operations.
View the Activity Log (in Windows) displaying the logs of all the child jobs and
migration jobs, and the purging activities of the master job in a tree format.
Restore data from a staging device. If the data from a backup job resides in two
locations (on the file system device and on the final destination media), you can
restore the data from either location.
Run command line tools that can analyze and purge data stored on a FSD in a
staging group.
Access reports using the Report Manager to capture information about purge and
migration activities on FSDs.
Perform a Double Tape Copy migration job from the disk staging location to two
final destinations simultaneously.
To ensure that the migration job continues when one of the devices become
unavailable, you can set a timeout value for additional backup media to continue
the migration job in another device. If you do not set a timeout value, then the data
migration job fails after the first backup media timeout completes. For more details
about setting the timeout value, see Backup Manager Backup Media Options (see
page 164).
How the Max Number of Streams Option Affects Backup and Restore Operations
Arcserve Backup provides you with the capability of streaming multiple jobs
simultaneously to FSDs. Simultaneous streaming is a process that divides your backup
jobs into several subjobs that run simultaneously. Arcserve Backup lets you use
simultaneous streaming to send multiple streams of data to a device in a staging group.
Since the data is split up among several different streams, simultaneous
streaming-enabled backup jobs can be completed significantly faster than regular
backup jobs.
When you back up data using disk staging, a backup job can spawn child jobs. Each child
job employs one stream of data. The actual number of child jobs that the parent job can
spawn varies based on whether the backup job is a node-level or a volume-level backup
job. However, the number of child jobs will never exceed the number of streams
specified for staging.
Note: If a job spawns child jobs and you do not specify a number of streams to use, the
child jobs will be created and backed up in one continuous stream.
For a node-level backup job, the number of child jobs spawned depends upon the
number of agents specified in the backup job. Similarly, for a volume-level backup job,
the number of child jobs spawned depends upon the number of volumes specified in
the backup job.
Example: Staging Backup Jobs with Multiple Streams
If a backup job consists of backing up four nodes and the backup level is at the node
level, the parent job can spawn a minimum of four child jobs. In this example, if you
specify three streams, the master job can stream three child jobs simultaneously and
start the fourth child job as one of the three previous child jobs end. After all child jobs
are complete, the parent job is considered finished.
Properties View
From the properties view in the Backup Manager, you can perform the following
tasks:
Configure Groups--Lets you open Device Group Configuration so that you can
configure device groups.
Set Disk-based Device Group Properties--Lets you open File System Device
Group Configuration so that you can configure staging group properties.
Back up to disk and then copy the data to two final destinations simultaneously
(Double Tape Copy) and delete the data on the staging device by creating staging
groups.
To ensure that the migration job continues when one of the devices become
unavailable, you can set a timeout value for additional backup media to continue
the migration job in another device. If you do not set a timeout value, then the data
migration job fails after the first backup media timeout completes. For more details
about setting the timeout value, see Backup Manager Backup Media Options (see
page 164).
Create flexible policies that determine when you want to copy and delete data.
Reduce the backup window when a single job breaks into multiple simultaneous
streams while writing to a disk staging area. The number of simultaneous streams
can be controlled according to your disk network throughput capabilities.
Before you can back up data using disk staging, you must perform the following tasks:
Create the staging devices. First, you must specify the devices in your environment
that you will use for staging operations.
Important! Staging backup operations can quickly consume a large amount of free
disk space on FSDs. Due to the maximum file size limitations of FAT 16 and FAT 32
file systems, you should not use these file systems on FSDs designated for staging
operations.
Configure the staging groups. After specifying the devices in your environment, you
must configure the device group to function as a staging group.
Configure the staging policies. To perform backup operations using staging, you
must define the copy and purge policies that Arcserve Backup will use to manage
data stored on staging devices.
The following sections provide you with information about how to configure Arcserve
Backup to perform staging backups.
More information:
Configure Device Groups to Use Staging (see page 210)
Specify Staging Groups Settings (see page 212)
Specify Copy and Purge Policies for Disk Staging Backups (see page 213)
Specify Postscripts Options for Disk and Tape Staging Backups (see page 220)
Specify Miscellaneous Options for Disk Staging Backups (see page 216)
From the Administration menu in the Navigation Bar on the Arcserve Backup
Manager Console, click Device Group Configuration.
Device Group Configuration opens.
2.
Click Next.
The Login Page dialog opens.
3.
Complete the required fields on the Login Page dialog and click Next.
The Options dialog opens.
4.
From the Options dialog, select the server that you want to configure, click
Configure Disk-based Groups, and then click Next.
5.
From the Groups list, select the group that you want to configure. To enable staging
for the selected group, click the Enable Staging option and then modify the
following options as needed:
Max Threshold--Lets you specify the maximum amount of used space on a disk
that Arcserve Backup will use for staging backups. When Arcserve Backup
detects that the amount of used disk space exceeds the Max Threshold,
Arcserve Backup pauses the backup job and purges the oldest migrated
sessions from the FSD until the amount of used disk space is equal to or less
than the Purge to Threshold.
Default value: If % is specified, 80%; if GB is specified, 8 GB; if MB is specified,
4000 MB.
The Max Threshold can be represented as either the total number of MB or GB
used, or as a percentage of the total capacity used on the FSD. If the Max
Threshold value is set as a percentage of the capacity of the FSD, the Max
Threshold value must be equal to or less than 100% and the Purge to Threshold
value must be greater than 0%.
Note: The Max Threshold must be greater than the Purge to Threshold. If you
specify an absolute value (for example, MB or GB), the value must be equal to
or greater than 1 MB.
Purge data when the used disk space exceeds the Max Threshold--Lets
Arcserve Backup purge migrated sessions from the FSD when the amount of
used disk space exceeds the Max Threshold.
Note: To ensure that the purge mechanism starts in a timely manner, best
practice is to specify a Max Threshold value that is at least 100 MB less than the
total disk space.
Purge to Threshold--Lets you specify the amount of used space on a disk when
Arcserve Backup stops purging the oldest migrated sessions from the disk.
Default value: If % is specified, 60%; if GB is specified, 6 GB; if MB is specified,
3000 MB.
Arcserve Backup automatically specifies the units specified in the Max
Threshold value (for example, %, MB, or GB). The Purge to Threshold value
must be less than the Max Threshold value. If you specify an absolute value (for
example, MB or GB), the value must be equal to or greater than 1 MB.
Example: The capacity of an FSD is 100 GB. The amount of used disk space is
75% (75 GB). The Max Threshold is 80% (80 GB) and the Purge to Threshold is
50% (50 GB). The administrator submits a job totaling 10 GB. Arcserve Backup
detects that the job, when complete, will be greater than the Max Threshold.
Arcserve Backup pauses the job and purges the oldest migrated sessions from
the FSD until the amount of used disk space is equal to or less than the Purge to
Threshold - in this example, 50% (or 50 GB). Arcserve Backup then continues
the backup job.
Note: If Arcserve Backup purges all of the migrated sessions from the disk, but
the amount of used continues to exceed the Purge to Threshold, Arcserve
Backup restarts the job and attempts to complete the job using the available
disk space.
Enable SnapLock for this group--Lets you enable SnapLock WORM protection
on the file system device.
Note: This option is not available for libraries. To use this option, the file
system device must support SnapLock technology. If you enable SnapLock on a
device that does not support SnapLock WORM protection, Arcserve Backup
write-protects the data, however, the data can be deleted from the device.
6.
7.
From the Backup Manager window, click the Staging Location tab.
2.
From the groups list, right-click a group and select Set Disk-based Device Group
Properties from the pop-up menu.
The Disk-based Group Property Configuration dialog opens.
3.
4.
In the Max Threshold field, specify the maximum file system device threshold. From
the drop-down list, choose MB, GB, or %.
5.
Click the Purge data when the used disk space exceeds the Max Threshold option if
you want Arcserve Backup to automatically purge migrated sessions from the FSD
when the amount of used disk space is greater than the Max Threshold
In the Purge to Threshold field, specify the amount of used space on a disk when
Arcserve Backup stops purging the oldest migrated sessions from the disk.
6.
When you enable disk staging, multiple streaming is enabled by default. If you:
Did not license the Enterprise Module, you can specify one or two streams.
7.
If the file system device supports SnapLock, and you want to WORM-protect the
backed up data, click the Enable SnapLock option.
8.
Click OK.
After you complete these steps, the newly created file system device group appears in
the Groups directory tree on the Staging Location tab.
Note: Device groups identified as staging device groups do not appear in the Destination
tab of the Backup Manager.
More information:
Configure Device Groups to Use Staging (see page 210)
2.
3.
Click Full Backup to specify policies for full backup jobs and select
Differential/Incremental Backup to specify policies for differential and
incremental backup jobs.
Do not copy data--Choose this option if you do not want to migrate the backup
sessions to final destination media. For example, consider differential and
incremental backup operations. Operations of this type tend to have short
retention periods and are small with respect to overall size. If you do not copy
the incremental and differential backups to final destination media, the need
for tapes to store your backups diminishes.
After--Lets you start the migration job after specified length of time elapses.
Note: Be aware that physical disks and volumes do not support differential and
incremental backups. As a result, Arcserve Backup applies full backup policies
to incremental and differential backups of physical disks and volumes. The
Copy Time is the only exception to this behavior. With staging backups,
Arcserve Backup copies incremental and differential backups of physical disks
and volumes to final destination media based on the copy policies specified for
incremental and differential backups.
Arcserve Backup starts the copy to final destination media operation based
upon the occurrence of one of the following events:
After job starts--Lets you start the migration operation at a fixed point in
time after the backup to disk operation starts.
After job ends--Lets you start the migration operation after the backup to
disk operation ends.
Due to variations in the overall size of backup jobs and the length of time
needed to complete backup to disk operations, simultaneous read and
write operations to the disk staging device can occur. This option prevents
simultaneous read and write operations to disk staging devices.
After each session is finished--Choose this option if you want to start the
copy to media operation immediately after the backup to disk operation
for the session is complete.
Most backup jobs consist of several sessions. When you specify this option,
you can direct Arcserve Backup to copy backup sessions to their final
destination immediately after the backup job is finished. This option
manifests simultaneous backup and copy operations. By performing
backup and copy operations simultaneously, you can reduce the overall
backup window and copy window.
Because this option induces simultaneous read and write operations on
the FSD, you should only specify this option if you are using a high-speed
device that can process many read and write operations simultaneously.
Note: For all Copy data after options, Arcserve Backup will not migrate sessions
to their final destination media until after the backup job for the session is
complete. This capability includes scenarios when the copy retention period
expires before the backup operation is complete.
At--Lets you start the migration operation at a specific time of day. When you
use this option you can direct Arcserve Backup to start the migration process at
a specific time on a daily basis.
Select the Or after the job is finished whichever happens later option if you
suspect or anticipate the backup to disk operation to end after the
specified start time for the copy to final destination operation. This option
prevents Arcserve Backup from copying sessions from disk to tape while
the backup operation is in progress.
Copy data for specified backups only--Lets you migrate only monthly or weekly
backups associated with rotation jobs.
Note: Copy data for specified backups only options do not apply to incremental
and differential backups.
Default value: Disabled.
With this option enabled, you can specify one of the following migration
options:
Copy data for monthly backups only--Lets you migrate only the monthly
full backup sessions, not the weekly full backup jobs, associated with
rotation jobs.
Note: This option can be applied on only GFS rotation jobs.
Copy data for weekly backups only--Lets you migrate only the weekly full
backup sessions, not the daily backup sessions, associated with rotation
jobs.
Seven day rotations--Lets you migrate data in the following scenarios: For
7-day weekly full backups, Arcserve Backup migrates the Saturday (full)
backup sessions. For 7-day weekly incremental/differential backup, full
backup on Sunday backups, Arcserve Backup migrates the Sunday (full)
backup sessions.
Five day rotations--Arcserve Backup migrates only the Friday (full) backup
sessions.
Note: This option can be applied on rotation jobs and GFS rotation jobs.
For more information, see Rotation Schemes (see page 307).
4.
5.
After--Lets you start the purge operation after specified length of time elapses.
Arcserve Backup starts the purge operation based upon the occurrence of one
of the following events:
After job starts--Lets you start the purge operation at a specified time
after the backup to staging device operation starts.
After job ends--Lets you start the purge operation at a specified time after
the backup to staging device operation ends.
At--Lets you start the purge operation at a specific time of day. Use the spin
box to specify the time of day that you want the operation to start.
Purge canceled sessions from disk--Use this option to direct Arcserve Backup
to delete sessions from the staging device immediately after a backup to
staging device is canceled.
This option helps to reclaim free disk space on the staging device as quickly as
possible.
Purge failed sessions from disk--Use this option to direct Arcserve Backup to
delete sessions from the staging device immediately after a backup to disk
staging device fails.
This option helps to reclaim free disk space on the staging device as quickly as
possible.
Create makeup jobs to back up data directly to final destination under disk
full conditions--Use this option to direct Arcserve Backup to back up data
directly to its final destination media if there is insufficient free space on the
file system device in a staging group.
A backup operation will fail if there is insufficient free disk space on the staging
device. To remedy this situation, Arcserve Backup can divert the backup
operation from the file system device in a staging group directly to the final
destination media. A makeup job searches for blank media and media from a
scratch. As such, specifying this option can increase the overall success rate of
your backup operations when a "disk full" condition exists.
Create makeup jobs on hold if Data Migration jobs fail--Use this option to
direct Arcserve Backup to create makeup jobs on HOLD if data migration (copy
to tape) jobs fail.
A data migration job can fail if a media or tape drive error occurs during the
copy to tape operation. Use this option to create a makeup job with a HOLD
status that you can change to a Ready status after correcting the tape drive or
media errors. If an error condition exists, this option minimizes the need to
create tapecopy jobs.
If you have a requirement to consolidate data across multiple jobs and ship
the tapes on a daily basis, you should choose the Overwrite option.
If the backup is a rotation or a GFS backup, you must specify the prefix of
the target media and the prefix of the media pool that you want to use for
consolidation on the Destination tab.
Note: For more information about consolidation options and examples, see
Consolidation During Migration (see page 441).
2.
3.
4.
From the Event list, select one of the following migration job events for which you
want to send an alert notification:
Format Blank Tape--A tape was formatted during the execution of a migration
job.
E*--An error occurred and the error message appeared in the Activity Log.
W*--A warning occurred and the warning message appeared in the Activity
Log.
C*--A critical massage occurred and the critical message appeared in the
Activity Log.
AE*--An agent error message occurred and the agent error message
appeared in the Activity Log.
AW*--An agent warning message occurred and the agent warning message
appeared in the Activity Log.
Examples:
AE* is specified in the Event Code field. An alert will be sent when any
agent error message occurs and the agent error message appears in the
Activity Log.
AE0006 is specified in the Event Code field. An alert will be sent only when
AE0006 occurs and the error message appears in the Activity Log.
E*;AE0006 is specified in the Event Code field. An alert will be sent when
any errors occur and the error messages appear in the Activity Log, when
AE0006 occurs and the error message appears in the Activity Log, or both.
5.
From the Methods & Recipients field, you can accept the default options, or create
a custom alert for the event. The <Default> configuration means that you will use
the alert options configured using the Alert Manager.
To create custom alerts, click the Configure button.
The Methods & Recipients Configuration dialog opens. You can specify one or more
of the defined alert configurations.Arcserve Backup provides the following defined
alert configurations:
Broadcast
Pager
Note: Pager options are not supported on Japanese versions of Arcserve
Backup.
6.
SMTP
SNMP
Event
Printer
Lotus Notes
Unicenter NSM
To add a new Methods & Recipients configuration, click the New button.
The Configuration Name dialog opens. Specify a name for the configuration and
click OK.
A new configuration tree displays in the browser at the left of the dialog. The new
configuration tree contains one branch for all available notification methods. You
must now add recipients to the methods branches of your tree. For example, if you
want to use the Printer notification method, you must add an available printer to
the tree.
7.
To add a recipient to a configuration, you must first select a method (for example,
Broadcast) from the configuration tree and then click the Add button.
The appropriate Add Recipient dialog opens for the selected configuration.
Configure the new recipient in this dialog. For more information about the different
Recipient dialogs, click the Help button.
After you configure the new recipient, it is added to the tree.
Note: You cannot add recipients for the Unicenter TNG alerts. If you click Modify,
the Unicenter TNG Event Map dialog opens. You can then have messages sent to
the Unicenter console or the World View repository when an alert is generated.
8.
To modify a Methods & Recipients configuration, select the configuration from the
Configuration drop-down list.
The selected Configuration tree displays in the browser. You can add, modify, or
delete recipients from the configuration tree by clicking the Add, Modify, or Delete
button.
To delete a configuration, select the configuration from the Configuration
drop-down list and click the Delete button.
To rename a configuration, select the configuration from the Configuration
drop-down list, and click the Rename button.
2.
3.
4.
From the Event list, select one of the following migration events for which you want
to run a postscript:
Migration job canceled--A migration job was canceled by a user while it was in
an Active, Ready, or Hold status. A makeup job was not created.
Makeup of migration job created--A migration job failed and Arcserve Backup
created a makeup job.
5.
Click in the Postscripts field adjacent to the selected event and do one of the
following:
Enter the path to script that you want to run after the event occurs.
User name
Password
Confirm password
2.
Click the Source tab, browse to and select the source objects that you want to back
up.
3.
Click the Schedule tab and specify the schedule that you want to use for the backup
job.
Note: For more information, see Rotation Schemes (see page 307) and Custom
Schedules (see page 318).
4.
Click the Staging Location tab and expand the Staging Servers object.
Browse to and select the staging group that you want to use for the backup job. If
you selected a deduplication job on the Start tab, choose a deduplication device
group from the Staging Location tab.
5.
Click the Policies tab. Complete the following Staging Policies required for the job:
Full Backup--Specify the Copy and Purge policies for full backups required for
the job.
(optional)--Click Enable Snaplock.
6.
7.
8.
Select the Encryption/Compression tab and complete the following fields for the
backup job, provided you are not using deduplication devices:
Encrypt data--Use this option to encrypt the backup data. You can specify one
of the following options:
At agent--Select this option to encrypt the backup data prior to the actual
backup process. For more information about this option, see Data
Encryption at the Agent Server (see page 113).
Compress data--Use this option to compress the backup data. You can specify
one of the following options:
9.
If you want to apply other options that affect the migration job, you should do
so at this time. For example, to eject the tape from a library after the migration
job is complete, click the Operation tab on the Global Options dialog and select
the Eject Media option.
If you specify encryption and compression options, and the backup destination
is a drive that does not support compression, or is a file system device (FSD),
Arcserve Backup encrypts the backup data and does not compress the backup
data.
10. Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
More information:
Submit a Backup Job (see page 136)
2.
Select the Use Rotation Scheme option, and then select the scheme name from the
Scheme Name drop-down list.
3.
4.
Select the Day Of Week for which you want to modify staging, and then click the
Modify button.
The Configuration dialog opens.
5.
6.
Click OK.
Note: To disable staging for a staging group, see Disable Staging (see page 227).
From the Staging Groups tree on the Staging Location tab, select the group that you
want to pause.
2.
Right-click the group name and select Configure Disk-based Groups from the
pop-up menu.
The Disk-based Group Property Configuration dialog opens.
3.
Note: To restart the data migration operation, repeat the above steps and clear the
checkmark from Pause data migration.
Disable Staging
Arcserve Backup provides you with the capability to disable (or bypass) backup to FSD
operations. When you use this option, data is backed up directly to its final destination
media, rather than being backed up to the FSD.
There are two methods that you can use to perform this task:
From the Rotation Rules tab on the Schedule tab of the Backup Manager.
Open the Backup Manager window and click the Schedule tab.
2.
3.
Click the Rotation Rules tab and select the rotation that you want to disable.
4.
5.
From the Staging drop-down list on the Configuration dialog, select Disabled.
6.
Click OK.
Open the Backup Manager window and click the Staging Location tab.
2.
Right-click the group that you want to disable and select Set Disk-based Device
Group Properties.
The File System Device Group Configuration dialog opens, displaying all groups in
your environment that are specified as file system device groups.
Note: The groups that are enabled for staging display with a corresponding dark
blue flag. The groups that are not enabled for staging display with a corresponding
light blue flag.
3.
4.
Clear the check mark from the Enable Staging check box.
5.
Click OK.
How You Can Manage Staged Data When the Database Fails
When you use disk staging to back up data, the information about the backup jobs,
sessions, staging policies, and so on is stored in the Arcserve Backup database. If the
database fails, and you need to recover the Arcserve Backup database, the staging
policies for the data residing on the staging device (for example, a file system device or a
library) that specify when to copy the data to the final destination media and, if file
system device (FSD), when to purge the data from the staging device are no longer
available.
If this situation occurs:
Arcserve Backup cannot copy (migrate) the data on staging device to its final
destination media.
Arcserve Backup cannot purge data from a file system device (FSD) to reclaim disk
space. As a result, future backup jobs will probably fail due to an insufficient
amount free disk space on the staging device.
To remedy this situation and retain all of the backup data that is stored on the staging
device, you can use the tapecopy command line utility to copy all the backup data from
the staging device to final destination media. (When you use this approach, media
rotation rules, such as Friday tape or Monday tape may not be adhered to.) Then, you
can use the -purge option from the Device Manager command line utility (ca_devmgr)
to delete the data from the FSD and reclaim disk space.
Backup Process--Arcserve Backup backs up data from the source to the staging
location. The staging location is a tape library or a virtual tape library (VTL).
Copy Process--Arcserve Backup copies or migrates the backup data from the staging
location to the final destination media. The final destination is tape media.
The following diagram illustrates the flow of data from the source to the first stage tape
library (or virtual tape library) and then on to the final destination.
Note: Arcserve Backup lets you transmit up to 32 streams of data using multistreaming.
To back up data using multiple streams and transmit more than two streams of backup
data, you must license the Arcserve Backup Enterprise Module (see page 39).
When you use backup to tape to tape (B2T2T) to protect data, the backup to tape to
tape operation consists of two phases:
Backup Phase
Arcserve Backup backs up data from the source to the tapes in the first stage, based on
user-specified policies.
During the backup job, global options, media selection rules, media pool usage,
rotation rules, GFS rotation rules, Alert messages, Export options, and so on are
identical to that of backing up directly to tape.
Note: Various global backup options do not apply to backup phase operations.
Multiplexing and multistreaming can be used to transmit and save data to first
stage media.
Note: The Multiplexing option can be used for backup operations to all tape
devices, with the exception of file system devices. The Multistreaming option can
be used for backup operations to tape libraries that contain two or more drives.
Copy Phase
Arcserve Backup copies data from the first stage to the final destination based on
user-specified policies.
Arcserve Backup copies data from the first stage media to the final destination
media one session at a time. Multiple sessions cannot be copied to a single tape
simultaneously.
If you need to copy data from more than one first stage media to one final
destination media, Arcserve Backup copies each session in succession until all the
sessions are copied to the final destination media.
Arcserve Backup sessions associated with different jobs can be consolidated during
migration. You can activate this capability using the consolidation option.
If a hardware error occurs during the process of copying data to final destination,
the job stops and Arcserve Backup creates a Makeup Job On Hold. After you correct
the hardware error, you can change the job status to Ready, and then the job
resumes.
More information:
How to Use Tape Staging to Manage Backup Operations (see page 232)
How to Submit a Tape Staging Backup Job (see page 236)
How to Configure Arcserve Backup to Perform Tape Staging Backups (see page 233)
If you need to store two copies of backup data, one copy on site and one copy at an
off-site storage location, B2T2T lets you back up data directly to tape. After the
backup job is complete, you can use Arcserve Backup copy utilities to automate and
create copies of the backup tapes, and then ship the tapes to an off-site storage
location.
B2T2T lets you encrypt backup data when you are copying the data to its final
destination media. This capability is beneficial when you are copying data from a
virtual tape library or a library that does not support encryption to a library that
supports encryption. This capability ensures that your backups are as fast as
possible and the tapes that you need ship to an off-site storage location are
encrypted.
While backup operations are in progress, you may have many jobs that are backing
up data to many different tapes. This can result in media that is not being used to
its full capacity. B2T2T operations let you consolidate backups to ensure that media
is being used to capacity when copying data to final destination. This capability
helps to reduce the cost of media because you are using fewer tapes for final
destination media, off-site storage, or both.
If you need to reduce the length of time required to back up data and copy the data
from a staging area to final destination, you can use virtual tape libraries (VTL) in
your environment to manage backup operations.
A VTL is a temporary storage location, such as a disk drive, that is configured to
behave like a library. Since most backup data is transmitted across a network,
Arcserve Backup lets you use multiplexing to reduce the backup window. When you
use a VTL to store backup data, you can quickly read data from a multiplexing
formatted data in a VTL because your operations do not encounter tape positioning
overhead. As a result, the processes of backing up data to a VTL, reading from a VTL
(disk), and copying the data to final destination media is fast. Arcserve Backup lets
you automate the process of copying to final destination media when you use a VTL
to stage your backup data.
More information:
Specify Miscellaneous Options for Tape Staging Backups (see page 235)
Specify Postscripts Options for Disk and Tape Staging Backups (see page 220)
Specify Migration Policies for Tape Staging Backups (see page 233)
2.
3.
Click Full Backup to specify policies for full backup jobs and click
Differential/Incremental Backup to specify policies for differential and
incremental backup jobs.
Do not copy data--Choose this option if you do not want to migrate the backup
sessions to final destination media. For example, consider differential and
incremental backup operations. Operations of this type tend to have short
retention periods and are small with respect to overall size. If you do not copy
the incremental and differential backups to final destination media, the need
for tapes to store your backups diminishes.
Be aware of the following behaviors:
Be aware that physical disks and volumes do not support differential and
incremental backups. As a result, Arcserve Backup applies full backup
policies to incremental and differential backups of physical disks and
volumes. The copy time is the only exception to this behavior. With staging
backups, Arcserve Backup copies incremental and differential backups of
physical disks and volumes to final destination media based on the copy
policies specified for incremental and differential backups.
Copy data for specified backups only--Lets you migrate only monthly or weekly
backups associated with rotation jobs.
Note: Copy data for specified backups only options do not apply to incremental
and differential backups.
Default value: Disabled.
With this option enabled, you can specify one of the following migration
options:
Copy data for monthly backups only--Lets you migrate only the monthly
full backup sessions, not the weekly full backup jobs, associated with
rotation jobs.
Note: This option can be applied on only GFS rotation jobs.
Copy data for weekly backups only--Lets you migrate only the weekly full
backup sessions, not the daily backup sessions, associated with rotation
jobs.
Seven day rotations--Lets you migrate data in the following scenarios: For
7-day weekly full backups, Arcserve Backup migrates the Saturday (full)
backup sessions. For 7-day weekly incremental/differential backup, full
backup on Sunday backups, Arcserve Backup migrates the Sunday (full)
backup sessions.
Five day rotations--Arcserve Backup migrates only the Friday (full) backup
sessions.
Note: This option can be applied on rotation jobs and GFS rotation jobs.
For more information, see Rotation Schemes (see page 307).
Create a makeup job on hold if a data migration job fails--Use this option to
direct Arcserve Backup to create makeup jobs on HOLD if data migration (copy
to tape) jobs fail.
A data migration job can fail if a media or tape drive error occurs during the
copy to tape operation. Use this option to create a makeup job with a HOLD
status that you can change to a READY status after correcting the tape drive or
media errors. If an error condition exists, this option minimizes the needs to
create tapecopy jobs.
Schedule a makeup job for a data migration job if it cannot proceed because
the source group or tape is not available--Use this option to direct Arcserve
Backup to schedule a makeup job when the source group or tape is not
available.
The source may not be available do to a variety of reasons. For example, the
backup phase for the job is not complete, or a hardware problem exists in the
tape library or virtual tape library.
2.
To consolidate the backup data during the migration operation, click the
Consolidate data across jobs while copying option and complete the following
fields.
Note: If you want to consolidate data across multiple jobs to the same tape, you
should run the backup jobs on the same machine.
If you have a requirement to consolidate data across multiple jobs and ship
the tapes on a daily basis, you should choose the Overwrite option.
Note: For more information about consolidation options and examples, see
Consolidation During Migration (see page 441).
You must license the Arcserve Backup Enterprise Module (see page 39) to back up
data using multiple streams and transmit more than two streams of backup data.
You must license the Arcserve Backup Tape Library Option to back up data to a tape
library that contains more than one tape drive.
Arcserve Backup provides you with the capability to submit a backup job using either
the Backup Manager or the command line utility. This information describes how to
perform a tape staging backup job using the Backup Manager. For information about
how to submit a staging backup job using the command line, see the Command Line
Reference Guide.
Note: Before you can back up data using tape staging, ensure that all preconfiguration
tasks are complete and all licensing requirements are fulfilled. For more information,
see Licensing Requirements for Staging Backups.
To back up data using tape staging
1.
2.
Click the Source tab, browse to and select the source objects that you want to back
up.
3.
Click the Schedule tab and specify the schedule that you want to use for the backup
job.
Note: For more information, see Rotation Schemes (see page 307) and Custom
Schedules (see page 318).
4.
Click the Staging Location tab and expand the Staging Servers object.
Browse to and select the staging group that you want to use for the backup job. If
you wish to enable deduplication, choose a deduplication device group from the
Staging Location tab.
5.
Click the Policies tab. Complete the following migration policies required for the
job:
6.
If the staging device contains two or more drives, you can select any device
group on the Destination tab.
Example: You are required to stage your backup data to a virtual tape library
and ship the final media to an off-site storage facility. To manage a backup of
this type, you can specify a group that corresponds with a virtual library on the
Staging Location tab, and then specify a group that corresponds with a tape
library on the Destination tab.
7.
If the final destination device contains one drive (for example, an FSD or a
single-drive library), you must select a device group on the Destination tab that
is different from the device group specified on the Staging Location tab.
8.
Encrypt data--Use this option to encrypt the backup data. You can specify one
of the following options:
At agent--Select this option to encrypt the backup data prior to the actual
backup process. For more information about this option, see Data
Encryption at the Agent Server (see page 113).
Compress data--Use this option to compress the backup data. You can specify
one of the following options:
Note: The Compress data options do not apply to backups to UNIX and Linux
data mover servers.
Click OK.
The Options dialog closes and the specified encryption and compression options are
applied.
Be aware of the following:
9.
If you want to apply other options that affect the migration job, you should do
so at this time. For example, to eject the tape from a library after the migration
job is complete, click the Operation tab on the Global Options dialog and select
the Eject Media option.
If you specify encryption and compression options, and the backup destination
is a drive that does not support compression, or is a file system device (FSD),
Arcserve Backup encrypts the backup data and does not compress the backup
data.
10. Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
More information:
Submit a Backup Job (see page 136)
2.
Click the Source tab, browse to and select the source objects that you want to back
up.
3.
Click the Staging Location tab and the Destination tab to configure the media pool
and group.
Specify the values that you require to submit the backup job in the following fields:
4.
Group
Select the Schedule tab, and select the Use Rotation Scheme option.
A list of available schemes display in the Scheme Name drop-down list.
5.
From the Scheme Name drop-down list, select the scheme that you require for your
backups.
6.
7.
Complete the required fields on the Submit Job dialog and click OK.
The disk staging method utilizes a disk as the staging area and is commonly referred
to as Archive to Disk to Tape.
The tape staging method utilizes a tape library or a virtual tape library as the staging
area and is commonly referred to as Archive to Tape to Tape.
Each staging method contains specific options to control the behavior of Arcserve
Backup during the archive process.
Note: The Archive Staging Methods have the same behavior as the Backup Staging
Methods. Refer to the Backup Staging Methods (see page 200) for details.
How to Use Disk Staging to Manage Archive Data (see page 242)
Archive Process--Arcserve Backup archives data from the source to the staging
location. The staging location is a Disk Staging Device.
Copy Process--Arcserve Backup copies or migrates the archive data from the
staging location to the final destination media. The final destination is usually tape
media, but can be another Disk Staging Device.
Note: Arcserve Backup lets you transmit up to 32 streams of data using multistreaming.
To archive data using multiple streams and transmit more than two streams of archive
data, you must license the Arcserve Backup Enterprise Module (see page 39).
Using disk staging you can archive data to disk staging devices that are used as a
temporary staging area. A staging job can divide your archive job into several
subjobs that run simultaneously. Disk staging lets you use simultaneous streaming
to send multiple streams of data to the disk staging device. Since the data is split
among several different streams, archive jobs with simultaneous streaming enabled
can be completed significantly faster than regular archive jobs.
You can then migrate (copy) the data from the disk staging device to a final storage
media (or from disk to tape). As a result, the tape drive can be kept streaming,
thereby minimizing the shoeshine effect (starting, stopping, and repositioning the
tape), and increasing both the life expectancy and efficiency of the tape drive.
While the archive image is still on the disk staging device, data can be restored
directly from the disk staging device. The restore time is significantly reduced
because restoring data from disk is generally faster than restoring from a tape (no
delays due to tape load and seek latency).
During the archive-to-disk staging device process, if the disk staging device gets full
or reaches the specified maximum threshold, Arcserve Backup lets you create
makeup jobs which would then archive the data directly to the final destination
after the staging archive job fails. This increases the success rate of archives. In
addition, if there are any errors during the copy-to-final destination process,
Arcserve Backup lets you create makeup jobs.
Note: Under disk full conditions, the makeup job created to archive the data to tape
will always try to use a blank tape or a media from a scratch set. It will never try to
append to an existing media.
The archive images are kept on the disk staging device until the retention time
expires (as determined by the specified purge policy). At that time, Arcserve Backup
automatically purges the data from the disk staging device, and reclaims disk space
so that archives can continue.
How to Use Tape Staging to Manage Archive Operations (see page 245)
Archive Process--Arcserve Backup archive data from the source to the staging
location. The staging location is a tape library or a virtual tape library (VTL).
Copy Process--Arcserve Backup copies or migrates the archive data from the
staging location to the final destination media. The final destination is tape media.
The following diagram illustrates the flow of data from the source to the first stage tape
library (or virtual tape library) and then on to the final destination.
Note: Arcserve Backup lets you transmit up to 32 streams of data using multistreaming.
To archive data using multiple streams and transmit more than two streams of archive
data, you must license the Arcserve Backup Enterprise Module (see page 39).
When you use archive to tape to tape to protect data, the archive to tape to tape
operation consists of two phases:
Archive Phase
Arcserve Backup archive data from the source to the tapes in the first stage, based on
user-specified policies.
During the archive job, global options, media selection rules, media pool usage,
rotation rules, GFS rotation rules, Alert messages, Export options, and so on are
identical to that of archiving directly to tape.
Note: Various global archive options do not apply to archive phase operations.
Multiplexing and multistreaming can be used to transmit and save data to first
stage media.
Note: The Multiplexing option can be used for archive operations to all tape
devices, with the exception of file system devices. The Multistreaming option can
be used for archive operations to tape libraries that contain two or more drives.
Copy Phase
Arcserve Backup copies data from the first stage to the final destination based on
user-specified policies.
Arcserve Backup copies data from the first stage media to the final destination
media one session at a time. Multiple sessions cannot be copied to a single tape
simultaneously.
If you need to copy data from more than one first stage media to one final
destination media, Arcserve Backup copies each session in succession until all the
sessions are copied to the final destination media.
Arcserve Backup sessions associated with different jobs can be consolidated during
migration. You can activate this capability using the consolidation option.
If a hardware error occurs during the process of copying data to final destination,
the job stops and Arcserve Backup creates a Makeup Job On Hold. After you correct
the hardware error, you can change the job status to Ready, and then the job
resumes.
If you need to store two copies of archive data, one copy on site and one copy at an
off-site storage location, Archive to Tape to Tape lets you back up data directly to
tape. After the archive job is complete, you can use Arcserve Backup copy utilities
to automate and create copies of the archive tapes, and then ship the tapes to an
off-site storage location.
Archive to Tape to Tape lets you encrypt archive data when you are copying the
data to its final destination media. This capability is beneficial when you are copying
data from a virtual tape library or a library that does not support encryption to a
library that supports encryption. This capability ensures that your archives are as
fast as possible and the tapes that you need ship to an off-site storage location are
encrypted.
While archive operations are in progress, you may have many jobs that are
archiving data to many different tapes. This can result in media that is not being
used to its full capacity. Archive to Tape to Tape operations let you consolidate
archives to ensure that media is being used to capacity when copying data to final
destination. This capability helps to reduce the cost of media because you are using
fewer tapes for final destination media, off-site storage, or both.
If you need to reduce the length of time required to archive data and copy the data
from a staging area to final destination, you can use virtual tape libraries (VTL) in
your environment to manage archive operations.
A VTL is a temporary storage location, such as a disk drive, that is configured to
behave like a library. Since most archive data is transmitted across a network,
Arcserve Backup lets you use multiplexing to reduce the archive window. When you
use a VTL to store archive data, you can quickly read data from a multiplexing
formatted data in a VTL because your operations do not encounter tape positioning
overhead. As a result, the processes of archiving data to a VTL, reading from a VTL,
and copying the data to final destination media is fast. Arcserve Backup lets you
automate the process of copying to final destination media when you use a VTL to
stage your archive data.
Backup types supported--Arcserve Backup lets you submit normal UNIX/Linux Data
Mover backups and tape staging UNIX/Linux Data Mover backups.
Note: For more information about installing and using UNIX and Linux Data Mover, see
the UNIX and Linux Data Mover Guide.
This section contains the following topics:
Back up Multiple Data Mover Servers in a Single Job (see page 247)
Back up Multiple Data Mover Servers in a Single Job Using Staging (see page 250)
Prerequisite Tasks
Verify that you configure at least one library. For information about how to
configure libraries, see Configure Libraries (see page 374).
2.
3.
4.
5.
Specify the source that you want to back up, as illustrated by the following screen:
Specify the schedule options that you require for the job.
Note: For more information about scheduling jobs, see Job Customization Methods
(see page 301).
Click the Destination tab.
The destination group directory tree appears.
7.
Expand the SAN object and expand the Shared Groups object.
Specify the Device Group where you want to store the backup data.
Note: Click the Device Group to identify the library associated with the group as
illustrated by the following screen:
Important! Arcserve Backup prevents you from submitting backup jobs when the
data mover server specified on the Source tab does not share the device group
specified on the Destination tab.
8.
(Optional) On the Destination tab, click the Multistreaming check box to back up
your data using multistreaming. Without multistreaming, Arcserve Backup
processes backup sessions sequentially. With multistreaming, Arcserve Backup lets
you distribute the backup sessions across multiple streams, which helps to decrease
the overall length of time required to complete the backup.
Note: For more information, see How Arcserve Backup Process Backup Data Using
Multistreaming (see page 103).
9.
(Optional) Click Options on the toolbar to specify additional options that you
require for the backup.
Note: For more information about backup job options, see Global Backup Options
(see page 154).
11. On the Security and Agent Information dialog, edit or confirm the security and
agent information for your job, and click OK.
The Submit Job dialog opens.
12. Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
Prerequisite Tasks
Verify that you configure at least one library. For information about how to
configure libraries, see Configure Libraries (see page 374).
2.
Enable staging
4.
5.
Specify the source that you want to back up, as illustrated by the following screen:
6.
Specify the schedule options that you require for the job.
Note: For more information about scheduling jobs, see Job Customization Methods
(see page 301).
Click the Staging Location tab.
The staging location and group directory tree appears.
7.
Expand the SAN object and expand the Shared Groups object.
Specify the Device Group where you want to stage the backup data.
Note: Click the Device Group to identify the library associated with the group as
illustrated by the following screen:
Important! Arcserve Backup prevents you from submitting backup jobs when the
data mover server specified on the Source tab does not share the device group
specified on the Staging Location tab.
8.
(Optional) On the Staging Location, click the Multistreaming check box to back up
your data using multistreaming. Without multistreaming, Arcserve Backup
processes backup sessions sequentially. With multistreaming, Arcserve Backup lets
you distribute the backup sessions across multiple streams, which helps to decrease
the overall length of time required to complete the backup.
Note: For more information, see How Arcserve Backup Process Backup Data Using
Multistreaming (see page 103).
9.
10. Complete the following migration policies required for the job:
Disaster Recovery
12. (Optional) Click Options on the toolbar and specify the options that you require for
the job.
As a best practice, you should apply other options that affect the migration job at
this time. For example, to eject the tape from a library after the migration job is
complete, click the Operation tab on the Global Options dialog and select the Eject
Media option.
Note: For more information about backup options, see Global Backup Options (see
page 154).
13. Click Submit on the toolbar to submit the job.
The Security and Agent Information dialog opens.
14. On the Security and Agent Information dialog, edit or confirm the security and
agent information for your job, and click OK.
The Submit Job dialog opens.
15. Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
Disaster Recovery
To ensure against data loss, maintain current backups of all your servers and
workstations. If you do not have these backups, Arcserve Backup is limited in its ability
to recover data. Be sure to create a media rotation scheme and a schedule to maintain
current backups.
By default, the Arcserve Backup server always generates or updates disaster recovery
information for all full backup systems, even when the Arcserve Backup Disaster
Recovery Option is not installed. This ensures that the latest backup information is
always available if the Arcserve Backup Disaster Recovery Option is installed a later
time.
Note: To disable the Arcserve Backup server from generating or updating the disaster
recovery information, create and set the following registry key value to 1 on the
Arcserve Backup server machine:
HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\CA ARCserve
Backup\Base\Task\backup\SkipDRSession
Arcserve Backup can recover data from optimized backup sessions to only
computers running Windows Server 2012.
With NTFS data deduplication backups, Arcserve Backup backs up only the data
deduplication settings. For example, the Enable data deduplication, Deduplicate
files older than (in days), and File extensions to exclude options. For all other
options, (for example, the Set Deduplication Schedule settings) Arcserve does not
include the settings with full volume backups because it cannot restore the settings
with full volume restores. When you want to recover all of the deduplication
settings, you must recover the entire computer or perform a disaster recovery of
the computer.
Arcserve Backup cannot perform Compare jobs on data that was backed up using
the NTFS data deduplication (optimize) option. When you submit Compare jobs of
this type, the jobs fail and an error indicating as such (Compare job not supported)
appears in the Activity Log.
When you perform optimized NTFS data deduplication backups and specify the
Compare Backup Media to Disk option, Arcserve Backup compares only the
reparsed files (not the entire volume).
Restore Manager
The aim of running a successful restore job is to identify the data you need quickly and
to retrieve it from the appropriate backup and archive media.
Arcserve Backup allows you to restore data to most computers attached to your
Windows network. Each restore job requires a source and destination. The files selected
as your source must originate from backup or archive media created by Arcserve
Backup, and the destination must be a hard drive. The Restore Manager provides three
tabs to customize your restore job:
Source
Destination
Schedule
The optional Arcserve Backup Client Agents allow you to communicate with remote
workstations in various environments to restore data to non-Windows systems, such as
UNIX.
Similarly, the optional Backup Agents allow Arcserve Backup to restore online databases
and applications such as Microsoft Exchange Server, Microsoft SharePoint Server,
Microsoft SQL Server, Lotus Domino, Oracle, and IBM Informix.
Restore by Tree--Lets you restore a specific directory or drive from a display of files
and directories that were backed up or archived with Arcserve Backup. Use this
method when you do not know which media contains the data you need, but you
know the computer from which the backup or archive originated.
The Restore by Tree view displays only the last instance of a backup or archive. To
view and access all other instances, select the object that you want to restore and
click the Recovery Point button. If there are multiple partial backups/archives of the
same drive, the Restore by Tree view displays only the last backup/archive.
However, if there is a full-volume backup/archive of the drive available, the last full
backup/archive is displayed, instead of the last partial backup/archive.
The Computer Name field allows you to filter based on partial name searching. You
can enter any part of the name and a list of relevant items are returned. For
example, if there are some computers whose computer name contains 'BB', you can
enter 'BB' in the Computer Name field and click the Update button. Relevant
computers are found. The Computer Name field also supports full name searching
and wildcard searching.
Note: The Restore Manager cannot display file paths that exceed 512 bytes. This
limitation includes the drive letter or network server and the share names. For
single-byte languages, this equates to approximately 500 characters. For multibyte
languages with a combination of single, mixed, and multibyte characters, 512 bytes
equates to 250 to 500 characters. For multibyte languages with all multibyte
characters, 512 bytes equates to approximately 250 characters. If a file path
exceeds 512 bytes, truncation occurs. To restore data from a truncated directory,
you must submit the restore job from the last directory in the path whose name
was not truncated.
Note: Arcserve Backup lets you export the results from the Restore Manager tree to
a text file. Right-click the session, media, directory, or server node and click Export
Data. Save the file to your local drive.
Search --Click the Search button to search your backups or archives for a specific file
or group of files with a similar file name. Arcserve Backup lets you specify file names
up to 255 characters, including the file extension, in the Search for field. If you do
not know the complete file name, you can simplify the results of the search by
specifying the wildcard characters "*" and "?" in the Search for field.
Note: The Search restore method does not work if the Database Engine is stopped.
Examples:
1.
Drive D:\ contains two directories that are backed up/archived on a weekly
basisD:\Temp and D:\Documents. D:\Temp and D:\Documents were both
backed up/archived on April 21 and April 28. A full backup/archive of drive D:\
was performed on April 1.
2.
3.
Restore by Session--Lets you select the session, the files, and directories you want
to restore. Use this method when you know the media name, but are not certain
about the session you want to restore.
This restore method does not work if the Database Engine is stopped.
Deduplication devices support the Restore by Session, but will likely contain
thousands of sessions. You will be prompted to specify a display option to manage
the volume.
The Media Name field allows you to filter based on partial name searching. You can
enter any part of the name and a list of relevant items are returned. For example, if
there are some sessions whose media name contains 'BB', you can enter 'BB' in the
Media Name field and click the Update button. Relevant sessions are found. The
Media Name field also supports full name searching and wildcard searching.
Note: The Restore Manager cannot display file paths that exceed 512 bytes. For
single-byte languages, this equates to approximately 500 characters. For multibyte
languages with a combination of single, mixed, and multibyte characters, 512 bytes
equates to 250 to 500 characters. For multibyte languages with all multibyte
characters, 512 bytes equates to approximately 250 characters. If a file path
exceeds 512 bytes, truncation occurs. To restore data from a truncated directory,
you must submit the restore job from the last directory in the path whose name
was not truncated.
Note: Arcserve Backup lets you export the results from the Restore Manager tree to
a text file. Right-click the session, media, directory, or server node and click Export
Data. Save the file to your local drive.
Restore by Query--Lets you restore files based on the search pattern used to locate
the names of the files or directories. Lets you specify the type of query to restore,
for example, All (default), Backup Session, or Archive. Use this method when you
know the name of the file or directory you want to restore, but do not know the
computer that was backed up or archived from or the media it was backed up or
/archived to.
Restore by query is not a case-sensitive operation.
Arcserve Backup lets you specify file names up to 255 characters, including the file
extension, in the File Name field. If you do not know the complete file name, you
can simplify the results of the query by specifying the wildcard characters "*" and
"?" in the File Name field.
Note: This restore method will not work if the Database Engine is stopped.
Search for Virtual Machine using the VM host name or VM type--Lets you
recover a virtual machine by VM name or VM type. If you search by VM type,
you must have VMware Converter 3.0.2 installed on the proxy or recovery jobs
fail. Using this restore method enables additional options on the Global
Options Operation tab.
SAN--(Storage Area Network) This option lets you transfer backup data
from proxy systems connected to the SAN to storage devices using Fibre
Channel communication.
NBDSSL--(Network Block Device Secure Sockets Layer) This option lets you
use the Network File Copy (NFC) protocol to communicate. NBDSSL
transfers encrypted data using TCP/IP communication networks.
Note: If the specified transport mode is not available, the transport mode
defaults back to the Dynamic option.
Recover Virtual Machine makes the specified VM unavailable while the
recovery job is in progress.
If you installed Arcserve Backup Enterprise Module, you will also have the Restore by
Image method available. Use this method when you must read and restore blocks of
data quickly by bypassing the file system.
How Arcserve Backup Lets You Browse a Large Number of Items in the Restore
Manager
Arcserve Backup lets you pause the process of loading items in the Restore Manager
when you browse a large number of directories, files, and so on. You can pause the
loading process when you click the Destination tab, clear the check mark from the
Restore files to their original location(s) option, and browse items on the Destination
tab.
The steps that follow describe how Arcserve Backup lets you browse a large number of
items in the Restore Manager window.
1.
When you select an item in from the directory tree in the Restore Manager,
Destination tab, Arcserve Backup displays a Loading dialog to inform you that a
large number of items need to be retrieved and loaded into the Restore Manager
window. You cannot click Cancel while Arcserve Backup is retrieving the list of items
to display in the Restore Manager window.
2.
After Arcserve Backup retrieves the list of items to display in the Restore Manager
window, the Loading dialog then displays the percentage of items that are loaded
into the Restore Manager. You can click Cancel to pause the operation.
3.
After you pause the Loading operation, you can continue the Loading operation by
right-clicking the target directory and selecting Show More from the pop-up menu.
4.
If you pause the loading process, the icon for the target directory displays as
follows:
5.
You can pause and continue the loading process as often as necessary. To load
more items, right-click the target directory and click Show More from the pop-up
menu.
6.
When the loading process is complete, the icon for the target directory displays as
follows:
2.
From the Loading message box, click Cancel to stop the loading process.
If Arcserve Backup did not load all items, the To show more objects, right-click the
target directory and select Show More from the pop-up menu warning message
appears.
Note: The message only appears the first-time you click Cancel on the Loading
message box.
3.
From the directory tree, right-click the target directory and click Show More from
the pop-up menu.
The Loading message box appears and Arcserve Backup continues loading the
items.
4.
You can pause and continue the loading process as often as necessary until
Arcserve Backup loads all items in the target directory.
If you pause the loading process, the icon for the target directory displays as
follows:
When the loading process is complete, the icon for the target directory displays as
follows:
Smart Restore
Arcserve Backup provides a transparent Smart Restore feature that can increase the
overall success rate of your restore operations. If a media read error or a hardware error
occurs during a restore job, Arcserve Backup searches for an alternate media to use to
complete the restore job.
Example: Smart Restore
During a restore job, the restore source media jams and disables the library. Arcserve
Backup then searches for duplicates of the backup session. If a duplicate of the session
exists, regardless of whether it exists on a file system device or another media, the
restore operation continues without user intervention.
Note: If a second media error occurs during the restore job, the job will fail.
Export the Restore by Query Results and View the Results in a Spreadsheet
Arcserve Backup lets you query the Arcserve Backup database and export the results of
the query to a text file. Arcserve Backup exports the values in tab-separated format.
With a tab-separated format, you can import the data into a spreadsheet application
(for example, Microsoft Excel) to analyze the results.
Example: Export the Restore by Query Results and View the Results in a Spreadsheet
Users asked you to restore several files that reside on different computers in your
environment. The users do not know the precise file names. There are other files with
similar file names on the computers. You can query the Arcserve Backup database using
wildcard characters to obtain the host names, file paths, file names, and file
modification dates. Using an Excel spreadsheet, you can sort the results and then ask
your users to inform you which files to restore.
From the Quick Start menu on the Arcserve Backup Home Page, click Restore.
The Restore Manager window opens.
2.
3.
4.
5.
6.
From the Restore Manager, select Restore by Query from the Source view
drop-down list.
The Restore by Query fields appear.
2.
Computer Name--Lets you specify the name of the computer that you want to
search. You can specify a specific computer name or select <<ANY>> from the
drop-down list to search all computers in your Arcserve environment.
File Name--Lets you specify a wild card or specific file name search. On UNIX
and Linux platforms, Arcserve Backup uses the standard 8.3 file naming
convention. For example, if you specify *.txt, all files with a .txt file extension
appear in the query results.
Note: Do not specify leading or trailing spaces in this field.
Look in Directory--Lets you specify the directory that you want to search. You
must specify an exact string match, starting with the drive letter, in this field.
UNIX and Linux platforms regard the backward slash character "\" as a
separator. For example, \root\dir1\text.txt.
Examples: Look in Directory
If the mount point is /, use the following search string:
/\root\dir1\text1
3.
Click Query.
Arcserve Backup queries the database and returns the files that meet your search
criteria.
4.
Select the files and directories you want to restore by double-clicking the name of
the file or directory.
A green light appears when a file or directory is selected.
Green marker--Lets you control the extent of the restore for an object directly. Click
a marker to exclude an object from a restore or to indicate that you want the
restore for the object to be full or partial. As you click the marker, you fill or empty
the marker of color, indicating the extent of the restore.
Gray marker--These markers are associated with objects that are not real and that
you cannot restore. Typically, these items serve as placeholders under which other
objects are grouped and displayed. As you click the green markers under a gray
marker item, the fill proportion of the gray marker changes automatically from
empty to partial to full depending on the proportion of files you have chosen to
restore.
The following table describes the different marker configurations and corresponding
restore levels:
Marker
Configuration
Description
Full restore.
Partial restore.
Empty center.
Do not restore.
Note: Gray marker configurations follow the same pattern as green marker
configurations, but reflect the proportion of files under them that are selected for
restore.
The fill proportion of a marker at a higher level of the directory tree depends on the fill
proportions of the markers of the objects at the lower levels.
If you click a marker at a higher, parent level so that it is completely filled, all the
markers at the lower, child levels are automatically filled completely.
If you click all the markers at the lower, child levels so that they are completely
filled, then the marker at the higher, parent level is automatically partially filled.
If the markers at the lower, child levels are a mix of completely filled and partially
filled, the marker at the higher, parent level is automatically partially filled.
Note: The default method is to restore files to their original location. If you clear the
Restore files to their original location check box, Arcserve Backup presents you with a
list of machines, directories, and files that you can specify for the location to restore the
data.
Every n frequency--Repeat this job every specified number of Minutes, Hours, Days,
Weeks, or Months.
Day(s) of the Week--Repeat this job on the days that are checked off.
Week(s) of the Month--Repeat this job on the weeks that are checked off.
Note: If you select the Run Job Now option when your storage device is busy, Arcserve
Backup reports that the storage device is busy and the job is not submitted to the job
queue. You should schedule your job, keeping the current date and time. This way,
when Arcserve Backup discovers that the storage device is busy, it automatically retries
the job until the drive becomes free.
For a description of detailed job scheduling features, see Customizing Jobs.
From Windows Explorer, locate the executable or application that you want to
specify as Run as administrator.
Right-click the executable or application and select Run as administrator from the
pop-up menu.
Windows prompts you to provide administrator credentials (a user name and a
password).
2.
3.
If you are not logged in as an administrator, enter the administrator user name
and password.
Follow the prompts and complete the required fields to complete this task.
More information:
Authentication Levels for Arcserve Backup Services, Components, and Applications (see
page 527)
Operation options.
Virus options.
Alert options.
Timeout Options--You can specify a timeout period that Arcserve Backup will wait
to provide the media you need to restore your data. Available media options are:
Timeout for First Backup Media--Period of time that Arcserve Backup waits for
the first media required for your restore job. If the time expires, the job fails.
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.
Rename Files--Copy the source file to the destination with the same file name
but a different extension. The format of the renamed extension will vary based
upon the file system that is present on the target partition.
If the length of file name is more than 251 characters, Arcserve Backup
truncates the file name at 251 characters and appends '.__0' to the file
name, after the first restore. For all subsequent restores, Arcserve Backup
appends '.__1', '.__2', and so on to the truncated file name.
If the length of the file name is less than or equal to 251 characters and has
a file extension, Arcserve Backup replaces the last character of the file
extension with the character 1 (for example, filename.tx1). For subsequent
restores, Arcserve Backup replaces the last character of the file extension
with the character 2, 3, and so on. After the 10th restore, Arcserve Backup
replaces the last two characters of the file extension with 10, 11, 12, and
so on (for example, filename.t10). After the 100th restore, Arcserve
Backup replaces the last three characters of the file extension with 100,
101, 102, and so on (for example, filename.100). After the 999th restore,
Arcserve Backup cannot rename the file extension, which causes the
restore to fail. If the length of the file name is less than or equal to 251
characters, and it does not have a file extension, Arcserve Backup appends
'.__0' to the end of the file name. If Arcserve Backup appends '.__0' to the
file name after the first restore, the renaming process appends two
characters after the 10th restore (for example, filename._10), and after the
100th restore, the renaming process appends three characters to the file
name (for example, filename.100). After the 999th restore, Arcserve
Backup cannot rename the file name, which causes the restore to fail.
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 are not copied to
the destination.
Create New File Version--Arcserve Backup will restore all files as new versions
of the original. The files in the target directory will not be affected.
Replace Current File Version--If a file in the target directory has the same name
and version number as a file in the restore data, Arcserve Backup will overwrite
the file.
Restore File Version--If a file in the target directory has the same name and version
number as a file in the restore data, Arcserve Backup will not restore the file. All
other files will be restored with their original names and version numbers.
Restore Registry Files and Event Logs--Restore registry files and event logs to the
restore target machine if the sessions selected for restore have the registry files and
event log files.
The following options apply to only virtual machine restores. These options appear on
the Operation tab only when Recover VM is the restore method specified on the
Restore Manager.
Overwrite VMware VM, if it exists--Lets you overwrite the VM, if the VM exists.
When you restore a VMware VM, Arcserve Backup detects the VMs that reside in
the host system. If the VM exists in the host system, this option lets you overwrite
the VM using the existing UUID of the VM.
Default value: Disabled.
Note: For Hyper-V VMs, the agent always overwrites the VM, if the VM exists in the
Hyper-V host.
Continue the restore job even when the scenario cannot be stopped--Lets you
restore a Arcserve Replication scenario while you are backing up the scenario.
When you attempt to restore a Arcserve Replication scenario while you are backing
up the scenario, by default, the restore job will fail. With this option specified,
Arcserve Backup will complete the restore job while a backup is in progress.
Note: This option appears on the Global Options dialog only when you integrate
Arcserve Backup with Arcserve Replication.
Enter the path to, and name of, the file to be executed on the machine before
the job starts.
Delay in Minutes--Specify the delay that Arcserve Backup waits before running
a job when the specified exit code is detected.
Run Command After Job--Enter the path to, and name of, the file to be executed on
the machine after the job is completed.
Do Not Run Command If--Specify that a command will not run if Arcserve Backup
detects the following events:
Run Command Before Job--Select the following options to run a command on your
machine before the job is executed:
Job Fails--If a job fails, then the command will not run.
Job is Incomplete--If a job is not completed, then the command will not run.
Run Before/After Command As--Specify the User Name and Password that
corresponds to that of the Local Host server selected, and is required to check the
system privileges on that server. The user name and password entered into these
fields should not be confused with the Arcserve Backup User Name and Password.
Log all activity--Record all of the activity that occurs while the job is running.
Note: When you specify Log all activity, Arcserve Backup creates a log file named
JobLog_<Job ID>_<Job Name>.Log. With this log file, you can view detailed logging
information about the job. Arcserve Backup stores the log files in the following
directory:
C\Program Files\CA\ARCserve Backup\LOG
Log disabled--Do not record any information about this job in the job log.
Choose one or more of the defined Alert configurations. The <default> configuration
means that you will use whatever is configured in Alert Manager. Click Configure to
define further configurations. Arcserve Backup provides the following defined Alert
configurations:
Broadcast
Pager
SMTP
SNMP
Event
Printer
Lotus Notes
Unicenter TNG
Select Attach Job Log to include the job log information in the Alert message. (This
option applies for Trouble Tickets and Mail only.)
Note: The list you create using Alert Options is saved with the Job Script and the
configuration defined using the Configuration button.
Make the Restored Copy of the Active Directory Authoritative--Forces the restored
copy to become the authoritative version of Active Directory on the system. This
means that, even if the restored replica set is older than the current replicas, the
older data is replicated to all of its replication partners. Authoritative restore is
typically used to restore a system to a previously known state.
Note: Servers running Windows Server 2008, Windows Server 2008 R2, or Windows
Server 2012 do not support placing the Active Directory in an authoritative mode.
When Restoring replicated data sets, mark the data as primary for all
replicas--Forces the restored File Replication service data to be replicated to other
servers. If this option is not enabled, the replicated data sets may not be replicated
to other servers because the restored data will appear to be older than the data on
other servers.
Select the drive letter in the case the quorum location changed since this
backup--Lets you specify a drive letter to restore data to when the location of
the quorum changed since the backup was performed.
If the node that you want to restore is corrupt or disabled, you must perform a
node restore before you perform an authoritative restore. To perform a node
restore, do not enable this option.
Note: For information about recovering clusters from a disaster, see "Recovering
Clusters" in the Disaster Recovery Option Guide.
Do not Stop World Wide Web Service--Lets you continue the www service while
the certificate server is being restored. The IIS Publishing Service may be using the
certificate service dynamic files at the time of certificate server restore. For this
reason, by default, WWW service will be stopped during certificate server restore. If
you do not want it to stop, use this option.
Restore a Remote Agent on a System without the Disaster Recovery Option (see
page 282).
Restore Arcserve Backup Member Servers without the Using the Disaster Recovery
Option (see page 283).
Best Practices - How to Recover a Stand-alone Server from a Disaster Using the
Disaster Recovery Option (see page 285).
Best Practices - How to Recover a Arcserve Backup Server from a Disaster Without
Using the Disaster Recovery Option (see page 287).
Open the Restore Manager and select the Restore by Tree method.
2.
In the left pane of the Restore Manager, select the volume, drive, directory, or file
you want to restore.
Arcserve Backup searches the database for all backed up versions of this file,
directory, drive, or volume.
Note: When using disk or tape staging, ensure that the staging tape is not offlined
without formatting or erasing the staging tape. This will allow you to view the
session details from the destination (migration) tape.
3.
Click the Recovery Points drop-down list to specify the date of the recovery point
that you want to use for the restore job.
Next, specify the precise recovery point that you want to use for the restore job, as
illustrated by the following example:
4.
5.
Click the Destination tab and specify the location where you want to restore the
data.
6.
Click the Schedule tab and specify a schedule for the job.
7.
(Optional) Click Options on the toolbar to specify any other options that you want
to apply to the job.
8.
Verify that there is one full backup of the remote agent machine, and verify that the
backup media is available.
Record the disk partition/volume configuration, including all volume drive letters
and volume mount points, when the system is up and running.
Ensure the operating system CD, the device drivers, and the Arcserve Backup
installation media are available.
Start the computer you want to recover, using the Windows operating system CD.
2.
Create partitions which are necessary for installing the operating system. Other disk
partitions/volumes can be restored manually after the operating system is installed.
For dynamic disk configuration, it must be restored after the operating system is
installed.
3.
Install the operating system and verify that the host name is the same as the
original system.
4.
5.
Install the device drivers which are not included on the operating system CD. This
includes SCSI/RAID/FC drivers and network adapter drivers.
6.
Configure the network and verify that all configurations are the same as the original
system.
7.
Apply the operating system patch. This is necessary when the system is going to be
connected to the network.
8.
Install the same antivirus software as backup time, and update to the latest patch.
This is necessary when the system is going to be connected to the network.
9.
10. Add this machine to the source node list of the Arcserve backup server if it is not on
the existing node list.
11. Select restore by tree in the Arcserve Backup Restore Manager and submit the
restore job.
Restore Arcserve Backup Member Servers without the Using the Disaster
Recovery Option
This section describes how to restore Arcserve Backup member servers without using
the Disaster Recovery Option.
Important! This procedure does not apply to restoring Arcserve Backup primary servers
and stand-alone servers.
Prerequisite Tasks:
Before proceeding, ensure that the following prerequisite tasks are complete:
Ensure that there is at least one full backup of the system and the backup
media is available.
Ensure that the operating system CD, the device drivers, and the Arcserve
Backup installation media are available.
To restore Arcserve Backup member server without using the Disaster Recovery
Option
1.
Start the computer you want to recover, using the Windows operating system CD.
2.
Create the partitions that are necessary for installing the operating system. Other
disk partitions/volumes can be restored manually after the operating system is
installed. For dynamic disk configuration, it must be restored after the operating
system is installed.
3.
Install the operating system and verify that the host name is the same as the
original system.
4.
5.
Install the device drivers which are not included on the operating system CD. This
includes SCSI/RAID/FC drivers and network adapter drivers.
6.
Configure the network and verify that all configurations are the same as the original
system.
7.
8.
Install the same antivirus software that was running when the last backup
completed and update to the latest patch.
Note: This step is necessary when the system is going to be connected to the
network.
9.
10. Install Arcserve Backup, agents, and options into the same directories as the
original installation.
11. Open the Restore Manager and click the Options toolbar button.
The Options dialog opens.
Click the Operation tab, select the Restore Registry File and Event Log option and
click OK.
The restore options are applied.
12. From the Restore Manager, specify the Restore by tree restore method and submit
the restore job to restore the system.
Restart the system after the restore job is complete.
If the system is not a domain controller, go to Step 17.
13. When restarting the system press the F8 key to start the Windows Server 2003
Expansion Option Menu.
14. When prompted, select Directory Service Restore Mode to start the system in the
restore mode.
15. Restore the System State using the following options:
From the Arcserve server, specify the Global Options for restoring data (see
Step 10).
If the operating system detects that the backed up registry information does
not reflect the currently-used hard disk device, you may need to change the
drive letter assignment. If this occurs, re-assign the proper drive letter.
If a file is required for the system, in addition to the system drive, you may
need to restart the system after the drive letter is re-assigned. If other drives
are data only, restarting the system is not necessary. If you are not sure of the
types of data that reside on the other drives, you should restart the system
after re-assigning the drive letter.
Best Practices - How to Recover a Stand-alone Server from a Disaster Using the
Disaster Recovery Option
The following scenario describes how to leverage the Disaster Recovery Option to
protect a Arcserve Backup server that is hosting SQL Server databases.
Server Specifications
The Arcserve Backup server is configured as follows:
The Arcserve database is hosted using Microsoft SQL Server 2008 Express
Edition.
Software Specifications
The following applications are installed on the Arcserve Backup server:
Microsoft SQL Server 2008 Express Edition as the Arcserve Backup database
Use the following guidelines to recover a Arcserve Backup server that is hosting SQL
Server databases from a disaster:
1.
During the backup operation, ensure that you do not status the SQL Server and SQL
Server 2008 Express instances as offline.
2.
3.
4.
5.
6.
Restore the disaster recovery element sessions for the SQL Server database
instances.
Note: For more information, see the Agent for Microsoft SQL Server Guide.
7.
8.
2.
3.
4.
5.
6.
7.
During and after the recovery process, you will encounter error messages in the
system log and the Arcserve Backup log. These messages are normal under recovery
circumstances and will not result in a loss of data or functionality problems.
When you restore the Arcserve Backup server without using the disaster recovery
option on to the same server, verify that there is enough space available on the
System Reserved Volume. The System Reserved Volume is allocated when installing
Windows Server 2012 with the default size of 350 MB. It is recommended to change
the size to about 490 MB (be careful to keep it less than 500 MB). If you cannot
increase the System Reserved Volume, recover the Arcserve Backup server using
the Disaster Recovery Option or create a new System Reserved Volume.
When creating new System Reserved Volumes, keep in mind that you can create
the System Reserved Volume only on the primary partition of an MBR (Master Boot
Record) disk. When the system volume and the boot volume are combined, the
BitLocker feature cannot be used to encrypt the volumes on your computer.
Follow these steps:
1.
Create a new volume. For example: F:, on the same disk that contains the boot
partition of about 490 MB (verify that the size of the volume is less than 500
MB).
2.
With Windows Server 2012 installed on the C:\ drive, open the DOS command
prompt (run as administrator) and type the following command:
bcdboot.exe C:\Windows /s F:.
3.
Type DISKPART
4.
5.
Reboot your machine and the new System Reserved Volume is created on the
F:.
Note: To revert to your previous configuration, repeat these same steps using the
original system volume by assigning it the drive letter, for example, D:.
To recover the Arcserve Backup server
Important! You must have performed at least one full backup of the Arcserve Backup
server before you can recover the Arcserve Backup server.
1.
2.
Reinstall Arcserve Backup, agents, and options into the same directories as the
original installation.
3.
After you install Arcserve Backup, open the Merge utility and merge the media used
for the last full backup.
4.
After the merge is complete, open the Restore Manager, and verify that the Restore
files to their original location(s) option is selected.
Locate the full backup sessions.
Select the backup sessions for the machine, excluding all the following Arcserve
Backup-specific sessions:
5.
6.
7.
On the Session User Name and Password dialog, complete the fields that follow, as
required, and then click OK.
User Name--Specifies the user name for the target Arcserve Backup server.
Note: You must complete this field on Windows Server 2003 64-bit, Windows
Server 2008, and Windows Server 2012 systems.
On the Session User Name and Password dialog, click Edit to modify the User Name,
Password, and IP address for the selected session.
The Enter User Name and Password dialog opens.
8.
On the Enter User Name and Password dialog, specify the User Name and Password
for the Arcserve Backup server, click the Apply [User Name and Password] to All
Rows check box to apply the user name and passwords specified to all sessions.
Note: When you are editing IP addresses and passwords, you must edit the
individual IP address and session password for each individual session.
Click OK.
The Enter User Name and Password dialog closes.
9.
After you restart Windows Server 2012 systems, the Startup menu may not
appear when you roll the cursor over the Startup menu. When this behavior
occurs, log off and then log in to the computer to display the Startup menu.
When you log in to the operating system, you may receive an error message
asking why the computer was unexpectedly shut down. This is expected
behavior caused by the System State Recovery. If needed, you should select the
appropriate response from the drop-down list and continue.
You may also see the message, "At least one service or driver failed during
system startup. Use Event Viewer to examine the event log for details." In
addition, the service SQL Server (ARCSERVE_DB) cannot start, thus resulting in
the error. This is normal behavior because the SQL Server service does not
recover during this step. This error will be corrected when you complete the
steps in the section Recover the Arcserve Backup database.
If the SQL Server service started and the Arcserve Backup database is not
Microsoft SQL Server 2008, continue to the next task: To recover the Arcserve
Backup database.
If the SQL Server service started and the Arcserve Backup database is Microsoft
SQL Server 2008, do the following:
a.
b.
Start the SQL Server service in single user mode using sqlservr.exe -m.
c.
Using SQL Server Management Studio, log in to the local SQL Server.
From the Object Explorer pane, drill down to <hostname>, [Security], and
[Logins].
Delete the original Windows account.
Example: <hostname>\Administrator
Note: If a message appears that warns you about deleting this account,
you can safely ignore the warning message.
Add a Windows account that you want to use to log in SQL Server.
Example: <hostname>\Administrator
Specify a default language for the database.
Specify [public] and [sysadmin] privileges to this account.
d.
Stop the single user mode for the SQL Server service.
e.
Open the Windows Services Manager and start the SQL Server service.
f.
If the SQL Server service did not start, continue to the next step.
12. Right-click the Data folder and select Properties from the pop-up menu.
The Properties dialog opens.
13. Click the Security tab and then click Advanced.
The Advanced Security Settings for Data opens.
Note: On Windows Server 2008 systems, click Edit on the Data Security Detailed
Settings screen.
14. Click the Permissions tab and select the Replace permission entries on all child
objects shown here that apply to child objects option and click OK.
Note: On Windows Server 2008 systems, click the Replace the existing inheritable
permissions on all descendants with inheritable permissions from this object
option.
If the Arcserve Backup Database is configured such that the database data files are
stored in a different directory, repeat Steps 12, 13, and 14 on this folder to change
its security attributes.
15. Open the Windows Services Manager and start the SQL Server service
(ARCSERVE_DB).
16. Do one of the following:
If the SQL Server service is started, continue to the next task, To recover the
Arcserve Backup database.
If the SQL Server service is not started and you cannot start the SQL Server
service, continue to the next step.
17. Open the Windows Computer Management Console, click Local Users, and then
click Groups.
The following group name should appear:
SQLServer2008MSSQLUser$MACHINENAME$ARCSERVE_DB
Open the Windows Services Manager and start the Arcserve Database Engine
service.
2.
3.
4.
Right-click the Arcserve Database session and select Agent Option from the pop-up
menu.
5.
Click the Restore Options tab, select the Force Restore over existing option, and
click OK.
Note: If you do not choose this option, the restore job may fail, and the Database
Engine will not start. For troubleshooting assistance, see the steps under the
section To Reactivate the existing Arcserve Backup database.
6.
2.
Execute asdbe_start.bat.
Note: The script uses a Microsoft SQL CLI utility "sqlcmd" to run a series of
commands that will bring the Arcserve Backup database online.
After you execute the script, the Database Engine service resumes.
3.
Repeat the steps in the section To recover the Arcserve Backup database.
Note: Verify that you specify the Disable Database Recording and Force Restore
over existing options before you start the job.
After the Arcserve Backup server starts, open the Restore Manager, locate, and
select the Job Queue session.
Note: When you select this session, Arcserve Backup requires a merge job of the
Job Queue session.
Click Yes to continue the recovery of the Job Queue session.
2.
From the Destination tab, specify an alternate location to restore the Job Queue
session.
3.
Click Submit on the toolbar to submit the job to restore the Job Queue session to an
alternate location.
Note: Verify that the alternate location is an empty directory.
4.
After the Job Queue session is restored to the alternate location, open the Server
Admin and do the following:
a.
b.
Right-click the Arcserve Backup server and select Stop all services from the
pop-up menu.
Access the alternate location and copy all Job Queue files under the folder that you
restored to the following directory: ARCSERVE_HOME\00000001.qsd
6.
From the Server Admin, restart all Arcserve Backup services by doing the following:
a.
b.
Right-click the Arcserve Backup server and select Start all services from the
pop-up menu.
2.
Select Directory Service Restore Mode and start the system in the Restore mode.
Start Arcserve Backup.
Error message E3073 occurs:
Unable to logon as user, user =Administrator,EC=Logon Failure or W3073 Unable to
logon as user, user =Administrator,EC=Logon Failure
3.
Go to Step 5.
4.
On the System State Restore Options dialog, click Make the Restored Copy of the
Active Directory Authoritative and click OK.
5.
6.
7.
Windows Server 2008 systems or later--Complete the steps that are described
in Restore Active Directory Objects (see page 583).
To recover Authoritative Active Directory in Windows Server 2008 or later
systems, perform the following steps:
a.
After the System State restore job completes, reboot the Active Directory
server in Directory Service Restore mode.
b.
c.
d.
e.
Error Messages
After you recover the Arcserve Backup server, you may discover errors, warnings, and
failure audits in the system Event Log similar to the error messages listed below,
depending on how your system is configured. Such messages are caused by the
intermediate state of recovery, or are related to the startup order in which Arcserve
Backup and the SQL Server services started.
Arcserve Backup may report the following errors during the intermediate state of
recovery.
Error 8355
This error message is reported when a "service broker" disabled setting is detected
in the MSDB that was recovered. You can safely ignore this error because this is the
default behavior of a system database recovery that is limited to SQL Server 2008
Express Edition. SQL Server 2000 and SQL Server 2005 are not affected by this
behavior.
You can suppress this error by doing the following:
1.
2.
For example:
C:\Users\Administrator>sqlcmd -S localhost\ARCSERVE_DB
3.
4.
5.
Arcserve Backup corrects the following error conditions after the recovery process is
complete:
Error 615
This error message is reported when the 'master' database is restored during
recovery without using the Arcserve Backup Disaster Recovery Option and SQL
Server is hosting a single Arcserve Backup database. This error may not occur when
SQL Server 2008 Express Edition hosts the Arcserve Backup database.
The Arcserve Backup Agent for Microsoft SQL Server will not back up the tempdb
database even when a full instance is selected. Tempdb is also excluded by the
Arcserve Backup server and file system agent when the normal file system is backed
up. However, tempdb is recorded as an existing database in the SQL Server master
database, so when the master is restored, the SQL Server service reports that it
cannot find tempdb.
Error 15466
This error message is reported when the system state is restored during recovery
without using Arcserve Backup Disaster Recovery Option. Either SQL Server 2008
Express Edition or SQL Server can host the Arcserve Backup database.
When you recover the Arcserve Backup server without using the Disaster Recovery
Option, the Windows operating system and SQL Server are reinstalled, and the
Service Master Key (SMK) of SQL Server is created. The Service Master Key (SMK) is
used to encrypt all database master keys and all server-level secrets such as
credential secrets or linked server login passwords.
They key is a 128-bit 3DES key. The SMK is encrypted using DPAPI and the service
account credentials. When the system state is restored but SQL Server sessions
have not yet been restored, the system state is overwritten by the restore
operation. However, the SQL Server instance is not yet overwritten. The SMK is in
the system state, so it has been recovered to the old one, which is therefore
inconsistent with the SQL Server instance. At this time, the recovery procedure
requires that you restart the operating system.
During the restart, SQL Server reads the SMK and checks it against the SQL
database. Because the SMK and SQL Server database are inconsistent, the error
occurs.
Error 17113
This error message is reported when the user permission settings for either the file
or its containing folders are incorrect. Using the procedures described in this topic,
you will adjust these permissions. The error will be corrected after you adjust the
permissions.
Errors not related to the recovery process
If the Arcserve Backup services and SQL Server services do not start in the proper
sequences, SQL Server error messages may appear in the system log. This behavior
is a known issue. For more information, see the readme file.
Restore by Session
Within this view, you can manually delete a selected session.
Restore by Tree
Restore by Media
Note: For more information about restoring data, see "Restoring Data."
Rotation schedules let you to define standard and consistent intervals at which to
rotate and retire backup media.
Filters let you select the files and directories to be included in (or excluded from)
your backup and restore jobs based on a wide variety of criteria.
Scheduling options provide you with the ability to schedule your jobs to run
immediately, later, or on a regular basis.
The Job Scheduler Wizard is a powerful tool that lets you quickly and easily
schedule and submit any job that can be entered at the command line.
The Job Status Manager is a graphical tool that helps you centrally manage
Arcserve Backup servers enterprise-wide.
Job scripts allow you to save the options, filters, and scheduling information you
define for your job as a file, so you can re-use, copy, or efficiently resubmit jobs
with these settings.
Job templates let you use preconfigured settings to submit jobs on any machine
running Arcserve Backup without having to repeat the set up detail tasks for each
job. The job template copies your configured backup schedule settings to be used
again in the future on any machine.
Note: For more information, see Dynamic Job Packaging (see page 302).
Open the Backup Manager and dynamically package a backup job. For example,
2.
Right-click the machine or disk that you do not want to back up, and then click
Exclude This Item on the pop-up menu.
(Excluded) appears next to the machine or disk name.
3.
2.
Click the Start tab and specify the backup type that you require for the job.
3.
4.
5.
Microsoft SQL Server Express Edition databases--Clear the check box next to
Arcserve Backup Database.
The Arcserve Backup database is excluded from source for the backup job.
6.
Click the Schedule tab and specify the schedule that you require for the job.
7.
Click the Destination tab and specify the destination that you require for the backup
data.
8.
Click Options on the toolbar and specify additional options that you require for the
job.
9.
Arcserve Backup backs up the entire backup server and does not back up the Arcserve
Backup database.
Drive e:\ was appended to the computer after the job completed. The next time the
job runs, Arcserve Backup backs up drive c:\ and drive d:\. Drive e:\ is not backed
up.
Directory c:\documents was appended to drive c:\ after the job completed. The
next time the job runs, Arcserve Backup backs up all of drive c:\, including
c:\documents, and drive d:\.
Drive d:\ was deleted from the computer after the job completed. The next time
the job runs, Arcserve Backup backs up drive c:\ and reports a failed backup of drive
d:\.
A source group contains computers A, B, C, and D when you submit the job. Computer A
contains drive c:\.
Computer E was added to the source group after the job completed. The next time
the job runs, Arcserve Backup backs up computers A, B, C, and D. Arcserve Backup
does not back up computer E because it was not included in the original source
group.
Drive d:\ was appended to computer A after the job completed. The next time the
job runs, Arcserve Backup backs up computers A, B, C, and D and drive d:\ in
computer A. Arcserve Backup behaves in this manner because computer A was
included in the original backup source group, and Arcserve Backup backs up the
volumes in the source group dynamically.
Note: For more information, see Submit Static Backup Jobs (see page 198).
2.
Right-click the source group or server that you want back up statically, and click
Enable Static Backup on the pop-up menu.
(Static Backup) appears next to the group or machine name.
3.
Convert Jobs Submitted Using the Classic View to the Group View
Arcserve Backup lets you browse source data and submit jobs in two view formats:
Classic view--Lets you browse source data and submit jobs based on the operating
system that is running on the source computers. For example, Windows,
UNIX/Linux, and so on.
Group view--Lets you browse source data and submit jobs based on the Arcserve
Backup agents that are running on the source computers. For example, Agent for
Microsoft Exchange, Agent for Microsoft SQL Server, and so on.
Submitting jobs using the Group View is a convenient method of submitting jobs. The
Group View lets you submit backup jobs that include specific agents. However, you
cannot change the view that you specified when you submitted the job (Classic View to
Group View and vice versa) after you submitted the job.
If you upgraded to this release, all of the jobs that you submitted using the previous
release are packaged in the Classic View. The following steps describe how to convert
jobs that were submitted using the Classic View to jobs that were submitted using the
Group View.
Rotation Schemes
Open the Job Status Manager and click the Job Queue tab.
The jobs in the Job Queue appear.
2.
3.
(Best practice) In the Group Name field, accept the default name provided or
specify a new name for the group.
Click OK.
From the Group Name drop-down list, select a name for the group and click
OK.
The Duplicated Source Notification dialog opens only when both of the
following conditions occur:
One or more nodes in the job that you want to convert are included with
full backup jobs that are configured as scheduled, repeating, or GFS
rotation jobs.
The group name specified, which is an existing group, is included with full
backup jobs that are configured as scheduled, repeating, or GFS rotation
jobs.
If you are sure that you want to use the group name specified, click Yes.
The job is converted.
Rotation Schemes
This section describes how to configure a rotation scheme for a backup job by using the
Arcserve Backup default scheme or by specifying your own rotation parameters. To
access the parameters for configuring a rotation scheme, select the Schedule tab in the
Arcserve Backup Manager. The parameters that you can use are described below.
Scheme Name--Select the type of rotation scheme you want, based on 5 or 7 days,
and incremental, differential, or full backups. For more information on these
standard schemes, see Calendar View Tab (see page 311) to modify your rotation
scheme.
Rotation Schemes
Append Media--If you specify the Enable GFS option, you can direct Arcserve
Backup allow data from GFS rotation to append to existing jobs on the media.
Daily Backup Method--The Daily Backup Method option lets you specify one of the
following options for your daily backup jobs:
Full--All source files are backed up. This backup method clears the archive bit.
Incremental--Files that have changed since the last backup are backed up. This
backup method clears the archive bit.
Differential - Archive Bit--Files that have changed since the last full backup job
are backed up. This backup method does not change the archive bit.
Use WORM Media--The Use WORM Media option lets you direct Arcserve Backup
to use WORM media for all rotation rules. With this option enabled, you have the
capability to use WORM media for daily, weekly, and monthly GFS backup jobs.
Important! Arcserve Backup does not support the use of WORM media for
multiplexing and multistreaming backup jobs. As a result, when you enable the
Multiplexing option or the Multistreaming option on the Destination tab of the
Backup Manager, the Use WORM Media option is disabled.
More information:
Calendar View Tab (see page 311)
Rotation Schemes
How You Can Manage GFS Rotation Jobs on File System Devices
Arcserve Backup supports using a GFS rotation scheme on File System Devices. A
retention period for the media being used in the GFS rotation scheme can be
determined using the following default retention cycle for a seven-day weekly rotation:
Frequency
Number of Media
Daily
Weekly
Monthly
12
Total
23
To run a rotation job beyond a year, a GFS rotation scheme requires 23 File System
Devices to be created. These settings can be modified to meet your specific needs.
Modifying the default values of the GFS rotation may change the number of FSDs
required.
Note: Previously, only local disks were considered FSDs. You can now create FSDs that
are accessible through a network share using a Universal Naming Convention (UNC)
path.
Because a GFS rotation job may be using local disk drives and drive arrays, users must
first make sure that there is enough space on the particular file system to store all the
data being backed up for the entire retention period. Creating file system devices on a
boot partition is not recommended because a boot disk that becomes full can cause the
operating system to function abnormally.
Note: All file system devices need to be assigned to the same device group.
A configured GFS rotation job can run on a daily basis at a specified time. Arcserve
Backup utilizes file system devices similar to a physical tape. As needed on a daily basis,
Arcserve Backup moves tapes between the save sets and the scratch sets in the media
pools, formats blank media, overwrites expired media, and tracks all operations in the
database.
You can choose to duplicate backup data stored on the file system devices to physical
tape media. The Job Scheduler Wizard and the Tapecopy utility provide the ability to
automate the creation of the duplicate images.
The following sections describe the tabs available to customize your rotation job.
Rotation Schemes
From the Backup Manager, select a source and destination, and click the Schedule
tab.
2.
Enable the Use Rotation Scheme option. From the Scheme Name drop-down menu,
choose one of the backup schemes.
Note: The Enable GFS option is automatically checked when a GFS scheme is
selected.
3.
If you want to add the data from one incremental or differential backup session to
the same media as the previous backup session, enable the Append Media option.
4.
In the Media Pool Name Prefix field, enter the prefix for all of your media names.
Arcserve Backup automatically creates and names your backup media using the
name you designate.
Note: Arcserve Backup prevents you from using the underscore character ( _ ) and
the hyphen character ( - ) when specifying Media Pool names.
5.
6.
Rotation Schemes
Note: This feature enables you to specify exceptions to the standard rotation scheme
you are using.
Exceptions Tab
Define particular days on which the backup method and the execution time or date
differs from the pre-existing schemes.
Media Tab
View information about the media pool you selected, including name, base serial
number, next serial number, serial number range, minimum number of media, retention
time, and prune retention time. You can also click the Daily, Weekly, or Monthly boxes
to change the number of required media per year.
Files accessed, modified, and created before, after, between, or within a specific
date range.
Arcserve Backup uses wildcards or substitute characters, except when it detects that an
absolute path is specified. If a valid absolute path is specified, Arcserve Backup will only
exclude (or include) the absolute path specified, rather than excluding (or including)
more directories, as it would for regular expression.
The wildcard characters supported for job filters based on file name or directory name
are as follows:
"*" --Use the asterisk to substitute zero or more characters in a file or directory
name.
"?" --Use the question mark to substitute a single character in a file or directory
name.
Important! Exercise caution when specifying filters for your backup or restore
operation. Incorrectly applied filters may not back up or restore the data you need, and
can result in lost data and wasted time.
Examples: Back Up Data Using Wildcards
The following table describes examples of how you can use wildcards in conjunction
with filters to back up data.
Note: The following examples assume that the source data resides in drive C:\.
Filter
Results
File
Include *.doc
File
Exclude *.doc
File
Include ?.doc
Filter
Results
File
Include
File
Exclude/Include
C:\DOC\C*
Directory
Include m*t
Directory
Exclude win*
Directory
Filter Options
You can access the filter options from the Backup Manager, Restore Manager, Copy,
Count, Scan, Compare, and Purge Utility windows.
Include filters--Results contain only those files that satisfy the filter specifications.
For example, suppose you selected to back up your entire local hard drive, and you
then set up a filter to include files in the \SYSTEM directory. The result would be
that Arcserve Backup would only back up files from your \SYSTEM directory. No
other files would be backed up.
Types of Filters
Filters are available which enable you to include and exclude files to suit your needs.
The following list describes the types of filters that you can use to filter data.
File Pattern Filter--Use the File Pattern filter to include or exclude files from a job.
You can specify a particular file name or you can use wildcards to specify a file
pattern.
Note: Wildcards "*" (asterisk) and "?" (question mark) can be used in the file
pattern filter.
File Attributes Filter--Use the File Attributes filter to include or exclude specific
types of files from a job. Select as many of the following types of file attributes as
you want:
File Modified Filters--Use the files last modified attribute to include or exclude files,
based on the time they were last changed. There are four options from which to
choose:
Before--Files whose date matches, or whose date is earlier than this date, are
included or excluded.
After--Files whose date matches, or whose date is later than this date, are
included or excluded.
Between--Files whose date falls between the two dates are included or
excluded from the job. You must specify two dates for this selection.
Within--Files whose date falls within the specified time are included or
excluded from the job. You must specify the number of days, months, or years.
File Created Filters--Use the files last created attribute to include or exclude files
based on when they were created. There are four options from which to choose:
Before--Files whose date matches, or whose date is earlier than, this date is
included or excluded.
After--Files whose date matches, or whose date is later than, this date is
included or excluded.
Between--Files whose date falls between the two dates are included or
excluded from the job. You must specify two dates for this selection.
Within--Files whose date falls within the specified time are included or
excluded from the job. You must specify the number of days, months, or years.
File Accessed Filters--Use the file last accessed attribute to include or exclude files
based on when they were last accessed. There are four options from which to
choose:
Before--Files whose date matches, or whose date is earlier than, this date is
included or excluded.
After--Files whose date matches, or whose date is later than, this date is
included or excluded.
Between--Files whose date falls between the two dates are included or
excluded from the job. You must specify two dates for this selection.
Within--Files whose date falls within the specified time are included or
excluded from the job. You must specify the number of days, months, or years.
File Size Filters--Use the file size attribute to include or exclude files based on the
specific size of the file. You can specify a size range from 0 to 99999999999 bytes,
KB, MB, or GB. There are four options from which to choose:
Equal to--Files whose size matches the size range are included or excluded
from the job.
Greater than--Files whose size matches or whose size is greater than the size
range are included or excluded from the job.
Less than--Files whose size matches or whose size is less than the size range
are included or excluded from the job.
Between--Files whose size falls between the two sizes are included or excluded
from the job.
Effective with this release, two new types of filters have been added:
Node name pattern-- Only nodes whose name meets the pattern are included for
backup. You can specify all or part of a search string using wildcards.
Node subnet pattern--Only the node whose IP address is in the subnet is backed
up.
The job you are submitting is a one time only job that you want executed
immediately.
You are submitting a single occurrence job but and you want it to run at a specific
time.
You are submitting a single occurrence job, but you do not want to run it now. You
want to submit the job on Hold, and start it manually at a later time.
You are submitting a job that should run regularly. This is especially useful for
setting up a media rotation scheme for your network.
You are submitting relatively low volume, daily, full backups. With custom
schedules, Arcserve Backup lets you specify the Append days option. The Append
days option helps to maximize the amount of data stored on tape and minimize the
number tapes that need to be stored, relative to a job.
Your storage device is 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.
Important! All scheduled times for Arcserve Backup jobs are based upon the time zone
where the Arcserve Backup server is located. If your agent machine is located in a
different time zone than the Arcserve Backup server, you will need to calculate the
equivalent local time that you want the job to start.
Custom Schedules
Custom Schedules
You can select a custom schedule on the Schedule tab in the Backup Manager. A custom
schedule enables you to run a backup job either once or on a repeating basis. You can
specify the following parameters for backup and restore jobs:
Repeat Method--All jobs can be scheduled using the Schedule options available in
each Manager. Jobs can be submitted with a repeat method of:
Day(s) of the Week--Repeat this job on the days that are checked off.
Week(s) of the Month--Repeat this job on the weeks that are checked off.
Note: This method is not available for synthetic full backup jobs.
Custom--Repeat this at the specified interval, but exclude the days that are
checked.
Note: This method is not available for synthetic full backup jobs.
Append days option--The Append days option lets you append backups to one tape
for the number of days that you specify. This option helps to maximize the amount
of data stored on tape, and minimize the number tapes that need to be stored
relative to a job. As a best practice, you should use this option when you perform
relatively small volume, daily full backups. However, you can apply this option to all
custom backup schedules except for run Once backup jobs and
grandfather-father-son rotation jobs.
Note: The Append days option cannot be applied to jobs where the destination
device is data deduplication devices or cloud devices. In addition, with the Append
days option applied to the backup, Arcserve Backup ignores the First Backup Media
(global options) applied to the job. For more information about First Backup Media
option, see Backup Manager Backup Media Options (see page 164).
Backup Method--This specifies what data will be backed up. Jobs can be submitted
with a backup method of:
Full (Keep Archive Bit)--Performed each time the job is repeated and keeps the
archive bit.
Full (Clear Archive Bit)--Performed each time the job is repeated and clears the
archive bit.
Incremental backup--Backs up only those files whose archive bit have been set
since the last full or incremental backup was performed. After each backup,
archive bits are reset so that they are not backed up during the next
incremental backup job.
Differential backup--Backs up only those files whose archive bits have been set
since the last full backup was performed. Because differential backup jobs do
not clear a files archive bit, the files that were backed up in the last differential
job are backed up again. Using this backup method, 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 will
probably require fewer media to restore your machines.
Note: For a synthetic full backup job, if the agent supports synthetic full
backups, the differential backup job is converted to an incremental backup job.
Use WORM Media--Directs Arcserve Backup to use WORM media when the backup
job runs.
View all available Arcserve Backup servers, job history, job queues, and activity logs.
Manage jobs--stop, add, run, delete, modify, reschedule jobs, and place jobs in a
hold status.
Monitor the progress of active jobs that are running on Arcserve Backup primary
servers and member servers. You can view the real-time status of active jobs in the
queue.
View job detail and job log information about all the jobs that have been executed.
Pop-up menus enable you to perform various operations with the Job Status Manager.
These menus appear in both the left (server browser) and right (Job Queue) panels. To
access a menu, right-click a selected item. When accessing a pop-up menu in the
browser, the pointer must be on a selected group, server, or object. When accessing a
pop-up menu in the Job Queue, a job must be selected.
Note: When you submit a job that spawns child jobs, the Job Queue tab displays details
about the master job only. The Activity Log tab displays details about the master and
child jobs. The Activity Log presents you with a description for the job.
Important! When you are executing a multistreaming, multiplexing, or disk staging job,
the number of child jobs associated with a master job will never exceed the number
streams specified for the job. However, if a job spawns multiple child jobs and the value
specified for the Multiplexing Max # of Streams option is one, the child jobs will be
created and backed up in one continuous stream (the default Max # Stream is four).
More information:
Preflight Checks for Your Backups (see page 126)
Open the Job Status Manager and select the Job Queue tab.
Locate the jobs with pending data migration jobs and click Data Migration Status.
The Migration Job Status <Backup Server Name> dialog opens as illustrated by the
following screen.
2.
Locate and click the sessions that you want to modify and click Modify.
The Migration Job Configuration dialog opens.
3.
Copy Time--Lets you specify the date and time that you want to start the
migration job.
Note: If you do not want to migrate the backup data to final destination media,
clear the check box next to Do not copy data.
4.
Purge Time--Lets you specify the date and time that you want to purge the
backup data from the staging device.
Target--Lets you specify the group containing the final destination media.
Apply to the selected rows--If you selected more than one session on the
Migration Job Status dialog, this option lets you apply the Copy Time, Purge
Time, and Target options that you specified to all of the sessions selected on
the Migration Job Status dialog.
Click OK.
Note: You can also view the pending migration jobs associated with a staging location by
completing the following steps:
1.
Open the Backup Manager and select Enable Staging on the Start tab.
2.
3.
4.
Click the Data Migration Status on the pop-up menu to open the Migration Job
Status dialog.
The dialog lists all pending migration jobs associated with the selected staging group or
device. For example, the dialog lists pending migration jobs that will migrate data from
the selected staging group or device.
More information:
How You Can Reclaim Disk Space (see page 229)
Back Up Data Using Tape Staging (see page 236)
From the Job Status Manager, select the Job Queue tab.
2.
To select multiple adjacent jobs, press and hold the Shift key as you select the
jobs.
To select multiple non-adjacent jobs, press and hold the Ctrl key as you select
the jobs.
3.
4.
From the pop-up menu, select HOLD, READY, or Delete Job as warranted by the
situation.
Add Job--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.)
Run Now--Available for jobs that have a Ready or Done status. This option is useful
in the following scenarios:
You want to run a job earlier than the time it is scheduled to run
A scheduled job did not run because of a hardware problem and you want to
run it immediately after the problem is fixed
If a device group is available, this option runs the job immediately. If you select Run
Now and a device group is not available, the job stays in the queue and waits for a
group to become available.
If you select the Run Now option for a repeating, rotation, or GFS rotation job, the
following conditions apply:
The job runs immediately and the existing schedule is not affected unless the
time it takes to run the job overlaps with the next scheduled run. In this
scenario, the scheduled run is skipped for that day. For example, if you have a
job scheduled to run Monday through Friday at 9:00 p.m., you select Run Now
at 6:00 p.m. and it does not finish till 10:00 p.m., the 9:00 p.m. scheduled run
for that day is skipped.
The backup method used for the job is the same backup method that will be
used for the scheduled run that day. For example, if you have an incremental
backup job scheduled for 9:00 p.m. and select Run Now at 6:00 p.m., the job
that runs at 6:00 p.m. will be an incremental backup. If you select Run Now on
a day that does not have a scheduled run, the backup method of the next
scheduled job will be used. For example, if you have an incremental job
scheduled to run Monday and you select Run Now on Saturday, the job that
runs on Saturday will be an incremental backup.
Stop Job--Cancels an active job from the Arcserve Backup queue and reschedules it
for its next regular interval.
Note: If you stop a job, the Last Result field displays Canceled.
Delete Job--Cancels the job and deletes it from the Arcserve Backup queue
completely.
You cannot use the Delete Job option on an active job. Use the Stop Job option if
you want to delete an active job that repeats at intervals (determined when you
create the job). Selecting the Delete Job button will interrupt and remove the job
completely from the queue, and it will not be rescheduled. You will have to recreate
the job if you did not save it to a script file.
Note: Arcserve Backup lets you re-create the Arcserve Backup database protection
job and the database pruning job in the event they are deleted intentionally or
unintentionally. For more information, see Re-create the Arcserve Backup Database
Protection Job (see page 625) and Re-create the Arcserve Backup Database Pruning
Job (see page 328).
Modify User Name--Modify the user name and password for server and source
nodes.
Preflight Check--Runs vital checks on the Arcserve Backup server and agents to
detect conditions that may cause backup jobs to fail.
Sort By--Jobs in the queue are listed in order of execution time. This option changes
the order in which jobs are listed in the queue. Sorting the Job Queue is for
informational purposes only. It does not affect the order in which jobs are
processed. To sort jobs, click any of the following fields: Status, Execution Time, Job
Type, Server, Last Result, Owner, Total Files, and Description.
Note: 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.
Ready--A new one-time or repeating job (a backup job that runs every Friday, for
example) waiting to be executed.
Hold--A job that is in the queue and was placed in a hold status.
Note: A job with a hold status will not execute until you remove the hold status.
Waiting for Target--A job that is ready to execute and is waiting for the target
device, media, or both to become available. A device or media may not be
available, for example, because it is busy with another job. To determine the
specific reason why a job is waiting for a device, click the Waiting for Target
hyperlink to open the Target Group Status dialog.
The Target Group Status dialog represents stream-based backups or device-based
backups.
The Target Group Status dialog describes the information that follows:
Title bar--Displays the name of the backup server, the job number, and the job
ID of the job that you clicked in the Job Status Manager.
Backup Server--The name of the backup server using the listed device.
Job No.--The job number that is using the listed device, if available.
Waiting for source group--A migration job is waiting for a source group to be
available.
Waiting for source tape--A migration job is waiting for the source tape to be
available.
Waiting for target tape--A job that should be active, but it is not because it is
waiting for the target device or media.
Positioning source tape--A migration job is waiting for the source tape to be
positioned in the drive.
Positioning target tape--A migration job is waiting for the target tape to be
positioned in the drive.
Note: Completed jobs remain listed in the Job Queue for a specified number of hours.
This period of time is set up through the Arcserve Backup Server Admin. For more
information, see Job Engine Configuration (see page 500).
Incomplete--The job was partially successful. Review the Activity log information to
check the exact nature of what occurred to prevent job completion.
Canceled--The job was intentionally canceled. The following actions may have
occurred:
Failed--The job failed to perform its designated task. This usually occurs if Arcserve
Backup cannot back up any source nodes of a job (for example, if the agent is not
loaded or an invalid password was entered) or if a hardware error occurs. If the job
was started, but the Manager could not complete the job, you will receive Run
Failed status. Review the Activity log information to check the exact nature of what
occurred to prevent the job from completing.
Run Failed--The job was started, but the program that runs the job failed, because
either there was not enough memory to run the job or a DLL file was not found.
Crashed--The job was started and a system error occurred which prevented
Arcserve Backup from completing its task, such as a memory violation that caused
Arcserve Backup or the operating system to be shut down. If a job has a status of
Crashed, it can be retried after the Job Engine restarts. This can be set up through
the Arcserve Backup Server Admin in the Job Engine Configuration tab.
Start the Arcserve Backup Server Admin and click the Configuration toolbar button.
The Configuration dialog opens.
2.
3.
4.
Click OK.
The database pruning job is submitted to the job queue and will run at the specified
time.
Type of job
When you install the Central Management Option, you can view Activity Log data as is
relates to the domain primary server, a domain member server, or both.
The following diagram illustrates that the Central Management Option is installed,
domain member server MEMBER01 is selected, and the activity log details for the
MEMBER01 display.
Group by Week (if checked) is always the first level group. The date comes from the
operating system's setting.
The Generic Log appears at the end of the master job list. It contains the logs that do
not belong to any job.
Note: If you do not install the Central Management Option, the Activity Log displays
data relating to the Arcserve Backup server that you are currently logged in to.
You can scan this log every day to see if any errors occurred. You can also use it to find a
session number in case you need to restore a specific session. You can organize the
Activity log view or print it to a file.
Open the Job Status Manager and select the Activity Log tab. Click the Delete
toolbar button.
The Delete dialog opens.
2.
Select the criteria you want to apply in the Delete dialog. Chose one of the
following options:
PartialLets you select specific logs based on a time period. You can choose
from the following criteria:
3.
Click OK.
A caution dialog appears.
4.
Click OK.
The Activity log files are deleted.
You can also use the command line interface to purge job logs (or any other log file)
from the Activity log. Use the ca_log -purge command to delete logs older than a
specified period of time from any log file. You can also use the ca_log -clear command if
you want to delete all log data from log files with no specified time period.
Note: For more information about the ca_log command, see the Command Line
Reference Guide.
Type: All
Session: blank
Keywords: Message
Open the Job Status Manager and select the Activity Log tab.
2.
Expand the Log Query Bar. By default the Log Query Bar is collapsed.
The Log Query Bar opens.
3.
View--Specify how you want to group the activity log messages. You can group
by week, type and job.
The Group by Week lets you group the activity log messages by the week
(default).
The Group by Jobs option, lets you group the Activity Log with the parent
job together with all of its child jobs. For each parent job and its
corresponding child jobs, the Activity Log presents you with a description
for the job (default).
The Group by Type option lets you group error messages, warning
messages, and information messages.
Job status--Specify the types of jobs that you want to view in the Activity Log.
You can view All, Finished, All unsuccessful, Canceled, Failed, Incomplete,
Crashed and Unknown.
Message type--Specify the types of messages that you want to view in the
Activity Log.
You can view All, Error, Warnings, Errors and Warnings, Informations, Errors
and Informations, and Warnings and Informations.
Date--Specify a date or range of dates of messages that you want to view in the
Activity Log.
You can show all messages, filter messages such that only messages before or
after a specified date display, or display a specific range of dates.
4.
Keywords--Sort the activity log by keywords. You can specify Job Name or
Message.
Click Update.
The Activity Log displays the results according to the specified query.
Note: To get the latest jobs, with the existing filters, click Refresh on the toolbar or
F5.
More information:
Tape Engine Configuration (see page 503)
Log all activity--Record all of the activity that occurs while the job is running.
Note: When you specify Log all activity, Arcserve Backup creates a log file named
JobLog_<Job ID>_<Job Name>.Log. With this log file, you can view detailed logging
information about the job. Arcserve Backup stores the log files in the following
directory:
C\Program Files\CA\ARCserve Backup\LOG
Group View
Note: The default view is Group View.
Classic View
Based on the view option that you specified, do one of the following:
Group View--Right-click one of the group objects in the browser (for example,
the Microsoft SQL Server, Microsoft Exchange Server, and Oracle Server
objects) and select Add/Import/Export Agents from the pop-up menu.
Note: If the group specified is Arcserve D2D Servers, click Add/Import/Export
D2D Servers on the pop-up menu.
Classic View--Right-click one of the classic objects in the browser (for example,
the Windows Systems object) and select Add/Import/Export Nodes from the
pop-up menu.
Note: If the classic object specified is Arcserve D2D Servers, click
Add/Import/Export D2D Servers on the pop-up menu.
The Add/Import/Export dialog opens. Any any existing computers are populated in
list of computers that will be added to the Source tree as viewed in the right-pane.
3.
Add the computers to the list in the right-pane, which will be added to the Source
tree. This can be done in the following ways:
Specify the host name or host name (IP address) of the computers that you
want to add in the text box and click Add.
The best practice is to specify the host name and the IP address of the target
system. This approach helps ensure that Arcserve Backup can accurately detect
the target system, based on its IP address, and display the system under the
Windows Systems object.
Note: If you specify only the host name, Arcserve Backup sets the IP address
value to 0.0.0.0.
Note: For more information, see Add Multiple Computers Using .csv and .txt
Files (see page 337).
The computers that will be added to the Backup Manager Source tree are displayed
in the right-pane list.
4.
(Optional) Click Delete or Delete All if necessary to remove items from the
right-pane list.
The Delete and Delete All buttons are only enabled if you select a node or multiple
nodes in the right-pane list. If the computer was originally entered in the text box or
imported from a .csv or .txt file, and you click Delete, the computers will be
removed from the right-pane list. If the computers were detected by
auto-discovery, and you click Delete, the computers display in the left-pane list of
computers detected by auto-discovery.
5.
Select the computers in the right-pane list for which you want to enter a user name
and password, and then click Security.
(Optional) From the list of computers that will be added to the Source directory
tree, double-click the Host name or Address value of the target system.
The Security dialog opens where you can add the user name and password for
multiple nodes and agents at one time. The nodes and agents displayed on the
Security dialog are provided from the right-pane list on the Add/Import/Export
dialog.
6.
7.
(Optional) Select a node or agent in the left-pane list and click Properties.
The Server Properties dialog opens and displays the Domain name, Server name, IP
address, Last response time, and Products installed. These properties are detected
by the auto-discovery service, so the Properties button will only be enabled when
you select a node or agent in the left-pane list and click Properties.
8.
Click OK.
If Arcserve Backup cannot access the newly added computers, the Add Agents
Result dialog opens.
Be aware of the following:
The Add Nodes Result or the Add D2D Servers Result dialog opens when adding
Nodes or Arcserve D2D Servers.
The result dialog provides you with a list of computers that Arcserve Backup
cannot access and the corresponding reason (Status) for each computer. If the
reason for the failure relates to security credentials, the result dialog lets you
modify the user name and password that Arcserve Backup requires to log in to
the computer. Follow the on-screen instructions on the result dialog to add the
computers and click OK.
The computers are added to the Backup Manager Source tree. If an existing
computer was deleted, it will be removed from the Backup Manager Source tree. If
a computer name is duplicated, you will see a warning message indicating that this
is a duplicate name and computer will not be added to the Source tree. In addition,
Arcserve Backup lets you add multiple host names with the same IP address.
Add Multiple Agents and Nodes Using .csv and .txt Files
The Import function lets you add multiple computers (for example, nodes, agents, and
Arcserve D2D Servers) using the Arcserve Backup user interface by importing them from
a .csv or a .txt file.
Note: A .csv file is a file that uses a comma-separated value format.
To add computers using .csv and .txt files
1.
Group View
Note: The default view is Group View.
Classic View
Group View--Right-click one of the group objects in the browser (for example,
the Microsoft SQL Server, Microsoft Exchange Server, and Oracle Server
objects) and select Add/Import/Export Agents from the pop-up menu.
Note: If the group object specified is Arcserve D2D Server, click
Add/Import/Export D2D Servers on the pop-up menu.
Classic View--Right-click one of the classic objects in the browser (for example,
the Windows Systems object) and select Add/Import/Export Nodes from the
pop-up menu.
Note: If the classic object specified is Arcserve D2D Server, click
Add/Import/Export D2D Servers on the pop-up menu.
Click Import.
The Windows Open dialog opens.
4.
Browse to the file containing the list of computers that you want to import and click
Open.
The computers added to the right-pane list on the Add/Import/Export dialog.
5.
Select the computers in the right-pane list for which you want to specify user name
and password and then click Security.
The Security dialog opens. The Security dialog lets you add the user name and
password for computers at one time. The computers displayed on the Security
dialog are provided from the right-pane list on the Add/Import/Export dialog.
6.
Click OK.
The computers are added to the Backup Manager Source tree.
Group View
Note: The default view is Group View.
Classic View
Group View--Right-click one of the group objects in the browser (for example,
the Microsoft SQL Server, Microsoft Exchange Server, and Oracle Server
objects) and select Add/Import/Export Agents from the pop-up menu.
The Add/Import/Export Agents dialog opens.
Classic View--Right-click one of the classic objects in the browser (for example,
the Windows Systems object) and select Add/Import/Export Nodes from the
pop-up menu.
The Add/Import/Export Nodes dialog opens.
3.
Click Export
The Export dialog opens.
4.
Select the agents or nodes that you want to export to a text file.
Note: By default, all agents or nodes are selected for you.
5.
(Optional) Click Select All or Clear All to select or clear the agents and nodes in the
list that you want to export.
6.
Click OK.
The Windows Save As dialog opens.
7.
Group View
Note: The default view is Group View.
Classic View
3.
2.
3.
From the Agent Option dialog, clear the Use computer name resolution check box.
Enter a Host name and an IP address.
Click OK.
The new IP address, host name, or both are applied to the agent or node.
Group View
Note: The default view is Group View.
Classic View
2.
Group View--Select and right-click the agent that you want to delete.
Classic View--Select and right-click the node that you want to delete.
Click Yes.
The agent or node is deleted.
The commands you can enter are not limited to Arcserve Backup. You can use this
wizard for virtually any executable, such as Notepad.exe.
Important! All scheduled times for Arcserve Backup jobs are based upon the time zone
where the Arcserve Backup server is located. If your agent machine is located in a
different time zone than the Arcserve Backup server, you will need to calculate the
equivalent local time that you want the job to be run.
When you submit a job using the Job Scheduler Wizard, it is labeled as a generic job in
the Job Queue and Activity log. Although you can modify a generic job using the Job
Queue; you can only reschedule and stop it.
Note: You must have Administrator rights on the local Windows machine to submit jobs
using the Job Scheduler Wizard.
Job Scripts
Job Scripts
A script is a job that you saved to a file. It contains the original source, destination,
options, and schedule information for the job. It will also contain any filters you created
to include and exclude files and directories.
Creating a script has the following advantages:
You can copy your settings to a different Windows machine running Arcserve
Backup.
You can quickly resubmit regularly executed jobs after a job has been accidentally
deleted.
After you create the job, click the Submit toolbar button.
The Submit Job dialog opens.
2.
3.
4.
Open the Job Status Manager and select the Job Queue tab.
Click Load on the toolbar.
The Add Job dialog opens.
Job Templates
2.
Browse to and select the script for the job that you want to execute.
Click Open.
The Select a Server dialog opens.
3.
From the drop-down list, select the server from which you want the job to execute.
Click the Submit on Hold option to submit the job in a Hold status.
Note: The Submit on Hold option is selected by default.
Click OK.
The job information for the previously saved script will be displayed in the Job
Queue as a new job.
Job Templates
A job template contains a series of settings such as the destination, options, and
schedule information for the job. Similar to job scripts, a template can also contain any
filters you created to include and exclude files and directories.
Job templates are different, however, from job scripts because they provide the
flexibility to repeat custom backup schedule settings on other Arcserve Backup
machines. Because the job template does not retain the backup source information as
the job script does, the template files can be copied and applied to any new server
source running Arcserve Backup. But, job scripts cannot be modified to accommodate
new server sources.
You can choose from seven default job templates or you can create a custom template
to meet your individual backup needs. The default job templates are designed to meet
specific backup tasks such as rotation scheme, backup method, and GFS options. The
default job templates can be accessed from the File menu when you choose the Open
Job Template option.
From the Arcserve Backup Manager window, select Backup from the Quick Start
menu.
The Backup Manager Window opens.
Job Templates
2.
Make selections for your backup job by accessing the Start, Source, Destination, and
Schedule tabs.
Click Submit in the toolbar to submit the job.
The Submit Job dialog opens.
3.
4.
In the File Name field, specify a name for the job template and click Save.
The job is saved as a job template with an .ast file name extension.
Note: While default job templates are stored in the Templates/Jobs folder in the
Arcserve Backup directory, you can save your template in any directory you want. To
open your custom job template on a local machine or from a remote server, access the
File menu and choose the Open from Template option. After the job template is open,
specify the source data, and then you can submit the job.
Open the Backup Manager by selecting Backup Manager from the Quick Start
menu.
The Backup Manager window opens.
2.
Make selections for your backup job by accessing the Source, Staging, Destination,
and Schedule tabs.
3.
4.
Edit or confirm the security and agent information for your job and click OK.
The Submit Job dialog opens.
Job Templates
5.
Click Save Template in the Submit Job dialog box to save your new job template
with an .ast filename extension.
The Save Job Template dialog opens.
6.
Save In--Specify the path for the job template file. While default job templates
are stored in the Templates/Jobs folder in the Arcserve Backup directory, you
can save your template in any directory you want.
File Name--Enter a name for the job template. By default, it will be saved with
an .ast extension.
Save as type--To save the job template in another format, select the file format
you want.
Select File from the main menu and then select Open from Template.
The Open Job Template dialog opens.
2.
Look In--Indicates the path for the job template file. While default job
templates are stored in the Templates/Jobs folder in the Arcserve Backup
directory, you can save your template in any directory you want.
File Name--Enter a name for the job template you want to open.
Files of type--If you saved the job template in another format, select the file
format you want to open. By default, the job template will be saved with an
.ast extension.
Once the job template is open, you can submit your job.
Note: You can choose from seven default job templates or you can create a custom
template to meet your individual backup needs. The default job templates are
designed to meet specific backup tasks such as rotation scheme, backup method,
and GFS options. The default job templates can be accessed from the File menu
when you choose the Open from Template option.
Device Configuration
Agent Admin
How You Can Back Up Devices Connected to Arcserve Backup Server (see page 347).
How You Can Back Up Devices Shared Between Arcserve Backup and
Windows-powered NAS (see page 348).
You can use the Web interface integration provided by Arcserve Backup on a remote
server and perform backup and restore tasks as well as monitor scheduled jobs
configured for the installation.
The Agents can be backed up from the remote Arcserve Backup Server which may be
running on another Windows-powered NAS device as shown in the following
illustration.
How You Can Back Up Devices Shared Between Arcserve Backup and Windows-powered NAS
You can configure Arcserve Backup Server, Manager, and the SAN Option on a
Windows-powered NAS device and create a secondary remote Arcserve Backup server
with a SAN Option. Both machines can connect to a shared backup device such as a tape
library through a fiber switch as displayed in the following illustration.
From the Backup Manager console, Destination tab, set the retention time through
Cloud Purge Policy when submitting a migration job. When the purge policy expires,
the cloud session is deleted to free up space and keep costs down.
From the Device Manager console, click Browse Cloud Folder from the toolbar,
select a folder and right-click to delete.
2.
Select the cloud sessions you want to delete from the Sessions directory tree.
3.
From the Archive Manager, select the Source (see page 355), Schedule (see
page 356), Policies (see page 356), and Destination (see page 358) tabs to specify
the options that you require for the job.
2.
Click the Options toolbar button to specify global options that you require for the
job. For more information, see Global Options for Archiving (see page 359).
3.
4.
On the Security and Agent Information dialog, edit or confirm the security and
agent information for your job, and click OK.
5.
When the Submit Job dialog opens, select Run Now to run the job immediately, or
select Run On and select a date and time when you want the job to run.
Note: For more information about the Run Now option, see Job Queue Tab (see
page 74).
6.
7.
If you selected multiple sources to archive and want to set the priority in which the
job sessions initiate, click Source Priority. Use the Top, Up, Down, and Bottom
buttons to change the order in which the jobs are processed. When you finish
setting priorities, click OK.
8.
To save the job as a Arcserve Backup job script, click the Save Job button.
9.
10. To preflight, check the job, click the Preflight Check button. If the preflight check
failed, click the Cancel button to modify the job settings.
11. On the Submit Job dialog, click OK.
The job is submitted.
If you would like to view the status of the archive job, go to the Job Status Manager (see
page 319).
More information:
How to Manage Jobs Using the Job Queue Tab (see page 323)
Archive Manager
Archive Manager
The Archive Manager lets you customize your archive jobs using filters, specifying
options, and setting schedules.
You can use the Archive Manager to:
Set archive schedules and policies for selected Windows, UNIX/Linux, and MAC file
system data.
Find data that is eligible for archiving and backing up, and then delete the archived
data from its original location immediately.
Use filters to selectively exclude or include directories and files for an archive job.
Specify the File Size and File Age for an archive job.
Set retention time to the archived data for how long to keep data in the archive
media.
View archive status through Dashboard reports. For more information on reports,
see the Dashboard Guide.
View list files that were archived. Arcserve Backup records the list of files in a CSV
file, and stores the CSV files in the following directory:
BAB_HOME\Archived Files
The CSV file is backed up in the Arcserve Backup Database protection job.
The CSV file is backed up in a backup job that includes the Catalog database, as
specified in the Global options for the job.
The Archive Manager provides tabs that let you customize your archive job:
Start tab--Lets you specify the type of archive: Normal, Deduplication, or Cloud. You
may also enable staging for each archive type. For the Cloud Archive option, the
Enable Staging option is selected automatically.
Source tab--Lets you specify the data that you want to archive.
Policies tab--Lets you specify a file type, file size, when the file was last accessed,
modified or created, and data verification.
Destination tab--Lets you specify the location where you want to store your archive
files.
The topics that follow provide full details about the options available on each tab.
Archive Manager
Cloud Archive--Cloud Archive lets you archive data to a cloud device destination
only.
Note: Enable staging (see page 241) is automatically selected if you choose this
option.
For each archive type, you must click the Source (see page 355), Schedule (see
page 356), Policies (see page 356), and Destination (see page 358) tabs to complete
archive job configuration.
You may also Enable Staging (see page 241). Staging operations allow you to archive
data to a staging device and then migrate the archive data to a final destination (usually
a tape). You can choose to Enable Staging on Normal Archive or Deduplication Archive
jobs.
Archive Manager
How to Specify Source Data for Archiving Using the Classic View and the Group
View
The source is the path to the data that you want to archive. You can easily find the files
you want to archive by browsing through the Archive Manager directory to select the
user-shared drives and directories.
Arcserve Backup lets you browse and specify the source data using the following views:
Classic View--This is traditional source view. Machines are listed first, allowing you
to expand and then select specific data sources. With the Classic View, Arcserve
Backup categorizes source computers based on the platform that is running on the
computer. For example, Windows systems and UNIX/Linux systems.
Group View--This view categorizes source computers based on the Arcserve Backup
agent that is installed on the computer. The agents are listed as branches on the
source tree. Within each branch, the computers that contain the specified agent are
listed.
You may also create customized groups that allow you to group machines according
to your own criteria. For example, using the Group view is an effective approach to
specifying source when you want to create a group for a specific file server.
When selecting a source, you can select to archive individual drives, directories, and files
To select individual drives, directories, and files to archive, expand a server name and
click the green boxes next to each drive, directory, and file.
To select an entire source group, click the green box next to the group name. When you
do this, all the servers, nodes, volumes, drives, directories, and files included in the
source group are automatically selected.
Be aware of the following behavior:
The view that you specify when you submit a job cannot be modified.
For example, you submit a job using the Classic View. Subsequently, you want to modify
the source selections for the job. When you modify the job and click the Archive
Manager, Source tab, the view drop-down menu is disabled.
Archive Manager
Repeat Method--All jobs can be scheduled using the Schedule options available in
each Manager. Jobs can be submitted with the following repeat methods:
Day(s) of the Week--Repeat this job on the days that are specified. (Default)
Friday is the default day of the week.
Week(s) of the Month--Repeat this job on the weeks that are specified.
Custom--Repeat this at the specified interval, but exclude the days that are
checked.
Append--Select this option to add additional days to your scheduled archive job.
Use WORM Media--Select this option to back up data to write once, read many
(WORM) backup media when the backup job runs.
File Filter--The File Filter options let you include or exclude files, directories, or both
from your archive job.
Types of filters offered in this section are:
File Pattern--Use the File Pattern filter to include or exclude files from a job.
You can specify a particular file name or you can use wildcards to specify a file
pattern.
Note: Wildcards "*" (asterisk) and "?" (question mark) can be used in the file
pattern filter.
Archive Manager
File Attributes--Use the File Attributes filter to include or exclude specific types
of files from a job. Select as many of the following types of file attributes as you
want:
Host Name Pattern--Use the Host Name Pattern filter to include or exclude
specific computer systems from a job.
File Size--The File Size options let you specify the file size attribute to include files.
You can specify a size range from 0 to 999999 bytes, KB, MB, or GB. There are three
file size options that you can specify:
Greater than--Files with a file size that is equal to or greater than the range are
included or excluded from the job.
Less than--Files with a file size that is equal to or less than the range are
included or excluded from the job.
Between--Files with a file size that falls between the ranges are included or
excluded from the job.
File Age--The File Age options let you use the file age attribute to exclude files
based on when they were last accessed, modified, and created in days, months, and
years.
Note: Arcserve Backup preserves the last access time for the file.
Verification--The Verification options let you verify that your data was archived
correctly. The following options are available.
Scan Archive Media Contents--Lets Arcserve Backup scan the media and check
that the header is readable for each file that is archived.
Archive Manager
Multistreaming
The Multistreaming options let you split single archive jobs into multiple jobs and
use all of the available tape devices in your system to complete the archive.
Group and Media field
Lets you specify the device group that you want to use for the archive job.
Place an asterisk in the Group or Media field to use the first available drive and
media in the group.
If you want to use any available group, click the Use Any Group option.
Media Pool
You must specify a media pool for the archive job. A media pool is required so that
you can specify tape media or group media.
Be aware of the following:
You cannot use inactive media pools that were created using the Media Pool
Manager for archive jobs. If you want to use this type of media pool, delete the
media pool using the Media Pool Manager and then submit the archive job
using the name of the media pool that was deleted.
When you specify a Media Pool, Arcserve Backup automatically checks the
other destination and archive options that you selected to verify that
restrictions and conflicts do not occur when you run the job. If Arcserve Backup
detects a conflict, a warning dialog opens. For more information on Media
Pools, see How Media Pools Work (see page 121).
You do not need to specify a media pool only if the final destination is a
deduplication device or deduplication device group.
Retention Time
Click this button to define the length of time that archive media is not used before
it is moved to the scratch set (tape media) or purged (deduplication devices and
backup to cloud devices).
Examples:
The device is a library and the retention time is 30 days: The media will remain in
the Save Set as long as it has been used within 30 days. If the media was not used
for 30 days, Arcserve Backup moves the media from the Save Set to the Scratch Set.
The device is a deduplication device and the retention time is 30 days: Arcserve
Backup purges the data from the deduplication device after the 30-day retention
period expires.
Servers
This field displays the name or the primary server and member servers in your
Arcserve Backup domain.
Note: If you did not install the Central Management Option, the name of the
current backup server displays in this field.
More information:
How Arcserve Backup Processes Backup Data Using Multistreaming (see page 103)
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 Backup 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 Backup
checks to see if the media in the drive is the one specified for the job. If it is not,
Arcserve Backup checks to see if the media is blank. If the media is not blank either,
Arcserve Backup reformats whatever media it finds in the device and starts to
archive files at the beginning of the media.
Deduplication devices do not support the Overwrite Same Media Name option. The
archive job will always append to the deduplication device even if the Overwrite
Same Media Name, or Blank Media or the Overwrite Same Media Name, or Blank
Media First, then Any Media options are selected.
If you want to format the deduplication device, format it manually in the Arcserve
Backup Manager.
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 Backup remembers the name and ID of the job's first media. When the job
requires additional media, Arcserve Backup 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 Backup reformats the media, giving it the same name and ID as the first
media. The sequence number changes.
Note: To overwrite media based on its name only, select the Distinguish Media by
Name Only option.
Overwrite Same Media Name, or Blank Media First, then Any Media--Overwrites
any media found in the device (as long as it has a different ID from the first media's
ID). If neither of these conditions are met, Arcserve Backup reformats whatever
media it finds in the drive and starts to archive files at the beginning of the media.
All subsequent media are reformatted with the same name and ID as the first
media. Only the sequence number changes.
Note: To overwrite media based on its name only, select the Distinguish Media by
Name Only option.
Calculate and Store CRC Value on Archive Media--Calculating and storing the CRC
value on the archive media will enable Arcserve Backup to perform CRC verification
during the archive job. To instruct Arcserve Backup to use the CRC value stored on
media, see the Verification (see page 356) section in the Policies tab.
Use Default Device Setting--Select this if you want to use the setting you
selected during library configuration.
Eject Media--Select this if you want to eject media from the drive after the job
finishes. This helps prevent any other job from overwriting information on this
media. If you select this, it overrides the setting you selected during library
configuration.
Do not Eject Media--Select this if you do not want to eject media from the
drive after the job finishes. If you select this, it overrides the setting you
selected during library configuration.
Note: For more information on library configuration, see the chapter Managing
Devices and Media.
By default, Retry Missed Targets is enabled, After Job Finishes is selected, and
the value of Max Times is 1.
File system archives--If the archive job requiring a makeup job consists of file
system archives, and the file system contains directories that reside in different
volumes, the makeup job archives only the failed volumes or directories. The
makeup job does not archive the entire file system if it contained successful
volume or directory archives.
Child jobs--The child makeup jobs (makeup of makeup jobs) run based on the
value specified for After Job Finishes.
More information:
Local Backup Options for UNIX and Linux Agents (see page 152)
You can use the Pre option to defragment a disk before an archive job starts.
Be aware of the following behavior when using Pre and Post options:
Arcserve Backup does not support running commands with executables that reside
on remote systems.
Using a Pre option and specifying an exit code prevents the archive operation from
starting until after the Pre option process is complete.
Using a Pre option and specifying an exit code and the Skip Operation option causes
Arcserve Backup to skip the archive operation and, if specified, prevents the Post
option process from starting.
Post option processes start unless the following conditions are present:
An exit code is specified, the Skip Post Application option is specified, and the
result exit code is equal to the exit code specified.
The result of the archive operation is equal to the value specified for the Do not
run Command if option.
Pre and Post options specified as global options run commands before a job starts
or after a job finishes. Pre and Post options specified as node-level (local) options
run commands before a node or after a node is archived.
For example, a user submits an archive job consisting of nodes A and B. A Pre
option is specified as a global option and a Pre option is specified for node B.
Immediately before the job runs, the global Pre option executes. While the job is
running, the Pre option specified for node B executes before node B is archived.
On Exit Code--Arcserve Backup detects exit codes of other programs. You can
specify the following options for a particular exit code:
Run Job Immediately--The job runs immediately if the selected exit code is
returned.
Skip Job--The job does not run if the appropriate exit code is detected.
Skip Post Application--Skip any commands specified to run after the job if
the appropriate code is detected.
Backup
Archive
Restore
Compare
Copy
Count
Purge
Log all activity--Record all of the activity that occurs while the job is running in the
Job Log.
Note: When you specify Log all activity, Arcserve Backup creates a log file named
JobLog_<Job ID>_<Job Name>.Log. With this log file, you can view detailed logging
information about the job. Arcserve Backup stores the log files in the following
directory:
C\Program Files\CA\ARCserve Backup\LOG
Log disabled--Do not record any information about this job in the Job Log.
Media not Available--Media was not available during the execution of a job.
Note: The archive media must be tape media.
Format Blank Tape--A tape was formatted during the execution of a job.
Specify one or more of the defined Alert configurations. The default configuration
means that you will use whatever is configured in Alert Manager. Click Configure to
define further configurations. Arcserve Backup provides the following defined Alert
configurations:
Broadcast
Pager
Note: Pager options are not supported on Japanese versions of Arcserve Backup.
SMTP
SNMP
Event
Printer
Lotus Notes
Unicenter TNG
Attach Job Log--Lets you include the job log information in the Alert message. (This
option applies for Trouble Tickets and Mail only.)
Note: The list you create using Alert Options is saved with the Job Script and the
configuration defined using the Configuration button.
Send CSV as attachment--Lets you save archived file names to a CSV file to be sent
in the Alert message.
The CSV file includes the following fields:
Send alert messages only for master jobs--Lets Arcserve Backup send you alerts
that reference only the master job number in the Alert message. The alert
messages do not reference child and subjob numbers. You can specify this option
on all jobs, including multiplexing and multistreaming jobs.
Archive Mount Points as Part of the volume that they are mounted--If you select
this, the volumes referred to by the Volume Mount Points will be archived as part
of the same session as the Volume Mount Points. When this option is not selected,
the volumes referred to by the Volume Mount Points are archived as separate
sessions. This option is available only when the previous option, Traverse Directory
Junctions and Volume Mount Points, is selected.
Note: When you apply the Traverse Directory Junctions and Volume Mount Points and
Archive Mount Points as Part of the volume that they are mounted options to named,
mounted volumes that contain virtual hard disks (VHDs), Arcserve Backup creates
separate archive sessions for mounted volumes that contain VHDs.
Example: Mounted Volumes that Contain VHDs
A server contains physical disk (C:\) that contains VHDs D:\ and E:\. VHD files (D.vhd and
E.vhd) that reside in C:\ are mounted as drive D:\ and drive E:\. Drive D:\ is mounted to
C:\MountD, and drive E:\ is mounted to C:\MountE.
If you archive C:\MountD and specify the Traverse Directory Junctions and Volume
Mount Points option, and the Archive Mount Points as Part of the volume that they are
mounted option is enabled or disabled, Arcserve Backup creates separate archive
sessions for drive D:\ and C:\MountD.
If you specify encryption and compression options, and the archive destination is a
drive that does not support compression, Arcserve Backup encrypts the archive
data and does not compress the archive data.
The following options define how Arcserve Backup processes archive data during an
archive job.
Session/Encryption Password
Merge and Scan operations where the encryption, compression, or both were
processed at the archive server. (You do not need to specify the password to
perform Merge and Scan operations where the encryption, compression, or
both operations were processed at the agent.)
Note: The Session/Encryption password is not required when you Merge or
Scan only the session headers.
Encryption/Compression methods
Encrypt data--Use this option to encrypt the archive data. You can specify one of
the following options:
At agent--Select this option to encrypt the archive data prior to the actual
archive process. For more information about this option, see Data Encryption
at the Agent Server (see page 113).
At backup server during archive--Select this option to encrypt the archive data
at the backup server during the archive process.
Compress data--Use this option to compress the archive data. You can specify one
of the following options:
At agent--Select this option to compress the archive data on the system where
the agent is installed and running.
Note: Arcserve Backup does not support data compression at the agent system
when the archive source consists of UNIX.
You must specify Encrypt data at backup server during archive to enable
compression at backup server.
With the 'at Backup Server' option specified in the Compress data section
and the 'at Backup Server during archive' option specified in the Encrypt
data section, Arcserve Backup uses software compression to compress the
data at the backup server before the data is encrypted.
If the storage device associated with the job does not support hardware
compression, Arcserve Backup ignores the 'at Backup Server' option
selected in the Compress data section.
The Device Manager gives you information about storage devices connected to
your system, the media in these devices, and the status of these devices. It is the
starting point for all media and device monitoring and maintenance operations.
The Media Pool Manager lets you create, modify, delete, and manage media pools,
collections of media managed as a unit to help you organize and protect your
media.
The Media Management Administrator (MMO) provides the tools you need to
control, manage, and protect media resources.
Device Assignment
Assigning a drive to a library allows Arcserve Backup to recognize the drives existence
within the library.
Usually the manufacturer configures a library in such a way that the first library drive
has the lowest SCSI ID number and the last library drive has the highest SCSI ID number.
Note: This is not always the case. See the documentation that came with your library for
information on how its drives are configured.
To manually assign a drive to a library, highlight the drive you want to assign from the
Available Devices list and the library in which the drive should reside from the Library
Devices list then use the Assign button to move the drive to the library. To un-assign a
drive from a library, highlight the drive in the Library Devices list and click Remove.
Note: All drives must be empty for Arcserve Backup to complete the drive configuration.
The process may take a few minutes, depending on the number of drives in your library.
Configure Libraries
Arcserve Backup automatically detects and configures your libraries as the Tape Engine
starts. You do not need to run a wizard or other external application to enable Arcserve
Backup to detect your libraries.
Note: If Arcserve Backup does not automatically configure your libraries, use Device
Configuration to manually configure your libraries.
To configure a library, verify that the following prerequisite tasks are complete:
1.
2.
Install the license for the Arcserve Backup Tape Library Option as required for your
environment.
3.
4.
If you want Arcserve Backup to read the data on the tapes, do the following:
a.
b.
c.
To configure libraries
1.
2.
Bar code reader installed--If your library contains a bar code reader, this
option lets you use the bar code reader in the device to inventory the tapes in
the library.
Bar code reader not installed--Specify this option if your library does not
contain a bar code reader.
Library Quick Initialization--To enable this option, you must select the Bar
code reader not installed option.
This option is designed for libraries that cannot read bar codes. With this
option enabled, Arcserve Backup retains information about the library's
slots in the Arcserve Backup database. As a result, Arcserve Backup does
not repeat the inventory process when the Tape Engine is restarted.
Arcserve Backup ignores this option on libraries that contain a bar code
reader.
Note: If the library does not support bar codes and this option is disabled,
Arcserve Backup inventories the entire library when Arcserve Backup
starts.
This option lets Arcserve Backup initialize faster by bypassing the inventory
slots process when the Tape Engine starts. When you use this option,
Arcserve Backup assumes that the media in the slot have not been added,
removed, moved, or swapped since the last shutdown. If you added,
removed, moved, or swapped media, you should manually inventory the
entire library or inventory the slots that changed.
Note: Arcserve Backup must inventory the library after you configure the
library. The quick initialization option takes affect after you complete the
first full inventory of the library.
Eject media upon backup job completion--Lets you direct Arcserve Backup to
move the tapes back to their original slots after the backup job is complete
rather than allow them to remain in the drives.
Note: You can override this option on a job-by-job basis by enabling the global
option for jobs called Do not Eject Media. In addition, if you do not enable the
ejection of media after a backup job completes and later decide that you want
to eject media after a particular job, you can enable the global option for jobs
called Eject Media.
Arcserve Backup ignores media expiration dates when you select this
option.
You should not identify a physical library as a VTL. When you identify a
physical library as a VTL, the library's backup and data migration
performance can be adversely affected.
Monitor blank tapes--Lets you log a warning message in the Activity Log when
the number of blank tapes available to the library is less than the specified
value. This option can be applied to single and multiple drive libraries.
Default value--1
Range--1 to 65535
3.
Clean by slot--Lets you designate specific slots as cleaning slots. You can specify
one or more cleaning slots and they do not need to be in a successive order.
Clean by Barcode--Lets you specify cleaning slots for your library based on a
specific bar code or a range of bar codes using a prefix and a wildcard
character. In the Clean Bar Code Prefixes field, enter the prefixes of your bar
coded cleaning tapes.
Specify the bar code prefixes into the Clean Barcode Prefix(s) field.
4.
The bar code on your cleaning tape is CLN123. In the Clean Barcode
Prefix(s) field, specify CLN123.
There are several cleaning tapes in your library. The bar code prefix for the
cleaning tapes is ABC. In the Clean Barcode Prefix(s) field, specify ABC*.
There are several cleaning tapes in your library. The cleaning tapes' bar
code prefixes are ABC, CLN1, and MX. In the Clean Barcode Prefix(s) field,
specify ABC*; CLN1*; MX*.
Automatic tape cleaning--Lets you direct Arcserve Backup to manage your tape
cleaning tasks automatically. When you enable this option you must specify the
number of hours that must elapse between cleaning tasks.
Click OK.
The library is configured.
The largest default tape block that Arcserve Backup can transfer is 64 KB. You can
increase the tape block size to 128 KB, 256 KB, or 512 KB when using tape drives in
your backup environment that support larger tape blocks.
Note: See the device and host bus adapter (HBA) manufacturer documentation to
verify that the device supports larger data transfers.
Large block backups require HBAs that support large transfer sizes. When Arcserve
Backup detects the HBA cannot support the data transfer size required for the
larger block size, Arcserve Backup disables the larger block size and records an error
message in the Tape engine log file.
When Arcserve Backup overwrites or uses blank tapes, Arcserve Backup formats the
media using the newly defined tape block size.
When Arcserve Backup appends data to media, Arcserve Backup writes the
appended data to the media using the block size originally applied to the media.
For SAN attached libraries, verify that the HBA for all SAN member servers can
support the transfer size that the tape block size requires. Backups to SAN member
servers that do not support the larger transfer size usually fail.
Stop the Arcserve Backup Tape Engine service on the backup server that you want
to configure.
2.
x86 platforms:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe
Backup\Base\TapeEngine
x64 platforms:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\CA ARCServe
Backup\Base\TapeEngine
Locate the DEVICE# key for the tape drive that you want to configure.
3.
Under the DEVICE# key, create a DWord registry key named ForceBlockSize.
Specify one of the following DWORD values:
Close the Edit DWORD Value dialog and close Windows Registry Editor.
4.
To review the attributes of each RAID level, instructions on selecting a RAID level, and
instructions on assigning drives to the RAID device, see the Tape Library Option Guide.
To enable or disable devices for RSM, the Tape Engine must be stopped. If your
Tape Engine is running, a pop-up window displays that lets you stop the Tape
Engine.
Servers Windows Server 2003 take control of all the devices attached to the server
when the Removable Storage service is enabled. This service manages removable
media, drives and libraries. To control these devices Arcserve Backup must have
exclusive access to them.
By default, RSM maintains exclusive control of all devices. When the Tape Engine
starts, Arcserve Backup detects all devices under the control of RSM and attempts
to obtain exclusive control of the devices by disabling the devices in RSM. However,
Arcserve Backup can obtain exclusive control from RSM only if the devices are not
being used by other applications. If RSM is not running when the Tape Engine starts,
Arcserve Backup detects the devices but Arcserve Backup cannot disable RSM's
control of the devices. As a result, RSM obtains exclusive control of the devices the
next time RSM starts. To help ensure that Arcserve Backup can obtain exclusive
control of RSM devices, you must specify the Enable/Disable Devices (for RSM)
option and disable the devices. You can access the Enable/Disable Devices (for
RSM) from Device Configuration as illustrated by the following screen:
When RSM has exclusive control of device, Arcserve Backup cannot send SCSI
commands directly to the device. However, when Arcserve Backup has exclusive
control of a device, it can communicate (input and output commands) directly to
the device.
When you choose the Enable/Disable Devices (for RSM) option, you are provided
with a list of all the devices that are currently available in the system. Arcserve
Backup manages the devices currently selected. If you want another application to
manage any device, clear the selected device.
You do not need to disable a device in the RSM if the device driver is not installed
on the Arcserve Backup server. RSM functions in this manner because the lack of a
device driver prevents RSM from detecting the device. Arcserve Backup does not
require the presence of a device driver to be able to detect a device.
More information:
Configure Devices Using the Device Wizard (see page 116)
IBM 3494--The IBM 3494 configuration option lets you configure or modify the
configuration of an IBM 3494 library. With this option, you can use the full
capabilities of Arcserve Backup with the large tape volume capacities of the IBM
TotalStorage Enterprise Automated Tape Library 3494.
To configure IBM 3494 Libraries, ensure that the following configurations are
complete before you start Enterprise Module Configuration:
IBM 3494 Automated Tape Library software is installed on the primary server.
For information about using IBM 3494 libraries with Arcserve Backup, see the
Enterprise Module Guide.
Image Option--The Image Option configuration option lets you install a driver on
target systems to enable Image Option capabilities. With this option, you can
perform high-speed backups by bypassing the file system, creating a snapshot
image of the drive, and reading data blocks from the disk.
For information about backing up and restoring data using the Image Option, see
the Enterprise Module Guide.
From the Windows Start menu, click Start, point to Programs (or All Programs), CA,
ARCserve Backup, and click Enterprise Module Configuration.
The Enterprise Module Configuration, Options dialog opens.
2.
Click the button for the device that you want to configure, follow the prompts on
the subsequent dialogs, and complete all required information.
Device Configuration
With Device Configuration, you can create file system devices, data mover file system
devices, and deduplication devices using a wizard application, or you can modify the
configuration of existing devices within the Windows environment. Devices are
configured to a folder on a specific shared drive. When you specify the device as your
backup destination, each session is stored as an individual file within that folder.
Arcserve Backup lets you configure disk-based devices without stopping the Tape
Engine. When you configure devices, you can change the credentials of devices used for
remote access by clicking Security from the Disk-Based Device Configuration dialog.
From Device Configuration, you can add one or many devices. When you click Next,
Arcserve Backup verifies the validity of information specified for all devices and displays
the results as tool tips. Point your mouse to the icon in the Device Name column. Device
status is indicated by the series of icons described in the following table:
Icon
Description
Function
Pending
Verifying
Passed
Failed
Warning
Ready
Ensure the paths specified for the Location are unique for each device.
Staging backup operations can quickly consume a large amount of free disk space on file
system devices. Due to the maximum file size limitations of FAT 16 and FAT 32 file
systems, you should not use these file systems on file system devices designated for
staging operations.
You can specify the Location of the FSD using any of the following formats:
To specify a path to a folder that resides on a mapped drive, use the format that
follows:
k:\fs_drive
Arcserve Backup converts the path and prompts you for credentials when you are
finished editing.
To use a shared folder as a File System Device that you want to access through the
network, specify the Universal Naming Convention (UNC) path of the shared folder,
for example, \\SERVER1\fs_drive\. For UNC path, we encourage users to always put
the correct credentials in the Security Window. Incorrect credentials may lead to
unexpected results on some platforms, such as Windows 2008, Vista, and others.
Arcserve Backup can use the mapped drive, but you must have logged in to the
mapped drive previously.
If you use a mapped drive for an FSD, Arcserve Backup converts the mapped drive
to a universal naming convention (UNC) path and prompts you to provide log in
credentials when you click Finish.
The log in credentials provided must enable full access to the mapped drive.
By default, Arcserve Backup uses the Arcserve Backup System Account to gain
access to each remote FSD. You can change the credentials that you use with
the selected file system device by using Security.
You do not need to provide credentials when you create an FSD using a local
disk.
Important! Arcserve Backup does not support sharing an FSD with multiple Arcserve
Backup servers. When an FSD is shared, the Arcserve servers using the FSD can
overwrite the other server's backup data.
Note: Arcserve Backup supports configuring an aggregate total of 255 FSDs and DDDs
(only if the number of physical devices configured is 0).
2.
3.
From the Login Server dialog, provide the required security credentials for the
Primary Server and click Next.
4.
From the second Login Server dialog, select the desired server and click Next.
The Disk-Based Device Configuration dialog opens, showing separate branches in
the tree for Windows File System Devices and Deduplication Devices.
5.
Click the branch for the type of device you wish to create, for example, Windows
File System Devices, and then click Add.
A new, blank device is added to the appropriate branch of the tree.
6.
b.
c.
In the Data File Location field, type a location or click the Browse button to
search for one.
d.
Note: The Index File Location field applies only to deduplication devices and is not
available when creating FSDs. The Tape Name and Vol Size fields auto-fill when
verification completes successfully.
Erase--Deletes the sessions and writes a blank header file on that folder.
The device commands that are not available for file system devices are:
Retension
Compression
Eject
Long erase
2.
Click Next.
The Login Server screen opens.
3.
Specify the domain name, primary server name, and authentication type.
Enter your user name and password and click Next.
Specify the server on which the disk-based device is to be removed and click Next.
The Disk-Based Device Configuration screen opens.
4.
From the desired branch of the tree (File System or Deduplication Device), click the
device you wish to remove to select it.
Click Remove.
The selected device is flagged for removal. If you change your mind and wish to
keep the device, click Cancel Remove.
5.
Click Next and review results. The device you removed is shown as Delete Successful in the Report column.
6.
Click Next to remove more devices or click Exit to end device configuration.
The disk-based device is removed.
2.
3.
Specify the domain name, primary server name, and authentication type.
Enter your user name and password and click Next.
Specify the server on which the disk-based device you wish to change is connected
and click Next.
The Disk-Based Device Configuration screen opens.
4.
From the appropriate branch of the tree, click the device you wish to change to
select it.
For File System Devices, you may change the Device Name, Description or Data File
Location.
For Deduplication Devices, you may change the Device Name, Description, Data File
or Index File Locations.
Note: You cannot change the Group and Tape Names from this screen. Use Device
Group Configuration to change the Group Name.
5.
Specify new security settings. If you changed remote locations for the Data File or
Index File Locations, click Security and provide the required User Name, Domain
and Password. Retype the password to confirm.
6.
Click Next.
7.
Click Exit to leave Device Configuration if you are done modifying devices.
Configure groups (see page 389) -- use this option to create, rename, or delete
groups, or assign or remove devices from groups.
Set Device Group Properties (see page 392) -- use this option to set properties for
deduplication groups or staging groups.
Configure Groups
The Configure groups option of the Device Group Configuration wizard lets you create,
rename and delete groups as well as assign or remove devices from groups.
When disk-based devices are created, they are automatically added to groups. However,
for times when you need to reassign devices, such as for hardware maintenance or
replacement, you can add a new (empty) group and assign devices to it later, or swap
devices among existing groups.
From the Arcserve Backup Manager Console, launch Device Group Configuration.
Device Group Configuration appears.
2.
Click Next.
3.
4.
b.
c.
click Next.
5.
6.
b.
click OK.
The new regular group appears in the Empty Groups list, but contains no device.
You may now assign an available disk-based device to this group.
From Device Group Configuration, click a Group from the list of available groups on
the left.
2.
From the list of Available Devices on the right, click a device to select it.
Note: If there are no Available Devices to choose from, remove a device from
another group or delete an existing device groups. Devices in deleted groups are
moved to the Available Devices list.
3.
Click Assign.
The device is added to the group you selected.
4.
5.
You can convert an existing File System Device group to a Deduplication Device group by
removing the FSD devices from it and adding a deduplication device to it. Similarly, you
can convert a deduplication group to a normal FSD group in the same manner.
1.
From Device Group Configuration, click a Group from the list of available groups on
the left.
2.
3.
Click Remove.
The device is removed from the Group and added to the list of Available Devices.
4.
You may reassign devices you have removed to other device groups.
2.
Click Next.
3.
On the Login Page, complete the required fields and click Next.
4.
On the Options dialog, select the server you would like to configure, choose
Configure Groups and then click Next.
5.
From the Device Group Configuration dialog, click a Group from the Groups list to
select it.
6.
Click Delete.
A confirmation message appears.
7.
Click OK to continue.
The selected group is deleted. The device assigned to the deleted group is moved to
the Available Devices List.
8.
9.
2.
Click Next.
3.
On the Login Page, complete the required fields and click Next.
4.
On the Options dialog, select the server you would like to configure, choose
Configure Groups and then click Next.
5.
From the Device Group Configuration dialog, click a Group from the Groups list to
select it.
6.
Click Rename.
The Rename Group dialog opens.
7.
From the Rename Group screen, specify a new name for the device group.
Click OK
The name is changed and the device previously assigned to the group remains
unchanged.
1.
2.
Specify the Primary Server and Authentication Type, enter the required security
credentials and click Next.
3.
Choose the Set Device Group Properties option and click Next.
4.
For File System Device Groups, click the Enable Staging option to set staging
properties. For Deduplication Device Groups, set the deduplication device
properties.
5.
Click Finish.
Max Threshold--Specifies the maximum amount of space that can be used on a disk
before a job fails. When the maximum threshold is reached, Arcserve Backup fails
the jobs.
Default Value: 80%
The Max Threshold is represented as either a percentage of the total capacity used
on the disk, or as the total number of GB or MB used.
Pause data migration--Instructs Arcserve Backup to halt the data migration process.
This option applies only to deduplication groups used in staging operations.
Default Setting: Disabled
Max Threshold--Specifies the maximum amount of space that can be used on a disk
before a job fails. When the maximum threshold is reached, Arcserve Backup fails
the jobs.
Default Value: 80%
The Max Threshold is represented as either a percentage of the total capacity used
on the disk, or as the total number of GB or MB used.
Purge data when the used disk space exceeds the Max threshold-- Instructs
Arcserve Backup to delete old sessions when the disk space used for backup
exceeds the Max Threshold value.
Purge to Threshold--Available only when the Purge data when the used disk space
exceeds the Max threshold option is enabled.
Enable SnapLock for this group--Available only on devices that support SnapLock
technology, this option prevents data purge, or over-write until the specified
retention time elapses.
Device Manager
More information:
Back Up Data Using Global Deduplication (see page 752)
Device Manager
The Device Manager provides information about storage devices that are connected to
your system, the media in these devices, and the status of these devices. When you
highlight a storage device or the adapter card it is configured to, summary information is
displayed about the adapter card or the storage device, such as the vendor, model
name, and board configuration.
If you have more than one storage device connected to your machine, Arcserve Backup
lets you separate them into groups. Establishing device groups is the key to the
flexibility and efficiency of Arcserve Backup.
Device Manager
By default, Arcserve Backup is installed with each storage device assigned to its own
group. If identical storage devices (same make and model) are detected, it automatically
places them in the same group. You can use Device Group Configuration to:
Maintenance Tasks
Using the Device Manager, you can perform the following maintenance tasks on your
media:
Important! Before you use these options, especially formatting and erasing, make sure
you have the right media selected.
Format Media
Although Arcserve Backup automatically formats blank media during a backup job, you
can use this option to manually format your media. Formatting writes a new label at the
beginning of the media, effectively destroying all existing data on the media.
Note: Use this option with care. After the media is formatted, Arcserve Backup can no
longer restore the data and any job sessions associated with the media.
Device Manager
Low level formatting, which is required on most hard drives and some mini cartridge
device drives, is not required for drives that Arcserve Backup supports.
To format media
1.
2.
Select the slot containing the media that you want to format. Assign a New Media
Name and an Expiration date to the media that you want to format.
Note: When you assign a New Media Name to a slot, the light icon next to the
selected slot turns green. Slots with write-protected media appear in red. These
media cannot be formatted. You must specify a New Media Name before
formatting the media.
Repeat this step if you want to specify more media.
3.
If you want to use the media in a media pool, select a slot with the green light icon
and check the Use Rotation option. Then, from the Media Pool drop-down list,
select the media pool that you want to use the newly formatted media in. In the
Serial No. field, you can accept the default serial number or specify a user-defined
serial number. (If no media pool name is defined and the media has an assigned
bar-coded serial number, then Arcserve Backup does not overwrite that serial
number during the format procedure.)
Note: Click the Apply to all button if you want to use all of the formatted media in a
media pool and assign all the media to the same media pool.
4.
Assign a name and an expiration date to the media you want to format. You must
specify a New Media Name before formatting the media. For more information, see
How to Choose Expiration Dates (see page 404).
Device Manager
5.
Click OK.
The Format dialog closes and the following message appears:
"Formatting will erase ALL of your data from the media. Do you want to format the
media?"
6.
Erase Media
Use this option to erase all data from a single media or from multiple media. Arcserve
Backup also erases all references to the contents of this media (if any) from the
database. When you reformat this media, its physical history (read and write passes) is
retained.
You should verify that you have selected the correct media before using the Erase
option. Erased data cannot be retrieved. When erasing media, you can choose from the
following options:
Quick Erase--Quick Erase effectively erases media. It avoids the time a Long Erase
would take (minutes to hours) by overwriting the media label. The media history
remains available to Arcserve Backup for tracking purposes.
Quick Erase Plus--This option performs the same operation as Quick Erase, and also
erases bar codes and serial numbers. For more information about bar code and
serial number cataloging, see Mount and Dismount Option.
Note: If the media you are erasing does not have a serial number or bar code, this
option functions in the same manner as the Quick Erase option.
Media erased using the Quick Erase Plus option can no longer be tracked by
Arcserve Backup, and information such as the expiration date is no longer carried
forward.
Long Erase--Long Erase completely removes all data from media. It takes much
longer than a Quick Erase, but the media is literally blank. For security reasons, use
the Long Erase option to ensure that all data on your media is erased completely.
Note: The long erase process consumes more time than the quick erase process.
This will be apparent when you erase large capacity libraries. Exercise caution when
using this option on large capacity libraries.
Device Manager
Quick Erase and convert to WORM--This option quickly erases all data from the
media. In addition, Arcserve Backup converts the media to Write Once - Read Many
(WORM) media.
To use this option, Arcserve Backup must detect DLTWORM capable media in the
library or in a stand-alone drive.
To erase media
1.
Note: Slots reserved for cleaning media do not appear In the Erase dialog.
2.
Select the slot you want to erase. When you select media, the light icon next to the
media turns green.
You can press the Shift key to select multiple contiguous media. Press the Ctrl key
to select multiple noncontiguous media. You can also click and drag the light icon to
select multiple contiguous media.
3.
Retension Tapes
The Retension option helps to ensure that tapes are tensioned properly to avoid errors,
jamming, or breaking. You should retension media if you are having trouble writing to it
or reading from it.
Note: This feature applies only to quarter inch cartridge tapes.
Device Manager
To retension tapes
1.
2.
Compress Media
Arcserve Backup lets you compress the backup data that is stored on the media. Use the
Compression option only if your storage device supports tape compression. If it does
not, the Compression toolbar button will be disabled.
Note: Set the Compression option off only if you plan to use a media in another drive
that does not support compression. In this case, the drive that does not support
compression will not be able to read the compressed data on the media.
To turn compression on or off
1.
Open the Device Manager and browse to the library that you want to configure.
2.
3.
4.
Click OK to set the Compression Mode to Off (if it is On) or On (if compression is
Off).
Eject Media
Use this option to eject media from library storage drives and return the media to their
home slots (the slot with which the media was associated during the inventory process).
To eject the media from all drives in a library or a single drive
1.
2.
From the Device Manager's devices directory tree, do one of the following:
To eject the media from all drives in a library, select the library.
To eject the media from a single drive, select the individual drive.
Device Manager
3.
4.
Right-click the library or drive and select eject from the pop-up menu.
Click OK to confirm.
Arcserve Backup ejects the media.
Open the Device Manager and browse to the server connected to the library
containing the drive that you want to status as online or offline.
2.
Expand the library, right-click the drive, and select Online or Offline from the
pop-up menu.
The drive status changes to offline or online.
Note: Drives display in a disabled mode when they are in an offline state.
Rebuild Media
Arcserve Backup lets you rebuild one missing or unusable tape containing backup data
in a RAID level 5 environment. Due to the architecture of RAID Level 5 (striping with
parity), you cannot rebuild more than one missing or defective tape.
Device Manager
Eject the incomplete RAID set, using the eject option from Arcserve Backup Device
Manager (choosing 'Eject' while highlighting the RAID ejects all tapes in RAID).
2.
Insert a tape that the user wants to use as the replacement for the missing tape in
one of the tape drives.
3.
4.
Insert the incomplete RAID set in the other tape drives and click the Rebuild toolbar
button.
Arcserve Backup rebuilds the media.
If there are no blank tapes in the library, import one tape, or erase an unused tape
in the library.
2.
Choose the RAID set that you want to rebuild and click the Rebuild toolbar button.
Arcserve Backup rebuilds the media.
Scan Devices
Use the Scan Device option to enumerate USB storage devices that are connected
directly to the Arcserve Backup server.
Note: This option applies to USB storage devices only.
To scan a USB storage device using the Scan Device option
1.
2.
3.
Select the USB controller icon in the device directory tree and click the Scan Device
toolbar button.
Arcserve Backup detects and enumerates the device in the Device Manager, device
directory tree.
Important! If the drivers for the USB storage device are not Plug and Play (PnP)
compatible, Arcserve Backup may not be able to detect and enumerate the storage
device. To resolve this, you must configure the USB storage device by stopping and
restarting the Tape Engine.
Device Manager
To scan a USB storage device by stopping and starting the Tape Engine
1.
b.
From the server tree, locate and select the primary server.
The Arcserve Backup services appear in the right side of the window.
c.
Right-click Arcserve Tape Engine and select Stop on the pop-up menu.
The Tape Engine stops.
Attach the USB storage device directly to the Arcserve Backup server.
3.
From the server tree, locate and select the primary server.
The Arcserve Backup services appear in the right side of the window.
b.
Right-click Arcserve Tape Engine and select Start on the pop-up menu.
The Tape Engine starts.
After the Tape Engine starts, Arcserve Backup detects and enumerates the device in
the Device Manager device directory tree.
More information:
Configure USB Storage Devices (see page 424)
Device Manager
More information:
How to Manage Jobs Using the Job Queue Tab (see page 323)
How Arcserve Backup Labels Media with Bar Codes or Serial Numbers
Labeling media allows the library to quickly recognize and differentiate one media from
the others. Bar code recognition is a library-specific feature. Each media comes from its
manufacturer with a bar code label affixed to the outer edge of the media cartridge.
This label has a predefined serial number in letters and numerals, which is used as the
media serial number when the media is formatted.
If you select a media pool name and the media has an assigned bar coded serial
number, that serial number is preserved and the media pool range is ignored.
Note: When the serial number or bar code does not exist on the media, Arcserve
Backup displays N/A (not available) on the media description in the Device Manager.
Device Manager
Tape manufacturers rate their tapes useful lives from about 500 to 1500 passes. This
does not mean that the tape is unusable after it reaches the maximum number of
passes, only that it is more susceptible to errors at this point.
You should choose expiration dates based on how you plan to use the tape. If you plan
to use the tape often, (for example, a few times a week), you should set the expiration
date to one year, or less, from the date of formatting. By contrast, if you plan to use the
tape 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, Arcserve Backup notifies you that you cannot
overwrite to expired media. To remedy this condition, you can specify to append the
backup data to the expired media by doing the following:
1.
2.
How Expired Media Appears in the Backup Manager and Device Manager
Arcserve Backup can detect expired media.
The following screen illustrates how expired media displays in the Backup Manager,
Destination tab.
Device Manager
The following screen illustrates how expired media displays in the Device Manager.
If you are formatting new, blank media, the default expiration date is three years
from the current date.
If you are reformatting media, the expiration date that appears is the date you
specified the first time the media was formatted.
Device Manager
When the backup job appends the backup data to an expired media, a warning
message is displayed as shown below:
This job is appending to an expired media. (MEDIA=media_name[S/N:serial_number],
ID=media_id, SEQ=sequence_number)
When a backup job chooses a media to overwrite or append the backup data, it
checks the alert period of the media expiration and displays the following message:
This job is using media that will expire after <# of days>
(MEDIA=media_name[S/N:serial_number], ID=media_id, SEQ=sequence_number).
Where <# of days> represents a specific number days (for example, 3, 5),
Media_name represents the name of the media (for example, tape1, Media_id
represents the media ID (for example, 3d3c), and Sequence_number represents the
sequence number.
Note: This operation applies to both first tape and spanning tape.
The alert period of the media expiration is 30 days by default. You can change this
by adding the DWORD AlertPeriodForTapeExpiration to the following registry key to
set the alert period (number of days):
\\HKEY_LOCAL_MACHINE\ComputerAssociates\Arcserve
Backup\Base\Task\Backup\AlertPeriodForTapeExpiration
Note: This approach only applies to tape media, and you cannot overwrite to an
expired media.
Inventory Slots
The Inventory Slots option checks the library slots and reads the media header. It then
associates the media header with the slot in which it was found (called the home slot).
In this way, the Tape Engine can track changes made to media in the library. For
example, media added or removed from a magazine or moved to a different slot.
Be aware of the following considerations when using the Inventory Slots option to
inventory media:
Each media that you load into the storage drives in the libraries must have a unique
serial bar code number.
You should only add and remove media when the Tape Engine is running so that
you can immediately inventory your slots.
For media that was created using a previous Arcserve release, this release
automatically creates a new media pool with the same name given to media that
was inventoried and used in a media pool in the previous Arcserve release.
Device Manager
To inventory slots
1.
Right-click a slot and select Inventory/Offline Slots from the pop-up menu.
The Inventory/Offline Slots dialog opens.
2.
Select the slot you want to inventory. Press the Shift key to select multiple
contiguous media. Press the Ctrl key to select multiple non-contiguous media. The
light icon next to selected media turns green.
Note: You can also click and drag the light icon to select multiple contiguous media.
3.
Quick Inventory--The Tape Engine matches the bar code number to the media
serial number, if the library supports bar codes, and the bar code option is
enabled. You can only use this method if you are using the bar code option.
Regular Inventory--The Tape Engine reads all the media information from the
media.
Note: This method is also known as a Manual Inventory.
4.
Click OK.
Arcserve Backup inventories the slots.
Device Manager
2.
From the Magazines drop-down list, select the magazine you want to mount or
dismount.
Depending on the operation that you want to perform, click one of the following:
Mount
Dismount
Device Manager
When importing media, you can choose one of the following methods:
Quick Import--Arcserve Backup imports the media and attempts to use the medias
bar code information to retrieve the corresponding information from the Arcserve
Backup database.
Note: You can only use this method if you are using the bar code option.
Open the Device Manager and browse to the library that you want to configure.
Select the library in the Device Management tree.
2.
Device Manager
3.
Choose Import to view all the available empty slots in a media library.
Note: If your library has a bar code reader, the Serial No. field displays the bar code
number of your tape. You can use the Serial No. field to identify tapes located in a
specific mail slot.
Select the mail slot containing the media you want to assign to your library.
Select the empty slot to which you want to import the media and click Assign.
Arcserve Backup imports the media into the library.
Note: The best practice is to import cleaning tapes to slots that you have
designated as cleaning slots, or set the barcode as a cleaning tape prefix. You can
do this from the Library Properties window of the Device Manager. If you import it
to a different slot, you may receive unrecognized media errors.
4.
Repeat the previous step for each media you want to import.
5.
Open the Device Manager and browse to the library that you want to configure.
2.
3.
4.
Select the Export option to view all the occupied slots in a library.
Highlight the media you want to export.
Select the mail slot to export to, and click Assign.
Arcserve Backup exports the media from the library.
Device Manager
5.
Repeat the previous step for each media you want to export.
6.
Click OK.
The media is exported from the library.
Clean Media
Use this option to clean the tape heads of any media drive in your library.
Note: To use this option, you must have at least one cleaning tape configured in your
library.
To clean media (tape heads)
1.
Note: Offline drives do not appear in the Device Name and Description lists.
2.
From the Choose the cleaning tape slot drop-down list, select the cleaning slot that
you want to use.
From the Clean tape heads within tape device list, select the drive whose head you
want to clean.
Click OK.
Arcserve Backup cleans the tape heads.
More information:
Configure Libraries (see page 374)
Device Manager
Slot number--This option lets you designate specific slots as cleaning slots. You can
specify one or more cleaning slots and they do not need to be in a successive order.
Bar code prefix--This option lets you designate slots based on a bar code prefix.
Example 1: If your cleaning tape bar code number is CLN123, specify "CLN*" as the
bar code prefix.
Example 2: If you are using more than one cleaning tape, and their bar codes start
with ABC, specify "ABC*" as the bar code prefix.
More information:
Add Cleaning Slots Based on Slot Number (see page 413)
Remove Cleaning Slots Based on Slot Number (see page 414)
Configure Cleaning Slots Based on Bar Code Prefix (see page 414)
Open the Device Manager and browse to the library that you want to configure.
2.
Right-click the library and select Library Properties from the pop-up menu.
The Library Properties dialog opens.
3.
4.
5.
6.
Click OK.
You have successfully added cleaning slots based on their slot number.
Device Manager
More information:
How to Configure Cleaning Slots (see page 413)
Open the Device Manager and browse to the library that you want to configure.
2.
Right-click the library and select Library Properties from the pop-up menu.
The Library Properties dialog opens.
3.
4.
5.
6.
Click OK.
The cleaning slots are removed based on their slot numbers.
More information:
How to Configure Cleaning Slots (see page 413)
Open the Device Manager and browse to the library that you want to configure.
2.
Right-click the library and select Library Properties from the pop-up menu.
The Library Properties dialog opens.
3.
Device Manager
4.
Device Manager
Arcserve Backup automatically detects and configures removable drives that are
connected via USB or SATA to a Arcserve Backup primary or member server. Before you
can back up data to a removable drive, you must configure the removable drive and
then bring the removable drive online.
To specify a removable drive as online
1.
Ensure that the removable drive is attached to a Arcserve Backup domain primary
or member server.
2.
Open the Device Manager window and expand the Servers object.
Browse to and select the server to which the removable drive is connected.
Arcserve Backup presents you with a list of devices attached to the selected server.
3.
From the list of devices attached to the server, select and right-click the removable
drive that you want to bring online.
From the pop-menu, select Online.
Arcserve Backup prompts you to confirm that you want to configure the device.
Note: This message displays only the first time that you bring the removable drive
online.
4.
Click OK.
Arcserve Backup prompts you to confirm that you want to bring the device online.
5.
Click OK.
The removable drive is now configured and is in an online state.
Use the Offline removable drive option when you want to perform maintenance,
repairs, or detach a drive from your Arcserve Backup environment. For example:
You do not want to use the removable drive for a period of time and you do not
want to overwrite the media in the drive.
You want to detach the removable drive from the Arcserve Backup server so that
you can replace it with an identical removable drive, or remove it completely from
your Arcserve Backup environment.
Important! When the removable drive is offline, jobs associated with the removable
drive may fail.
Device Manager
2.
From the list of devices attached to the server, select and right-click the removable
drive that you want to take offline.
From the pop-up menu, select Offline.
Arcserve Backup prompts you to confirm that you want to take the removable drive
offline.
3.
Click OK.
The removable drive is now in an offline state in the Device Manager window.
Note: After you mark the removable drive as offline, <Offline> displays in the Device
Manager window.
After you replace the device with a device that is different from the original device
and start the Tape Engine, Arcserve Backup assumes that the device is a new device
and creates a new device group for the device. Since the replacement device is not
associated with the original device group, jobs associated with the original device
group will fail.
To remedy the failed jobs, you must reconfigure the jobs associated with the
original device group and then resubmit the jobs.
Device Manager
After you replace the device with a device that is the same as the original device
and start the Tape Engine, Arcserve Backup assigns the device to the device group
where the original device was assigned.
This behavior ensures that jobs associated with the original device group do not fail.
Limitations:
The replacement device must be a product from the same manufacturer as the
original device.
The replacement device must be the same type of device as the original device
(for example, a single-drive library, a tape drive, and so on).
The replacement device must be connected to the same adapter and channel
as the original device.
The Arcserve Backup server, where the original device is connected, must not
be a member of a SAN domain.
From the Administration menu in the Navigation Bar on the Home Page, select
Device.
The Device Manager window opens.
2.
Device Manager
3.
Note: If you do not want to identify a library as a VTL, repeat the above steps and
remove the check mark from the Library is a VTL check box.
Media Movement
When you insert a media into a magazine slot or remove a media from a slot, you must
either inventory this slot or remount the magazine.
Important! If you are manually inserting media into a library, always insert media into
slots, never into its library drives.
Device Manager
After you start Arcserve Backup, you can use the Device Manager to:
From the Device Manager, click the Device menu and then click Manage Device
Groups.
From the Device Manager window or the Staging Location tab in the Backup
Manager window, click Manage Device Groups located in the device properties
preview pane.
Device Manager
From the Device Manager, click the Device menu and select Manage Device Groups.
The Device Group Configuration dialog opens. Existing groups, and the slots
assigned to each group, are listed here. If you have reserved one of your slots for
cleaning media, it cannot be assigned to a group and it does not appear in this
dialog.
2.
Click New.
The New Group dialog opens.
3.
From the Administration menu in the Navigation Bar on the Arcserve Backup
Manager Console, select Device Group Configuration.
The Device Group Configuration Welcome dialog opens.
2.
Click Next.
The Login Page dialog opens.
3.
Complete the required fields on the Login Page dialog and click Next.
The Options dialog opens.
Device Manager
4.
Select the server that you want to configure, click the Configure Groups option, and
then click Next.
The Device Group Configuration dialog opens. Library devices and their
corresponding slots (available for assignment) display in the Available Devices list.
5.
From the Available Devices list, select the slots that you want to assign to a group.
You can select one available slot at a time, or you can select the library to assign all
of its available slots to a group.
6.
From the Groups list, select the group to which you want to assign the slot.
7.
Click Assign.
Arcserve Backup removes the slot from the Available Devices list and places it in the
Groups list, below the group to which it was assigned.
8.
9.
Click Finish and then click Exit to exit Device Group Configuration.
The slots are assigned to the library groups.
Device Manager
From the Device Manager, click the Device menu and select Configure Groups.
The Device Group Configuration dialog opens.
2.
Highlight the slot you want to remove. Slots are listed in the Groups list beneath the
name of the group to which they were assigned.
3.
Click Remove.
The slot is removed from the group to which it was assigned in the Groups list and
placed in the Available Devices list.
4.
5.
Click OK.
The slots are removed from the library groups.
From the Device Manager window, click Configure Groups (from the list of
functions) or click the Groups toolbar button.
The Device Group Configuration dialog box opens.
2.
3.
Device Manager
From the Device Manager window, click Configure Groups (from the list of
functions) or click the Groups toolbar button.
The Device Group Configuration dialog opens.
2.
3.
Tape drives
Media changers
After you connect the USB storage devices to your Arcserve Backup server, you can use
them for all of your backup and restore operations.
Note: If you disconnect USB devices from the Arcserve Backup server and do not restart
the Tape Engine after disconnection, you can manually assign the disconnected devices
to new groups. These assignments are activated after you reconnect your devices to the
server and restart the Tape Engine. If you restart the Tape Engine after disconnecting
USB devices from the Arcserve Backup server, you cannot manually assign the
disconnected devices to new groups.
Device Manager
More information:
Scan Devices (see page 402)
Ensure that the media is formatted to the NTFS or FAT32 file system.
Note: If you need to format or reformat the media, consult the manufacturer's
documentation for formatting guidelines, or use a Windows-based application to
format the media.
Open the Device Manager window and expand the Servers object.
2.
3.
4.
Device Manager
Filter Libraries
Arcserve Backup lets you use filters to configure the Device Manager to display only the
information you need, thereby increasing data manageability and application
performance.
To filter libraries
1.
Open the Device Manager window and select Preferences from the View menu.
The Preferences dialog opens.
Device Manager
2.
Select the Library Filter tab and specify the filter options that are appropriate to
your needs:
Show device name as Vendor ID and Serial Number--Lets you view device
names as the Vendor ID and the serial number.
Show Empty Slots--Select this option to view the empty slots in the library.
Show Blank Media Only--Select this option to view the blank media in the
library.
Show Tapes within Media Pool--Select this option to view the tapes within a
particular media pool. Wild cards ("*" and "?") are accepted in the media pool.
Show Tapes Matching Serial #--Select this option to view the tapes that match
a certain serial number. Wild cards ("*" and "?") are accepted in the serial
number.
If a filter was applied to the current manager, the status bar will indicate it by
displaying FILTER in the second panel and it will be detailed in the right panel of the
view.
Note: Click Clear to clear all the fields of their information and remove all library
filter criteria.
3.
Optionally, click the Save as Default button after you have entered the criteria for
your library filter to apply the filtering criteria to all Device Manager views.
4.
Click Apply.
The filtering criteria are applied to the current view.
Note: Click the Cancel button to discard the changes to your filtering options.
Device Manager
How Arcserve Backup Supports Write Once Read Many (WORM) Media
Arcserve Backup allows you to back up your data either to rewriteable media or WORM
media. WORM media, with significantly longer shelf life than magnetic media, manifests
secure, long-term storage for data you do not want to erase.
Arcserve Backup lets you mix WORM and non-WORM media in a library. From the
Device Manager, you can identify WORM media by an icon with the letter "W" inside a
red circle. In addition, Arcserve Backup lets you specify WORM media for custom backup
jobs.
The Backup Manager contains three options for Daily, Weekly, and Monthly WORM
media rotations for use with GFS rotations. You can locate these options on the Backup
Manager, Schedule tab, when you specify the Use Rotation Scheme option.
STK Volsafe
LTO3 WORM
SAIT WORM
When a backup job spans tapes and the media is WORM media, Arcserve
Backup needs WORM media to complete the job.
When you are running a backup job that specifies Use WORM Media and there
is no WORM media available, Arcserve Backup may convert blank
WORM-capable media to WORM media for the job.
Note: For these scenarios, the available WORM media must be DLT SDLT-II or
higher.
Device Manager
Arcserve Backup does not automatically assign WORM media to the Scratch Set
in a media pool. WORM media cannot be recycled and as such, is always
assigned to the Save Set in a media pool.
Arcserve Backup cannot use WORM media with file system devices and
Arcserve Backup tape RAID devices.
Identify high-risk tape drives and media that are approaching or have reached their
end of life.
Note: For more detailed information, see How DLTSage Error Handling Works (see
page 430).
Resolving DLTSage Errors
For information about resolving DLTSage errors, see the following:
DLTSage Errors with the Tape Library Option (see page 431)
DLTSage Errors without the Tape Library Option (see page 432)
Device Manager
The tape drive cannot read from or write to a tape, or the media performance is
severely degraded.
Device Manager
If another tape drive is available (empty) Arcserve Backup moves the tape to the
next available tape drive and runs the backup job.
If there are no available drives, Arcserve Backup moves the tape to a tape drive that
is not locked, and runs the backup job.
If all other drives are locked, Arcserve Backup runs the backup job in the current
tape drive.
If the media targeted for the job is loaded, allow it to remain in its current drive and
run the backup job.
If the media targeted for the job is not loaded, identify the last used drive and load
the tape into the next available, empty drive, and then run the backup job.
Device Manager
If Arcserve Backup detects a write error during a backup, and the symptoms relate
to a contaminated tape drive or media, Arcserve Backup makes a second attempt to
write to the tape drive.
If the second write attempt fails, Arcserve Backup cleans the tape drive if one or
more of the following conditions exist:
DLTSage detected the need to clean the tape drive and drive usage exceeds
one fourth of the scheduled cleaning.
If Arcserve Backup determines that a tape drive must be cleaned to continue a job, the
following actions take place:
The library returns the tape to its home slot and locks the tape drive.
The library reloads the tape into the cleaned drive and aligns the tape with the
buffer.
Note: These mechanisms run automatically upon error detection. No user intervention
is required. After Arcserve Backup cures the error, the backup job continues. For more
information about automated error resolution, see the Tape Library Option Guide.
Device Manager
Device Manager
Messages
The messages that follow appear when Arcserve Backup detects that SKM is installed on
the device and the SKM application is offline or not functioning:
Failed Format and Erase Operations--The message that follows opens when Format
and Erase operations fail on SKM controlled devices:
The following Activity Log message appears when Arcserve Backup cannot decrypt
the encryption that is detected on SKM controlled media:
Device Manager
How to Ensure that Arcserve Backup Spans Media in a Single Drive Autoloader
When Arcserve Backup backs up data to a single drive autoloader, and detects there is
no blank media at spanning, Arcserve Backup pauses the job at spanning to let you
insert blank tapes into the drive. This behavior is designed to help ensure that backup
data spans media properly.
When Arcserve Backup spans media and detects no blank media in a single drive
autoloader, the events that follow occur:
1.
Arcserve Backup pauses the job and prompts you to insert blank media into the
autoloader.
Note: If there are no empty slots, you can replace the older media with blank
media. However, you must not replace or remove the media from the recently
spanned slots. While spanning tapes, Arcserve Backup locks the affected slots
during the inventory process. As a result, removing or replacing the spanning tapes
prevents Arcserve Backup from updating the slot information properly. If you insert
media that is not blank, you may inadvertently erase the data from the media using
Device Manager.
2.
After you close the door to the autoloader, Arcserve Backup inventories all media in
the slots.
If the inventory process does not start automatically, you can inventory the media
manually using Device Manager.
Note: You must wait for the inventory process to finish, which can take several
minutes to complete.
After the inventory process is complete, the backup job resumes using the blank
media, after you click OK on the message box that prompted you to replace the
media.
2.
Important! If you do not perform these steps, you must inventory the media manually
using Device Manager.
Device Manager
Media Assure
From the Media Assure & Scan Utility, you can select the Media Assure button to display
the Media Assure Option dialog. This dialog allows you to enable a media assure
operation, which helps you ensure that the sessions on the media are restorable. A
Media Assure job scans sessions randomly based on specified criteria.
After a Media Assure & Scan job completes, check the Activity Log in the Job Status
Manager for errors. Based on the nature of the errors, you can take corrective actions to
remedy the error.
Note: For the Media Assure feature, it depends on the session records in the Arcserve
Backup database. So, if there are no records for the media in the database or the
session records for this media have been destroyed, media assure will not scan any
sessions.
Enable Media Assure--Check this option to enable a media assure scan job that will
select some sessions to scan randomly. Otherwise, it is a regular scan job.
Scan all data in a session--Select this option to scan all session details.
Scan only session headers for each session--Select this option to scan session
headers only and not the session details. This is quicker than scanning all data in a
session, however it may be harder to find the problem.
Sessions that were backed up in the last (number) Days--Specifies the number
of days that sessions were backed up to include in the Media Assure operation.
The default is 7 days. So, all sessions that were backed up in the last 7 days will
be scanned.
Specify the Nodes for which the sessions should be scanned (Using "," to
separate)--Indicates the sessions to scan in the specified nodes. This can be a
wildcard match. For example, if you specify the node name ARC*, sessions will
be selected from the node name ARC001 and the node name ARC002. If you
don't specify any node name, then any session in all nodes may be selected. By
default, all sessions in all nodes may be selected.
Device Manager
If Arcserve Backup detects a write error during a backup, and the symptoms relate
to a contaminated tape drive or media, Arcserve Backup makes a second attempt to
write to the tape drive.
If the second write attempt fails, Arcserve Backup cleans the tape drive if one or
more of the following conditions exist:
DLTSage detected the need to clean the tape drive and drive usage exceeds
one fourth of the scheduled cleaning.
If Arcserve Backup determines that a tape drive must be cleaned to continue a job, the
following actions take place:
1.
2.
The library returns the tape to its home slot and locks the tape drive.
3.
4.
The library reloads the tape into the cleaned drive and aligns the tape with the
buffer.
5.
Device Manager
An error occurs during the process of writing the backup data to the media. For
example, the data is corrupt.
The backup data changed as it transmitted through the network or storage area
network.
When an error occurs, the drive reports a SCSI error in the Tape Engine log file and the
backup will fail.
The Arcserve Backup implementation of LBP does not support the following backups:
To implement LBP, you can create the registry key described in the following procedure.
The registry entry can be created under the DEVICE<#> key in the registry for the
stand-alone tape drive.
Follow these steps:
1.
2.
Note: DEVICE# represents the number of the device where you want to implement
LBP.
3.
4.
Device Manager
Media Maximization
Media maximization is a process that helps optimize disk and tape usage in GFS and
rotation jobs. In a GFS or rotation job, when data is backed up on a scheduled basis to
the same media pool, Arcserve Backup automatically appends the newly backed up data
to a partially filled tape, instead of formatting a new tape each time. Using media
maximization, you can optimize disk and tape space and also reduce the number of
tapes needed to store your GFS rotation job data.
Media maximization can be used with the following types of jobs:
GFS jobs
Custom disk staging jobs using media pools to append backup data
Note: Arcserve Backup applies media maximization to a GFS Rotation job only if the
specified media pool prefix is the same for those sets of jobs that are intended to use
media maximization. For example, you can consolidate data from Job 1 and Job 2 on to
the same tape in media pool A, and you can also consolidate data from Job 3 and Job 4
to another tape in media pool B.
Device Manager
However, in the media maximization process, Arcserve Backup does not back up data to
a media that is already being used by an active backup job. So, you must ensure that the
backup job schedule or migration schedule (in a staging job) is configured so that the
backup or migration of data is sequential. If Arcserve Backup detects that the media is
currently in use, it will revert to formatting a new tape for the second job, rather than
wait for the first job to complete.
GFS rotations--Multiple backup servers are processing GFS backup jobs. Arcserve
Backup will store the backup data on the same media, only if you specify the same
media pool prefix for all of the jobs.
Device Manager
Device Manager
The Consolidate data across jobs while copying option, which is a Miscellaneous option
that appears on the Policies tab, lets you specify if you want to consolidate the data
from different jobs onto a single tape during migration.
Example: How Consolidate Data During Migration Works
You can consolidate data from Job 1 and Job 2 onto the same tape, and you can also
consolidate data from Job 3 and Job 4 to another tape. In this scenario you would need
to do the following:
When submitting a backup of Job1, choose consolidation. Specify the media prefix
as AAA and the media pool as MP1.
When submitting a backup of Job 2, choose consolidation. Specify the media prefix
as AAA and the media pool as MP1.
When submitting a backup of Job 3, choose consolidation. Specify the media prefix
as BBB and the media pool as MP2.
When submitting a backup of Job 4, choose consolidation. Specify the media prefix
as BBB and the media pool as MP2.
If you want data to be consolidated from Jobs 1 and 2 and from Jobs 3 and 4, you must
specify the exact same media prefix and the exact same media pool in each submitted
job. Since the consolidation has to be done to the same tape set you must also choose
the same tape library group in the target destination. In addition, the jobs which are
supposed to consolidate must run on the same backup server.
Important! If any of these four parameters are different (Media Prefix, Media Pool,
target destination, and backup server), the data will NOT be consolidated to the same
tape set.
Device Manager
You can also specify the copy method as either to overwrite the data on a tape or to
append to the data on an existing tape.
Overwrite--If you have a requirement to consolidate data across multiple jobs and
ship the tapes on a daily basis, you should choose the Overwrite option. This will
ensure that a tape is formatted on a daily basis and all the data backed up on that
day would be migrated to a single tape.
For example, if you have two jobs (Job 1 and Job 2) and you want to ship the tapes
offsite on a daily basis. In this scenario you would choose Overwrite. When the
backup job finishes on Monday, Arcserve Backup would format a final tape for
Monday and copy the data from the staging tapes of Jobs 1 and 2 to the final tape.
Then, after the backup finishes on Tuesday, Arcserve Backup would format a final
tape for Tuesday and copy the data from staging tapes of Jobs 1 and 2 to the final
tape. This way a tape is formatted every day and helps you to ship the tapes offsite
on a daily basis.
Append--If you have a requirement to consolidate data across multiple jobs (for
daily backups) for the whole week to a single tape and ship the tapes on a weekly
basis, you should choose the Append option. This will ensure that for example, in
5-day GFS rotation jobs, all the incremental or differential data (belonging to
different jobs) that are backed up on Monday, Tuesday, Wednesday, and Thursday
is consolidated to one tape set. The full backups that happen (for different jobs) on
Friday would be consolidated to another tape set.
For example, if you have two jobs (Job 1 and Job 2) and you don't want to ship the
tapes offsite on a daily basis. In this scenario you would choose Append. When the
backup job finishes on Monday, Arcserve Backup would format a final tape for
Monday and copy the data from the staging tapes of Jobs 1 and 2 to the final tape.
Then, after the backup finishes on Tuesday, Arcserve Backup would copy and
append the data from staging tapes of Jobs 1 and 2 to the final tape from Monday.
A new tape would not be formatted and only one tape would be formatted for the
entire week of daily backups. This helps you utilize your tapes more efficiently.
Device Manager
The following diagram shows the tape usage requirements if you do not enable the
consolidate during migration option:
The following diagram shows the tape usage requirements if you enable the consolidate
during migration option:
the minimum number of media that must be contained in the Save Set
The following diagram shows how a typical media pool processes a backup job and the
movement of Save Sets and Scratch Sets within a media pool:
Save Sets
The media pool Save Set is a set of media that cannot be overwritten until the media
pool's retention requirements that you specify have been met. You can modify Save Set
information for all Custom backup jobs, move media from the Save Set to the Scratch
Set, or you can move media from one media pool Save Set to another media pool Save
Set.
You define the minimum number of media that must be contained in the Save Set and
the retention period (in days). These settings determine how long media will be held.
After both of these criteria have been satisfied, Arcserve Backup releases the oldest
media in the Save Set back into the Scratch Set, where it can be recycled and re-used
(overwritten).
The retention period is the number of days in which a media has not been used
(written to) before it is moved into the Scratch Set. For example, if you specify a
retention period of 14 days, a media remains in the Save Set if it has been used
within that specified time. If the media has not been used for 14 days, it is moved to
the Scratch Set.
The minimum number of media contained within the Save Set is the number of
media that must 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.
Note: You will receive a warning if you attempt to format or erase media that is
contained in a Save Set.
Scratch Sets
The media pool Scratch Set is a set of media that has been recycled from the Save Set
after its specified retention criteria has been satisfied. The media from the Save Set that
can be re-used and overwritten are placed in the Scratch Set after they have met the
specified criteria (the minimum number of media to save and retention period). The
oldest media in the Scratch Set, those that have not been used for the longest period of
time, are used first.
Each time a media in the Scratch Set is used, it moves from the Scratch Set to the Save
Set. The media moves back to the Scratch Set once the specified retention criteria have
been met. If the media meets these retention criteria, Arcserve Backup prompts for a
blank tape or accepts media from the Scratch Set.
Arcserve Backup performs media pool maintenance at the beginning of a job, and will
not allow media in the Save Set to be moved to the Scratch Set until the two retention
criteria are met. When you select a media pool Scratch Set in the left pane of the Media
Pool Manager, the right pane will display the media pool name, the set name, the owner
name, and the date the Scratch Set was created.
When the media meets certain criteria in a Save Set (minimum number of media in Save
Set and retention period) they are recycled to the Scratch Set. Each time a media in the
Scratch Set is written to, it moves from the Scratch Set to the Save Set. Additionally, if
Arcserve Backup detects non-blank media in the Scratch Set, the Media Pool Manager
controls the usage of the media such that WORM media containing data is not used.
The retention period is the number of days in which a media has not been used before it
is moved into the Scratch Set. For example, if you specify a retention period of 14 days,
a media remains in the Save Set if it has been used within that specified time. If the
media has not been used for 14 days, it is moved to the Scratch Set.
You define the minimum number of media contained within the Save Set. This is the
number of media 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.
Media pools apply to every media, regardless of which backup type and method were
selected. Arcserve Backup performs media pool maintenance at the beginning of a job,
and will not allow media in the Save Set to be moved to the Scratch Set until two criteria
are met:
The oldest tape in the Save Set is compared and exceeds the retention time.
If the media meets these criteria, Arcserve Backup prompts for a blank tape or accepts
media from the Scratch Set.
Serial Numbers
The serial number of a media is one way to categorize media pools. You cannot change
the serial number of media, but you can create a serial number for media by:
Bar code--A number is read from a bar code label and this number becomes the
serial number. A changer with a bar code reader is required for this method. This
will override any previously defined media pool settings.
Base--This is the base number, which Arcserve Backup will use when
automatically assigning serial numbers. The first media formatted will have the
same serial number as the base number. Each medias serial number thereafter
will be increased by one.
Range--You can specify the range (up to 31 digits) from which the media pool
serial numbers will be categorized.
Where..
Is
backup type
F - full backup
I - incremental backup
D - differential backup
W - weekly backup
M - monthly backup
A - all daily backups (full, incremental, and differential)
when you use the Media Maximization option
(enabled by default) and enable the Append Media
option. For more information on the Media
Maximization option, see the section Media
Maximization in GFS Rotation Jobs.
user-defined media pool prefix The name you assigned to the media pool for your
GFS Rotation scheme.
day of the week
Date
This media naming convention allows you to easily identify backup media. For example,
the media used for the first full backup in your rotation scheme will have the following
name: F TP MON 11/1/05.
Note: Arcserve Backup prevents you from using the underscore character ( _ ) and the
hyphen character ( - ) when specifying Media Pool names.
Five-day rotation schemes have the following retention times for each media pool:
Daily (_DLY)--six days (daily media in seven-day Rotation Schemes have a retention
time of eight days)
The following are the formulas used for calculating the number of media in the Save
Sets and the retention times for the GFS media pools:
Daily pool--This pool holds the media for daily backup jobs. 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].
Weekly pool--This pool holds the weekly media. The retention period equals the
number of weekly media times seven, minus one [(# of weekly media * 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].
Monthly pool--This pool holds the monthly media. The retention period equals the
number of monthly media times 29 minus five [(# of monthly media * 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].
More information:
Media Maximization in GFS Rotation Jobs (see page 450)
More information:
GFS Media Pools (see page 449)
Use the same Rotation Scheme--GFS jobs that use different rotation schemes may
need different tape names. To ensure that multiple GFS jobs will share the media,
use the same rotation scheme.
Start GFS jobs on the same day--The first day of a GFS job is a full backup. Jobs that
start with different dates may not be able to share media during the first week. To
ensure that multiple GFS jobs will share media during the first week, start GFS jobs
on the same day. Otherwise, media sharing will begin after the weekend.
If you want to modify multiple GFS backup jobs to use a new media pool, modify
them on the same day--This ensures that all jobs will share the media right away.
Otherwise, media sharing will begin after the weekend.
Modify existing GFS jobs to use the same media pool as other GFS jobs--If the
existing GFS jobs you modified use the same rotation scheme, media sharing should
begin right away. However, if any of the jobs have been running for less than one
week, media sharing may begin after the weekend.
Monday = One tape that includes full backup data from job 1(day 1), job 2(day 1),
and job 3(day 1)
Tuesday = One tape that includes incremental backup data from job1(day 2), job
2(day 2), and job 3(day 2)
Wednesday = One tape that includes incremental backup data from job 1(day 3),
job 2(day 3), and job 3(day 3)
Thursday = One tape that includes incremental backup data from job 1(day 4), job
2(day 4), and job 3(day 4)
Friday = One tape that includes weekly backup data from job 1(day 5), job 2(day 5),
and job 3(day 5)
Monday = Three full backup tapes. One tape for job1(day 1), one tape for job 2(day
1), and one tape for job 3(day 1)
Tuesday = Three incremental backup tapes. One tape for job1(day 2), one tape for
job 2(day 2), and one tape for job 3(day 2).
Wednesday = Three incremental backup tapes. One tape for job1(day 3), one tape
for job 2(day 3), and one tape for job 3(day 3).
Thursday = Three incremental backup tapes. One tape for job1(day 4), one tape for
job 2(day 4), and one tape for job 3(day 4).
Friday = Three Weekly backup tapes. One tape for job1(day 5), one tape for job
2(day 5), and one tape for job 3(day 5).
Without the Media Maximization option, you need 15 tapes for the week.
Note: When submitting multiple GFS Rotation Jobs with the same media pool without
Append Media enabled, tapes can be shared only if the same Backup Method is used.
For example, a tape that has data from a full backup job can be shared only with data
from another full backup job. It cannot be shared with data from incremental,
differential, weekly, or monthly backup jobs.
To share tapes among different jobs with different backup methods, Arcserve Backup
uses the same GFS rotation naming syntax, but it uses a different naming convention for
backup types when the Append Media feature is enabled:
(backup type)-(user-defined media pool prefix)-(day-of-the-week)-(date)
F - full backup
I - incremental backup
D - differential backup
W - weekly backup
M - monthly backup
A - full backup
A - incremental backup
A - differential backup
W - weekly backup
M - monthly backup
If you submit GFS rotation jobs with the Append Media feature enabled, you can
maximize media usage by submitting multiple jobs using the same media pool and use
the previous day's tape within the current week.
For example, if you submit three GFS rotation jobs all using the same media pool and
5-day rotation scheme, all three jobs share the same set of tapes. In addition, multiple
days can share the same tape, drastically reducing the amount of tapes you use:
Monday, Tuesday, Wednesday, Thursday = One tape that includes full backup data
from job 1(day 1), job 2(day 1), and job 3(day 1), and incremental backup data from
job 1 (days 2, 3, and 4), job 2(days 2,3, and 4), and job 3(days 2,3, and 4).
Friday = One tape that includes weekly backup data from job 1(day 5), job 2(day 5),
and job 3(day 5)
Monday = Three full backup tapes. One tape for job1(day 1), one tape for job 2(day
1), and one tape for job 3(day 1)
Tuesday, Wednesday, Thursday = Three incremental backup tapes. One tape for
job1(days 2, 3, and 4), one tape for job 2(days 2, 3, and 4), and one tape for job
3(days 2,3, and4).
Friday = Three weekly backup tapes. One tape for job1(day 5), one tape for job
2(day 5), and one tape for job 3(day 5).
This results in nine tapes for the week.
Note: If you submit a GFS Rotation job with Append Media enabled and Arcserve
Backup cannot use the previous day's media for some reason, it will format a media in
the Scratch Set or a blank media using the With Append Media naming convention. To
minimize the likelihood of this situation occurring, see Media Maximization Rules in this
chapter.
Create a new media pool--To assign media to a media pool, you first need to create
the media pool. A media pool name can consist of up to 16 uppercase characters.
Delete an existing media pool--To delete a media pool, you must first re-assign the
media to another media pool.
Move media in a pool--You can move media from one set to another. You can also
move media from a Scratch Set to a Save Set and vice versa by using the Assign
Media and Remove Media options.
Assign media to a media pool--You can assign media to a media pool during the
process of formatting. When you format media using Device Management, you
define certain media pooling information that will be associated with the media.
Remove media from a media pool--You can remove media from a media pool.
Note: Media Pool operations, backup jobs using the Overwrite option, Tape Erase
operations, and backup jobs involving Media Pools (such as GFS rotation jobs) are not
supported on WORM (Write Once Read Many) media. These operations are either
blocked or disabled in WORM support updates.
From Administration menu in the Navigation Bar on the Home Page, click Media
Pool.
The Media Pool Manager opens.
2.
3.
Enter a name for the media pool in the Pool Name field. Fill in the remaining fields
appropriately.
The Minimum # of media in Save Set, Retention Time, Prune Retention Time, Base
Serial Number, and Serial Number Range fields contain default values that you can
change if desired.
Note: The Next Serial Number field cannot be set.
4.
Vault Name--A vault name must be specified for each rotation. You can select the
name of a vault from the drop-down vault list.
Keep for Cycles--The number of vault cycles you want tape volumes to be
retained in this rotation.
Days Elapsed from First Format Date--Starting from the day the tape volumes
were first formatted, enter the number of days you want tape volumes to
remain in this rotation.
By Date--Tape volumes are retained in this rotation until the date you enter
here is reached.
By Tape Expiration Date--Tape volumes are retained in this rotation until their
expiration date passes.
If a tape volume meets one of these conditions, it remains in the same rotation. None of
these conditions have priority over the other so if any condition is true, the media will
stay in the vault--even if conditions appear to conflict. For example, if you select 60 in
the Hold Days field but enter a date that is only 30 days away in the By Date field, the
tape volume will stay for 60 days.
When you click Add, the new rotation is saved and added to the Rotation branch in the
MM management window.
When the Retention period for a tape volume expires, the tape volume is unvaulted and
returned to Tape Service to be re-used.
MM Admin Interface
Slot--Virtual slots in a vault are assigned when a tape volume is vaulted. Each slot is
used to store one tape volume. By default, there are 32000 slots in a vault, but you
can designate a different maximum number of slots as you create a vault.
Vault Criteria Descriptor (VCD)--Defines the controlling data set you want to use for
the selected tape volume. You can choose the controlling data set by media name
or file name, or you can select an individual media as the controlling data set.
Vault cycle--The actual movement of tape volumes. You must describe the vault,
the tape volumes, and the rules for tape volume movement under the MMO by
creating a Vault Criteria Descriptor (VCD) record. The MMO uses this descriptive
information to execute a vault cycle when movement is scheduled.
Reports--Each time you execute a vault cycle or an estimated vault cycle, Arcserve
Backup generates several reports before another vault cycle can be initiated. The
Vault Selection Report contains a list of tape volumes to be selected for moving into
the vaults through the VCD. The Shipping Report and the Receiving Report provide a
reliable record of the result of the vault cycle and the current location of your tape
volumes.
The Shipping Content Report and the Receiving Content Report provide you with
basic session detailsin addition to the information contained within the Shipping
Report and the Receiving Reportsuch as the session number, source path, start
date, size, and number of files.
An Inventory Report is also available, which you can generate at any time.
MM Admin Interface
The MM Admin interface is designed to make vault creation, scheduling, VCD creation,
rotation, and report creation easy. The tools provided by MM Admin allow you to
establish the vaulting policy needed for complete Media Management.
The MM Admin workspace includes a menu bar, the main MM Admin toolbar, and the
MM management window. The left pane of the MM Management window displays the
MM primary management server in a tree structure for easy navigation. The right pane
displays information related to the object selected in the left pane. It also displays any
output messages and reports generated during your MM Admin session.
MM Admin Interface
MM Admin Toolbar
The following table describes tasks that you can perform using the Media Management
Administrator (MM Admin). Click the corresponding toolbar button to start the task.
Button
Task
Initialize MM Database
Retrieve Data
Refresh
Property
Print Preview
MM Admin Window
The objects in the left pane of the MM Admin window are arranged in an expandable
tree. To view related information, double-click the branch you need. After you access a
branch, you can add, modify, or delete objects from the tree structure using the
available pop-up menus. Right-click any object to access pop-up menus.
MM Admin Interface
When you open MM Admin, the MM primary management server is displayed at the
top of the tree. Double-click the branch to expand it and access the following objects:
Current Server--Displays information about the server you are currently using.
Schedule--Lists the names of the previously created schedules, and allows you to
access the Vault Criteria Descriptor and Rotation objects.
Find Media in Vault--Lets you access the Find Media dialog to locate a particular
media.
Schedule Object
The Schedule object provides information about previously defined schedules and
allows you to create new schedules. You must create a schedule before you define the
Vault Criteria Descriptor and Rotation that determine selection and retention policies
for your vault.
When you select the Schedule object, the right pane of the MM Admin window displays
the names of previously defined schedules. These schedules are also listed under the
Schedule object in the left pane. Right-click the Schedule object to create a new
schedule. Right-click a specific schedule to delete it. For more information about
creating or deleting a schedule, see the section How You Can Schedule Tape Volume
Movement.
After you have named and created a schedule, the Vault Criteria Descriptor (VCD) and
Rotation objects appear in the left pane of the MM Admin window.
MM Admin Interface
When you select the Vault Criteria Descriptor object, the right pane of the MM Admin
window displays columns listing the following information for existing VCDs:
VCD Type--Indicates whether the controlling data set is defined by media pool, file
name, or by user.
Media Pool--If the controlling data set is a media pool, the name of the media pool
appears.
Host Name--If the controlling data set is a file name, the host where the file resides
appears in this column.
Path/File Name--If the controlling data set is a file name, the full path and file name
appear in this column.
In the right pane of the MM Admin window, right-click an existing VCD to update or
delete it. Right-click the Vault Criteria Descriptor object in the left pane to create a new
VCD. For more information about creating, updating, or deleting a VCD, see the section
How You Can Manage Tape Volumes and VCDs.
More information:
How You Can Manage Tape Volumes and VCDs (see page 469)
Rotation Object
Media management relies upon user-defined rotation policies to determine when and
where tape volumes should be moved. Use the Rotation object to set or update the
retention policies that determine when tapes will be moved or released from the vault
and returned to Tape Service.
When you select the Rotation object, the right pane of the MM Admin interface lists the
following information about previously defined rotations:
Retention Hold Days--Starting from the Last Write date (the date the media was
last written to), this indicates the number of days that the tape volumes will be held
in this rotation.
Note: To view the Last Write date, expand the Vault object and highlight a media
name in the top right-hand pane. The Last Write date appears in the lower
right-hand pane.
Retention Keep for Cycles--Indicates the specific number of vault cycles and tape
volumes that are held in this rotation.
MM Admin Interface
Retention Days Elapsed from First Format Date--Indicates that tape volumes are
held in this rotation until a specified number of days have elapsed since they were
first formatted.
Retention By Date--Indicates that tape volumes remain in this rotation until the
specified date has passed.
Existing rotations are also listed in the right pane of the MM Admin window under the
Rotation object.
To update an existing rotation, right-click the rotation name and select Update from
the pop-up menu.
To create a new rotation, right-click the Rotation object and select Create.
Reports Object
Although tape volume location information in the database is updated when you initiate
a vault cycle, the physical movement of tape volumes is done manually. MM Admin
generates reports indicating the current location and destination where the tape
volumes must be moved so that you can route them to other storage locations and back
to the data center, as necessary.
MM Admin Interface
The Reports object provides access to the reports generated by the vault cycle process
and the Inventory reports, which can be generated at any time. Expand the Reports
object in the left pane of the MM Admin window to view the following report types:
Shipping Content Report--Contains a list of tape volumes and sessions in each tape
volume to be pulled from each of the vaults.
Receiving Content Report--Contains a list of tape volumes and sessions in each tape
volume to be distributed to the vaults.
The Inventory Report, By Vault--Lists tape volumes grouped by the vault where
they reside.
The Inventory Report, By Media--Lists tape volumes grouped by vault and shows
Media name in front.
When you select a report type in the left pane of the MM Admin window, the right pane
displays the contents, listing the available reports identified by date. Click a report to
view it in the right lower pane. You can print any of these reports using the Print button
on the MM Admin toolbar. At the time it is generated, you can also select to send a
report by email if you configure the alert notification system to use Microsoft Exchange.
For more information on sending reports using email, see How the Media Management
Process Works (see page 465). For more information on using alerts, see Using the
Alert Manager.
The Inventory Reports are based on information in the Slot table, and can be generated
at any time. The Shipping and Receiving Reports are based on movement records
generated during a vaulting cycle, and are updated after each vault cycle process
completes.
The Vault Selection Listing is produced each time the Start Vault Cycle command is
executed. For each VCD processed, this listing identifies the first tape volume in the tape
volume set and the controlling data set. This information is provided for all tape volume
sets selected for the vaulting cycle.
MM Admin Interface
Status Object
MM Admin can run only one vault cycle at a time. To monitor the progress of the vault
cycle, or to obtain current online status, double-click the Status object in the left pane of
the MM Admin interface to view the following information:
Last Operation Started At--The date and time the last operation began.
Last Operation Finished At--The date and time the last operation ended.
When using Media Management Administrator (MM Admin), the vault cycle
processes tapes for the primary server and all of the member servers.
You must click the Start Vault Cycle button every time you want current information
on the MM location of the media.
Execute the Start Vault Cycle process to generate reports detailing the movement of the
tape volumes and location information. The slots that already contain tape volumes and
the new slots that will be vaulted are grouped together by their common schedule.
Beginning with the first rotation in the schedule, tape volume sets are assigned to a
vault and its slots based on the expiration criteria. Slots are automatically created and
tape volumes automatically vaulted during this process.
When the first rotation is satisfied, the next rotation in the schedule is processed, and so
on through the entire schedule until all rotations have been exhausted. Media
management then generates reports indicating the current location and destination
where the tape volumes must be moved. If you do not want to remove these tapes
manually, you can use the ca_mmo -export command at the DOS prompt so MM Admin
automatically exports them. See Device Manager (see page 395) for more information
about command line utilities for media management.
You can use the Simulate Vault Cycle command to produce a Vault Selection Report. Use
this command at any time to predict how many tape volumes will be moved without
actually updating the location information. If you want to send the Vault Selection
Report to someone by email, make sure your system is configured to send alerts using
Microsoft Exchange and, from the Configuration menu, enable the option Send the
report by E-mail. For more information on configuring alerts, see Using the Alert
Manager."
The vault cycle generates the Shipping and Receiving Reports, listing the old and new
locations of the tape volume set, to provide you with the information you need to
manage your media. These reports provide the following information:
Shipping Report--tells you what media to pull manually, and where to send it.
Shipping Content Report--lists all tape volumes and sessions in each tape volume to
be pulled from each of the vaults.
Receiving Report--tells you what media will be coming in to each particular vault.
Receiving Content Report--lists all tape volumes and sessions in each tape volume
to be distributed to the vaults.
If you want to send the shipping and receiving reports to someone by email, make sure
your system is configured to send alerts using Microsoft Exchange and, from the
Configuration menu, enable the option Send the report by E-mail. For more information
on configuring alerts, see Using the Alert Manager.
When a tape volume comes under Media Management control, Tape Service updates
the tape volume's location status to OFF_SITE. To prevent a tape volume from being
used while under Media Management control, the tape volume is automatically checked
out, and the location is updated to reflect this. Because all vaulted tape volumes are
placed in checked out status, if you need to retrieve tape volumes, they must be
checked into Tape Service before they can be used.
Vault Management
The first step in establishing a vaulting policy is to create a vault. You can create vaults
using MM Admin.
This section contains the following topics:
Create Vaults
When you create a vault, location information is automatically updated and integrated
with the Location Maintenance feature in Arcserve Backup. If you select a vaulted tape
through Arcserve Backup, vault location information appears. Location information is
also updated in the Media Pool Manager. If you select a vaulted tape for restore, a
message appears indicating that the tape is OFF_SITE.
To create vaults
1.
From the Arcserve Backup Home page, open the Media Management Administrator
window.
2.
Right-click the Vault object and select Create from the pop-up menu.
The Create Vault dialog opens.
3.
4.
Select the Use in Local option if this vault will not be moved to another location. If
the tape volumes in this vault are to be maintained off site, do not select this
option.
5.
Click Add to save and add the vault to the Vault branch in the Media Management
Administrator window.
The vault is created.
Modify Vaults
Use the following steps when you want to modify the Vault Name, Vault Description, or
Use in Local option.
To modify vaults
1.
From the Administration menu in the Navigation Bar on the Home Page, click MM
Admin.
The Media Management Administrator window opens.
2.
Browse to and double-click the Vault object in the left pane of the Media
Management Administrator window.
A list of existing vaults displays.
3.
Right-click the vault you want to modify from the list, and select Modify from the
pop-up menu.
The Edit Vault dialog opens
4.
Delete Vaults
Use the following steps to delete vaults from the MM Admin.
Note: Before you delete a vault, you must remove all media from the vault and ensure
that there are no rotations are associated with the vault.
To delete vaults
1.
Open the Media Management Administrator window and browse to the vault that
you want to delete.
2.
Right-click the vault name and select Delete from the pop-up menu.
A delete confirmation message box opens.
3.
If you are sure that you want to delete the vault, click Yes.
The vault is deleted.
Create Schedules
Media Management relies upon a user defined schedule to determine the tape volumes
to move, and when and where to move them. When you select the Schedule object, you
can view existing schedules in the right pane of the Media Management Administrator
window or you can define new rotation policies and vaulting criteria.
To create schedules
1.
Open the MM Admin, right-click the Schedule object in the left pane of the Media
Management Administrator window, and select Create from the pop-up menu.
The Create Schedule dialog opens
2.
On the Create Schedule dialog, specify a name for the schedule and click Add.
The new schedule is saved and added to the Schedule branch in the Media
Management Administrator window.
After you create a schedule, the Vault Criteria Descriptor (VCD) and Rotation
objects appear in the left pane of the Media Management Administrator window.
These objects allow you to select media and retention policies.
Modify Schedules
After a schedule is created and the corresponding VCD and Rotations are configured,
you can then modify each of these subordinate settings. For more information, see
Modify Vault Criteria Descriptors (VCD) (see page 470) and Modify Rotations (see
page 474).
2.
Right-click the Schedule object that you want to delete and select Delete from the
pop-up menu.
A confirmation window appears.
3.
Verify that this is the Schedule that you want to delete and then click Yes.
The schedule is deleted.
From the Administration menu in the Navigation Bar on the Home Page, click MM
Admin.
The Media Management Administrator window opens.
2.
Expand the Schedule object, expand a schedule, right-click Vault Criteria Descriptor
object, and select Create from the pop-up menu.
The Create Vault Criteria Descriptor dialog appears.
3.
Media Pool Name--To use a media pool name as the controlling data set, enter
the name of the media pool or use the drop-down list to select a media pool
name from the pool list. Only the media within the Save Set of the media pool
can be vaulted. The media in the Scratch Set cannot be vaulted.
File name--To use a file name as the controlling data set, select the File Name
option and enter the host name and the full path and file name from your
backup, such as C:\DOC\Readme.txt, in the appropriate fields. Browse through
the Database or Restore Manager to obtain path or file information. The MM
Admin finds all tapes used for the backup of this directory or file.
4.
Click Add.
The VCD is added to the Vault Criteria Descriptor branch in the Media Management
Administrator window.
Open the MM Admin, expand the list of schedules under the Schedule object and
select a schedule from the list.
Expand the schedule to display the Vault Criteria Descriptor and Rotation objects.
Right-click the Vault Criteria Descriptor object and select Modify from the pop-up
menu.
The Edit Vault Criteria Descriptor dialog opens.
2.
Modify the Media Pool Name, the File Name, the Assigned by User option
associated with the VCD and click OK.
The modified value is applied.
From the Schedule object, select the specific VCD from the list under the Vault
Criteria Descriptor.
2.
3.
Click OK.
Temporary Check In
The Temporary Check In option is useful for tracking media movement if you want to
temporarily move a tape volume from a vault to use for a restore job, but want to
return it back to the vault when the job is finished.
All tape volumes that are vaulted are in checked out status. Use the Temporary Check In
option to change this status to checked in so that you can keep track of your tape
volume while it is temporarily being used for a restore job. When you finish using the
tape volume, the next vault cycle returns it to the vault and changes the status back to
checked out.
Note: The Temporary Check In option is only for tracking tapes that are temporarily
returned from the vault, and is not a requirement for the actual tape movement; if you
do not use this option, you can still manually move a tape volume from a vault and
return it when a job is finished. However, you should use this option because, if you do
not use it and move a tape volume, there will be a discrepancy between the status of
the tape volume that appears in the MM Admin and the actual location of the tape.
To use the Temporary Check In option, in the left pane of the MM Admin window,
double-click the Vault object to see a list of existing vaults. Select a vault to display its
information in the right pane. Select the name of the media you want to move,
right-click, and select Temporary Check In.
Example: Temporary Check In
For example, to perform an emergency restore operation using a tape volume from one
of the vaults, use the Temporary Check In feature to temporarily check the tape volume
in to Tape Service, execute the restore operation, and then run a vault cycle to return
the tape volume to the vault.
From the left pane of the MM Admin window, double-click the Vault object.
A list of existing vaults displays.
2.
Permanent Retention
Use the Permanent Retention option to permanently vault slots and the tape volumes
they contain. If you use this option, when a tape volume is vaulted, it does not return to
Tape Service. The only way to return it is to change the vault status back to the default.
To permanently check tape volumes out of Tape Service, select the Permanent
Retention option on the Create Rotation dialog.
Create Rotations
Media Management relies upon rotation policies to determine when and where tape
volumes should be moved. You can define rotation policies using the Media
Management Administrator interface.
Before you create a rotation, you must create a schedule. If no schedule has been
created, you cannot access the Rotation object.
To create a rotation, perform the following procedure:
1.
2.
3.
4.
5.
6.
Enter a Vault Name for your rotation. You can select a vault name from the list.
7.
8.
Keep for Cycles--The number of vault cycles you want tape volumes to be
retained in this rotation.
Days Elapsed from First Format Date--Starting from the day the tape volumes
were first formatted, enter the number of days you want tape volumes to
remain in this rotation.
By Date--Tape volumes are retained in this rotation until the date you enter
here is reached.
By Tape Expiration Date--Tape volumes are retained in this rotation until their
expiration date passes.
Click Add.
The new Rotation is saved and added to the Rotation branch in the Media
Management Administrator windows.
Modify Rotations
Use the steps that follow to modify the movement of tape volumes associated with a
schedule.
To modify rotations
1.
Expand the Schedule object in the left pane of the MM Admin window and select a
schedule from the tree.
2.
3.
Double-click the Rotation object and select a rotation in the right pane.
4.
5.
Delete Rotations
If you want to delete a schedule, you must first delete the associated rotation and VCD.
To delete rotations
1.
From the left pane of the MM Admin window, expand the schedule object, and the
expand schedule for the rotation that you want to delete.
The rotation displays in the right pane of the MM Admin window.
2.
From the right pane of the MM Admin window, select the rotation from the list.
3.
Right-click the rotation that you want to delete and select Delete from the pop-up
menu.
A confirmation message appears
4.
Click Yes.
The rotation is deleted.
Media Name--Lists the media name, ID, sequence number, and serial number.
Slot Status--Either Active, Unvaulted, Temporary Check In, Manual Check In, or
Manual Check In and Retire:
Temporary Check In--The media will be checked in temporarily during the next
vault cycle.
Manual Check In--The media will be checked in during the next vault cycle.
Manual Check In and Retire--The media will be checked in and retired during
the next vault cycle.
Ready--The default status. The media has been assigned to the vault, but has
not been exported from the tape library to the mail slot yet.
Local--Either Yes or No. Yes appears if the media belongs to a local machine. No
appears if it belongs to a remote machine.
When you highlight a media name, additional information appears in the Properties
pane in the lower right-hand corner of the page. This information includes the media
name, serial number, random ID, host name, slot status, slot name, media export status,
media type, media class, last write, last read, and slot creation date. Because MM
Admin lets you start a vault cycle only with local media, the media icon appears in
yellow if the vaulted media is not a local media with a remote host name. If you want to
start a vault cycle with a remote media and member servers, use the ca_mmo -startall
command line utility.
Note: For more information about command line utilities for media management, see
the Command Line Reference Guide.
Because slots are automatically created when a tape volume is vaulted, you typically
have no reason to update slot information.
From the Administration menu in the Navigation Bar on the Home Page, click MM
Admin.
The Media Management Administrator window opens.
2.
From the Media Management Administrator window, right-click the Find Media in
Vault object and select Find from the pop-up menu.
The Find Media in Vault dialog opens.
3.
Find by Tape Name--Lets you enter the tape name, the random ID, and the
sequence number to identify the tape you want Arcserve Backup to find.
Find by Serial Number--Lets you enter the serial number of the desired media.
Arcserve Backup completes the Find by Serial Number task using case-sensitive
values. For example, the serial number ABC123 is different from the serial
number abc123.
4.
Click Find.
When the search is finished, the vault and slot information appears in the right
pane of the Media Management Administrator window.
Arcserve Backup does not support Tapecopy using the cloud-based device feature.
Arcserve Backup does not allow multiple cloud-based devices to point to a single
cloud folder or group at the same time. This may cause data corruption.
2.
From the Servers directory tree, locate the server you want to configure.
Select Manage Cloud Connection from the toolbar to configure your cloud
connections.
Note: You can also select Manage Cloud Connection by right-clicking the specific
server in the Servers directory tree and select Manage Cloud Connections or click
the Manage Cloud Connection link in the Servers details section.
The Cloud Connection Configuration dialog opens.
3.
4.
Complete the required fields on the Add Connection dialog and click OK.
Note: The fields that appear on the Add Connection dialog vary based on the cloud
vendor that you are using.
The Add Connection dialog contains the following fields:
Access Key ID or Query ID--Specify the account name for the cloud connection.
Secret Access Key or Secret Key--Specify the password for the cloud
connection.
Vendor URL--Specify the vendor's URL. Typically, this field defaults to the URL
of the public vendor you selected. If you selected a private vendor, it is then
required for you to enter the URL.
Description
Do not use proxy--Select this option if you want a cloud vendor connection to
bypass the settings from the Proxy Settings dialog. Arcserve Backup directly
connects to the cloud vendor instead of going through the proxy.
Advanced
5.
Click OK to close the Add Connection dialog to save the configuration and return to
the Cloud Connection Configuration dialog.
6.
7.
From the Cloud Connection Configuration dialog, click Add to add more cloud
connections or click close to apply the configurations.
asterisk (*)
semicolon (;)
blank space
ampersand (&)
Important! You cannot link multiple cloud-based devices from different servers under a
single cloud folder at the same time. This may cause data corruption.
2.
3.
From the Login Server dialog, provide the required login credentials for the Primary
Server and click Next.
4.
From the second Login Server dialog, select the server that you want to log in to
and click Next to open the Cloud-Based Device Configuration dialog opens. The
Cloud-Based Device Configuration dialog displays a list of Devices and any
corresponding cloud information.
Note: You create the cloud connections before you create cloud-based devices. For
more information, see Create Cloud Connection Configuration (see page 478).
5.
Click Add.
A new, blank device is added.
6.
Device Name--In the Device Name field, enter a name, or accept the default.
Cloud Folder--In the Cloud Folder field, enter the folder name where the
cloud-based device resides, or click the arrow button next to the field to launch
a new window to browse for a cloud folder for the specific cloud-based device.
Note: You can also browse for an existing cloud folder directly from the Device
Manager screen. For more information, see Browse Cloud Folder (see
page 483).
7.
Group Name--(Optional) In the Group Name field, enter a name for the group.
Note: You can also launch the Cloud-based Device Configuration through Device
Manager and Device Configuration:
Device Manager:
Click the Manage Cloud-based Device button from the toolbar;
Device Configuration:
1.
From the Manager Console, click the Navigation Bar and expand the
Administration menu.
2.
3.
2.
From the Device Manager, there are three ways you can launch the Browse Cloud
Folder feature:
Right-click the specific server in the Servers directory tree and select Browse
Cloud Folder;
OR
Click the Browse Cloud Folder link in the Servers details section.
3.
Select a Cloud Connection Name to display the list of Cloud Folders where your
Cloud-based Device resides.
The Cloud Folder displays the tape name of the cloud-based device, the compressed
size and file size of the cloud folder.
Be aware of the following:
You can also browse for a cloud folder when creating a cloud-based device. For
more details, see Create Cloud-Based Devices (see page 480).
From the Cloud-Based Device Configuration screen, you can select a Cloud
Folder to mount as a Cloud-based Device, then click OK.
You can right-click a folder or file to delete. This helps you manage the Arcserve
Backup objects created in the cloud.
Open the Device Manager and select the specific cloud-based device from the
Servers directory tree.
2.
Right-click the cloud-based device and click Format on the pop-up menu or click
Format on the toolbar.
The Format dialog opens.
3.
Assign a New Media Name to the cloud-based device that you want to format.
4.
Click OK.
The Format dialog closes and the following message appears:
"Formatting will erase ALL of your data from the media. Do you want to format the
media?"
5.
Quick Erase--Quick Erase effectively erases the cloud-based device. It avoids the
time a Long Erase would take (minutes to hours) by overwriting the device label.
The history remains available to Arcserve Backup for tracking purposes.
Quick Erase Plus--This option performs the same operation as Quick Erase, and also
erases bar codes and serial numbers. For more information about bar code and
serial number cataloging, see the Mount and Dismount Option.
Note: If the cloud-based device you are erasing does not have a serial number or
bar code, this option functions in the same manner as the Quick Erase option.
If the Quick Erase Plus option is used, it can no longer be tracked by Arcserve
Backup, and information such as the expiration date is no longer carried forward.
Open the Device Manager and select the specific cloud-based device from the
Servers directory tree.
2.
Right-click the cloud-based device and click Erase on the pop-up menu or click Erase
on the toolbar.
The Erase dialog opens.
3.
Open the Device Manager and browse to the server connected to the library
containing the cloud-based device that you want to status as online or offline.
2.
Expand the library, right-click the cloud-based device, and select Online or Offline
from the pop-up menu.
The status changes to offline or online.
Note: Offline state appears disabled, when selected.
Open the Device Manager and select the specific cloud-based device from the
Servers directory tree.
If the device supports compression, then Arcserve Backup enables the Compression
toolbar button. To verify if the device supports compression, select the Detail tab
when the device is highlighted.
2.
Right-click the cloud-based device and click Compression on the pop-up menu or
click Compression on the toolbar.
3.
Click OK to set the Compression Mode to Off (if it is On) or On (if compression is
Off).
2.
3.
Click the Staging Location tab and expand the Staging Servers object.
a.
Browse to and select the group you want to choose as the staging group for
this backup job.
Note: Cloud group cannot be selected as a staging group.
4.
b.
c.
Specify the staging policies for full, differential, and incremental backups
required for your job.
Browse to and select the cloud group you wish to use as the final destination
for this backup job.
Note: For information about creating cloud-based devices, see Create
Cloud-Based Devices (see page 480).
b.
c.
Specify the cloud purge policy for backups required for the job.
d.
Click OK.
5.
Click the Schedule tab and specify the schedule that you want to use for the backup
job.
6.
7.
Specify the global options that you want to apply to the job and then click OK.
Note: For more information about Global Options, see Global Backup Options (see
page 154).
8.
9.
Complete the required fields on the Submit job dialog and then click OK.
The job is submitted.
2.
3.
Specify the value of the chunk size that you require (in bytes).
Examples:
5 MB = 5242880 bytes
25 MB = 26214400 bytes
4.
The Job Engine--This engine processes your jobs at their designated date and time.
It scans the job queue for a job that is ready to run, then sends it to the appropriate
handler.
The Tape Engine--This engine communicates with, and controls, your storage
devices. The Tape Engine selects the device needed for a job.
Information about jobs processed by Arcserve Backup, such as the job type, the
final result, the start and end time, submitter, and description.
Media used by Arcserve Backup, such as its type, its name, the date it was first
formatted, its expiration date, and the sessions on it.
Files, directories, drives, and machines that Arcserve Backup has backed up or
copied.
You can control these Arcserve Backup engines in the Server Admin. To view
information about an individual engine, open the Server Admin from the Quick Start
menu in the Navigation Bar on the Home Page. From the Arcserve domain directory
tree, select the primary server, member server, or stand-alone where you want to
obtain engine status information.
Important! To manage and configure Arcserve Backup engines, you must be logged in to
Arcserve Backup with the caroot password or a Arcserve Backup Administrator account.
Job Engine--Displays information about the jobs submitted, such as the total
number of jobs and the number of ACTIVE, READY, HOLD, and DONE jobs. It also
shows the queues, which ones are being scanned, and the scanning interval.
Tape Engine--Displays information about jobs using the Tape Engine, such as the
type of job, and who submitted it. It also displays information on media groups.
Depending upon the color, the icons indicate one of the following states:
Stop and Start All Arcserve Backup Services Using Batch Files
There are two methods that you can use to manually stop and start Arcserve Backup
services, such as the Job Engine, the Tape Engine, and the Database Engine.
One method is to open the Server Admin, select the server name from the domain tree,
select the individual service that you want to stop or start, and then click the Stop or
Start toolbar buttons. However, circumstances may arise that require you to stop all
Arcserve Backup services. For example, you need to apply a patch or fix that was
released by Arcserve Support.
The cstop and the cstart commands let you shut down and restart all Arcserve Backup
services sequentially, based upon their dependencies to the other Arcserve Backup
services. This process ensures that there is no loss of data while the services are shutting
down, and that all Arcserve Backup services are running properly when your system
restarts.
To stop or start all Arcserve Backup services using a single command, use the file
cstop.bat or cstart.bat located in the Arcserve Backup home directory.
cstop.bat
When you run cstop.bat, Arcserve Backup stops the services in the following order:
1.
2.
3.
4.
5.
6.
7.
8.
9.
cstart.bat
When you run cstart.bat, Arcserve Backup starts the services in the following order:
1.
2.
3.
Arcserve PortMapper
4.
5.
6.
7.
8.
9.
Arcserve Backup Global Dashboard requires the following services for Central
Primary server configurations:
Arcserve Backup Global Dashboard requires the following services for Branch
Primary server configurations:
When you execute cstop.bat and cstart, Arcserve Backup stops and starts the
services that correspond to the type of primary server that you installed (Central
Primary server or Branch Primary server).
2.
After the command line opens, enter one of the following commands:
Arcserve PortMapper
CASportmap
Note: If stop and restart the CA Remote Procedure Call service (CASportmap)
using the Command Line (or the Computer Management console), the service
cannot communicate with its port assignments properly. This can prevent a
user account with caroot equivalence from logging in to the Arcserve Backup
domain. To remedy the inability to log in to the Arcserve Backup domain, run
the cstop command and then run the cstart command. This enables the service
to communicate properly and lets the user account with caroot equivalence log
in to the Arcserve Backup domain.
Note: Repeat this step to start and stop each Arcserve Backup service.
Stop and Start Arcserve Backup Services Using the Server Admin
Using the Server Admin, you can stop and start individual Arcserve Backup services that
are running on a primary, stand-alone, and member server.
Use this method when you need to stop one or two Arcserve Backup services for a short
time. For example, you need to stop and start the Tape Engine on the primary server so
that it can detect a newly installed library.
When you need to stop and start all Arcserve Backup services, you should use the cstop
and cstart batch files. These batch files let you stop and start all Arcserve Backup
services sequentially, based on their dependencies to other Arcserve Backup services.
For more information, see Stop and Start All Arcserve Backup Services Using Batch Files
(see page 493).
Be aware of the following behavior regarding stopping all Arcserve Backup services:
If you use the Server Admin to stop all services, the service status displays as
unknown.
The Stop all Services option lets you stop all Arcserve Backup services except the
Arcserve Service Controller service. Arcserve Backup behaves in this manner
because the Arcserve Service Controller service controls the starting of Arcserve
Backup services.
To stop and start Arcserve Backup services using the Server Admin
1.
From the Quick Start menu in the Navigation Bar on the Home Page, click Server
Admin.
The Server Admin opens.
2.
Expand the domain directory tree and select the server where you want to stop or
start Arcserve Backup services.
The Name, Status, Up Time, and Description of the Arcserve Backup services display
in the Server Admin window.
3.
4.
5.
(Optional) To stop all Arcserve Backup services running on all Arcserve Backup
servers in a domain, right-click the domain and click Stop all services in domain on
the pop-up menu. To restart all services on all servers in a domain, right-click the
domain and click Start all services in domain on the pop-up menu.
Open the Arcserve Backup Server Admin by clicking Server Admin in the Quick Start
menu.
The Server Admin window opens.
2.
3.
Select the desired engine tab and specify the settings that suit your needs.
More information:
Alert Configuration (see page 518)
Job Engine Configuration (see page 500)
Tape Engine Configuration (see page 503)
Database Engine Configuration (see page 514)
Job Queue Scanning Interval (seconds)--The Job Engine constantly scans the job
queue for jobs that should execute. By default, the job queue is scanned every 10
seconds. To change the time interval, specify a number from 1 through 9999.
Retention Time for DONE Job (hours)--Jobs with a final status of DONE remain in
the job queue for the time specified in this field. By default, Arcserve Backup keeps
DONE jobs for 24 hours before they are deleted from the queue. To change the
time, specify a number from 0 through 999.
Note: Single occurrence staging jobs (disk to disk to tape and disk to tape to tape)
will be removed from the job queue after the migration phase of the job is
complete and the length of time specified for this option has elapsed.
Database Polling Interval (minutes)--The Job Engine periodically polls the Arcserve
Backup database to discover copied and purged sessions on staging enabled
devices. The value specified in this field determines the time interval between polls.
The default value for this field is five (5) minutes, and the minimum value is one (1)
minute.
Message Type in Activity Log--The Activity Log contains information about all
Arcserve Backup activities. By default, notes, warnings, and errors that occur when
running Arcserve Backup appear in its Activity Log. To change the types of
messages, specify one of the following values:
None
No messages appear.
Errors
Only errors that occur while running Arcserve Backup appear.
Warnings & Errors
Warnings and errors that occur while running Arcserve Backup appear.
Notes, Warnings & Errors (default)
Includes all notes, warnings, and errors that occur while running Arcserve
Backup.
Debug
Includes debugging information and all notes, warnings, and errors that occur
while running Arcserve Backup.
Network Shares--By default, Arcserve Backup opens Use All Shares in the Browser.
This means that both Default Shares and User Shares are available for selection as
either your source or destination for a job. To change the type of shares that are
displayed in the Browser, specify one of the following:
Use Default Shares Only
Only administrative shares are available.
Use Users Shares Only
Only shares that have been specifically set by users are displayed.
Submit Makeup Jobs on HOLD--Use this option to place a hold status on a job
rather than a ready status.
Block pop-ups when data migration jobs finish--When a staging migration job is
finished, pop-up messages display to inform you if a job was successful, failed, and
so on. Specify this option when you do not want pop-up messages to appear after
the migration job is finished.
Block pop-ups when any job finishes--When a job is finished, pop-up messages
display to inform you if a job was successful, failed, and so on. Specify this option if
you do not want pop-up messages to appear after a job is finished.
Enable archive CSV file--Specify this option to create a CSV file for the archived
files. By default, this option is disabled.
Archive CSV file folder--This field lets you specify the folder where you want to
store the Archive CSV file. By default, Arcserve Backup stores the archive CSV files in
BAB_HOME\Archived files.
Be aware of the following:
The Archive CSV file folder field is enabled only if the Enable archive CSV file
option is specified.
The folder that you specify must reside on the Arcserve Backup server.
Arcserve Backup includes the CSV file folder with the Arcserve Backup database
protection job.
Arcserve Backup backs up the CSV file folder in any backup job that includes
the Arcserve Backup Catalog Database when specified as a global backup
option. For more information, see Backup Manager Operation Options (see
page 167).
More information:
Job Status Types (see page 325)
Level--If you keep the default (Summary), you do not need to specify any other
options. The available values are:
None--No information is logged. Tape Engine logging is halted and the Tape
Engine Log does not appear in the Job Status Manager.
Summary--(default) Logs critical messages and reduces the size of the tape log
by excluding unnecessary information. For this option, the Tape.log is present
in the Job Status Manager. The Tape.log file, by default, is generated and
stored in the Arcserve Backup\Log folder. If the log path needs to be changed,
you can do so by creating an alternate log path entry in the registry file. For
more information on creating an alternate log path entry, see Alternate Path to
the Tape Engine Log (see page 509).
Detail--This option logs all commands sent to the attached backup devices by
Arcserve Backup. Reads/Writes and Test Unit Ready commands are excluded.
Tape Engine specific information, which may be used by Arcserve Support to
help troubleshoot backup and restore issues, is also logged. The Tape.log file,
by default, is generated and stored in the Arcserve Backup\Log folder. If the log
path needs to be changed, you can do so by creating an alternate log path
entry in the registry file.
The Tape.log file for this option can be viewed in the Job Status Manager by
accessing the Tape Log tab.
Both Screen and File--The messages are recorded in the Tape Engine Log as
well as to a DOS box (the Tape Engine Message window).
Screen Only--The messages are sent to the Tape Engine Message window only.
File Only--(default) The messages are recorded in the Tape Engine log only. You
can view the Tape Engine log in the Job Status Manager.
Important! If you select either option, Both Screen and File or Screen Only, you
must configure the Arcserve Tape Engine service such that it can interact with your
desktop and display the contents of the tape log in a DOS window. For more
information, refer to the section Enable Interaction with the Desktop (see
page 512).
From the Arcserve Backup Manager interface, select Server Admin from the Quick
Start Menu in the Navigation Bar on the Home Page.
The Server Admin window opens.
2.
From the Domain/Server directory tree, select the server that you want to
configure.
Click the Configuration toolbar button.
The Configuration - Server Name dialog opens.
3.
Limit log size by--Check the Limit log size by check box to enable Circular
Logging. In the Limit Log Size By field enter the value that you want to specify
as the maximum total size of all chunked TAPE.LOG files.
The Limit log size by value divided by the Maximum log file count value
represents the maximum size of all chunked log files. For example, if you
specify a Limit log size by value of 100 MB and a Maximum log file count of 10,
Arcserve Backup chunks TAPE.LOG when it reaches 10 MB (100/10 = 10).
The default value for the limit log size by option is 100 MB, and the range is
between 1 and 2000 MB.
To disable Circular Logging, clear the limit log size by check box.
Prune logs older than--Use this option to specify the number of days that must
elapse before Arcserve Backup prunes the log files.
The default value for the Prune logs older than option is 100 days, and the
range is between 1 and 365 days.
Log file split criterion--The options in this section define the behavior of how
Arcserve Backup splits the log files.
Maximum single log file size--This option works in conjunction with the
Prune logs older than option. When you specify the Maximum single log
file size and Prune logs older than options, Arcserve Backup switches to
Circular Logging mechanisms when the TAPE.LOG reaches its maximum
size, and deletes chunked log files when their age is greater than the value
specified under the Prune logs older than option.
The default value for the Maximum single log file size option is 10000 KB,
and the range is between 1 and 100000 KB.
Note: You can modify this setting only if the Prune logs older than option is
specified.
4.
Use Global Scratch Set--Lets Arcserve Backup use a Global Scratch Set. This option
is enabled by default.
The Global Scratch Set treats all of the scratch tapes in all media pools as one large
Scratch Set. This helps ensure that backup jobs do not fail when a scratch tape is
not available in its own media pool.
When this option is enabled, the Media Pool Manager shows only the Save Set for
each pool (not the Scratch Set), but adds an object named GlobalScratchSet. This
object contains all of the media available in the scratch sets of all your media pools.
If you right-click GlobalScratchSet and select Assign Media, you can move media
from an unassigned set to the Scratch Set.
When you select a media in the Global Scratch Set, two extra properties appear as
column headings on the top right-hand pane and on the Properties tab in the lower
right hand pane: Medium Type and Media Pool. If you click a column heading on
the top right-hand pane, you can sort the list by that column. If the media you
select in the Global Scratch Set is vaulted, it appears in a different color to indicate
that it is inactive.
Note: If you enable the Global Scratch Set and submit a backup job using a specific
media pool, Arcserve Backup first attempts to find media in that media pool's
Scratch Set. If no media is available, the Global Scratch Set media will be used. Also,
if you specify a media pool and submit a backup job that spans tapes, media in the
Global Scratch Set can be used.
Show Tape Log on Job Status Manager--Lets you view the Tape Log in the Job
Status Manager. If the Activity Log is open when you enable this option, you must
click Refresh to update the manager.
Note: This option is available only on Windows computers.
Use TapeAlert--Lets Arcserve Backup detect and report TapeAlert flags asserted by
your tape drives and libraries. If you do not want to receive TapeAlert-related
messages, disable this option.
With this option enabled, Arcserve Backup queries all devices connected to
Arcserve Backup for TapeAlert flags in one minute intervals. If Arcserve Backup
detects a TapeAlert flag, it reports real-time details about the flag in the
Activity Log and the Tape.log file.
With this option disabled, Arcserve Backup does not maintain a separate
thread-querying mechanism for detecting and reporting TapeAlert flags. As a
result, Arcserve Backup will not query for TapeAlert flags until the job is
running and a SCSI error occurs. If Arcserve Backup detects a TapeAlert flag
while the job is running, it reports the details about the flag in the Activity Log
and the Tape.log file.
Enable Message Logging into Event Log--By default, all messages are written only
into the Arcserve Backup Activity Log. If you check this box, the following groups of
check boxes become enabled:
Exclude Message Type From Logging Check Boxes--Use these check boxes to select
which type of message should be excluded from the Event Log.
Exclude Message Logging From Check Boxes--Use these check boxes to exclude all
messages from a particular Arcserve Backup module.
900--Audit events
The diagram that follows displays Arcserve Backup events in Windows Event Viewer.
More information:
Event Log Configuration (Windows Servers) (see page 508)
Set the value to the local drive path you want to use as the new log file location (for
example, D:\temp\log). After the log path is established, you can enable it by either
restarting the Tape Engine or changing one of the logging options described earlier. To
change the tape log path back to the default, you can remove the LogPath value and
restart the Tape Engine.
Note: Alternate paths can only be local drives as mapped drives are not supported for
redirecting the log.
Circular Logging
Circular Logging is a process that lets you control the size and behavior of the Tape
Engine log file. Using this feature, you can set a size limit that directs Arcserve Backup to
chunk the log file into smaller log files when a user-specified size limit is exceeded.
Additionally, you can specify a retention period, total count, or both for log files. After
the retention period elapses, Arcserve Backup deletes the chunked log files.
The Tape Engine log file is labeled TAPE.LOG. It can be found in the CA\ARCserve
Backup\LOG directory.
To configure and use Circular Logging, start the Server Admin from the Quick Start menu
on the Arcserve Backup Home Page. For more information see Specify Circular Logging
Settings (see page 511).
where #### represents the sequential log number created on a given day.
Example: Log File Names
For example, on a given day, the Tape Engine generates three log files based upon a file
size limit of 100 MB. The log file names are as follows:
TAPE.LOG
TAPE.LOG.0001
TAPE.LOG.0002
1.
2.
If TAPE.LOG reaches a specified value for the second time, Arcserve Backup
renames TAPE.LOG.0001 to TAPE.LOG.0002, renames TAPE.LOG to TAPE.LOG.0001,
and creates a new TAPE.LOG file.
3.
If TAPE.LOG reaches a specified value for the third time, Arcserve Backup renames
TAPE.LOG.0002 to TAPE.LOG.0003, renames TAPE.LOG.0001 to TAPE.LOG.0002,
renames TAPE.LOG to TAPE.LOG.0001, and creates a new TAPE.LOG file.
This process continues in a cyclical manner. Arcserve Backup always retains the latest
three log files.
Important! Arcserve Backup calculates the value in which a new log file is created based
upon the amounts that you specify in the Limit Log Size By and Log File Count options.
For example, if you specify a Log Limit Size By amount of 500 MB and a Log File Count of
10, Arcserve Backup creates a new log file when the current log size exceeds (500
divided by 10) 50 MB.
From the Arcserve Backup Home Page, click the Quick Start menu and select Server
Admin.
The Arcserve Backup Server Admin dialog opens.
2.
3.
4.
To enable Circular logging, click the Limit Log Size By option in the Limit Log Size
section of this dialog, and then specify then maximum size in MB. This amount
represents the maximum size of all log files.
5.
In the Log File Count field, select the number of log files that you want Arcserve
Backup to retain. This amount represents the maximum number of TAPE.LOG files
that Arcserve Backup will retain.
6.
2.
Click the Prune Logs Older Than option and specify the number of days that you
want to elapse before Arcserve Backup prunes log files.
3.
(Optional) In the Single Log File Size field, enter a size in KB to specify a size limit for
a single log file. If you do not specify a value in the Single Log File Size field, Arcserve
Backup uses the default value, 10000 KB, as the size limitation for each single log
file.
4.
Important! If you enable both Limit Log Size options (Limit Log Size By and Prune Logs
Older Than), Arcserve Backup prunes log files if either the total number of log files
exceeds the Log File Count, or the date of the log files exceeds the number of days
specified under the Prune Log Files Older Than option. You cannot specify a Single Log
File SizeArcserve Backup uses the formula Total Log Size divided by Log File Count to
calculate the Log File Size setting.
From the Windows Start menu, select Programs (or All Programs), Administrative
Tools, and select Component Services.
The Component Services dialog opens.
2.
3.
4.
5.
High quantities of backup jobs that use deduplication, that may or may not run
simultaneously.
Diminished Tape Engine performance can occur due to the amount of virtual memory
that is allocated to applications by the operating system. By default, Windows 32-bit
operating systems allocate 2 GB of virtual memory for applications. The default
allocation on 32-bit operating systems can prevent computers that contain 3 or more
GB RAM from utilizing all of the RAM that is installed on the computer.
Note: Windows 64-bit operating systems can allocate up to 4 GB of virtual memory.
Windows operating systems let you increase the amount of virtual memory allocated for
applications. If your backup server demonstrates slow performance in a large backup
environment, you can increase the amount of virtual memory available to applications
to improve the performance of the Tape Engine.
Note: You should increase virtual memory only of your backup server contains a
Windows 32-bit operating system with at least 2.5 GB RAM.
The following sections describe how to increase virtual memory allocation on computers
running 32-bit versions of Windows Server 2003 and Windows Server 2008.
To increase virtual memory allocation on 32-bit Windows Server 2003 systems
1.
From the desktop, right-click My Computer and select Properties on the pop-up
menu.
The System Properties dialog opens.
2.
3.
4.
In the System startup area on the Startup and Recovery dialog, click Edit
The Windows boot.ini file opens in Notepad.
5.
Add /3GB to the end of the startup string below [Operating Systems], as illustrated
by the following:
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise"
/noexecute=optout /fastdetect switch: /3GB
6.
Close Notepad.
When Notepad prompts you to save your changes, click Yes.
7.
2.
3.
Files and directories that have been backed up, copied, and restored.
Run Pruning at--This field is active only if the Enable Database Pruning option is
on. Specify when you want the pruning operation to run.
Default value: If enabled, will occur at 12:00 p.m.
Prune database job records older than--This field is active only when the
Enable auto pruning option is specified. This option lets you specify how long
job records should be retained in the database before Arcserve Backup prunes
them.
Default value: If pruning is enabled, 180 days.
Range: 1 to 999 days.
Prune other database records older than--This field is active only when the
Enable auto pruning option is specified. This option lets you specify how long
other records (for example, session detail records) should be kept in the
database before Arcserve Backup prunes them.
Default value: If pruning is enabled, 30 days.
Range: 1 to 999 days.
Prune activity logs older than--Specify how long activity logs should be kept in the
database before Arcserve Backup prunes them.
Default value: 14 days
Range: 1 to 999 days.
Prune catalog files older than--Specify how long catalog files should be kept in the
database before Arcserve Backup prunes them.
Default value: 60 days.
Range: 1 to 9999 days.
Update statistics--This option lets Arcserve Backup update table and index
statistics. With correct and up-to-date statistical information, SQL Server and
SQL Server 2008 Express can determine the best execution plan for queries,
which improves query performance.
You should update the statistics on a daily basis.
Reduce DB size--This option lets Arcserve Backup reclaim disk space on your
system by reducing the size of the data files in the Arcserve database.
You should reduce the size of the database on an as-needed basis.
Submit Prune Job--Select this option to submit the pruning job now.
Submit Arcserve DB protection job--This option lets you recreate the Arcserve
Backup Database Protection Job because the original job was deleted. For more
information, see Recreate the Arcserve Backup Database Protection Job (see
page 625).
Catalog Database
Catalog database folder--This option let you specify the location of the
Arcserve Backup catalog database folder. Click the ellipsis button to browse
and select a different location for the catalog database folder.
By default, the catalog database folder will be located on the Primary Server at:
C:\Program Files\CA\ARCserve Backup\CATALOG.DB\
Minimum disk free space threshold--This option lets you specify the minimum
percentage of free disk space when Arcserve Backup deletes catalog files.
Default value: 10 %
Range: 1% to 99%
Note: Arcserve Backup periodically checks the free disk space percentage on
the volume where the catalog database folder is located. If the detected free
space is lower than the specified percentage, a warning message will be sent to
the activity log and it would automatically begin to delete catalog database files
(minimum of 7 days old and starting with the oldest first) from the disk until
the detected free space percentage is greater than the threshold setting.
Example: If the detected free space is lower than the 10%, a warning message
is sent to the activity log and it would automatically begin to delete catalog
database files (minimum of 7 days old and starting with the oldest first) from
the disk until the detected free space percentage is greater than 10%.
More information:
How the Catalog Database Works (see page 650)
How to Protect the Arcserve Backup Database (see page 607)
Alert Configuration
Alert is a notification system that sends messages to people in your organization using
various methods of communication. Alert does not generate its own messages. You
must tell Alert what information you want to communicate and where you want to send
it.
If you configure Alert from Server Admin, you can generate notifications for non-job
related events, such as starting or stopping the Tape Engine. To do this, enter the words
or phrases you want to communicate in exactly the same format as they appear in the
Activity Log and click Add.
Or, if you want to send all activity log messages, enter an asterisk and click Add. Alert
generates notification messages and sends them to the appropriate recipients. For
information on selecting recipients and configuring methods to transmit Alert
notifications, see Using the Alert Manager."
2.
To receive an Alert notification when the Tape Engine starts, enter engine in
the Alert list to have Alert detect the event. However, the Alert engine then
sends notifications for any events that related to engine, such as Database
engine started.
To receive Alert notifications for all activity log messages, enter '*'.
To receive Alert notifications for Audit log events, enter the following in the
Alert list field:
Note: The keywords for Audit Log events are case-sensitive and square
brackets are required.
3.
4.
Click OK.
When the text of an event matches one of the keywords you have entered, the
Alert engine generates Alert notifications for all recipients previously configured
using the Alert Manager.
2.
3.
From the Arcserve Backup Home Page, open the Server Admin by selecting Server
Admin from the Quick Start menu.
The Arcserve Backup Server Admin window opens.
2.
Select Arcserve Backup System Account from the Server Admin menu.
The Arcserve Backup System Account dialog opens.
3.
4.
Server
User Name
Password
Domain
Click OK.
Note: If you are using a remote deployment of Microsoft SQL Server to host the
Arcserve Backup database, and the login credentials for the Arcserve Backup system
account (User Name and Password) are identical to the login credentials for the
remote SQL Server account, a message appears to notify you that modifying the
login credentials for the system account also modifies the login credentials for the
remote SQL Server account. If you are sure that you want to modify the login
credentials for the remote SQL Server account, click OK.
The login credentials for the Arcserve Backup system account are modified.
Open the Arcserve Backup Server Admin by clicking Server Admin on the Quick Start
menu on the Home Page.
The Server Admin window opens.
2.
Expand the domain directory tree and select a server that you want to view or
reconfigure the node tier assignments.
3.
Select the Node Tier Configuration option from the Admin menu.
The Node Tier Configuration dialog opens, displaying the nodes assigned to each
Tier category (High Priority, Medium Priority, Low Priority).
4.
Select one or more nodes that you want to reassign to a different tier category and
click on the corresponding arrow icon to move the selected nodes from one tier to
another.
Note: Multiple nodes can be selected for tier assignment by using the "CTRL" or
"SHIFT" key combinations.
5.
Click the single arrow icon to move only the selected nodes.
Click the double arrow icon to move all the node in the tier.
Identify the total number of licenses applied and the number of active licenses for
each component in a Arcserve Backup domain.
View the names of the servers using the component licenses in a Arcserve Backup
domain.
Release licenses from servers to make the licenses available to other servers in your
domain.
Note: For information about releasing licenses from servers, see Release Licenses
from Servers (see page 525).
From the Arcserve Backup Manager Console, open the Server Admin by clicking
Server Admin in the Quick Start menu.
The Server Admin opens.
The Arcserve Backup primary server and its member servers display in a directory
tree structure as illustrated by the following:
2.
To view the Arcserve Backup products installed on a primary server and a member
server, select the server in the directory tree.
The components and licenses for the selected server display in the properties view,
as illustrated by the following:
3.
Active Licenses--Specifies the number licenses that are currently active for the
selected component. The total includes purchased licenses and trial licenses.
Available Licenses--Specifies the number of licenses available for use for the
selected component. The total includes only purchased licenses.
You are using one purchased license and one trial license for a component.
Arcserve Backup recommends purchasing one license to replace the trial
license so that you have uninterrupted use of selected component.
You are protecting six Windows computers using the Client Agent for
Windows. You purchased four Client Agent for Windows licenses. In the
past, backups may have failed due to an insufficient number licenses.
Arcserve Backup recommends purchasing two additional licenses to help
ensure that you have uninterrupted use of the Client Agent for Windows.
The following dialog illustrates that there are 10 active licenses and zero
available licenses for the Tape Library Option. The host names of the
computers using the Tape Library Option licenses display in the Licensed
machines field.
More information:
Central License Management (see page 53)
From the Arcserve Backup Manager Console, open the Server Admin by clicking
Server Admin in the Quick Start menu.
The Server Admin opens.
2.
From the server directory tree, right-click the primary server and select Manage
Licenses from the pop-up menu.
The License Management dialog opens.
3.
From the License status section, select the component containing the license that
you want to release.
The machines using the license display in the Licensed machines field.
4.
Clear the check box next to the machine name with the license that you want to
release and click Apply.
The active license is released from the selected server. The license is now available
to other servers running the Arcserve Backup product in your Arcserve domain.
Note: After you click the Apply button, the selected machine no longer appears in
the Licensed machines field.
From the Arcserve Backup Home Page, open the Server Admin by selecting Server
Admin from the Quick Start menu.
The Arcserve Backup Server Admin window opens.
2.
3.
4.
Use selected network card--Lets you specify the network interface cards that
you want to use from the list. When configured in this manner, any job that
Arcserve Backup executes defaults to the first network interface card. When
you are using multistreaming, and more than one process is created, each
subsequent process will use the next configured network interface card.
Click OK.
The network card settings are applied.
Component
Description
_HTMSETUP.EXE
Component
Description
<CD_ROOT>\IntelNT\Exchange.DBA\SETUP.EXE
IntelNT\Exchange.DBA\Exchange.DBA\SETUP.EXE--Inst
alls the Agent for Microsoft Exchange Server for
database level backups.
IntelNT\Exchange.DBA\ExchangeD.DBA\SETUP.EXE--Ins
talls the Agent for Microsoft Exchange Server for
document level backups.
<CD_ROOT>\IntelNT\EO\SETUP.EXE
<CD_ROOT>\SETUP.EXE
AGENTDEPLOY.EXE
AGIFPROB.EXE
AGPKIMON.EXE
ALADMIN.EXE
ARCSERVECFG.EXE
ASDBInst.exe
ASRECOVERDB.EXE
ASREMSVC.EXE
AUTHSETUP.EXE
BABHA.EXE
BACKINT.EXE
Backup integration module for the Agent for SAP R/3 for
Oracle.
BACKINTCONFIG.EXE
Configuration utility for the Agent for SAP R/3 for Oracle.
BCONFIG.EXE
Component
Description
BDELOBJ.EXE
BDELOBJ_BAB.EXE
BRANCHCFG.EXE
BRANCHSERVICE.EXE
CadRestore.exe
CALICESE.EXE
CALicnse.exe
CARUNJOB.EXE
CENTRALSERVICE.EXE
CHGTEST.EXE
Component
Description
DBACONFIG.EXE
DELETEME.EXE
DEPLOYDUMMY.EXE
DSCONFIG.EXE
dosboot.exe
EMCONFIG.EXE
ETPKI_SETUP.EXE
HDVSSCOM.exe
jucheck.exe
LandingPage.exe
LICCHECK.EXE
Lets the Arcserve Backup Agent for Lotus Domino and the
Arcserve Backup Agent for Informix verify the status of their
licenses.
MASTERSETUP.EXE
Component
Description
MASTERSETUP_MAIN.EXE
MEDIASVR.EXE
MergeIngres2Sql.exe
ORAUPGRADE.EXE
qphmbavs.exe
RAIDTEST.EXE
rdbgsetup.exe
RMLIC.EXE
SDOInst.exe
SETUP.EXE
Installation Wizard.
setup100.exe
SETUPFW.EXE
SETUPSQL.EXE
SETUPSQL_EXP.EXE
SILENT.EXE
SIMULATE.EXE
Component
Description
SMPLEMON.EXE
SPS012UPGRADE.EXE
SPADMIN.EXE
SQLAGENTRMTINST.EXE
SQLCONFIG.EXE
SQLdiag.exe
SqlWtsn.exe
TAPEENG.EXE
TAPETEST.EXE
Uninstall.exe
UNINSTALLER.EXE
UPDATECFG.EXE
UPDATECFG.EXE
Component
Description
ACSCFG.EXE
ADMIN.EXE
Component
Description
adrasr.exe
AdrLogViewer.exe
adrmain.exe
adrstart.exe
AgPkiMon.exe
ALERT.EXE
ARCSERVEMGR.EXE
ASWANSYNC.EXE
ATLCFG.EXE
BAOFCONFIGMIGRATION.EXE
BDAEMON2.EXE
CA_AUTH.EXE
CA_BACKUP.EXE
CA_DBMGR.EXE
CA_DEVMGR.EXE
CA_JOBSECMGR.EXE
CA_LOG.EXE
CA_MERGE.EXE
ca_msvmpopulatedb.exe
CA_QMGR.EXE
ca_recoverdb.exe
CA_RESTORE.EXE
CA_SCAN.EXE
CAADVREPORTS.EXE
Component
Description
CAAGSTART.EXE
CAAUTHD.EXE
Authentication service.
CACLURST.EXE
caclurst utility.
CADIAGINFO.EXE
CADIAGSUPPORT.EXE
CADIAGWIZ.EXE
CADISCOVD.EXE
CADVWIZ.EXE
CADVWIZE.EXE
CALICNSE.EXE
CAMINFO.EXE
CAREPORTS.EXE
CASDSCSVC.EXE
Discovery Service.
CASERVED.EXE
Service Controller.
CASISCHK.EXE
CATIRPC.EXE
Arcserve Portmapper.
CAVER.EXE
CDBMERGELOG.EXE
Component
Description
CONFIGBAF.EXE
CONFIGENCR.EXE
CSTMSGBOX.EXE
DBACFG.EXE
DBENG.EXE
DBTOSQL.EXE
DBTOSQL_EXP.EXE
drcreate.exe
DUMPDB.EXE
DVCONFIG.EXE
ELOConfig.exe
ERRBOX.EXE
EXPTOSQL.EXE
GROUPCONFIG.EXE
IMPORTNODEINFO.EXE
INSTALLALERT.EXE
JOBENG.EXE
JOBWINDOW.EXE
JOBWINUTIL.EXE
Job window.
Component
Description
JOBWIZARD.EXE
LDBSERVER.EXE
LIC98LOG.EXE
A license service.
LIC98SERVICE.EXE
A license service.
LIC98VERSION.EXE
A license service.
LICDEBUG.EXE
LICRCMD.EXE
LOGWATNT.EXE
LQSERVER.EXE
MERGECALIC.EXE
MERGECAT.EXE
MERGEOLF.EXE
MERGEROLF.EXE
MMOADMIN.EXE
MSGENG.EXE
Ofant.exe
ofawin.exe
PFC.EXE
RMANCFG.EXE
SERVERMIGRATION.EXE
ServerMigrationDR.exe
SETMANPC.EXE
SETUPRD.EXE
SETUPSQL.EXE
Component
Description
SQLCLEAN.EXE
SQLCLEAN_EXP.EXE
SQLTOSQL.EXE
TAPECOMP.EXE
TAPECOPY.EXE
UNIVAGENT.EXE
UPGRADEUTIL.EXE
vmdbupd.exe
VSERVICE.EXE
W95AGENT.EXE
Manage Domain Users and Groups Using the ca_auth Command Line Utility
To manage the domain user and groups, Arcserve Backup provides a command line
utility called ca_auth.
For more information about domain user management, type ca_auth under the
command prompt, or see Command Line Reference Guide.
The first time that you open the Job Status Manager, the domain directory tree displays
the Arcserve Backup domain that you are currently logged in to, as illustrated by the
following screen.
At any other time, you can Add and Delete domains from the Job Status Manager.
After you add domains to the Job Status Manager, you can perform the following tasks:
Manage job status--Modify job status, such as Ready, Hold, Run now, Stop Job, and
refresh the data for the jobs.
Manage job protection--Modify the user name for the job and the encryption
password for the job.
Manage job maintenance--Modify job schedules, add jobs, delete jobs, preflight
check jobs, Quick search jobs, generate logs, and print information about jobs.
The capability to perform these tasks is limited by the role assigned to account for the
specified domain.
Example: Role Assignment
The current Arcserve Backup domain is DomainA. The user "Arcserve User" adds two
Arcserve Backup domains: DomainB and DomainC. The roles for each domain are as
follows:
Arcserve User can perform the following tasks in each Arcserve Backup domain:
2.
Right-click Arcserve Backup Domains and select Add Domain from the pop-up
menu.
The Default Server Information dialog opens.
3.
From the Arcserve Backup Primary Server drop-down, select the Arcserve Backup
domain that you want to add.
Complete the following:
4.
Click OK.
The Arcserve Backup domain specified appears in the Job Status Manager below
Arcserve Backup domains.
2.
From the domain directory tree expand Arcserve Backup Domains and locate the
domain that you want to delete.
Right-click the Domain and click Delete Domain on the pop-up menu.
The Arcserve Backup domain is deleted from the Job Status Manager.
The computer name of the primary server in an Arcserve domain was changed.
To ensure that the primary server and the member servers can communicate, see
Change the Computer Name of the Primary Server on the Primary Server (see
page 543), and Change the Computer Name of the Primary Server on a Member
Server (see page 548).
The computer name of a server that is running the Manager Console was changed.
To ensure that a server that is running the Manager Console can communicate in an
Arcserve domain, see Change the Computer Name on a Server that is Running the
Manager Console (see page 553).
More information:
Discovery.cfg Configuration File (see page 549)
Change the Computer Name of the Primary Server on the Primary Server
The following procedure helps ensure that the primary server and member servers in an
Arcserve domain can communicate after you change the computer name of the primary
server.
You must change the computer name of the primary server before you complete these
steps.
Note: You can use this procedure when you change the computer name of a
stand-alone server.
If you are using only Microsoft SQL Server 2008 Express for Arcserve Backup without any
other SQL instance installed, you may also need to:
Install Microsoft SQL Server Management Studio Express (SSMSE) onto this
machine, if it is not already installed. SSMSE is a graphical tool for managing SQL
Server 2008 Express Edition, and for managing instances of the SQL Server Database
Engine created by any edition of SQL Server 2005. For more information, see
Microsoft SQL Server Management Studio Express on the Microsoft Download
Center website.
Be familiar with the sqlcmd utility, which is used to enter Transact-SQL statements,
system procedures, and script files at the command prompt. For more information,
see sqlcmd Utility on the Microsoft Developer Network website.
For more information about renaming systems hosting Microsoft SQL Server databases,
see the following topics on the Microsoft Developer Network website:
How to Rename a Computer that Hosts a Stand-Alone Instance of SQL Server 2005
Renaming a Server
Restart the target system to complete the Windows computer name change
process.
2.
3.
Open the Windows Command Line and change the directory to the following
directory:
%ARCSERVE_HOME%
In the PRIMARY field, change the name of the primary server as required for your
environment.
Important! Do not modify the Arcserve Domain Name in the discovery.cfg
configuration file. When you change the Arcserve Domain Name in the
discovery.cfg configuration file, the password for the caroot account is deleted. Use
the discovery.cfg configuration file only for the purposes of changing the host name
of the primary server, a member server, and a stand-alone server.
Close the file and save your changes.
For more information, see Discovery.cfg Configuration File (see page 549).
5.
From the Windows Command Line that you opened earlier, execute the following
command to start all Arcserve services:
cstart
From the Windows Start menu, select All Programs, CA, ARCserve Backup, and click
Server Configuration Wizard.
The Server Configuration Wizard opens and the Select Options dialog appears.
7.
From the Select Options dialog, click the Select Database option, and click Next.
The Check caroot dialog opens.
8.
Click Next.
Important! You must specify the caroot password to complete this task.
The System Account dialog opens.
9.
Complete the following fields on the System Account dialog and click Next.
User Name--Specify the Windows user name required to log in to the primary
server.
Domain--Specify the Windows domain name or host name of the new primary
server.
Password--Specify the password for the Windows user name required to log in
to the primary server.
10. From the Select Database Options dialog, complete the fields and follow the
prompts, as required, for your current database installation and click Next.
The subsequent dialogs that open will vary, based on whether you are running
Microsoft SQL Server or Microsoft SQL Server 2008 Express in your current
environment.
Note: For the Select Database option, if the server is a Central Primary Server in a
Global Dashboard domain, and the new selected database is Microsoft SQL Server
Express or Microsoft SQL Server 2000 (which are not supported by a Global
Dashboard Central Primary Server), consider exporting and retaining the Global
Dashboard information prior changing the database. After the Select
Database operation is completed, the Global Dashboard information will be lost
because the server will no longer function as a Central Primary Server. If you want
to retain the grouping configuration and the registered branch information, you
need to export this Global Dashboard information to a temporary location before
performing the Select Database operation. For more information about exporting
and importing Global Dashboard information, see the Dashboard User Guide.
Important! The Server Configuration Wizard prompts you to overwrite the existing
Arcserve_DB instance, and by default, the option is enabled. To retain your previous
data, such as job history, activity logs, and so on, you must clear the checkmark
from the Overwrite the existing "Arcserve_DB" instance option.
11. After the Server Configuration Wizard completes the updates, click Finish.
12. From the Windows Command Line that you opened earlier, execute the following
commands to stop and restart all Arcserve services:
cstop
cstart
All Arcserve services stop and restart. The primary server functions using the new
computer name.
Note: Do not close the Windows Command Line.
13. You must now create equivalence for the caroot user account.
From the Windows Command Line, execute the ca_auth command using the
following syntax:
Note: Do not include angle brackets <> with your arguments.
ca_auth -cahost <new primary server host name> -equiv add <user name> <new primary
server host name> caroot caroot <password>
16. Run the Microsoft SQL Agent Account Configuration utility to update the ODBC
communication settings if any of the following conditions are met:
The server is the primary server with a locally installed Arcserve Backup
database,
The server is the primary server, a standalone server, or a member server AND
Arcserve Backup database or the Agent for Microsoft SQL Server is installed on
the same machine.
To start the Microsoft SQL Agent Account Configuration utility, click Start on the
Windows Taskbar, choose All Programs, CA, ARCserve Backup, and Microsoft SQL
Agent Account Configuration.
After you start the utility, follow the prompts and accept all settings.
17. Verify the renaming operation.
To verify the renaming operation has successfully completed, select information
from either @@servername or sys.servers. The @@servername function returns
the new name, and sys.servers table shows the new name.
Note: After a computer has been renamed, any connections that used the old
computer name must connect using the new name.
18. Release all Arcserve Backup licenses registered to the former primary server.
Note: For more information, see Release Licenses from Servers (see page 525).
19. Update the Arcserve Backup System account. To do this, open the Arcserve Backup
Manager Console and then open the Server Admin Manager.
Select the Arcserve Backup server and click Arcserve Backup System Account as
illustrated by the following:
Password
Click OK.
21. Open the Job Status Manager and complete the following tasks:
Modify the Database Protection Job and any other backup jobs that are set to
run on the renamed server, to update the Staging and Destination locations.
Note: For more information, see Modify or Create a Custom Database
Protection Job (see page 614).
You must change the computer name of the primary server before you complete
this task.
Note: For more information, see Change the Computer Name of the Primary Server
on the Primary Server (see page 543).
You must complete this task on all member servers in the Arcserve domain.
The Server Configuration Wizard may display the following messages while you are
completing this task:
Arcserve Backup is unable to connect to the original primary server. You can
safely click Continue to clear this message.
Arcserve Backup is unable to unregister the member server. You can safely click
Yes to clear this message.
2.
From the Windows Start menu on the member server, select All Programs, CA,
ARCserve Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
3.
From the Select Options dialog, click Move this server to another Arcserve Backup
domain and click Next.
The Check caroot dialog opens.
4.
Specify the password for the caroot account and click Next.
5.
In the Add to another Arcserve Backup domain dialog, specify the new hostname
for the primary server, specify the password for the caroot account and click Next.
The System Account dialog opens.
6.
User Name--Lets you specify the Windows user name that is required to log in
to the primary server.
Domain--Lets you specify the Windows domain name or host name of the new
primary server.
Password--Lets you specify the password for the Windows user name that is
required to log in to the primary server.
Click Next and follow the on-screen instructions to complete the configuration.
7.
Repeat Steps 1 through 6 for all member servers in the Arcserve domain.
The discovery.cfg configuration file is located in the following directory on the primary
and member servers:
%ARCSERVE_HOME%\config\discovery.cfg
Important! Do not modify the Arcserve Domain Name in the discovery.cfg configuration
file. When you change the Arcserve Domain Name in the discovery.cfg configuration file,
the password for the caroot account is deleted. Use the discovery.cfg configuration file
only for the purposes of changing the host name of the primary server, a member
server, and a stand-alone server.
2.
Open the Windows Command Line and change the directory to the following
directory:
%ARCSERVE_HOME%
Execute the following commands, to stop and start all Arcserve services:
cstop
cstart
From the Windows Start menu, select All Programs, CA, ARCserve Backup, and click
Server Configuration Wizard.
The Server Configuration Wizard opens and the Select Options dialog appears.
4.
Click the Move this server to another Arcserve Backup domain option and click
Next.
The Add to Another Arcserve Backup Domain dialog opens.
5.
On the Add to Another Arcserve Backup Domain dialog, complete the following
fields and click Next.
User Name--Specify the Windows user name required to log in to the member
server.
Domain--Specify the Windows domain name or host name of the new member
server.
Password--Specify the password for the Windows user name required to log in
to the member server.
Click Next.
Note: At this time, a pop-up message may appear to inform you that various
Arcserve Backup services will not start. This is expected behavior that will not
adversely affect this procedure.
7.
Click OK.
The Arcserve Backup Data Migration dialog opens.
8.
9.
12. After the member server name change is complete, the old (invalid) member server
name remains in the Arcserve Backup Manager. To remove the invalid member
server name from the Manager, do the following:
a.
Open the command line window and browse the Arcserve Backup installation
directory.
b.
Note: If your Arcserve Backup implementation contains more that one invalid
member server, repeat this step (b) for each member server.
c.
Log in to the primary server or the server hosting the Arcserve Backup database
to verify the status of the Arcserve Backup database.
(Optional) Open Microsoft SQL Server Management Studio and open to the
Arcserve Backup database instance using Windows authentication.
For example, the path to a Microsoft SQL Server Express Edition database is as
follows:
<server name>\ARCServe_DB
If the above commands did not complete successfully, verify that the server name,
the user name that is logged in to Arcserve Backup, and database name are correct,
and then repeat this step.
13. To verify the changes, open the Manager Console, open the Backup Manager, and
select the Source tab.
Expand the Windows Systems object in the Source directory tree.
The member server, with its new host name, appears under the Windows Systems
object.
More information:
BSBAB--Manage Arcserve Servers Using the Server Configuration Wizard-AdminW (see
page 559)
Change the Computer Name of a Server that is Running the Manager Console
When you change the computer name of a server that is running the Manager Console,
you do not need to process modifications to the primary server, a stand-alone server, a
member server, or the server that is running the Manage Console.
2.
3.
4.
Windows Authentication--Lets you specify a Windows user name that the user
will use to log in to Arcserve Backup.
Password
Confirm Password
Click OK.
The user is added.
2.
Select the user that you want to delete and click Delete on the toolbar.
Click OK to confirm that you want to delete the user profile.
The user is deleted.
2.
Select the user that you want to modify and click Properties on the toolbar.
The User Properties dialog opens.
3.
Password
Confirm Password
Click OK.
The user password is changed.
2.
Select the user that you want to modify and click Properties on the toolbar.
The User Properties dialog opens.
3.
2.
Select the user that you want to modify and click Properties on the toolbar.
The User Properties dialog opens.
3.
Note: To reactivate users, perform the above steps and click Active in the Status field.
Back up the Arcserve Backup primary server or stand-alone server and include the
directory that contains the Arcserve Backup database with the backup.
Back up data and specify the Job Scripts option on the Operations section of the
Global Options dialog.
In all of these methods, the Job Queue is one of the last few objects backed up during
the job. If you used the Database Protection Job, or included the Arcserve Backup
database in the same backup job, the Arcserve Backup database and Job Queue will
reside on the same backup media, and the Job Queue sessions will be between one and
six sessions before the Arcserve Backup database.
In the event the Arcserve Backup Job Queue is damaged or is deleted in error, use the
following steps to restore the Job Queue to the last backup.
To restore the Arcserve Backup Job Queue
1.
Ensure that there are no jobs running on any Arcserve Backup server in the affected
Arcserve Backup domain.
2.
Open the Restore Manager and select Restore by Tree from the methods
drop-down list.
Expand the Windows Systems object and locate the Arcserve Backup server, or the
remote server where the Arcserve Backup database is located.
Expand the Arcserve Backup server, locate and click the Arcserve Backup database.
From Properties on the Restore Manager window, locate and notate the Media
Name, the ID, and the Session Number for the Arcserve Backup database.
3.
From the Session directory tree, locate and expand the Backup Media containing
the Arcserve Backup database backup data.
Locate the session that contains the Arcserve Backup database, and start searching
upward from there. The session path of the Job Queue backup session will end in
00000001.QSD, and the Session Type will be Arcserve Job Queue. Locate the session
that contains the Job Queue backup session, as illustrated below.
Click the check box next to the session containing the Job Queue backup session.
4.
5.
Clear the check mark next to Restore files to their original location, and specify an
alternate location to restore the Job Queue backup session.
Note: The Client Agent for Windows must be installed on the system containing the
alternate location and the alternate location must be an empty directory (For
example, C:\Temp). The best practice is to specify directory on the Arcserve Backup
primary or stand-alone server.
Submit the job.
6.
7.
After the restore job is complete, open the Server Admin and stop all Arcserve
Backup services by doing the following:
a.
b.
Right-click the Arcserve Backup server and select Stop All Services from the
pop-up menu.
Browse to directory where you restored the Job Queue backup session.
Copy all Job Queue files under the folder that you restored to the following
directory:
ARCSERVE_HOME\00000001.qsd
9.
Open the Server Admin and restart all Arcserve Backup services by doing the
following:
a.
b.
Right-click the Arcserve Backup up server and select Start All Services from the
pop-up menu.
Manage the roles of the servers in your Arcserve Backup domain. For example, you
can:
Allow a member server to separate from one Arcserve Backup domain and join
a different Arcserve Backup domain.
Select the application that you want to use to manage the Arcserve Backup
database.
For Microsoft SQL Server 2008 Express installations, the database must be installed
on the primary server. If you require remote database communication, you must
use Microsoft SQL Server to host the Arcserve database.
Move the Arcserve Backup database to other systems or use a different SQL Server
database instance in your environment.
Repair the Arcserve database connection to a primary server and member servers.
The caroot account password lets you log in to the Arcserve Backup Manager
Console to perform administrative tasks.
Specify the application that you want to use to host the Arcserve Backup
database.
You can specify Microsoft SQL Server 2008 Express or Microsoft SQL Server as
the Arcserve database application. SQL Server 2008 Express must be installed
locally to the Arcserve Backup primary server. SQL Server can be installed
locally or remotely to the Arcserve Backup primary server.
Specify SQL Server collation to ensure that you can search and sort backup data
that contains Unicode-based characters.
Note: Arcserve Backup does not support migrating Arcserve Backup database
information from multiple Arcserve Backup domains into a single Arcserve Backup
domain. Although you can demote a primary server and allow it to join a different
Arcserve Backup domain, joining a different domain will result in the loss of the
backup job history from the demoted primary server, and you will not be able to
view media and session details in the Restore Manager on the demoted server. For
more information, see Data Migration Limitations in an Arcserve Domain (see
page 562).
Note: Use the Server Admin Manager to modify the Arcserve Backup System
Account on a primary server and a member server (for example, user name,
password, and so on). For more information, see Change or Modify the Arcserve
Backup System Account (see page 520).
The original primary server hosted the Arcserve database instance using Microsoft
SQL Server 2008 Express Edition and new primary server is hosting the Arcserve
database instance using Microsoft SQL Server 2008 Express Edition.
The original primary server hosted the Arcserve database instance using Microsoft
SQL Server and new primary server is hosting the Arcserve database instance using
Microsoft SQL Server.
Important! Arcserve Backup does not support data migration when the original primary
server hosted the Arcserve database with Microsoft SQL Server and the new primary is
hosting the Arcserve database with Microsoft SQL Server 2008 Express Edition.
To accomplish a successful data migration, complete the following steps:
1.
From the primary server that you want to demote, back up the Arcserve database
using the Database Protection Job.
Note: Allow the Database Protection Job to finish before continuing.
2.
3.
Demote the original primary server and allow it to join new primary server's
domain.
4.
5.
From the Agent Restore Options dialog (see page 635) on the new primary server,
specify the following options:
Scenario 2:
You modify the application hosting the Arcserve database from Microsoft SQL Server
2008 Express Edition to Microsoft SQL Server.
Note: This scenario applies to Arcserve primary server and Arcserve stand-alone server
installations.
To accomplish a successful data migration, complete the following steps.
1.
Run the Server Configuration Wizard (see page 564) on the primary or stand-alone
server and specify the Select database option.
After the database modification and configuration process is complete, the Server
Configuration Wizard prompts you to migrate the data from the old database
instance to the new database instance.
2.
Migrate the data from the Microsoft SQL Server 2008 Express Edition instance to
the Microsoft SQL Server instance.
3.
4.
Reinstall the Agent for Arcserve Database to create the new database instance
using the following executable:
<ARCserve_HOME>\Packages\ASDBSQLAgent\SQLAgentRmtInst.exe
5.
Uninstall the ARCSERVE_DB instance of Microsoft SQL Server 2008 Express Edition.
Scenario 3:
You exchange the roles of the primary server and a member server in an Arcserve
domain. The original primary server hosted the Arcserve database instance using
Microsoft SQL Server 2008 Express Edition and new primary server is hosting the
Arcserve database instance using Microsoft SQL Server.
Note: In this scenario you must convert the Arcserve database from a Microsoft SQL
Server 2008 Express Edition instance to a Microsoft SQL Server instance on the primary
server that you want to demote before you back up the Arcserve database instance.
Run the Server Configuration Wizard on the primary server and specify the Select
database option.
After the database modification and configuration process is complete, the Server
Configuration Wizard prompts you to migrate the data from the old database
instance to the new database instance.
2.
Migrate the data from the Microsoft SQL Server 2008 Express Edition instance to
the Microsoft SQL Server instance.
3.
From the primary server that you want to demote, back up the Arcserve database
using the Database Protection Job.
Note: Allow the Database Protection Job to finish before continuing.
4.
5.
Demote the original primary server and allow it to join new primary server's
domain.
6.
From the Agent Restore Options dialog (see page 635) on the new primary server,
specify the following options:
7.
From the Windows Start menu, select Programs (or All Programs), CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
2.
Select the task that you want to perform, click Next, and follow the on-screen
procedures to complete your configurations.
All jobs must be stopped on the member server before the upgrade process starts.
Arcserve Backup detects all jobs with a Ready Status and places them in a Hold
status for you. If there are jobs in progress, Arcserve Backup displays a message and
the upgrade process pauses until all jobs in progress are complete.
If the promoted primary server will be configured as the central server in a Global
Dashboard domain and you want to continue to use the grouping configuration and
registered branch information collected from the old central server, you must
import this dashboard information into the server after it has been promoted. For
more information about how to import this dashboard information, see the
Dashboard User Guide.
During the upgrade process, you will be prompted to specify a Arcserve Backup
database application. You can specify Microsoft SQL Server 2008 Express Edition or
Microsoft SQL Server.
Microsoft SQL Server 2008 Express Installations
You can install the Arcserve Backup database local or remote to the primary
server.
Microsoft SQL Server does not support local installations when Arcserve
Backup is installed in NEC CLUSTERPRO environments.
For remote Microsoft SQL Server database installations, the primary server
must have a system account that properly authenticates with SQL Server and
communicates via ODBC before you start the upgrade process.
Open the Windows Control Panel, select Administrative Tools, Data Sources
(ODBC), and System DSN.
2.
3.
Note: Use the Server Admin to install Arcserve Backup options, such as the
Central Management Option, on the new primary server after the promotion
process is complete. For more information, see Install and Uninstall Arcserve
Backup Server Based Options (see page 590).
From the Windows Start menu, click Start, select All Programs, CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
2.
Click the Promote this server to primary server option and then click Next.
3.
After the configuration is complete, you must install the Arcserve Backup database
protection agent on the system hosting the Arcserve Backup database.
4.
If the SQL Server database is installed on the Arcserve Backup primary server,
open Windows Explorer and browse to the following directory:
C:\Program Files\CA\ARCserve Backup\Packages\ASDBSQLAgent
If the SQL server database is not installed on the Arcserve Backup primary
server, open Windows Explorer and browse to the following directory:
C:\Program Files\CA\ARCserve Backup\Packages\ASDBSQLAgent
Auth Mode
Specify the authentication mode that the agent will use to communicate with
and protect the Arcserve database.
If you specify SQL Authentication as the authentication mode, complete the
following fields:
SQL SA Name
Specify the SQL system account name.
SQL SA Password
Specify the SQL system account password.
7.
Click Install and follow the on-screen instructions to complete the installation.
All jobs must be stopped on the primary server before the demotion process starts.
Arcserve Backup detects all jobs with a Ready Status and places them in a Hold
status for you. If there are jobs in progress, Arcserve Backup displays a message and
the demotion process pauses until all jobs in progress are complete.
You must specify Arcserve Backup authentication credentials to allow the demoted
primary server to join the domain of another primary server (for example, caroot
and your Arcserve Backup password). The process of allowing a member server to
join a Arcserve Backup domain does not support using Windows authentication.
Demote the primary server and allow the member servers and the data mover
servers that it is managing to join the new domain.
As a best practice, you should move the member servers to different Arcserve
Backup domains and register the data mover servers with different primary servers
before you demote the primary server. Optionally, you can promote the member
servers to primary servers or stand-alone Arcserve Backup servers. Likewise, you
should promote the member servers before you demote the primary server.
If the primary server to be demoted contains data mover server relationships, you
must reconfigure the data mover server's file system device settings after you
demote the primary server and register the data mover server with different
primary server.
All registered licenses will be removed from the demoted primary server.
If you set up jobs using a different caroot user account before the demotion, you
must manage the migrated jobs on the primary server in the domain that the new
member server joins using the original caroot account and password as the job
owner for all migrated jobs.
The table that follows describes database migration scenarios and the type of data
that Arcserve Backup migrates from the demoted primary server to the domain that
the new member server (demoted primary server) joins:
Database on Demoted
Primary Server
Authenticatio
n Data
Migrates?
No
No
No
No
No
No
Database on Demoted
Primary Server
Authenticatio
n Data
Migrates?
Yes
No
Yes
Yes
Yes
No
From the Windows Start menu, click Start, select All Programs, CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
2.
Click Demote this server to member server and then click Next.
3.
4.
(Optional) After the configuration is complete, you can uninstall the Arcserve
database protection agent from the server that you demoted by doing the
following:
From the Windows Control Panel, open Add and Remove Programs.
Select the Agent for Arcserve Database option and click OK.
Follow the on-screen instructions to complete the uninstallation.
6.
(Optional) To move the CA licenses from the demoted primary server to a different
Arcserve Backup primary server, do the following:
a.
On the demoted primary server, locate the file labeled ca.olf in the following
directory:
c:\program files\ca\SharedComponents\ca_lic
b.
c.
Copy ca.old from the demoted primary server to the following directory on the
other primary server:
c:\program files\ca\SharedComponents\ca_lic
d.
On the other Arcserve Backup Primary server, open a Command Line window
and open the following utility.
c:\program files\ca\SharedComponents\ca_lic\mergeolf.exe
For more information about using the MergeOLF command, see the Command
Line Reference Guide.
7.
Uninstall the Arcserve Backup server-based options from the demoted primary
server.
You can use the Server Admin Manager to uninstall the following server-based
options from the demoted primary server:
Note: For more information, see Install and Uninstall Arcserve Backup Server Based
Options (see page 590).
You must remove all other options from the demoted primary server (for example,
Global Dashboard) using Windows Add and Remove Programs.
Note: For information about Arcserve Backup server-based options that you can
install on Arcserve Backup servers, see "Types of Arcserve Backup Server
Installations" in the Implementation Guide.
8.
Restart the primary server in the domain that the member server (demoted primary
server or stand-alone server) joined. This step helps to ensure that the information
about backup data associated with the member server is accurate on the primary
server.
All jobs must be stopped on the member server before the move process starts.
Arcserve Backup detects all jobs with a Ready Status and places them in a Hold
status for you. If there are jobs in progress, Arcserve Backup displays a message and
the move process pauses until all jobs in progress are complete.
After the member server joins a different Arcserve Backup domain, the jobs
associated with the previous domain will migrate to the new domain. However, all
database information relating to the member server will remain with the previous
domain.
From the Windows Start menu, click Start, select All Programs, CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
2.
Click the Move this server to another Arcserve Backup domain option and then
click Next.
3.
Change the Password for the Arcserve Backup Domain Administrator (caroot)
Account
The caroot password can consist of any combination of alphanumeric and special
character but may not exceed 15 bytes. A password totaling 15 bytes equates to
approximately 7 to 15 characters. Using the Server Configuration Wizard, you can
change the password for the Arcserve Backup Domain Administrator (caroot) account.
The Domain Administrator account lets you log in to the Arcserve Backup Manager
Console to perform administrative tasks.
The caroot password can consist of any combination of alphanumeric and special
characters, but may not exceed 15 bytes. A password totaling 15 bytes equates to
approximately 7 to 15 characters.
Before you change the password for the Arcserve Backup system account, you must be
logged in to a Arcserve Backup primary server.
Note: Use the Server Admin to change the password to the system account on a
member server. For more information, see Change or Modify the Arcserve Backup
System Account (see page 520).
To change the password for the Arcserve Backup Domain Administrator (caroot)
account
1.
From the Windows Start menu, click Start, select All Programs, CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
2.
Click the Password for Backup Server Logon and Administration option and then
click Next.
3.
If the installation wizard detects installation errors with a member server, the
Arcserve Backup Configuration Repair Mode dialog appears as illustrated by the
following screen:
2.
Click Next.
The Server Configuration Wizard starts in repair mode.
Follow the prompts and complete the required fields on the subsequent dialogs to
repair the Arcserve Backup configuration.
To remedy this problem, troubleshoot and repair the communication using the SQL
Server Configuration Manager and then use the Server Configuration Wizard to repair
ODBC communication between the Database engine and the Arcserve database
instance.
To repair the Arcserve database connection on a primary server
1.
2.
From the Windows Start menu, click Start, select All Programs, CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
3.
Select the Repair database connection for member server(s) option and click Next.
4.
Follow the prompts and complete all required fields on the subsequent dialogs to
repair the database connection.
Note: When you repair the database connection on a primary server that is
managing member servers, the Server Configuration Wizard attempts to repair the
database connection on all member servers in the Arcserve domain.
2.
From the Windows Start menu, click Start, select All Programs, CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
3.
4.
Follow the prompts and complete all required fields on the subsequent dialogs to
repair the database connection.
You want to protect the application data (submit backup and restore jobs) using the
virtual name of the service or application that is registered with MSCS.
You want to add the virtual name of the service or application to the Backup
Manager Source tab and Destination tab.
You want to submit backup and restore jobs in a storage area network (SAN)
instead of a local area network (LAN).
Note: To submit backups of this type, the physical nodes in the MSCS cluster must
be connected to the SAN and a shared tape library.
To complete this task, the virtual clusters and the member server must reside on the
same physical machine. In addition, the virtual clusters and the member server must be
in an online state while you complete this task.
You can perform this task in cluster environments where MSCS is installed on any of the
following Windows operating systems:
Before you complete this task, verify that the following prerequisite tasks are complete:
MSCS is installed on the nodes that you want to register with the primary server.
The Arcserve Backup member server component and the application agent are
installed on all of the nodes in the cluster.
The physical nodes contained in the virtual cluster that you want to register with
the primary server are connected to the SAN and a shared library.
2.
From the Windows Start menu, select All Programs, CA, ARCserve Backup, and click
Server Configuration Wizard.
The Server Configuration Wizard opens to the Select Options dialog.
3.
Click Register virtual clusters as Arcserve Backup domain member servers and then
click Next.
The Check caroot dialog opens.
4.
5.
Click the check boxes next to the Virtual Names that you want to register with the
primary server and click Next.
6.
7.
8.
Right-click the node that you registered with the primary server and click Refresh
on the pop-up menu.
The virtual node displays the correct status.
Note: As a best practice, you should verify that you have a sufficient quantity of
Arcserve Backup server component licenses to support backing up data to member
servers. To submit jobs to member servers (virtual clusters), you must apply Arcserve
Backup server component licenses to the member servers. The license count will be
consumed based on the quantity of virtual clusters that you registered as member
servers in the Arcserve Backup domain.
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
The Client Agent for Windows is installed on the domain controller server.
The domain controller server resides in the same domain as the server from which
the backup was taken.
The operating system running on the domain controller server is the same version,
release, and service pack as the server from which the backup was taken.
Arcserve Backup lets you protect the Active Directory using the following approaches:
Restore the System State to its original location--Arcserve Backup lets you restore
the System State, which includes all objects in the Active Directory, to the server
from which it was backed up. With this approach, you overwrite all of the objects
contained in the Active Directory.
Use this approach when you need to restore the entire Active Directory to a
previous point in time.
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
Note: To protect Active Directory data, Arcserve Backup Client Agent for Windows must
be licensed on the Domain Controller server.
Arcserve Backup lets you restore Active Directory data that was backed up using the
following Arcserve Backup releases:
Arcserve Backup r12. Includes the general availability release and all of the latest
service packs.
Arcserve Backup r12.5. Includes the general availability release and all of the latest
service packs.
The CA Active Directory Object Level Restore utility lets you restore the following Active
Directory objects:
Organizational Unit
User
Group
Computer
Contact
Connection
Shared folder
Printer
Site
Site container
Site link
Site settings
Subnet container
Trusted domain
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
Configuration class
Lostandfound class
Builtindomain class
Dnszone class
Domain class
Domaindns class
Dmd class
Organizationalunit class
Containerecifiers class
The CA Active Directory Object Level Restore utility cannot restore the following Active
Directory objects
System Schema
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
Create a backup job as you would create any other backup job and include the
System State object for the computer with the source selections for the job.
Create a backup job that includes only the computer's System State.
Note: The following steps describe how to submit a normal backup job. For information
about submitting staging and deduplication backup jobs, see "Backing up Data."
To back up the Active Directory
1.
Open the Backup Manager Window and click the Start tab.
The Backup job types display.
2.
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
3.
4.
Click the Schedule tab to define when and how frequently you want to back up the
System State.
Note: For information about scheduling jobs, see "Customizing Jobs."
5.
6.
Select the Device Group where you want to store the backup data.
7.
Click Options on the toolbar to define backup options for the job.
Note: For information about backup options, see "Backing up Data."
8.
Restore the Active Directory backup data to an alternate location using the Restore
Manager. The alternate location should reside on the server where the System
State was backed up.
Recover the Active Directory object to the current Active Directory using the CA
Active Directory Object Level Restore utility.
Restoring the Active Directory to its original location restores all of the objects
contained in the Active Directory. The process for restoring the Active Directory to its
original location is the same that of restoring files, directories, and so on. For more
information, see "Restoring Data."
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
Open the Restore Manager window, click Source, and expand the server and
System State containing the Active Directory that you want to restore.
Click the check box next to Active Directory as illustrated by the following screen:
2.
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
3.
(Optional) To restore the Active Directory to an alternative server, copy the files
from the restore destination that you specified in the previous step to the
alternative server.
Note: The best practice is to specify an alternative directory on the server where
you are restoring the Active Directory. However, if you must restore the Active
Directory to an alternative server, you can copy the restored Active Directory files
from the alternative server to the source server or any other domain controller that
is in the same domain as the source server. The restrictions on this capability are as
follows:
4.
The Client Agent for Windows must be installed on the alternative server.
The operating system running on the alternative server must be the same
version, release, and service pack as that of the server from which the backup
was taken.
Log in to the Domain Controller server containing the restored, or copied, Active
Directory data.
Open Arcserve Backup Agent Admin by doing the following:
From the Windows Start menu, select All Programs, CA, ARCserve Backup, and click
Arcserve Backup Agent Admin.
Arcserve Backup Agent Admin opens.
Note: To open the Arcserve Backup Agent Admin, you must be logged in to the
server using an account that has Domain Administrative privileges.
5.
From the Options menu on the Arcserve Backup Agent Admin dialog, click AD
Object Level Restore Utility.
The CA Active Directory Object Level Restore dialog opens.
6.
Left pane--Lets you view all objects included in the selected Active Directory
ntds.dit database file.
Right pane--Lets you view the attributes and child objects related to the item
selected in the left pane.
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
Note: Arcserve Backup lets you restore only the Active Directory Objects that
appear in the CA Active Directory Object Level Restore dialog. Arcserve Backup
cannot restore system related objects.
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
7.
(Optional) Click Option on the toolbar to open the Restore Options dialog.
Arcserve Backup lets you filter the active directory objects that you want to restore
and specify a log level for the restore operation.
a.
b.
Log Level--Lets you specify the level of details that you require in the
debug log.
Default value: 0
Range: 0 to 3
0--Prints error messages to the log files.
1--Prints error and warning messages to the log files.
2--Prints error, warning, and information messages to the log files.
3--Prints error, warning, information, and debug messages to the log files.
Note: Level 3 is the highest level of logging details. If you encounter
problems restoring active directory files, you should specify level 3 and
then send the log files to Arcserve Support.
The Active Directory restore process generates the following log files:
adrestorew.log
CadRestore.exe.trc
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
8.
(Optional) Click Filter on the toolbar to open the Filter Settings dialog.
Note: The best practice is to use filters when you are searching for a specific object.
Specify one of the following filter settings:
Show all types of objects--Lets you display all objects in the Active Directory
Object Restore dialog.
(Optional) To limit the number of child nodes, click Maximum number nodes
under each parent nodes and specify a limit in the text box.
Show only the following types of objects--Lets you display only objects of a
particular type in the Active Directory Object Restore dialog.
Show only the following named objects--Lets you display only objects with a
particular name in the Active Directory Object Restore dialog.
Note: The Active Directory for a computer can contain a large number of
objects. The best practice is to filter the objects using the Show only the
following named objects filter and specify the name of the object that you
want to restore.
From the Active Directory Object Restore dialog, expand the Active Directory tree
and click the check box next to the objects that you want to restore.
Click Restore on the toolbar to restore the specified objects.
Arcserve Backup restores the Active Directory objects to the current Active
Directory.
After the restore is complete the Restore Status message box opens.
Note: The Restore Status messages box describes the outcome of the job.
How Arcserve Backup Protects Active Directory Data on Domain Controller Servers
Recover the Active Directory using the CA Active Directory Object Level Restore
utility (see page 583).
2.
3.
4.
Reset Microsoft Exchange Server User Passwords After Recovering the Active
Directory
Arcserve Backup lets you recover the Active Directory on domain controller servers.
Although the Active Directory contains data that relates to Windows user accounts,
Windows does not store the passwords for user accounts in the Active Directory. As
such, the Active Directory recovery process does not let you restore user passwords.
Use the following guidelines for resetting user passwords after you recover the Active
Directory:
If the user account was present in the Active Directory before recovered the Active
Directory, you do not need to reset the password for the user account.
If the user account was not present in the Active Directory (for example, deleted),
you must reset the password for the user account.
Before you install and uninstall Arcserve Backup server based options, the following
considerations apply:
You can install and uninstall options only on a primary or stand-alone Arcserve
Backup server.
The Arcserve Backup options that display in the Install/Uninstall Options dialog will
vary depending on the type of Arcserve Backup server you are configuring.
If you are installing server based options, ensure that all external devices (for
example, libraries) are connected to the primary servers, member servers, and the
SAN in your environment. Arcserve Backup automatically detects supported devices
and configures them for use automatically when the tape engine starts.
You must manually configure devices that Arcserve Backup does not automatically
detect.
From the Quick Start menu in the Navigation Bar on the Home Page, click Server
Admin.
The Server Admin opens.
2.
Expand the domain directory tree and click the primary or stand-alone server where
you want to install or uninstall options.
The domain directory tree is illustrated by the following:
Discovery Configuration
3.
Right-click the server where you want to install and uninstall options and select
Install/Uninstall Options from the pop-up menu.
The Install/Uninstall Options dialog opens.
4.
From the Product Name list on the Install/Uninstall Options dialog, place a check
mark next to the options that you want to install and clear the check mark next to
the options that you want to uninstall.
5.
Discovery Configuration
Discovery Configuration in a service that you can use to periodically discover computers
in your network for newly added or upgraded Arcserve Backup software. A Discovery
server runs as a background process that collects information from all other Discovery
servers installed with Arcserve products across the corporate network.
Discovery Configuration allows you to distribute discovered network target information
to remote servers. This capability allows administrators to decrease network traffic load
created by Discovery servers to discover Windows domains or IP subnet addresses.
The Discovery Configuration allows you to perform the following tasks:
Add, remove or modify information in any of the three tables created by Discovery
Configuration (IP subnets, IP subnet masks, and Windows domains)
You can open the Discovery Configuration at the command line or from Windows
Explorer:
Discovery Configuration
Discovery Configuration
Enable Discovery of Arcserve Backup Products allows the Discovery Service (DS) to
broadcast queries repeatedly, with a specified interval.
It is not recommended that this be run at all times because it continually broadcasts
queries which could increase network traffic.
Network Tab
Use the Network tab to configure the following options:
Adapters Tab
Discovery Configuration
In another scenario, you might want to enumerate the entire corporate network to find
all possible subnets and then filter some of them out. The discovery process runs in the
background, and enumerates Windows network's resources. A list of Windows domains
for subsequent Mailslot broadcasting or a listing of IP subnets for UDP broadcasting is
created.
Note: This process may take some time, depending on the size of your network. It is
recommended that the IP subnets and domains discovery be run during a time of
minimum network traffic.
Discovery Configuration
The discovery service broadcasts and retrieves all the information of the local subnet
machines as well as manually-defined subnets and manually-defined machines.
To enable add a machine name (IP address) manually
1.
Start Discovery and click the Add button on the Windows Domain tab.
2.
Start Discovery and click the Add button on the Subnet tab.
The Add a Subnet dialog opens.
2.
If you choose to perform an auto discovery, the discovery service will ping and
publish a product list to each machine in each subnet listed in the Discovery
Configuration Subnet tab and retrieve the product information from the remote
machine.
Discovery Configuration
3.
To do this, start Discovery and click the Configure button on the Summary tab. The
Configuration dialog opens as shown in the following example:
The Discovery server initiates an IP address sweep for remote subnets by using the
auto-discovered subnets, subnet masks, machine, or Windows domains along with
the manually-configured subnets, subnet masks, machines or Windows domains.
Selecting this option may increase network traffic and can take a considerable
amount of time to complete, depending on the size of your network. We
recommend that you run this option during a time of minimum network traffic.
Note: If you choose to discover Arcserve Backup products in remote subnets, the
discovery service does not rely on a UDP broadcast to locate remote instances. You
need to know the size of the subnet and range of IP addresses using a subnet mask.
Discovery Configuration
Select the "All auto discovered subnets (may increase network traffic)" option in the
Enable Discovery using TCP/IP Subnet sweep field in the Configuration dialog.
Add other remote SAN machine names/IP addresses by accessing the Windows
Domain tab.
Note: The configuration for each remote SAN server must be consistent to ensure
accurate discovery. If you only configure one SAN server, other servers may still fail in
discovery.
2.
From the Backup Manager of the base server, delete the old machine object.
3.
Click Add/Import/Export Nodes and add or import the nodes that you require.
Note: For more information, see Add, Import, and Export Nodes Using the User
Interface (see page 334).
4.
If you have a scheduled job in the queue, delete that job and recreate it to ensure
that it runs properly.
Maintenance Options
Do not update your Arcserve Backup maintenance contract--If you do not wish to
update Arcserve Backup at this time, click the X in the upper left-hand corner of the
maintenance notification message to close the message. If you do not want to
receive the messages, you must disable (see page 599) maintenance notification
messages.
Alert Options
Arcserve Backup lets you disable (see page 599) and enable (see page 600) the
maintenance notification message using the Arcserve Backup icon located in the
Windows system tray.
From the Windows system tray, right-click the Arcserve Backup icon Disable Alert
from the pop-up menu.
Open Windows Registry Editor and browse to the following registry key:
x86 platforms:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve
Backup\Base\Admin\MessageEngine\MonthsPassedInLastMaintenance
x64 platforms:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\CA ARCserve
Backup\Base\Admin\MessageEngine\MonthsPassedInLastMaintenance
You installed Arcserve Backup components using trial licenses and you want to
apply license keys to the components.
Managing Firewalls
2.
3.
Click a component.
b.
c.
Click Add.
Note: If you attempt to apply an upgrade license key to a new Arcserve Backup
component installation, the Upgrade Verification dialog opens. You must provide
the license key for your previous installation to apply your upgrade license key.
(Optional) Repeat this step to apply license keys to other Arcserve Backup
components.
4.
Managing Firewalls
This section contains the following topics:
Allow Arcserve Backup Services and Applications to Communicate Through the Windows
Firewall (see page 601)
How to Configure Your Firewall to Optimize Communication (see page 602)
Managing Firewalls
The following procedure lets you allow Arcserve Backup services and applications to
communicate if the Windows firewall was in the Off state when you installed Arcserve
Backup.
To allow Arcserve Backup services and applications to communicate though the
Windows firewall
1.
Open the Windows Command Line, and change to the following directory:
c:\Program Files\CA\SharedComponents\ARCserve Backup\
2.
Arcserve Backup services and applications are added to the Windows firewall
exception list. Arcserve Backup services and applications can now communicate
though the Windows firewall.
Detailed information about each file and directory that was backed up to media
when you perform a restore.
When you want to restore a specific file, the database determines which media a
file is stored on.
Database Manager
Database Manager
The Database Manager lets you perform the following tasks:
Visually compare the size of your database to the total available disk space.
Note: For Microsoft SQL Server databases, the total database size reported by the
Arcserve Backup Database Manager is the size of the data device. You can obtain
more information by browsing through the Microsoft SQL Server Enterprise
Manager.
Database Views
When you open the Database Manager, the left panel displays the following options:
Summary--Space the database used on your hard disk, database type, and other
settings.
Sort Order
To change the sort order of records displayed in the Job, Media, and Device Records
view, click on the field name you want to sort.
Database Pruning
You can set Arcserve Backup to remove old records from the database. For more
information, see Administering the Backup Server.
Database Manager
Media Errors--Indicates data corruption occurred on the media preventing the read
or write operation from successfully completing.
Soft Read Errors--An error occurred while reading the media. Arcserve Backup
attempted to correct the problem in real-time. A higher number of soft read errors
indicate possible defective media. Media should be replaced for any future
backups.
Soft Write Errors--A write error occurred during the backup. Arcserve Backup is
correcting the media problem in real time. A high number of soft write errors
indicates the media should be replaced for future backups. Make sure the drive
heads are cleaned after the current backup session is completed.
Database Manager
Soft Read--Number of soft read errors that occurred during the job.
Media Usage--Amount of time the media was used during the job.
Backup date
Type of database
Arcserve Backup manages the log files using the following logic:
1.
The information for the most recent full, incremental, and differential backup of the
Arcserve Backup database is always stored in the file labeled ASDBBackups.txt.
2.
After the second full backup of the Arcserve Backup database is complete,
ASDBBackups.txt is renamed ASDBBackups.1.txt and then a new ASDBBackups.txt is
created.
3.
4.
The log file renaming and creating process continues until Arcserve Backup creates
a log file named ASDBBackups.10.txt.
5.
If a log file labeled ASDBBackups.10.txt exists after the full backup is complete,
Arcserve Backup deletes ASDBBackups.10.txt, renames the older log files, and then
creates a new ASDBBackups.txt log file.
Open the Server Admin Manager and click the Configuration toolbar button.
The Configuration dialog opens.
2.
3.
Because the Agent for Arcserve Database is a form of the Agent for Microsoft SQL
Server, it will appear as the Arcserve Backup Agent for Microsoft SQL Server in the
systems installed programs list. If both are present, only a single entry will appear. If
you need to uninstall one or the other, the installation sequence will prompt you to
select which variant to remove.
You can use the stand-alone utility that installs the Agent for Arcserve Database in any
of the following situations:
To install the agent on a remote computer, if the Arcserve Backup installer is unable
to do so directly
Configure Backup and Restore Parameters for the Agent for Microsoft SQL Server Using the
Central Agent Admin
Use the Central Agent Admin utility to configure the Agent for Microsoft SQL Server
backup and restore parameters for supported versions of Microsoft SQL Server. The
parameters include settings for Microsoft Virtual Device Interface (VDI) objects and
remote communication.
To configure backup and restore parameters for the Agent for Microsoft SQL Server
using the Central Agent Admin
1.
From the Arcserve Backup Quick Start menu, choose Administration, Central Agent
Admin.
Central Agent Admin opens.
2.
In the Windows Systems tree, expand the server on which the agent is installed and
then select the Agent for Microsoft SQL Server.
Click Configuration on the toolbar.
The Options Configuration dialog opens.
3.
Click Agent for Microsoft SQL Server from the list on the left.
The Options Configuration shows the corresponding SQL Server settings.
4.
5.
Select the Instance (ARCSERVE_DB) or the name of the instance for which you wish
to change configuration for the Agent for Microsoft SQL Server.
6.
Data Block Size (in bytes)--All data transfer sizes are multiples of this value.
Values must be a power of 2 between 512 bytes and 64 KB inclusive. The
default is 65536 or 64 KB.
7.
Under Named Pipes Configuration, specify the Maximum Connection Wait Time
(ms) time, in milliseconds, the Agent for Microsoft SQL Server should wait to close a
named pipe if a remote connection fails. The default setting is 400 ms.
8.
Click Apply to Multiple to display a dialog from which you can select additional SQL
Servers. Click OK to apply the settings and return to Configuration.
9.
Configure Backup and Restore Parameters for the Agent for Microsoft SQL Server Using the
Backup Agent Admin
Use the Backup Agent Admin utility to configure the Agent for Microsoft SQL Server
backup and restore parameters for supported versions of Microsoft SQL Server. The
parameters include settings for Microsoft Virtual Device Interface (VDI) objects and
remote communication.
To configure backup and restore parameters for the Agent for Microsoft SQL Server
using the Backup Agent Admin
1.
Log in to the computer where the Agent for Microsoft SQL Server is installed.
From the Windows Start menu, select All Programs, CA, ARCserve Backup, Backup
Agent Admin.
The Arcserve Backup Agent Admin dialog opens.
2.
Select Agent for Microsoft SQL Server from the drop-down list and click the
Configuration icon.
The appropriate configuration dialog opens.
3.
On the Common Settings tab, specify the Level of Detail and Synchronized
Recording under Agent Log Settings, as follows:
Level of Detail--Controls the settings for level of detail of the agents Activity
Log and Debugging Log. For the Activity Log settings, a Level of Detail setting of
Normal (0) includes basic information about agent activity. A setting of Detail
(1) includes more detailed information about agent activity. A setting of Debug
(2) enables the Debugging Log at a moderate level of detail. A setting of Trace
(3) enables the Debugging Log at a very high level of detail. The Activity Log is
localized for your reference. The Debugging Log is for Arcserve Support use,
and is not available in multiple languages.
4.
5.
On the Instance Settings tab, select the Instance (ARCSERVE_DB) or the name of the
instance for which you wish to change configuration for the Agent for Microsoft SQL
Server.
6.
Data Block Size (in bytes)--All data transfer sizes are multiples of this value.
Values must be a power of 2 between 512 bytes and 64 KB inclusive. The
default is 65536 or 64 KB.
7.
Under Named Pipes Configuration, specify the Maximum Connection Wait Time
(ms) time, in milliseconds, the Agent for Microsoft SQL Server should wait to close a
named pipe if a remote connection fails. The default setting is 400 ms.
8.
Execution Time--11:00AM
Important! After you start the Database Protection Job, the Tape Engine will connect to
a blank media in the first group that Tape Engine detects, and assign the media pool
labeled ASDBPROTJOB. If the Tape Engine cannot connect to a blank media in the first
group within five minutes, the Tape Engine will try to connect with blank media in the
other groups sequentially. If the Tape Engine cannot connect to blank media, in any
group, the job will fail.
More information:
Modify, Create, and Submit a Custom Database Protection Job (see page 614)
Create a backup job as you would create any other backup job and include the
Arcserve Backup database objects with the source selections for the job.
This method requires that you know if you are running SQL Server 2008 Express or
SQL Server in your environment. With this knowledge you must specify the proper
source selections and Global Backup Operation options for the job to ensure that
the required metadata and related items for each database type are backed up.
This approach lets you back up the affected databases, files, or both, when the
backup up job is complete.
Important! You should not protect the Arcserve database using multiple backup servers
that do not reside in the domain that is using the Arcserve database.
Ensure that the Tape Engine can detect at least one device in your environment. For
more information, see "Managing Devices and Media."
Ensure that the default Database Protection Job exists in the Job Queue. If the
Database Protection Job does not exist in the Job Queue, you must recreate it. For
more information, see Recreate the Arcserve Backup Database Protection Job (see
page 625).
2.
3.
Click the Destination tab and specify a location, media, or both where you want
to store the backup data. For more information, see Options You Can Specify
on the Backup Manager Destination Tab.
From the Start tab, click the Enable Staging check box.
The Staging Location and Policies tabs appear.
Click the Staging Location tab and specify where you want to stage the backup
data. For more information about using staging, see Backup Staging Methods
(see page 200).
4.
Click the Schedule tab and specify a schedule for the job. For more information, see
Rotation Schemes (see page 307).
5.
6.
Job scripts--This option ensures that new and updated job scripts are
backed up after jobs are complete.
Catalog files--This option ensures that the Catalog files are backed after
backup jobs are complete.
Job scripts--This option ensures that new and updated job scripts are
backed up after jobs are complete.
SQL Server--Optional Options-For SQL Server databases, the following options are optional:
Catalog files--This option ensures that the Catalog files are backed after
backup jobs are complete.
Click OK.
The Global Options dialog closes and the Operation options are applied.
7.
8.
From the Submit Job dialog, enter a description for your job and click OK.
The Database Protection Job is submitted.
Specify Microsoft SQL Server 2008 Express Backup Options for the Arcserve
Backup Database
Arcserve Backup can use full and differential backup methods when backing up
Microsoft SQL Server 2008 Express databases. This capability lets you use a rotation
scheme or a schedule when backing up the Arcserve Backup database. Additionally,
Arcserve Backup lets you check the consistency of the database before the backup job
starts or after the backup job is complete.
To specify Microsoft SQL Server 2008 Express backup options
1.
Open the Backup Manager windows, select the Source tab, and expand the
Windows System object to locate the Arcserve Backup primary server.
2.
Expand the Primary server, right-click the Arcserve Backup Database object, and
select Agent Option from the pop-up menu.
The Agent Backup Option dialog opens.
3.
From the Agent Backup Option dialog, specify the options that you require to
protect the database.
Full--Select this option to perform a full backup every time the job is run.
When you perform a full backup, Arcserve Backup performs a full backup
of the three system databases, the 24 Arcserve databases, and records a
synchronization checkpoint. Arcserve Backup creates two backup sessions.
One session will contain the disaster recovery elements. The other session
will contain all of the data that is required to restore the Arcserve Backup
database.
Specify the Database Consistency Check (DBCC) options that you require. DBCC
options let you check the allocation and structural integrity of all the objects in
the specified databases.
Do not check indexes--Select this option to check only the system tables.
With Override Global Options specified, the DBCC options selected at the
database level will be the only DBCC options specified.
With Override Global Options not specified, all of the DBCC options
specified for the database and all the DBCC options selected in the Global
options will be applied together.
On the Global Options/Agent Options tab, the DBCC options that follow are
specified:
After backup
On the Agent Backup Options dialog, Override Global Options is not selected
and the DBCC options that follow are specified:
Before backup
When you submit the backup job, Arcserve Backup applies the DBCC options
specified in logical order: Perform the DBCC before the backup starts. If the
DBCC fails, perform the backup. After the backup is complete, do not check the
indexes.
4.
Click OK.
Specify Microsoft SQL Server Backup Options for the Arcserve Backup Database
Arcserve Backup lets you protect the Arcserve Backup database using full, incremental,
and differential backup methods. This capability lets you use rotation schemes and
schedules to protect the database. Additionally, Arcserve Backup lets you back up only
the transaction log and check the consistency of the database before the backup job
starts or after the backup job completes.
Note: For information about how to protect Microsoft SQL Server databases that do not
function as the Arcserve Backup database, see the Agent for Microsoft SQL Server Guide.
Open the Backup Manager windows, select the Source tab, and expand the
Windows System object and locate the server that is hosting the Arcserve Backup
database.
The server hosting the Arcserve Backup database can be a primary server, a
member server, or a remote system. If the server hosting the Microsoft SQL Server
database does not appear in the Backup Manager directory, you must add the
server to the directory tree under the Windows Systems object before continuing.
For more information, see Back Up Remote Servers (see page 197).
Note: To specify SQL Server backup options, you must authenticate using Windows
or SQL Server credentials.
2.
Expand the server, right-click the Arcserve Backup database object, and select
Agent Option from the pop-up menu.
The Agent Backup Option dialog opens.
3.
From the Agent Backup Option dialog, specify the options that you require to
protect the database.
The following backup methods are provided:
Use Global or Rotation Options--Backs up the database selected using the jobs
Global or Rotation Phase Backup Method. The Global or Rotation Options
provides the following options:
The Full job method will result in a Full backup of the database.
The Incremental job method will result in a Transaction Log backup With
Truncation for databases using the Full and Bulk-Logged Recovery Models,
and a Differential backup of databases using the Simple Recovery Model,
unless this database has not yet had a Full backup.
The three main System databases are exempt from the Global or Rotation
job method; selecting this option for databases [master], [model], or
[msdb] will always result in a Full backup.
Full--Full backup is performed. The files included in the Database Subset will be
backed up in their entirety.
Differential--Backs up data that has changed since the last Full backup. For
example, if you ran a complete backup of your database on Sunday night, you
can run a differential backup on Monday night to back up only the data that
changed on Monday. This option is not available for the [master] database.
Transaction Log--Backs up only the Transaction log. This option is only available
for databases using the Full and Bulk-Logged Recovery Models.
Back up Transaction Log After Database--Backs up the transaction log after the
database is backed up. This allows you to perform a Full or Differential backup
and a Transaction Log backup in the same job. This option is available only for
databases using the Full and Bulk-Logged Recovery Models.
Remove inactive entries from transaction log, after backup--Truncates the log
files. This is the default option.
Backup only the log tail and leave the database in unrecovered mode--Backs
up the log and leaves the database in a restoring state. This option is available
for Microsoft SQL Server 2000 or later. Use this option to capture activity since
the last backup and take the database offline to restore it.
Important! Do not use the "Backup only the log tail and leave the database in
unrecovered mode" log truncation option to back up the ARCserve Database.
Performing a backup with this option causes the database to be placed in an
offline status, and you can lose the ability to find the backups of the ARCserve
Database in order to perform a restore and bring the database online. If you
perform a backup of the ARCserve Database using this option, you can use
ARCserve Database Recovery Wizard to recover the Arcserve Backup database
and bring it back online.
After Backup--Select this option to check the consistency of the database after
the backup completes.
Continue with backup, if DBCC fails--Select this option to continue the backup
even if the check before backup operation fails.
Do not check indexes--Select this option to check the database for consistency
without checking indexes for user-defined tables.
Note: The system table indexes are checked regardless of whether you select
this option.
With Override Global Options specified, the DBCC options selected at the
database level will be the only DBCC options specified.
With Override Global Options not specified, all the DBCC options specified
for the database and all the DBCC options selected in the Global options
will be applied together.
On the Global Options/Agent Options tab, the DBCC options that follow are
specified:
After backup
On the Agent Backup Options dialog, Override Global Options is not selected
and the DBCC options that follow are specified:
Before backup
When you submit the backup job, Arcserve Backup applies the DBCC options
specified in logical order: Perform the DBCC before the backup starts. If the
DBCC fails, perform the backup. After the backup is complete, do not check the
indexes.
Override Global Options--Enabling this option will override the Global option
setting pertaining to the selected database.
Note: Backup Method and Transaction Log Truncation options are not affected
by this option because they can be overridden separately. This option is
available only on a per-database basis.
4.
SQL Native Backup Compression--This option applies to only SQL Server 2008
(Enterprise) and later versions. If enabled, this option lets Arcserve Backup use
SQL Server database backup compression settings, which results in faster
backup times and smaller sessions.
Click OK.
The Agent Backup Options are applied.
2.
Select the Job Queue tab and find the Database Protection Job.
Note: If the Database Protection Job was deleted, you can recreate the job using
the steps in Recreate the Arcserve Backup Database Protection Job (see page 625).
Right-click the Database Protection Job and select Ready from the pop-up menu.
The status of the Database Protection Job changes from Hold to Ready. A full
backup of the database will be performed at the next Execution Time.
3.
(Optional) To start the Database Protection Job now, right-click the Database
Protection Job and select Run Now from the pop-up menu.
The Database Protection Job starts now.
Important! After you start the Database Protection Job, the Tape Engine will
connect to a blank media in the first group that Tape Engine detects, and assign the
media pool labeled ASDBPROTJOB. If the Tape Engine cannot connect to a blank
media in the first group within five minutes, the Tape Engine will try to connect with
blank media in the other groups sequentially. If the Tape Engine cannot connect to
blank media, in any group, the job will fail.
Access Requirements
When you submit a job that includes remote Windows database servers, Arcserve
Backup prompts you for a default user name and password for the system on which the
database resides. Arcserve Backup accesses the remote servers using this user name
and password.
A Microsoft SQL Server native user name and password are also required to access some
database servers. When prompted by the system, enter the Microsoft SQL Server user
ID and the password of the system administrator (sa), or enter a user ID and password
with equivalent privileges. This user may be a Windows user, depending on security
settings.
Note that there are two different data transfer mechanisms available to the agent, and
that they have different permission requirements. A backup using Named Pipes only
requires the Backup Operator permission for the specific database being backed up, and
the Database Creator role to back up the database. A backup using Virtual Devices,
however, requires the System Administrator role.
Note: A user in the Backup Operator Group does not have rights to access the Arcserve
Backup database. As a result, member servers are not visible to the user in the Backup
Manager.
2.
Select the Job Queue tab and locate the Database Protection Job.
Right-click the Database Protection Job and select Delete from the pop-up menu.
A warning message appears.
3.
If you are sure that you want to delete the Database Protection Job, click OK.
The Database Protection Job is deleted.
Note: For information about how to recreate the Arcserve Backup Database Protection
Job, see Recreate the Arcserve Backup Database Protection Job (see page 625).
2.
3.
b.
In the Server field, specify the name of the Arcserve Backup server where you
want the Database Protection Job to run. You can specify an Arcserve primary
server or an Arcserve member server from the domain where you want to
recreate the Database Protection job.
c.
In the Group field, specify the name of the device group where you want to
store the Database Protection Job data.
Click OK.
Arcserve Backup recreates the Database Protection Job.
4.
The Arcserve Backup database could not be recovered from a disaster using
ARCserve Database Recovery Wizard.
The Arcserve Backup database could not be started for various reasons.
When you execute this procedure, the Server Configuration Wizard overwrites the
existing Arcserve Backup database instance, which allows you to re-initialize the
Arcserve Backup database.
Important! The re-initialization process overwrites your Arcserve Backup database and
you will lose backup data. Ensure that the Arcserve Backup database is corrupt before
you complete this task.
You can perform this task with Microsoft SQL Server databases and Microsoft SQL
Server 2008 Express Edition databases.
To re-initialize the Arcserve Backup database
1.
From the Arcserve Backup primary or stand-alone server, start the Server
Configuration Wizard.
Note: To start the Server Configuration Wizard, click Start, point to All Programs,
CA, ARCserve Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens with the Select Options dialog.
2.
3.
4.
5.
In the Select Database dialog, accept the default options and click Next.
A message appears warning you that certain information will not be migrated.
6.
7.
8.
If the Arcserve Backup database is a Microsoft SQL Server 2008 Express Edition
database, continue to the next step.
If the Arcserve Backup database is a Microsoft SQL Server database, the SQL
Database System Account dialog opens. Accept the default options on the SQL
Database System Account dialog and click Next.
In the Select database installation path dialog, ensure that the Overwrite DB option
is enabled.
Note: Enabling this option is essential for re-initializing the database.
Click Next.
The Arcserve Backup database is re-initialized.
9.
Click Finish.
Note: After the re-initialization process is complete, all scheduled jobs in the Job
Queue (for example, the Arcserve database pruning job and the Arcserve database
protection job) will maintain a status of Hold. For the jobs to resume their schedule,
you must change the status of each job from Hold to Ready. To change the job
status, open the Job Status Manager, right-click the jobs and click Ready on the
pop-up menu.
Standard Restore - Backed up in the Arcserve Backup domain that is using the
database--This restore method can be used in the following scenarios:
The Arcserve Backup database was backed up in the Arcserve Backup domain
that is using the database.
You want to restore the Arcserve Backup database to a particular point in time.
Note: You can restore the Arcserve Backup database to its original location or a
different location.
The database was backed up in a Arcserve Backup domain that is different from
the Arcserve Backup domain that is using the database.
You want to restore the Arcserve Backup database to a particular point in time.
Note: For SQL Server 2008 Express installations, you must restore the Arcserve
Backup database to its original location. For SQL Server installations, you can
restore the Arcserve Backup database to its original or a different location.
Recover the Arcserve Backup Database Using Arcserve Database Recovery Wizard
ARCserve Database Recovery Wizard is a self-protection utility that lets you recover the
Arcserve Backup database if it fails and was backed up by the Arcserve Backup domain
that is using the database. Using the wizard you can recover the database from recent
full or differential backups, or recover the database from full backup sessions that are
stored on devices connected to the backup server.
Important! You cannot use ARCserve Database Recovery Wizard to recover a Arcserve
Backup database that was backed up and used in a different Arcserve Backup domain.
To use ARCserve Database Recovery Wizard, ensure that your system meets the
following prerequisite conditions:
Agent for Arcserve Database is installed on the computer that is hosting the
Arcserve Backup database.
You are running this wizard on the primary backup server or a stand-alone backup
server.
The Arcserve Backup Manager Console is not running on the Arcserve Backup
server.
The Arcserve Backup Server Configuration Wizard is not running in the Arcserve
Backup server.
Arcserve ASDB
Arcserve HA
Arcserve Registry
2.
If the Arcserve Backup server is configured as cluster-aware, start the SQL Server
service (ARCSERVE_DB).
3.
From the Windows Start menu, click Start, point to Programs, CA, ARCserve Backup,
and click Database Recovery Wizard.
The Authentication dialog opens.
4.
From the following scenarios, specify the credentials that are required to log in to
the server:
Microsoft SQL Server or Microsoft SQL Server Express Edition is installed on the
same computer as Arcserve Backup--Specify the Windows Domain\Account
and Password for the Arcserve Backup server.
You are using SQL Server authentication--Click SQL Server Authentication and
specify the Login ID and Password that are required to log in to the SQL Server
database.
Click Next.
The Restore Points dialog opens.
Note: The caroot Authentication dialog opens only if you logged in to Arcserve
Backup using a Windows account and then started the ARCserve Database Recovery
Wizard. On the caroot Authentication dialog, enter the password in the caroot
Password field and click OK.
5.
The Restore Points dialog retrieves information about available backup sessions
from the Arcserve Backup database backup log files.
To retrieve more backup sessions, click More Recovery Points.
The Scan Media dialog opens.
To recover the Arcserve Backup database using the sessions that currently appear
on the Restore Points dialog, select the session that you want to recover, click Next,
and go to Step 6.
6.
b.
c.
Specify the session that you want to recover and click Add to List.
The specified Recovery Points appear in the Selected Recovery Points list.
Note: To retrieve more Recovery Points, select a different device and repeat the
Steps b and c.
Additional options:
Eject--Lets you eject tapes and removable hard disk (RDX) media from the
device.
Note: This option functions only on stand-alone tape drives and RDX media
devices.
Refresh--Lets you refresh the backup device list. You must click Refresh after
you insert a new tape or RDX media into the device.
Note: If a backup session spans multiple media, the wizard prompts you to insert
the related media.
Click OK.
The Restore Points dialog opens.
7.
On the Restore Points dialog, select the session that you want to restore and click
Next.
If the specified session is encrypted or contains password protection, the Session
Password dialog opens.
8.
From the Session Password dialog, enter the password in the Password field and
click OK.
The Recovering the ARCserve Database dialog opens and the recovery process
starts.
Important! You will be given three opportunities to provide the correct session
password. If you cannot provide the correct password after three attempts, the
recovery will fail. You must then click Back and repeat Step 5 and specify a different
recovery point.
Note: The Messages field on the Recovering ARCserve Database dialog contains
important information about the results of the recovery. To view detailed
information about the recovery, see the following log file:
ARCSERVE_HOME\Log\ASrecoveryDB.log
9.
10. If the Arcserve Backup server is configured as cluster-aware, bring the following
Arcserve Backup resources back online:
Arcserve ASDB
Arcserve HA
Arcserve Registry
The first job that you run after you recover the Arcserve Backup database appears
in the Job Status Manager with the same Job ID as the restore job for the Arcserve
Backup database. Arcserve Backup demonstrates this behavior because the Job ID
assigned to the Arcserve Backup database restore job is lost after you restore the
Arcserve Backup database.
Note: For more information about ca_recoverdb syntax and options, see Syntax (see
page 633) and Options (see page 634).
Arcserve ASDB
Arcserve HA
Arcserve Registry
2.
3.
Start all Arcserve Backup services using the cstart.bat batch file.
Note: The cstart.bat batch file is stored in the Arcserve Backup home installation
directory.
4.
Execute ca_recoverdb.exe.
Note: For more information see Syntax (see page 633) and Options (see page 634).
5.
Arcserve ASDB
Arcserve HA
Arcserve Registry
Syntax
The ca_recoverdb command line syntax is formatted as follows:
ca_recoverdb [ -cahost <hostname> ]
[-i [n]]
-username <username> [-password <password>]
[-dbusername <database username> [-dbpassword <database password> ] ]
[-sessionpassword [session password] -session password [session password]...]
[-waitForjobstatus <polling interval>]
Options
The ca_recoverdb provides various options for recovering a lost Arcserve Backup
database.
The ca_recoverdb command includes the following options:
cahost <hostname>
Redirects default host from the backup log to the host specified by cahost.
For example:
HostA - The default host that existed in backup log, which will be used in
ca_restore.
HostB - The host that you specify.
In these examples, if you do not specify the cahost switch, then the ca_restore
command invoked by the ca_recoverdb utility will look as follows:
ca_restore -cahost HostA
If you do specify the cahost switch with the parameter HostB, then the ca_restore
command invoked by the ca_recoverdb utility will look as follows:
ca_restore -cahost HostB
-i [n]
Specifies to use the interactive mode. If you include this switch, it allows you to
specify a point in time from which to perform the Arcserve Backup database
recovery by selecting which backup to use as a baseline. When the interactive mode
is invoked, the ca_recoverdb displays the list of Arcserve Backup sequences for
which it has log files. Each of the log files start with a Full database backup, and
contains all of the other backups which are dependent on that Full backup to be
restored (the Full backup is root of the dependency chain for those sessions).
The parameter n is used to specify the number of latest backup log sets
(dependency chains) that you want to select from. The range of values for n is 1 to
99, and the default value is 10.
When you select a Full backup sequence, you will then be prompted to select which
session to use as the restore point. After you select a session, the ca_recoverdb
utility will determine the dependency chain for that sequence, and use ca_restore
to submit a restore job for each session.
If you do not include the -i switch, the ca_recoverdb utility automatically uses the
most recent backup as the specified selection, and builds the dependency chain for
that session. This is helpful if you just want to recover to the latest point in time
backup. However, if the most recent backup is lost or damaged, you can use the
interactive mode to restore from an older session, and then merge tapes to
re-integrate the latest information.
Specify Microsoft SQL Server 2008 Express Edition and Microsoft SQL Server
Database Restore Options
The Agents Restore Options dialog lets you specify how you want to restore Microsoft
SQL Server 2008 Express Edition and Microsoft SQL Server database instances.
To specify Microsoft SQL Server 2008 Express Edition and Microsoft SQL Server
database restore options
1.
From the Quick Start menu in the Navigation Bar on the home page, click Restore.
The Restore Manager window opens.
2.
3.
More information:
Agent Restore Options - Microsoft SQL Server Express Edition - Restore Options (see
page 636)
Agent Restore Options - Microsoft SQL Server Express Edition - Restore Database File
Options (see page 638)
Agent Restore Options - Microsoft SQL Server - Restore Options (see page 638)
Agent Restore Options - Microsoft SQL Server - Database File Options (see page 645)
Agent Restore Options - Microsoft SQL Server Express Edition - Restore Options
Arcserve Backup lets you specify Microsoft SQL Server Express Edition restore options
and the location to restore them.
The Restore Options tab lets you choose how your database is recovered. This tab
contains the following selections:
Arcserve Backup Automatic Selection
Lets you automatically select all required sessions and options. This option is
enabled by default for every restore job and applies selected options appropriately
to the automatically selected sessions.
Miscellaneous
Force restore over existing files or database
Enable this option to let Microsoft SQL Server overwrite files it does not
recognize as part of the database it is restoring. Use this option only if you
receive a message from Microsoft SQL Server prompting you to use the With
Replace option. This option is equivalent to using the With Replace parameter
of the restore command.
Use current ASDB as original location
Enable this option if you want to use current Arcserve Backup database as
original location.
Agent Restore Options - Microsoft SQL Server Express Edition - Restore Database File Options
Arcserve Backup lets you specify Microsoft SQL Server Express Edition restore options
and the location to restore them.
The Restore Database Files tab lets you specify the location to which the database is
recovered. This tab contains the following selections:
Restore to Original Location
Lets you restore the database to its original location, overwriting the current
version.
Database Move Rules
Lets you recover the database to a new drive or directory.
Restored Arcserve
Database
Overwritten Arcserve
Database
Agent Action
Manual Follow-up
The server
information from the
restored Arcserve
Backup database is
not retained.
The session
passwords and user
profiles are not
re-associated.
The server
information from the
restored Arcserve
Backup database is
retained.
Restored Arcserve
Database
Overwritten Arcserve
Database
Agent Action
Manual Follow-up
The server
Note: Before you run the DumpDB utility, you must execute cstop and cstart on all
servers in each domain that uses the overwritten Arcserve Backup database.
For information about using the DumpDB utility, see the Command Line Reference
Guide.
Log point in time restore
Stop before job mark
This option includes date and time fields in which you can set a specific date
and time mark. The option recovers the database to the specified mark but
does not include the transaction that contains the mark. If you do not check the
After datetime check box, recovery stops at the first mark with the specified
name. If you check the After datetime check box, recovery stops at the first
mark with the specified name exactly at or after datetime.
Note: This option is for only Microsoft SQL Server 2000 and SQL Server 2005.
Move to Directory
Select the Move To Directory check box and enter a different directory path in
the field beside.
Filename Pattern Change
Select the Filename Pattern Change check box, to change the filenames for the
entire database, FileGroup, or Transaction Log. Enter a wildcard pattern that
matches the names of the files you want to rename in the field below and
enter the wildcard pattern that you want it to be renamed to in the to field.
For example, if you want to rename all the files that begin with Group as
Members, enter Group* in the field and Member* in the to field.
Note: If you are using a wildcard pattern to rename files, and the pattern for
the original filenames does not match with one or more of the files to which it
would be applied, a yellow indicator will appear at the bottom of the dialog,
and in the tree next to both the affected files and the object where the rule
was applied.
Select the Rename File check box and enter a different file name, to rename a
single file.
Click Apply for the changes to take effect.
The Arcserve database is not functional and the instance hosting the Arcserve
database is functional
In these scenarios you can restore the Arcserve database using the Backup Manager on
the system that backed up the Arcserve database.
Important! You cannot restore the Arcserve database while there are jobs in progress. If
a job tries to access the Arcserve database while the restore is in progress, the job will
fail.
To restore the Arcserve Backup database that was backed up in a different Arcserve
Backup domain
1.
Stop all Arcserve Backup services running on the primary and the member servers
in the domain using the cstop batch file.
Note: For more information, see Stop and Start All Arcserve Backup Services (see
page 493).
2.
Log in to the Arcserve domain containing the backup data for the database that you
want to restore.
Open the Restore Manager window, click the Source tab, select the Restore by Tree
method, expand the Windows Systems object, and browse to the primary server
associated with the database that you want to restore.
Expand the server that you want to restore.
Based on the type of database that is running in your environment, select the
following database objects:
Microsoft SQL Server 2008 Express
Expand the server object and select the following objects:
3.
4.
Select the Operation tab, click the Disable Database Recording option, and click OK.
The database restore options are applied.
5.
Click the Destination tab and select the Restore files to their original location
option.
Important! If the Arcserve Backup database is a Microsoft SQL Server 2008 Express
instance and Arcserve Backup is installed in a cluster-aware environment, you must
place the SQL Server service in cluster maintenance mode before submitting the
restore job.
Click the Submit on the toolbar to submit the restore job.
The Submit Job dialog opens.
Note: If there are jobs in progress, Arcserve Backup prompts you to restore the
Arcserve database to a different location. If you cannot restore the Arcserve
database to a different location, allow all jobs in progress to complete, and then
restore the Arcserve database.
6.
Complete the fields on the Submit Job dialog and click OK.
After the restore job is complete, complete the following tasks:
a.
Start all services on the primary and member servers in the domain using the
cstart command.
Note: For more information, see Stop and Start All Arcserve Backup Services
(see page 493).
b.
c.
After you restore the Arcserve Backup database, the job history for the Database
Protection Job will indicate that the job is incomplete and the Activity Log will
indicate that the job is in progress with an Unknown status. This behavior occurs
because the data for the Activity Log and the Database Protection Job is stored in
the Arcserve Backup database and the data was incomplete while backup was in
progress.
In addition, the status of the Database Protection Job (Done) will be the same as it
was before you submitted the restore job. This behavior occurs because the Job
Queue will obtain the status of the Database Protection Job from the job scripts
rather than from the Arcserve Backup database.
The first job that you run after you recover the Arcserve Backup database appears
in the Job Status Manager with the same Job ID as the restore job for the Arcserve
Backup database. This behavior occurs because the Job ID assigned to the Arcserve
Backup database restore job is lost after you restore the Arcserve Backup database.
Arcserve Backup may attempt to purge data that had already been purged from the
staging device when you restore the Arcserve Backup database in a disk staging
environment. You will receive a warning message, however, the purge job will
complete successfully.
How to Recover the Arcserve Database When the SQL Server Instance Hosting
the Arcserve Database is Not Functional
A typical disaster recovery scenario consists of the following steps:
1.
2.
3.
Reinstall the Agent for Microsoft SQL Server and the Client Agent for Windows, if
necessary. (The Client Agent is needed to restore Microsoft SQL Server Disaster
Recovery Elements.)
4.
If you have a Microsoft SQL Server Disaster Recovery Elements session, restore
it.
If an offline backup or Disaster Recovery Elements backup do not exist and you
do not have the Microsoft SQL rebuildm.exe utility, reinstall the Microsoft SQL
Server or MSDE-based application.
5.
6.
7.
8.
Restore all other databases and transaction logs, except the replication database.
9.
ARCserve Database Recovery Wizard lets you recover the Arcserve Backup database
from the following sources:
Sessions retrieved from ASDBBackups log files. Sessions retrieved from this source
can consist of full, incremental, and differential backups.
Note: ARCserve Database Recovery Wizard does not create jobs that appear in the Job
Queue.
To resolve this problem, whenever Arcserve Backup performs a backup, all the job,
session, and media information is loaded into a database, while a separate catalog file is
also created under the catalog database folder with just the pertinent description
information about each session. In addition, two corresponding catalog index files (.abd
and .abf) are also generated displaying the index tree structure of the directories and
files within the catalog file. These catalog index files are retained on the disk and can be
used to quickly browse the content of the session in the catalog file to locate the
information when needed.
More information:
Configure the Catalog Database (see page 653)
Catalog Browsing
Whenever you need to check for a directory or file to be restored, locate recovery
points, or to just perform a search, instead of querying the content of the entire
database, Arcserve Backup performs the query on just the catalog files with the help of
the catalog index. If this catalog browsing finds the details in the catalog database folder
for a specific session, it will not look in the Arcserve Backup database. However, if it
does not find it, it will then attempt to look in the Arcserve Backup database again. If it
still does not find the details of the session in both the catalog database folder and the
Arcserve Backup database, it will then prompt you to select whether or not you want to
merge the session again so that the merge process can recreate the catalog file into the
catalog database folder or can regenerate the details from the tape session contents
into the Arcserve Backup database.
Note: All application agent sessions except for Microsoft Exchange Server, such as SQL
Server, Informix, Oracle, Microsoft SharePoint Server, Lotus Notes etc, do not support
catalog browsing and the details from those sessions will be inserted into the Arcserve
Backup database.
Open the Server Admin Manager and click the Configuration toolbar button.
The Configuration dialog appears.
2.
3.
Catalog database folder--Lets you define the where you will store the catalog
database. The catalog database folder will contain all the associated catalog
files and catalog index files. You can click the ... (ellipsis) button to browse and
select a different location for the catalog database folder.
By default, the catalog database folder will be stored in on the primary of
stand-alone server in the following directory:
C:\Program Files\CA\ARCserve Backup\CATALOG.DB\
Note: You can only modify the catalog database folder from the Primary
Server.
Minimum disk free space threshold--Lets you specify the minimum percentage
of free disk space when Arcserve Backup deletes catalog files.
Default value: 10 %
Range: 1% to 99%
Note: Arcserve Backup periodically checks the free disk space percentage on
the volume where the catalog database folder is located. If the detected free
space is lower than the specified percentage, a warning message will be sent to
the activity log and it would automatically begin to delete catalog database files
(minimum of 7 days old and starting with the oldest first) from the disk until
the detected free space percentage is greater than the threshold setting.
Example: If the detected free space is lower than the 10%, a warning message
is sent to the activity log and it would automatically begin to delete catalog
database files (minimum of 7 days old and starting with the oldest first) from
the disk until the detected free space percentage is greater than 10%.
4.
Click OK.
The Catalog Database options are applied.
The overall size of the catalog database increases significantly. For example, the size
of the catalog database increased from one GB (gigabyte) to 30 GBs.
More than eight hours are required to complete the Database Protection Job.
More than four hours are required to complete the Database Pruning Job.
The catalog database is consuming a significant amount of disk space on the C:\
drive, which affects the amount disk space required for the Windows pagefile.sys
file.
You cannot export the Arcserve Backup database to a flat file using Microsoft SQL
Server utilities due to the overall size of the database.
You wish to modify your current Arcserve Backup database configuration such that
summary information is recorded in the Arcserve Backup database and detail
information is recorded in the catalog database.
Best Practices
Before you move the Arcserve Backup catalog database to a different location, consider
the following best practices:
If you must move the catalog database, the best practice is to move the catalog
database to a location resides or communicates locally with the Arcserve Backup
server.
Note: You should not move the catalog database to a remote disk that resides on a
Network Attached Storage (NAS) device or a mapped network drive. These
locations may require authentication to access the devices.
The application used for the Arcserve Backup is not relevant to the location of the
catalog database. However, consideration should be given for the protocols used
for communication:
For configurations where the catalog database resides on a SAN device, you should
consider installing an additional SCSI controller or HBA card on the Arcserve Backup
server to accommodate communication between the Arcserve Backup server and
the storage device.
Note: The steps that follow apply to Arcserve Backup servers using Microsoft SQL Server
or Microsoft SQL Server 2008 Express Edition to host the Arcserve Backup database.
To move the Arcserve Backup catalog database to a different location
1.
2.
Ensure that all jobs, including the Database Protection Job and the Database
Pruning Job, are in a Hold state.
Ensure that the Arcserve Backup Manager Console is closed on all servers in the
Arcserve Backup domain, with the exception of the primary or stand-alone
server.
If there are member servers in the Arcserve Backup domain, execute Cstop on all
member servers to stop all Arcserve Backup services.
Note: For information about using Cstop, see Stop and Start All Arcserve Backup
Services Using Batch Files (see page 493).
3.
Execute Cstop on the Arcserve Backup primary or stand-alone server to stop all
Arcserve Backup services.
4.
After all services stop, bring the new location for the catalog database online.
5.
In the new location for the catalog database, create the path.
For example:
F:\ARCserve\catalog.db
6.
Copy all folders from the original location to the new location.
For example:
Original location
C:\Program Files\CA\ARCserve Backup\CATALOG.DB
New location
F:\ARCserve\catalog.db
7.
After you copy the Catalog files to the new location, execute Cstart on the primary
or stand-alone Arcserve Backup server to restart all Arcserve Backup services.
Note: For information about using Cstart, see Stop and Start All Arcserve Backup
Services Using Batch Files (see page 493).
Allow several minutes to elapse to ensure that all Arcserve Backup services start.
8.
9.
Optionally, you can click the ellipsis to browse to the new location for the catalog
database.
Click OK.
The Configuration dialog closes.
10. Submit a simple backup job from the primary or stand-alone server.
11. After the simple backup job is complete, submit a simple restore job from the
primary or stand-alone server.
12. After the simple backup and restore jobs on the primary or stand-alone server are
complete, ensure that Arcserve Backup is writing job summary and detail
information to the new location for the catalog database.
13. If there are members servers in the Arcserve Backup domain, execute Cstart on one
of the member servers. Allow several minutes to elapse to ensure that all Arcserve
Backup services start.
14. Submit a simple backup job from a member server.
15. After the simple backup job is complete, submit a simple restore job from the
member server.
16. After the simple backup and restore jobs on the member server are complete,
ensure that Arcserve Backup is writing job summary and detail information to the
new location for the catalog database on the primary server.
17. Execute Cstart on the remaining member servers in the Arcserve Backup domain.
You should allow five minutes to elapse between Cstart executions to minimize
SAN, LAN, and Arcserve Backup RPC updates.
Note: After you move the catalog database to a different location, restore job and
summary and detail data from the same backup job may not reflect in the catalog
database. To remedy this problem, run Repair Database Connection using the Server
Configuration Wizard. For more information, see Repair the Arcserve Database
Connection on a Primary Server (see page 575).
If you are upgrading to this release and currently running Microsoft SQL Server for
the Arcserve Backup database, you must continue using Microsoft SQL Server for
the Arcserve Backup database.
Arcserve Backup does not support using Microsoft SQL Server 7.0 for the Arcserve
Backup database.
By default, Arcserve Backup creates the Arcserve Backup database (ASDB) using a
simple recovery model. You should retain this model for proper operation.
Microsoft SQL Server supports local and remote communication. This capability lets
you configure the Arcserve Backup database to run locally or remotely to your
Arcserve Backup server.
Note: For more information, see Remote Database Considerations (see page 659).
By default, Arcserve Backup stores information about the backed up files and
directories in the Catalog Database. This behavior causes the Catalog Database to
grow in size at a faster rate than the Arcserve Backup database. Given this behavior
and the needs of your organization, you should plan to have a sufficient amount of
free disk space to support the growth of the Catalog Database.
For Global Dashboard, the Central Primary Server, Arcserve Backup database
(ASDB) must have Microsoft SQL Server 2005 or later installed (does not support
Microsoft SQL Server 2008 Express Edition or Microsoft SQL Server 2000 as its
database).
Note: For a Branch Primary Server, no additional hardware or software is required
beyond the minimum requirements for any Arcserve Backup primary server.
Set the database security mode to SQL security in the SQL Enterprise Manager. This
applies when using SQL security as the authentication mode and the systems that
you want to back up reside inside or outside the Windows domain.
If you specify Microsoft SQL Server 2000, Microsoft SQL Server 2005, Microsoft SQL
Server 2008, or Microsoft SQL Server 2012 as the Arcserve Backup database during
setup, you can use Windows authentication or SQL Server authentication to
communicate with the Microsoft SQL database.
If the Microsoft SQL Server account is changed, you must make the corresponding
changes using the Server Configuration Wizard.
The Arcserve Backup Database Engine periodically polls the status of the Microsoft
SQL Server database. If Microsoft SQL Server does not respond in a timely fashion,
the Database Engine assumes that the Microsoft SQL Server is unavailable and shuts
down (red light). To avoid this situation, you can set the registry key to an
appropriately longer value to increase the wait time for Arcserve Backup Database
Engine, as follows:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Database\MSSQL\SQLLoginTimeout
Arcserve Backup does not support local Microsoft SQL Server installations on
Arcserve Backup servers in NEC CLUSTERPRO environments. In NEC CLUSTERPRO
environments, you must install the Arcserve Backup database instance on a remote
system.
If the ODBC driver is configurable, the System Data Source "ASNT" under System
DSN, in the ODBC Data Source Administrator should have the Client Configuration
set to utilize TCP/IP communication.
There is no organizational requirement and you want to take advantage of the ease
of management that comes with having a single location for the database.
You require a separate server that is not a Arcserve Backup server to function as a
dedicated as a Microsoft SQL Server machine.
To ensure that Arcserve Backup can communicate with the system that is hosting
the Arcserve database instance, you should enable TCP/IP communication between
the SQL Server database instance and the Arcserve server.
Note: For more information, see How to Enable TCP/IP Communication on
Microsoft SQL Server Databases (see page 661).
Important! Microsoft SQL Server 2008 Express Edition does not support remote
database communication.
Open the Windows Control Panel, select Administrative Tools, Data Sources (ODBC),
and System DSN.
2.
3.
Microsoft SQL Server must be installed on the system hosting the Arcserve Backup
database before you start this task.
After you configure Arcserve Backup to use Microsoft SQL Server as the Arcserve
database, the Server Configuration Wizard opens a command utility labeled
exptosql.exe that migrates the core and detail tables from the Microsoft SQL Server
2008 Express database to the newly configured Microsoft SQL Server database.
You can use this procedure to move the Arcserve Backup Microsoft SQL Server
database to a different server.
Note: For more information about using Microsoft SQL Server as the Arcserve Backup
database, see Using Microsoft SQL Server as the Arcserve Backup Database (see
page 658).
From the Windows Start menu, click Start, select All Programs, CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
2.
3.
4.
exptosql.exe core
This is a required step. The core argument lets you migrate the core tables
from the SQL Server 2008 Express database to the SQL Server database.
Important! You must execute this command immediately after the SQL Server
configuration is complete.
b.
exptosql.exe detail
This is an optional step. The detail argument lets you migrate the detail tables
from the SQL Server 2008 Express database to the SQL Server database. You
can execute this command, at any time, after the core migration process is
complete.
Note: Depending on the size of the SQL Server 2008 Express database, the detail
table migration process can require a significant amount of time to complete.
The Server Configuration Wizard lets you change your current Microsoft SQL Server
configuration to the following types of configurations:
Cluster-aware
Remote
Local
To access the new SQL Server installation, you must specify a method of
authentication. You can use one of the following authentication methods:
Windows security
For remote SQL Server installations that use SQL Server authentication, you must
provide the Login ID and Password for the Remote Server Administrator Account.
From the Windows Start menu, click Start, select All Programs, CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
2.
After the configuration is complete, you must install the Arcserve Backup database
protection agent on the system hosting the SQL Server database.
3.
If the SQL Server database is installed on the Arcserve Backup primary server,
open Windows Explorer and browse to the following directory:
C:\Program Files\CA\ARCserve Backup\Packages\ASDBSQLAgent
If the SQL server database is not installed on the Arcserve Backup primary
server, open Windows Explorer and browse to the following directory:
C:\Program Files\CA\ARCserve Backup\Packages\ASDBSQLAgent
Auth Mode
Specify the authentication mode that Arcserve Backup will use to communicate
with and protect the database.
If you specify SQL Authentication as the authentication mode, complete the
following fields:
SQL SA Name
Specify the SQL system account name.
SQL SA Password
Specify the SQL system account password.
6.
Click Install and follow the on-screen instructions to complete the installation.
Configure Microsoft SQL Server 2008 Express as the Arcserve Backup Database
Using the Server Configuration Wizard, you can configure Microsoft SQL Server 2008
Express as the Arcserve Backup database.
Before you configure Microsoft SQL Server 2008 Express as the Arcserve Backup
database, be aware of the following considerations and limitations:
To deploy Microsoft SQL Server 2008 Express in your environment, Microsoft .NET
Framework 2.0 and Microsoft Data Access Components (MDAC) 2.8 Service Pack 2
must be installed on the primary server. If the Server Configuration Wizard does not
detect either of these applications, the wizard installs them for you.
Microsoft SQL Server 2008 Express does not support remote installations. You must
install the Arcserve database on the Arcserve Backup primary server.
You cannot migrate database information from a Microsoft SQL Server database
installation to a Microsoft SQL Server 2008 Express database installation.
To configure Microsoft SQL Server 2008 Express as the Arcserve Backup database
1.
From the Windows Start menu, click Start, select All Programs, CA, ARCserve
Backup, and click Server Configuration Wizard.
The Server Configuration Wizard opens.
2.
3.
Tape Log (see page 668)--Logs all media activity (for debugging purposes only)
Reports Manager (see page 669)--Generates reports from the Arcserve Backup
database for viewing or printing.
Type of job
All child jobs listed under the parent job along with a description
The Activity Log has an organize feature which allows you to sort the log using filters,
message grouping, or message post date. For more information on the Activity Log, see
Customizing Jobs.
Tape Log
The Tape Log contains messages sent by the tape drives to Arcserve Backup. This log is
not generated during normal operation. It is designed for debugging purposes only. To
enable the Tape Log, use the Server Admin Configuration menu.
Note: In a cross-platform environment, the Tape Log does not display information for
non-Windows servers. Only Windows server Tape Engine information is available for
viewing in the GUI.
Job Log
A Job Log is generated for each job that is run by Arcserve Backup. You can specify the
level of detail in the log by choosing the log options before you submit the job. For more
information about the job log, see Customizing Jobs."
Report Manager
The Report Manager provides you with a variety of reports based on the backup activity
stored in the Arcserve Backup database. You can preview a report, print to a printer or
file, as well as schedule when to generate a report.
You can view all Create now-based reports in the Report Manager window or a
browser application, such as Internet Explorer.
You must view all Schedule-based reports in the Report Manager window.
From the Monitor & Reports menu in the Navigation Bar on the home page, click
Report.
The Report Manager opens and a collapsible tree that provides an expandable view
of reports in various categories appears.
2.
On the Report Categories view, select a report template from the list.
The Report template list appears on the right pane.
3.
Select and right-click the report that you want to generate. From the pop-up menu,
specify one of the following options:
Schedule
Lets you schedule a report to run at a specific time.
When you specify this option, the Schedule Report dialog opens. On the
Schedule Report dialog, follow the prompts and complete the required fields to
schedule the report.
Create now
Lets you generate a report that runs now.
When you specify this option, the Create Report dialog opens. On the Create
Report dialog, follow the prompts and complete the required fields to create
the report now.
After Arcserve Backup creates the report, you can view the report results on the
Report Content view pane as illustrated by the following graphic.
Note: The Report Manager also allows you to remove reports using the delete option to
delete the entire report files or delete reports based on date.
Standard
Custom
Advanced
These reports are described in further detail in this section. For a summary listing of
each report and type, see Report Categories (see page 672).
Standard Reports
Arcserve Backup provides several standard reports that display general backup and
restore activity. The reports cover activity for job runs, media backups, and backup
device errors. You can use a report filter to select the backup media you want to include
in the report. Standard reports cannot be customized or scheduled to print at a specific
time interval (not including the Preflight Check Report and GFS Media Prediction
Report).
Note: Arcserve Backup cannot display the Preflight Check Report and the GFS Media
Prediction in the Report Manager when Arcserve Backup generates the reports via a
schedule.
Custom Reports
Custom reports can be modified to meet your specific needs. Although the layout is
similar to standard reports, custom reports are created using templates and saved in
.XML format.
Note: You can adjust the layout of a custom report by modifying the width of the report
columns. Open Windows Notepad and search for the report you want to adjust. Add or
change the WIDTH attribute of the FIELD tag in the report template.
Custom reports can be scheduled to run immediately, at a specified time or repeat
interval, and can be scheduled from the Primary server or a Member server. You can
also specify to have the generated custom report sent to you by email.
Advanced Reports
Advanced reports provide you with an overview of the current data protection status in
your Arcserve environment. Advanced reports are predefined, available in different
types when you install Arcserve Backup, and contain report data headings that you can
modify to suit your specific needs.
To run a report, you must specify the report type and the path of the file where the
generated report will be saved.
Advanced reports are similar to custom reports in that they can be scheduled to run
immediately or at a specified time or repeat interval. You can also elect to have the
generated advanced report sent to you by email.
Report Categories
The report categories that display in Report Manager originate from an external XML
schema file (categories.xml) in the Arcserve Backup home directory. You can change the
display order of the report categories by editing the categories.xml file.
The following table describes the categories, and types available for standard and
custom reports.
Daily Status Reports
This report category provides the status of all jobs executed within the last 24
hours, including reports that display all clients which failed backup and media
written in the last 24 hours.
The following reports are available:
Note: The Daily Backup Status Report contains a field called Compression Ratio. The
compression ratio shows the amount of data actually written to disk after
deduplication. The field is available only for sessions backed up to deduplication
device groups.
Job Reports
This report category shows the status information for report jobs executed on a
weekly basis. It provides reports showing all failed backups and a preflight check
report that displays the status of report jobs scheduled to run at a future date.
The following reports are available:
Media Reports
This report category shows detailed media information about sessions backed up,
including a list of media errors generated. Forecasted media schedules for GFS jobs
are also available.
The following reports are available:
Arcserve Backup for Laptops and Desktops Session Details Report (standard)
Note: The Media Utilization, Session Detail and Session Reports now contain a field
called Compression Ratio for Deduplication. This ratio shows the amount of data
actually written to disk after deduplication. The field is only available for sessions
backed up to deduplication device groups. This field is present through the Report
Manager and also through Report Writer, File, Open, Arcserve Backup Home
Directory, Templates, Reports.
Media Pool Reports
This report category shows detailed media pool related information including the
status of media in scratch sets and GFS rotation profiles.
The following reports are available:
Device Reports
This report category shows information about backup devices used with Arcserve
Backup including the number of errors incurred during a backup on a device.
The following report is available:
Note: The Backup Client Data Size Report now contains a field called Compression
Ratio. This ratio shows the amount of data actually written to disk after
deduplication. The field is only available for sessions backed up to deduplication
device groups. This field is present through the Report Manager and also through
Report Writer, File, Open, Arcserve Backup Home Directory, Templates, Reports.
Resource Usage History Reports
This report category shows forecasted usage information based on historical data.
The following reports are available:
Staging Reports
This report category provides you with information that you can use to analyze and
manage data that was backed up to a file system device using staging.
With Staging Reports you can view status information about migration sessions,
SnapLock sessions, and sessions that did not purge from staging devices. The
Summary report lets you view information about a specific job or a group of jobs
based upon a user-specified range of dates.
The following reports are available:
Statistics Reports
This report category provides an overview of the current data protection status. The
reports include information about the backup and restore status. However, the
output is based on the filter combinations you specify.
The following reports are available:
My Reports
This report category shows user-created reports that are saved in the following
directory:
CA\ARCserve Backup\Templates\Reports
Statistics Reports
The statistics reports can accept and parse a variety of report filters; however, not all
filters are required for all the reports. Based on the type of report that is being
generated, only the filters required and supported by that specified report will be used.
To run any advanced report, you must specify at least the report type and the path to
where the generated report will be saved.
The following report types, along with the corresponding supported filters can be
generated using the statistic report category:
Start Date
End Date
Job Comment
Start Date
End Date
Job Comment
Start Date
End Date
Drive Throughput
This report provides information about the average throughput that is being seen
on the tape drives in the system. Throughput obtained from this report can be
compared against the native throughput of the drive. The output of this report can
be filtered to specific drives by specifying the drive serial number.
Backup Error
This report shows the number of errors and warnings generated for the backup job
for each of the backup paths during the reporting period. This helps in determining
the clients with most number of errors.
Supported Filters:
Start Date
End Date
Job Comment
Start Date
End Date
Job Comment
Start Date
End Date
Partial Backups
This report shows the clients with the most number of partial backups. This reports
help identify and restore critical file.
Supported Filters
Start Date
End Date
Start Date
End Date
None
Vaulting Report
This report shows the list of tapes that will move in or out of the vault on the day of
reporting.
Supported Filters
None
Locate the report you want to schedule from the report list tree.
2.
Click Schedule in the left panel pane next to the report description.
3.
Specify the name and format type (.xml or .csv) for the report.
4.
(Optional) Check the alert option box if you want to be alerted when report is sent
by email and click Next.
5.
Choose schedule options to run the report immediately or at a specific time and
click Next.
6.
Review your selection in the Job Summary page and enter a job description, if
necessary.
7.
Create a report template using the Arcserve Backup Report Writer and save it to a
file.
2.
Locate the Job Scheduler Wizard executable in the Arcserve Backup home directory
and double click to launch it.
3.
Select CAReports in the Run this program combo box and enter the report template
name, the output file name where the report data will be stored, and silent mode
(-s) mode as the parameters.
Note: For a full command line supported by the Report Writer, see the Command Line
Reference Guide.
From the Quick Start menu select Monitor and Reports, and then click Report
Writer.
The Arcserve Backup Report Writer window opens.
2.
Select the File menu and click Open to locate the report you want if you are
generating a Predefined report. Otherwise, if you are generating a User-defined
report, go to Step 3.
3.
Enter a name for your report in the Report Title text box. Optionally, you can enter
a description of your report in the Description text box.
4.
In the Available Queries table, highlight the source from which you want to gather
information for your report. When you highlight a source (such as Media or a Media
Pool), the Available Columns table is populated with the types of data you can
collect from the selected source. For example, if you select Job in the Available
Queries table, you can collect information about the Job Type, the Job Owner, the
Job Start Time, and several other items.
To select an item to include in your report, highlight the item in the Available
Columns table and click Add. The item then moves to the Report Columns table.
Note: You can create reports made up of information collected from multiple
sources. For example, you could create a report that reports on Job Type, Tape
Name, and Source Host.
5.
Click Next to go to the Report Criteria screen. From this screen, you can customize
your report in the following ways:
Set the order of the recordsThe records (or rows) in the columns of your
report can be sorted in either ascending or descending order. By default, the
records are ordered in ascending order.
Set the order of the columnsThe column at the top of the Report Columns list
appears as the first (leftmost) column in your report. To change the position of
a column, highlight it in the Report Columns table and click the up or down
arrow.
Set filtersThe records for your report can be filtered for specific criteria that
you define. Use the Enter Value field, with the Operators and Condition
drop-down menus, to specify the criteria for each type of record (each listing in
the Report Columns table) in your report. After you specify a filter, click Add
Criteria to add it to the Query Criteria table.
For example, to report only on jobs with a Job ID from 150 through 250, follow
these steps:
6.
a.
b.
Set the Operators drop-down menu to >=, type 150 in the Enter Value field,
and set the Condition drop-down menu to and. Then click Add Criteria.
c.
Set the Operators drop-down menu to <= and type 250 in the Enter Value
field. Click Add Criteria. The Query Criteria table then reflects your criteria.
Note: If you are using Report Writer to generate predefined Disk Staging Reports, the
Add and Remove buttons are not accessible.
Universal Agent
Diagnostic Wizard
You can launch the Diagnostic Wizard from the Arcserve Backup program group. It
allows you to configure what kind of report and log you want to generate.
You can run one of the two following report generation modes:
Express Mode--Collects information about the local machine. Does not include
advanced debugging information.
The Diagnostic Wizard also lets you select where to place the log on your hard disk.
After you complete the Diagnostic Wizard, a file is created. You can view this file from
the Diagnostic Report Manager, which is also accessible from the Arcserve Backup
program group.
The following sections describe the process of running and reviewing an Express mode
report.
Note: To run the Diagnostic Wizard in the Advanced mode, choose the Advanced option
on the Select Diagnostic Type screen, and then follow the on-screen instructions.
Ensure that the Remote Registry service is running in the Windows Service
Manager.
2.
Ensure that you allow TCP port 445 to communicate through the Windows firewall
on the Windows operating system.
Open the Diagnostic Wizard by selecting Start, Programs, CA, ARCserve Backup, and
then click Diagnostic Wizard.
The Arcserve Diagnostic Wizard opens.
2.
Click Next.
The Select Diagnostic Type window opens.
From here, you can choose to collect diagnostic logs from either the local server or
a remote server, as well as whether or not you want to include advanced debugging
information in the report.
Choose the Express type to gather local logs without including debugging
information.
3.
Click Next.
Select the attributes of the machine you want to gather logs from.
4.
Click Next.
Specify the location where you want to save the diagnostic information file in the
Diagnostic Information File Name field and click Next.
A summary of the logs to be collected displays.
5.
Click Start.
This process can be lengthy, depending on the system and the amount of
information that you requested.
6.
When the process is complete, click OK, and then click Finish.
After the file has been created, you may be prompted to send it to Arcserve
Technical Support.
Open the Diagnostic Wizard by selecting Start, Programs, CA, ARCserve Backup, and
then Diagnostic Wizard.
The Arcserve Diagnostic Wizard opens.
2.
Click Next.
The Select Diagnostic Type window opens.
From here, you can choose to collect diagnostic logs from either the local server or
a remote server, as well as advanced debugging information in the report.
Choose the Advanced type to gather local logs without including debugging
information.
3.
Click Next.
The Select an Arcserve Backup Job window opens.
Choose an Arcserve job.
4.
Click Next.
Select the attributes of the machine you want to gather logs from.
5.
Click Next.
Select the debug mode.
6.
Click Next.
Specify the location where you want to save the diagnostic information file in the
Diagnostic Information File Name field and click Next.
A summary of the logs to be collected displays.
7.
Click Start.
This process can be lengthy, depending on the system and the amount of
information that you requested.
8.
When the process is complete, click OK, and then click Finish.
After the file has been created, you may be prompted to send it to Arcserve
Technical Support.
Start the Diagnostic Report Manager by selecting Start, Programs, CA, ARCserve
Backup, and then select Diagnostic Report Manager from the Arcserve Backup
program group.
The Diagnostic Report Manager opens.
2.
3.
4.
(Optional) You can also view Product Logs by selecting the Base products and
Options node on the left-hand pane.
The list of all product logs appears on the right-hand pane, together with tape logs
and job logs.
From the File menu on the Diagnostic Report Manager you can also export, save, and
print the selected log file.
If the entire bar is red, the backup of all the nodes in that subnet failed.
If some portion of the bar is yellow, while the rest is green, the backup of some
nodes was incomplete, while the rest were successful.
Click a node to open the details window, which shows the backup information specific
to the selected node. You can check machine information such as CPU, OS and Memory,
as well as check more detailed information by launching related Dashboard Reports. To
launch a Dashboard Report, double-click the item in a group and then open the desired
report.
Filtering--You can filter by node name or tier, including patterns, such as PAY to find
all machines whose names contain PAY. You can save filters on a per-user basis.
Print--You can print out a copy of the full view, not including the mini-map, zoom
slider or toolbar buttons. You can also zoom into a specific area and print it.
Zoom Controls--Using a slide bar, you can enlarge and decrease the display
magnification, changing the Infrastructure Visualization scale.
Some controls on the toolbar are common to all Infrastructure Visualization views, such
as Refresh and Print. Other views have specific toolbars.
Nodes View -- The toolbar contains Group nodes by: Subnet/Agent, Node name
filter and Node tier filter controls.
When the color bar is all one color, the last backup status for all nodes in the group have
the same status. When status differs, the bar is shaded proportionately.
Nodes View
Nodes View is the default view and represents the backup relationship of nodes. It may
be filtered by two radio buttons on the toolbar: Subnet and Agent View.
In Subnet view, the nodes backed up by Arcserve Backup are displayed in subnet
groupings. All servers are shown across the top and all nodes backed up by those
servers are shown grouped by their subnets. Servers with nodes beneath them are
displayed with a summary item and an Expansion symbol (+). Click the symbol to
view subnet groups. On the summary item, there is a status bar that shows total
nodes in percent format based on a pre-defined color scheme, and text details
including Total Node Count, Subnet Group Count and node count for each color
status.
In Agent view, the nodes backed up by Arcserve Backup are grouped by installed
agents. All servers are shown across the top and all nodes backed up by those
servers are shown grouped by the agents installed on that server. When a node has
more than one agent installed, it appears under multiple agent groups. Since last
known backup status is not Agent-specific, the status bar is gray.
Hyper-V
Shows the Microsoft Hyper-V VMs backed up using the Arcserve Backup Agent for
Virtual Machines in the following hierarchy: Backup Server, Hyper-V Host Server,
VM.
Backup status for each VM is represented by text and visual indicators. VMware
ESX/ESXi and Hyper-V servers are displayed similar to Groups and have status bars at
the top to indicate overall backup status of the VMs beneath them. Gray indicates a VM
has not been backed up, which could occur when VMs are populated into the Arcserve
database by the VM data population utility, but not yet backed up.
Connecting lines between a VMware proxy or Hyper-V server and a backup server
indicate that at least one VM under that group was backed up.
Device View
This view lets you see the backup devices connected to the respective Arcserve Backup
server in the Arcserve domain. The devices are grouped by device type.
Click a device to open a Details Window that displays more information about the
device. For example, for Tape Libraries, the Details Window shows the number of drives
and number of slots. Each device type is indicated by icons for file system and
deduplication devices, as well as for tape drives and libraries.
Note: For Arcserve Backup running in a cluster environment, the views display the
information of the currently active node.
Local Mode shows Infrastructure Visualization views for the Central site only.
Note: To check the last update status of data from each branch site, check the Central
Manager interface in the Global Dashboard window. For more information, see the
Arcserve Backup Dashboard Guide.
If the branch site is at version r12.5 and the Central site has been upgraded to the
current release, be aware of the following behavior in Global Visualization:
Virtual Machine view shows only VMs that were backed up.
To launch Infrastructure Visualization, click Monitor & Reports from the Navigation Bar
and then choose Infrastructure Visualization, which loads with the Nodes by Subnet
view by default.
Infrastructure Visualization displays the most recent backup status only. If a particular
node is backed up by more than one server, it is displayed only under the server that
performed the most recent backup. The color bar (see page 689) at the top of each
group provides status at a glance.
Launch the Arcserve Backup Manager and connect to the Primary Server.
2.
3.
Locate the subnet group for which you wish to obtain backup status. In the bar
across the top of the group, you can see the failure percentage of all nodes within
this subnet.
4.
Click the plus sign to expand a group and view further backup details.
5.
6.
Click Related Reports and then choose a report item to launch. From the report, you
can determine the causes of reported errors for troubleshooting purposes.
Group by Subnet--Subnet Group shows all servers, all nodes backed up by those
servers. By default, nodes are collapsed, but you can expand further to see the list
of subnets and corresponding nodes. If a machine has multiple network cards and is
part of more than one subnet, it appears multiple times.
Note: When grouping by subnet, a Data Mover node is displayed without an IP
address.
Group by Agent--Agent Group shows all servers, all nodes backed up by those
servers according to the agents installed on each machine. If a machine has more
than one agent installed, it appears multiple times.
Note: Click a node to obtain backup details, including links to Dashboard Reports.
Launch Infrastructure Visualization from the Navigation Bar, Monitors & Reports.
Infrastructure Visualization opens in Nodes View (default) with all Arcserve Backup
servers shown across the top. The default grouping is by Subnet.
2.
The group is not expanded by default. Click the + symbol to expand a group and
view further backup details.
The number of nodes is shown, and the name of the backup server and backup
status for each node in the subnet are displayed.
2.
3.
Select the VMware or Hyper-V option to view the virtual machines of the desired
type in your environment.
4.
2.
3.
In the View-Specific toolbar, enter the name of the node you wish to view in the
Node Name field. For example, PAY locates all nodes whose names contain PAY
anywhere in the string.
2.
3.
In the View-Specific toolbar, choose a filter from the Node Tier list:
High Priority
Medium Priority
Low Priority
2.
3.
Domain Reports
Note: Reports that are marked with an asterisk (*) indicate that the report is a
Storage Resource Management (SRM) type of report. SRM reports let you monitor
your entire storage environment at a glance and measure the status of all related
resources.
Volume Report *
Disk Report *
Network Report *
CPU Report *
Memory Report *
OS Report *
License Report
Backup Server Reports (primary servers, member servers, and data mover servers)
You can set up alerts from the following Arcserve Backup managers and utilities:
Backup Manager
Restore Manager
Compare Utility
Purge Utility
Copy Utility
Merge Utility
Count Utility
To select job-related events, open these managers or utilities, click the Options toolbar
button, and then select the Alert tab on the Options dialog.
Job-related events can also be accessed by selecting the Utilities menu and choosing any
of the Utilities menu options. To select non-job related events, in Server Admin click
Config, and then the Alert tab.
After you select events and they appear in the Activity Log, Alert generates notification
messages and sends them to the appropriate recipients. For more information about
selecting the information you want to communicate using Alert, see Backing Up Data
(see page 133) for job-related events, and Administering the Backup Server (see
page 491) for non-job related events.
Alerts can be sent in the following ways:
Windows Event Log--Places event information in the Event logs of local and remote
computers.
SMTP (Simple Mail Transfer Protocol)--Sends email messages using the standard
email protocol on the Internet.
Alert Manager--The Alert Manager is used to configure how Alert sends its
messages and to whom to send them.
Alert Service ([Alert Notification Server] Service)--This service is responsible for the
reception, processing, and distribution of Alert messages.
ALBUILD.DLL--This .DLL acts as the channel between Alert and other applications.
This file should be located in the Alert home directory.
*.CFG--The application profile file is provided by an application. This *.CFG file must
be present in the Windows directory so that Alert can handle messages generated
by an application.
Set Up Alerts
Arcserve Backup provides event-based notification through email, pager, SNMP,
broadcast, event log, or through Unicenter Network and Systems Management views. If
you have Unicenter installed, you can use its Monitoring Agent to monitor the status of
the Arcserve Backup processes and media, and report on the failure of backup jobs.
Example: Alert Notification
You can configure Alert to broadcast a message when a backup job finishes successfully.
To set up Alerts
1.
From the Backup Manager window, click the Options toolbar button.
The Options dialog opens.
2.
3.
Set Up Alerts
4.
5.
Enter a name for the configuration in the Configuration Name field and then click
OK.
Select the Broadcast method, and click the Add button.
The Add Broadcast Recipient dialog opens.
6.
In the Group/Machine field, select your machine from the network, and click Add to
add it to the Recipients field.
Or, if you know the machine name, enter the machine name into the recipient field.
Click OK and click OK again to save the configuration.
7.
From the Methods & Recipients drop-down menu, select the saved configuration.
8.
Select an Event from the Event drop-down menu, and click the Add button.
Now that you have set up Alert, you can proceed with your backup.
Click OK.
Click Submit on the toolbar to submit your job.
The Security and Agent Information dialog appears.
9.
From the Security and Agent Information dialog, select the job you want to run.
If the user name and password do not appear, click the Security button and enter
the appropriate user name and password.
Review the security information and click OK.
The Submit Job dialog screen opens.
10. Enter a description for your backup job (optional), and click OK to submit the job.
Your job, which is now active, appears on the Job Queue tab in the Job Status
window. If the job is active, you can view its status by double-clicking it on the Job
Queue tab to invoke the Job Properties dialog.
When the job finishes, Alert notifies you, using the specified method.
Ports Option
The Ports option contains communication port profiles. Pagers and functions that use
serial port access use these profiles. To configure, right-click Ports and select New Item.
Enter the following information:
Port--The name of the communications port you want the pager message to be
broadcast from.
If you want these settings to apply to any function that uses serial port access, place a
check mark in the Use As Default box. When you are finished configuring port
information, click OK.
Note: Pager options are not supported on Japanese versions of Arcserve Backup.
Broadcast Alerts
You can use Alert broadcasts to communicate information to specific network users or
groups.
To use Broadcast Alerts, you must enable Windows Messenger services on Windows XP
and Windows Server 2003 systems. The Messenger service is disabled by default on
Windows XP and Windows Server 2003 systems.
Note: Windows Vista, Windows Server 2008 and later versions do not support
Messenger services. As a result, Broadcast Alerts is not supported either of these
platforms.
To configure broadcast options, right-click Broadcast and select New Item.
When the Broadcast Recipients page appears, enter or select all machine names in your
network that you want to receive alert messages, and then click Add.
CA Unicenter TNG
You can use CA Unicenter TNG to send messages to the Unicenter TNG console and
World View repository when an alert is generated.
Note: Alert must be running on both the Event Management machine and the
WorldView machine.
To configure CA Unicenter TNG settings, right-click CA Unicenter TNG and select
Unicenter TNG Settings. When the Unicenter TNG Settings dialog appears, enter the
following information:
Event Management Machine--Enter the name of the machine that is running the
Unicenter Event Management console.
TNG World View Machine--Enter the name of the machine that contains the
WorldView repository. If the WorldView machine is the same machine you are
running Alert on, enter the user name and password for access to the Unicenter
TNG repository.
You can also configure the TNG Event Map to set the criteria for Alert specifications in
the Unicenter TNG environment. To do this, expand CA Unicenter TNG, right-click
Critical, Warning, or Informational, and select Edit Item. When the Unicenter TNG Event
Map screen appears, enter the following information:
Severity--Use this option to tailor the severity of the message that is passed from
Alert to TNG. Select the type of alert message that you want to broadcast, Error,
Fatal, Informational, Success, or Warning.
Attribute--Set the message to blink or reverse. The default option sets the message
to the TNG default.
Flags--Select the appropriate check boxes to hold the message or highlight the
message in the console.
Sent to Console--Select the check box to send the alert message to the console.
Event Priority
Description
Informational
Blue
Color
Send to Console
If you want to send error alerts to the Unicenter TNG Console using red text, and have
the object status in the World View repository updated, configure another recipient as
follows:
Event Priority
Description
Critical
Red
Color
Send to Console
Email Notification
You can use Lotus Notes, Microsoft Exchange, or SMTP to send email notification
messages to specific users.
Important! You must install Lotus Notes or Microsoft Exchange Client to set up
configuration data and to send messages. See your Windows manual for instructions on
how to set up your email account.
Lotus Notes
To configure Lotus Notes settings, right-click Lotus Notes and select Lotus Notes
Settings. When the Lotus Notes Settings page appears, enter the following information:
Use Specific Account--If you want Alert to switch to another user ID, place a check
mark in this box and enter information in the following fields:
After you configure Lotus Notes Settings and right-click Lotus Notes, select New Item or
Message Attributes.
If you select New Item, Alert contacts the Lotus Notes server to display the address
book. Select the users to whom you want to send alerts.
If you select Message Attributes, you can attach files to the email alert. Enter a subject,
click Add File to select the file you want to attach, and then click OK.
Microsoft Exchange
To configure Microsoft Exchange settings, right-click and select one of the following:
Message Attributes--If you select this, you can attach files to the email alert. Enter
a subject, click Add File to select the file you want to attach, and then click OK.
MS Exchange Settings--If you select this, the Service Logon Settings dialog appears.
This is the same dialog that appears when you set up a service account. Enter the
domain, user name, and password you want to use with the Alert Service. Make
sure the account and user you enter is an account with Login as Service rights and is
also an account on the Microsoft Exchange Server. If you are running the Microsoft
Exchange Client, you must also enter the name of the server and mailbox. The
mailbox name is case-sensitive and should not be hidden in a folder.
Note: If you are using Microsoft Outlook, right-click your Microsoft Outlook icon and
select Properties. Select Microsoft Exchange Server and click Properties to view the
server and mailbox information you should enter.
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 ID is
included in the message to the pager; therefore, if the number is less than four
digits, use leading zeros.
Message Delay--Enter the number of seconds to wait between the time the
connection is made and the time the alert message is sent.
Note: When sending an alphanumeric page, consult your paging service for proper
modem settings. The Alert service requires the TAP protocol for alphanumeric pages.
Note: Pager options are not supported on Japanese versions of Arcserve Backup.
Right-click SMTP and select SMTP Settings to open the SMTP Settings screen.
2.
Sender Address--The sender name that you want the alert email to display in
mailboxes.
Subject--The subject that you want the alert email to display in mailboxes.
Click OK.
3.
After you configure the SMTP Settings, right-click SMTP, select New Item to open
the SMTP Recipients screen.
4.
Click OK.
SNMP Notification
You can use SNMP to send an SNMP trap to an SNMP manager. Examples of SNMP
managers include HP OpenView, IBM NetView, and CA Unicenter TNG.
To configure SNMP settings, right-click SNMP and select New Item. When the SNMP
Recipient page appears, enter the following information:
IPX--If you select this, enter the 8-byte network address of the machine where
the SNMP manager is located. Next, enter the 12-byte node address of the
machine where the SNMP manager is located. Use this field for Novell
networks.
IP--If you select this, enter the IP address of the machine where the SNMP
manager is located. Use this field if you are running the TCP/IP stack.
Trouble Tickets
You can use Trouble Tickets to communicate information through printed documents.
To configure Trouble Ticket settings, right-click Trouble Ticket and select New Item.
When the Trouble Ticket Recipients page appears, enter the following information:
Header--Enter the information that will appear at the top of each Trouble Ticket.
To select recipients, highlight a printer and click Add. When prompted, enter a user
name and password to connect to the printer device.
In addition to using Trouble Tickets to send printed notification messages, you can also
Trouble Tickets to send job logs. To do this, create a new item and select recipients.
Then, in the Backup Manager, before you submit a job, click the Options icon or, from
the Backup menu, select Options. When the Global Options dialog appears, click the
Alert tab, place a check mark in the Attach Job Log box, and then click OK. After you
submit the job, the job log is sent to the recipients you specified.
Event Priorities
All applications calling Alert specify one of the following event priorities:
Critical
Warning
Informational
Message Testing
To test any of the Alert messaging functions, from the toolbar, select Send Test
Message. You should test each setting after you configure it.
To avoid unnecessary alarm, inform Alert recipients that you are performing a test.
Alert Event Log--Stores every message that Alert generates. It displays the date and
time a particular event occurred, the applications that sent the alert, and the
application that generated the event.
Manage Agents
Manage Agents
Arcserve Backup Central Agent Admin lets you perform agent management tasks such
as modifying agent information, configuring agents, and managing agent services.
Modify Agents
Arcserve Backup Central Agent Admin lets you add, modify, or delete agents, similar to
the Backup Manager.
To modify agents
1.
Open the Arcserve Backup Manager Console. From the Quick Start Menu, select
Administration and click Central Agent Admin.
The Central Agent Admin window opens.
2.
3.
4.
5.
Open the Arcserve Backup Manager Console. From the Quick Start Menu, select
Administration and click Central Agent Admin.
The Central Agent Admin window opens.
2.
3.
4.
5.
(Optional) Select or deselect one or more machines for which you want to apply or
remove the same security settings.
6.
Configure Agents
Open the Arcserve Backup Manager Console. From the Quick Start Menu, select
Administration and click Central Agent Admin.
The Central Agent Admin window opens.
2.
3.
4.
Click Start Service or Stop Service to start or stop the agent services, respectively.
5.
(Optional) Select Start the agent backup service as the system starts, to ensure that
the service starts as soon as the system starts.
2.
Configure Agents
Arcserve Backup Central Agent Admin lets you configure the following Arcserve Backup
agents from a central location:
Configure Agents
To configure agents
1.
Open the Arcserve Backup Manager Console. From the Quick Start Menu, select
Administration and click Central Agent Admin.
The Central Agent Admin window opens.
2.
3.
Select the agent you want to configure and update the settings.
4.
(Optional). Click Apply to Multiple to apply the same settings to multiple agent
machines.
5.
2.
Right-click an agent and select Set Debug Level on the pop-up menu.
The Set Debug Level dialog opens.
3.
Set the appropriate debug level such as Normal, Detail, Debug, or Trace, and click
OK.
The debug level registry settings for the agent is now complete.
Add Computers
Add Computers
Arcserve Backup Central Agent Admin lets you add one or more remote computers in a
manner that is similar to the Backup Manager.
To add computers
1.
Open the Arcserve Backup Manager Console. From the Quick Start Menu, select
Administration and click Central Agent Admin.
The Central Agent Admin window opens.
2.
3.
Complete the required fields on the Add Agent dialog and click Add.
You can now view the added computers in the left pane of the Central Agent
Admin.
Add Nodes
You can use the Add, Import, and Export Nodes feature to add multiple nodes and
agents into the system in either of the following ways:
To add multiple nodes and agents using the user interface
1.
Open the Arcserve Backup Manager Console. From the Quick Start Menu, select
Administration and click Central Agent Admin.
The Central Agent Admin window opens.
2.
3.
Enter the name of a node you want to add and click Add. You can also select one or
more nodes from the left-pane list, and click Add or Add All.
4.
(Optional) Select any node on the left-pane list and click Properties.
The Server Properties dialog appears showing the server details and list of products
installed on that server. Click OK.
Add Nodes
5.
(Optional) Select any node on the right-pane list and click Security.
The Security dialog appears where you can set the user a user name and password
for the node. You can also apply the same user name password to multiple nodes.
Click OK.
6.
Click OK.
You can now view the added nodes and agents in the Central Agent Admin.
To add multiple nodes and agents using a .csv and .txt file
1.
2.
3.
Specify the name of the .csv or .txt file from the user interface.
The node and agent names are imported from the .csv or .txt file and are added
into the system.
4.
Click OK.
You can now view the added nodes and agents in the Central Agent Admin.
Open the Arcserve Backup Manager Console. From the Quick Start Menu, select
Administration and click Central Agent Admin.
The Central Agent Admin window opens.
2.
3.
Right-click an agent log file and click View Log Within Specific Time Range from the
pop-up menu.
The Log Retrieval Configuration dialog appears.
4.
Retrieve log file against error time--Obtains log file information for the
specified start and end times.
2.
3.
Retrieve log file against error time--Obtains log file information for the
specified start and end times.
Specify a destination folder where you want to export or save the log file, and click
OK.
The agent log file is exported to the specified location.
2.
Right-click the agent log file you want to delete and click Delete Selected Log.
3.
CPU usage
Memory usage
Disk throughput
Arcserve Backup lets you enable or disable SRM PKI, specify default or custom values for
the indicators, and generate alert messages when the indicators exceed values that you
specified.
To configure SRM PKI
1.
Open the Arcserve Backup Manager Console. From the Quick Start Menu, select
Administration and click Central Agent Admin.
The Central Agent Admin window opens.
2.
Right-click the Windows Systems node and select Configure SRM PKI.
The Configure SRM PKI dialog opens and the Policy tab appears.
3.
Use Default Policy--Lets you specify the default values for each performance
indicator. To specify custom values for the indicators, clear the checkmark next
to Use Default Policy.
Note: You can view the status of modified threshold values for each agent by
clicking the Broadcasting Status tab.
Enable PKI--Lets Arcserve Backup agents send hourly PKI values to the primary
server for SRM PKI reports.
Note: For more information about SRM PKI reports, see the Dashboard User
Guide.
4.
Make any necessary changes for one or more listed agents in the Policy tab.
5.
6.
On the Configure SRM PKI dialog, click Apply, and then click OK.
The Configure SRM PKI dialog closes and the PKI values are applied.
Open the Arcserve Backup Manager Console. From the Quick Start Menu, select
Administration and click Central Agent Admin.
The Central Agent Admin window opens.
2.
Right-click the Windows System object and select Set SRM Exclude Path.
The Set SRM Exclude Path dialog appears.
3.
4.
(Optional) You can add or delete one or more paths using Add or Delete.
Note: The Top Nodes with Most Unchanged Files dashboard report uses the SRM
exclude path list to determine which files must be excluded when you generate the
report. The report excludes all files in the SRM exclude paths that you specify in the
Central Agent Admin.
The node assignments for each tier can be reconfigured and customized to meet your
individual needs by using the Node Tier Configuration dialog, which is accessed from the
Arcserve Backup Server Admin or from the Backup Manager (right-click Windows
Systems in Source tab) or from the Central Agent Admin (right-click Windows Systems).
To configure node tiers
1.
Right-click the Windows Systems object, and select Node Tier Configuration.
The Node Tier Configuration dialog opens, displaying the nodes assigned to each
Tier category (High Priority, Medium Priority, Low Priority).
2.
Select one or more nodes that you want to reassign to a different tier category and
click on the corresponding arrow icon to move the selected nodes from one tier to
another.
Note: Multiple nodes can be selected for tier assignment by using the "CTRL" or
"SHIFT" key combinations.
3.
Click the single arrow icon to move only the selected nodes.
Click the double arrow icon to move all the node in the tier.
4.
Select the computer from where you can open the Arcserve Backup Manager
Console under the Windows Systems object and expand the computer to view the
details.
5.
Click Connections.
The connection details of that computer appear on the right pane.
Select any computer under the Windows Systems object and expand the computer
to view the details.
2.
Right-click the Universal Agent and select Set Debug Level from the pop-up menu.
The Configure Debug Level dialog appears.
3.
Select a debug level such as Normal, Detail, Debug, or Trace, and click OK.
You have now configured the debug level for that computer.
1.
Select any computer under the Windows Systems object and expand the computer
to view the details.
2.
Right-click the Universal Agent and select Disable SRM Client to disable the SRM
client. If the SRM Client is disabled, select Enable SRM Client to enable to it.
3.
Click OK to confirm that you want to enable or disable the SRM client.
Arcserve Backup scans incoming data and segments it into chunks. This process
occurs in the SIS layer of the Tape Engine.
Arcserve Backup executes a hashing algorithm that assigns a unique value to each
chunk of data and saves those values to a hash file.
Arcserve Backup compares hash values. When duplicates are found, data is written
to disk only once, and a reference is added to a reference file pointing back to the
storage location of the first identified instance of that data chunk.
In the diagram below, the disk space needed to backup this data stream is smaller in a
deduplication backup job than in a regular backup job.
With deduplication, three files are created for every backup session:
Reference files--count hashes and store the address in the data files that
correspond to each hash.
Data files--store the unique instances of the data you backed up.
The two index files together consume a small percentage of the total data store so the
size of the drive that stores these files is not as critical as its speed. Consider a solid state
disk or similar device with excellent seek times for this purpose.
Arcserve Backup compares new hash values to previous values, looking for
duplicates. When duplicates are found, data is not written to disk. Instead, the
reference file is updated with the storage location of the original instance of the
data chunk.
Note: Use Optimization for better throughputs and decreased CPU usage. With
Optimization enabled, Arcserve Backup scans file attributes, looking for changes at the
file header level. If no changes were made, the hashing algorithm is not executed on
those files and the files are not copied to disk. The hashing algorithm runs only on files
changed since the last backup. To enable Optimization, select the Allow optimization in
Deduplication Backups option located on the Deduplication Group Configuration screen.
Optimization is supported on Windows volumes only. It is not supported for
stream-based backups, such as SQL VDI, Exchange DB level, Oracle, and VMware Image
level backups.
When you must restore deduplicated data, Arcserve Backup refers to the index files to
first identify and then find each chunk of data needed to reassemble the original data
stream.
Deduplication Considerations
Deduplication Considerations
Some data deduplication characteristics and considerations are as follows:
You can specify a data deduplication device as the destination in a regular backup
job.
You can specify a data deduplication device as the staging device, the final
destination device, or both. However, you cannot choose the same deduplication
device for both staging and final destinations.
Deduplication Considerations
You can specify different retention schedules for different jobs that all use the same
deduplication device.
You can specify a purge policy for final destination when using a deduplication
device. This is not possible using a normal FSD.
You can specify a GFS rotation to a deduplication device where all full and
incremental/differential backups are submitted to the same device, whereas GFS
jobs to an FSD create daily, weekly, and monthly media.
Due to the manner in which AS400 backup session header data is populated, the
deduplication process cannot detect duplicate AS400 backup sessions and
deduplicate the redundant backup sessions.
Due to the manner in which Oracle RMAN backup session header data is populated,
the deduplication process cannot detect duplicate Oracle RMAN backup sessions
and deduplicate the redundant sessions. However, the Global Deduplication
process lets Arcserve Backup examine and handle Oracle RMAN backup sessions.
For more information, see Global Deduplication (see page 752).
As a best practice, when backing up data on servers running Window Server 2012
related to agent backups, (for example, the Agent for Oracle and so on), enable
NTFS Deduplication when you discover that the backup data compression ratios are
lower than expected. When used with Arcserve deduplication, NTFS Deduplication
can provide higher compression ratios of the backup data.
However, when Arcserve backup compression ratios are relatively high (for
example, greater than 70%), using NTFS Deduplication with Arcserve deduplication
may not increase the overall backup compression ratios.
Function
Compression
Supported
1
Not Supported
X
Device Format
Device Erase
Deduplication Considerations
Function
Supported
Encryption
Image Backup
Maximum Threshold
Minimum Threshold
Multistreaming
Multiplexing
Not Supported
Optimization in Deduplication
Scan Jobs
SnapLock
Deduplication devices can be used in disk to disk to tape or disk to tape to tape
(staging) operations. However, to use the staging feature with more than two
streams of backup data, you must license the Arcserve Backup Enterprise Module
(see page 39).
For deduplication, you should upgrade your Windows, UNIX, Linux, and MAC client
agents to Arcserve Backup r12.5 or later.
Note: The client agents for AS400 and Open VMS do not require an upgrade.
To back up deduplication device files, you must license the Arcserve Backup Agent
for Open Files. On Windows 2003, 2008, and 2012 systems, only the license for the
Agent for Open Files is required; the Agent does not need to be installed.
For more information about protecting the deduplication device itself, see How to Back
Up Deduplication Devices (see page 745).
2.
3.
Specify the primary server name, authentication type, user name and password and
then click Next.
4.
Specify the server on which the deduplication device is to be created and click Next.
For local servers (default), you may browse and select a path. If you wish to specify
a remote server, you must have administrator rights to that server and must
manually type the path.
The Disk-based Devices Configuration dialog opens.
5.
Click the entry in the Device Name column to edit it or accept the default.
Click the entry in the Description column to edit it or accept the default.
Click the entry in the Data File Location column to specify a path.
Note: You can specify a path manually or browse for an existing path. To enter
a location for a remote Data File, you must specify the Machine Name or IP
Address, followed by the Share Name. Use the following format:
\\MachineName\ShareName or \\IPAddress\Sharename
Click the entry in the Index File Location column to specify a path. To avoid
errors, use the format specified for the Data File Location to enter a remote
location, or click the arrow to browse for an existing path.
Click the Group Name column and provide a name. If you leave this blank, a
name is automatically provided that you can change in Group Configuration.
This is the name you will select when submitting backup jobs that use
deduplication devices.
Be aware of the following:
The Data File Location and Index File Location fields are empty, by default.
When you create the deduplication device, Arcserve Backup can create the
path that you specify, if it does not exist, or you can browse for a path that
exists.
You should specify different paths for the Index File Location and Data File
Location that are on NTFS volumes, and the locations should not contain
data from other applications. To help you ensure the best performance,
the Index File Location should reside on a disk with a fast seek time, such
as a solid state disk.
You do not need to specify user credentials when the index file location
and the data file location reside on the local computer.
If the index file and the data file reside on different remote computers,
ensure that Arcserve Backup can access the remote computers using the
same set of credentials. You must use this approach because Arcserve
Backup lets you specify only one set of credentials when configuring data
deduplication devices.
Before the backup is done and you reach the end of the data file, increase
the size of the data file by allocating another 1 GB.
The last 1 GB chunk of data is rounded down so that the data file occupies
the actual compressed session size after the deduplication process is
complete.
(Optional) If you specified remote path locations, click Security to provide login
credentials.
The Security dialog opens.
Note: You must clear the Use Arcserve System Account (default) option to enable
the security fields.
Complete the required fields on the Security dialog and click OK.
The Security dialog closes.
7.
8.
Click Next to return to the Welcome to Device Configuration screen or click Exit to
leave Device Configuration.
Important! When you create a deduplication device, the purge policy is automatically
set to four weeks. That default purge policy is inherited by every job you set up for the
device. If you wish to retain backups longer than four weeks, you must adjust the purge
time when you submit the backup job.
More information:
Specify Copy and Purge Policies for Disk Staging Backups (see page 213)
Format--Deletes the sessions from that device and rewrites the header file with a
new tape name
Erase--Deletes the sessions and writes a blank header file on the device
Staging backup job -- Select a deduplication device group as the staging location,
the final backup destination, or both provided you do not select the same
deduplication device group.
Specify local backup options as usual except for Compression and Encryption
options. Deduplication does not support Compression and Encryption. If Arcserve
Backup detects an encrypted session, deduplication is skipped and the job proceeds
as a normal backup job. Refer to the section, Compression and Encryption with
Deduplication (see page 744) for more information.
Choose a deduplication device as the backup destination for a regular backup job.
For more information, see Deduplication Device Management. (see page 395)
Set up a schedule, including GFS rotation, if desired. For more information, see GFS
Rotation Jobs on Deduplication Devices (see page 756).
Specify a purge policy. For more information, see Considerations for Specifying
Deduplication Device Copy and Purge Policies (see page 744).
Note: For information about submitting backup jobs, see Submit a Backup Job (see
page 136),
On the Staging Location tab, select the deduplication device group, enable staging
and specify a staging policy.
On the Destination tab, select a different deduplication device group and specify a
purge policy. If you do not specify a purge policy, the default value of 4 weeks is
inherited from deduplication device creation for full backups, and 2 weeks for
incremental/differential backups.
For more information, see How to Submit a Disk Staging Backup Job.
2.
3.
Click the Staging Location tab and expand the Staging Servers object.
a.
Browse to and select the deduplication group you want to choose as the
staging group for this backup job.
b.
c.
Specify the staging policies for full, differential and incremental backups
required for your job.
Browse to and select the group you wish to use as the final destination for this
backup job.
Note: You may select a regular device group or another deduplication group,
but you may not select the same deduplication group you specified as the
staging destination.
b.
c.
Click the Full Backup tab and specify the purge policy for full backups required
for the job.
d.
Click the Differential/Incremental Backup tab and specify the purge policy for
incremental and differential backups required for the job.
Purge data after -- Specify the number of weeks, days, hours, and minutes
to purge the job session after the operation ends.
Note: Make sure you view the deduplication staging policy because the default
deletion policy is set to four weeks. If you want to retain backups longer than
four weeks, you must manually adjust the policy.
e.
f.
4.
Click the Miscellaneous tab and choose the desired miscellaneous options:
Purge failed sessions from disk--Removes any sessions that fail from the
deduplication device.
Click OK.
Click the Schedule tab and specify the schedule that you want to use for the backup
job.
Note: If you choose Use Rotation Scheme and Enable GFS, the Media Pool fields are
not available for deduplication device groups.
5.
Click the Options button on the toolbar to open the Global Options dialog. Set up
Global Options as usual.
6.
More information:
Global Backup Options (see page 154)
Submit a Backup Job (see page 136)
Specify Copy and Purge Policies for Disk Staging Backups (see page 213)
2.
3.
Click the Staging Location tab and expand the Staging Servers object.
Browse to and select the deduplication group you wish to choose as the staging
group for this backup job.
4.
More information:
Backup Staging Methods (see page 200)
If you use a deduplication device as the destination in a non-staging backup job, you
may configure purge policies. Click Deduplication Policy. The policy is enabled by
default.
Purge cancelled sessions from disk -- Use this option to delete sessions
from the destination device after a backup to destination device is
cancelled.
Purge failed sessions from disk -- Use this option to delete sessions from
the destination device after a backup to destination device fails.
If you use a deduplication device in a staging job as a staging device, you can specify
both copy and purge policies by clicking the Policies tab. For more information, see
Specify Copy and Purge Policies for Disk Staging Backups (see page 213).
In staging jobs where you use deduplication devices for both staging and
destination locations, your jobs will have two purge policies.
Purge policy is always enabled. You cannot disable purge, but you can adjust the purge
schedule.
Staging Location
Final
Destination
Staging Location
Final
Destination
Deduplication device
Deduplication device
Deduplication device
From the Restore Manager, you can view session level compression ratio
information.
From the Backup, Restore or Device Managers, you can view the device/tape level
compression ratios.
From the Report Manager, you can view the session compression ratio from the
Session Details and Session Reports. You can view device level or node level
compression ratio from the Dashboard report.
The compression ratio is the result of the amount of actual data to be stored divided by
the amount of data stored after deduplication expressed as a ratio or as a percentage.
Deduplication device files are normally skipped in local backup jobs (deduplication
device and Arcserve Backup are on the same machine). However, you can forcibly
include them by opening Global Options and enabling "Back up deduplication
device data" on the Operation tab.
To back up deduplication device files, you must license the Agent for Open Files.
For information about how to restore deduplication devices, see Restore Deduplication
Device Files (see page 753).
1.
Ensure that you have licensed the Arcserve Backup Agent for Open Files so that files
in use can still be backed up. If the deduplication device is connected locally to the
backup server, you must issue the license on the backup server.
2.
Ensure that the machine to which the deduplication device is connected supports
VSS.
3.
Select the deduplication data folder and index folder of the device you wish to
back up. If these folders reside on different volumes as recommended, they are
backed up to two different sessions.
Note: Arcserve Backup lets you protect deduplication data when the data files
and the index files reside on different computers. If you are using this
approach, ensure that you specify the proper source nodes on the Backup
Manager, Source tab.
4.
b.
From the Global Options Operation tab, enable Back up deduplication device
data.
c.
From the Global Options Volume Shadow Copy Service tab, enable Use VSS and
disable Revert to traditional backup if VSS fails. If you do not perform this step,
then the backup job automatically enables this option when the backup job
runs.
Save and run the backup job as usual. For more information, see Backing up Data
(see page 133).
Note: The ca_backup command line utility does not support the process of backing up
data that belongs to deduplication devices.
The local server hosting the deduplication device you wish to replicate should be
designated as the Master server.
The server running Windows Server 2003 or later should be designated as the
Replica server.
Note: After you install the Arcserve Replication Engine on both the Master and Replica
servers, you must create and configure a Arcserve Replication scenario for the
deduplication device that you wish to protect. If a deduplication device fails, you can
restore data using the VSS snapshot generated by Arcserve Replication.
1.
From the Arcserve Replication Manager, choose Scenario, New, or click the New
Scenario button from the toolbar to launch the Scenario Creation Wizard.
2.
At the Welcome screen, select Create New Scenario, select an appropriate Group,
and then click Next.
3.
At the Select Server and Product Type screen, select File Server, Replication and
Data Recovery Scenario (DR) and Integrity Testing for Assured Recovery (AR). You
must choose the Integrity Testing for Assured Recovery (AR) option to generate the
VSS Snapshots used for recovering failed deduplication devices. Click Next to
continue.
4.
At the Master and Replica Hosts screen, provide a Scenario Name. For example,
DDD. Enter the Hostname or IP address and Port Number for both Master and
Replica servers. Click Next to continue.
5.
Wait for Engine Verification to complete. If needed, click Install to upgrade the
Engine on one or both servers and then click Next to continue.
6.
At the Master Root Directories screen, select the deduplication device data file
folder and index file folder. Click Next to continue.
7.
At the Replica Root Directories screen, select the data file folder on the Replica
server. Due to the size of the VSS snapshot, we recommend that you put the index
and data files for the deduplication device being replicated on the same volume.
Click Next to continue.
8.
At the Scenario Properties screen, accept the defaults and click Next to continue.
9.
At the Master and Replica Properties screen, accept the defaults and click Next to
continue.
10. Wait for Scenario Verification to complete. If errors or warnings are listed, resolve
them before continuing. Click Next to continue.
11. At the Scenario Run screen, click Finish.
You must complete the Configure Arcserve Replication Scenarios for Deduplication
Devices procedure before you can run the scenario.
From the Arcserve Replication Manager, select the scenario you created to replicate
the deduplication device.
a.
b.
2.
3.
From the Arcserve Replication Manager, select the Master server to which the
deduplication device is locally connected.
a.
b.
Set the Spool, Spool Directory property to a folder on a different hard disk than
the deduplication device. This improves performance.
b.
Set the Scheduled Tasks, Replica Integrity Testing for Assured Recovery, Action
on successful test, Create Shadow Copy (VSS) property to On.
c.
d.
4.
Set the Scheduled Tasks, Replica Integrity Testing for Assured Recovery,
Scheduler property.
2.
3.
From the Arcserve Replication Manager, select the scenario you created to replicate
the deduplication device.
a.
b.
c.
b.
Set the Scheduled Tasks, Replica Integrity Testing for Assured Recovery, Action
on successful test, Create Shadow Copy (VSS) property to On.
4.
5.
Select the Replica server for the deduplication device replication scenario you
created.
b.
Click the Replica Integrity Testing button on the Arcserve Replication Manager
toolbar.
c.
When the Replica Testing for Assured Recovery screen opens, click OK to start.
1.
2.
From the Backup Manager, set up a backup job in the usual manner.
3.
From the Source tab, select the Windows C:\ volume directories of different
machines.
4.
(Optional) If using staging, click the Staging Location tab and select a deduplication
device group.
5.
6.
7.
Browse the node on which the backed up index files are stored
Create a new deduplication device configured to use the restored index and data
folders
Stop and then restart the Tape Engine to ensure that any operations taking place
when the backup was initiated are invalidated
Merge the new deduplication device so that records match the physical device.
Note: The Merge operation may be incomplete or fail if there are active sessions on the
backed up Deduplication device.
1.
2.
Click Snapshot View and select the snapshot from which you wish to restore.
b.
3.
Log on to the Replica server, open the exposed drive, and copy the exposed index
and data files to an alternate location.
4.
From the Arcserve Backup Device Manager, remove the failed deduplication device.
This device must be removed to avoid conflicts in which two devices exist with the
same tapeName, randomID, and sequenceNum.
5.
From the Arcserve Backup Device Manager, create a new deduplication device
using the index and data file paths just copied. For more information, see Create
Deduplication Devices (see page 737).
6.
Stop and restart the Tape Engine to ensure any operations taking place during
backup initiation are invalidated.
7.
Merge the new deduplication device so that the DB tape record is updated to
match the physical deduplication tape. Use the Merge session header only option
from Merge Global Option, Database menu to do so. The Merge operation may be
incomplete or fail if there are active sessions on the backed up Deduplication
device.
You may need to create a new Arcserve Replication scenario to replicate the new
deduplication paths. To use the existing scenario, you can restore the Snapshot to
previous deduplication paths, but you will need to first delete or move any files
presently stored there.
You can scan all data (default) or only session headers, as well as set filter options. You
can specify one node or multiple nodes, separating names with commas in the field
provided. You cannot specify * groups for deduplication Media Assure scan jobs, but
you can specify a * tape in a specific group, or you can select a specific tape. The job
scans the sessions that satisfy your selection criteria and repeats periodically until
deleted.
Note: Media Assure supports scanning only one group and is suspended by other jobs
targeting the same media. If suspended, an error is produced, "E3708 Unable to reserve
group <group name> in <minutes> minutes."
More information:
Media Assure & Scan Utility (see page 32)
With GFS or normal rotation, with Append Media or without Append Media, backup
jobs saved to deduplication devices behave in the same way.
Note: For more information about GFS rotations, see Rotation Schemes (see page 120).
Disk Fragmentation
To reduce disk fragmentation, space is always allocated for the first backup of a given
session in 1 GB increments, until the session ends. If four streams are writing, each
stream uses a pre-allocated chunk of disk space.
The last 1 GB chunk of data is rounded down so that the data file occupies the actual
compressed session size after the deduplication process is complete. This approach
helps to ensure that the disk is fragmented in 1 GB chunks.
This is done only for backups to deduplication devices and only for the first backup of
one root directory on one device.
For second backup and subsequent jobs, the amount of data physically written to disk is
expected to be low.
When the deleted sessions are referenced by other deduplication backup sessions,
the information about the sessions is removed immediately from the Arcserve
Backup database. However, Arcserve Backup cannot reclaim the disk space until the
deleted sessions are not referenced by other deduplication backup sessions.
When the deleted sessions are not referenced by other deduplication backup
sessions, the information about the sessions is removed from the Arcserve
database and the disk space is reclaimed immediately.
From the Quick Start menu on the Arcserve Backup Home Page, click Restore.
2.
3.
4.
Browse to the deduplication device containing the sessions that you want to delete.
Expand the deduplication device to display the deduplication backup sessions
stored on the device.
5.
Deduplication Reports
Deduplication Reports
Arcserve Backup reports have been modified to include deduplication statistics. See
Report Categories (see page 672) for more information.
License for the Arcserve Backup Client Agent for each server on which you want to
use the feature
License for the Arcserve Backup Enterprise Module for each server from which you
want to back up the client agents
Example: Licensing requirements for raw backup of physical disks and volumes
If you want to use the raw backup of physical disks and volumes feature on servers A, B,
and C, you must install a license for the Arcserve Backup Client Agent on all three
servers. In addition, you must register one license for the Enterprise Module on the
backup server from which you back up these three servers.
Chapter 13: Raw Backup and Restore of Physical Disks and Volumes 761
Supported Functions
You can use the following Arcserve Backup functions with raw backup and restore:
Backup estimation
Compression
Encryption
Arcserve Backup does not support performing raw incremental and differential
backups. If you submit such a backup job, Arcserve Backup will automatically
change it to a full backup job.
Arcserve Backup does not execute backups using Volume Shadow Copy Service
(VSS) snapshot technology.
Arcserve Backup does not support the backup and restore of physical disks or
physical volumes for clusters. Therefore, these devices will not be displayed under
the cluster virtual node in the Source tab of the Backup Manager.
Arcserve Backup does not support the backup and restore of physical disks or
physical volumes for removable media. Therefore, these devices will not be
displayed in the Source tab of the Backup Manager.
Backup jobs may fail when Arcserve Backup cannot obtain exclusive access to the
device.
When a dynamic physical disk is restored to another physical disk, Arcserve Backup
does not copy the partition information to the destination physical disk. Therefore,
the volumes and partitions of the source physical disk are not shown on the
destination physical disk after the restore. In other words, you can restore dynamic
disks only to their original location. In addition, if you have multiple dynamic disks,
then you must restore all of these dynamic disks to their original locations to
reinstate the original volume partitioning.
The reason for restoring dynamic disks to their original location is:
The partition table on a dynamic disk does not contain an entry for each volume on
the disk because the volume information is stored in the dynamic disk database.
Each dynamic disk of a system contains a replica of this dynamic disk database. The
location of the database is determined by the partition style of the disk.
On Master Boot Record (MBR) disks, the database is contained in the last 1
megabyte (MB) of the disk.
As a result, unless this database is written to the disk during the restore, the
partition information cannot be restored. For a system with multiple dynamic disks,
all the disks have to be restored to their original locations because each disk
contains a copy of the database, and database copies must be identical to restore
the original partition information.
The physical volumes corresponding to system or boot volumes and the disks on
which these physical volumes reside are not displayed in the Source tab of the
Backup Manager.
The Filter option is not available for raw backup and restore of physical disks and
volumes.
Chapter 13: Raw Backup and Restore of Physical Disks and Volumes 763
PhysicalDisk_<Disk id>:
Indicates a physical disk. <Disk id> represents the identification tag of the disk.
Arcserve Backup and Windows Disk Management display the <Disk id> in the same
way.
PhysicalVolume_<Disk id>_<Volume id>
Indicates a physical volume. <Volume id> is a drive letter or the GUID. The GUID is a
hexadecimal number that displays only when the volume is an unnamed volume
(no drive letter association). For example, PhysicalVolume_Disk 2_E: means that the
volume E: resides on Disk 2.
From the Windows Start menu, click Start, Programs, CA, ARCserve Backup, and
Backup Agent Admin.
The ARCserve Backup Agent Admin window appears.
2.
3.
4.
Click OK.
The raw backup and restore feature is enabled for the agent.
Regular backup--Lets you specify a regular device group as the backup destination.
2.
From the Navigation Bar, click Quick Start, and then click Backup.
The Backup Manager opens.
3.
4.
5.
Click the Source tab and locate the physical disks or volumes that you want to back
up.
6.
Click the Schedule tab and define the schedule for the backup job.
Chapter 13: Raw Backup and Restore of Physical Disks and Volumes 765
7.
(Optional) Click the Staging Location tab and specify a staging device group.
Note: The Staging Location tab displays only when you click the Enable Staging
check box on the Start tab.
8.
(Optional) Click the Policies tab and specify the Tape staging policies and Copy
policies for the job.
Note: The Policies tab displays only when you click the Enable Staging check box on
the Start tab.
9.
Click the Destination tab and select the device group to store the backup data.
2.
From the Navigation Bar, click Quick Start, and then click Restore.
The Restore Manager opens.
3.
4.
5.
Click the Destination tab and select a folder on a physical disk or volume.
Note: The restore destination must not be the same location as the source
directory that you specified on the Source tab.
6.
Click the Schedule tab and define the schedule for the restore job.
7.
2.
From the Navigation Bar, click Quick Start, and then click Restore.
The Restore Manager opens.
3.
4.
5.
6.
Click the Schedule tab and define the schedule for the restore job.
Chapter 13: Raw Backup and Restore of Physical Disks and Volumes 767
7.
2.
From the Navigation Bar, click Quick Start, and then click Restore.
The Restore Manager opens.
3.
Click the Source tab and select the source physical disk or volume.
4.
Click the Destination tab and select a physical disk or volume that is different from
the one you selected as the source.
5.
Click the Schedule tab and select when you want the restore process to start.
6.
2.
3.
4.
Specify the backup settings that you require for your D2D/UDP backups.
Note: For more information about specifying D2D/UDP backup settings, click Help
on the Backup Settings dialog.
From the Backup Manager, select the Start (see page 139), Source (see page 140),
Destination, and Schedule (see page 152) tabs to specify the options that you
require for the job.
Note: To back up the D2D/UDP sessions using multistreaming, on the Destination
tab, click the Multistreaming option and then specify the maximum number of
streams that you want to allow for the job.
2.
Click the Options toolbar button to specify the backup options that are required for
the job. For more information, see Global Backup Options (see page 154).
3.
4.
On the Security and Agent Information dialog, edit or confirm the security and
agent information for your job, and click OK.
5.
When the Submit Job dialog opens, select Run Now to run the job immediately, or
select Run On and select a date and time when you want the job to run.
Note: For more information about the Run Now option, see Job Queue Tab.
6.
7.
If you selected multiple sources to back up and want to set the priority in which the
job sessions initiate, click Source Priority. Use the Top, Up, Down, and Bottom
buttons to change the order in which the jobs are processed. When you finish
setting priorities, click OK.
8.
To save the job as a Arcserve Backup job script, click the Save Job button.
9.
10. To preflight check the job, click the Preflight Check button. If the preflight check
failed, click the Cancel button to modify the job settings.
11. On the Submit Job dialog, click OK.
The job is submitted.
From the Backup Manager, click the Start (see page 139) tab and specify the type of
backup job that you want to submit.
2.
Click the Source (see page 140) tab to display the D2D/UDP nodes and proxy
servers.
Specify the proxy servers containing the nodes that you want to back up as
illustrated by the following screen:
3.
Click the Destination tab to specify the location where you want to store the backup
data.
Note: To back up the D2D/UDP sessions using multistreaming, on the Destination
tab, click the Multistreaming option and then specify the maximum number of
streams that you want to allow for the job.
4.
Click the Schedule (see page 152) tab to specify when and the frequency that you
want the job to run.
5.
Click the Options toolbar button to specify the backup options that are required for
the job. For more information, see Global Backup Options (see page 154).
6.
7.
On the Security and Agent Information dialog, edit or confirm the security and
agent information for your job, and click OK.
8.
When the Submit Job dialog opens, select Run Now to run the job immediately, or
select Run On and select a date and time when you want the job to run.
Note: For more information about the Run Now option, see Job Queue Tab.
9.
10. If you selected multiple sources to back up and want to set the priority in which the
job sessions initiate, click Source Priority. Use the Top, Up, Down, and Bottom
buttons to change the order in which the jobs are processed. When you finish
setting priorities, click OK.
11. To save the job as a Arcserve Backup job script, click the Save Job button.
12. To save the job template, click the Save Template button.
13. To preflight check the job, click the Preflight Check button. If the preflight check
failed, click the Cancel button to modify the job settings.
14. On the Submit Job dialog, click OK.
The job is submitted.
2.
3.
Click the check box next to the D2D/UDP Recovery Point Server name.
b.
Right-click the D2D/UDP Recovery Point Server and click Enable Static Backup
on the pop-up menu.
The Static Backup option is applied to the computer, as illustrated by the following
screen:
Note: The Static Backup option remains applied to the specified computer until you
disable this option. You can repeat this step to disable the Enable Static Backup
option.
4.
Click the Schedule tab and specify the schedule that you want to use for the backup
job.
Note: For more information, see Rotation Schemes (see page 307) and Custom
Schedules (see page 318).
5.
6.
Specify the group that you want to use to store the backup data.
The storage group is applied.
7.
8.
9.
2.
3.
4.
Click the Schedule tab and specify the schedule that you want to use for the backup
job.
Note: For more information, see Rotation Schemes (see page 307) and Custom
Schedules (see page 318).
5.
6.
Specify the group that you want to use to store the backup data.
The storage group is applied.
7.
8.
9.
Recover D2D/UDP data that was backed up via D2D/UDP servers at file level
granularity.
Recover D2D/UDP virtual machine data that was backed up via D2D/UDP Central
Host-Based VM Backup proxy servers at file level granularity.
Note: The following steps describe how to submit restore jobs using the Restore by
Session method. The process of restoring D2D/UDP data and D2D/UDP virtual machine
data using the Restore by Tree method is identical to that of all other types of data. For
more information about the Restore by Tree method, see "Restoring Data."
2.
3.
From the Session tree, expand Sessions and locate the D2D/UDP server that you
want to recover.
Expand the server that you want to recover and locate the session from which you
want to recover data at file level granularity.
Next, click the check boxes next to the files, folders, or directories that you want to
recover, as illustrated by the following screen:
4.
5.
Verify that the Restore files to their original locations option is specified and then
click the Schedule tab.
The Schedule options appear.
6.
Specify the Schedule options that you require for the job.
7.
Click Options on the toolbar to specify the global options that you require for the
job.
Note: For more information, see Global Restore Options (see page 271).
8.
9.
If the required media resides on multiple Arcserve Backup servers, click the
drop-down list and specify the backup server that you want to execute the job and
then click OK.
The Session User Name and Password dialog opens.
10. On the Session User Name and Password dialog, edit or confirm the user name and
password that is required to access the sessions and click OK.
The Submit Job dialog opens.
11. Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
Recover D2D/UDP nodes that were backed up via D2D/UDP Recovery Point Servers
at application level granularity.
Arcserve Backup lets you recover Microsoft Exchange Server data only at the
mailbox level. To recover data at message level granularity, recover the data to a
temporary location and then use D2D/UDP to recover at a Granular Recovery
Technology (GRT) level. For more details, see the D2D/UDP user guide.
The following steps describe how to submit restore jobs using the Restore by
Session method. The process of restoring D2D/UDP data nodes using the Restore by
Tree method is identical to that of all other types of data. For more information
about the Restore by Tree method, see "Restoring Data."
2.
Verify that one of the following conditions exist on the D2D/UDP destination server:
3.
4.
From the Session tree, expand Sessions and locate the D2D/UDP node that you
want to recover.
Expand the server that you want to recover and locate the session from which you
want to recover Microsoft database data at application level granularity.
Next, click the check boxes next to the objects that you want to recover, as
illustrated by the following screen:
5.
(Optional) To specify options that affect only this restore job, right-click selected
objects, select Local Options on the pop-up menu and then do either or both of the
following options:
Microsoft SQL Server databases--Complete the following fields on the D2D/UDP
SQL Server Options dialog:
Restore files to their original location--This option lets you restore data to the
original location from where the backup image was captured.
Dump files only--This option lets Arcserve Backup dump the selected Microsoft
SQL database files to the specified folder. In addition, you can specify or
browse to the folder location where the dump file is restored to.
Restore to Original Location--This option lets you restore data to the original
location from where the backup image was captured.
Note: When restoring the logs folder to the original location, the files that are
in the logs folder will be skipped.
Dump files only--This option lets you restore only the dump files. For this
option, Arcserve Backup restores the Microsoft Exchange database file to a
specified folder, and will not bring it online after recovery is complete. You can
then move this file to a different server and mount it to an Exchange server to
view the data that is contained in the file.
Note: When a Recovery Mailbox Database exists and you restore it with the
Dump file only option, it fails.
Replay log on database--This option lets you specify when the database files
are dumped to the destination folder, you can replay and apply all Exchange
transaction log files and commit them to the database file.
Note: This option is not applicable for Microsoft Exchange Server 2003
databases.
Dismount Database--This option lets you dismount the database before you
restore and mounts the database after restored.
Typically before a restore, Microsoft Exchange will perform some checks to
help ensure the following:
For D2D/UDP, these two options are controlled by this "Dismount the
database before restore and mount the database after restore" option.
With this option, D2D/UDP lets you launch the restore process
automatically without any manual operations. (You can also specify to
dismount/mount database manually).
Click OK.
6.
7.
Click the check box next to Restore files to their original locations. With this
option specified, Arcserve Backup restores the data to the location where the
backup was taken.
Clear the check box next to Restore files to their original locations. With this
option specified, you must specify an alternative location. In addition, Arcserve
Backup restores the data to the alternative location using the local restore
options specified for the database.
Example: Machine-A contains the following database:
C:\Program Files\SQL Server\example.dat
With the Restore files to their original locations option specified, Arcserve
Backup restores the database to original path on Machine-A. If you clear the
check box next to Restore files to their original locations, specify Machine-B as
the alternative location, and the local restore option Restore to Original
Location is specified for the database, Arcserve Backup restores the database
to the original path (C:\Program Files\SQL Server\example.dat) on Machine-B.
Click the Schedule tab.
The Schedule options appear.
8.
Specify the Schedule options that you require for the job.
9.
Click Options on the toolbar to specify the global options that you require for the
job.
Note: For more information, see Global Restore Options (see page 271).
2.
3.
Expand the D2D/UDP Servers object and locate the D2D/UDP server that you want
to restore.
Note: If the D2D/UDP server is assigned to a proxy server, expand the D2D/UDP
Proxy Servers object to locate the server.
Right-click the D2D/UDP server that you want to recover, point to D2D Restore, and
click Find Files/Folders to Restore on the pop-up menu.
The Find Files/Folders to Restore dialog opens.
4.
To submit a restore, follow the prompts and complete the required fields on the
Find Files/Folders to Restore dialog.
Note: For more information about how to submit the restore, click Help on the Find
Files/Folders to Restore dialog.
Recover the raw session to a shared folder, network file share, or a device that the
failed server can access while completing the BMR process.
2.
Boot the server that you want to recover using the D2D/UDP BMR media and then
browse to the location where you recovered the raw session. Then follow the
on-screen steps to complete the BMR process.
Note: For information about recovering files and folders and performing BMR on
D2D/UDP servers, see the D2D/UDP documentation.
Arcserve Backup recovers raw sessions using the same directory structure as the
D2D/UDP backup destination.
Example: E:\restore is the alternative location.
Arcserve Backup recovers the catalog files for raw sessions using the following
pattern:
E:\restore\CATALOG\<original session number>\
Arcserve Backup lets you restore raw sessions only to alternative locations; not to
original locations.
The steps listed below describe how to perform the following recoveries:
Note: The following steps describe how to submit restore jobs using the Restore by
Session method. The process of restoring D2D/UDP Agent-based or agentless nodes
using the Restore by Tree method is identical to that of all other types of data. For more
information about the Restore by Tree method, see "Restoring Data."
Follow these steps:
1.
2.
3.
Locate the D2D/UDP server containing the raw session that you want to recover.
On the Destination tab, clear the check box next to Restore files to their original
location(s), and specify the alternative location where you want to recover the data.
Click the Schedule tab.
The Schedule options appear.
5.
Specify the Schedule options that you require for the job.
6.
Click Options on the toolbar to specify the global options that you require for the
job.
Note: For more information, see Global Restore Options (see page 271).
7.
8.
If the required media resides on multiple Arcserve Backup servers, click the
drop-down list and specify the backup server that you want to execute the job and
then click OK.
The Session User Name and Password dialog opens.
9.
On the Session User Name and Password dialog, edit or confirm the user name and
password that is required to access the sessions and click OK.
The Submit Job dialog opens.
10. Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
After the restore job completes, use the sessions that you restored to an alternative
location to recover the D2D/UDP data.
Log in to the D2D/UDP Recovery Point Server and open Windows Registry Editor.
Important! Log in to the D2D/UDP Recovery Point Server when you back up the
node using the D2D/UDP Recovery Point Servers object in the Backup Manager
Source tree.
Note: Using the D2D/UDP Recovery Point Server to perform a backup on a
D2D/UDP nodes, supports generating catalog files, only if the D2D/UDP Recovery
Point Server is available. If the D2D/UDP Recovery Point Server is not available, then
generating the catalog file fails.
2.
3.
4.
Generate catalogs: 1
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP Recovery Point Server 791
Submit Backup Jobs of Arcserve UDP Nodes through the Arcserve UDP Recovery Point Server
From the Backup Manager, click the Start (see page 139) tab and specify the type of
backup job that you want to submit.
2.
Click the Source (see page 140) tab to display the Arcserve UDP nodes and proxy
servers.
Specify the proxy servers containing the nodes that you want to back up as
illustrated by the following screen:
3.
Click the Destination tab to specify the location where you want to store the backup
data.
Note: To back up the Arcserve UDP sessions using multistreaming, on the
Destination tab, click the Multistreaming option and then specify the maximum
number of streams that you want to allow for the job.
4.
Click the Schedule (see page 152) tab to specify when and the frequency that you
want the job to run.
5.
Click the Options toolbar button to specify the backup options that are required for
the job. For more information, see Global Backup Options (see page 154).
6.
On the Security and Agent Information dialog, edit or confirm the security and
agent information for your job, and click OK.
8.
When the Submit Job dialog opens, select Run Now to run the job immediately, or
select Run On and select a date and time when you want the job to run.
Note: For more information about the Run Now option, see Job Queue Tab.
9.
10. If you selected multiple sources to back up and want to set the priority in which the
job sessions initiate, click Source Priority. Use the Top, Up, Down, and Bottom
buttons to change the order in which the jobs are processed. When you finish
setting priorities, click OK.
11. To save the job as a Arcserve Backup job script, click the Save Job button.
12. To save the job template, click the Save Template button.
13. To preflight check the job, click the Preflight Check button. If the preflight check
failed, click the Cancel button to modify the job settings.
14. On the Submit Job dialog, click OK.
The job is submitted.
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP Recovery Point Server 793
2.
3.
Click the check box next to the Arcserve UDP Recovery Point Server name.
b.
Right-click the Arcserve UDP Recovery Point Server and click Enable Static
Backup on the pop-up menu.
The Static Backup option is applied to the computer, as illustrated by the following
screen:
Note: The Static Backup option remains applied to the specified computer until you
disable this option. You can repeat this step to disable the Enable Static Backup
option.
4.
Click the Schedule tab and specify the schedule that you want to use for the backup
job.
Note: For more information, see Rotation Schemes (see page 307) and Custom
Schedules (see page 318).
5.
6.
Specify the group that you want to use to store the backup data.
The storage group is applied.
7.
8.
9.
2.
3.
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP Recovery Point Server 795
4.
Click the Schedule tab and specify the schedule that you want to use for the backup
job.
Note: For more information, see Rotation Schemes (see page 307) and Custom
Schedules (see page 318).
5.
6.
Specify the group that you want to use to store the backup data.
The storage group is applied.
7.
8.
9.
Recover Arcserve UDP data that was backed up via Arcserve UDP Recovery Point
Servers at file level granularity.
Note: The following steps describe how to submit restore jobs using the Restore by
Session method. The process of restoring Arcserve UDP data nodes using the Restore by
Tree method is identical to that of all other types of data. For more information about
the Restore by Tree method, see "Restoring Data."
Follow these steps:
1.
2.
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP Recovery Point Server 797
3.
From the Session tree, expand Sessions and locate the Arcserve UDP nodes that you
want to recover.
Expand the nodes that you want to recover and locate the session from which you
want to recover data at file level granularity.
Next, click the check boxes next to the files, folders, or directories that you want to
recover, as illustrated by the following screen:
4.
5.
Verify that the Restore files to their original locations option is specified and then
click the Schedule tab.
The Schedule options appear.
6.
Specify the Schedule options that you require for the job.
7.
Click Options on the toolbar to specify the global options that you require for the
job.
Note: For more information, see Global Restore Options (see page 271).
8.
9.
If the required media resides on multiple Arcserve Backup servers, click the
drop-down list and specify the backup server that you want to execute the job and
then click OK.
The Session User Name and Password dialog opens.
10. On the Session User Name and Password dialog, edit or confirm the user name and
password that is required to access the sessions and click OK.
If the Arcserve UDP session is protected by a session password then the Arcserve
UDP session password is required. (The Arcserve UDP session password is the
password that was given in the Arcserve UDP Recovery Point Server plan for the
respective Arcserve UDP sessions backed up to tape).
The Submit Job dialog opens.
11. Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
Recover Arcserve UDP nodes that was backed up via Arcserve UDP Recovery Point
Servers at application level granularity.
Arcserve Backup lets you recover Microsoft Exchange Server data only at the
mailbox level. To recover data at message level granularity, recover the data to a
temporary location and then use Arcserve UDP to recover at a Granular Recovery
Technology (GRT) level. For more details, see the Arcserve UDP user guide.
The following steps describe how to submit restore jobs using the Restore by
Session method. The process of restoring Arcserve UDP node data using the Restore
by Tree method is identical to that of all other types of data. For more information
about the Restore by Tree method, see "Restoring Data."
2.
Verify that one of the following conditions exist on the Arcserve UDP destination
server:
The Arcserve UDP service is running on the Arcserve UDP destination server.
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP Recovery Point Server 799
3.
4.
From the Session tree, expand Sessions and locate the Arcserve UDP node that you
want to recover.
Expand the server that you want to recover and locate the session from which you
want to recover Microsoft database data at application level granularity.
Next, click the check boxes next to the objects that you want to recover, as
illustrated by the following screen:
5.
(Optional) To specify options that affect only this restore job, right-click selected
objects, select Local Options on the pop-up menu and then do either or both of the
following options:
Microsoft SQL Server databases--Complete the following fields on the Arcserve
UDP SQL Server Options dialog:
Restore files to their original location--This option lets you restore data to the
original location from where the backup image was captured.
Dump files only--This option lets Arcserve Backup dump the selected Microsoft
SQL database files to the specified folder. In addition, you can specify or
browse to the folder location where the dump file is restored to.
Restore to Original Location--This option lets you restore data to the original
location from where the backup image was captured.
Note: When restoring the logs folder to the original location, the files that are
in the logs folder will be skipped.
Dump files only--This option lets you restore only the dump files. For this
option, Arcserve Backup restores the Microsoft Exchange database file to a
specified folder, and will not bring it online after recovery is complete. You can
then move this file to a different server and mount it to an Exchange server to
view the data that is contained in the file.
Note: When a Recovery Mailbox Database exists and you restore it with the
Dump file only option, it fails.
Replay log on database--This option lets you specify when the database files
are dumped to the destination folder, you can replay and apply all Exchange
transaction log files and commit them to the database file.
Note: This option is not applicable for Microsoft Exchange Server 2003
databases.
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP Recovery Point Server 801
Dismount Database--This option lets you dismount the database before you
restore and mounts the database after restored.
Typically before a restore, Microsoft Exchange will perform some checks to
help ensure the following:
For Arcserve UDP, these two options are controlled by this "Dismount the
database before restore and mount the database after restore" option.
With this option, Arcserve UDP lets you launch the restore process
automatically without any manual operations. (You can also specify to
dismount/mount database manually).
Click OK.
6.
7.
Click the check box next to Restore files to their original locations. With this
option specified, Arcserve Backup restores the data to the location where the
backup was taken.
Clear the check box next to Restore files to their original locations. With this
option specified, you must specify an alternative location. In addition, Arcserve
Backup restores the data to the alternative location using the local restore
options specified for the database.
Example: Machine-A contains the following database:
C:\Program Files\SQL Server\example.dat
With the Restore files to their original locations option specified, Arcserve
Backup restores the database to original path on Machine-A. If you clear the
check box next to Restore files to their original locations, specify Machine-B as
the alternative location, and the local restore option Restore to Original
Location is specified for the database, Arcserve Backup restores the database
to the original path (C:\Program Files\SQL Server\example.dat) on Machine-B.
Click the Schedule tab.
The Schedule options appear.
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP Recovery Point Server 803
8.
Specify the Schedule options that you require for the job.
9.
Click Options on the toolbar to specify the global options that you require for the
job.
Note: For more information, see Global Restore Options (see page 271).
The raw sessions can also be used to perform bare metal recovery (BMR) of Arcserve
UDP servers. Using the raw sessions, the BMR process is a two-phased approach:
1.
Recover the raw session to a shared folder, network file share, or a device that the
failed server can access while completing the BMR process.
2.
Boot the server that you want to recover using the Arcserve UDP BMR media and
then browse to the location where you recovered the raw session. Then follow the
on-screen steps to complete the BMR process.
Note: For information about recovering files and folders and performing BMR on
Arcserve UDP servers, see the Arcserve UDP documentation.
Arcserve Backup recovers raw sessions using the same directory structure as the
Arcserve UDP backup destination.
Example: E:\restore is the alternative location.
Arcserve Backup recovers the catalog files for raw sessions using the following
pattern:
E:\restore\CATALOG\<original session number>\
Arcserve Backup lets you restore raw sessions only to alternative locations; not to
original locations.
The steps listed below describe how to perform the following recoveries:
Note: The following steps describe how to submit restore jobs using the Restore by
Session method. The process of restoring Arcserve UDP Agent-based and agentless
nodes using the Restore by Tree method is identical to that of all other types of data.
For more information about the Restore by Tree method, see "Restoring Data."
Follow these steps:
1.
2.
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP Recovery Point Server 805
3.
Locate the Arcserve UDP server containing the raw session that you want to
recover.
On the Destination tab, clear the check box next to Restore files to their original
location(s), and specify the alternative location where you want to recover the data.
Click the Schedule tab.
The Schedule options appear.
5.
Specify the Schedule options that you require for the job.
6.
Click Options on the toolbar to specify the global options that you require for the
job.
Note: For more information, see Global Restore Options (see page 271).
7.
8.
If the required media resides on multiple Arcserve Backup servers, click the
drop-down list and specify the backup server that you want to execute the job and
then click OK.
The Session User Name and Password dialog opens.
9.
On the Session User Name and Password dialog, edit or confirm the user name and
password that is required to access the sessions and click OK.
The Submit Job dialog opens.
10. Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
After the restore job completes, use the sessions that you restored to an alternative
location to recover the Arcserve UDP data. For information about how to recover
individual Arcserve UDP files and folders, and how to perform BMR operations on
Arcserve UDP servers, see the Arcserve UDP documentation.
Note: For information about recovering files and folders and performing BMR on
Arcserve UDP servers, see the Arcserve UDP documentation.
Log in to the Arcserve UDP Recovery Point Server and open Windows Registry
Editor.
Important! Log in to the Arcserve UDP Recovery Point Server when you back up the
node using the Arcserve UDP Recovery Point Servers object in the Backup Manager
Source tree.
Note: Using the Arcserve UDP Recovery Point Server to perform a backup on a
Arcserve UDP node, supports generating catalog files, only if the Arcserve UDP
Recovery Point Server is available. If the Arcserve UDP Recovery Point Server is not
available, then generating the catalog file fails.
Chapter 15: Backing Up and Recovering Arcserve UDP Nodes from the Arcserve UDP Recovery Point Server 807
2.
3.
4.
Generate catalogs: 1
Generate a real full backup based on the synthetic schedule for data assurance.
Run a real full backup on the next full backup day without waiting for the scheduled
full backup to run.
Submit on demand synthetic full backups without waiting for the scheduled data
synthetic job to run.
Migrate synthetic full backup sessions to tape, cloud, and disk devices using D2D2T.
Use the disaster recovery processes and point-in-time restores to recover data.
Arcserve Backup lets you perform a disaster recovery using a synthetic full backup
session without referring to the previous full or incremental sessions.
Client Agent - All platforms that Arcserve Backup for Windows Client Agent
supports. SFB is only applicable to r16 or higher Windows Client Agents (not
UNIX/Linux).
Server - All platforms that Arcserve Backup server supports. Synthetic full backup is
a 'job type' that you can submit on any Arcserve Backup r16 servers, primary server,
member server, or standalone server.
Note: To perform synthetic full backup jobs, you must install and license Arcserve
Backup Agent for Open Files on the computers that you want to back up.
Generate real full backups that are based on the synthetic schedule for data
assurance.
Run a real full backup on the next full backup day without waiting for the scheduled
full backup to run.
Submit on demand synthetic full backups without waiting for the scheduled data
synthetic job to run.
Migrate synthetic full backup sessions to tape, cloud, and disk devices using D2D2T.
Use the disaster recovery processes and point-in-time restores to recover data.
Arcserve Backup lets you perform a disaster recovery using a synthetic full backup
session without referring to the previous full or incremental sessions.
Note: To include objects in the backup source that resides on servers, you must first
enter the servers into the Client Database. The Arcserve Backup software must be
running to add servers to the database.
You can perform synthetic full backups on the following applications and platforms:
Client Agent - All platforms that Arcserve Backup for Windows Client Agent
supports. SFB is only applicable to r16 or higher Windows Client Agents (not
UNIX/Linux).
Server - All platforms that Arcserve Backup server supports. Synthetic full backup is
a 'job type' that you can submit on any Arcserve Backup r16 servers, primary server,
member server, or standalone server.
The following diagram illustrates how Arcserve Backup creates synthetic full backup
sessions:
SFB is supported only on disk staging and deduplication devices. You can migrate
SFB sessions to tape, cloud, and disk devices with D2D2T.
SFB supports only Arcserve Backup r16 (or higher) Windows client agents. However,
if there are other agents in the backup source in the same job (such as database
agents or pre-r16 Windows client agents), on the day of the synthetic full backup,
Arcserve Backup uses the original scheduled backup method for the other agents.
Arcserve Backup synthesizes only Arcserve Backup r16 (or higher) Windows client
agents.
Detailed information about synthetic full backups can be viewed in the Job Backup
Status Report, Node Backup Status Report, and Total Protection Size Reports on the
Dashboard.
To perform synthetic full backup jobs, you install and license Arcserve Backup Agent
for Open Files on the computers that you want to back up.
The following behavior is expected when you modify a synthetic full backup job:
When you change the values of the encryption or compression options that are
applied to the job, a real full backup job runs on the next day a full backup job
is scheduled to run.
When you change the values of the synthetic backup job schedule or the purge
policies, the purge time for all related sessions is updated. A real full backup job
will not run.
When you add nodes or disks to the synthetic backup job, a real full backup job
runs on only the added nodes and disks. A real full backup job does not run for
the job.
The following behavior is expected when you change the backup destination for a
device (group or tape):
When the destination device for the backup job is to a data deduplication
device, a real full backup job runs on the next day a full backup job is scheduled
to run.
When the destination device for the backup is a file system device or a data
deduplication device with migration to tape and you change the staging
location, a real full backup job runs on the next day a full backup job is
scheduled to run.
When the destination device for the backup is a file system device or a data
deduplication device with migration to tape and you change the destination
tape, the job runs based on the schedule for the job. (A real full backup does
not run the next day that the job is scheduled to run.)
When the job launches, the first execution will be a real full backup and subsequent
backups will be incremental backups. The full session will be the first parent full
session, and subsequent incremental backups execute according to the incremental
backup policy you have defined.
When the last incremental backup job executes, it queries Client Agent for all
changed and unchanged files. After the last incremental backup, the Data Synthetic
job is created.
The Data Synthetic job assembles the last full session (parent session) and
subsequent incremental sessions into one SFB session.
The new SFB session becomes the parent full session for the next SFB job (unless a
real full backup session is executed after the SFB session).
2.
Select either Normal backup or Deduplication backup, and Enable Synthetic Full
Backup.
Note: When you select Normal backup and Enable Synthetic Full Backup, Enable
Staging is selected by default; if you disable the Enable Staging option, you cannot
select the Enable Synthetic Full Backup option.
3.
Select the Source (see page 140), Schedule (see page 152), Policies (see page 815),
and Destination tabs to specify the options that you require for the job. If you
selected a staging job, you must also specify staging location.
4.
Click the Options toolbar button to specify global options that you require for the
job. For more information, see Global Backup Options (see page 154).
5.
6.
Edit or confirm the security and agent information for your job, and click OK.
7.
When the Submit Job dialog opens, select Run Now to run the job immediately, or
select Run On and select a date and time when you want the job to run.
Note: For more information about the Run Now option, see Job Queue Tab.
8.
9.
If you selected multiple sources to back up and want to set the priority in which the
job sessions initiate, click Source Priority. Use the Top, Up, Down, and Bottom
buttons to change the order in which the jobs are processed. When you finish
setting priorities, click OK.
10. To save the job as a Arcserve Backup job script, click the Save Job button.
11. To save the job template, click the Save Template button.
12. To preflight check the job, click the Preflight Check button. If the preflight check
failed, click the Cancel button to modify the job settings.
13. On the Submit Job dialog, click OK.
The job is submitted.
Note: For information about how to use disk staging (D2D2T) and tape staging (D2T2T)
to manage your backup operations, see How Backup to Disk to Tape Works.
2.
3.
Specify the following synthetic schedule and options as required for the job:
Synthetic after backup job
Lets you specify the amount of time in hours and minutes that must elapse
before Arcserve Backup executes a synthetic full backup (not a real full backup)
after the last incremental backup job.
Synthetic Schedule
Lets you specify the synthetic schedule. You specify the number of weeks or
months that elapse before a synthetic full backup is executed, and the day of
the week to execute the synthetic full backup. Based on the schedule type, you
can specify the day of the week and the week of the month to execute the
synthetic full backup.
Do full backup
Lets you specify whether to execute a real full backup (not a synthetic full
backup), and the frequency of this backup.
Note: Specifying a real full backup changes a backup method
(incremental/differential) to a real full backup.
2.
Select Normal backup and Enable Synthetic Full Backup. The Enable Staging option
is selected by default.
3.
When you select Normal backup and Enable Synthetic Full Backup, Enable
Staging is selected by default. This is because synthetic full backup can only be
enabled for Normal Backup with the Enable Staging option. You can migrate
the data to Tape, Cloud, and Disk devices.
When you select Deduplication backup and Enable Synthetic Full Backup,
Enable Staging is not selected by default. This is because synthetic full backup
supports submitting to a deduplication device without the Enable Staging
option. However, you can also submit a synthetic full backup job to a
deduplication device using the Enable Staging option.
Synthetic full backup does not support Unix/Linux Data Mover backup.
4.
Click the Schedule tab, select the Use Rotation Scheme option, and select the
<5-day weekly incremental backup, full backup on Friday> scheme.
Note: No matter what daily backup method you select, it executes an incremental
backup for file system agents except on the first day and on the days that match the
do full backup schedule. On the days that match the do full backup schedule, it
executes a full backup for the file system agents.
5.
Synthetic after backup job: After the last incremental backup job completes, a
data synthetic job will be generated as a run-on job. To avoid multiple jobs
competing for CPU/Disk resources, you can select when to launch the data
synthetic job after the last incremental backup job is complete.
Synthetic Schedule: You can set the schedule for how long to run a data
synthetic job to generate a synthetic full backup session. If this option is not
selected, the synthetic schedule will be set as every one (1) week, which is the
default setting. In this scenario, a data synthetic job will run every Friday. You
can also select the Synthetic Schedule check box to set the Synthetic Schedule
as every n weeks.
Do Full Backup: You can set the schedule for how long to run a traditional full
backup for data assurance.
Ensure the Do Full Backup Schedule is longer than the Synthetic Schedule when you
enable the Do Full Backup option. Otherwise, the data synthetic job may not have a
chance to run. You can check the Detailed SFB Schedule to know when the data
synthetic job will run, when the full backup job will run, and when the incremental
backup job will run.
6.
Click the Staging Location tab and select the staging location for your job.
7.
8.
Click the Destination tab, select tape as your destination, and specify the Media
pool name.
9.
Click the Options toolbar button to specify global options that you require for the
job. For more information, see Global Backup Options (see page 154).
12. Specify the options that you require for the job:
Run Now
Specifies to run the job immediately.
Run On
Lets you specify a date and time when you want the job to run, and enter a
description for your job. The job name for the Synthetic Full Backup will start
with Synthetic Backup:
Source Priority
Lets you specify the priority in which job sessions initiate if you selected
multiple sources to back up. Use the Top, Up, Down, and Bottom buttons to
change the order in which the jobs are processed.
Save Job
Saves the job as a Arcserve Backup job script.
Save Template
Saves the job template.
Preflight Check
Specifies to preflight check the job. If the preflight check fails, click the Cancel
button to modify the job setting.
Note: Similar to a migration job, after the last incremental backup completes, a new
data synthetic job will be created and added into the job queue under the master
job. If the data synthetic job fails, a makeup job will be created and added into the
job queue.
2.
Select Normal backup and Enable Synthetic Full Backup. The Enable Staging option
is selected by default.
3.
When you select Normal backup and Enable Synthetic Full Backup, Enable
Staging is selected by default. This is because synthetic full backup can only be
enabled for Normal backup with the Enable Staging option. You can migrate
the data to Tape, Cloud, and Disk devices.
When you select Deduplication backup and Enable Synthetic Full Backup,
Enable Staging is not selected by default. This is because synthetic full backup
supports submitting to a deduplication device without the Enable Staging
option. However, you can also submit a synthetic full backup job to a
deduplication device using the Enable Staging option.
Synthetic full backup does not support Unix/Linux Data Mover backup.
4.
Click the Schedule tab, select the Use Rotation Scheme option, and select the
<5-day weekly incremental backup, full backup on Friday, with GFS enabled>
scheme:
Note: No matter what daily backup method you select, it executes an incremental
backup for file system agents except on the first day and on the days that match the
do full backup schedule. On the days that match the do full backup schedule, it
executes a full backup for the file system agents.
5.
Synthetic after backup job: After the last incremental backup job completes, a
data synthetic job will be generated as a run-on job. To avoid multiple jobs
competing for CPU/Disk resources, you can select when to launch the data
synthetic job after the last incremental backup job is complete.
Synthetic Schedule: This option is not applicable when Enable GFS is selected.
This means you cannot specify a Synthetic Schedule as n weeks for a GFS job,
and the Synthetic Schedule will be set as every one (1) week. In this scenario,
the data synthetic job will run every Friday.
Do Full Backup: You can set the schedule for how long to run a traditional full
backup for data assurance.
Ensure that the Do Full Backup Schedule is longer than the Synthetic Schedule when
you enable the Do Full Backup option. You can check the Detailed SFB Schedule to
know when the synthetic job will run, when the full backup job will run, and when
the incremental backup job will run.
6.
Click the Staging Location tab and select the staging location for your job.
7.
8.
Click the Destination tab, select tape as your destination, and specify the Media
pool name.
9.
Click the Options toolbar button to specify global options that you require for the
job. For more information, see Global Backup Options (see page 154).
12. Specify the options that you require for the job:
Run Now
Specifies to run the job immediately.
Run On
Lets you specify a date and time when you want the job to run, and enter a
description for your job. The job name for the Synthetic Full Backup will start
with Synthetic Backup:
Source Priority
Lets you specify the priority in which job sessions initiate if you selected
multiple sources to back up. Use the Top, Up, Down, and Bottom buttons to
change the order in which the jobs are processed.
Save Job
Saves the job as a Arcserve Backup job script.
Save Template
Saves the job template.
Preflight Check
Specifies to preflight check the job. If the preflight check fails, click the Cancel
button to modify the job setting.
Note: Similar to a migration job, after the last incremental backup completes, a new
data synthetic job will be created and added into the job queue under the master
job. If the data synthetic job fails, a makeup job will be created and added into the
job queue.
2.
Select Normal backup and Enable Synthetic Full Backup. The Enable Staging option
is selected by default.
When you select Normal backup and Enable Synthetic Full Backup, Enable
Staging is selected by default. This is because synthetic full backup can only be
enabled for Normal backup with the Enable Staging option. You can migrate
the data to Tape, Cloud, and Disk devices.
When you select Deduplication backup and Enable Synthetic Full Backup,
Enable Staging is not selected by default. This is because synthetic full backup
supports submitting to a deduplication device without the Enable Staging
option. However, you can also submit a synthetic full backup job to a
deduplication device using the Enable Staging option.
Synthetic full backup does not support Unix/Linux Data Mover backup.
3.
4.
Click the Schedule tab, select the Custom Schedule option, and specify the Repeat
Method.
Note: No matter what daily backup method you select, it executes an incremental
backup for the file system agents except on the first day and on the days that match
the do full backup schedule. On the days that match the do full backup schedule, it
executes a full backup for the file system agents.
5.
Synthetic after backup job: After the last incremental backup job completes, a
data synthetic job will be generated as a run-on job. To avoid multiple jobs
competing for CPU/Disk resources, you can select when to launch the data
synthetic job after the last incremental backup job is complete.
Synthetic Schedule: You can set the Synthetic Schedule for how long to run a
synthetic job to generate a synthetic full backup session. If this option is not
selected, the Synthetic Schedule will be set as every one (1) day, which is the
default setting. In this scenario, the data synthetic job will run after the
incremental backup is completed on every backup day. You can also select the
Synthetic Schedule check box to set the Synthetic Schedule as n weeks.
Do Full Backup: You can set the schedule for how long to run a traditional full
backup for data assurance.
Ensure that the Do Full Backup Schedule is longer than the Synthetic Schedule when
you enable Do Full Backup. Otherwise, the data synthetic job may not have a
chance to run. You can check the detailed SFB Schedule to know when the synthetic
job will run, when the full backup job will run, and when the incremental backup job
will run.
6.
Click the Staging Location tab and select the staging location for your job.
7.
8.
Click the Destination tab, select tape as your destination, and specify the Media
pool name.
9.
Click the Options toolbar button to specify global options that you require for the
job. For more information, see Global Backup Options (see page 154).
12. Specify the options that you require for the job:
Run Now
Specifies to run the job immediately.
Run On
Lets you specify a date and time when you want the job to run, and enter a
description for your job. The job name for the Synthetic Full Backup will start
with Synthetic Backup:
Source Priority
Lets you specify the priority in which job sessions initiate if you selected
multiple sources to back up. Use the Top, Up, Down, and Bottom buttons to
change the order in which the jobs are processed.
Save Job
Saves the job as a Arcserve Backup job script.
Save Template
Saves the job template.
Preflight Check
Specifies to preflight check the job. If the preflight check fails, click the Cancel
button to modify the job setting.
Note: Similar to a migration job, after the last incremental backup completes, a new
data synthetic job will be created and added into the job queue under the master
job. If the data synthetic job fails, a makeup job will be created and added into the
job queue.
Open the Job Status Manager and click the Job Queue tab.
2.
Right-click the synthetic job that you want to convert and select the option Run real
full on next full day.
A real full backup will be executed on the next full backup day. The next full backup
day is the day that will execute a full backup based on the original schedule, not the
synthetic schedule.
For example, on a Monday, you submit a 5-day weekly incremental backup, full backup
on Friday rotation SFB job with a synthetic schedule every 4 weeks, and you right-click
the job and select the option Run real full on next full day on the first Thursday,
Arcserve Backup will run a real full backup on the first Friday.
Similarly, if you modify a SFB job, it will also run a real full backup on the next full
backup day.
Open the Job Status Manager and click the Job Queue tab.
2.
Right-click the synthetic job that you want to run immediately and select Synthesize
Now.
The synthetic job is submitted.
2.
Select the tape that contains the Synthetic Full Backup sessions and click Media
Assure.
3.
Select the Enable Media Assure and Scan Synthetic Full Backup session only options,
and click OK.
4.
Click Submit.
The media assure job is submitted. The job scans all of the Synthetic Full Backup
sessions on the tape that were not scanned previously.
How the Purge Policy and a DB Pruning Job Works for Synthetic Full Backup
How the Purge Policy and a DB Pruning Job Works for Synthetic
Full Backup
Tape data, ASDB information, and the Catalog file of sessions pending synthesization
cannot be purged by the job engine and a DB pruning job. It will use the following
algorithm to get a minimum data retention time for the session that is pending
synthesization:
MAX( MIN( Synthetic Cycle Time * 2, Real Full Cycle Time ), Session Retain Time in
Purge Policy )
This ensures there is always at least one full backup (regardless if it is a real full backup
or synthetic full backup) session and all subsequent incremental sessions. Because
Arcserve Backup will not prune catalog files for these sessions, the CATALOG.DB folder
may use disk space, the size of which depends on your backup sources and purge policy.
Arcserve Backup treats one full backup (regardless if it is a real full backup or synthetic
full backup) session and all subsequent incremental sessions as a unique session set that
will be used for the next synthetic job. Therefore, the full backup session and all
subsequent incremental sessions will have the same purge policy even if you have set a
different purge policy for full backups and incremental backups. Arcserve Backup
calculates the purge time for the full session only and applies the same purge time for
all subsequent incremental sessions.
You can determine the purge time for synthetic related sessions by viewing the master
job log in the activity log.
2.
3.
Note: When the Enable Point in Time Restore (PIT restore) option is enabled, no matter
what daily backup method you select, it executes a Point in time incremental backup for
file system agents except on the first day and on the days that match the Do full backup
schedule. On the days that match the Do full backup schedule, it executes a full backup
for file system agents.
The Backup method in the Activity log and the Session method in the Restore by Session
window will be changed from Incremental to Point in time incremental. However,
the Backup method on the Backup GUI is still Incremental.
For the Point in time incremental backup method, the Client Agent will send unchanged
catalog information on the normal incremental day. Then, mergcat.exe will index both
the changed catalog file and the unchanged catalog file to a full file system structure.
After it is indexed, you can do a Point in Time restore job. However, this takes more disk
space and CPU usage.
When the Enable Point in Time Restore (PIT restore) option is disabled, the daily backup
method is Incremental. This is the default setting for a SFB job.
For the Incremental backup method, the Client Agent will not send an unchanged
catalog file on the normal incremental day. The Client Agent will only send unchanged
catalog information on the synthetic day. Mergcat.exe has no chance to index the
unchanged catalog file. This will save disk space and CPU usage.
To submit a Point in Time restore job, you select a node from the source tree and select
a recovery point date, and the related session versions are listed in the Recovery Point
drop-down list. After you select a recovery point, the related session information is
updated in the Tree view and in the List view.
Synthetic full backup only supports r16 Windows Client Agents. It does not support
Windows Client Agents before r16, database agents, or application agents.
However, you can still submit a synthetic full backup job to back up mixed sources
(including r16 Windows Client Agents, pre-r16 Windows Client Agents, database
agents, or application agents). For the agents not supported by synthetic full
backup, it uses the daily backup method you had previously specified.
Synthetic full backup only supports disk-staging devices and deduplication devices.
You can migrate synthetic full backup sessions to tape, cloud, and disk devices with
D2D2T.
Ensure that you define the Do full backup option on the Backup Manager Schedule
tab for data assurance when you submit a synthetic full backup job.
When you modify an existing synthetic full backup job, a traditional full backup runs
the next day that a full backup is scheduled to run. To disable this behavior, modify
the following registry key:
1.
2.
3.
When you submit a synthetic full backup job, the Arcserve Backup user interface
displays your 90-day detailed synthetic schedule for your reference. However, the
detailed synthetic schedule that displays in the user interface may not be consistent
with your actual schedule when you modify existing synthetic full backup jobs.
When you schedule a synthetic full backup job, the Detailed SFB Schedule field
displays the current date as the default start date. However, when you select the
Run On date in the Submit Job screen, the synthetic full backup job is scheduled
based on the day you specify.
With synthetic full backup, you can schedule a synthetic full backup using a
timeframe that is longer than a week. Using this setting, the default retention time
(six days) of the media pool for a rotation scheme cannot prevent overwriting
necessary data. Therefore, when you submit a D2D2T synthetic full backup job with
a rotation scheme and a synthetic schedule of more than a week, verify that the
retention time of the media pool is longer than the synthetic schedule, which will
require more media.
Note: To perform synthetic full backup jobs, you must install and license Arcserve
Backup Agent for Open Files on the computers that you want to back up.
Deduplication backup
Tuesday
Wednesday
Thursday
Friday
Full
Incremental
Incremental
Incremental
Incremental +
Synthetic Full Backup
Full
Incremental
Incremental
Incremental
Full
Full
Incremental
Incremental
Incremental
Full
When I select the GFS scheme, the synthetic schedule is disabled. When will the data
synthetic job launch?
For the Synthetic Full Backup job with GFS scheme, the data synthetic job will be
launched on the full backup day. For example, if you choose the 5-day incremental
backup, Full backup on Friday with GFS enabled scheme, the data synthetic job will be
launched on every Friday. If you choose the 7-day incremental backup, Full backup on
Sunday with GFS enabled scheme, the data synthetic job will be launched on every
Sunday.
If a synthetic full backup job was modified, a real full backup is launched on the next
scheduled full backup day
If the last data synthetic job failed on the synthetic day, a real full backup is
launched on the next synthetic day
If there are no parent full backup sessions found when the data synthetic job
launches on the synthetic day, it will convert the data synthetic job to a real full
backup instead.
You must install and license the option to perform backup operations to libraries
that are shared on a SAN.
You must install the option on the Arcserve Backup Primary server.
Ensure that you have a sufficient number of Storage Area Network (SAN) Option
licenses to support your environment.
The Central Management Option is a prerequisite component for the Storage Area
Network (SAN) Option.
The Storage Area Network (SAN) Option is a count-based license. You must issue
one license for all Arcserve servers that share a library with another Arcserve
server.
Your environment consists of a primary server and three member servers. The
primary server and the three member servers share a multiple drive library on a
SAN. This configuration requires you to issue four Storage Area Network Option
(SAN) licenses issued on the primary server. All servers in the Arcserve domain are
sharing a library.
Your environment consists of a primary server and three member servers. Two
member servers share a multiple drive library and the third member server is
configured with a locally attached, multiple drive library. This configuration requires
you to issue four Tape Library Option licenses and three Storage Area Network
(SAN) Option licenses on the primary server. All servers in the Arcserve domain
have access to a multiple drive library; however, three Arcserve servers are sharing
a library.
Coordinates the use of shared library resources among the servers in the SAN,
preventing conflict if two servers try to allocate a device or media at the same time
You can designate any Arcserve Backup SAN server as the primary SAN server. However,
because the primary SAN server is responsible for managing and initializing the shared
SAN, you should use your most reliable server as the primary SAN server.
The following diagram shows how a SAN is configured with a primary SAN server that
has Arcserve Backup and the SAN option installed:
When a job is ready to run, the option reserves the device and media. Once reserved,
that device and media are no longer available to any other jobs across all SAN servers.
The SAN Option enables Arcserve Backup servers to share one or more tape libraries by
creating a virtual ring. Any backup or restore jobs on a server that has the option
installed run as local jobs. As the backup progresses, Arcserve Backup sends data over
the SAN hardware to the tape libraries for storage instead of over the LAN cabling. This
provides greater speed, reduces network traffic, and maximizes backup and restore
throughput.
Backup Plans
You should plan a backup strategy that is appropriate for your SAN configuration. You
should consider the impact of multiple Arcserve Backup servers sharing a single device.
For example, if your backup device contains two tape drives and there are five option
servers sharing the media libraries, you should not schedule five backup jobs to begin
simultaneously. This would force the option to determine which two of the five jobs to
begin first. Instead, you should carefully consider and schedule the start times for jobs
to meet your backup strategy and allow you to control the schedule sequence.
Note: Each scheduled backup job waits in the queue until a tape drive is available to
perform the backup.
Improved Backup and Restore Speed--Eliminates the need for remote backups
through your Local Area Network (LAN).
Terminology
The following terms are commonly used in a SAN environment:
Storage Area Network (SAN)--A high-speed network designed for sharing attached
tape libraries.
SAN server group--A group of Arcserve Backup servers that can share a set of tape
libraries on a Storage Area Network.
Primary SAN server--The Arcserve Backup server that initializes the shared tape
libraries and is responsible for controlling usage and detecting any changes in status
of these devices.
Installation Prerequisites
Before you install the SAN Option, verify the following prerequisites:
Note: Arcserve Backup supports libraries configured with one drive. If your library has
more than one drive, you must license the Arcserve Backup Tape Library Option to
enable multi-drive capabilities.
Your system requirements meet the minimum requirements needed to install the
option. For more information about installation requirements, see the
Implementation Guide.
Your system meets the minimum hardware and software requirements needed to
install Arcserve Backup and the Arcserve Backup Tape Library Option (if necessary).
You have installed all appropriate SAN hardware device drivers for adapters to
access the devices attached to the Fibre Channel adapter.
Note: For information about the SAN hardware and drivers, see the Arcserve
Backup for Windows Certified Device List. You can access the Certified Device List
from the Arcserve Backup home page.
You have Arcserve Backup and the Central Management Option installed on the
computer on which you want to install the option. In addition, if you have a
multi-drive library you must also have the Tape Library Option installed. This
computer can be either a local computer or a remote computer.
Note: If these applications are not already installed, you must install them when
you install the SAN Option.
These options (Central Management Option, SAN Option, and Tape Library
Option) are all installed on the Primary server only.
There is license count for the Primary server and each SAN member server.
There is one Central Management Option license for the entire SAN, and one
SAN and Tape Library Option license for each server in the SAN (Primary server
and all associated SAN member servers.)
You know the user names, passwords and IP addresses for the primary SAN server
and SAN-attached member servers.
You have all SAN hardware and related device drivers installed.
The Windows backup server identifies all of the appropriate SAN devices, including
the medium changer and tape drives.
All SAN servers in your storage area network can communicate with one another by
pinging each server by name or by pinging their IP address with the display server
name switch.
IP connectivity and name resolution among all servers participating in the SAN is
essential. To ensure you have IP connectivity and name resolution, you may need to
update the IP host file on each server so that the name and IP address of each
server is present in the IP host file of all other servers. The IP host file on each
server resides in \windows\system32\drivers\etc.
You can install the Arcserve Backup base product, agents, and options all in one
session
You can install the Arcserve Backup base product first, and then install the agents
and options separately later.
You can install the Storage Area Network (SAN) Option on the primary SAN server
(only).
Install the server, the option, and the agent in the same installation session.
Use three separate installation sessions; one session to install the server, a second
session to install the option, and a third session to install the agent.
Use two separate installation sessions. When using two separate sessions, you can
group the components in the following ways: Install the server in one session and
the option and agent in a separate session; install the server and option in one
session and the agent in a separate session; or install the server and agent in one
session and the option in a separate session.
Manage devices
Manage media
To start the SAN Configuration utility, access the above directory and then double-click
the file named ELOConfig.exe.
From the Device Manager window, select Configure Groups from the properties
pane.
The Device Group Configuration dialog opens.
2.
Click New.
The New Group dialog opens.
3.
Select the type of device group in the Type field, and enter a name for the device
group in the Name field. Click OK.
The new device group is displayed in the Device Group Configuration dialog.
Device Management
Use the Device Manager to display information about the storage devices connected to
your SAN server group, the media in these devices, and the status of these devices.
Through the Device Manager, you can view all of the shared devices connected to your
SAN server group.
L ib r a r y
P r im a r y S e r v e r
(N o t S h a re d )
M e m b e r S e rv e r
L ib r a r y
(S h a re d )
Each Arcserve Backup SAN Option installed server in the SAN server group displays
the same view of the SAN attached devices.
If you change the device configuration on the primary server (reconfiguring a library
as a RAID, or add more drives to the library for example), you must stop the tape
engine service on all SAN servers (primary and all member), then start the primary
server Tape Engine first. After the primary server Tape Engine is running, you can
then start each of the SAN attached member servers to see the new configuration
correctly.
For more information about managing devices, see Device Manager (see page 395).
Media Management
Consider the following when managing media:
Because SAN servers share media, be careful when selecting media from a scratch
set. Scheduled jobs can be affected if the media is unavailable.
Only one administrator of media pools should supervise the SAN server group.
For more information about media pool management, see Media Pool Manager (see
page 454).
Media Pools
A media pool is a collection of media that is managed as a set and shared in the SAN.
Each media pool is assigned a name, and the media is organized by serial numbers.
Manage media pools from the Arcserve Backup Media Pool Manager window, which
you access by clicking the Media Pool Manager icon.
For more information about media pools, see How Media Pools Work (see page 445).
Report Manager--Generates reports from the Arcserve Backup database for viewing
or printing. You can open the Report Manager from the Quick Access menu and
view reports such as the Job report, Backup Media Error report, Session report,
Backup Device report, and the Media Pool report.
For more information about reporting, see Arcserve Backup Logs and Reports (see
page 667).
You can configure Arcserve virtual libraries for shared Tape Libraries on the primary
server only.
If the device configuration on the primary server changes (for example, you
reconfigure a library into multiple Arcserve virtual libraries), you must stop the tape
engine service on all SAN servers (primary and all member), then start the primary
server Tape Engine first. After the primary server Tape Engine is running, you can
then start each of the SAN attached member servers to see the new configuration
correctly
For more information about Arcserve virtual libraries, see Virtual Library Configuration
Option (see page 380).
Appendix A: Troubleshooting
This section provides troubleshooting information to help you identify and resolve
problems that you may encounter when using Arcserve Backup.
This section contains the following topics:
Log in Problems (see page 857)
Authentication Problems (see page 865)
Backup and Restore Problems (see page 874)
Media Problems (see page 885)
SAN Configuration Problems (see page 892)
Cluster-based Backup and Restore Problems (see page 897)
Miscellaneous Problems (see page 900)
Log in Problems
This section contains the following topics:
Unable to Log In After Changing the caroot Password (see page 857)
Makeup Jobs Created When the Media is Full (see page 859)
Unable to Log In to Arcserve Backup After Changing the Computer Name (see page 859)
Arcserve Backup Cannot Communicate after Changing the IP Address of a Arcserve
Backup Server (see page 860)
Log in Problems
Solution:
Your password did not change at the time of setup. There are various reasons for this;
your machine name may have extended characters or you may have a machine name in
a language other than English. If so, run the following debugging authentication
commands (replace AB_MACHINE with your machine name) so that you can send the
logs to Arcserve Customer Support for investigation:
Note: The caroot password can consist of any combination of alphanumeric and special
characters, but may not exceed 15 bytes. A password totaling 15 bytes equates to
approximately 7 to 15 characters.
1.
where AB_MACHINE is your machine. If this does not work, resolve the name to an
IP address by changing the etc/hosts file or on the DNS.
2.
3.
Enter the following command to tell Arcserve Customer Support if the portmapper
is running on your machine:
netstat -na >netstat.log
4.
Enter the following command to let Arcserve Customer Support know which
Arcserve Backup services have registered with the rpc server running on the client
machine:
rpcinfo.exe -p AB_MACHINE >rpcinfo.log
This creates the rpc.log file in the Arcserve Backup home directory under \log.
Log in Problems
Error E3392 (Backup server TCP reconnection timeout) is recorded in the Activity
Log.
Solution:
The remedies for this problem are as follows:
Although the job completed successfully, Error E3392 caused the job to appear to
fail. The Makeup Job was created because Arcserve detected a failed job. In
conclusion, you can safely delete the Makeup Job.
You can increase the time-out waiting period value by modifying the following
registry keys:
HKEY_LOCAL_MACHINE\Software\ComputerAssociates\CA ARCserve
Backup\ClientAgent\Parameters\SendTimeOut
Log in Problems
Solution:
The computer name is a name that your computer uses to identify itself in a network or
a domain. In a centralized management environment, an Arcserve domain can consist of
a primary server and one or more member servers, or a stand-alone server. Arcserve
Backup uses the computer names of the primary server and the member servers to
establish communication between the servers.
For more information about how to process computer name changes in an Arcserve
domain, see How to Process Computer Name Changes in an Arcserve Domain (see
page 542).
The network interface card (NIC) was replaced in a Arcserve Backup server. When
the computer rejoins the network, the IP address is different from that of the
previous network card.
Symptoms
After you change the IP address on a primary server, a stand-alone server, and a system
hosting the Arcserve Backup Manager Console, Arcserve Backup demonstrates the
following behavior:
On a member server and a system hosting the Arcserve Backup Manager Console,
the value of the Domain is "None" in the Default Server and Security fields on the
Manager Console.
Error messages appear when you click the Backup link in the Navigation Bar on the
member server. For example, a pop-up message appears "Connecting to primary
server."
Log in Problems
Pinging the primary server from the Command Line on a member server, returns
the message "Request timed out."
Equivalence errors may occur when you execute a task using a Arcserve Backup
command line utility on the primary server or a stand-alone server. For example,
one of the following messages may appear:
Ntuser not validated in authentication server on Hostname.
Do you want to create equivalence (default : y)?
After you change the IP address on a member server, Arcserve Backup demonstrates
the following behavior:
On a member server, the value of the Domain is "None" in the Default Server and
Security section on the Manager Console.
From the primary server or a system hosting the Arcserve Backup Manager Console,
you cannot log in to the member server.
Pinging a member server from the Command Line on the primary server, returns
the message "Request timed out."
Equivalence errors may occur when you execute a task using a Arcserve Backup
command line utility on a member server. For example, one of the following
messages may appear:
Ntuser not validated in authentication server on Hostname.
Do you want to create equivalence (default : y)?
Log in Problems
Solutions
To remedy the communication problems, use the procedure that corresponds with the
type of Arcserve Backup server where the IP address was changed.
IP Address Changed on the Primary Server or Stand-alone Server
Important! After you change the IP address of a primary server or a stand-alone server,
basic backup jobs and restore jobs from the server itself can complete successfully.
Additionally, the host names of the member servers should display in the Arcserve
Backup managers on the primary server. However, to ensure that you can successfully
complete backup jobs and restore jobs on member servers, you must complete the
modification described in Step 1 on the member server before completing any other
task.
1.
2.
If the Arcserve Backup server is a primary server, stop and restart the Arcserve
Backup services using the following commands:
cstop
cstart
If there are member servers in your Arcserve Backup domain, open the Windows
Command Line the member server.
Execute the ipconfig command using the /flushdns switch. For example:
c:\documents and settings\windows user name>ipconfig /flushdns
Note: You must repeat this step on all member servers in your Arcserve Backup
domain.
3.
Create equivalence on the primary server or stand-alone server using the ca_auth
command. The syntax for this task is as follows:
ca_auth [-cahost HOST-NAME] -equiv add ntuser HOST-NAME ARCserveBackupUser
[caroot_username] [caroot_password]
Note: For more information about using the ca_auth command, see the Command
Line Reference Guide.
IP Address Changed on a Member Server
1.
Create equivalence on the member server using the ca_auth command. The syntax
for this task is as follows:
ca_auth [-cahost HOST-NAME] -equiv add ntuser HOST-NAME ARCserveBackupUser
[caroot_username] [caroot_password]
Note: For more information about using the ca_auth command, see the Command
Line Reference Guide.
2.
Log in Problems
Open the Windows Command Line on the Arcserve Backup server that is backing up
the agent system.
Execute the ipconfig command using the /flushdns switch. For example:
c:\documents and settings\windows user name>ipconfig /flushdns
If you added the agent system to the primary server, a member server, or a
stand-alone server by referencing the IP address rather than the agent system's
host name, you can log in the Arcserve Backup server and manually change the IP
address of the agent system. To do this, complete the following steps:
1.
Log in to the Arcserve Backup server, open the Backup Manager, and expand
the Windows system object.
2.
Right-click the agent system and select Modify Agent from the pop-up menu.
The Agent Option dialog opens.
3.
Specify the new IP address in the IP address field and click OK.
The new IP address is applied to the agent system.
Log in Problems
When you use a static IP address, you can register the new static IP address on the
DNS server. Based on the type of server (for example, a primary server, member
server, and so on), use the ipconfig command task described in the previous
sections to refresh their local DNS client.
This action lets you resolve the cache for establishing a new relationship between
the host name and IP address.
If you do not register the new static IP address with the DNS server, you must
modify the Hosts file on the servers to reflect this change.
To remedy this scenario, do the following:
1.
From Windows Explorer, open the following file using a text editing application
such as Notepad:
C:\WINDOWS\system32\drivers\etc\hosts
2.
Specify the static IP address and host name of the system as illustrated by the
following screen:
3.
Note: When you use this solution, you must modify the Hosts file when you change
the IP address, and delete the specified information when you revert to a dynamic
IP address.
Authentication Problems
Authentication Problems
This section contains the following topics:
Authentication Security Settings (see page 865)
Restricted Users Cannot Access the Activity Log and the Audit Log (see page 867)
Authentication Errors Occur When Stopping and Starting the CAportmapper Service (see
page 870)
Credential Problems with Cloud Connection (see page 870)
Unable to Open Report Writer (see page 871)
Unable to Create Reports from Report Manager (see page 872)
Updating Passwords Using ca_jobsecmgr Does Not Complete Successfully (see page 873)
Ensure that Arcserve Backup has properly authenticated the caroot account. Use
the Server Configuration Wizard to perform this authentication. Select the
Password for Backup Server Logon and Administration option to set the caroot
account and password.
Administrator--Full Control
If you are having general problems understanding what rights your backup account
needs to perform storage functions in your environment, consider the following
information.
If you are backing up only your local Arcserve Backup server, the Arcserve Backup
System account configured at installation has sufficient rights (Administrator and
Backup Operator).
If you are backing up remote data within your domain (through the Client Agent for
Windows or through the network facility of Arcserve Backup), your backup account
requires additional rights. The following is a general outline of common permissions
necessary for a powerful backup account. You can tailor your backup account to
match your needs, and some rights may not be required in your environment.
Authentication Problems
Note: Security requirements for storage-related functions are dependent upon the
resources accessed. Windows security rules and requirements should be considered
at all times.
The backup account should have the following Group Rights:
Administrator
Backup Operator
Note: A user in the Backup Operator Group does not have rights to access the
Arcserve Backup database. As a result, member servers are not visible to the
user in the Backup Manager.
Domain Administrator
Log on Locally
Log on as a service
When prompted by Arcserve Backup to enter security within a domain, always use
domain\username as the context.
The security entered in Arcserve Backup jobs is static and does not update
dynamically if the Windows security account information changes at the operating
system level. If you change the account information packaged in your Arcserve
Backup jobs, you must modify the jobs and repackage them with the proper
security information.
You must back up remote Registry and System State information through the
Arcserve Backup Client Agent for Windows.
If you manually stopped and restarted the CA Remote Procedure Call service
(CASportmap) without using the cstop and cstart command, the service cannot
communicate with its port assignments properly. This can prevent a user account
with caroot equivalence from logging in to the Arcserve Backup domain.
To remedy the inability to log in to the Arcserve Backup domain, run the cstop
command and then run the cstart command. This enables the service to
communicate properly and lets the user account with caroot equivalence log in to
the Arcserve Backup domain.
Authentication Problems
Restricted Users Cannot Access the Activity Log and the Audit Log
Valid on Windows Server 2003, Windows Vista, and Windows Server 2008 systems.
Symptom:
When you log in to Arcserve Backup using Windows authentication and a Windows
account with restricted privileges (for example, Backup Operator and Remote Desktop
User), you cannot access the Arcserve Backup Activity Log and Audit Log.
Note: This behavior does not occur when you configure Arcserve Backup to authenticate
with the Arcserve Backup database using SQL Server authentication.
Solution:
To remedy this behavior, grant all Windows accounts that require access to the Activity
Log and the Audit Log the privilege to connect to SQL Server using Microsoft SQL Server
authentication.
To grant privileges on Microsoft SQL Server 2000
1.
2.
To grant privileges on Microsoft SQL Server 2008 Express Edition and Microsoft SQL
Server 2005 or later
1.
2.
Authentication Problems
3.
Add the restricted Windows accounts into Microsoft SQL Server by doing the
following:
a.
Authentication Problems
b.
Right-click the Arcserve Backup instance and click Properties on the pop-up
menu.
The Login Properties dialog opens as illustrated by the following screen.
c.
d.
In the Users mapped to this logon field, select the databases that you want to
map by click the Map check box.
e.
In the Database role membership for field, select the roles that you want to
apply to this user for the selected database and click OK.
Authentication Problems
You stop the CAportmapper service using either the Net Stop command or by
stopping the service from the Windows Computer Management console.
Important! You must stop and start the CAportmapper Service using the cstop or cstart
command. These commands let you stop and start all Arcserve Backup services
sequentially, based on their dependencies with other Arcserve Backup services.
More information:
Stop and Start All Arcserve Backup Services Using Batch Files (see page 493)
Authentication Problems
Solution:
This problem occurs when you log in to the Arcserve Backup server using a domain user
account that is not a member of an administrative group. If you apply caroot
equivalence to the account, you can open the manager console, however, you cannot
open Report Writer.
The solution to this problem is to allow the domain user account to join an
administrative group. However, if you do not want to allow the user account to join an
administrative group, complete the following alternative solution:
1.
2.
3.
4.
b.
Add the user account and allow Full Control for this key.
c.
Log in to the Arcserve Backup server using the domain user account.
Open the manager console.
Open Report Writer.
Report Writer opens.
Authentication Problems
Solution:
This problem can occur under the following conditions:
The user does not have write access to the specified directory.
To remedy this condition, verify that the user has write permissions to the specified
directory.
Report Manager cannot communicate with the Arcserve Tape Engine, the Arcserve
Database Engine, or both.
To remedy this condition, verify that the Tape Engine service and the Database
Engine service are running on the backup server.
Authentication Problems
2.
Open the Backup Manager and click the Source tab to display the source directory
tree.
3.
From the Backup menu, click Source Context Menu and then click Security to open
the Security dialog.
4.
Complete the required information on the Security dialog and click OK.
5.
(Optional) For the jobs that are not scheduled, resubmit the failed jobs.
MS Error Code
SHARING VIOLATION
ACCESS DENIED
Cause: A target file for the backup job was not accessible,
or another process (such as an application service) was
using a target file when Arcserve Backup ran the backup
job.
Resolution: Ensure that your user account has sufficient
rights to access the target file, and stop all services and
applications using the target file before restarting the
backup job.
MS Error Code
Citrix 4.0
Solution:
When you restore a Citrix 4.0 server, the job may fail because the Microsoft SQL Server
instance hosting the Citrix database instance will not start after the restore job is
complete.
To remedy this problem, restart the Citrix database instance manually.
2.
Select the files being restored that failed, set the destination, and submit a new
restore job.
Arcserve Backup Does Not Restore Data Based on File Access Time
Valid on Windows platforms.
Symptom:
Arcserve Backup does not restore data when filtered based on the last file access time.
Solution:
Using the Restore Manager and the ca_restore command line utility, you can recover
files based on the last time they were accessed. However, Arcserve Backup does not
store the last file access time in the backup records. As a result, Arcserve Backup cannot
restore data based on the last file access time.
The remedy for this problem is to modify the registry key listed below on the agent
computer and then submit the backups.
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe
Backup\ClientAgent\Parameters\FileAccessTimeFlag
Value: 1
Scheduled Backup Jobs Fail After Changing the Login Credentials for Agent
Computers
Valid on all operating systems.
Symptom:
Scheduled backup jobs fail after you change the login credentials (User name, Password,
or both) for agent computers.
Solution:
This is expected behavior.
Arcserve Backup stores information about the login credentials for agent computers in
the Arcserve Backup database. As a scheduled backup job runs, Arcserve Backup
retrieves the login credentials from the database, which allows Arcserve Backup to log in
to the agent and process the scheduled backup job. If you change the login credentials
for an agent computer without updating the database, Arcserve Backup cannot log in to
the agent to process the job, which causes the job to fail.
As a best practice, you should update the Arcserve Backup database with the new login
credentials immediately after you change the login credentials on your agent
computers.
To update the Arcserve Backup database with the new login credentials, do the
following:
1.
2.
3.
Specify the new User name, Password, or both that is required to log in to the agent
computer and click OK.
The Security dialog closes and the Arcserve Backup database is updated with the
current login credentials for the agent computer.
Cannot submit synthetic job since this job has been modified
The synthetic full backup job was modified and no real full backup and incremental
job is done.
2.
Unable to submit the data synthetic job, or there are no sessions that need to be
synthesized
The synthetic full backup job cannot synthesize full sessions because there are no
suitable sessions that can be synthesized. This can occur due to two possible
scenarios:
Sessions were already synthesized before this job was submitted, so there is no
need to synthesize them again.
3.
4.
Even though there were some sessions that were synthesized to full sessions, some
of the sessions were either skipped or failed. This can occur due to two possible
scenarios:
Sessions were already synthesized before this job was submitted, so there is no
need to synthesize them again.
Solution:
1.
No action is required for this message. It will do a real full backup on the next
synthetic day.
2.
If you have any sessions that failed, verify the previous incremental session and
make any necessary adjustments to ensure a successful backup.
3.
4.
If you have any sessions that failed, verify the previous incremental session and
make any necessary adjustments to ensure a successful backup.
Arcserve D2D Backup Jobs Fail When Submitted from the Backup Manager
Valid on Windows Platforms.
Symptom:
When you submit Arcserve D2D backups from the Backup Manager, the jobs fail when
the source data includes Arcserve D2D sessions that were backed up previously by
Arcserve Backup. Error message AW0813 appears in the Activity Log.
Solution:
This is expected behavior. If a backup job consists of Arcserve D2D sessions that were
backed up previously, Arcserve Backup fails the job and reports error message AW0813
in the Activity Log. This behavior is designed to help prevent backing up Arcserve D2D
data redundantly.
If you want to modify this behavior to allow Arcserve Backup to back up Arcserve D2D
sessions that were backed up previously, do the following:
1.
From the Arcserve D2D server (node) that you are backing up, open Windows
Registry Editor.
2.
3.
4.
Arcserve Backup Does Not Back up Files that were Moved or Renamed
Valid on Windows platforms.
Symptom:
When performing file system backups, Arcserve Backup does not back up files that were
moved or renamed on a node after the last backup completed. Arcserve Backup does
not generate error or warning messages in the Activity Log.
Solution:
This is expected behavior. The Client Agent for Windows lets you back up files only if
they are modified after the last backup completed. The Client Agent for Windows
cannot identify files that were moved or renamed as files that were modified.
To help prevent this behavior from occurring, you must install and license Arcserve
Backup Agent for Open Files, and verify that the CA Universal Agent Service is running in
your backup environment before you rename or move files on the node. The CA
Universal Agent service allows Arcserve Backup to detect files and directories that were
changed or moved on the agent node. If the Universal Agent Service was not running
when the files were moved, renamed, or both, ensure you have installed and licensed
Arcserve Backup Agent for Open Files, and submit a full backup of the node to help
ensure that Arcserve Backup backs up all of the files.
When you move or rename a file or folder, the Archive bit for the object is not updated.
As a result, Arcserve Backup does not back up the file or folder the next time an
incremental backup job runs. To help ensure that the Universal Agent detects and backs
up the moved and renamed files, the Universal Agent enumerates all fixed volumes that
are present on the node at specific intervals. The Universal Agent then monitors each
volume for moved or renamed files and folders. If a file or folder is detected, the archive
bit for the object is updated.
You can enable and disable this function of CA Universal Agent Service. The function is
enabled by default. To modify the default behavior, do the following:
1.
2.
3.
4.
5.
The default time interval for volume enumeration is one hour. To modify the default
behavior, do the following:
1.
2.
3.
4.
5.
Arcserve Backup Cannot Perform a Hyper-V Backup Job That Contains Data on
SMB Shares
Valid on Windows platforms.
Symptom:
When you submit Hyper-V backup jobs where the disks or configuration files of the
virtual machine are on remote SMB (Server Message Block) shares, the backup job fails.
Solution:
This behavior occurs because the File Server VSS Agent Service is not enabled on the file
server. You can enable the File Server VSS Agent Service by logging on to the Server
Manager and selecting the following menu options: Server Roles, File and Storage
Services, File and iSCSI Services, and File Server VSS Agent Service.
Arcserve Backup Cannot Perform a Hyper-V Writer or SQL VSS Writer Back Up Job
That Contains Data on SMB Shares
Valid on Windows platforms.
Symptom:
When you submit a Hyper-V or SQL VSS Writer backup job where the application has
data on remote SMB (Server Message Block) shares, the backup job fails.
Solution:
This behavior occurs because the File Server VSS Agent Service is not enabled on the file
server. You can enable the File Server VSS Agent Service by logging on to the Server
Manager and selecting the following menu options: Server Roles, File and Storage
Services, File and iSCSI Services, and File Server VSS Agent Service.
Media Problems
Memory Usage Increases When Restoring Data From a Remote FSD Located on a
Windows 2008 SP2 and Windows 2008 R2 Server
Valid on all operating systems.
Symptom:
The system response becomes very slow because of the increase in memory usage. The
reason why this occurs is because the behavior of the Windows operating system as the
system file cache consumes most of the physical RAM.
Solution:
To resolve this issue, follow the work-around in the knowledge base article from the
Microsoft link: http://support.microsoft.com/kb/976618/en-us.
Media Problems
This section contains the following topics:
Tape Errors Occur When Backing Up or Restoring Data (see page 885)
Arcserve Backup Cannot Detect RSM Controlled Devices on x64 Platforms (see page 887)
Arcserve Backup Does Not Detect a Cleaning Tape (see page 888)
Hardware Does Not Function as Expected (see page 889)
Autoloaders and Changers Appear Offline (see page 890)
Catalog Database Log Files Consume a Large Amount of Disk Space (see page 890)
Unrecognized Vaults Appear in the Media Management Administrator (see page 892)
Media Problems
Possible Problems
If you receive an error that suggests that there is something wrong with one of your
tapes, you should take corrective action as soon as possible to ensure the security of
your data. Before replacing your tape, however, you should make certain that it is the
tape that is causing the problem, and not another part of your system. Try these steps
to rule out the possibility that the problem is being caused by something other than the
tape:
Check the history of the Activity Log for the task that caused the error. Although
you may get a media error, it may only be the consequence of an earlier error.
For example, during a backup job, you may receive a SCSI port error. After receiving
this error, you may get errors that indicate a problem with the tape, or even with
the drive, but it is possible that these errors are only a consequence of the
problems with the SCSI port. Therefore, you should check the Activity Log for all the
messages and errors you received prior to receiving the error that indicated a
problem with your tape. In this way, you can determine whether there is actually a
problem with your tape, or if the tape error was the consequence of another
problem.
Monitor the library robot. If the robot is not functioning properly, you may get tape
errors. Make sure that the robot can move tapes in and out of the drives.
Rule out the possibility of a mechanical problem with the drive. To do so, try one of
these options:
If the tape still causes errors after the drive has been cleaned, move the tape to
a drive that you know is in good working order and try the same task again. If
you get the same error, then it is likely that there is a problem with the tape.
Note: If your drives are inside a library, and you want to try your tape in a
different drive, the problem drive must be offline. If Arcserve Backup did not
automatically set the drive to an offline status when it detected the media
error, right-click the library and select Offline from the pop-up menu.
Try the same task on the same drive, but with a different tape. If you get the
same error, then it is likely that the tape is fine, but that there is a problem
with the drive or some other system component.
Possible Resolutions
After you have determined that there is a problem with the tape--part of the tape is
unreadable, the tape is physically damaged in some way, and so on--you should replace
the tape as soon as possible. Before you do that, you will need to back up the data on
the bad tape to a reliable tape. You have two options at this point:
Media Problems
Try moving the tape to a drive that you know is in good working order. You can also
try cleaning the drive.
2.
Use the Tapecopy utility to copy the data from the bad tape to the new tape.
Note: If the bad tape was part of a library, export the tape from the library so that it
does not get used again.
Remove the bad tape. If the bad tape is part of a library, export it.
2.
Media Problems
Method 1--Let Arcserve Backup discover the location (slot) of the cleaning tape. To
do this, complete the following steps:
1.
2.
Open the Device Manager window, right-click the library and select Inventory
from the pop-up menu.
Arcserve Backup inventories the media in the slots. After the inventory process
is complete, Arcserve Backup detects the presence of a cleaning tape. The slot
where the cleaning tape resides becomes the cleaning slot.
Method 2--Manually specify the location (slot) of the cleaning tape. To do this,
complete the following steps:
1.
Open the Device Manager window, right-click the library and select Properties
from the pop-up menu.
The Library Properties dialog opens.
2.
3.
From the Available Slots lists, click an available slot and then click the Add
button.
The available slot moves to the Clean Slots list.
4.
Click OK.
5.
Media Problems
E6300 Windows NT SCSI Port Errors in the Arcserve Backup Activity Log.
Possible Resolutions
The following list of resolutions can help you address hardware-related issues:
Ensure that the operating system is properly recognizing your devices. If the
operating system is having a problem seeing the devices, Arcserve Backup may not
function properly.
Ensure that the latest Device Patch is installed for Arcserve Backup.
Check the Arcserve Backup Certified Device list to ensure compatibility with your
device's firmware.
Ensure that the proper SCSI drivers are loaded for your SCSI adapter.
Try using different tapes to ensure that the errors are not media-related.
Check physical connections and SCSI cabling. Errors can occur because of physical
problems, such as a bent SCSI pin.
Media Problems
If you are using Library Quick Initialization, ensure that you disable this option when
you are troubleshooting hardware and devices. You can then apply the Library
Quick Initialization option after troubleshooting has been completed.
Note: The Library Quick Initialization option can be found on the General tab on the
Library Properties dialog.
2.
Disconnect the device and correct the problem with the device.
Note: For information about troubleshooting the device, see the device
manufacturer's documentation.
3.
4.
Media Problems
Solution:
Arcserve Backup generates catalog database log files that can be used for debugging
purposes. The log files are stored in the following directory on the Arcserve Backup
server:
C:\Program Files\CA\ARCserve Backup\LOG
By default, Arcserve Backup generates up to 3 log files, and the overall size of each log
file can be up to 300 MB. However, Arcserve Backup lets you customize the behavior of
the log files by creating registry keys that control the number and size of the log files.
If you created the required optional keys and specified high values for the number and
size of the log files, the log files can consume a large amount of disk space on the
backup server.
To control the number and size of the catalog database log files, do the following:
1.
2.
3.
DebugLogFileSize
Note: With this value, Arcserve Backup generates a new log file after the
catalog database logging activity causes the current log file to exceed the
specified value.
LogFileNum
Range: 1 to 1023
Recommended value: 3
With this value, Arcserve Backup retains the number of log files specified.
If catalog database logging activity causes the number of log files to exceed
the specified limit, Arcserve Backup deletes the oldest log files until the
number of log files is equal to the specified limit.
Solution:
This is expected behavior. Arcserve Backup creates two default vaults without media
associations when you install UNIX and Linux Data Mover, register the data mover
servers with the primary server, and migrate MM Admin data from your previous
Arcserve Backup installation. The unrecognized vaults will not affect your backup and
storage operations.
Check on each server that the shared devices can been seen by the Operating
System, by checking the Windows Device Manager.
If the shared devices cannot be seen by Windows, then double check your
SAN zoning to make sure this server is included. If it is included, reboot the
server to get Windows to discover the devices. When you get Windows to see
the devices, then you can restart the Tape Engine on that machine.
If the server having problems seeing the devices is the Primary server, then you
need to restart the Arcserve Backup Tape Engine service on this server and
then on all SAN-attached Member servers in that domain.
Check if the shared devices can been seen by Arcserve Backup through the
Arcserve Backup Device Manager, looking under each server.
If shared devices cannot be seen by Arcserve Backup, but Windows does see
them, then you need to restart the Tape Engine service.
If the server having problems seeing the devices is the Primary server, then you
need to restart the Arcserve Backup Tape Engine service on this server and
then all SAN-attached Member servers in that domain.
If the Arcserve Backup Member server's Tape Engine service was started before the
Primary server's Tape Engine has finished initializing, the Member server will wait
for the Primary server for a period of time, but eventually will start without being
able to "share" the devices.
If the Arcserve Backup Member server's Tape Engine service was started before the
Primary server's Tape Engine service was started, the Member server will wait for
the Primary server, for a period of time, but eventually will start, without being able
to "share" the devices.
Solution:
Check the Arcserve Backup Activity log to see when, and in what order the services
might have started. Make sure all devices on the Arcserve Backup Primary server are
initialized, then just restarting the Tape Engine service on the Member server(s) should
be enough to resolve this.
Important! When starting the Tape Engine service in a Arcserve Backup Domain that is
part of a SAN, it is important to always start the Primary server's service first and let it
fully initialize before starting the Tape Engine service on any of the Member servers.
2.
If the IBMtape driver is installed, search under the services key for a key name that
is equal to the file name of the IBMtape driver.
For example, if the file name of the IBMtape driver ibmtp2k3.sys, the key name is
ibmtp2k3.
Select the key, add a DWORD value named "DisableReserveUponOpen," and set it
to 1.
3.
The Arcserve Backup SAN License for the server you are trying to run the backup on
has expired.
Each SAN-attached server must have a SAN License. The licenses are all applied to
the Primary server in the corresponding Arcserve Backup Domain.
The Arcserve Backup TLO License for the server you are trying to run the backup on
has expired.
Each SAN-attached server sharing a multiple drive library must have a TLO License.
The licenses are all applied to the Primary server in the corresponding Arcserve
Backup Domain.
The Arcserve Backup Primary server Tape Engine service is no longer available.
Solution:
1.
Check the Arcserve Backup Activity log for any SAN license errors.
If necessary add the applicable SAN license.
2.
Check the Arcserve Backup Activity log for any TLO license errors.
If necessary add the applicable TLO license.
3.
Check the Arcserve Backup Primary server Tape Engine service status
a.
In the Arcserve Backup GUI, access the Server Admin screen and check the
status of the Tape Engine service.
b.
In the Arcserve Backup Activity log, check for a Primary server Tape Engine stop
event.
c.
In the Windows system Event Viewer, check for a Tape Engine service stop
event or an exception.
If the problem is related to the Primary Tape Engine service being down, then
restart and try again.
If the problem persists, contact Arcserve support for online technical assistance and
a complete list of locations, primary service hours, and telephone numbers.
For MSCS clusters, see Stop MSCS From Monitoring Arcserve Backup Services
on Windows Server 2003 Systems (see page 919).
Back up each of the nodes with their private disks and system state, using the
hostname when submitting the backup jobs.
Note: Because shared disks can move from one node to another and there is no
reliable way of predicting which node will own the shared disks during backup, do
not back up shared disks using the machine hostname.
2.
Back up the shared disks, using the cluster virtual name when submitting the
backup job. If the shared disks fail over from one node to another, the cluster
virtual node name fails over with it, so that Arcserve Backup always backs up the
cluster shared disks. To ensure this, set up the cluster dependencies so that the
cluster name and cluster shared disks fail over at the same time.
Note: To provide disaster protection for your cluster nodes, you must perform a full
backup of each node.
For MS SQL Server 2008 Express, you must use the virtual name which the Arcserve
Backup is deployed on.
2.
For MS SQL Server 2005 cluster, you must use the virtual name which the SQL
Server Cluster is deployed on. (In this case, make sure that you set the correct
virtual name of the SQL Server cluster when installing Arcserve Backup. To find out
the SQL Server Cluster virtual name, refer to the SQL Server Cluster document.
Miscellaneous Problems
Miscellaneous Problems
This section contains the following topics:
Discovery Service Does Not Function Properly (see page 900)
Arcserve Backup Servers and Agent Servers Cannot Communicate with Each Other (see
page 900)
SRM PKI Alert is Enabled by Default (see page 902)
Job Queue Log Files Consume a Large Amount of Disk Space (see page 904)
Unable to View all Job Logs for Rotation Backups after the Database is Pruned (see page
906)
Arcserve Backup Servers and Agent Servers Cannot Communicate with Each
Other
Valid on Windows Server 2008 R2 and Windows Server 2012 systems.
Symptom:
Arcserve Backup servers, Arcserve Backup agent servers, or both, may not be able to
communicate with each other after you change the Windows Server 2008 R2 firewall
connection settings.
Miscellaneous Problems
Solution:
To ensure that Arcserve Backup primary servers, member servers, and stand-alone
servers running Windows Server 2008 R2 can browse, back up, and restore data that
resides on Arcserve Backup agent servers running Windows Server 2008 R2, you must
allow the Arcserve Backup applications on the backup servers and the agent servers to
communicate using one of the following Windows network location types:
Windows domain
For information about how to allow applications communicate using the above
Windows network location types, see the Windows Server 2008 R2 documentation.
Miscellaneous Problems
However, when you upgrade from a previous version of Arcserve Backup, the Enable
Alert option may be enabled, by default. Based on specific scenarios, the following
solution describes the corrective actions required to disable the Enable Alert option.
Miscellaneous Problems
Solutions:
To disable the Enable Alert option, do one of the following:
Solution 1:
You want to disable the Enable Alert option for all the agents that exist currently in your
backup environment
1.
2.
3.
On the Apply to Multiple dialog, select the individual agents, click Select All, or click
Unselect All, and then click OK.
Open the Arcserve Backup database instance using the Microsoft SQL Server
Management Console.
2.
3.
In the validalert field, change the value from 1 (enable alert) to 0 (disable alert).
4.
Miscellaneous Problems
5.
Change the value of the validalert field by executing the following command:
SQLCMD.exe -S <Server_Name>\<ARCserve_Instance_Name> d asdb
Example:
C:\Program Files\CA\ARCserve Backup\LOG\JobQueue.log
As the log files reach a specified size (for example, 300 MB), Arcserve Backup renames
the log file and creates a new Job Queue log file. By default, Arcserve Backup deletes the
log files 31 days after they were generated.
Miscellaneous Problems
Based on the following conditions, the Job Queue log files can consume a large amount
of free disk space on the backup server:
Arcserve Backup lets you control the size and quantity of the Job Queue log files by
doing the following:
1.
2.
To limit the size of the log files that Arcserve Backup generates, open the following
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe
Backup\Base\QueueSystem\DebugFileSize
3.
To limit the quantity of log files that Arcserve Backup retains, open the following
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe
Backup\Base\Task\Common\JobQueueMaxFiles
4.
Default: 10
Range: 5 to 30
Recommended value: 10
(Optional) To decrease the level of debugging detail, create the following registry
key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe
Backup\Base\QueueSystem\DebugLevel
Range: 1 to 5
Recommended value: 3
Note: A higher value increases the level of debugging detail.
Specify a value of 1 or 2.
Miscellaneous Problems
Values too low--Arcserve Backup may not be able to provide you with a sufficient
level of information to debug problems.
Values too high--The log files may consume too much free disk space on the backup
server.
Unable to View all Job Logs for Rotation Backups after the Database is Pruned
Valid on Windows platforms.
Symptom:
When you want to view all job logs relating to rotation and repeating jobs, you can view
only job logs for the most recent execution for the job.
Solution:
When Arcserve Backup database pruning jobs run, the pruning job deletes all job logs
for a particular job with the exception of the most recent log file. This behavior prevents
you from having the capability to view all of the log files relating to repeating jobs and
jobs defined with rotation schedules. To configure database pruning jobs to retain all of
the job logs associated with repeating and rotation jobs, complete the following steps:
1.
From the backup server, open the following key using the Windows Registry Editor:
x86 Operating Systems:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe
Backup\Base\Database
2.
3.
After you create this keyword, Arcserve Backup prunes the job logs based on the
value that you define for the Prune activity logs older than option for the Database
Engine. For more information, see Database Engine Configuration (see page 514).
This behavior applies to only job logs. Arcserve Backup does not prune the Activity
Log for recent executions of jobs.
You can view the job logs in the Job Queue, the Job History, and the Database
Manager.
Cluster Overview
A computer cluster is a group of connected computers that work together closely so
that in many respects they can be viewed as though they are a single computer. Clusters
can be categorized in two types: HA (High Availability) and High Performance. Within HA
clusters, there are two working modes: active/active or active/passive. Currently,
Arcserve Backup can only be deployed in an active/passive HA mode.
The primary function of a cluster occurs when one server (or node) in a cluster fails or is
taken offline. In a cluster environment, the other node in the cluster will then take over
the failed server's operations. Arcserve Managers using server resources experience
little or no interruption of their work because the resource functions move
transparently from the active node to the failover node.
Cluster Overview
The servers within a cluster environment are not only connected physically by cables,
but also programmatically through clustering software. This connection allows clustered
servers to take advantage of features (such as fault tolerance and load balancing) that
are unavailable to stand-alone server nodes. Clustered servers can also share disk drives
that contain important information, such as a clustered database.
For example, assume node A and node B form a clustered Arcserve Backup HA server.
The Arcserve Backup cluster server will work only in the "active/passive" mode, and as a
result, only one Arcserve Backup instance is running at the same time. In this
environment, Arcserve Managers could connect to the Arcserve Backup server AS1 or
Arcserve Backup server AS2 without knowing which node is active and currently hosting
their server. The virtual server name and IP address ensures that the server location is
transparent to Arcserve Backup applications. To the Arcserve Manager, it appears that
the Arcserve Backup server is running on a virtual server called CL1.
When one of the software or hardware resources fails or is shut down, a failover occurs.
Resources (for example: applications, disks, or an IP address) migrate from the failed
active node to the passive node. The passive node takes over the Arcserve Backup
server resource group and now provides service.
Cluster Overview
If node A fails, node B automatically assumes the role of the active node. To an Arcserve
Manager, it is exactly as if node A were turned off and immediately turned back on
again. The location of the active node (A or B) in the Cluster (CL1) is transparent to
Arcserve Backup.
Cluster Overview
Cluster Overview
Resource Group
A cluster resource is any physical or logical component that can be physically shared
between multiple cluster nodes, but can only be hosted (owned) by one active node at a
time. The virtual IP address, virtual computer name, shared disk, and even the
applications are considered cluster resources. A cluster system allows you to categorize
these resources as a "group" for a specific functionality purposes. These resource
groups can be treated as a "container" of resources. A cluster resource group is a logical
unit for application deployment, which means that a cluster-aware application must be
installed into a group and bind itself with the resources that are associated with that
group. The resource group is the minimum unit for failover purposes.
Cluster Overview
Shared Disks
Shared disks provide shared location for cluster-aware applications to save data. Shared
disks allow cluster-aware applications, which might run on different nodes because of
failover, to gain access to a logical volume in a consistent way, as if they are local at
each of the nodes. Each virtual shared disk corresponds to a logical volume that is
actually local at one of the nodes, which is called the server or primary node. Each node
within the cluster must have access to a shared disk to operate within the cluster. The
cluster system is configured so that only the active node can access the shared disk at
any time.
Cluster Overview
Mirrored Disks
Mirrored disks provide a shared location for cluster-aware applications to save data.
Mirrored disks (applicable to NEC clusters only) are separate disk devices that are
physically attached to their host separately, but work like one single device logically.
Mirrored disks contain an exact duplicate of the disk that it mirrors. Data is stored twice
by writing to both the local disk and its remote mirrored disk. If a disk fails, data does
not have to be rebuilt and can be easily recovered by copying it from the mirrored disk
to the replacement disk. It is recommended that mirrored disks reside on different
devices so that a single-point disk failure cannot damage both copies of the data. The
main disadvantage of mirrored disks is that the effective storage capacity is only half of
the total disk capacity because all data gets written twice. The cluster system is
configured so that only the active node can access the mirrored volume and sync-up the
data between different physical disks.
Quorum Disks
In addition to the resource groups created for each clustered application, a cluster
always has a resource group to represent the quorum of the cluster. This resource
group, by default named Cluster Group, is created when the cluster is created. In a
shared disk quorum, the disk containing the quorum resource is called the quorum disk,
and it must be a member of the default Cluster Group. A quorum disk is used to store
cluster configuration database checkpoints and log files which help manage the cluster
as well as maintain consistency. The quorum resource is used to decide which nodes of
the cluster are supposed to form the cluster. Because the cluster configuration is kept
on a quorum disk resource, all nodes in the cluster must be able to access and
communicate with the node that owns it.
Note: Quorum Disks apply to only Microsoft Cluster Server (MSCS) environments.
Cluster Overview
Planned Failovers
Planned failovers occur when it is necessary to perform maintenance on the active
node within a cluster and you want Arcserve Backup to migrate the cluster
resources from that active node to a passive node within the cluster. Examples for
planned failovers are system maintenance, disaster recovery tests, and training.
When a planned failover occurs, Arcserve Backup recovers in another node with all
scheduled jobs retained.
Unplanned Failovers
Unplanned failover can occur because of hardware or software failures. When
unplanned failover occurs, Arcserve Backup recovers in another node, picks up the
failed job from the Arcserve Backup job queue, and resumes the job from the point
where it failed. If a failover occurs, the job resume is based on a checkpoint
mechanism as follows:
For a local backup job, the job will resume at the volume level after a failover.
For example, if a backup job involves two volumes: C and D, and a failover
occurs when the backup for volume C was finished and the backup for volume
D was ongoing. After the failover, the backup job will restart and skip the
backup for volume C and continue to backup volume D.
For a remote backup job, the job will resume at the host level.
For example, if a backup job involves Host1 and Host2, and a failover occurs
when the backup for Host1 is finished, but the backup for Host2 is not. After
the failover, the backup job will restart and skip the backup for Host1 and
continue to backup Host2 (in this case, the backup for Host2 does not skip any
volumes that might be backed up before failover).
Jobs running on other backup servers instead of the HA server of the domain will
rarely be impacted by failover. For example, when the Primary server is HA server,
and it fails over, the jobs running on member servers are not impacted except in
one situation. If you are using a HA primary server, the jobs that run on the member
servers may fail when an unplanned failover occurs on the HA primary server. (The
failures only occur when the jobs on the member servers are finishing when the
failover occurs)
Note: If you are using Arcserve Backup Agents to backup the active node of the
cluster or the virtual node, and an unplanned failover occurs (the active node is
down), the job would become incomplete. To ensure that these nodes could be
backed up after failover, you should configure the jobs to create makeup jobs.
The following diagram shows a typical active/passive cluster environment. The active
node in this cluster is associated with two names and IP addresses: one for the physical
name of the machine and the other for the virtual name created by the cluster itself or
the cluster-aware application. The passive node is associated with only one name, the
physical name of the machine. To fully protect the cluster, you need to install the
Arcserve Backup agent into both of these physical nodes. In each of these instances,
depending on the protected target, Arcserve Backup will be deployed to protect your
cluster and back up your data using either the physical node or the virtual node.
MSCS Protection
Microsoft Cluster Server (MSCS) software provides a clustering technology that keeps
server-based applications highly available, regardless of individual component failures.
For MSCS, there are two basic types of targets that need to be protected by backup:
cluster self-protection, in which the cluster itself is protected (metadata and
configuration information) and clustered-application protection.
Run on, and take advantage of, MSCS high availability features such as:
Job failover from one Arcserve Backup node in a cluster to another node
Provide disaster protection for MSCS nodes using the Arcserve Backup Disaster
Recovery Option. For more information, see the Disaster Recovery Option Guide.
Backup and restore applications, such as MS SQL Server and MS Exchange Server,
installed on MSCS clusters using the Arcserve Backup agents. For more information
on available agents, see the Implementation Guide.
all data on the local disks contained in the Windows boot/system partitions
During restore operations, you first need to determine the severity of the problem. If
you cannot boot the node at all, see Recovering Clusters in the Arcserve Backup Disaster
Recovery Option Guide. If you can boot the operating system and only the cluster
database is damaged, you will not be able to selectively restore the Cluster Database as
a single entity, it must be restored as part of a System State session restore.
Note: To back up and restore the Cluster Database, it is sufficient to back up and restore
the Windows System State with the cluster service running. When a cluster node is in
the Directory Service Restore mode, the Logon properties of the Cluster Service User
Account must be set as Administrator to ensure that Arcserve Backup can be accessed
while in Windows Safe Mode.
Stop MSCS From Monitoring Arcserve Backup Services on Windows Server 2003 Systems
When a Arcserve Backup server is configured as cluster-aware, all critical Arcserve
Backup services will be monitored by MSCS. If some service fails, MSCS will try to restart
it or trigger a failover if the restart attempt fails. This means that you can no longer stop
a service by using the Arcserve Backup Server Administrator. If you attempt to stop a
Arcserve Backup service, the following message opens:
However, in some situations, you may want to stop Arcserve Backup services. For
example, you need to stop various services so that you can perform hardware
maintenance.
Note: For information about how to perform this task on Windows Server 2008 systems,
see Stop MCSC From Monitoring Arcserve Backup Services on Windows Server 2008
Systems (see page 921).
To stop MSCS from monitoring Arcserve Backup services on Windows Server 2003
systems
1.
2.
Select the group that the Arcserve server is deployed in, and locate the applicable
Arcserve resource. Right-click the Arcserve resource and click Properties on the
pop-up menu.
The ARCserve HA Properties dialog appears.
3.
Service Name
Controlling Resources
Tape Engine
Arcserve HA
Arcserve Registry
Arcserve ASDB
Arcserve HA
Arcserve Registry
Arcserve HA
4.
Using the Windows Service manager, stop the applicable Arcserve Backup service to
allow you to perform the necessary maintenance.
5.
Stop MSCS From Monitoring Arcserve Backup Services on Windows Server 2008 Systems
When a Arcserve Backup server is configured as cluster-aware, all critical Arcserve
Backup services will be monitored by MSCS. If some service fails, MSCS will try to restart
it or trigger a failover if the restart attempt fails. This means that you can no longer stop
a service by using the Arcserve Backup Server Administrator. If you attempt to stop a
Arcserve Backup service, the following message opens:
In some situations, you may want to stop Arcserve Backup services. For example, you
may need to stop various services so that you can perform hardware maintenance.
Note: For information about how to perform this task on Windows Server 2003 systems,
see Stop MSCS From Monitoring Arcserve Backup Services on Windows Server 2003
Systems (see page 919).
To stop MSCS from monitoring Arcserve Backup services on Windows Server 2008
systems
1.
2.
Select the Arcserve Backup server where the Arcserve service is deployed in, and
locate the applicable Arcserve resource. Right-click the ARCserve service or
application and click Properties on the pop-up menu.
The ARCserve HA Properties dialog opens.
3.
Service Name
Controlling Resources
Tape Engine
Arcserve HA
Arcserve Registry
Arcserve ASDB
Arcserve HA
Arcserve Registry
Arcserve HA
4.
Using the Windows Service manager, stop the applicable Arcserve Backup service to
allow you to perform the necessary maintenance.
5.
Stop MSCS From Monitoring Arcserve Backup Services on Windows Server 2012 Systems
When a Arcserve Backup server is configured as cluster-aware, all critical Arcserve
Backup services will be monitored by MSCS. If some service fails, MSCS will try to restart
it or trigger a failover if the restart attempt fails. This means that you can no longer stop
a service by using the Arcserve Backup Server Administrator. If you attempt to stop a
Arcserve Backup service, the following message opens:
In some situations, you may want to stop Arcserve Backup services. For example, you
may need to stop various services so that you can perform hardware maintenance.
Note: For information about how to perform this task on Windows Server 2003 systems,
see Stop MSCS From Monitoring Arcserve Backup Services on Windows Server 2003
Systems (see page 919).
Follow these steps:
1.
2.
Select the Arcserve Backup server where the Arcserve cluster role is deployed in,
and locate the applicable Arcserve resource. Right-click the ARCserve HA resource
and click Properties on the pop-up menu.
The ARCserve HA Properties dialog opens.
3.
Service Name
Controlling Resources
Tape Engine
Arcserve HA
Arcserve Registry
Arcserve ASDB
Arcserve HA
Arcserve Registry
Arcserve HA
4.
Using the Windows Service manager, stop the applicable Arcserve Backup service to
allow you to perform the necessary maintenance.
5.
2.
Run the "babha.exe -postsetup" utility to set up new Arcserve cluster resources.
When a cluster-aware installation is successfully finished, a Post Setup pop-up
screen appears with an option to create HA resources.
3.
Select the Create HA resources for MSCS option and click OK to create the new
cluster resources.
Note: You should specify this option only after you completed the Arcserve Backup
installation on the last node in the cluster.
The following new Arcserve cluster resources are created:
Windows Server 2003--On Windows Server 2003 systems, the following cluster
resources are created:
Arcserve HA
Arcserve ASDB
Arcserve Registry
Arcserve Share
Windows Server 2008--On Windows Server 2008 systems, the following cluster
resources are created:
Arcserve HA
Arcserve ASDB
Arcserve Registry
Windows Server 2012--On Windows Server 2012 systems, the following cluster
resources are created:
Arcserve HA
Arcserve ASDB
Arcserve Registry
Arcserve database
Arcserve Registry
Arcserve Share
Arcserve database
Arcserve Registry
Arcserve database
Arcserve Registry
Right-click the group name and click Take offline on the pop-up menu.
Right-click the service or application name and click Take this service or
application offline.
The state of the Arcserve cluster resources is changed from Online to Offline.
Windows Server 2012 systems:
The state of the Arcserve cluster resources is changed from Online to Offline.
2.
Based on the Windows Server system you use, perform one of the following
options:
Delete all cluster resources. For more information, see Delete Arcserve Backup
Cluster Resources (see page 926).
All Arcserve Backup cluster resources are deleted.
2.
From the Arcserve Backup home directory, run the cstart.bat utility to start all
Arcserve Backup services.
3.
From the Start menu, access the Server Configuration Wizard to run the
ARCserveCfg.exe utility for the active node and make the necessary change. Do not
check the "Last Cluster Node" checkbox on the last screen of the Server
Configuration Wizard.
For more information about changing the database, see Specify a Arcserve
Backup Database Application (see page 662).
Note: Local SQL Server is not supported when NEC CLUSTERPRO/ExpressCluster
is used to make Arcserve Backup highly available.
Note: When this utility is run on the first node within a cluster, it will run in the
normal mode.
The first "active" cluster node is configured for the new property and a new
arcservecfg.ICF configuration file is created.
4.
From the Arcserve home directory, run the cstop.bat utility to stop all Arcserve
Backup services.
All Arcserve Backup services are stopped.
5.
Right-click the group name and select Move Group on the pop-up menu.
Right-click the service or application name and click Move this service or
application to another node on the pop-up menu.
Right-click the ARCserve cluster role name and click Move this role to another
node on the pop-up menu.
The status of the original node will be changed to "passive" and the status of the
next node within the cluster will be changed to "active".
6.
From the Start menu, access the Server Configuration Wizard to run the
ARCServeCfg.exe utility for the new active node and make the necessary change.
Note: When this utility is run again on any subsequent nodes in the same cluster, it
will detect the existence of the arcservecfg.ICF configuration file and automatically
run the utility in the cluster mode.
The next "active" cluster node is configured for the new property.
7.
Repeat steps 5 and 6 for all remaining nodes in the cluster. When you are
performing this configuration procedure on the last node in the cluster, check the
"Last Node" checkbox on the last screen of the Server Configuration Wizard.
All nodes in the cluster are configured for the new property.
8.
Right-click the group name and select Move Group on the pop-up menu .
Right-click the service or application name and click Move this service or
application to another node on the pop-up menu.
Right-click the Arcserve cluster role name and click Move this role to another
node on the pop-up menu.
The status of the last node will be changed to "passive" and the status of the
original node within the cluster will be changed back to "active".
9.
Create all Arcserve Backup cluster resources manually. For more information, see
Rebuild Cluster Resources Manually (see page 924).
The new Arcserve cluster resources are created.
The state of the new Arcserve cluster resources is changed from Offline to Online.
Delete all cluster resources. For more information, see Delete Arcserve Backup
Cluster Resources (see page 926).
All Arcserve Backup cluster resources are deleted.
2.
From the Arcserve Backup home directory, run the cstart.bat utility to start all
Arcserve Backup services.
All Arcserve Backup services are started.
3.
From the Start menu, access the Server Configuration Wizard to run the
ARCserveCfg.exe utility for the active node and specify the new Arcserve Backup
domain. For more information about changing a domain, see Move a Member
Server to a Different Arcserve Backup Domain (see page 572).
The first "active" cluster node is configured for the new domain.
4.
From the Arcserve home directory, run the cstop.bat utility to stop all Arcserve
Backup services.
All Arcserve Backup services are stopped.
5.
From the Cluster Administrator, right-click on the group name and from the pop-up
menu, select Move Group to change the active node.
The status of the original node will be changed to "passive" and the status of the
next node within the cluster will be changed to "active".
6.
From the Arcserve Backup home directory, run the cstart.bat utility to start all
Arcserve Backup services.
All Arcserve Backup services are started.
7.
From the Arcserve home directory, run the cstop.bat utility to stop all Arcserve
Backup services.
All Arcserve Backup services are stopped.
8.
9.
From the Cluster Administrator, right-click on the group name and from the pop-up
menu, select Move Group to change the active node back to the original node.
The status of the last node will be changed to "passive" and the status of the
original node within the cluster will be changed back to "active".
10. Create all Arcserve Backup cluster resources manually. For more information, see
Rebuild Cluster Resources Manually (see page 924).
Note: You should create Cluster resources based on new Arcserve database type.
The new Arcserve cluster resources are created.
11. From the Cluster Administrator, right-click on the group name and from the pop-up
menu, select Bring Online.
The state of the new Arcserve cluster resources is changed from Offline to Online.
Ability to fail jobs over from one Arcserve Backup node in a cluster to another
node when Arcserve Backup failover occurs.
all data on the local disks contained in the Windows boot/system partitions
During restore operations, you first need to determine the severity of the problem. If
you cannot boot the node at all, see Recovering NEC Clusters in the Arcserve Backup
Disaster Recovery Option Guide. If you can boot the operating system and only the NEC
cluster files are damaged, refer to the applicable NEC CLUSTERPRO/ExpressCluster
document to manually restore these configuration files that are related to NEC clusters.
For NEC clusters, few applications are designed to be cluster-aware and many do not
recognize the NEC virtual name/IP address. However, for some of the more popular
applications, NEC provides specific documentation for configuring these applications as
cluster-aware and deploying them so that you can perform backup and restore jobs.
Refer to NEC website for a list of all supported applications and detailed information on
how to configure them as cluster-aware. If you have deployed one of these supported
applications, refer to the corresponding NEC documentation for details about how to
perform a backup and restore with cluster support.
However, in some situations, you may want to stop some Arcserve Backup service. For
example, you may want to stop the Tape Engine so that you can perform hardware
maintenance.
Note: This section contains graphics that correspond with NEC
CLUSTERPRO/ExpressCluster version 8.0. If you are running a more recent version of
NEC CLUSTERPRO/ExpressCluster, see your NEC CLUSTERPRO/ExpressCluster
documentation.
2.
Locate and select the applicable Arcserve service. Right-click on the service and
from the pop-up menu, select Stop Monitoring. A confirmation screen appears
asking you to confirm or cancel your request to stop monitoring the selected
service. Click OK.
The selected Arcserve Backup service is no longer being monitored by NEC
CLUSTERPRO/ExpressCluster.
Stop the cluster group. For more information, see Stop NEC Cluster Groups (see
page 937).
Note: You must stop the group to edit the group properties.
2.
Remove the registry sync and edit the start.bat and stop.bat scripts to disable
Arcserve Backup scripts added during installation. For more information, see
Disable Arcserve Backup in NEC Cluster Scripts (see page 938).
3.
From the Arcserve Backup home directory, run the cstart.bat utility to start all
Arcserve Backup services.
All Arcserve Backup services are started.
4.
From the Start menu, access the Server Configuration Wizard to run the
ARCserveCfg.exe utility for the active node and specify the new Arcserve Backup
domain. For more information about changing a domain, see Move a Member
Server to a Different Arcserve Backup Domain (see page 572).
The first "active" cluster node is configured for the new domain.
5.
From the Arcserve home directory, run the cstop.bat utility to stop all Arcserve
Backup services.
All Arcserve Backup services are stopped.
6.
From the Cluster Manager, right-click on the group name and from the pop-up
menu, select Move Group to change the active node.
The status of the original node will be changed to offline (passive) and the status of
the next node within the cluster will be changed back to online (active).
7.
From the Arcserve Backup home directory, run the cstart.bat utility to start all
Arcserve Backup services.
All Arcserve Backup services are started.
8.
From the Arcserve home directory, run the cstop.bat utility to stop all Arcserve
Backup services.
All Arcserve Backup services are stopped.
9.
10. From the Cluster Manager, right-click on the group name and from the pop-up
menu, select Move Group to change the active node back to the original node.
The status of the last node will be changed to offline (passive) and the status of the
original node within the cluster will be changed back to online (active).
11. Rebuild the NEC Cluster Scripts and Registry Sync. For more information, see Enable
Arcserve Backup in NEC Cluster Scripts (see page 941).
The new NEC HA scripts are created and the registry is synchronized.
12. Start the cluster group.
Stop the failover group that the Arcserve Backup is deployed on and then suspend
the cluster group.
For more information, see Stop NEC Cluster Groups (see page 937).
Note: You must stop the group to edit the group properties.
2.
Remove the registry sync and edit the start.bat and stop.bat scripts to disable
Arcserve Backup scripts added during installation. For more information, see
Disable Arcserve Backup in NEC Cluster Scripts (see page 938).
Resume the cluster and then start the failover group.
3.
From the Start menu, access the Server Configuration Wizard to run the
ARCserveCfg.exe utility for the active node and make the necessary change. Do not
check the "Last Cluster Node" checkbox on the last screen of the Server
Configuration Wizard.
For more information about changing the database, see Specify a Arcserve
Backup Database Application (see page 662).
Note: Local SQL Server is not supported when NEC CLUSTERPRO/ExpressCluster
is used to make Arcserve Backup highly available.
Note: When this utility is run on the first node within a cluster, it will run in the
normal mode.
The first "active" cluster node is configured for the new property and a new
arcservecfg.ICF configuration file is created.
4.
From the Start menu, access the Server Configuration Wizard to run the
ARCServeCfg.exe utility for the new active node and make the necessary change.
Note: When this utility is run again on any subsequent nodes in the same cluster, it
will detect the existence of the arcservecfg.ICF configuration file and automatically
run the utility in the cluster mode.
The next "active" cluster node is configured for the new property.
5.
Repeat steps 4 and 5 for all remaining nodes in the cluster. When you are
performing this configuration procedure on the last node in the cluster, check the
"Last Node" checkbox on the last screen of the Server Configuration Wizard.
All nodes in the cluster are configured for the new property.
6.
From the Cluster Manager, right-click on the group name and from the pop-up
menu, select Move Group to change the active node back to the original node.
The status of the last node will be changed to offline (passive) and the status of the
original node within the cluster will be changed back to online (active).
7.
Stop the failover group that the Arcserve Backup server is deployed on and then
suspend cluster services.
Rebuild the NEC Cluster Scripts and Registry Sync. For more information, see Enable
Arcserve Backup in NEC Cluster Scripts (see page 941).
The new NEC HA scripts are created and the registry is synchronized.
8.
2.
From the tree listing, right-click on the Arcserve group, and from the pop-up menu
select Stop group.
A confirmation pop-up screen appears.
3.
Click OK.
The selected group is stopped.
2.
Select the NEC Group that the Arcserve server is deployed in, and locate the
corresponding Arcserve cluster resources. Right-click on each Arcserve cluster
resource and from the pop-up menu, select Property.
The Group property dialog appears.
3.
Select the Reference and Change option. When the Group properties dialog opens,
select the Script tab.
The Script tab dialog appears.
4.
From the Script list, select start.bat and click Edit. When the start.bat script appears,
locate the REM SET process script (two locations) and set the value to zero as
follows:
SET process=0
Note: In the start.bat file, the REM SET process script is located after NORMAL and
after FAILOVER.
The start.bat script is modified.
5.
From the Script list, select stop.bat and click Edit. When the stop.bat script appears,
locate the REM SET process script (two places) and set the value to zero as follows:
SET process=0
Note: In the stop.bat file, the REM SET process script is located after NORMAL and
after FAILOVER.
The stop.bat script is modified.
6.
7.
From the Registry key list, select the existing registry key and click Delete.
The Registry key is deleted.
2.
Select the NEC Group that the Arcserve server is deployed in, and locate the
corresponding Arcserve cluster resources. Right-click on each Arcserve cluster
resource and from the pop-up menu, select Property.
The Group property dialog appears.
3.
Select the Reference and Change option. When the Group properties dialog opens,
select the Script tab.
The Script tab dialog appears.
4.
From the Script list, select start.bat and click Edit. When the start.bat script appears,
locate the REM SET process script (two places) and set the value to 1 as follows:
SET process=1
Note: In the start.bat file, the REM SET process script is located after NORMAL and
after FAILOVER.
The start.bat script is modified.
5.
From the Script list, select stop.bat and click Edit. When the stop.bat script appears,
locate the REM SET process script (two places) and set the value to 1 as follows:
SET process=1
Note: In the stop.bat file, the REM SET process script is located after NORMAL and
after FAILOVER.
The stop.bat script is modified.
6.
From the Group properties dialog, select the Registry tab. When the Registry dialog
opens, click Add.
The Add/Change registry key dialog appears.
7.
Add the Registry key that corresponds with your computer's architecture:
x86 Platforms:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base
x64 Platforms:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\CA ARCServe
Backup\Base
Click OK.
The Registry key is added to the Registry key list on the Group Properties dialog.
There are two NDMP modes available with NetApp Cluster running Data ONTAP 8.2:
NDMP node-scope-mode:
A cluster is in a mixed version state where Data ONTAP 8.2 and earlier versions in
the Data ONTAP 8.x release family are running on nodes, NDMP follows the
node-scoped behavior. This NDMP behavior continues even after upgrading to Data
ONTAP 8.2.
In the node-scoped NDMP mode, you can perform tape backup and restore
operations at a node level.
You can manage NDMP at a node level by using NDMP options and commands. It is
required that you use NDMP specific credentials to access a storage system to
perform tape backup and restore operations.
Refer to the following link to view the NetApp documentation on commands for
managing node-scoped NDMP mode.
https://library.netapp.com/ecm/ecm_download_file/ECMP1196817
Node-scoped mode
NDMP Control Connection Type
Node-management LIF
Node-management LIF
Data LIF
None
Cluster-management LIF
Limitations
The NetApp Clustered Data ONTAP 8.2 introduces the scalability limit for NDMP
sessions that are based on the system memory size of the storage system. For more
information, click on the following link for the Clustered Data ONTAP 8.2
documentation.
https://library.netapp.com/ecmdocs/ECMP1196874/html/GUID-479784EB-7101-4F16-9
580-37FFF7C6D040.html
Arcserve Backup can support only the maximum of 7 NAS devices per NAS node when
the device is backed up from using the Node management LIF. A NAS device can be a
changer or a tape drive.
In the Vserver aware NDMP mode, Arcserve Backup can support only the maximum of 7
NAS devices per cluster when the device is backed up from using the Cluster
management LIF. A NAS device can be a changer or a tape drive.
For more details, you can refer to the following NetApp Clustered Data ONTAP 8.2
Commands: Manual Page Reference documentation for increasing the NDMP session
count: https://library.netapp.com/ecm/ecm_download_file/ECMP1196817
On client agent systems, Arcserve Backup displays folder names, file names, and
registry strings using JIS2004 Unicode characters.
All servers in a Arcserve Backup domain (primary and member servers) must be
running this release of Arcserve Backup and have the same language packs
installed.
Arcserve Backup r16, r15, r12.5, r12 SP1, and Arcserve Backup r12 agents and the
Arcserve Backup r16.5 base product cannot co-exist on the same computer.
However, the Arcserve Backup r16.5 base product can co-exist with these agents in
the same network.
To back up and restore Microsoft Exchange Server and Microsoft SharePoint Server
data with support for JIS2004 Unicode characters, you must enable the Arcserve
Catalog database.
All Arcserve Backup servers sharing a single Microsoft SQL Server database should
be upgraded to the same version of Arcserve Backup.
All Arcserve Backup domains sharing a single Microsoft SQL Server database must
specify the same SQL Server collation setting. You can specify the SQL Server
collation setting from a primary and stand-alone server using the Server
Configuration Wizard.
Windows Server 2003, Japanese version, with the Japanese fonts patch.
Note: For more information, see the Microsoft website.
Browse and view system and volume information in the Arcserve Backup managers,
view logs, and generate reports without displaying unrecognized text.
View job details and Activity Log data in the Job Status Manager.
Generate Alert Manager email messages with JIS2004 Unicode text attachments
(for example, a Job Log).
Execute job scripts using scripts created in previous releases of Arcserve Backup.
Note: This capability is limited to scripts created using Arcserve Backup r12.
All releases of the Arcserve Backup base product from Arcserve Backup r12 Service
Pack 1 to this release on x86 and x64 systems.
Note: Unicode support is only applicable to local backup, restore, and compare
operations.
All releases of the Arcserve Backup Client Agent for Windows from Arcserve Backup
r12 Service Pack 1 to this release on x86 and x64 systems.
All releases of the Arcserve Backup Agent for Microsoft Exchange Server from
Arcserve Backup r12 Service Pack 1 to this release on x86 and x64 systems.
All releases of the Arcserve Backup Agent for Microsoft SQL Server from Arcserve
Backup r12 Service Pack 1 to this release on x86 and x64 systems.
All releases of the Arcserve Backup Agent for Microsoft SharePoint Server 2007
from Arcserve Backup r12 Service Pack 1 to this release on x86 and x64 systems.
All releases of the Arcserve Backup Agent for Virtual Machines from Arcserve
Backup r12 Service Pack 1 to this release on VCB Proxy systems.
All releases of the Arcserve Backup Agent for Open Files from Arcserve Backup r12
Service Pack 1 to this release on x86 and x64 systems.
Note: Unicode support is only applicable to VSS-based backup and restore
operations.
Arcserve Replication and High Availability agents on x86 and x64 systems.
Agent for Lotus Domino: all supported releases and service packs
Agent for Microsoft Exchange Server 2000 and 2003: all supported releases and
service packs
Agent for Microsoft Exchange Server 2007 on Windows Server 2003: all
supported releases and service packs
Agent for Microsoft Exchange Server 2007 Service Pack 1 on Windows Server
2008: r12
Agent for Microsoft SharePoint Server 2003: all supported releases and service
packs
Enterprise Option for SAP R3 for Oracle: all supported releases and service
packs
Image Option-based backups and restores: all supported releases and service
packs
Note: The Arcserve Backup Enterprise Module is a prerequisite component for
the Image Option.
Alert Manager
Alert options specified as Global Options in the Arcserve Backup managers and
utilities that follow:
Backup Manager
Restore Manager
Merge Utility
Count Utility
Purge Utility
BConfig.exe
Note: This component lets you configure the Arcserve Backup server when you
are installing or upgrading Arcserve Backup.
DBAConfig.exe
Note: This component lets Arcserve Backup configure database instances
during the installation process.
Discovery Configuration
Report Writer
SetupSQL.exe
Note: This component lets the installation wizard create the Arcserve Backup
database with Microsoft SQL Server when you are installing Arcserve Backup or
upgrading Arcserve Backup from a previous release.
Importing a host list from a text file with a file name that contains Unicode
characters when you install and upgrade Arcserve Backup, agents, and options
on remote systems.
Importing a host list from a text file with a file name that contains Unicode
characters when running Remote Agent Deployment.
Specifying file names and file paths as criteria for creating a Vault Schedule
using the Media Management Administrator using JIS2004 Unicode characters.
Specifying JIS2004 Unicode characters for the caroot password using the
Arcserve Backup Server Configuration Wizard. The Server Configuration Wizard
interprets Unicode characters as the question mark symbol "?," which is an
acceptable character for the caroot password. However, after you set the
caroot password using the Server Configuration Wizard, you will not be able to
change the caroot password from the Manager Console.
Sending Alert email messages with file attachments when the file attachments
are stored in directories that are named with Unicode characters.
Note: The file attachment itself can contain Unicode characters.
Renaming and editing XML content in the report template files using JIS2004
Unicode Characters. The generated reports will not display properly. The report
template files are stored in the following directory:
ARCserve_Home\template\reports
You cannot restore data at file level granularity from raw (full VM) backup data.
You cannot perform mixed mode backups, which consist of raw (full VM) weekly
backups and file mode daily backups.
You can protect Hyper-V VMs that are in a powered off state when you execute
Arcserve Hyper-V Configuration Tool.
Appendix D: Protecting Hyper-V Systems Using the Hyper-V VSS Writer 957
This release of Arcserve Backup for Windows Client Agent for Windows
The Arcserve Backup Client Agent for Windows must be installed in partition zero
(0) on the Hyper-V server machine. Partition zero (0) is reserved for the host
operating system and its applications. All other partitions, for example, partition 1,
2, and so on, are reserved for child partitions or virtual machines (VMs).
This release of Arcserve Backup for Windows Agent for Open Files
You must register the license for the Agent for Open Files for the Hyper-V host
system with the Arcserve Backup server.
Note: Optionally, you can register the license for the Agent for Open Files using the
license key for the Agent for Open Files for Virtual Machines on Windows.
If the Arcserve Backup server components are installed on the Hyper-V server
system, add the local Hyper-V server into the Backup Manager.
If the Arcserve Backup server components are not installed in the Hyper-V
server, add the remote Hyper-V server into the Backup Manager by completing
the steps that follow:
a.
From the Source tree in the Backup Manager, right click the Windows
Systems object and select Add Machine/Object from the pop-up menu.
The Add Agent dialog opens.
b.
From the Add Agent dialog, specify the name of the Hyper-V server in the
Host Name field or the IP address in the IP address field, and then click
Add.
After you add the Hyper-V server system into the Backup Manager, expand the
Hyper-V server to display the Microsoft Hyper-V VSS Writer as illustrated by the
following screen.
Appendix D: Protecting Hyper-V Systems Using the Hyper-V VSS Writer 959
The virtual hard disk in the backup cannot be offline mounted to retrieve specific
files.
The applications in the VM will not be aware that a backup, a restore, or both
occurred when you restore the backed up data.
Note: For more information about these limitations, see the Microsoft website.
You can offline mount the virtual hard disk from this backup to retrieve specific
files.
The VSS capable applications residing in the VM will detect that the backup or
restore of the VM is taking place, and they will participate in that backup or restore
process to ensure that the application data is consistent.
Open the Backup Manager, select the Source tab, and select the Microsoft Hyper-V
VSS Writer object.
All Hyper-V settings and virtual machines are specified for backup. If you do not
want to back up all of the VMs, expand the Microsoft Hyper-V VSS Writer object (to
display all servers) and clear the check mark next to the server that you do not want
to back up.
2.
(Optional) Right-click the Microsoft Hyper-V VSS Writer object and select Writer
Options from the pop-up menu.
3.
4.
5.
Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
The Hyper-V servers can be in an online state or offline state during the restore
operation.
The Hyper-V VSS Writer ensures that the backup data is properly restored to its
original location.
You do not need to perform additional steps during the restore or after the restore
is complete.
Using Arcserve Backup to restore Hyper-V server data, you can recover data in the
following scenarios:
You can restore Hyper-V server backup data to its original location.
Note: For information about using the VSS Writer, see the Arcserve Backup for Windows
Microsoft Volume Shadow Copy Service Guide.
Appendix D: Protecting Hyper-V Systems Using the Hyper-V VSS Writer 961
2.
From the drop-down list, select the Restore by tree method, expand the
Windows Systems object, browse to Microsoft Hyper-V VSS Writer, and specify
one or more VMs that you want to restore.
From the drop-down list, select Restore by session, browse to and specify a
session to restore.
3.
4.
Complete the required fields on the Submit Job dialog and click OK.
The job is submitted.
Note: After the restore is complete, the restored VMs will be in a Saved state. In other
words, the online restore places the VMs in an offline state when the restore is
complete. You must then start the VMs manually to bring them back online.
Glossary
archive job schedules
An archive job schedule lets you configure your archive job by using the Repeat Method
on the Schedule tab in the Archive Manager. The schedule lets you run an archive job on
a repeating basis.
archive manager
The Archive Manager lets you customize your archive jobs using filters, specifying
options, and setting schedules.
cloud connection configuration
A cloud connection is a user-defined configuration that contains the information that
Arcserve Backup needs to communicate with the specified cloud vendor. The cloud
connection helps ensure that your backup data is stored under the account that you
created with the cloud vendor.
cloud storage
A cloud storage is the final destination where your cloud devices are stored.
cloud-based device
A cloud-based device is a virtual, Arcserve Backup device that you create in association
with a Arcserve Backup cloud connection. The cloud-based device lets you direct
Arcserve Backup to store data with the cloud vendor specified by the Arcserve Backup
cloud connection.
data deduplication
Data deduplication is technology that allows you to fit more backups on the same
physical media, retain backups for longer periods of time, and speed up data recovery.
data mover server
Arcserve Backup data mover servers facilitate the transfer of data to local storage
devices. The storage devices include shared libraries and file system devices. Data
mover servers are supported on UNIX or Linux operating systems. Arcserve Backup
manages data mover servers from a single, centralized, primary server. Arcserve Backup
data mover servers function in a manner that is similar to member servers.
Grandfather-Father-Son rotation
A Grandfather-Father-Son (GFS) rotation is a backup schedule policy that uses daily
(Son), weekly (Father), and monthly (Grandfather) backup media sets (tapes).
media pool
A media pool is a collection of backup media (tapes) that is set aside for a specific job
and managed as a unit.
Glossary 963
member server
Member servers function as worker servers to a primary server. Member servers
process jobs dispatched by the primary server. Using primary and member servers you
can have a single point of management for multiple Arcserve Backup servers in your
environment. You can then use the Manager Console on the primary server to manage
its member servers.
multiplexing
Multiplexing is a process in which data from multiple sources is written to the same
media (tapes) simultaneously.
multistreaming
Multistreaming is a process that lets you divide backup jobs into multiple sub-jobs
(streams) that run simultaneously and sends data to the destination media (tape device
or file system device).
primary server
Primary servers function as a master server that controls itself and one or more member
servers and data mover servers. With primary servers you can manage and monitor
backup, restore, and other jobs that run on primary servers, member servers, and data
mover servers. Using primary, member, and data mover servers, you can have a single
point of management for multiple Arcserve Backup servers in your environment. You
can then use the Manager Console to manage the primary server.
staging
Staging is a method of protecting data that lets you back up data to a temporary data
storage location, and then based on selected policy options, migrate (copy) the data to
the final destination media.
The disk staging method utilizes a disk as the staging area and is commonly referred to
as Backup to Disk to Tape (D2D2T).
The tape staging method utilizes a tape library or a Arcserve Backup virtual tape library
as the staging area and is commonly referred to as Backup to Tape to Tape (D2T2T).
synthetic full backup
Synthetic Full Backup, or SFB, is a backup for Windows Client Agents that is executed as
part of a Normal backup with staging option, Deduplication backup with staging option,
or Deduplication backup that synthesizes, or combines, an initial full session and its
subsequent incremental backups into one session. Each synthetic full session becomes
the parent full session for the next SFB job (unless a real full backup session is executed
after the SFB session).
virtual tape library
A virtual tape library (VTL) is a hard disk that is configured to behave like a tape library.
You must configure the hard disk using Arcserve Backup.
writer
A writer is application-specific software that lets Arcserve Backup create shadow copies
of application-based data. A volume shadow copy is copy of the data that resides in a
volume at a specific point in time.
Glossary 965
Index
6
64-bit Windows platform support 40
A
Activity Log
data 329, 330, 668, 717
organizing 331
pruning 331
add Arcserve Backup users 94
add Windows users 93
administrative shared drives 133
Agent for Open Files, managing 189
Alert Manager 25, 707
configuration options 709
Append X days option 317, 318
Archive Manager
How to Specify Source Data for Archiving Using
the Classic View and the Group View 355
Options on the Archive Manager Destination Tab
358
Options on the Archive Manager Policies Tab
356
overview 353
archiving data
Advanced Options for Archiving 369
How Arcserve Backup Archives Data 351
overview 351
Submit Archive Jobs 351
Arcserve D2D
starting 128
Arcserve database
database protection job, about 613
database protection job, deleting 624
database protection job, modifying 614
database protection job, recreating 625
database protection job, starting 623
device records 605
error reporting 605
MS SQL index rebuilding 605
protecting 607
pruning 604
restoring 628
Arcserve Replication 25, 130
Audit Log Reports 672
B
backing up data
backing up data, deduplication 740
differential backup 307
entire nodes 193
incremental backup 307
multiplexing 106, 109, 189
multistreaming, defined 103
schedules and rotations 152
setting up jobs 140
submitting backup jobs 136
Backup Manager 25, 137
global backup options 154
bar codes 448
broadcast option 710
C
ca_auth command 36, 37, 538, 539
ca_devmgr command 204, 228
ca_jobsecmgr command 38
ca_log command 330
ca_mmo command 464, 465, 469, 474
cabatch command 35
CAReports command 679, 681
catalog database
about 650
enabling media pool maintenance 607
enabling the catalog database 653
Central Agent Admin 719
central management
administering Arcserve servers 52
managing devices 52
managing jobs 47
managing licenses 53
managing the ARCserve database 49
monitoring jobs 48
using alerts 51
using job history 55
using logs 50
using reports 50
change password, system account 520
change the Arcserve system account password 573
changing an ARCserve computer name
about 542
Index 967
D
database
agents 133, 257
Database Engine 491, 514
Database Manager 25, 604
MS SQL configuration 658, 661
MS SQL index rebuilding 605
ODBC data source configuration 660
pruning 328, 331, 604
Database Manager 25, 604
database protection job
about 613
deleting 624
modifying 614
recreating 625
starting 623
decryption, data 110
deduplication
configure groups option 393
create device 737
defined 731
modify device 387
remove device 387
demote a primary server to a member server 568
demote a primary server to a member server
568
demote a primary server to a member server
(MSCS clusters) 927
demote a primary server to a member server
(NEC cluster) 936
Destination Tab for Archiving 358
Device Configuration 210
E
ejecting media 396, 400
email option 712
encryption algorithm 111
encryption, data,
about 110
at the agent server 113
during backups 114
during migration 114
encryption, data, with deduplication 744
engines
about 491
Database Engine 491, 514
Job Engine 491, 500
service state icons 493
status 492
Tape Engine 491, 503
Enterprise Module 39
equivalence 36, 539
erasing media 396, 398
options described 398
error log, devices 605
exclude objects from jobs 302
exclude the Arcserve database from jobs 303
F
failover 910
G
GFS media pools 449
GFS rotations 122, 307, 449, 451, 452
global backup options 154
advanced backup options 156
alert options 154
backup media options 164
global backup options, encryption options 159
job log options 184
media exporting options 155
operation options 167
verification options 166
Volume Shadow Copy Service options 162
Global Options for Archiving 359
Advanced Options 369
Job Log Options 366
Media Options 360
Operation Options 362
Pre/Post Options 364
global password changes 38
global restore options 271
backup media options 271
destination options 272
job log options 277
pre/post options 276
group view, Backup Manager 140, 145, 306
H
home page 23
I
importing and exporting media 404
installation considerations
Microsoft SQL Server 658
interact with the desktop 512
inventory slots 404
inventorying slots 407
Index 969
J
Job Log Options for Archiving 366
job queue, restoring 557
Job Scheduler Wizard 341
schedule a custom report, Job Scheduler wizard
679
job scripts 342
Job Status Manager 25, 319
Job Detail tab 333, 668
Job Log tab 333
job queue 323
job status, types 325
multiple jobs, managing 322
Tape Log tab 332, 668
job status, types 325
L
labeling 404
library functions 404
cleaning tape heads 404, 412
importing and exporting media 404
inventory slots 404
mounting and dismounting media 404
online and offline libraries 404, 415
library groups
assigning slots 420
creating 419
deleting 423
removing slots 423
renaming 424
licensing
managing 523
release licenses 525
log in to Arcserve Backup 92
logs 713
Job Log data 668
Tape Log data 668
M
magazines, mounting and dismounting 409
Manager Console
opening 90
managing domain servers 538
managing jobs
Job Detail tab 333, 668
Job Log data 668
Job Log tab 333
N
navigation bar 23
NEC clusters
change cluster domain 934
change database 936
demote member server 936
disable cluster scripts 938
enable cluster scripts 941
failover support 914
promote member server 936
stop cluster groups 937
stop HA service monitoring 933
network interface cards, configuring multiple 526
node tier 521, 728
O
online and offline libraries 404, 415
Operation Options for Archiving 362
Optimize Restore feature 204
options
Compare Utility options 33
Count Utility options 33
Discovery Configuration options 591, 592
filtering options 314
local backup options 134, 152
Media Assure & Scan Utility options 32
options, deduplication device group 393
Purge Utility options 34
staging options 210, 212, 225, 226, 227
P
password changes, global 38
password management 79
pfc command 126
Policies Tab for Archiving 356
Pre/Post Options for Archiving 364
preferred shares, add computers 119
Preflight Check Utility 126
promote a member server to a primary server 565
promote a member server to a primary server
565
Q
Quick Search 76
Quick Start menu 23
quorum disk 913
R
raw backup
raw backup, definition 761
raw backup, enabling 765
raw backup, licensing 761
raw backup, naming convention 764
raw backup, performing backup 765
raw backup, restoring, alternate location 767
raw backup, restoring, another device 768
raw backup, restoring, original location 767
rebuild media 396, 401
register virtual clusters as domain member servers
561, 577
removable drive support 427
removable media support 425, 426
renaming backup servers
member server 548
primary server 543
stand-alone server 553
replacing devices 417
Report Manager 25, 669, 671
custom reports 671
report categories 672
schedule a custom report, Report Manager 679
standard reports 671
Report Writer Utility 34
creating custom reports 680
Restore Manager 25, 257
global restore options 271
restoring data
destination options 269
duplicate backup sessions 265
Smart Restore 204, 265
staged backups 280
retensioning media 396, 399
roles
about 83
add 97
Index 971
remove 98
rotation 471
creating a rotation 456
deleting a rotation 474
modifying a rotation 474
rotations 301, 307, 318
RSS Feeds 25
run as Administrator 270
S
SAN
backup plans 846
benefits 846
control job run time 854
create shared device groups 851
data backup and restoration 852
device management 853
environment 844
how the option works 844
installation 849
installation prerequisites 847
licensing 843
media management 853
operating system compatability 847
reports and logs 854
server management 846
terminology 846
troubleshooting 892
using the option 850
virtual libraries 855
save sets 447
scanning devices 396, 402
schedule a custom report, Job Scheduler wizard
679
scheduling jobs 301, 307, 317, 318
backup jobs 152
restore jobs 269
scratch sets 447
Secure Key Manager integration 433
serial numbers and bar codes 448
Server Admin 25
Server Configuration Wizard
about 559
change the Arcserve database application 662,
667
change the domain administrator password
572
demote a primary server 568
T
Tape Engine
changing the system account 520
configuration 503, 504, 507
location, log file 509
manage the size of the log file, Circular Logging
510, 511
message log options 504
pruning, tape log file 511
Tape Log data 668
Tape Log tab 332, 668
tape movement, scheduling MM Admin
deleting a schedule 468
tape staging
architecture 230
migration policies 233
miscellaneous policies 235
overview 232, 233
postscripts 220
submit a backup job 236
tape usage optimization 439
tapecopy command 228, 265, 309
tier 521
V
vault criteria descriptor (VCD) 469
creating a VCD 469
deleting a VCD 469
modifying a VCD 469
vault criteria descriptor object 460
vaults 466
creating a vault 466
deleting a vault 468
modifying a vault 467
virtual libraries, configuration 380, 418
VMware 39
W
wildcards 312
Windows user authenication 89
Windows-powered NAS 346, 347
wizards 23
Diagnostic Wizard 682
Job Scheduler Wizard 341
Server Configuration Wizard 559
WORM media 428
U
Unicenter TNG option 710
unicode characters 949
USB storage devices 396, 402, 424
User Profile Utility
adding or deleting a user 554, 555
assigning a user to a group 556
changing a user password 555
user profiles
administrator profile 36
equivalence 36, 37
utilities 23, 30
Compare Utility 33
Count Utility 33
Diagnostic Utility 682
Media Assure & Scan Utility 32
Index 973