Documente Academic
Documente Profesional
Documente Cultură
R2
20047221
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
PN: 20047221
Legal Notice
Copyright © 2010 Symantec Corporation. All rights reserved.
Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec
Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks
of their respective owners.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
10 9 8 7 6 5 4 3 2 1
Installing Backup Exec
This document includes the following topics:
■ System requirements
■ Post-installation tasks
System requirements
The following are the minimum system requirements to run this version of Backup
Exec:
4 Installing Backup Exec
System requirements
Item Requirements
Operating system You can find a list of compatible operating systems, platforms, and
applications at the following URL:
http://entsupport.symantec.com/umi/V-269-1
Additional You can use Backup Exec with Microsoft Windows Microsoft
application Operations Manager (MOM) 2005.
support
Internet browser Internet Explorer 6.0 or later. Service Pack 1 is required for SQL Server
2005 Express.
Item Requirements
Storage Hardware You can use storage media drives, robotic libraries, removable storage
devices, and non-removable hard drives.
http://entsupport.symantec.com/umi/V-269-2
Support is available for the first drive in each robotic library when
you purchase Backup Exec. To enable support for each additional
robotic library drive, you must purchase the Backup Exec Library
Expansion Option.
Note: The Backup Exec service account and the Backup Exec System Logon Account
are set to the same user name when Backup Exec is installed. If you need to change
the user name for the service account is no longer used, then you should also
change the Backup Exec System Logon Account to use new credentials.
Installing Backup Exec 7
Installing a typical installation of Backup Exec
Note: Before you install, make sure that your license keys for Backup Exec and
any agents or options are available. If you do not have license keys, go to the
following URL to activate the product:
https://licensing.symantec.com
License keys are required to install Backup Exec and its agents and options.
However, you can install a trial version of Backup Exec without a license key.
To import license keys from a file Do the following in the order listed:
8 Click Next.
9 On the Service Account panel, provide a user name, password, and domain
for an Administrator account that the Backup Exec system services can use.
10 If you want to change the directory where Backup Exec files are installed,
click Change, and then select a new location.
11 Click Next.
12 On the Remote Computers panel, do one of the following:
To push-install the Remote Agent for Do the following in the order listed:
Windows Systems to a single remote
■ Click Add, and then select Add a
computer
Single Computer.
■ Enter the name of the remote
computer, and then enter the
credentials for the remote computer.
■ Click Next.
To push-install the Remote Agent for Do the following in the order listed:
Windows Systems to multiple remote
■ Click Add, and then select Add
computers
Multiple Computers with the Same
Settings.
■ Enter the name of a remote computer,
and then click Add to List. Repeat this
step for each remote computer that
you want to install the Remote Agent
on.
■ Enter the credentials for the remote
computers.
■ Click Next.
13 Click Next.
14 Review the installation summary, and then click Install.
The installation process creates an installation log named Bkupinst.htm on the
computer where Backup Exec is installed.
Note: If you install Backup Exec through Terminal Services and the installation
media is on a shared drive (network share) you must install using a UNC path.
Installation by mapped drives is not supported.
If you installed the trial version or the Not For Resale (NFR) edition of Backup
Exec, you can install trial versions of the additional options. If you have a licensed
version of Backup Exec, you can use a trial version of most options and agents for
a specified period of time.
Note: If the Central Admin Server Option is installed, and you want to install
additional options on a managed media server, you can pause the managed media
server. When a managed media server is paused, the central administration server
does not delegate jobs to it. When the installation is complete, un-pause, or resume,
the managed media server.
3 Click Next.
4 Select the additional options that you want to install, and then click Next.
5 If you are prompted, enter information or choose settings for the additional
options that you want to install. Click Next after each selection.
6 Read the Backup Exec installation summary, and then click Install.
The Backup Exec services are stopped while the additional options are
installed. If any active jobs are running, you are prompted to stop them, or
to wait for the jobs to finish.
When the installation is complete, the services are restarted.
7 Click Finish.
return to the previous version of Backup Exec or to continue with the upgrade. If
you choose to continue with the upgrade, then devices, media, and jobs are not
migrated from the previous version of Backup Exec.
Backup Exec 2010 R2 provides backward compatibility as follows:
■ Backup Exec 2010 R2 can communicate with Backup Exec 12 Remote Agent
for Windows Systems and later.
■ Backup Exec 2010 R2 can communicate with Backup Exec for NetWare 9.2
Remote Agent.
■ Backup Exec 2010 R2 Central Admin Server Option server can communicate
with Backup Exec 12.5 (with the appropriate patch) or Backup Exec 2010 (with
the appropriate patch) for the purpose of rolling upgrades.
■ Backup Exec 2010 R2 Command Line Applet is compatible with Backup Exec
12 and later.
A Backup Exec 2010 R2 Remote Administration Console can manage media servers
on which Backup Exec version 11d and later is installed. However, if the media
server uses a previous version of Backup Exec, you cannot use any of the new
features of the current version. If you want to use the features of the current
version, you must use the current version on both the Remote Administration
Console and the media server. A Remote Administration Console that uses a
previous version of Backup Exec cannot be used with a media server on which the
current version is installed. For example, a Backup Exec 2010 Remote
Administration Console cannot manage a Backup Exec 2010 R2 media server.
However, a Backup Exec 2010 R2 Remote Administration Console is
backward-compatible with a Backup Exec 2010 Remote Administration Console.
Before you upgrade Backup Exec, do the following:
■ Delete the job histories and the catalogs that you no longer need to shorten
the upgrade window.
■ Run a database maintenance job.
■ Upgrade any existing instances of SQL Server 2000 to either SQL Server 2005
with SP3 or to SQL Server 2008.
You cannot change the configuration of your media servers during an installation.
For example, you cannot change a central administration server to a managed
media server. If you want to change the configuration of your media servers, do
it either before or after you upgrade to the current version. You cannot change
the database location during the upgrade process. If you want to change the
database location after the upgrade, use BEUtility.
To upgrade the options that are installed on remote computers, you must reinstall
them. Options that are push-installed are not upgraded until you reinstall them.
Installing Backup Exec 13
Post-installation tasks
The Remote Agent for Windows Systems and the Advanced Open File Option are
push-installed.
Note: If you upgrade from a previous version of Backup Exec that uses a
non-English version of Windows, you must download the SQL Express SP3 setup
file for that language from the Microsoft Web site.
Post-installation tasks
For best results before starting Backup Exec, do the following:
■ Make sure that your storage devices are connected and configured properly.
■ Decide if your backup will be to a tape device or a disk device. You can configure
both devices when you prepare your Backup Exec environment.
Note the following:
■ If you’re backing up to a tape device, verify that the device is supported.
You can install drivers for the devices when you configure your Backup
Exec environment.
■ If you’re backing up to a disk device using the Backup-to-Disk feature,
decide where you can create a backup folder. You should create it on a disk
that won’t be included in the backup jobs and that has enough free space
to contain the backup job.
■ Understand how Backup Exec provides overwrite protection for your media.
■ Understand the default media set and its four-week overwrite protection
period.
■ Learn about creating new media sets with weekly, monthly, or quarterly
retention periods.
■ Decide which resource credential you want your Backup Exec logon account
to use when browsing and making backup selections. You can use an existing
Backup Exec logon account, or create a new one.
■ Decide the format that you want to display all reports, either HTML or Adobe
Portable Document Format (PDF). The default setting is HTML.
14 Installing Backup Exec
Post-installation tasks