This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
IntroductionThis document lists the available operating systems, platforms, and applications specifically supported by Symantec to be compatible with Backup Exec ™ 2014.
The following guidelines regarding this Software Compatibility List (SCL) should be understood:
• Symantec support of 3rd party manufacturer products:Symantec will cooperate with 3rd party vendors and attempt to assist in the diagnosis of problems found between the 3rd party products and Symantec products.Symantec Technical Support, for the combination of Symantec and 3rd party products listed in this document, is conditional on the 3rd party product being supported bythe original manufacturer or vendor. If the original vendor has ceased providing support for a version of their product, Symantec also will no longer be able to providesupport on that product in combination with our products.
• Minor update version support:The contents of this document including 3rd party applications, databases, operating systems, in combination with Symantec products represent what has been testedin Symantec labs, or in Symantec-supervised partner labs, but is not intended to be a complete list of supported products and versions. Manufacturers of these productsmay frequently release minor version updates to their products as maintenance during their product's normal life cycle. (e.g. version 1.x.x.x) that may not be explicitlylisted in this document. In these situations where the base or major version of the product is listed as supported in this document but the minor maintenance update isnot, Symantec will provide "reasonable effort" support on these versions until specific testing of them has completed.
• Not every combination of software and hardware has been tested:Symantec provides reasonable effort to qualify Backup Exec with as many different operating systems, service packs, hardware platforms, database application servicepacks, and other applications as possible. However, due to the number of combinations, it is not possible to test all combinations for compatibility. If a particular servicepack or version is not listed as specifically supported by Symantec, it may work fine but it has not been explicitly tested by Symantec with Backup Exec and may not beeligible for support.
• To request additions to this list:Software is selected and prioritized for certification based on market research and input from the field, including customer feedback. If a customer would like to havesoftware considered for inclusion on this SCL, simply submit the request by email. [Send us an email request.]<mailto:[email protected]?subject=Backup Exec 2014 SCL - Customer Feedback> Requests will be reviewed by the appropriateSymantec Product Management team members for possible certification, with final decisions based on the overall fit with the product, target market, and frequency ofrequest.
• Alternative Configurations:Our Licensed Software is designed to interoperate with many types of systems, applications, and hardware. Sometimes a customer may choose to use our LicensedSoftware in an "Alternative Configuration", namely, an environment that has not been validated, approved, or verified to operate with our Licensed Software or whichdoes not support such Licensed Software or only supports limited functionality. Symantec does not support Alternative Configurations, and we have no obligation toprovide Support Services to Licensed Software in an Alternative Configuration. Symantec makes no warranty with respect to use of Licensed Software in an AlternativeConfiguration and any such use is at your own risk. A "Supported Configuration" might be converted into an Alternative Configuration where a vendor modifies one ofits components that is part of the original Supported Configuration. As a consequence, your Licensed Software would then be operating in an Alternative Configuration.If you experience a problem with the Licensed Software in an Alternative Configuration or if your issue deals with script that was not developed by Symantec or anauthorized consulting partner, then we may ask you to reproduce the problem in a Supported Configuration environment. Please note we have no obligation to attemptto resolve problems that cannot be replicated in a Supported Configuration. However, if the problem can be replicated in a Supported Configuration, we will investigatethe problem in that Supported Configuration and attempt to resolve it. If the problem cannot be replicated in a Supported Configuration, then Symantec has no obligationto investigate or attempt to resolve the problem.
What's NewThis document reflects updates for Backup Exec 2014 Service Pack 2 and newer: <http://www.symantec.com/docs/TECH225093.>• Exchange 2013 CU8 is supported.• OES 11 SP2 is supported.• RHEL 6.6 RMAL is supported.• RHEL 7 RMAL is supported.• Enterprise Vault 11.0.1 is supported (SP1).• ESXi 5.1 U3 is supported.• vCenter Server 5.1 U3 is supported.• vCenter Server Appliance 5.1 U3 is supported.
Contents
Getting StartedBackup Exec Server Operating
System CompatibilityAgent Operating System
Compatibility
Agent for Applications and DatabasesCompatibility
Agent for VMware and Hyper-VCompatibility Backup Exec Upgrade Compatibility
Backup Exec Feature SpecificCompatibility 3rd Party Software Compatibility End-of-Life information
Backup Exec 2014 Hardware Compatibility List (HCL) <http://www.symantec.com/docs/TECH214803>
What’s Different in Backup Exec 2014 <http://www.symantec.com/docs/DOC5216>
Supported languages for the Backup Exec• Backup Exec supports only the following languages. No other combination of Backup Exec and operating system language configurations are tested or qualified.
Languages
Chinese (Simplified), Chinese (Traditional), English, French, German, Italian, Japanese, Korean, Brazilian Portuguese, Russian, Spanish
Operating System You cannot install a Backup Exec server on a computer that runs the Windows Server Core installation option of Windows Server 2008/2012. You can only
install the Backup Exec Agent for Windows on Server Core computers.
On the computers that run Windows 2003, ensure that those computers have Windows Imaging Component installed before you install Backup Exec 2014.
Windows Imaging Component is required to install Backup Exec 2014.
See the Microsoft website for more information on downloading and installing Windows Imaging Component.
You cannot install SQL Express or SQL Server on a Windows Server 2008 computer that is configured in a Read Only Domain Controller (RODC) role. The
Read Only Domain Controller role does not let you use the local accounts that are required for SQL Express and SQL Server. When you install Backup Exec on
an RODC computer you must select a remote SQL instance for the Backup Exec Database.
For Windows Server 2012 and later computers, you cannot install Backup Exec or the Agent for Windows on a volume that is enabled for deduplication in
Installation disk space 1.26 GB (Typical installation)
1.91 GB (Includes all options)
Note: Disk space requirements may vary depending on the operations performed, the options installed, and the specific system configuration. The Backup Exec
Database and catalogs require additional space. An additional 525 MB is required for SQL Express. Any disk storage that you use also requires additional
space.
Other Hardware The following hardware is recommended:
• Network interface card or a virtual network adapter card
• CD/DVD drive
• A mouse
Storage Hardware You can use storage media drives, robotic libraries, removable storage devices, and non-removable hard drives.
You can find a list of compatible types of storage at the following URL:
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.
Certifications
Name Source
Certified for Windows Server Click to view a list of Backup Exec Windows Logo certifications: <http://windowsservercatalog.com/results.aspx?&bCatID=1372&cpID=2038>
FIPS 140-2 Click to view the validation certificate: <http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140crt/140crt918.pdf>
Backup Exec Server Operating System CompatibilityWindows Operating System Compatibility
Notes:Backup Exec 2014 Small Business Edition and Backup Exec Quickstart Edition are compatible with all supported Windows Operating Systems that are listed in thefollowing sections.
Microsoft
Microsoft - Windows Essential Business Server 2008
Name Version Service Pack CPU Architecture
Windows Essential Business Server 2008 Premium SP2 x86-32, x86-64
Windows Essential Business Server 2008 Standard SP2 x86-32, x86-64
Microsoft - Windows Server 2003 R2
Name Version Service Pack CPU Architecture
Windows Server 2003 R2 Datacenter Edition SP2 x86-32, x86-64
Windows Server 2003 R2 Enterprise Edition SP2 x86-32, x86-64
Windows Server 2003 R2 Standard Edition SP2 x86-32, x86-64
Agent Operating System CompatibilityAgent for Windows Compatibility
Notes:• Backup Exec 12.5, 2010, 2010 R2, 2010 R3, and 2012 Agents are backwards compatible with Backup Exec 2014 servers for the purpose of upgrades only. Thisconfiguration is not recommended or supported for extended periods. Every effort should be made to get all Backup Exec components to the same version as soon aspossible.• Any data that was previously backed up using the Intelligent Image Option can no longer be restored using Backup Exec 2014.
Agent for Linux CompatibilityNotes:• The Advanced Open File feature for Agent for Linux is supported only on select Red Hat Enterprise Linux (RHEL) and Novell SUSE Enterprise Linux Server (SLES)platforms. Please refer to the RHEL and SLES footnotes to identify the supported versions.• Some versions of Linux may require that you install the libstdc++.so.5 package. <http://www.symantec.com/docs/TECH52256>
Asianux Consortium
Name Version Service Pack CPU Architecture
Asianux [1] 3.0 x86-32, x86-64
1. Backup Exec client-side deduplication is supported for 64-bit Linux systems.
1. Advanced Open File Option for Linux file system support includes ext2, ext3, ext4 and ReiserFS.
2. Backup Exec client-side deduplication is supported for 64-bit Linux systems.
3. File system support includes ext2, ext3, ReiserFS, JFS, VxFS.
4. The Remote Agent for Linux Servers (RALUS) does not support Red Hat servers that have been installed using the 'minimal' installation option.
5. File system support includes ext4.
6. File system support includes ext2, ext3, and ext4.
7. Advanced Open File Option is not supported.
SUSE
Name Version Service Pack CPU Architecture
SUSE Linux Enterprise Server [1] [2] [3] [4] 10 SP3 x86-32, x86-64
SUSE Linux Enterprise Server [1] [2] [3] [4] 10 SP4 x86-32, x86-64
SUSE Linux Enterprise Server [1] [2] [3] 11 SP1 x86-32, x86-64
SUSE Linux Enterprise Server [1] [2] [3] 11 SP2 x86-32, x86-64
SUSE Linux Enterprise Server [1] [2] [5] 11 SP3 x86-32, x86-64
SUSE Linux Enterprise Server [2] [5] [6] 12 x86-64
1. Advanced Open File Option for Linux file system support includes ext2, ext3, ext4 and ReiserFS.
2. Backup Exec client-side deduplication is supported for 64-bit Linux systems.
3. File system support includes ext2, ext3, ext4, ReiserFS, JFS, and VxFS.
4. Supported with Open Enterprise Server (OES) 2.0 SP3, with Novell Storage Services (NSS) file system, NDS, GroupWise, and iFolder on 32-bit and 64-bit platformsfor SUSE Linux Enterprise Server 10.
5. File system support includes ext2, ext3, and ext4.
6. Advanced Open File Option is not supported.
Agent for Mac CompatibilityNotes:• Single sign-on accounts for OS X are not supported. Local Linux accounts must be used for compatibility with Agent for Mac.
Apple
Name Version Service Pack CPU Architecture
Mac OS X 10.5 (Leopard) .8 x86-32, x86-64
Mac OS X [1] [2] [3] 10.6 (Snow Leopard) x86-32, x86-64
Mac OS X 10.7 (Lion) x86-64
Mac OS X 10.9 (Mavericks) .2 x86-64
1. All Mac OS X 10.6 platforms are supported.
2. Includes support for 64-bit, which means the ability to run a 32-bit binary on a chipset that supports the 64-bit instruction set.
3. Workstation and Server
Remote Media Agent for Linux Compatibility
• The Advanced Open File feature for Remote Media Agent for Linux is supported only on select Red Hat Enterprise Linux (RHEL) and Novell SUSE Enterprise LinuxServer (SLES) platforms. Please refer to the RHEL and SLES footnotes to identify the supported versions.
Agent for Applications and Databases CompatibilityNotes:• The Backup Exec Agent for Oracle on Windows or Linux Servers does not support multiple Oracle database versions that are installed on the same computer.• Advanced Disk-based Option off-host backups of clustered Exchange databases in Exchange 2007/Exchange 2010 Clustering solutions are not supported.• Legacy mailbox backups are no longer supported with any version of Exchange. This functionality has been replaced by the Granular Recovery Technology (GRT)feature.• Backup Exec 2014 Small Business Edition only supports Microsoft Exchange, Active Directory, SQL, Sharepoint, and Hyper-V. Any other application or database notspecifically listed should be considered unsupported by Backup Exec Small Business Edition at this time.• Backup Exec supports all editions of the Microsoft SQL Server versions even though they are not specifically listed.
IBM
Name Version Service Pack CPU Architecture OS
Lotus Domino [1] [2] 8.0 x86-32, x86-64 Windows
Lotus Domino [1] [2] 8.0 .1 x86-32, x86-64 Windows
Lotus Domino [1] [2] 8.0 .2 x86-32, x86-64 Windows
Lotus Domino [1] [2] 8.5 x86-32, x86-64 Windows
Lotus Domino [1] [2] 8.5 .1 x86-32, x86-64 Windows
Lotus Domino [1] [2] 8.5 .2 x86-32, x86-64 Windows
Lotus Domino [1] [2] 8.5 .3 x86-32, x86-64 Windows
Domino 9.0 x86-32, x86-64 Windows
1. 32-bit Lotus Domino installed on 64-bit systems is supported.
2. Lotus Domino databases in NSF format is supported. (Lotus/DB2 database format is not supported)
1. For Exchange 2007 running on Windows 2008. Please see the following TechNote for further details <http://www.veritas.com/docs/000088536.> Symantec does notsupport installing Microsoft Office on the same server where the CDO/MAPI components are installed.
2. Backup Exec does not support Microsoft Exchange Management role scopes.
3. To back up Microsoft Exchange Server 2010, you must install Backup Exec on a Microsoft Windows 2008 SP2 64-bit server or newer.
4. To back up Microsoft Exchange Server 2013, you must install Backup Exec on a Microsoft Windows 2008 R2 SP1 64-bit server or newer.
SQL Server [1] [2] 2012 SP2 x86-32, x86-64 Windows
SQL Server [1] [2] 2014 x86-32, x86-64 Windows
1. For "AlwaysOn Availability Groups”, the Full backup method is supported for the Primary Replica SQL instance, or the Full Copy backup method is supported for theSecondary Replica SQL instance. Backups and restores are not supported via the SQL Listener name. Please see the following TechNote for further details:<http://www.veritas.com/docs/000021670>
2. For mirroring and log shipping, only Full/Copy backups on the primary nodes are supported.
Microsoft - Windows Active Directory
Name Version Service Pack CPU Architecture OS
Windows Active Directory 2003 SP2 x86-32, x86-64 Windows
Windows Active Directory 2003 R2 SP2 x86-64 Windows
Windows Active Directory 2008 SP2 x86-32, x86-64 Windows
Windows Active Directory 2008 R2 x86-64 Windows
Windows Active Directory 2008 R2 SP1 x86-64 Windows
Windows Active Directory 2012 x86-64 Windows
Windows Active Directory [1] 2012 R2 x86-64 Windows
1. Windows 2012 R2 Active Directory (AD) Granular Recovery Technology (GRT) is supported only with Backup Exec Servers on Windows 2012 R2 operating systems.Please see the following TechNote for further details <http://www.veritas.com/docs/000087447.>
MBR – basic disks Both application-level Granular Recovery Technology (GRT) and file/folder-level GRT are supported.
MBR – dynamic disks GRT is not supported.
GPT – basic disks Both application-level GRT and file/folder-level GRT are supported.
GPT – dynamic disks GRT is not supported.
Windows Storage Spaces GRT is not supported.
Hyper-V: File System Support
Configuration Support
NTFS Both application-level GRT and file/folder-level GRT are supported.
FAT Both application-level GRT and file/folder-level GRT are supported.
ReFS Both application-level GRT and file/folder-level GRT are supported, if the Backup Exec server uses the same version or a later version of the operating
system that the guest uses.
Windows Data Deduplication Role/Feature Both application-level GRT and file/folder-level GRT are supported, if the Backup Exec server uses the same version or a later version of the operating
system that the guest uses, and if the Windows Deduplication Role/Feature is enabled on the Backup Exec server.
Hyper-V: VM Disk Structure
Configuration Support
Pass-Through Disk The data on the pass-through disk is not backed up. File/folder-level GRT is attempted. Application-level GRT is not attempted.
Fibre Channel Adapter The data on the Fibre Channel Adapter is not backed up. File/folder-level GRT is attempted. Application-level GRT is not attempted.
Shared vhd/vhdx files The data on the shared vhdx file is not backed up. File/folder-level GRT is attempted. Application-level GRT is not attempted.
The virtual machine is protected with an offline backup The data is protected, but it is not application-consistent. File/folder-level GRT is attempted. Application-level GRT is not attempted.
SMB (Server Message Block) network protocol The data on the SMB is not backed up. File/folder-level GRT is attempted. Application-level GRT is not attempted.
MBR - basic disks Both application-level Granular Recovery Technology (GRT) and file/folder-level GRT are supported.
MBR - dynamic disks Supports GRT of all dynamic volume types, except RAID 5.
GPT - basic disks GRT is not supported.
GPT - dynamic disks GRT is not supported.
Windows Storage Spaces GRT is not supported.
VMware: File System Support
Configuration Support
NTFS Both application-level GRT and file/folder-level GRT are supported.
FAT Both application-level GRT and file/folder-level GRT are supported.
ReFS Both application-level GRT and file/folder-level GRT are supported, if the Backup Exec server uses the same version or a later version of the operating
system that the guest uses.
Windows Data Deduplication Role/Feature Both application-level GRT and file/folder-level GRT are supported, if the Backup Exec server uses the same version or a later version of the operating
system that the guest uses, and if the Windows Deduplication Role/Feature is enabled on the Backup Exec server.
VMware: VM Disk Structure
Configuration Support
RDM disks - virtual compatibility mode The data on the virtual compatibility mode RDM disk is backed up. GRT is not attempted. The virtual compatibility mode RDM disk
cannot be restored. Perform a redirected restore to restore data on the virtual compatibility mode RDM disk.
RDM disks - physical compatibility mode or independent disks The data on the physical compatibility mode RDM disk is not backed up. All other disks are backed up. GRT is not attempted.
Backup Exec Upgrade CompatibilityUpgrade and Rolling Upgrade Compatibility
Notes:Features or requirements that are no longer supported by Backup Exec may affect your ability to restore backed-up resources. Please review the section titled 'Featuresor requirements no longer supported by Backup Exec' in this document, or in this technote: <http://www.symantec.com/docs/TECH178552>
Direct upgrade to Backup Exec 2014
Name Version Service Pack
Backup Exec for Windows Server [1] 12.5 All Service Packs
Backup Exec for Windows Servers 2010 All Service Packs
Backup Exec for Windows Servers 2010 R2 All Service Packs
Backup Exec for Windows Servers 2010 R3 All Service Packs
Backup Exec 2012 All Service Packs
1. To upgrade versions of Backup Exec prior to 12.5 to Backup Exec 2014, you must first upgrade to Backup Exec 12.5/2010/2012.
Agent versions that can be temporarily used with Backup Exec 2014
Name Version Service Pack
Backup Exec for Windows Servers [1] 12.5 All Service Packs
Backup Exec for Windows Servers [1] 2010 All Service Packs
Backup Exec for Windows Servers [1] 2010 R2 All Service Packs
Backup Exec for Windows Servers [1] 2010 R3 All Service Packs
Backup Exec [1] 2012 All Service Packs
1. You can use previous versions of an Agent with Backup Exec during a rolling upgrade. A warning message is displayed in the job log when previous versions of an Agent are used, but backups and restores can continue normally. New features are disabled until you upgrade the Agent to the same version as the Backup Exec
Temporarily Manage Backup Exec Servers with Backup Exec 2014
Name Version Service Pack
Backup Exec for Windows Servers [1] 2010 R3 SP3
Backup Exec for Windows Servers [1] 2010 R3 SP4
Backup Exec [1] 2012 SP2
Backup Exec [1] 2012 SP3
Backup Exec [1] 2012 SP4 + Hotfix 215906
1. You can perform rolling upgrades in the Backup Exec 2014 Central Admin Server Option (CASO) environment, which is included in the Enterprise Server Option. Arolling upgrade lets you upgrade the central administration server from the previous version to the current version first, and then upgrade the managed Backup Execservers from the previous version to the current version over a period of time. A warning message is displayed in the job log when previous versions of a server areused, but backups and restores can continue normally. New features are disabled until you upgrade the version of all of the Backup Exec servers.
Backup Exec Feature Specific CompatibilitySimplified Disaster Recovery (SDR)
Notes:• The Microsoft Assessment and Deployment Kit (ADK) is only supported on Windows Server 2008 SP2 and later.• If the Backup Exec server does not run on Windows Server 2008 SP2 or later, the Standalone Create Disaster Recovery Disk Wizard needs to be installed on adifferent machine running 2008 SP2 or later. This wizard guides you through the download and installation of the ADK. You can then create the recovery disk byconnecting to a remote Backup Exec server or locally with the default options. For further details and instructions <http://www.symantec.com/docs/TECH211137>• The Agent for Linux, Remote Media Agent for Linux, and the Agent for Mac do not support the Simplified Disaster Recovery feature.• If the Backup Exec server on which you want to create the Simplified Disaster Recovery disk image does not have an internet connection, and does not have ADKinstalled, instructions are provided on how to install the ADK. You can then use the Create Simplified Disaster Recovery Disk Wizard to create the recovery disk.
Backup Exec Servers recoverable by SDR
Microsoft
Microsoft - Windows Essential Business Server 2008
Name Version Service Pack CPU Architecture
Windows Essential Business Server 2008 Premium SP2 x86-32, x86-64
Windows Essential Business Server 2008 Standard SP2 x86-32, x86-64
Convert to VirtualNotes:• The Convert to Virtual feature supports both Hyper-V and VMware ESX environments.• Windows Server 2008 SP2 is not supported as a target Hyper-V host for the virtual machine. The target machine must be running Windows Server 2008 R2, or later.• For the Convert to Virtual feature, conversion of Fibre Channel disk devices (not used as Windows volumes), USB devices, Removable disks, and ISCI disks are notsupported. Both Hyper-V and VMware have these limitations.• VMware Converter does not convert GPT disks.• Only basic disks are supported for conversion for both Hyper-V and VMware ESX environments.
Notes:• File system archiving cannot be done from the Windows 2008 SP2 cluster shares. However, it can be done from the Windows 2008 R2 cluster shares.• Exchange Mailbox Archiving Option cannot be installed on the Windows Small Business Server or on the Exchange Server.• Exchange mailbox archiving can be done from Exchange 2003, Exchange 2007, and Exchange 2010 SP3 servers.• Archiving cannot be completed with backups created using Virtual Agents (Microsoft Hyper-V and Virtual Server Agents and Agent for VMware Virtual Infrastructure).
Supported Outlook Versions for Exchange Mailbox Archiving option on the Backup Exec server
Name Version Service Pack CPU Architecture
Microsoft Outlook [1] 2007 SP2 x86-32bit, x86-64bit
1. Requires Outlook 2007 SP2 and Microsoft hotfix kb968858
Note:• For Windows server 2008, Backup Exec automatically installs IIS. You must install IIS and World Wide Web Publishing Service on Windows Server 2003.• Outlook 2010 is not supported with the Exchange Mailbox Archiving Option.
Supported Client Outlook Versions for using Virtual Vault
Name Version Service Pack CPU Architecture
Microsoft Outlook 2007 SP2 x86-32bit, x86-64bit
Microsoft Outlook 2010 x86-32bit, x86-64bit
Remote Admin Console (RAC)Notes:The Remote Administrator Console can be installed on any operating system listed in the "Backup Exec 2014 Server - Operating System Compatibility" section and onany operating systems listed in the following table.
Backup Exec Database Compatibility• This section represents the databases that Backup Exec can use as a repository.• Backup Exec installs Microsoft SQL Server 2008 R2 Express with SP2 components.• If you already have a compatible SQL instance running on your network, you can have Backup Exec use that instance.• Following are compatible versions of SQL:
Backup Exec Management Command Line InterfaceNote:• BEMCLI is installed with Backup Exec and replaces BEMCMD.
Requirements to run BEMCLI:
• Windows PowerShell V2 or V3
• .NET 3.5 or 4.0
• PowerShell's execution policy must set to a value that is less restrictive than Restricted (e.g. AllSigned). For more information, see Get-Help Set-ExecutionPolicy.
Exchange GRT restore to PST fileThis feature allows a user to restore directly to a PST file from a GRT enabled backup of a Exchange database. The PST file must use Outlook friendly mailbox folderstructure of being beneath the 'Top of Information Store' only. Sub-folder below this level are not supported.
Outlook versions required on the target server:
• 32-bit Outlook 2007
• 32-bit Outlook 2010
• Outlook 2013 is not supported.
• 64-bit Outlook clients in any version are not supported.
File naming convention:
• Restore creates PST file name which matches mailbox display name in UI
• File name collisions handled with '(n)' suffix. IE: John Smith [John Smith].pst and John Smith [John Smith](1).pst
File size limits:
• Outlook 2007 has 20 GB limit• The maximum size of the .PST file is 20 GB. If the restore exceeds the size limit, the data is spanned across multiple .PST files which are numbered consecutively.• When you restore multiple mailboxes in the same job, each mailbox that you restore has a PST file.
Microsoft articles on how to change PST file size limits:• <http://support.microsoft.com/kb/832925>• <http://support.microsoft.com/kb/830336>
3rd Party Software Compatibility32-bit and 64-bit Interoperability
Notes:• The 32-bit Backup Exec server table illustrates interoperability between a 32-bit Backup Exec server and various remote systems and applications.• The 64-bit Backup Exec server table illustrates interoperability between a 64-bit Backup Exec server and various remote systems and applications.• If an agent or option is not listed in the tables below, it is supported on both 32-bit and 64-bit (64-bit) platforms.
32-bit Backup Exec server
Agent 32-bit Windows OS 64-bit Windows OS Linux
Active Directory 2003 Supported Supported N/A
Active Directory 2008 Supported Supported N/A
Active Directory 2008 R2 N/A Supported N/A
Active Directory 2012 N/A Supported N/A
Active Directory 2012 R2 N/A Supported N/A
Lotus Domino/Notes [1] Supported Supported N/A
Microsoft Exchange 2007 Not Supported Not Supported N/A
Microsoft Exchange 2010 N/A Not Supported N/A
Microsoft Exchange 2013 N/A Not Supported N/A
Microsoft SharePoint 2007 [2] Supported Supported N/A
Federal Information Processing Standard 140-2 (FIPS) [4] Supported Supported N/A
1. Both 32-bit and 64-bit Backup Exec 2014 servers will back up 64-bit Domino server on a 64-bit OS. Note that a 32-bit Domino server installed on a 64-bit OS is alsosupported.
2. SQL Server/Express 2008 32-bit and 64-bit versions are supported as database backend servers.
3. Both 32-bit and 64-bit SQL Server/Express 2005 is supported on Windows Server 2003 64-bit.
4. FIPS 140-2 mode is supported only for 32-bit Windows platforms. Linux and Mac operating systems are not supported. 128 AES encryption is not supported in FIPSmode.
64-bit Backup Exec server
Agent 32-bit Windows OS 64-bit Windows OS Linux
Active Directory 2003 Supported Supported N/A
Active Directory 2008 Supported Supported N/A
Active Directory 2008 R2 N/A Supported N/A
Active Directory 2012 N/A Supported N/A
Active Directory 2012 R2 N/A Supported N/A
Lotus Domino/Notes [1] Supported Supported N/A
Microsoft Exchange 2007 [2] Not Supported Supported N/A
Microsoft Exchange 2010 N/A Supported N/A
Microsoft Exchange 2013 N/A Supported N/A
Microsoft SharePoint 2007 [3] Supported Supported N/A
1. Both 32-bit and 64-bit Backup Exec 2014 servers will back up 64-bit Domino server on a 64-bit OS. Note that a 32-bit Domino server installed on a 64-bit OS is alsosupported.
2. If Backup Exec resides on a 32-bit Windows 2003 installation, the Exchange tools must be installed locally to back up Exchange 2007. CDO must be installed on theExchange server to run GRT backup and restore jobs.
3. SQL Server/Express 2008 32-bit and 64-bit versions are supported as database backend servers.
4. Both 32-bit and 64-bit SQL Server/Express 2005 are supported on Windows Server 2003 64-bit.
Cluster SupportFor Windows operating systems, Backup Exec supports file share clusters for all supported versions and variations of Windows that feature cluster services (MSCS).
Note:• File System Archiving cannot be done from the Windows 2008 cluster shares. Windows 2008 R2 cluster shares are required.
Name Notes
Microsoft SQL Server 2005 Microsoft Cluster Server
Microsoft SQL Server 2008 Microsoft Cluster Server
Microsoft SQL Server 2008 R2 Microsoft Cluster Server
Microsoft SQL Server 2012 Microsoft Cluster Server
Microsoft Exchange 2007 CCR, LCR, SCC, Microsoft Cluster Server [1]
Oracle Supported with RAC, Microsoft Cluster Server and FailSafe.
1. If Backup Exec resides on a 32-bit Windows 2003 installation, the Exchange tools must be installed locally to back up Exchange 2007. CDO must be installed on theExchange server to run GRT backup and restore jobs.
2. Window Enterprise Edition is still required since a DAG (Database Availability Group) still uses pieces of Windows Failover Clustering.
End-of-Life informationFeatures and requirements no longer supported by Backup Exec
EOL Notice: These operating systems, backward compatibility for restores, and rolling upgrades, third-party software applications, and Symantec products are no longersupported for use with this version of Backup Exec for Windows.• The Version EOL Started identifies the version of Backup Exec that no longer provides the support and includes all subsequent releases.
Backup Exec Server Operating System Compatibility
Name Version Service Pack CPU Architecture Version EOL Started
Microsoft Windows XP All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2012
Windows Server 2003 [1] All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2014
Unified Data Storage Server 2003 All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2014
Windows Small Business Server 2003 All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2014
Windows Small Business Server 2003 R2 All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2014
1. Windows Server 2003 R2 SP2 is supported.
Microsoft - Agent for Windows Servers
Name Version Service Pack CPU Architecture Version EOL Started
Windows XP All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2014
Windows 2000 All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2012
Unified Data Storage Server 2003 All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2014
Windows Small Business Server 2003 All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2014
Windows Small Business Server 2003 R2 All Versions and Editions All Service Packs x86-32, x86-64 Backup Exec 2014