Click Finish after selecting the appropriate check boxes Note: A reboot may be required to complete the installation. Choose Installation and Licensing - Live Update to download latest patches. Note: It is best to continue to run Live Update until it states that it is up to date.
This may take multiple attempts. After running LiveUpdate, it is necessary to push the updated agents to all remote agents. If no license keys are input, all agents and options are available in trial mode. Figure 18 Note: SQL requires an unencrypted and uncompressed drive as the installation location. The custom installation wizard is similar for BE and Figure 15 A Custom installation includes the option to install Veritas device drivers for all tape devices.
Note that Veritas drivers are not Windows Certification Tested. During the installation progress, click Continue Anyway if prompted about the device driver installation. Figure 16 Click here to navigate to the next step i. Installation Review.
How to reinstall Backup Exec on the same server while saving settings, jobs definitions and current catalog information. Was this content helpful? Yes No Rating submitted. Please provide additional feedback optional :. Even though the CASO server has the functionality to perform all Media Server tasks in a large scale environment, it is recommended to designate it the role of being an administration server only.
When selecting a server or servers where to install CASO to, it is highly recommended that the system s meet the following system requirements, especially if Windows is clustered or in a SAN Storage Area Network Environment:. Due to the large number of disk writes that will occur to the DB it is highly recommended to designate separate high speed disks for both the Data and Log components. It can possibly function with less memory than 8GB, depending on how many MBES and the amount of tape hardware being managed by the CASO Server; however the configuration may run into performance or communications issues between the machines.
Even though a 32 bit processor can be used, it is recommended that a server with a 64 bit processor and operating system be used instead.
How to determine if the CASO setup us considered a large scale environment? The important aspect of determining this is based on the number of concurrent connections to the DB.
The maximum number of concurrent connections to the MMS and tape hardware is around ; once this maximum is reached performance issues can occur or DB exceptions can show in the Windows Event Logs. Also, the maximum limit for MBES is 90 when the catalogs are centralized, regardless of the version of SQL being used or hardware that is available. When upgrading the CASO setup from a prior release of Backup Exec, the following provides important tips in upgrading the setup.
Make sure jobs do not run during the upgrade process. This can be done by simply putting jobs that are scheduled to run during the upgrade on hold. MBES servers can be paused too; this will also prevent jobs from running. If the Backup Exec services on the MBES do not stop, this may indicate a problem and should be resolved before proceeding with the upgrade. Please see the troubleshooting section below if the services don't stop as they should.
Run setup on the CASO server. Following guidelines on installing and complete the upgrade. Reboot the server after install if prompted. Run setup on each of the MBES servers. Follow guidelines on installing and complete the upgrade. If all MBES servers are being seen correctly along with jobs and devices, then the upgrade has been completed successfully.
If a lot of jobs are scheduled to run after being taken off hold, it is recommended to gradually take the jobs off hold rather then run all at once. Because of this, some MBES servers may temporarily need to be left at a prior revision until it is possible to upgrade these machines.
Veritas does support temporary rolling upgrades for one prior version of Backup Exec, but not for extensive periods as the features of the newer version cannot be used and if any problems occur with the prior version MBES's, then it is recommended to proceed with upgrading that machine before doing any further extensive troubleshooting.
The entire System State is backed up. Incremental backups are supported only for the system file components of System State; the other System State components are backed up as a full backup. Block-level backup methods must be selected for SQL. After the initial incremental backup runs for SQL, block-level backups are performed for any subsequent full or incremental backups for which the Simplified Disaster Recovery option is ON. Conversion will not be performed if a block-level backup method is not selected.
Full backups are always performed for Active Directory. Neither incremental backups nor differential backups are supported for Active Directory. Backup Exec supports conversion of disks or volumes that are larger than 2 terabytes TB for VMware hosts and Hyper-V or later hosts.
If the boot volume or the system volume on the source physical computer is larger than 2 TB and you are converting to a VMware or Hyper-V R2 virtual machine, then Backup Exec cannot convert it. A boot volume cannot be split or created as a dynamic spanned volume.
This limitation also applies if the boot volume on the source is larger than the destination datastore's maximum supported disk size. Backup Exec converts all disks and volumes on the destination to simple or spanned dynamic volumes. Even if the source disk is a basic disk, the converted disks on the destination will be dynamic. Since Backup Exec supports only simple and spanned dynamic volumes, if the source volume type is striped, mirror, or raid5, then Backup Exec converts that volume to either simple or spanned on the destination.
Conversion of a volume that is larger than 2 TB is supported in the following situations:. Conversion of GPT disks is not supported, regardless of the size of the volume on the disk. Conversions of GPT disks fail.
In situations where the VMware source disk size is larger than the destination datastore's maximum supported size, the source disk is split into multiple disks. Backup Exec splits the disk based on the destination datastore's maximum allowed size. Before you create a job to convert a physical computer to a Windows Server and later Hyper-V host, review the following information:. Disk data is stored in vhdx files for conversion of a physical computer to a virtual machine running on a Windows Server and later Hyper-V host.
The vhdx files can have a maximum capacity of 64 TB. The physical computer's disk sector size is maintained during the conversion. Conversion to any previous versions of a Windows Hyper-V host is not supported, so those jobs fail. If the physical computer runs Windows Server or later with one or more Windows deduplication volumes, conversion to a Hyper-V host is possible, but it may fail.
The converted disk data is not deduplicated. In other words, an unoptimized data transfer is performed. Unrestricted access to catalogs and backup sets for restore - Enables this managed Backup Exec server to have unrestricted access to all centrally stored catalogs.
This option also enables this managed Backup Exec server to restore data from any backup set on any storage devices that it shares. This option can be selected only if the Centrally managed Backup Exec server option is selected. Selecting both of these options enables the central administration server to have the greatest amount of control over this managed Backup Exec server.
Locally managed Backup Exec server — Enables the central administration server to monitor the managed Backup Exec server.
However, the server and its devices, media, and backup jobs are controlled locally. Follow the remaining prompts in the install wizard. Verify that the central administration server is communicating with the managed Backup Exec servers that were upgraded: On the central administration server's Storage tab, right-click the managed Backup Exec server and verify that the Communication Enabled option is checked.
The following information applies if you select the option Centrally Managed Backup Exec server and also select the option Unrestricted access to catalogs and backup sets for restore : This Backup Exec server becomes a Managed Backup Exec server. A persistent network connection is required between the Managed Backup Exec server and the Central Administration Server.
The catalogs are centralized and are stored on the Central Administration Server. Note that this combination of options may not be suitable if a low-bandwidth network connection exists to the central administration server. This managed Backup Exec server can access and restore backup sets for all storage devices that it shares with other Backup Exec servers. The backup jobs that are created on the Central Administration Server can be load-balanced and delegated to this Managed Backup Exec server.
A rolling upgrade cannot be performed with this configuration. The following information applies if the option Centrally managed Backup Exec server is selected, but do not select the option Unrestricted access to catalogs and backup sets for restore : This Backup Exec server becomes a Managed Backup Exec server. The catalogs are in distributed mode by default, but can be changed. The catalogs for the jobs that run on this Managed Backup Exec server are stored locally.
This Managed Backup Exec server can access and restore any backup set stored on the storage devices that it hosts, regardless of which Backup Exec server ran the backup job. However, for the shared storage devices that other Backup Exec servers host, this managed Backup Exec server can access and restore only the backup sets that were created from backup jobs it ran. This option is recommended for use with the private cloud configuration. A persistent network connection is not required between the managed Backup Exec server and the central administration server.
Therefore, this option may be useful when a very low-bandwidth connection exists between the managed Backup Exec server and the central administration server. It may also be useful when the managed Backup Exec server cannot always be connected to the central administration server.
The catalogs are in distributed mode by default. The catalogs for the jobs that run on this managed Backup Exec server are stored locally.
0コメント