Symantec Backup Exec 2012SP2 Administrator's GuideAddendum

The software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Documentation version: 2012 SP2

Last updated: May 2013

Legal NoticeCopyright © 2013 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, the Checkmark Logo and are trademarks or registeredtrademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Othernames may be trademarks of their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The LicenseAgreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see theThird Party LegalNoticeAppendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

Administrator's GuideAddendum

This document includes the following topics:

■ About the Administrator's Guide Addendum

■ Revisions to the Backup Exec 2012 Administrator's Guide

■ Additions to the Backup Exec 2012 Administrator's Guide

About the Administrator's Guide AddendumThe addendumcontains additions and changes to the Symantec BackupExec 2012Administrator's Guide.

See “Revisions to the Backup Exec 2012 Administrator's Guide” on page 5.

See “Additions to the Backup Exec 2012 Administrator's Guide” on page 15.

Revisions to the Backup Exec 2012 Administrator'sGuide

The following table lists the revised topics:

Table 1-1 Revisions to the Backup Exec 2012 Administrator's Guide

RevisionsChapterTopic

The following item should beadded to the table of specialconsiderations:

32-bit and 64-bit computers

If you try to push-install BackupExec from a 32-bit computer to a64-bit computer, you may beprompted to insert the 64-bitinstallation media.

InstallationSpecial considerations forinstalling Backup Exec to remotecomputers

Administrator's Guide AddendumRevisions to the Backup Exec 2012 Administrator's Guide

6

Table 1-1 Revisions to the Backup Exec 2012 Administrator's Guide (continued)

RevisionsChapterTopic

Windows Server 2012 has beenadded to the following item:

Windows Vista/Server2008/7/Server 2012

To push-install Backup Execoptions to a computer that runsWindows Vista/Server2008/7/Server 2012, you mustenable certain items on thedestination computer's WindowsFirewall Exceptions list.

You must enable the followingitems:

■ File and Printer Sharing

■ Windows ManagementInstrumentation (WMI)

For more information refer toyour Microsoft Windowsdocumentation.

To push-install Backup Execoptions to Windows Vista/Server2008/7/Server 2012 computersthat do not belong to a domain, doone of the following:

■ Make sure that theAdministrator account on thecomputer from which youpush-install the agent oroption is also defined on thedestination computer

■ Disable User Access Controltemporarily on the destinationcomputer during theinstallation process

Formore information, refer to theMicrosoft knowledge base.

InstallationAbout push-installing the AgentforWindows to remote computers

7Administrator's Guide AddendumRevisions to the Backup Exec 2012 Administrator's Guide

Table 1-1 Revisions to the Backup Exec 2012 Administrator's Guide (continued)

RevisionsChapterTopic

The description for the itemBackup method for files shouldinclude the following note for theUsing catalogs method:

TheAdvancedDisk-based BackupOption off-host backup featuredoes not support the Usingcatalogs method.

BackupsFiles and Folders options

Additional steps have beenincluded in this procedure forenvironments in which the Agentfor VMware or the Agent forMicrosoft Hyper-V is installed.

See “Changing the location of adisk storage device ” on page 13.

Disk-based storageChanging the location of a diskstorage device

The following information hasbeen included in the descriptionsfor the storage trending statusesof History of used space is stillbeing gathered and Not enoughstatistical information isavailable:

After you create disk storage,Backup Exec may takeapproximately one month togather enough information toprovide a storage estimate.

Disk-based storageAbout storage trending for diskstorage and virtual disks

Administrator's Guide AddendumRevisions to the Backup Exec 2012 Administrator's Guide

8

Table 1-1 Revisions to the Backup Exec 2012 Administrator's Guide (continued)

RevisionsChapterTopic

The example port number thatwas provided in the followingexample entry is incorrect.

ndmp 100000/tcp #Network DataManagement Protocol

Port 100000 is not a valid NDMPport. The correct port number forNDMP is 10000. If that portnumber is in use by anotherprocess, youcanchange theNDMPport to something else, such as9999 for example.

Configuration andsettings

About using Backup Exec withfirewalls

This topic should include thefollowing note:

The AdvancedDisk-based BackupOption off-host backup featuredoes not support the Usingcatalogs method.

Backup strategiesAbout configuringBackupExec todetermine if a file has been backedup

The following sentence isincorrect:

If you want to use Backup Exec'sGranular Recovery Technology(GRT), you must purchase andinstall the Agent for Applicationsand Databases on your virtualmachines.

The following sentence is correctand should replace the existingsentence:

If you want to use Backup Exec'sGranular Recovery Technology(GRT), the Backup Exec Agent forApplications and Databases mustbe installed on the Backup Execserver and theAgent forWindowsmust be installed on the virtualmachines.

BackupExecAgentfor VMware

Requirements for backing upMicrosoft application data onvirtual machines

9Administrator's Guide AddendumRevisions to the Backup Exec 2012 Administrator's Guide

Table 1-1 Revisions to the Backup Exec 2012 Administrator's Guide (continued)

RevisionsChapterTopic

The following items should beremoved fromtheUser credentialscolumn of Table I-1, for thecomponent Enterprise Vaultdatabases and components (vaultstore, indexes, partitions, vaultstore database, Directory,Monitoring, Fingerprint, FSAReporting, and Audit databases):

■ The user account must beincluded in the BackupOperators group on allcomputers where EnterpriseVault databases reside. WithEnterpiseVault partitions, theuser accountmust be includedin the Administrators group.

■ Note: To back up a computerthat has a partition, or apartition and a database, youmust be a member of thecomputer's Administrator'sgroup. To back up a computerthat has only an EnterpriseVault database on it, you needonly to be a member of theBackup Operators group.

Symantec BackupExec Agent forEnterprise Vault

About the Agent for EnterpriseVault

The following item should beincluded in the list of features thatarenot supportedby theAdvancedDisk-based Option off-hostbackup:

The Using catalog file backupmethod

Symantec BackupExec AdvancedDisk-basedBackupOption

About off-host backup

Administrator's Guide AddendumRevisions to the Backup Exec 2012 Administrator's Guide

10

Table 1-1 Revisions to the Backup Exec 2012 Administrator's Guide (continued)

RevisionsChapterTopic

The steps in this topic areincorrect. For the correct steps,see the topic "Push-installing amanagedBackupExec server fromthe central administration server"in the Central Admin ServerOption chapter.

Symantec BackupExec CentralAdmin ServerOption

Changing a Backup Exec server toa managed Backup Exec server

In Table 16-6, the definition forthe option Full path of VMwareTools ISO imagecontains thefollowing incorrect sentence:

If you use a network disk,Symantec recommends using amapped drive on the local BackupExec server.

In Table 16-7, the definition forthe option Full path of Hyper-VIntegration Components ISOimage contains the followingincorrect sentences:

Note: You cannot use a UNC pathfor remote shares. However, youcanmap a drive to a remote share.

For both VMware and Hyper-V,the ISO image cannot be on amapped drive.

VirtualizationVirtualmachineconversionoption

11Administrator's Guide AddendumRevisions to the Backup Exec 2012 Administrator's Guide

Table 1-1 Revisions to the Backup Exec 2012 Administrator's Guide (continued)

RevisionsChapterTopic

In the table namedDeduplicationmethods forBackupExecagents,in the column labeled Client-sidededuplication (file system/VSS),the entry for the Agent forEnterprise Vault should be No.

The client-side deduplicationmethod for file system backupsdoes not support the Agent forEnterprise Vault.

Additionally, the column labeledClient-side deduplication (filesystem/VSS) should instead belabeledClient-sidededuplication(file system backups orVSS-snapshot enabled backups,whichever is supported).

Backup ExecDeduplicationOption

Deduplicationmethods forBackupExec Agents

In the table named ExchangeServer requirements, in thecolumn labeledForoperationsonall Exchange Servers, the entryshould include that the useraccount must be a member of thefollowing groups:

■ The Exchange OrganizationManagement group(2010/2013)

■ The Exchange OrganizationAdministrators group (2007)

Symantec BackupExec Agent forMicrosoftExchange Server

Requirements for using theExchange Agent

Administrator's Guide AddendumRevisions to the Backup Exec 2012 Administrator's Guide

12

Table 1-1 Revisions to the Backup Exec 2012 Administrator's Guide (continued)

RevisionsChapterTopic

The steps in this topic areincorrect. The following steps arecorrect:

1. On the central administrationserver, clickStart>MicrosoftSQLServer (version number) >ConfigurationTools>SQLServerConfiguration Manager.

2. Expand the SQL ServerNetworkConfiguration, and thenclickProtocols for the SQLServerinstance that is in use by thecentral administration server.

3. Double-click TCP/IP, and thenclick the IP Addresses tab.

4. Write down the TCP dynamicport number.

5. Create an alias for themanagedBackup Exec server to allow it toconnect to the SQL port on thecentral administration server.

Symantec BackupExec CentralAdmin ServerOption

Opening a SQL port in CASO for aSQL 2005 or 2008 instance

Changing the location of a disk storage deviceYou can change the location of an existing disk storage device.

Note:Whenyou copy files from the original disk storage device to thenew location,do not copy .cfg files.

To change the location of a disk storage device

1 Ensure that no jobs are running or are scheduled to run until you havecompleted the process of changing the location of a disk storage device.

2 Do one of the following:

13Administrator's Guide AddendumRevisions to the Backup Exec 2012 Administrator's Guide

Use the Configure Storage wizard tocreate a new disk storage device with adifferent name and drive letter than theoriginal disk storage device.

If the Agent for VMware or the Agent forMicrosoft Hyper-V are not installed

Youmust use the samedrive letter for thenew disk storage device location that wasused for the existing disk storage device.

Do the following in the order listed:

■ In Windows, assign a new drive letterto the disk volume of the existing diskstorage device.

■ In Windows, assign the drive letterthat the existing disk storage deviceoriginally had to the new disk storagevolume.

■ Use the Configure Storage wizard tocreate a new disk storage device withthe same drive letter that the existingdisk storage device originally had.

If the Agent for VMware or the Agent forMicrosoft Hyper-V are installed

3 In Windows Explorer, copy and paste all of the files except the .cfg files fromthe \BEData folder on the original disk storage device to the \BEData folderon the new location.

4 In Windows Explorer, delete all of the files from the original disk storagedevice.

5 Delete the original disk storage device.

6 Rename thenewdisk storage devicewith thenameof the original disk storagedevice.

7 On the Backup ExecAdministration Console, right-click the newdisk storagedevice, and then click Inventory and Catalog.

See the following topics in the Symantec Backup Exec 2012 Administrator'sGuide:

■ Deleting a storage device

■ Inventorying and cataloging a storage device

Administrator's Guide AddendumRevisions to the Backup Exec 2012 Administrator's Guide

14

Additions to the Backup Exec 2012 Administrator'sGuide

The following topics are new for Backup Exec 2012 SP2:

■ Support for Windows Server 2012

■ About including or excluding files for backup definitions

■ Special considerations for converting aphysical computer to aWindowsServer2012 Hyper-V host

■ Agent for Hyper-V notes

Support for Windows Server 2012BackupExec 2012 SP2 supportsWindows Server 2012with some limitations. Youcannot install a BackupExec server onaWindowsServer 2012 computer.However,you can use the Agent for Windows to back up and restore Windows Server 2012computers with their operating systems and legacy features. You cannot installthe Agent for Windows on ReFS volumes or any volumes that have been enabledfor deduplication in Windows.

Backup Exec supports the backup of non-deduplicated data on any volumes thathave Windows deduplication enabled. If you try to back up data from a volumethat has Windows deduplication enabled, Backup Exec backs it up in its original,non-deduplicated format. Ensure that you have enough storage space for thenon-deduplicated data before you run a backup.

BackupExec supports thenon-deduplicated restore of volumes that haveWindowsdeduplication enabled. When you restore files from a volume that has Windowsdeduplication enabled, Backup Exec places the files on the disk asnon-deduplicated. Ensure that you have enough disk space to restore thenon-deduplicated data before you run a restore job.

Simplified Disaster Recovery (SDR) is not supported for Windows Server 2012. Ifyou run an SDR backup job to back up a Windows Server 2012 computer that wasupgraded fromanearlier versionofWindows, you cannotuseSDRremote recoveryto restore either the earlier versionofWindowsorWindowsServer 2012.However,if you have the disaster recovery information file and the backup sets from whenyou backed up the earlier version of Windows, you can perform an SDR localrecovery. If you do not have the disaster recovery information file, you can useBackup Exec to perform a manual disaster recovery. Refer to the "Disasterpreparation and recovery" chapter in the Backup Exec Administrator's Guide formore information about performing a manual disaster recovery.

15Administrator's Guide AddendumAdditions to the Backup Exec 2012 Administrator's Guide

For more information about specific limitations, refer to the Backup Exec 2012SP2 Readme document.

About including or excluding files for backup definitionsIf you want to modify a backup definition's backup selections, you can open thebackup definition and choose Edit in the Selections box. Then, on the BackupSelections dialog box, you can select the Selection Details tab.

The Selection Details tab lets you quickly include or exclude files for backups byspecifying file attributes. Exclusions apply to all of the jobs in a backupdefinition.

You can do any of the following:

■ Include or exclude subdirectories. For example, you can choose to back up aparent folder without backing up any folders that reside inside it.

■ Include only modified files. For example, you can choose to back up only thefiles that have changed since the last backup job.

■ Include only read-only files.

■ Include or exclude files by file name attributes. For example, you can selectonly files with .txt extensions, or exclude files with .exe extensions from abackup. If you exclude files by an attribute that does not exist, all files of thattype are excluded. For example, excludes based on SQL database dates resultin global SQL excludes since SQL databases do not have date attributes.

■ Select only any files that fall within a specified date range. For example, youcan select any files that were created or modified during the month ofDecember.

■ Specify the files that have not been accessed in a specified number of days.For example, you can select the files that have not been accessed in 30 daysfrom your "My Documents" folder. Then, run a full backup job for which youselect the method to back up and delete the files.The Backup Exec Archive Option offers more features for data archiving.

You can configure specific exclusions for incremental and differential backupjobswithin abackupdefinitionusing theExclusionsoptionon theBackupOptionsdialog box.

You can also configure global exclusions. Global exclusions apply to all the backupjobs that you create.

Administrator's Guide AddendumAdditions to the Backup Exec 2012 Administrator's Guide

16

Special considerations for converting a physical computer to a WindowsServer 2012 Hyper-V host

Before you create a job to convert a physical computer to a Windows Server 2012Hyper-V host, review the following information:

■ Disk data is stored in VHDX files for conversion of a physical computer to aWindows Server 2012 Hyper-V host.

■ The conversion of simple GPT disks is supported.

■ Storage Spaces are not supported.

■ If the physical computer runs Windows Server 2012 with an ReFS volume,conversion to a Windows Server 2012 Hyper-V host is supported. Conversionto any previous versions of aWindowsHyper-V host is not supported, so thosejobs fail.

■ If the physical computer runsWindowsServer 2012with one ormoreWindowsdeduplication volumes, conversion to a Hyper-V host is possible, but it mayfail. The converted disk data is not deduplicated. In other words, anunoptimized data transfer is performed. For this reason, the conversion mayfail if the amount of unoptimized data is greater than the capacity of thedestination volume.

Agent for Hyper-V notesThis section contains specific information about how theAgent forHyper-Vworkswith Windows Server 2012 and general notes for using the Agent for Hyper-Vwith any supported version of Windows in this release of Backup Exec.

See the section called “Notes about how the Agent for Hyper-V works withWindows Server 2012” on page 17.

See the section called “General notes about the Agent for Hyper-V” on page 20.

Notes about how the Agent for Hyper-V works with WindowsServer 2012TheBackupExec2012SP2Agent forHyper-V lets youbackupand restoreHyper-Vvirtualmachines that arehosted onMicrosoftWindowsServer 2012. This versionofBackupExec supports theWindowsServer 2012VHDX file format andMicrosoftincremental backups.

Microsoft's new VHDX file format supports virtual disks that are up to 64 TB insize. BackupExec supports backupsand restores forVHDX-basedvirtualmachines.Backup Exec processes the VHDX files similarly to how it processes VHD files.

17Administrator's Guide AddendumAdditions to the Backup Exec 2012 Administrator's Guide

Virtual machine file/folder-level Granular Recovery Technology (GRT) andapplication-level GRT are handled in the following ways for VHDX files:

■ If a virtual machine has only VHD files, then both file/folder-level GRT andapplication-level GRT are fully supported.

■ If a virtual machine has only VHDX files, file/folder-level GRT andapplication-level GRT are supported if the VHDX has a capacity of less than2 TB. If the VHDX files have a capacity larger than 2 TB, then file/folder-levelGRT and application-level GRT are not supported. The job will complete witha status of success with exceptions, but no GRT restore capability will beavailable. A full restore of the virtual machine will be available.

■ If a virtualmachine has amixture of VHD andVHDX files, but all of the VHDXfiles have a capacity of less than 2 TB, then both file/folder-level GRT andapplication-level GRT are fully supported.

■ If a virtual machine has a mixture of VHD and VHDX files, but one or moreVHDX files have a capacity of greater than 2 TB, then file/folder-level GRTand application-level GRT are not supported. The job will complete with astatus of success with exceptions, but no GRT restore capability will beavailable. A full restore of the virtual machine will be available.

Application-level GRT is supported for Microsoft Active Directory 2012 and SQL2012. Limited application-GRT is supported forMicrosoft SharePoint Server 2013andMicrosoft Exchange Server 2013. For SharePoint 2013, individual documentscannot be restored, but the entire content database can be restored. For Exchange2013, individual mailbox items cannot be restored, but the entire database andlogs can be restored.

Microsoft's incremental backups for Hyper-V differ from Backup Exec'sincremental backups. No options are available within Backup Exec to configurethe Microsoft incremental backup method for a virtual machine. Instead, youmust use PowerShell on theHyper-V host to configure theMicrosoft incrementalbackup. TheMicrosoft incremental backup setting is applied as a property of eachindividual virtual machine, so some virtual machines may use the Microsoftincremental backupmethod while other virtual machines do not use it. Youmustconfigure a virtual machine to use the Microsoft incremental backup methodbefore you run a backup job. For virtual machines that do not have the Microsoftincremental backup method enabled, Backup Exec incremental backups will beperformed. For virtual machines that do have the Microsoft incremental backupmethod enabled, the Microsoft incremental backup is performed instead of theBackup Exec incremental backup. The Backup Exec job log lists the incrementalbackup method that was used. A Backup Exec differential backup of virtualmachines that have Microsoft incremental backup enabled is not supported, so ajob with that configuration will fail

Administrator's Guide AddendumAdditions to the Backup Exec 2012 Administrator's Guide

18

Note: To use Microsoft's incremental backups, the Hyper-V host must haveWindows Server 2012 installed and the virtual machine must use the WindowsServer 2012 version of the Hyper-V Integration Services.

Note: A one-time backup job may cause virtual machines that have Microsoftincremental backups enabled to perform a full backup during the next scheduledfull/incremental job.

The following limitations apply to using the Agent for Hyper-V with WindowsServer 2012:

■ Virtual machines that are configured with Fibre Channel HBAs are skippedduring backup jobs. The job log lists a message to indicate that the virtualmachine was skipped.

■ The deduplication stream handler for VHDX files is not supported.

■ Remote VSS is not supported.

■ A VSS Copy backup of a Windows 2012 Hyper-V virtual machine is notsupported.

■ File/folder-level GRT is not supported for volumes that use theWindows 2012Resilient File System (ReFS). In addition, application-level GRT cannot beperformed for the virtual machine on which the ReFS volume is located.

Note: File/folder-level GRT is supported for volumes that are configured withNTFS.

■ File/folder-level GRT is not supported for volumes that have Windows 2012deduplication enabled. In addition, application-level GRT cannot be performedfor the virtual machine on which Windows 2012 deduplication is enabled.

Note: File/folder-level GRT is supported for volumes that are configured withNTFS.

■ A virtual machine that was backed up from a Hyper-V 2012 host cannot berestored to a virtual machine with an earlier version of Hyper-V, such as 2008or 2008 R2.

■ Virtualmachines that have storage spaces arenot supported becauseMicrosoftHyper-V VSS is unable to take snapshots of virtual machines with storagespaces.

19Administrator's Guide AddendumAdditions to the Backup Exec 2012 Administrator's Guide

■ Hyper-VReplicationvirtualmachine backupsmay result in redundant backupsof the primary virtual machine and the replicated virtual machine.

■ GRT is not supported for virtual machines that have VHDX image files with alogical sector size of 4096 bytes. This applies to both application-level GRTand file/folder-level GRT. A full restore of a virtual machine with thatconfiguration can be performed.

■ Virtual machines that are configured with remote storage are skipped duringbackup jobs. The job log contains a message about the skipped jobs.

■ Virtual machines that run non-Windows operating systems and have VHDXimage files are not supported.

For details about the new features of Microsoft Windows Server 2012, see theMicrosoft website.

General notes about the Agent for Hyper-VThe following notes detail information about using the Agent for Hyper-V withBackup Exec 2012 and any other supported versions of Microsoft Windows.

■ GRT is not supported for virtual machines that use dynamic disks, such asspanned, mirrored, striped, or RAID 5 disks.

■ You must assign shadow storage to each NTFS volume that exists on a virtualmachine if the virtual machine uses the Windows 2008 operating system.Otherwise, the backup job fails.

■ The restore of a Hyper-V virtual machine that is created within amount pointfails if the mount point does not exist at the time of the restore. To avoid thisissue, configure the virtualmachine to use volumeGUID pathswith nomountpoints. To solve this issue, recreate themount point path or restore the volumethat contains the mount point before you restore the virtual machine.

■ GRT is not supported for backups to tape of anExchange 2003 virtualmachinethat runs on a Hyper-V host that is installed as a server role on a Server Coreinstallation of Windows Server 2008 or later. Backup to a disk storage deviceis supported.

■ Backup Exec does not support virtual machines that have duplicate names.

■ When using the Agent for Hyper-V to back up a virtual machine that runs anysupported version of Microsoft SharePoint, you may experience apre-processing time of more than 30 minutes if application-level GRT forSharePoint is enabled for that virtual machine.

Administrator's Guide AddendumAdditions to the Backup Exec 2012 Administrator's Guide

20