download-documentUnavailable

Veritas now offers Professional Service for Backup Exec™ — the Backup Exec Installation, Migration and Upgrade Service — this service will help you implement the latest version of Backup Exec.

The service includes the following three options:

Option 1: An installation of the current version of Backup Exec or a previous version if required.
Option 2: An upgrade of the Backup Exec Server to the latest version of Backup Exec
Option 3: A migration of the data from an existing Backup Exec server to a new Backup Exec server

To purchase the service, contact your local software reseller or Veritas account representative today. Click here for more details.

You may also reach out to Authorized Veritas Distribution Partner using following link:
alshamasislamicinstitute.com.pk

IMPORTANT: Prior to following the information in this article, ensure that the information in Article  and Article has been reviewed and understood

Steps to Upgrade to Backup Exec x or x

Below are the steps to upgrade from earlier versions of Backup Exec. 

To run a direct upgrade to Backup Exec x minimum version required is Backup Exec

To run a direct upgrade to Backup Exec x minimum version required is Backup Exec 15

To run a direct upgrade to Backup Exec 22  minimum version required is Backup Exec

Any earlier version of Backup Exec will need to be upgraded to minimum supported verions to be upgraded to Latest version of Backup Exec

Steps to download the Backup Exec Licenses, Installation Files, Updates, Feature Pack, Service Pack, Hotfix and Patches within VEMS

Backup Exec  Download

1.      Login to the Backup Server with the Backup Exec service account credentials. Open Windows Services MMC and review the Backup Exec serivces. The account used to Start teh Backup Exec Server or Job Engine service is the Backup Exec Service Account to be used during the upgrade process.

2.      Stop all the Backup Exec services and the SQL service for BKUPEXEC.

3.      Tape a Copy/Backup of the Backup Exec Data and Catalogs folders to safe location. 

 X:\Program Files\Symantec\Backup Exec\” folder

or

“ X:\Program Files\Veritas\Backup Exec\”

[X represents driver where Backup Exec is installed]

4.      If custom reports are configured copy or backup of “ X:\Program Files\Veritas\Backup Exec\Reports” will also need to be taken

5.      Start the SQL service for BKUPEXEC

6.      Mount the ISO for the Backup Exec x,  x, or 22 installer onto the Backup Server

7.      Right click on alshamasislamicinstitute.com.pk and "Run as Administrator". (Due to security settings, some environments may require alshamasislamicinstitute.com.pk to be started using 'Run as Admin')

Additional Notes for (Backup Exec 22)

• During an upgrade to Backup Exec , the installer will deploy SQL 64bit BKUPEXEC64 instance to host the Backup Exec database. It will remove the Local BKUPEXEC SQL instance ( default BE SQL Instance used before BE ) towards the end of the upgrade
• If the older version of Backup Exec being upgraded uses a custom SQL Instance i.e. anything other than BKUPXEC SQL instance name, then the Backup Exec upgrade will continue to use the same SQL version.
.• A fresh installation of Backup Exec deploys SQL Express 64bit instance. This default instance name is “BKUPEXEC64”..

8.     Click on Backup Exec option for upgrade or Fresh install

9.      Click on I accept and click Next

       Click on Local install for Upgrade or Fresh Install and click “Next”

     Wait for the Environment Check to Complete

     Enter the License Keys and click “Next”. For more information related to step by step instructions for installing license keys review - Step By Step guide to install and review Backup Exec licenses

     Enter the Backup Exec Service account username and password and click “Next”

     Click on Next and Install until you get the Migration Screen and wait for it to complete.

     Once Migration is complete it should show “successful”, you can review the Migration report and click on “I Accept” and continue if all looks good.

     Continue with the Upgrade Steps:

     Once Upgrade or Install is complete, reboot if required or asked.

     All your configuration should be available after the reboot.

     After reboot once the Backup Server is up and if the setup has Deduplication folder configured, it will be listed as “OFFLINE”.

     In the alerts you will see the below alert which will indicate that the Deduplication folder is being converted to the new version 10 with estimated time

     You will need to then check the PDDE conversion logs to verify if conversion was successful,  located in “C:\Program Files\Symantec\Backup Exec\Logs” File name: “PDDE10 conversion log”

     You will need at least 12% free space on the Drive that hosts the Deduplication folder for the conversion to complete successfully.

     Once the conversion completes you will need to restart all Backup Exec services and the devices should now be online.

    Make sure you upgrade all your remote agents and that can be done by right clicking on each server and clicking on update. They may require a reboot after upgrade and hence you can decide when and how you would like to upgrade the remote agents.

Note:-

To run a direct upgrade to Backup Exec x minimum version required is Backup Exec

To run a direct upgrade to Backup Exec 21 minimum version required is Backup Exec 15

Any earlier version of Backup Exec will need to be upgraded to supported versions to be upgraded to Latest version of Backup Exec

For more information related to step by step instructions for installing license keys review - Step By Step guide to install and review Backup Exec licenses

Base and upgrade installers

Click Base and upgrade installers to view the files associated with this product version. Check the box next to each file that you wish to download, then click Download. The Download button will appear once you check the first file. After you click Download, you may be prompted to select a Veritas Entitlement Management System (VEMS) account. If you are asked to select a VEMS account, select the account that you wish to be the account of record for your download transaction.

To download files in the Base and upgrade installers section:

• You must have a Veritas account. If you do not have a Veritas account, you can create one by clicking Sign in at the top of the page and then clicking Create one.
• Your Veritas account ID (email address) must be registered as a user of a VEMS account that holds an entitlement for the product with an Entitled Version (displayed in VEMS) that is greater than or equal to this product's' version.
• Your Veritas account ID must have either the VEMS Administrator or Download Software privilege.
• You must log in with this Veritas account. To log in, click Sign in.

Note: You may not be entitled to download all files listed as some Veritas product offerings entitle different file sets. For example, some product offerings vary by platform (Windows, Linux, Unix, etc.). In these cases you will only be able to download files for the platforms entitled by your VEMS entitlements.

To view which products and versions you are entitled to download, log into VEMS by clicking Licensing on Support home page. Once logged in, click Entitlements at the top of the page. Locate the entitlements for this product and verify that the Entitled Version for at least one entitlement for the product is greater than or equal to the version of the product you want to download. You will not be able to download the product if the version of the product you want to download is greater than the Entitled Version of all of the entitlements for the product.

The Download Center records all download transactions. After you click Download, you may be prompted to select a Veritas Entitlement Management System (VEMS) account. Select the VEMS account you wish to be the account of record for your download transaction.

Updates

Click Updates to view all software updates associated with this version of the product. Click the Update name to view the full details of the update and to download its files. Check the box next to each file that you wish to download, then click Download. The Download button will appear once you check the first file.

To download files in the Updates section:

• You must have a Veritas account. If you do not have a Veritas account, you can create one by clicking Sign in at the top of the page and then clicking Create one.
• You must log in with this Veritas account. To log in, click Sign in.
• Some updates require that you purchased a maintenance contract and that your contract was active at the time the update was release. If so, your Veritas account ID (email address) will need to be a registered user of a Veritas Entitlement Management System (VEMS) account that holds an entitlement for one of the product releases listed in the update's' Applies to the following releases section.
• If you are not a registered user of any VEMS accounts that entitles the download, you will be prompted to enter an Entitlement Code. Enter either a VEMS entitlement ID or appliance serial number. If the Entitlement Code can be matched to a VEMS entitlement that can entitle the download, you will be able to download the update. VEMS entitlement IDs and the appliance serial numbers can be found on on your Veritas Certificate or can be provided by registered VEMS user.

The Download Center records all download transactions. After you click Download, you may be prompted to select a VEMS account. Select the VEMS account you wish to be the account of record for your download transaction.

Getting Help

If you are having any trouble downloading files you think you should be able to download, first contact someone within your company that has administrative access to your VEMS account(s). If you still need assistance, you can chat with us from the Support homepage or contact us.

Error Message

V - Cannot run job. Your current capacity usage has significantly exceeded your licensed capacity. To increase the licensed capacity, contact your software provider to obtain a new license with an upgraded capacity.

0xec - The servers capacity usage has exceeded its licensed capacity. Backup jobs will fail until capacity usage drops below the licensed capacity.

UMI Code: V

UMI Code: V

Capacity Metering

Metered per Gigabyte instead of Terabyte. This allows more granular capacity licenses.

Subscription Good/Better/Best editions are licensed/priced based upon capacity usage meters.

Trial, NFR, and Beta editions provide unlimited capacity (however BE displays the calculated capacity usage in the BE Home page Capacity Usage widget for all BE editions).

Capacity licenses can be 'stacked' but they must all be the same BE edition. Because we will not require stacked Subscription licenses to have the same end-date, a BE servers total licensed capacity can change as new subscription licenses are added and subscription licenses expire.

The BE install/license dialog allows the user to choose to allocate less than the available license capacity for the server. The use case for this scenario would be if the customer has a large capacity license and they want to "spread" that available capacity around to multiple BE servers. From the capacity usage calculation/notification/enforcement operational perspective, BE only cares about the allocated capacity for the server.

Awareness and Enforcement

By default the capacity usage enforcement will be 'hard'. This can be controlled by a license policy attribute in the Veritas license SLF file.

There will be one daily 'nag' alert when capacity usage exceeds 85% (User configurable threshold). This is the same a previous BE capacity editions. All daily license compliance nag alerts are sent by default at 4AM (same as previous releases of BE). There is a registry value that can be added to change the time of day (hour) the license usage alerts are generated:

• Add new DWORD value "CheckEvalExpireHour" in the BE "Server" registry key.

• Set value 1 = 1 AM 4 = 4 AM, 12 = 12 noon, 23 = 11 PM, etc.

• Restart BE server service.

There will be one daily 'nag' alert when capacity usage exceeds %. This is the same a previous BE capacity editions.

By default BE provides a 15% 'grace' value above the licensed capacity usage value before 'hard' capacity usage enforcement may occur. The capacity grace percentage can be controlled by a license policy attribute in the Veritas license SLF file.

It is possible for 'stacked' licenses to have different license policy attributes (grace percent, grace period, and enforcement type). In the case of stacked licenses with different license policy attributes BE will use the MOST LIBERAL of the stacked attributes (largest grace percent, longest grace period, SOFT enforcement over HARD enforcement).

Once the server has exceeded the capacity usage grace value (%) we start a 30 day count-down until backup jobs begin failing. The capacity grace day period can be controlled by a license policy attribute in the Veritas license SLF file.

Once above % of licensed capacity usage the daily 'nag' alert will include the count-down number of days until BE will stop functioning.

After 30 consecutive days of exceeding % backup jobs will be failed when they run.

If the calculated capacity usage drops below % BE will reset the 30 day clock and backup jobs will be allowed to run (until their capacity usage is back above % for more than 30 days).

Capacity Usage Widget

The Capacity Usage widget on the BE Home page will also show the 30 day count-down clock if they have exceeded % capacity usage.

When the capacity usage countdown is triggered by exceeding the licensed capacity + capacity grace percentage (default license policy is 15%) the BE capacity usage widget (and daily capacity usage warning alert messages) will start at 30 days remaining.

• When the countdown gets down to less than 24 hours remaining in the 30 day countdown the BE capacity usage widget will display 1 day remaining.

• When the 30 day countdown runs out the BE capacity usage widget will display 0 days remaining and all backup jobs that run on that BE server will be failed with the capacity compliance error code/message.

Within the Capacity Usage widget Capacity Usage Detail Information dialog we are allowing the user to remove selected backup set(s) from the capacity usage calculation in order to allow the customer to work around "accidental" backups. This functionality is limited to three backup sets per 30 day period.

The Capacity Usage widget Capacity Usage Detail Information dialog also will include an "Export to CSV" button which will allow the user to export the capacity usage calculation data to a CSV file (for printing/audit purposes).

Capacity Usage Calculation

The calculation of the capacity usage was modified from previous BE releases to be the LARGEST FULL backup set for each protected resource within the last 30 days. This prevents the user from 'hacking' the capacity usage calculation by scheduling a small backup of a resource immediately after a large backup of the same resource.

Support for detecting and excluding backup sets from the capacity calculation of the same resource using different backup paths (i.e, backing up a VM using RAWS versus backing up the VM using vSphere agent) has been added. For example, if you back up the same resource using both a VM/Host backup and a beremote only the VM/Host backup sets should be included in the capacity usage calculation with this limitation only "System State or Utility partition may be used in the capacity calculation in this case when VM and agent based backup is taken" Backup Exec allows to exclude 3 Backup sets from capacity calculation and this can be availed in this scenario to ignore this limitation. Refer FAQ 16 in

Subscription Expiration Notification and Enforcement

Early warning alerts are generated 60, 30, and 5 days before a subscription license expires. This applies to all subscription editions (Gold, Silver, Bronze, NFR, Beta).

Early warning alerts for perpetual edition maintenance contracts continue to function as they did in previous BE releases.

No warning alert is specifically generated when a subscription expires.

After a subscription expires all jobs that run by bengine (backup, restore, duplicate, verify, catalog, P2V, B2V, IR, etc) are failed with an error/alert indicating the subscription has expired.

Troubleshooting: Installation and Configuration

Beserver debug log for Capacity Usage/Compliance status check. The line in bold contains the important information.

BESERVER 9/19/ AM 29 CImageMgmtBO::GetCapacityUsageGB:: CalculationPeriodDays=30

BESERVER 9/19/ AM 29 CImageMgmtBO::GetCapacityUsageGB:: CapacityInGigabytes=

BESERVER 9/19/ AM 01 ServerConfigBO:GetTotalCapacityUsedGB() TotalCapacityUsedGB=

BESERVER 9/19/ AM 01 ServerConfigBO:CheckUsageCapacityStatus() LicensedCapacityGB=, CapacityGracePercent=15, CapacityGraceDays=30, currentCapacityUsageGB=, capacityUsageTriggerGB=

BESERVER 9/19/ AM 01 ServerConfigBO:GetCapacityUsageGracePeriodCountdown() alshamasislamicinstitute.com.pkd(09/19/ )

BESERVER 9/19/ AM 01 ServerConfigBO:GetCapacityUsageGracePeriodCountdown() currentTriggerDate=09/19/ , triggerSpan=0, graceSpan=30, Countdown Days Remaining=30

BESERVER 9/19/ AM 01 ServerConfigBO:GetCapacityUsageGracePeriodCountdown() alshamasislamicinstitute.com.pkd(09/19/ )

BESERVER 9/19/ AM 01 ServerConfigBO:GetCapacityUsageGracePeriodCountdown() currentTriggerDate=09/19/ , triggerSpan=0, graceSpan=30, Countdown Days Remaining=30

BESERVER 9/19/ AM 29 CImageMgmtBO::GetCapacityUsageGB:: registry CMS_SERVER_CAPACITY_USAGE_CALCULATION_OVERRIDE=0

Backup Exec Readme

About this readme

^Back to top

Last updated October 22,

Copyright © Veritas Technologies LLC.

All rights reserved.

Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , "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.

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 the information in the Administrator's Guide. If the information in this file conflicts with the Administrator's Guide, the information in this file is correct.

For the most current information on Veritas Technologies products and services, please visit our website:

alshamasislamicinstitute.com.pk

Some hyperlinks in Veritas products and documentation lead to English-language websites that can be configured to display other languages upon the first visit.

What's new in Backup Exec

^Back to top

Table: What's new in Backup Exec

You can find a list of the new features in earlier releases of Backup Exec in the What's new in Backup Exec document.

Features or requirements no longer supported by Backup Exec

^Back to top

Jobs that contain data from the platforms that are no longer supported are not migrated during a product upgrade. Data from unsupported platforms cannot be backed up or restored from existing backup sets. Additionally, some jobs cannot be migrated automatically because the way in which they are set up in Backup Exec has changed. You can recreate those jobs manually.

For more information about the features and the platforms that are no longer supported in this release or will be retired in a future release, see the Backup Exec Software Compatibility List.

Backup Exec no longer supports the following features or software requirements:

• Exchange and SharePoint

• Backup Exec 16 Feature Pack 2 and later does not support ESXi version for vSphere.

• You cannot install Backup Exec on a server that runs Windows bit and Windows R2 bit servers.

• You cannot use an existing SQL Server or SQL Server instance as the location of the Backup Exec Database Instance.

Where to find more information

^Back to top

The Backup Exec technical support knowledge base contains the information that pertains to this release of Backup Exec.

The Backup Exec knowledge base provides technical notes, how-to topics, best practices, troubleshooting articles, and other valuable information to help you use Backup Exec.

For more information, go to the following URL:

alshamasislamicinstitute.com.pk

You can view Backup Exec resources at the following URL:

alshamasislamicinstitute.com.pk

Backup Exec installation notes

^Back to top

The following notes provide information about installing Backup Exec:

• Before you install or upgrade Backup Exec, review the Backup Exec Software Compatibility List (SCL) and Hardware Compatibility List (HCL) to ensure that your systems are compatible with the new version of Backup Exec.

• Backup Exec supports the Backup Exec server installation on supported bit operating systems only. Installation of Backup Exec on bit operating systems is no longer supported. However, you can install the Agent for Windows on bit operating systems.

• The Backup Exec installation program now uses the Microsoft .NET Framework version Not all versions of Windows support .NET Framework If the Backup Exec installation program encounters an operating system that requires a different version of the .NET Framework, Backup Exec blocks the installation and displays an error message that instructs you to install the required version of .NET Framework.

• If installation fails due to a SQL Express installation error, refer to the Microsoft SQL Server SP2 Express Edition readme:

  alshamasislamicinstitute.com.pk?id=

• An error (error code 2) may occur when you install SQL Express in an environment with the following conditions:

  • Active Directory is installed on a computer that runs Windows Server

  • The computer belongs to a root domain that uses a short domain name such as "alshamasislamicinstitute.com.pk".

    To avoid this error, install SQL Express to a child domain such as "alshamasislamicinstitute.com.pk", or use an instance of SQL Server instead of SQL Express.

• If the SQL Server instance is on the same server that you install Backup Exec on, the service account for the instance must have full permissions to the destination folder where Backup Exec is installed.

• If you perform a remote install or push-install, and you specify a domain administrator account for the Backup Exec Services, you must enter an existing domain administrator account. New accounts are not granted proper rights for domains. If you perform a local installation, you can specify a new local administrator account and the account is granted proper rights when it is created.

• When you install Backup Exec, or when you install tape device drivers from Backup Exec, a Microsoft message may appear that indicates one of the following:

  • The software that you are about to install does not contain a Microsoft digital signature.

  • Windows can't verify the publisher of this driver software.

  • The software has not passed Windows Logo testing.

    It is recommended that you allow the driver software to continue being installed.

    To prevent this message from appearing, you can change the policy setting. However, if you change the policy setting to "silently succeed", other driver software can be installed without any warning.

• The user-created folders that are in the Backup Exec installation folder or subfolders are deleted when you uninstall Backup Exec. If you want to keep the folders, copy them to another location before you uninstall Backup Exec.

The following notes provide information for Backup Exec upgrades:

• You cannot upgrade a Backup Exec server that runs on a bit operating system to Backup Exec. Migrate Backup Exec to a bit operating system, and then upgrade to the latest version of Backup Exec.

• The Back up files and directories by following junction points and mount points option is not selected by default. However, the jobs that are migrated keep the option that was selected in the previous version.

• When you upgrade the central administration server, any managed Backup Exec servers that are not also upgraded may show that there is no available space. If there is available space on the managed Backup Exec server, the backup operation runs. After you upgrade the managed Backup Exec server, the correct amount of available space appears.

• The Resource Selection column in the server details view on the Backup and Restore tab may display "unknown" if the selections are not available from the previous version of Backup Exec. The first time you run the backup job, the selections display in the Resource Selection column.

• When you upgrade to Backup Exec, the default cataloging option might change to Enable Instant GRT depending on your Backup Exec server environment and the version from which you are upgrading. After upgrade if this option is not set as the default, you can set the Enable Instant GRT option as the default option to take advantage of faster backups.

  To know more about the various scenarios and the possible changes to your existing jobs, see:

  alshamasislamicinstitute.com.pk

Software Compatibility List (SCL) and Hardware Compatibility List (HCL) and driver notes

^Back to top

The following notes detail information about the software and hardware that you use with Backup Exec:

• The Software Compatibility List (SCL) and the Hardware Compatibility List (HCL) contain the latest information about supported and unsupported software and hardware and are updated regularly. Before you install or upgrade Backup Exec, review the current compatibility lists to confirm the compatibility of your hardware and software.

• You do not need to install tape device drivers if Backup Exec runs on Windows Server and later. Kernel-mode drivers and alshamasislamicinstitute.com.pk are no longer installed if Backup Exec is installed on Windows Server and later. If you use older or unsupported tape devices, test the devices before you use Windows Server and later to determine the functionality in case kernel-mode drivers are required.

Cluster-aware Backup Exec notes

^Back to top

The following notes detail information about using cluster-aware Backup Exec:

• If a failover occurs during a backup that uses the Incremental - Changed Files - Reset Archive Bit backup method, Backup Exec skips the data that was backed up before 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 before the failover.

Agent for Windows notes

^Back to top

The following notes detail information about using the Agent for Windows with Backup Exec:

• When you uninstall the Agent for Windows, you may encounter a message that presents a list of applications that you should close before you continue the uninstall process. If the list contains only the following, you can ignore the message and continue the uninstall process.

  Backup Exec Setup Launcher

  Backup Exec Log Server

  Backup Exec Agent for Windows

  If additional applications appear, close all applications except the ones that are listed above before you continue with the uninstall process.

Deduplication Feature notes

^Back to top

The following notes detail information about using the Deduplication Feature with Backup Exec:

• If you cannot configure your OST device with this release of Backup Exec, you may need to install a later version of your OST plug-in. Please contact your vendor to obtain the most recent plug-in for your device.

• Deduplication requirements have changed for Backup Exec and later. You should review the topic Requirements for the Deduplication Feature in the Backup Exec Administrator's Guide.

• You cannot create a deduplication storage folder in a storage path that contains double-byte characters. The following error appears:

  A deduplication storage folder could not be created in the given directory.

• The ability to store a deduplication storage folder and its related database on separate volumes is no longer available. Backup Exec creates the database on the same volume as the deduplication storage folder. This applies to new deduplication storage folders that are created in Backup Exec and later. If you stored the database in a separate volume in a previous release of Backup Exec, that configuration is preserved when you upgrade to Backup Exec.

• If you want to back up a deduplication storage folder that is located in Shadow Copy Components, you should use a storage device other than the deduplication storage folder, such as tape, network storage, or OpenStorage deduplication devices.

• When you upgrade to Backup Exec, there may be a large amount of expired media that the deduplication storage folder or OST device must reclaim. This first backup job may take a long time to process.

• If you create a deduplication storage folder on a managed Backup Exec server, you receive the following error message on the storage folder's Properties page on the managed Backup Exec server:

  The System Logon Account cannot be used for a deduplication disk storage device.

  This error message should not appear on the central administration server. This error message cannot be removed, but it does not affect functionality. The properties on the managed Backup Exec server incorrectly display the logon account from its own database, but Backup Exec uses the logon account from the central administration server's database.

Agent for VMware notes

^Back to top

The following notes detail information about using the Agent for VMware:

• Backup Exec installed on Windows Server , does not allow GRT for VMware virtual machines running on Windows Server and Windows Server For more information, refer to the following technote:

  alshamasislamicinstitute.com.pk

• Do not install Backup Exec on the same computer where the VMware vCenter is installed. This configuration is unsupported at this time and causes backup jobs to fail. You must install vCenter and Backup Exec on different computers.

• A quiesced snapshot of a virtual machine that uses the VMware VSS provider may fail, which causes the backup job to fail with the following error:

  Final error: 0xea7 - The operation failed because the vCenter or ESX server reported that the virtual machine's configuration is invalid.

  A quiesced snapshot could not be created for the virtual machine <machine name>.

  If you have VMware's VSS provider installed, try the following options to resolve the issue:

  • Follow the instructions in the following VMware tech note.

    alshamasislamicinstitute.com.pk

    If the issue is not resolved, then try the following options.

  • If a CD or DVD is attached to the virtual machine, remove it, and then run the job again with the VMware VSS provider.

  • If a CD or DVD is not attached to the virtual machine, install the Backup Exec VSS provider, and then run the job again.

The following notes detail information about known issues in the VMware VDDK 6 that affect Backup Exec. See the VMware VDDK 6 Release Notes for details.

• SAN backups of cloned virtual machines on the same data center may fail or may fall back to NBD (if NBD is selected). Also, SAN redirected restore jobs may fail or fall back to NBD if the original virtual machine still exists on the same datastore.

• Hotadd transport may fail or fall back to NBD for any disks that are larger than 2 TB on vVol datastores. This issue applies to both backup and restore jobs.

• Hotadd transport may fail or fall back to NBD during a restore of a virtual machine to a vVol datastore if the Backup Exec server is on a different datastore.

The following note details information about instant recovery of a VMware virtual machine:

To run an instant recovery job for a backup set that is on one of the following devices, create a duplicate backup job and then target the backup job to a disk storage device. You can use the duplicate backup to create an instantly recovered virtual machine.

• Tape storage

• Deduplication disk storage

• Cloud storage

• Disk cartridge devices such as RDX

Agent for Hyper-V notes

^Back to top

The following notes detail information about using the Agent for Hyper-V:

• Restore of Hyper-V Host Component on a Windows Hyper-V server fails. As a workaround, stop the Hyper-V Virtual Machine Management service, and then proceed with the restore.

Review the following notes for the instant recovery feature:

• To run an instant recovery job for a backup set that is on one of the following devices, create a duplicate backup job and then target the backup job to a disk storage device. You can use the duplicate backup to create an instantly recovered virtual machine.

  • Tape storage

  • Deduplication disk storage

  • Cloud storage

  • Disk cartridge devices such as RDX

Review the following notes before you upgrade the Backup Exec server:

In Backup Exec 15 Feature Pack 4 and later, the default option for processing Hyper-V backups has changed to Use the standard processing method.

• When you upgrade from Backup Exec 15 Feature Pack 3, the existing Hyper-V backup setting does not change. Existing and new backup jobs use the setting that was configured in Feature Pack 3, unless you change it.

• When you upgrade from Backup Exec 15 Feature Pack 2 or earlier, the default Hyper-V backup setting for existing jobs is Use the standard processing method. Existing and new backup jobs use this setting unless you change it.

SharePoint Agent notes

^Back to top

The following note detail information about using the SharePoint Agent with Backup Exec:

• Backup Exec does not support Project Server Service Application from SharePoint and

Exchange Agent notes

^Back to top

The following notes detail information about using the Exchange Agent with Backup Exec:

• If the Microsoft Exchange writer is not available when you perform a backup of Exchange , you may receive the following error:

  V - Snapshot Technology: Initialization failure on: "Microsoft Information Store". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). Snapshot technology error (0xE): The database specified for the snapshot was not backed up because the database was not mounted.

  To confirm that the error occurs because the Microsoft Exchange Writer is not in the output, run the following command on the Exchange server:

  alshamasislamicinstitute.com.pk LIST WRITERS

  Refer to the following URL for more information:

  alshamasislamicinstitute.com.pk

  Note:

  Ensure that you include the Exchange Windows Service "Microsoft Exchange Replication" in any troubleshooting procedures because it hosts the Microsoft Exchange Writer.

Agent for Oracle notes

^Back to top

The following notes provide information about using the Backup Exec Agent for Oracle on Windows or Linux Servers with an Oracle 12c database:

• Before running a pluggable database (PDB) point-in-time (PIT) restore, either server-initiated or dba-initiated, you must manually add a non-admin Oracle user to the administrators group, and then restart the Oracle service. This condition is applicable only if the Oracle 12c database is running on a Windows server with a non-admin Oracle user.

• If the Oracle instance you want to protect is part of an Oracle 12c RAC on Linux, switch to the Oracle user, and then run the Backup Exec Agent Utility for configuring the Oracle instance on each RAC node.

• For configuring the Oracle 12c instance in the Backup Exec Agent Utility, use a user that has SYSBACKUP privileges.

• Oracle does not recommend restoring only the ROOT database because it might cause metadata inconsistencies. Instead, you should recover the whole container database (CDB).

  alshamasislamicinstitute.com.pk

• The point-in-time (PIT) restore job of the root fails with an error message: "Specifying CDB$ROOT database is not supported".

  This feature is not supported by Oracle.

  alshamasislamicinstitute.com.pk

• The Oracle Agent Utility cannot validate a path specified on the ASM disk and accepts the path as specified. Therefore, you must ensure that the path you entered is correct and accessible.

• During a pluggable database (PDB) point-in-time (PIT) restore, the restore job is in a queued state for 10 minutes by default. After 10 minutes, the restore job resumes. See the following technote for more information.

  alshamasislamicinstitute.com.pk

System Disaster Recovery notes

^Back to top

The following notes detail information about using Simplified Disaster Recovery with Backup Exec:

• To create a Simplified Disaster Recovery (SDR) disk image on Windows Server operating system, Backup Exec supports Microsoft Windows Assessment and Deployment Kit (ADK) as the default ADK for SDR creation. You have to manually download and install Windows ADK using the following link.

  alshamasislamicinstitute.com.pk?ocid=tia

  You should review the topic for Simplified Disaster Recovery in the Backup Exec Administrator's Guide.

• To create a Simplified Disaster Recovery (SDR) disk image on Windows Server R2 to Windows Server operating systems, Backup Exec supports only Windows ADK

  You should review the topic for Simplified Disaster Recovery in the Backup Exec Administrator's Guide.

• Volumes created on storage pools and spaces in Windows ADK environment are not recognized by the restored Windows Server operating system. This is a Microsoft issue.

Central Admin Server Feature notes

^Back to top

The following notes detail information about using the Central Admin Server Feature (CAS) with Backup Exec:

• If scheduled jobs begin to stall, then complete with a status of "Recovered", and then have a status of "On Hold", do the following to fix the issue:

  • On the central administration server or the managed Backup Exec server, click the Backup Exec button, click Configuration and Settings, and then select Backup Exec Settings.

  • In the left pane, click Job Status and Recovery.

  • In the Stalled field, enter 15 minutes.

  • In the Recovered field, enter 45 minutes.

• In a CAS environment, storage devices may be acquired at a slower rate than in a non-CAS environment. To increase the rate of acquisition, change the DelayBeforeMountTime value to zero in the following registry key:

  HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Misc

• If you perform a rolling upgrade and have updated the central administration server to Backup Exec 16 Feature Pack 2, do not create disk storage on any managed Backup Exec servers that have not been updated yet. You can create disk storage on the managed Backup Exec servers after you upgrade the servers to Backup Exec.

Veritas now offers Professional Service for Backup Exec™ — the Backup Exec Installation, Migration and Upgrade Service — this service will help you implement the latest version of Backup Exec.

The service includes the following three options:

Option 1: An installation of the current version of Backup Exec or a previous version if required.
Option 2: An upgrade of the Backup Exec Server to the latest version of Backup Exec
Option 3: A migration of the data from an existing Backup Exec server to a new Backup Exec server

To purchase the service, contact your local software reseller or Veritas account representative today. Click here for more details.

You may also reach out to Authorized Veritas Distribution Partner using following link:
alshamasislamicinstitute.com.pk

IMPORTANT: Prior to following the information in this article, ensure that the information in Article  and Article has been reviewed and understood

Steps to Upgrade to Backup Exec x or x

Below are the steps to upgrade from earlier versions of Backup Exec. 

To run a direct upgrade to Backup Exec x minimum version required is Backup Exec

To run a direct upgrade to Backup Exec x minimum version required is Backup Exec 15

To run a direct upgrade to Backup Exec 22  minimum version required veritas backup exec 20 Backup Exec

Any earlier version of Backup Exec will need to be upgraded to minimum supported verions to be upgraded to Latest version of Backup Exec

Steps to download the Backup Exec Licenses, Installation Files, Updates, Feature Pack, veritas backup exec 20, Service Pack, Hotfix and Patches within VEMS

Backup Exec  Download

1.      Login to the Backup Server with the Backup Exec service account credentials. Open Windows Services MMC and review the Backup Exec serivces. The account used to Start teh Backup Exec Server or Job Engine service is the Backup Exec Service Account to be used during the upgrade process.

2.      Stop all the Backup Exec services and the SQL service for BKUPEXEC.

3.      Tape a Copy/Backup of the Backup Exec Data and Catalogs folders to safe location. 

 X:\Program Files\Symantec\Backup Exec\” folder

or

“ X:\Program Files\Veritas\Backup Exec\”

[X represents driver where Backup Exec is installed]

4.      If custom reports are configured copy or backup of “ X:\Program Files\Veritas\Backup Exec\Reports” will also need to be taken

5.      Start the SQL service for BKUPEXEC

6.      Mount the ISO for the Backup Exec x,  x, veritas backup exec 20, or 22 installer onto the Backup Server

7.      Right click on alshamasislamicinstitute.com.pk and "Run as Administrator", veritas backup exec 20. (Due to security settings, some environments may require alshamasislamicinstitute.com.pk to be started using 'Run as Admin')

Additional Notes for (Backup Exec 22)

• During an upgrade to Backup Execthe installer will deploy SQL 64bit BKUPEXEC64 instance to host the Backup Exec database. It will remove the Local BKUPEXEC SQL instance ( default BE SQL Instance used before BE ) towards the end of the upgrade
• If the older version of Backup Exec being upgraded uses a custom SQL Instance i.e. anything other than BKUPXEC SQL instance name, then the Backup Exec upgrade will continue to use the same SQL version.
.• A fresh installation of Backup Exec deploys SQL Express 64bit instance, veritas backup exec 20. This default instance name is “BKUPEXEC64”.

8.     Click on Backup Exec option for upgrade or Fresh install

9.      Click on I accept and click Next

       Click on Local install for Upgrade or Fresh Install and click “Next”

     Wait for veritas backup exec 20 Environment Check to Complete

     Enter the License Keys and click “Next”. For more information related to step by step instructions for installing license keys review - Step By Step guide to install and review Backup Exec licenses

     Enter the Backup Exec Service account username and veritas backup exec 20 and click “Next”

     Click on Next and Install until you get the Migration Screen and wait for it to complete.

     Once Migration is complete it should show “successful”, you can review the Migration report and click on “I Accept” and continue if all looks good.

     Continue with the Upgrade Steps:

     Once Upgrade or Veritas backup exec 20 is complete, reboot if required or asked.

     All your configuration should be available after the reboot.

     After reboot once the Backup Server is up and if the setup has Deduplication folder configured, it will be listed as “OFFLINE”.

     In the alerts you will see the below alert which will indicate that the Deduplication folder is being converted to the new version 10 with estimated time

     You will need to then check the PDDE conversion logs to verify if conversion was successful,  located in “C:\Program Files\Symantec\Backup Exec\Logs” File name: “PDDE10 conversion log”

     You will need at least 12% free space on the Drive that hosts the Deduplication folder for the conversion to complete successfully.

     Once the conversion completes you will need to restart all Backup Exec services and the devices should now be online.

    Make sure you upgrade all your remote agents and that can be done by right clicking on each server and clicking on update. They may require a reboot after upgrade and hence you can decide when and how you would like to upgrade the remote agents.

Note:-

To run a direct upgrade to Backup Exec x minimum version required is Backup Exec

To run a direct upgrade to Backup Exec 21 minimum version required is Backup Exec 15

Any earlier version of Backup Exec will need to be upgraded to supported versions to be upgraded to Latest version of Backup Exec

For more information related to step by step instructions for installing license keys review - Step By Step guide to install and review Backup Exec licenses

Base and upgrade installers

Click Base and upgrade installers to view the files associated with this product version. Check the box next to each file that you wish to download, then click Download. The Download button will appear once you check the first file. After you click Download, veritas backup exec 20, you may be prompted to select a Veritas Entitlement Management System (VEMS) account. If you are asked to select a VEMS account, select the account that you wish to be the account of record for your download transaction.

To download files in the Base and upgrade installers section:

• You must have a Veritas account. If you do not have a Veritas account, you can create one by clicking Sign in at the top of the page and then clicking Create one.
• Your Veritas account ID (email address) must be registered as a user of a VEMS account that holds an entitlement for the product with an Entitled Version (displayed in VEMS) that is greater than or equal to this product's' version.
• Your Veritas account ID must have either the VEMS Administrator or Download Software privilege.
• You must log in with this Veritas account. To log in, click Sign in.

Note: You may not be entitled to download all files listed as some Veritas product offerings entitle different file sets. For example, some product offerings vary by platform (Windows, veritas backup exec 20, Linux, Unix, etc.). In these cases you will only be able to download files for the platforms entitled by your VEMS entitlements.

To view which products and versions you are entitled to download, log into VEMS by clicking Licensing on Support home page. Once logged in, click Entitlements at the top of the page. Locate the entitlements for this product and verify that the Entitled Version for at least one entitlement for the product is greater than or equal to the version of the product you want to download. You will not be able to download the product if the version of the product you want to download is greater than the Entitled Version of all of the entitlements for the product.

The Download Center records all download transactions. After you click Download, veritas backup exec 20, you may be prompted to select a Veritas Entitlement Management System (VEMS) account. Select the VEMS account you wish to be the account of record for your download transaction.

Updates

Click Updates to view all software updates associated with this version of the product. Click the Update name to view the full details of the update and to download its files. Check the box next to each file that you wish to download, then click Download. The Download button will appear once you check the first file.

To download files in the Updates section:

• You must have a Veritas account. If you HELICON FOCUS PRO 7.7.6 CRACK WITH LICENSE KEY FREE not have a Veritas account, you can create one by clicking Sign in at the top of the page and then clicking Create one.
• You must log in with this Veritas account. To log in, click Sign in.
• Some updates require that you purchased a maintenance contract and that your contract was active at the veritas backup exec 20 the update was release. If so, your Veritas account ID (email address) will need to be a registered user of a Veritas Entitlement Management System (VEMS) account that holds an entitlement for one of the product releases listed in the update's' Applies to the following releases section.
• If you are not a registered user of any VEMS accounts that entitles the download, you will be prompted to enter an Entitlement Code, veritas backup exec 20. Enter either a VEMS entitlement ID or appliance serial number. If the Entitlement Code can be matched to a VEMS entitlement that can entitle the download, you will be able to download the update. VEMS entitlement IDs and the appliance serial numbers can be found on on your Veritas Certificate or can be provided by registered VEMS user.

The Download Center records all download transactions. After you click Download, you may be prompted to select a VEMS account. Select the VEMS account you wish to be the account of record for your download transaction.

Getting Help

If you are having any trouble downloading files you think you should be able to download, first contact someone within your company that has administrative access to your VEMS account(s). If you still veritas backup exec 20 assistance, you can chat with us from the Support homepage or contact us.

Description

This article contains information about the latest Alerts, releases notifications, patches as well as known issues for Backup Exec x.  

Alerts

Veritas Technologies LLC issues alerts for issues involving potential data loss, security vulnerabilities or other critical issues often requiring immediate action, veritas backup exec 20. Below you will find links to the latest Alerts for Backup Exec x:

• Oracle Database Restore from Duplicate set may fail if duplicate job was configured to use “'Most Recent Full Backup” job option. alshamasislamicinstitute.com.pk
• Vmware backup veritas backup exec 20 the VMware Virtual Machine on Backup Exec may skip the backup of VMDKs if the Global Excludes are configured, veritas backup exec 20. ()
   

Major and Minor Releases
Backup Exec   Release Date: 6 November

Backup Exec   Release Date: 2 April

Backup Exec   Release Date: 13 August

Backup Exec   Release Date: 23 October

Backup Exec   Release Date : 6 May

Backup Exec   Release Date : 2  September

Backup Exec   Release Date : 12  December 

Downloads:

See the Related Article, Veritas Entitlement Management System Guide, for more information on licenses and downloads.

Patches

Known Issues

• Backup Exec console crashes after installing .NET Framework ()
• Deduplication Option is no longer licensed in this upgrade" message appears and prevents Backup Exec from being installed ()
• Unable to edit or create backup jobs targeted to Deduplication storage after upgrading to Backup Exec ()
• Vmware backup of the VMware Virtual Machine on Backup Exec may skip the backup of VMDKs if the Global Excludes are configured. ()

The following entries are the top technical solutions from Support:
 

Back to Top

End of Symantec LiveUpdate Services for Backup Exec

End of Symantec LiveUpdate Services for Backup Exec on May 02,

Back to Top

Following is a list of Admin Guides, veritas backup exec 20, HCLs and SCLs for most recent supported Backup Exec versions.

Click on the desired link to download the HTML or PDF file:

The easy-to-remember way to get back to this page is to use alshamasislamicinstitute.com.pk

For End of Support information, veritas backup exec 20, please see alshamasislamicinstitute.com.pk

Steps to download the Backup Exec Licenses and Installation Files within VEMS

Please follow this link for more information about the Backup Exec Migration Assistant tool and migrating an existing Backup Exec installation (Backup Exec15, 16, veritas backup exec 20, 20) to a new server platform.
alshamasislamicinstitute.com.pk

Please see this link for information about how and where to obtain updates

How to get updates for Backup Exec - Feature Pack, Service Pack, Hotfix, Patches and Device Drivers 

To obtain the latest documents and localized language documents, please see here.  The local language can be selected from remo recover android globe icon in the top right-hand corner of the screen.

See the Related Articles section below for information about supported configurations and more.