VERITAS Backup Exec for Windows
Last Updated: November 2, 2004
This document contains release notes for Backup Exec and
contains information that may not be in the Administrator's Guide. The
information in this document is more current than information in the
Administrator's Guide. If information in this file conflicts with the
Administrator's Guide, the information in this file is correct.
Administrator's Guide Addendum contains additions and changes to text in
the Administrator's Guide. You can access the Addendum from the Backup
Exec Information Desk. On the navigation bar, click Overview.
From the Overview pane, click Information Desk. In the Documentation
section, click View VERITAS Backup Exec Administrator's Guide
For the most current information on VERITAS Software
products and services, please visit our website at
Back to top
What's New in This
Policies provide a method for managing backup jobs and strategies.
Policies contain job templates, which are job attributes that define
how and when Backup Exec processes a job. Templates specify the
devices, settings, and schedule for a job, but do not include the
selections to be backed up. To create jobs, combine a policy with a
selection list. Backup Exec offers four types of templates: backup,
duplicate backup data, export media, and synthetic backup (the
Advanced Disk-based Backup Option is required to create synthetic
backup templates). For more information on
policies, click Overview on the navigation bar and select How to
use policies from the Getting Started section of the Information
Desk. Backup Exec provides a policy wizard for
grandfather/father/son media rotation.
Availability windows for selection lists
You can set a time range for when resources in a selection list will
be available for backup. You can set a default availability window
for all resources, or set the availability window for each
individual selection list you create.
Create and edit custom filters for the current jobs view, the job
history view, the active alerts view, and the alert history view to display only the information that you specify. These
are filters that you name and save for later use, so that you can
sort large lists of objects depending on your specific criteria.
Using filters to specify criteria for the data you want to view
makes Backup Exec data more manageable when you have a large
Using filters, whether standard or custom, will
also shorten loading times and prevent server timeouts
that can happen when a very large number of items are loading.
Filters can be applied while Backup Exec is loading the records. For
example, you can apply a filter to job histories while Backup Exec
is loading the histories, and only the histories that meet the
criteria you selected will appear.
Set thresholds for recovering stalled jobs
If the Backup Exec services become unresponsive, you can enter the
number of seconds before active jobs are considered stalled and the
number of seconds that jobs can be stalled before they are
recovered. After this number of seconds is exceeded, the jobs are
recovered by Backup Exec. Any error-handling rules that have been
enabled will apply to the recovered jobs.
You can specify dates for media sets to send media to and
return media from vaults. This feature enables you to update the
vault with the media location, and generates a report so that you
can physically collect the media and take it to or return it from a
Backup Exec for Windows Server Environment Check
You can select from the installation program to run this utility before Backup Exec is installed.
This utility checks if the
media server has the proper system environment (operating system
version, service packs, etc.), checks 3rd party application versions
(Internet Explorer, ODBC, MDAC, etc.), and removes incomplete
uninstalls of previous VERITAS products. The Environment Check
utility does not remove old installations of Backup Exec or any
other VERITAS products.
VERITAS recommends running the Environment Check utility on the
media server and all remote computers that are to be protected. The
Environment Check utility must be run locally; it can be run from
the installation CD's pre-install checker on remote computers
that meet operating system requirements for the media server.
Use audit logs to examine and review information about operations
that have been performed in Backup Exec. The audit log displays the
date and time of the activity, who performed it, what the activity
was, and a description of the activity. You can save audit logs as
files, and groom audit logs as part of the Backup Exec database
Custom error-handling rules
In addition to applying a default error-handling rule to a group of
similar errors, or an error category, you can create a custom
error-handling rule for one or more specific error codes in an error
category. You can also create an error-handling rule directly from a
history record by right-clicking on a history record in the job
EFI system partition backup and restore
The Extensible Firmware Interface (EFI) is required to boot Windows
on all Intel Itanium 64-bit computers. You can back up and restore
EFI system partition data using Backup Exec on Intel Itanium 64-bit
computers. EFI system partition data can be backed up only on remote
computers using the Backup Exec Remote Agent.
Job deletion for run once jobs
The options for deletion of run once jobs after
they have completed successfully can
help manage your job lists. These options, which can be set by
selecting Tools, Options, and then Schedule,
allow you to have Backup Exec automatically delete run once jobs
after they run or after they run successfully. The default setting
is Do not delete jobs.
Back to top
This release of Backup Exec includes the
following new features and capabilities in the agents and options:
Central Admin Server Option
The new Backup Exec for Windows Servers Central Admin Server Option
(CASO) enables you to maximize your Backup Exec for Windows Servers
investment by providing centralized administration and delegated job
processing functionality for existing or newly configured Backup
Exec for Windows Servers media servers in your storage environment.
The Central Admin Server Option transforms your stand-alone Backup
Exec media server-based environment into a centrally managed data
protection enterprise, built on the following concepts:
Use of a Backup Exec for Windows Servers
media server as a central administration server.
Use of the Backup Exec Administration Console
to monitor and manage distributed backup environments, which
consist of the central administration server and managed media
servers. Through the Backup Exec Administration Console, you can:
Monitor active, scheduled, and completed
Cancel jobs and start scheduled jobs.
Pause and resume media servers and devices.
Respond to alerts.
View CPU, OS, and memory statistics of a
Backup Exec server.
Run the server diagnostics utility and view
Determine the version of Backup Exec
installed on a server.
Report on data across media servers.
Push install media servers.
Use of the central administration server to store catalogs,
device and media information, jobs, and selection
lists. Job log information generated by the various Backup Exec
media servers can also be stored on this central server.
Use of your existing storage hardware using media server pools and
job delegation concepts, which enable you to delegate the
processing of backup and restore jobs to various Backup Exec
media servers on your network.
Use of a scalable architecture to handle the future growth of
data on your network.
Remote Agent for Linux/Unix Servers
The new VERITAS Backup Exec for Windows Servers Remote Agent for
Linux/Unix Servers (RALUS) is installed as a separate, add-on
component that enables Windows Server network administrators to
perform backup and restore operations on Linux and Solaris
hosts that are connected to the network. This agent must be running
on these computers before backup or restore operations can be
performed. The following versions are supported:
Red Hat Advanced Server 2.1
Red Hat Enterprise Linux AS, ES, WS 3.0
SuSE Linux 8.0, 8.1, 8.2
SuSE Linux Enterprise Server 8
Solaris (SPARC) 8,9
United Linux LSB 1.0 (Includes SuSE Linux Enterprise Server 8)
64-bit IDR. IDR is now available for
computers that use Intel 64-bit Itanium processors. With 64-bit
IDR, you can only create bootable CDs and perform only remote
Alternate operating system media path. When you create bootable
tape or CDs, you must provide the Windows operating system
files. In previous releases of Backup Exec, IDR only accepted
the Windows operating system installation CD. In this release,
you can enter a path to the Windows operating system files
locally or on
the network or to existing .iso image files. In addition, you
can use MSDN-style CDs.
Offline protection. If a computer crashes before you create
disaster recovery media, IDR can still recover the computer if a
full backup that includes information needed to restore the
system was made prior to the crash.
Plug-and-play tape driver support is now available.
The updated Agent for Microsoft SharePoint Portal Server includes
support for all of the components of Microsoft SharePoint Portal Server 2003.
These components include portal sites, Windows SharePoint Services
sites, web storage system-based document libraries, Single Sign-on,
and the configuration database in single-server, server farm, and
shared service deployments.
Advanced Disk-based Backup Option
The VERITAS Backup Exec for Windows Servers - Advanced Disk-based
Backup Option (ADBO) is installed as a separate, add-on component of
Backup Exec for Windows Servers. The Advanced Disk-based Backup
Option provides the following features:
Synthetic backup. This policy-driven feature enables a backup to be assembled, or
synthesized, from baseline backups and subsequent incremental backups. This feature
eliminates the need to run full backups, and because the synthesis
is performed on the Backup Exec media server without accessing the
remote computer, the overall backup window and the network bandwidth
requirements are reduced.
Offhost backup. This feature enables the backup operation to be
moved away from the remote computer, or host computer, to a Backup
Exec media server, reducing network bandwidth requirements. Moving the backup from the remote computer to a
media server enables better backup performance and reduces the load
on the remote
computer as well.
The Offhost backup option requires that both the media and remote
servers have the Windows 2003 Enterprise Edition or Data Center
The Full - Back up files - Archive
the files (delete files after successful copy) Backup Method is
not supported when using the Offhost backup feature; the backup job will fail with the error ''0xe000848c -
Unable to attach to a resource."
Remote Agent Monitor
Use the Remote Agent Monitor to check if a backup or restore job is
running on the computer. The Remote Agent Monitor is installed when
the Remote Agent is installed on a remote computer. You can set how
often the Remote Agent Monitor checks for activity on the remote
computer, and you can set an option to start the Remote Agent
Monitor whenever you log on. Enables you to activate debug logging
for a variety of Backup Exec services.
Back to top
Backup Exec Installation Notes
The following are the minimum system requirements for
the Backup Exec media server and CASO server (following installation of
Backup Exec or certain Backup Exec options, a reboot may be required):
Microsoft Windows 2000 Professional, Windows 2000
Server, Windows 2000 Advanced Server, or Windows 2000 Datacenter
Microsoft Windows XP Professional Service Pack 1 or
Microsoft Windows Server 2003 family
The following operating systems are supported, but not
Internet Explorer 6.0 or later.
Pentium class system and later compatible processors
Backup Exec Media Server
Backup Exec CASO Server (depends on number of media
servers being supported)
Required: 512 MB RAM.
Recommended: 1 GB
Note: RAM requirements may vary depending on
operations performed, the options installed, and the specific system
20 MB above the Windows recommended size for total
paging file size (total for all disk volumes)
To view or set the paging file size:
On Windows 2000, click Start, point to
Settings, and then click Control Panel. Double-click
System, click the Advanced tab, and then click
Performance Options. Click Change to reset the paging
file size for all drives.
On Windows Server 2003 and Windows XP, go to
Control Panel, double-click System, click the Advanced
tab, and then in Performance, click Settings. Click
the Advanced tab, and then in Virtual memory, click
Change to reset the paging file size for all drives.
Backup Exec media server
550 MB hard disk space required after Windows is
installed (typical installation)
Network interface card or a virtual network adapter
(Optional) Printer supported by Microsoft Windows
(Recommended) A mouse
(Optional for pager notification) Modem supported by
Backup Exec requires at least one storage media
drive and/or robotic library. Removable storage devices and
non-removable hard drives can also be targeted for backups. Refer to
the Backup Exec hardware compatibility list for a complete list of
devices that are supported. Support for multi-drive robotic
libraries is available separately. Refer to the Microsoft Windows
Hardware Compatibility list for a complete list of supported SCSI
Back to top
Messages and Tips
"Either there is no default mail client or
the current mail client cannot fulfill the messaging request.
Please run Microsoft Outlook and set it as the default mail
Do one of the following:
If Microsoft Outlook is not installed, run
the installation program and set up a profile. When prompted to
set Outlook as the default, respond Yes.
If Microsoft Outlook is installed, set
Outlook as the default mail client. Open Internet Explorer,
click the Tools menu, and then click Internet Options.
Click the Programs tab, and in the E-mail field, choose
Microsoft Outlook, and then click OK.
During a remote, or push, installation of Backup Exec, when prompted
to enter an account for Backup Exec to use as its service account,
enter an existing account or specify a new account (if you are
creating a local account). If you specify a domain, you
must enter an existing account. New accounts are not granted proper
A second attempt at a remote Backup Exec
installation due to a reboot request or remote installation failure
may result in one of the following error messages if a different set
of connection credentials is used within the same remote
installation session: "The credentials supplied conflict with
an existing set of credentials" or "Multiple connections
to a server or shared resource by the same user, using more than one
user name, are not allowed. Disconnect all previous connections to
the server or shared resource and try again."
If this occurs, use the original set of connection
credentials when retrying the remote installation, disconnect all
previous connections to the remote computer and try the installation
again, or exit the current remote installation session and launch a
"Attempting to connect to server <server name>
failed with the following error:
Unable to connect through Remote Install object.
Will not check remote credentials"
Perform the following steps:
Cancel out of the current remote installation
Navigate to directory path "%ProgramFiles%\Common
Remove the Read-Only file attribute from the
And retry the remote installation.
"The Windows Installer service cannot update the
system file mfc42u.dll because the file is protected by Windows. You
might need to update your operating system for this program to work
The mfc42u.dll file is language-specific. Backup
Exec attempts to update the file because of language differences.
The existing mfc42u.dll file on the computer is the correct file
needed by the Backup Exec installation. There is no need to update
the operating system. Click OK to continue with the
After installing Backup Exec
on a computer running Windows Server 2003, you might receive an
error message that the Network Load Balancing Service failed to
start. Microsoft reports the cause as: "Although Network Load
Balancing (NLB) is not currently installed, some NLB registry keys
might be present in the registry". Although Microsoft Knowledge Base
Article 268437 describes the problem as applying to Windows 2000
Advanced Server, the fix also works for Windows Server 2003.
Microsoft Knowledge Base Article 268437 can be found at:
After installing Backup Exec on a computer
running Windows Server 2003, a message displays during driver
installation that indicates the drivers about to be installed have
not gone through the Microsoft Windows Hardware Quality Labs (WHQL)
program. The VERITAS drivers go through a similar qualification
process. VERITAS recommends that you install the VERITAS drivers.
Use the following steps to make the necessary policy setting change:
Incorporate the driver installation into
Setup by using the DriverSigningPolicy=ignore setting. (See
Implement a driver signing policy in a
Windows 2000, Windows XP, or Windows Server 2003 Domain by using
Under Administrator Tools, in the
Active Directory Users and Computers snap-in,
right-click the domain root, click Properties, and
then click the Group Policy tab.
Click the default domain policy, and then
Expand Computer Configuration, expand
Windows Settings, and then expand Security
Settings. Expand Local Policies, expand
Security Options, and then modify Device: Unsigned
driver installation Behavior to the setting that you
want to use. Select "silently succeed".
Note: This policy is a domain-wide policy.
Note: To set the policy on the local computer
where no Domain policy is applied, click Start, point to
Settings, click Control Panel, and then
double-click System. On the Hardware tab, click
Driver Signing..., and then select a verification setting.
Note: Windows XP queries for the policy and
ensures that it matches the entry that is stored for it in an
alternate location. However, if the operating system determines
that the Driver Signing Policy registry key has been
tampered with, the operating system automatically resets to the
correct values (or the default value, which is Warn and
Ignore for non-driver signing policy).
Note: For silent installations, the /td: option
to install VERITAS tape device drivers will be ignored unless
your driver signing policy is set for Ignore.
Reference Microsoft article:
You might be required to restart the computer when
you install certain options. If you selected the Advanced Open File
Option or Enable Robotic Library Support, you must restart the
computer when installation is complete. You might need to restart the
computer after you install tape device drivers or MDAC.
If you are installing Backup Exec for Windows
Servers into a Microsoft Windows 2000 Service Pack 2 or prior
Cluster Server (MSCS) environment, underscore characters are not
allowed for the Network Name resource (the virtual server name) in
the Backup Exec Cluster Configuration Wizard. Underscore characters
are allowed if you are running Windows 2000 Service Pack 3 or
To evaluate the Remote Agent for Linux/UNIX
1. Install Backup Exec for Windows Servers in evaluation mode.
2. Using the Remote Agent for Linux/UNIX Server (RALUS) CD, install
the RALUS agent on a supported Linux/UNIX system.
If you are using RALUS on Linux servers, the
following Linux packages are pre-requisites:
When you are
connecting to the ExecView server through a browser, if you are
prompted to install the latest Java Runtime Environment you must
answer Yes in order to view the ExecView Console.
During installation of Backup Exec and ExecView
on a Windows XP SP1 system, you may see the following message: "Java
(TM) update failed to apply changes to your system"
To remedy the situation, download Windows XP
Patch <Q814995_WXP_SP2_x86_ENU.exe> from
You can also try manually installing Java from
either the Backup Exec or the ExecView installation CD. Use Windows Explorer to
navigate to WinNT\Install\JRE and run jresetup.exe. After installing
Java, re-run setup for Backup Exec and/or ExecView.
If you install the ExecView Communications Module
(ECM) on a machine using an ATI, Matrox, Intel, or NeoMagic video
adapter, you may receive a fatal exception error message on a blue
screen. The error will be similar to the following:
*** STOP: 0x00000050 (0XE350D010, 0X00000000, 0XFOEF444C, 0x0000001)
PAGEFAULT_IN_NONPAGED_AREA *** Address F0EF444C base at F0EB8000,
DateStamp 3C6C21F - ati3d1ag.dll
To resolve this issue on a Microsoft Windows 2003 computer, reduce
the hardware acceleration setting by performing the following steps:
Click Start, click Control Panel,
and the double-click Display.
On the Settings tab, click Advanced.
On the Troubleshoot tab, move the
Hardware acceleration slider all the way to the left (to the None
position), and then click OK.
To resolve this issue on a Microsoft Windows 2000
computer, reduce the hardware acceleration setting by performing the
Click Start, point to Settings,
click Control Panel, and then double-click Display.
On the Settings tab, click Advanced.
On the Troubleshooting tab, move the
Hardware Acceleration slider all the way to the left (the None
position), and then click OK.
Note: If the issue continues to occur, on the Settings
tab, reduce the Colors of the Display Properties
to 256 Colors, and then click OK.
If you are installing Storage Foundation for
Windows Servers High Availability Administrative Console (SFWSHAAC)
components on the Central Admin Server, you must reboot the Central
Admin Server after the installation completes.
For information and detailed procedures for
installing Backup Exec with the Central Admin Server Option (CASO),
setting up managed media servers, and using Backup Exec in a CASO
environment, see your VERITAS Backup Exec for Windows Servers
- When remotely installing RALUS over SSH protocol, the following
setup steps must be performed to enable temporary SSH trust
relationships between machines involved:
- On the system the agent is being installed from (ssh client), run:
ssh-keygen -b 1042 -t dsa
accepting the defaults, including no passphrase. This will create
an ssh key for your system in the file /.ssh/id_dsa.pub
- On each remote computers where packages will be installed (ssh
server), check to see whether a /.ssh/authorized_keys2
file exists. If the file does not exist, copy the /.ssh/id_dsa.pub
file on the ssh client to /.ssh/authorized_keys2 on each
ssh server system. If the file does exist, create a backup of the /.ssh/authorized_keys2
file and append the contents of the /.ssh/id_dsa.pub file
to the original.
- On each remote computer where packages will be installed (ssh
server) check that the sshd_config file (usually found in
/etc/ssh or /etc/opt/openssh) on each ssh server
contains the uncommented keyword:
- If this keyword is not found or is set to no,
add the keyword and restart sshd. An ssh start/stop script should
be located within /etc/init.d.
- The client must issue one ssh command to each ssh server so that
its key fingerprint is received, and it becomes a known host.
- At this point, successive ssh issued commands will be answered
without prompting for a password, passphrase, or confirmation. You
can now successfully run the agent install script using the -usessh
option. When the installation is completed, the backup copies of /.ssh/authorized_keys2
can be restored on each server.
Back to top
VERITAS Management Pack for MOM
The VERITAS Management Pack for
Microsoft Operations Manager (MOM) will provide tight
interoperability between VERITAS Backup Exec software and Microsoft
Operations Manager, improving operations management and efficiency,
while simultaneously maximizing application availability, lowering
costs and helping meet business objectives. The VERITAS Management
Pack for MOM can be downloaded from http://seer.support.veritas.com/docs/271030.
Back to top
Uninstalling Backup Exec
When uninstalling Backup Exec, if debug logging
has been enabled, the following error message may be
displayed: "Error 1306.C:\Program Files\VERITAS\Backup
Exec\NT\Logs\Log_MsiExec.txt. Another application has
exclusive access to this file. Please close all other applications
and retry the operation. "
To disable debug logging, set the registry key
HKLM\VERITAS\Backup Exec\Debug\BEMSDKLog to 0.
Back to top
The Template Definition Usage Report
job is no longer supported in this release. If you created a
scheduled Template Definition Usage Report job from an older version
of Backup Exec, upgrade to this version, and then run the scheduled
report job, the job fails.
Back to top
Settings Not Migrated
when Upgrading Backup Exec
Notifications (email, pager, etc.).
MMC User defined filters.
Jobs for which the Retry after option
was selected are put on hold.
Backup Exec password database option.
Note: User-defined selections must be
recreated, and the credentials used to connect to resources must
be re-entered, otherwise Backup Exec will attempt to connect to
the resource using the System Logon Account.
Back to top
NSE Migration Issues
- If you are upgrading a Backup Exec Network
Storage Edition (NSE)
computer and the upgrade fails, the system may be left in an
inconsistent state. Recover your original NSE configuration and
reattempt the install/upgrade/migration. For more information,
refer to your NSE Administrator's Guide information on master server
- If you are upgrading from NSE, the
Backup Exec v10.0 logon account wizard (which is part of the first
time startup wizard), may list the logon account <Default Backup
Account> which was the default logon account in NSE. This account
will not work with this version of Backup Exec. You must: create a
new logon account, use other accounts migrated from NSE, or use the
Backup Exec 10.0 System Logon account.
- When upgrading from NSE in a cluster,
the NSE directory on the local drive (i.e. C:\program files\Backup
Exec NSE) is not deleted. This directory can be manually deleted
provided Backup Exec 10 is not installed in this directory.
- Prior to upgrading from NSE to Backup
Exec, you must manually uninstall the NSE WMI performance counter
provider and the NSE WMI SNMP provider. For more information on how
to uninstall the providers, refer to the NSE 8.6 Administrator's
- If you upgrade your computer from
Windows 2000 to Windows 2003, you must edit selection lists and
replace the System State selection with the Shadow Copy Components
selection. Refer to "Protecting Upgraded Windows Server 2003
Resources" in the backup chapter of your VERITAS Backup Exec
for Windows Servers Administrator's Guide.
- Examine the install logs for details
regarding the data migration process.
- The following functionality is not
fully migrated due to differing implementations of these features
from NSE and/or BE 8.6:
- Unprotected resources
- Disabled resources
- Resource types
- Global Excludes and Task Level
- Software compression at the
- Prevent other simultaneous backups
of this resource
- Audit Logs
- Alert History
- Notifications and Recipients
- Virus scan is no longer supported by Backup
- Intelligent Image Option (IIO)
is no longer supported by Backup
- Remote agent priority at the resource
level does not migrate to Backup Exec.
- Empty Policy does not migrate to
Hardware and Driver Notes
The compatibility list contains the latest
information about supported hardware and software and is updated
regularly. Before installing or upgrading Backup Exec, review the
current compatibility list to confirm the compatibility of your
hardware and software. You can find the current compatibility list
on the VERITAS Support website at
http://support.veritas.com/rd/bews-compatibility.htm. If you
don't find your hardware or software listed or if you have questions
about the information in the compatibility list, please contact
You must remove media from all tape drives and
reboot after installing VERITAS Device Drivers in order to properly
load the drivers. If a reboot is not performed, some devices may be
incorrectly discovered and displayed in Backup Exec. If this has
occurred, reboot and then delete any offline devices to correct the
HP (previously Compaq) hot swap support using
VERITAS tape class drivers requires tapeinst.exe to be run locally
after Backup Exec is installed.
If you are using an Hitachi 9970 and attempt to
protect a Microsoft Cluster Server (MSCS) resource using the Advanced Disk-based
Backup Option (ADBO), you may receive the error message "The
job failed with the following error: A failure occurred querying the
Writer status." To correct this problem, do the following:
Make sure the RM Shadow Copy Provider for
Volume Snapshot Service is present and running.
If the service is not running, run
RMVSSPRV.exe from c:\horcm\tool.
If the service is still not running, contact
Hitachi for support.
Back to top
General Backup Exec Notes
For the Japanese version only: There is a known
issue with viewing SMTP email notification message. Japanese
characters in the Subject line using Microsoft Outlook Client
2000 or 2002 may not appear properly. Workarounds include using
Microsoft Outlook Client 2003 or Microsoft Outlook Express for
viewing the mail messages.
When browsing remote backup or restore
selections, you may receive an informational message stating that
the Backup Exec Remote Agent must be installed. This message may
appear even though the agent is installed. The message can be safely
ignored by clicking the OK button and proceeding with the backup or
restore job creation.
Windows 2003 systems may display a security
warning when the Job Summary is displayed after submitting a job.
This is caused by the Internet Explorer Enhanced Security
Configuration option that is installed by default on Windows
2003 systems. On the warning screen, select to add the site to your
Trusted sites zone to prevent the warning from being displayed on
Running Windows 2003 Service Pack 1 or Windows XP
Service Pack 2 results in the following:
You will not be able to push install to
remote Windows 2003 Service Pack 1 or Windows XP Service Pack 2
Performing remote backup and restores may require manual configuration.
Running the Remote Agent for Windows or
NetWare servers automatically creates an exclusion in
the Microsoft firewall.
Using ExecView will require manual
For more information refer to the following
Additional information can also be found on the
The Synthetic Backup feature supports all
standard file systems that can be backed up using either the Remote
Agent for Windows or NetWare Servers or the Remote Agent for Linux
and Unix Servers; however, the synthetic backup feature does not support
NetWare. System State and EFI partitions are also supported. Databases, such as SQL
and Exchange are not supported.
NetBIOS over TCP must be enabled on both the
media server and systems running Remote Agent for Windows Servers in
order for Backup Exec for Windows Servers to operate correctly. This
can be configured by your network administrator via DHCP or you can
enable it by following these steps:
Start the Network Connections control panel
Open the properties for the appropriate
Open the properties for the Internet Protocol
Select the Advanced button from the General
tab on the Internet Protocol (TCP/IP) Properties dialog
Select Enable NetBIOS over TCP/IP from the
WINS tab on the Advanced TCP/IP Settings dialog
The offhost and Storage Foundation for Windows
high availability integration features require that you are running version
4.2 of VERITAS Storage Foundation for Windows. If you have an earlier build, please be sure to
get the listed build from the web site.
Doing incremental/differential backups with
Offhost backups using the Windows Change Journal is not supported in
this release of Backup Exec. The modified time backup can still be used.
This release provides support for the following
offhost backup providers:
VERITAS Volume Snapshot Service Dynamic Provider
Hitachi RM Shadow Copy Provider
When protecting a server running VERITAS Cluster
Server version 4.1 and a virtual file share resource is manually
failed over or taken offline while backup job preprocessing is occurring, the backup job will
Port 3527 is reserved by Backup Exec. If this
port is in use by another application, install will complete but one
of Backup Exec's services will not start and Backup Exec will not
load. Finding the application that is using port 3527 and
reassigning that application to another port is preferred; however,
you can change the port used by Backup Exec if necessary .
To change the port Backup Exec uses:
RegEdit or RegEdt32, navigate to
2. Right click Server, select New and then
select DWORD Value.
3. Name the key MQPortID, and
enter the value of the new port that Backup Exec should use
Note: All MMS and CASO servers
should be configured to use the same port you assigned for MQPortID.
4. Restart Backup Exec's services
The Device Summary Report lists Backup-to-Disk
devices. However, statistics for Backup-to-Disk devices are not
included on the report because Backup Exec does not track statistics
for those devices.
The ArcServe Tape reader supports generic file
system backups, but does not support Exchange, SQL, system state,
compression or encryption.
If you receive error 1065 "Database specified
does not exist", after installing a managed media server and
specifying a central administration server, perform the steps listed
This problem is usually caused when UDP traffic
is blocked on the network somewhere between the CAS and the MMS.
To determine the TCP/IP port for the Backup Exec
central administration server database:
On the server where the Backup Exec central administration
server database is installed, open a command prompt and enter the following:
cd /d "%ProgramFiles%\Microsoft SQL
In the SQL Server Network Utility, choose the
SQL instance where the Backup Exec central administration server
database is installed (BKUPEXEC by default).
Under 'Enabled Protocols:', highlight TCP/IP,
then click 'Properties...'. Record the port number displayed in
'Default Port:'. This is the port that the SQL instance is
listening on. Close the SQL Server Network Utility.
To set the TCP/IP port on the managed media
server (needs to be performed on every MMS that is exhibiting the
On the Backup Exec managed media server, open
a command prompt and enter the following:
cd /d "%SystemRoot%\system32"
In the SQL Server Client Network Utility,
ensure that TCP/IP is listed under Enabled protocols by order. If it is not, highlight it under
and click Enable.
Switch to the Alias tab, and click Add.
Under Network libraries, choose TCP/IP.
In the Server name box, type the SQL
Server and instance name where the Backup Exec Central
Administration Server database is installed, in the format
Click to clear the Dynamically determine
In the Port number box, type the port
number that was recorded previously for the Backup Exec Central
Click OK to close the Add Network Library
Configuration dialog, and OK again to close the SQL Server
Client Network Utility.
For more information about using Backup Exec
across firewalls, refer to your VERITAS Backup Exec for
Windows Servers Administrator's Guide.
Mount points are not supported for replication by
VERITAS Replication Execwhen VERITAS Volume Manager volumes are
mounted in file servers, Microsoft SQL servers, and Microsoft Exchange
VERITAS Volume Replicator (VVR) is used for replication and mount
points are used to mount
different volumes, assign the same drive letters at both the primary
and secondary sites otherwise databases cannot be mounted at the
There is a known issue with ExecView not being
accessible from the main Backup Exec user
interface after being launched. If you are on the Overview
tab after launching ExecView successfully and change to either the
Information Desk or System Summary views, the ExecView console will
shut down. After this occurs, you will be unable to launch the
ExecView Console until the main Backup Exec user interface is closed
When running a catalog or restore job that
requires media be inserted in a library, you will be prompted to
create an import job. After creating the import job, select Options
from the Import Job Properties, and then select Auto-inventory
after import is completed.
Backup-to-Disk (B2D) folders must be created
on volumes that are not snapped using Advanced Open File Option (AOFO)
Copy-on-Write providers. Failure to do this could cause the backup
job to use up 100% CPU and ultimately may run out of disk space on
the B2D volume. You should backup B2D folders without using AOFO
Copy-on-Write providers. Backup Exec supports two Copy-on-Write
snapshot providers: VERITAS Volume Snapshot Provider (VSP) and
Microsoft Software Shadow Copy Provider (which is the default
provider when using VSS).
a NAS device is emulating Windows, and is not truly a Windows
operating system, please confer with the NAS manufacturer for
assistance before creating B2D folders on the NAS device. VERITAS
does not certify NAS devices, and if the operating system is not a
true Windows operating system, VERITAS cannot properly troubleshoot
the issue, because the operating system is a proprietary operating
servers cannot be used as a B2D target because of file system rights
BEWSCommandLine_en.pdf, which documents the
use of the Backup Exec Command Line Applet, erroneously states that
the -op: and -ap: switches are required for the -o101
Operation. Only the -m switch is required this operation.
When Windows Internet Name Service (WINS) is
installed and the WINS data directory (%SystemRoot%\system32\wins)
is backed up, non-snapshot backups will result in a job status of
"Completed with Exceptions". For Windows 2000, this is
caused by the wins.mdb (WINS database), winstmp.mdb (temporary), and
J50*.log (transaction logs) files being in-use. For Windows 2003,
this is caused by the winstmp.mdb (temporary) file being in-use. For
Windows 2000, since WINS cannot be directly protected by a volume
backup, continue to use the WINS management console in conjuction
with a volume backup to protect WINS as documented by Microsoft. For
Windows 2003, WINS is protected by the WINS VSS Writer via the
Backup Exec Shadow Copy Components resource so the backup error is
benign and can be ignored.
Not all resource types and methods are protected
with OBB; for example, SPPS is not protected with OBB and the
Offhost option is not supported by OBB.
selection lists contain resources that no longer exist or are
offline, you must use the Text view of the selection list,
find the selection, and delete it. The Graphical view may
show a partial selection, but deselecting it will not remove the now
Excludes based on criteria that does not exist for the selected
filesystem will result in an exclude for that filesystem. For
example, a global exclude based on date for a SQL database will
result in a exclude since the SQL database does not have a date
Back to top
Backup Exec Web Administration Console
The grid control used throughout the BEWAC
application has been updated. Some browsers may not properly detect
that the files used by the grid control have been updated and may
attempt to use the outdated files located in the browser’s cache. If
this occurs, you may see some incompletely rendered pages in the
To fix this problem, do the following:
a) Close all browser windows on the client
b) Delete the browser’s cache (for
instructions, see your browser’s documentation).
After these steps have been followed, the grid
control should work properly.
Click Yes when prompted to allow the
client’s browser to update and properly initialize the new component.
If you click No, the control is not
updated, yet it will still be initialized. BEWAC features may not
BEWAC can be installed only on systems running
Windows Powered Server Appliance Kit 2.0 or later and Windows
Storage Server 2003.
Windows Powered Server Appliance Kit 2.0 only
supports English, French, German, Japanese, and Spanish; therefore,
this release of BEWAC only supports those languages.
BEWAC is hosted by the Administration web site under
the Microsoft Web Server (IIS: Internet Information Services).
Certain directory security settings might inhibit the caching of
server variables that contain logon information, causing BEWAC to
prompt frequently for credentials in pages that use the selections
For Japanese versions: You cannot perform Backup,
Test Run, or other jobs containing the web scheduler using BEWAC if
the Japanese Locale W2K3 default is changed to Japanese Traditional
When accessing Backup Exec Help from the Help tab, a
message may appear stating that a page contains both secure and
non-secure items. This message is a result of icons used in
the body of the Help documents and is of no threat to system
security. By selecting Yes, the document will display
normally and the icon will appear; if No is selected, the
document will display normally but the icon will be missing.
You can avoid this prompt by changing Internet
Explorer settings. From the browser tool bar, select Tools,
then Internet Options. Click the Security tab,
and then click Custom Level and scroll to Display Mixed
Content. Select Enable to display the icon automatically.
Back to top
Backup Exec Utility (BEutility.exe)
Back to top
Cluster-aware Backup Exec Notes
Customers wishing to use a SQL server with Backup
Exec for Windows Server 10.0 in a clustered environment will need to
uncluster their previous product. Then, on one node of the cluster,
select to use a remote SQL server. On all other nodes, select to use
a local MSDE instance. After all nodes have been upgraded, re-run
the cluster wizard from the node that uses the SQL instance to re-create the cluster.
When Exchange 2000 or 2003 servers are clustered
in an active/active configuration, if the same node controls both
virtual Exchange servers, all individual mailboxes from both servers
are displayed under the mailbox icon for each virtual server. If
both mailbox icons are selected for backup, each mailbox is backed
up twice. To display the mailboxes for each server correctly and
prevent a redundant mailbox backup, make both virtual Exchange
servers active on separate nodes.
If a failover occurs during a backup that is
using the Incremental - Changed Files - Reset Archive Bit
backup method, Backup Exec skips the data that was backed up prior
to the failover when the job is restarted on the failover node. In
addition, catalog files are not generated for the data that was
backed up prior to the failover.
To prevent possible loss of data in failover
situations, VERITAS recommends that you use the Incremental -
Using modified time backup method instead of the Incremental
- Changed Files - Reset Archive Bit method.
When browsing servers, icons for both virtual and
non-virtual servers appear identical until an icon for the
virtual server is expanded.
Shutting down a media server with an active
Backup Exec cluster node could prevent other SAN servers from
accessing SAN libraries and drives. Use the cluster manager to
either take the active node offline or move the active node to
another node in the cluster before shutting down the media server.
To use CASO in a VERITAS Cluster
Server environment, you must install VERITAS Cluster Server Client, and
then manually copy the vcsapi_mt.dll file
from "cluster server\bin" on one of the VCS nodes to
"cluster manager\vssapi" on the central administration
Back to top
Notes for Backup Exec Agents and Options
Exchange Agent Notes
Checkpoint restart is not supported for Exchange
mailboxes and public folder backups if the option Enable Single
instance backup for message attachment is enabled on the Backup
Job Properties dialog box for Exchange.
When performing an
Exchange snapshot backup with the Exchange option Perform
before backup when using Microsoft Volume Shadow Copy Service (VSS)
snapshot provider enabled and the dependent option Continue
with backup if consistency check fails disabled, then data for
specific Exchange objects that are determined to be corrupt will not
backed up. All other non-corrupt Exchange objects will be backed up.
For example, if any transaction log
file for a Storage Group is corrupt, then none of the transaction
log files will be backed up for that Storage Group when the Continue
with backup if consistency check fails option is disabled,
however, the Exchange database files will be backed up if Backup
Exec determines they are not corrupt. Likewise, if a specific
Exchange database file is corrupt, then only that specific database
file is not backed up while all other non-corrupt database files and
transaction log files will be backed up.
Note: When Continue with backup if
consistency check fails is enabled all Exchange data will be
backed up regardless of whether or not if corrupt exists.
When restoring an individual Exchange
database from a snapshot, all of the databases in the storage
group must be taken offline.
When restoring an Exchange database from a
snapshot, the “No loss restore”, “Temporary location for
log and patch files”, and “Commit after restore completes”
options are not applicable. Exchange will use the soft-recovery
process when the restored databases are mounted.
Remote Agent for Windows or NetWare Servers
is required to discover resources on remote computers. However,
installing a MAPI client on the media server enables Exchange
resources to be discovered on remote resources on which the
Remote Agent is not installed. If the Exchange resources are in
another domain, the logon account used for the media server must
also be valid for the Exchange resources.
Snapshot backups of the Site Replication
Service (SRS) are not supported by the Exchange 2003 VSS Writer;
the backup job will fail.
Snapshot considerations when circular logging
is enabled include the following:
Incremental and differential snapshots
backups cannot be performed, the backup job will fail.
Only point-in-time, loss restores are
possible. Roll-forward, no-loss restores cannot be
Individual database restores cannot be
performed, the restore job will fail.
Snapshot backups of Exchange are only supported
for Exchange Server 2003 on Windows 2003. Therefore when a migrated
or new snapshot backup job is performed for Exchange Server 2000 or
Exchange Server 2003 on Windows 2000, the backup job will fail. The
job will not fallback to a non-snapshot backup because Exchange
snapshot and non-snapshot backups are not interoperable.
If other resources are included in the snapshot backup job of
Exchange Server 2000 or Exchange Server 2003 on Windows 2000, these
other resources will fallback to a non-snapshot backup. When
creating backups of both Exchange and non-Exchange resources in
these configurations, select the option Process logical volumes
for backup one at a time to allow all other resources to
continue to perform a snapshot backup. The job, however, will still
fail due to the Exchange snapshot failure. To prevent having a
failed job when using these configurations, you should create a
separate backup job for the Exchange resource and not use snapshot
technology for the backup. For more information, refer to your VERITAS
Backup Exec for Windows Servers Administrator's Guide.
On Windows Small Business Server 2003 the
Microsoft Exchange Server 2003 VSS Writer is disabled, which will
cause snapshot backups for Exchange 2003 to fail. To successfully
perform an Exchange 2003 snapshot backup, review the following
Microsoft Knowledge Base article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183.
This issue must be resolved in order to successfully perform a
restore using the Intelligent Disaster Recovery option.
For Exchange Server 2003 installations on
Microsoft Windows Small Business Server 2003, circular logging is
enabled by default to prevent transaction logs from using too much
disk space when regular backups are not performed. Full backups of
Exchange truncate the transaction logs and prevent them from using
too much disk space. VERITAS recommends that you clear the circular
logging option and perform regular full backups of Exchange.
To clear the circular logging
From the Microsoft Exchange
program group, open the System Manager utility.
Expand the Servers node, and
then select the Exchange server.
In the right pane,
right-click First Storage Group, and then select
Clear the Enable circular
Close the System Manager,
and then restart the Exchange server.
Back to top
Admin Server Option (CASO) Notes
- The Central Admin Server option is not supported in a workgroup. The central administration server and all managed media servers must be part of a domain.
- One-Button Backup (OBB) is not available on a CASO server or a
- If you change the system time on either the managed media server or
administration server, you must restart the Backup Exec services on the system
in order for the application to properly take into account the
- When a standalone media server is configured as a managed media
server, the device and media database is configured centrally to use the
Backup Exec database on the central administration server. Any device
and media data from a previous operation of the local media server is
lost at this point. When the ADAMM service restarts, the standard device
discovery process is executed to rediscover the physical devices
attached to the server. However, there is no facility for discovering
Backup-to-Disk folders, so the original Backup-to-Disk specifications
cannot be recovered. You must create the Backup-to-Disk folder again at
the managed media server and point it to
the original location. After that, you must run an inventory job to
discover the Backup-to-Disk media; then, each media must be cataloged
before data can be restored from it.
Back to top
Intelligent Disaster Recovery (IDR)
On Windows 2000 and XP, to avoid issues when using Intelligent Disaster
Recovery (IDR) to recover dynamic disks managed by VERITAS Volume
Manager (VM) or Microsoft's Logical Disk Manager (LDM), create two
IDR diskettes using the procedure "Creating the Intelligent Disaster
Recovery Diskettes Only" in the Intelligent Disaster Recovery
chapter of the Administrator's Guide. Then, reinstall the operating
system and install Volume Manager if it was on the computer when the
backup for IDR was created. Insert the first IDR diskette. Run the
copyidr.cmd from the first IDR diskette and follow the prompts in
the IDR Wizard to complete the recovery. This two-floppy method of
recovery is not supported with Windows 2003. Windows 2003
incorporates the Storage Foundation for Windows installation.
"When creating IDR CD's and Tape Images,
you can also give the path to an existing ISO image file for the operating
system that you are protecting.
To select an ISO image:
Note: Only the directory and not the ISO image can be
Manually enter the name of the ISO file.
For example, if an operating system ISO file (WinXP.ISO) is
present in directory C:\Directory1, browse to Directory1 and
manually add the ISO file name. In this case, the path would be:
When the Intelligent Disaster Recovery
Preparation wizard is used on a Windows 2003
media server to create a bootable CD image, the VERITAS IDR CD writing
feature cannot be used to burn the created iso image. You should use the third
party software that comes with the CD-writer to burn the iso image."
If the SQL database used for Backup Exec resides
on a remote SQL server, then the system database files used by IDR
will also reside on the remote SQL server. When performing a full
IDR backup, you must include IDR files, such as master$4idr,
Model$4idr, and MSDB$4idr, from the remote SQL server
otherwise the files will not be available for recovery. You must
also back up the bedb.bak file in order to restore your Backup Exec
The IDR process on a cluster node does not
restore the quorum data to the quorum drive. In order to restore the
quorum data, run clrest.exe from the command line. This command will
move the data from the default location to the quorum drive. The
clrest.exe utility can be found in the Backup Exec installation
directory. Use the format:
clrest [-f] path [drive letter]
For computers running Windows 2000, IDR does not
restore Windows Management Instrumentation (WMI) and Terminal
Licensing Services (TLS). To use Backup Exec to restore WMI and TLS
to a Windows 2000 computer, use the following procedures.
Create a restore job
using the appropriate backup set that contains valid WMI data.
From the Restore Job
Properties dialog box, on the Properties pane, under
Source, click Selections, and select the default location
"%SystemRoot%\system32\wbem" of the identified backup set.
On the Properties
pane, under Settings, click Advanced, and select the
option Restore Windows Management Instrumentation repository.
Run the job.
Create a restore job
using the appropriate backup set that contains valid TLS data.
From the Restore Job
Properties dialog box, on the Properties pane, under
Source, click Selections, and then select the default
location "%SystemRoot%\system32\Lserver" of the identified backup
set. Note: The installation location of this feature is
On the Properties
pane, under Settings, click Advanced, and select the
option Restore Terminal Services database.
Run the job.
Back to top
Oracle Agent Notes
If you upgraded from Oracle Version 7 to Version
8, it is possible that the Oracle installation program did not
update the OCIW32.DLL in the %ORACLE_HOME%\BIN directory. When the
Oracle Agent is installed on an Oracle 8 server, it requires the
Oracle 8 version of OCIW32.DLL to function properly.
To check the version of OCIW32.DLL, use Windows
Explorer to locate the file in the %ORACLE_HOME%\BIN directory.
Right-click to determine the file's version. If it is an earlier
version (1.005, 7), copy the Oracle Version 8 OCIW32.DLL from the
\WIN32\V8\rsf80\OCIW32.dll directory on your Oracle installation
media to the %ORACLE_HOME%\BIN directory.
The Backup Exec Agent for Oracle Server supports
a new configuration parameter that can be set in the registry. The
parameter enables the agent to support incremental/differential
backups of the Oracle archived redo logfile directory. By default
the Backup Exec Agent for Oracle Server backs up ALL files in the
Oracle archived redo logfile directory, regardless of the backup job
type (normal, incremental, differential, etc). However, if you set
this configuration option, you can submit incremental/differential
backup jobs, and the agent will back up only the archived logfiles
that have been created since the previous backup. This configuration
option affects only the backup of files in the archived redo logfile
To enable this feature, use REGEDIT or REGEDT32
to add the DWORD value "AllowIncrementalLogfileBackup" to the
"HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec Oracle Agent"
registry key. Set the value of this new DWORD entry to any non-zero
value (for instance 1). After setting this value in the registry,
you must stop and then restart the "Backup Exec Oracle Agent" system
service using the Windows Server System Service control panel.
The Backup Exec Agent for Oracle Server does not
support concurrent backup and/or restore operations. Attempting to
back up or restore an Oracle database from more than one media
server at a time will cause the operation to fail.
If you run a backup job that is created to
protect individual tablespaces, and a specified tablespace within
the job is dropped from the database before the job runs, the
dropped tablespace is not backed up. In this situation, Backup Exec
does not provide notification of this condition.
Oracle 10g creates archive log files in a Flash
Recovery Directory and creates a new subdirectory each day. The
Backup Exec Oracle agent supports protecting archived redo logs in a
single directory. Oracle Enterprise Manager can be used to create a
single directory for the archived log files. The Backup Exec Oracle
Agent should be configured to use this directory during installation
Back to top
Open File Option Notes
When the VERITAS Volume Manager FlashSnap Option
is used for Advanced Open File Option backups, the SnapBack of the
volume is done asynchronously since SnapBack can take a long time
(depending on the size of the volume snapped and the changes that
may have happened during the backup). Rather than hold the job
completion for the length of time this operation may take, the job
will instead Complete with Success (if no other error occurs). Use
the VERITAS Enterprise Administrator (Volume Manager GUI) to verify
that the resynchronization completed.
In rare cases, it is possible that the SnapBack
fails and a broken mirror results. In such a case, the next VM
FlashSnap job submitted (for the same volume) may fail with the
error " Volume cannot be snapped" or "Volume has not been
Snap-started or is not a dynamic volume". The job itself will be
logged as "Complete with Exceptions". Use the VERITAS Enterprise
Administrator to verify why the SnapBack did not complete, and then
correct the error.
Back to top
ServerFree Option Notes
For a list of supported devices with the
ServerFree Option, go to
http://support.veritas.com/rd/bews-compatibility.htm. Select the
document titled "VERITAS Backup Exec for Windows Servers ServerFree
Option - Device Support List for Windows 2000 HP ServerFree
To back up an NTFS volume that is part of a
secondary VERITAS Volume Replicator (VVR) Replicated Volume Group
(RVG), you must do one of the following:
Use the VERITAS FlashSnap Option to create a
snapshot of the target volume via the VERITAS Enterprise
Administrator (VEA). If there is no existing snapshot for the
volume, select Snap Start from VEA to establish a snapshot
mirror of the volume, and then select Snap Shot to create a
point-in-time copy of the volume that can be accessed. After the
volume is snapped, use Backup Exec to back up the snapshot. This
is the recommended method. By using this method, you still
maintain a replica of your data. Remember that using this method
creates a point-in-time snapshot of the data. Therefore, any
information that is replicated after the snapshot is not backed
up until the next time a backup is run. Refer to the Volume
Manager User's Guide for information about FlashSnap.
Back to top
SAN Shared Storage Option Notes
Whenever a database is updated by a member server
in a SAN Shared Storage Option configuration, you must manually
refresh the other Backup Exec administration consoles in the
configuration to see those changes. To manually refresh the user
interface, right-click the proper component and then select
Refresh, or press <F5>.
If you have a
Managed Media Server that is a secondary server in a SAN SSO
configuration, and you want this server to be managed by a different
Central Administration Server, follow these steps:
Make the MMS a
standalone server, effectively removing it from the SSO
server to another CAS.
The MMS must be
removed from the SSO configuration prior to changing its CAS,
otherwise all of the SAN SSO device configuration data will be
migrated to the CAS database to which the server is assigned.
When a standalone media server is configured as a
SAN SSO secondary server, a new data partition for that server is
created in the Backup Exec database on the primary server. This
partition is initially empty, so any data from a previous operation
of the server is lost at this point. When the ADAMM service
restarts, the standard device discovery process is executed to
rediscover the physical devices attached to the server. However,
there is no facility for discovering Backup-to-Disk folders, so the
original Backup-to-Disk specifications cannot be recovered. You must
create the Backup-to-Disk folder again and point it to the original
location. After that, you must run an inventory job to discover the
Backup-to-Disk media; then, each media must be cataloged before data
can be restored from it.
Back to top
SQL Agent Notes
Advanced Open File Option (AOFO) backups
(snapshot backups) are limited to full Microsoft SQL Server database
Back to top
Desktop and Laptop
If you install the
Desktop and Laptop Option (DLO) after Backup Exec has been
clustered, you must rerun the cluster configuration wizard. This
allows Backup Exec to determine that DLO is present and to
reconfigure the Backup Exec group to account for it.
When the Backup Exec
DLO Administration Console is upgraded from version 9.1 to version
10.0, customized alert configuration settings are not preserved.
Specifically, informational alerts for completed backup jobs, queued
restore jobs, and completed restore jobs are returned to the default
If your original files
reside on an NTFS volume, the Desktop User Data Folder and the
Network User Data Folder should also reside on an NTFS volume. If
your original files reside on an NTFS volume and either the Desktop
User Data Folder or the Network User Data Folder reside on a FAT or
FAT32 volume, the Restore view and the Restore Search view may
contain duplicate entries for the same file. If this occurs, you can
select either file to restore and receive the same outcome. In
addition, when you add, change, or delete a local backup selection
or change Desktop Agent or Profile settings, the Pending files list
may include files that did not change. You can ignore these files.
DLO also adds 20 characters to each backup file
name, which contributes to the maximum path length problem above, and
can also cause maximum name limits to be reached.
The Active Directory naming convention of user
principal name (UPN) with the format username@domain is not
supported by DLO. DLO only supports the format domain\username.
When the Move Network User Data Folder
option in the DLO Administration Console is used to move a Network
User Data Folder to a UNC location (for example, \\myserver\userdata\username)
rather than an existing Storage Location, the permissions on the new
location may need to be modified. The local administrator group and
the owner of the files must have read and change permissions for the
Network User Data Folder, and the Everyone group should be
In the Desktop Agent Backup Selection Standard
view, files and folders are represented in a tree view where users
can select or deselect files and folders for backup. When the check
box next to a file or folder is grayed out, the selection was
defined by the administrator and can only be changed if the
administrator has granted this right in the profile definition. When
a red 'X' appears in the check box next to a file or folder, this
item has been globally excluded from all backups by the
administrator and cannot be selected.
Back to top
Agent for Windows or NetWare Servers
Full, differential, and incremental jobs that specify using the
modified time will revert to using the archive bit for NetWare servers
included in the job.
Back to top
Agent for Linux or Unix Servers
- The Remote Agent for Linux or Unix
Servers (RALUS) uses the locale settings encoding to back up and restore
multi-byte character representation of files and directories. When the
character representation of files and directories does not fall in the
locale character set, RALUS might fail to back up or restore those files
or directories. To prevent failed backups and restores, the config
option for the encoder must be specified with LATIN-1 as in
“Software\VERITAS\Backup Exec\Engine\RALUS\Encoder=LATIN-1”. When
using LATIN-1 encoding, back up and restore of all files will occur with
no loss but the UI display for backup selections and catalogs might not
be correct. You should not perform a redirected restore of backups to an
agent that is not using the same character encoding or filename
characters may be lost. The configuration entry to be edited is located
by default in /etc/VRTSralus/ralus.cfg.
- When installing RALUS using the Backup
Exec for Windows Servers installation CD and the push installation
technology built into the installer, you can install to multiple
remote Unix hosts, provided the remote servers are of the same OS
type. For example, from a Linux computer, you can push install RALUS
to multiple Solaris servers. You cannot, however, use a remote
target list that consists of both Linux and Solaris computers.
If you need to remotely install to different operating systems, you
must perform multiple push installations. For example, you could run
the installation program, installing to all Solaris servers. You
could then run the installation program a second time, installing to
all Linux servers.
- If you are using NFS version 3, RALUS
will always follow mount points even if the option Follow remote mount points
is not selected. You can force the use of version 2 by creating the
mount point with the option nfsvers=2.
Back to top
Advanced Disk-based Backup Option
When using Hitachi hardware, the
following limitations exist for the Offhost backup feature:
supports only basic disks for Offhost backup. If a computer uses
a combination of dynamic and basic disks, a complete system backup
using the Offhost backup feature is not possible when the Hitachi
provider is used.
Raid Manager log cannot be on a volume being snapped. Hitachi
executes I/O to its Raid Manager log file during the snapshot commit
process, and the VSS coordinator blocks I/O to any drive being
snapped. Therefore, if the log directory for Raid Manager is on the
volume that is being snapped, then log I/O is blocked and the snap
process is deadlocked.
VCS 4.1 is not
supported with the Hitachi provider. Version 4.1 of VCS
only supports dynamic disks; the Hitachi provider does not support
dynamic disks for Offhost backup.
Backing up VERITAS Storage Foundation for Windows
(VSFW) volumes with the Backup Exec Offhost option requires
transferring snapshot volumes in shared storage from host to host.
VSFW volumes backed up using the Offhost option should reside in
VSFW disk groups with either the “private protection” or “cluster
disk group” disk group property. Private dynamic disk group
protection and cluster disk group property settings use hardware
locking techniques to protect a dynamic disk group located on shared
storage from access by other hosts connected to the shared storage
Back to top