Changing OST login information when using dedup appliance in BackupExec

We’ve had this question come up from our customers more than once after new firmware was installed on the dedup appliance, or some other reason BUE and the OST login isn’t working.

The command is spauser.  From the BUE 2010 admin guide page 1589 Symantec Backup Exec Deduplication Option

Changing the password for the logon account for a deduplication storage folder
When you specify a Backup Exec logon account for a deduplication storage folder, an additional user account is created for the deduplication components with the same user name and password. However, if you change the credentials for the

Sharing a deduplication device between multiple media servers
Backup Exec logon account, the credentials for the additional user account are not changed automatically. You must use the spauser.exe utility to update the password for the additional user account. This account is known as the “User 1” account when you use the spauser.exe utility to view a list of user names that are associated with the deduplication storage folder.

To change the password for the logon account for a deduplication storage folder
1 On the Backup Exec Network menu, click Logon Accounts.
2 Select the Backup Exec logon account that you want to change, and then click Edit.
3 Click Change Password. 4 Type the new password. 5 Click OK. 6 At a command prompt, type the following command:
spauser.exe -c -u
The user name is case-sensitive . If you do not know the user name, type the following command to find the user name that is associated with “User 1”:
spauser.exe -l
You will be prompted for the old password and a new password. Be sure that the new password is the same as the password that you used in step 4.
See “About deduplication storage folders” on page 1579.

Symantec Backup Exec 2010 R2 – Service Pack 1 Released

Symantec has released Service Pack 1 for Backup Exec 2010 R2.

Information and download links:
Backup Exec 2010 R2 revision 4164 Service Pack 1

Release notes for what has been fixed:

There are several fixes related to the Deduplication option and the Virtual Agent (AVVI, VMware) so I’d recommend customers updating asap.

Backup Exec 2010 Customers – Apply Latest Patches!

Several very important patches have been released the last couple of weeks for Backup Exec 2010 (including R2). A lot of these fixes have to do with the deduplication component, Granular Restore Technology (GRT) as well as the Agent for VMware.

You can apply the latest patches by running the Symantec LiveUpdate utility on your Backup Exec Server.

You can also refer to the below TechNotes for a listing of what has been fixed/updated in the last few patches:



Symantec Backup Exec 2010 R2 – Latest Info from 2010 Tech Engage Seminar

I was out in Las Vegas last week at the Symantec Worldwide Technical Symposium (WTS) and Partner Tech Engage (PTE).

I attended a Backup Exec 2010 R2 session which they mentioned the following key points that will be beneficial to our customers:

1) When using Backup Exec Deduplication, a rule of 1GB of RAM per 1TB of storage for the deduplication pool is being changed to a new “formula” of 1.5GB of RAM per 1TB of storage for the deduplication pool. They are changing this recommendation due to issues that Symantec Support has seen. We are recommending our customers to increase the RAM on their Backup Exec Media Servers if they fall outside of this recommendation.

2) The instructors of this session acknowledged there are quite a few “hiccups” with the Deduplication option when using Granular Restore Technology (GRT) based backups, even more so when using GRT and VMware vStorage based backups. They said several hotfixes will be released (more than likely in a “pack”) this week (the week of 11/1/10) that will address a lot of these issues. I’ll try to update this blog when those patches are released.

3) A “stream handler” for VMware vStorage backups will be released for Backup Exec when Backup Exec R3 is released, due out the beginning of next year. The stream handler is a feature that can more intelligently look inside the backup stream which will result in better performance and better deduplication rates for those types of backups. Symantec NetBackup already has a VMware aware stream handler built-in, so I was surprised that Backup Exec didn’t.


Backup Exec 2010 R2 – Remote Agent Install Error Code 1603

While onsite trying to remotely push a Backup Exec 2010 R2 remote agent, we were getting a lot of the “error code 1603” messages, which stated:
“Error connecting to the remote server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603.”

It seems like this is the likely problem, mentioned in the below Symantec technote:

Our workaround was to just install the client manually on each server that wouldn’t connect, instead of going through all the steps mentioned in the above technote.

Release: Backup Exec 2010 R2

Backup Exec 2010 R2 is the second release of Backup Exec 2010 and is generally available to all users starting today, August 2nd, 2010.

This release features improvements in usability, licensing and renewal management, deduplication, virtualization, and extends platform and application support. Here are some of the most important features that the release introduces…

  • Enhanced Installation and backup wizards reduce the time and complexity of setting up your backups
  • Backup recommendation tool identifies potential gaps in your backup strategy and provides recommendations on the agent(s) required to ensure complete data protection.
  • Integrated RSS and Renewal Assistant help keep you informed and current.
  • NEW! support for SharePoint 2010, Exchange 2010 SP1, Microsoft SQL 2008 R2, Enterprise Vault 9, Mac OSX 10.6, NDMP NetApp ONTAP 8.0, EMC DART 6.0, and OST support for Data Domain DDOS 4.8 with Boost Technology.

And time for some good news..customers who are current with maintenance or support contracts for previous versions of their licensed Backup Exec software can upgrade to the appropriate Backup Exec 2010 R2 licenses at no additional charge. Download Here!

Existing customers who do not have current maintenance or support may purchase version upgrades at up to 35 percent off MSRP. Save Now!

For more information, please visit the R2 FAQ page.

Free 60 day trailware for Backup Exec 2010 R2 can be downloaded from

Some more information on the R2 release is available here

Version Information:
Original 2010 = 13.0.2896
2010 R2 = 13.0.4164

All of the previous and upcoming (i.e. existing hotfixes and SP1) are rolled up in BE 2010 R2.  For clarification, here are a list of the fixes as well as a link to the post from the support team:

The following issues reported by our customers have been resolved in Backup Exec 2010 R2:

Issue ID Description
1037546 Email notification configured in a policy will not include attached job log
1081603 Restore of a Mailbox Completes Successful but Data is not Visible or is not restored
1117800 After recovery using Intelligent Disaster Recovery feature, CD-ROM is not found in my computer when Z drive is used for the CD-ROM.
1221471 Remote Agent for Macintosh Systems installation changes owner and group permissions for /opt, /private/etc and /private/var
1376065 Unable to restore ADAM if the database and logs are installed into a non-default path
1426956 Alert added to warn of Backup Exec Database being over 4GB
1452631 No RMAN Output in Oracle Job Log.
1590025 Job Rate is displayed incorrectly in the Job History when international numeric formats are in use.
1596948 Jobs within a Synthetic Policy with rules will run multiple times a day even though not scheduled
1597670 When the ‘Move Media to Vault’ report is run on a CASO CAS, if the Media Server filter is used, the report will be blank.
1654276 Incorrect software compression ratio is reported in the job log when using both software compression and software encryption
1818393 GRT restores of Hyper-V backups are 6 to 7 times slower than redirecting the VHD files to same GRT staging location.
1713413 Unable to browse file system on Solaris 10 cluster.
1724588 GRT Restore of files/folders to an alternate VM path fails with Unable to Attach error for tape backup sets.
1766628 Authentication error when selecting DB2 resources
1825660 Synthetic full backup fails with “Directory or file was not found” when the incremental backup spans to a another tape in the middle of writing the on tape catalog
1852904 After Win2008 DR and reboot: “Windows cannot verify the digital signature” – fails to boot up
1856745 Automatic cancellation does not work for inventory jobs.
1862029 Redirected restore of a SQL 2005 database to a 2008 server does not use the default data path.
1864806 Catalog search not working when partial catalog files exist in the catalog folder.
1875898 Restore jobs of Sharepoint V3 ServicesDB always fails in Japanese Edition
1890615 Warning needed when invalid entries are created for some agents and options
1917097 Unable to restore Incremental backup of DB2 instance
2006341 Pause/Unpause does not work when using the BEMCMD switch -o79
1944918 GRT sets on cartridges as part of removable B2D get deleted from the Backup Exec DataBase when the cartridges are detached, reattached, and inventoried
1957646 Job Engine crash in ImageBasedFHPlugin
1956235 Remote Server backups fail with “Access Denied” errors if global excludes have been added more than twice after the backup job is created
1950529 When a Hyper-V virtual machine redirected restore job is tried, the job fails with error “An invalid parameter was specified”.
1951105 All Hyper-V VM backups fail if master VM has pass through disk configured on it.
1952063 Issues with Dedupe related to Windows dynamic cache issue
1956541 Storage Provisioning Option LUNs show up in the device tree but cannot be selected as a target for a new backup job
1957651 Bengine.exe process is crashing in msvcr80!memcpy+0x158
1957836 Serialization of a B2D can result in a crash of BEServer.exe
2002377 Unable to register in-line patch with Live Update
1958705 Post-commands do not run on each server backed up after job verification completes
1959591 Restore of VMware image fails with error “The selected transport mode is unsupported by the current setup” when using HOTADD transport mode
1961140 seg fault during RALUS backup if “Collect additional information for synthetic backup and for true image restore” is selected
1970061 Backup of VMWare VM with 2 virtual disks of the same name only backs up 1 of the virtual disks
1962583 After installing Outlook 2010 on the Exchange 2010 CAS GRT restores fail with MAPI Errors
1971148 Backup of VM’s on ESX 3.5 complete with the exception V-79-57344-38725 – One or more virtual disks contain volumes that do not support Granular Recovery Technology (GRT). Granular restores cannot be performed for these volumes.
1966862 When using BEMCMD, Restore job created with file redirection only restores the directory structure
1977153 VMWare backup fails with error “You have requested access to an area of the virtual disk that is out of bounds”
1979478 Some VMWare guest OS files might not be restored even if restore job had completed without error
1982632 GRT restore for Exchange 2010 mailbox completes successfully but no messages restored and EWS log reports error “The specified object was not found in the store”
1987655 VMWare agent is unable to perform file level GRT from two different VMDK’s at the same time.
1987488 The “Next” button doesn’t work on the “Add Multiple Servers with the Same Settings” dialog on German installations
1998621 VxValidator.exe crashes on VxValidatorOps.dll module in Environment Check stage during BE 2010 upgrade when the media server has VSP.SYS installed.
2008520 GRT backup of Windows 2008 VM with dynamic MBR disks complete with exception “One or more virtual disks contain volumes that do not support GRT”
1998808 BEUtility’s ‘New Backup Exec Database Location’ does not update the log registry path when moving BEDB from a remote SQL 2000 to 2005
1998144 Unable to redirect a SQL 2008 database restore with SQL FILESTREAM enabled.
2002282 SharePoint GRT restore failed with status 71 (File not found during granular extraction).
2003116 The “Set Job Log and Catalog Locations” option in BEUtility does not update the job log location as specified.
2002328 Installation of BE2010 with a HF streamed into it does not lay down all of the files.
2004354 Backup Exec preinstaller in Windows 7 displays “Vista meets the minimum requirements for Backup Exec”
2008439 GRT restore fails with error “0xe00002fd – Cannot restore properties for one or more messages or folders” and the EWS log reports the error “The extended property attribute combination is invalid”
2013617 Remote Agent ‘Push’ install will not use the %ProgramFiles% value in the installation path, when installing to non-English Operating Systems
2013895 Enterprise Vault Agent based backups fail with error “A selection on device was skipped because of previous errors with the job.” for an Enterprise Vault site upgraded to EV 8.0 and with the FingerPrint Database not configured.
2016677 Some VMWare virtual machines are not listed in resource view of the restore selections
2018380 VMWare GRT restore selections show ghost drives and in turn cause GRT operation to not work for valid volumes and applications that support GRT.
2019514 The restricted encryption key cannot be used after renaming the computer.
2025682 List attachments do not show in restore selections, when Sharepoint Site is hosted on remote SQL2000
2027368 Unable to create deduplication folder. Access Denied because the System Logon Account and purediskdbuser are not members of the “users” group
2053808 Exchange GRT restore hangs after a certain point and the beremote debug log on Exchange Client Access Server reports “MapiItem::SaveProps, SaveChanges() returned 80131600”
2030297 The setting ¿Start the Remote Agent Utility every time you log on” in Remote Agent utility is not retained on a Windows 2008 R2 Server.
2032624 Intermittent Unable to Attach error on backing up MOSS setup on Windows 2008 with WebServers in NLB and SQL in cluster.
2034355 Error when running a PDF report in BE 2010 on 64 bit Windows 2008
2046321 Job hangs at MEDIA REQUEST when spanning tapes on a RL connected to EMC Cellera
2038958 NDMP Duplicate jobs crash Backup Exec job engine (bengine.exe faulting module libcatalog.dll)
2036948 NetWare backups to Dedupe folder or OST devices hang when spanning the media.
2042206 Beutility crashes while changing service account details
2043199 VMWare Application level GRT based restore of an Exchange DBindividual email fails when the DBlogsinstallation files reside other than the default location on C drive.
2042963 Post GRT restore Distribution List (DL) in the email loses its properties and comes up as an email address.
2043203 VMWare Application level GRT based restore for a SQL DB fails when the mdfldfinstallation files reside other than the default location on C drive.
2042991 Hyper-V GRT backups to Tape of a CSV clustered VM that has pre-existing snapshots created completes with exception “Failed to mount one or more disk images during backup”
2046664 During Automated SQL master restores, beremote crashes when a large number of DBs exist on a SQL instance
2048325 Tracer.exe, Tracercli.exe, and discover.exe don’t work on Windows 2008 without disabling UAC (Use Account Control)
2051339 Backup of Oracle 11g on Linux server hangs indefinitely.
2051849 Remote agent on Exchange 2010 DAG passive node crashes on msvcr80!woutput_l+6b3
2051942 Install fails with the error “Installation failed with error 3. GetLastError = :5”
2053973 Application error occurs in beremote.exe while VMware virtual machine is restored.
2055941 RAWS 2010 upgrade installation fails on AgentSeqDlgs!Symantec.BackupExec.AgentSeqDlgs.AgentInstaller.GetVMwareGuest()+0x245. Final error is ERROR: Installation failed with error -1073741819
2055964 Running a backup job to a deduplication folder hangs the job on a queued status when a library is multi-path attached.
2059437 File and directory structure is not properly restored when restoring from a backup of EFS encrypted data.
2059251 Renamed files cannot be restored from synthetic backups when using the Microsoft Change Journal
2075644 Backup of Windows 2008 64 bit VM hosted on ESX 3.5 U5 fails with error “An attempt to take a snapshot of a virtual machine failed because it was unable to quiesce an application”


Symantec Backup Exec 2010 and Netbackup 7 Super Post

Here’s a great post which discusses pricing with Backup Exec 2010 and Netbackup 7.

Note, Backup Exec 2010 Trialware is out now. Netbackup 7 First Availability (FA) program is available now, which is the same as the General Availability (GA) code.
Netbackup 7 is now on the Symantec site, with the announcement that General Availability (GA) is: February 1st!

Backup Exec 2010 is also available February 1st! and it’s on the Symantec site as well:

Update – Ready to start upgrading or testing Backup Exec 2010? Symantec has released trialware as of yesterday so you can start before the actual release on 2/1/10.
Symantec’s blog post copied below for your reference, as it has some additional links on it:

Good news! Backup Exec 2010 has launched today with the Trailware available for download from February 1, 2010. The new product encompasses great new features like Deduplication and Unified Archiving. To read the complete list of new features key benefits and to download the trailware, please visit  the Backup Exec website.

Have questions on how to upgrade?  Please refer to this document that walks you through the upgrade process.

Getting back to Connect, we have created some great information in regards to the new product launch. Here is a video that explains the product’s deduplication feature. Check this Group page for finding all the BE 2010 and BESR 2010 information in one place.  Don’t forget to add it to your favourites. 

In the process of your upgrade,  with any questions, comments, suggestions and great information you are sharing with the community regarding the new product, we encourage you to please make sure to tag the content with the appropriate Version (2010), the Topics (Installation, Upgrade etc) and the public group “BE 2010 and BESR 2010 Launch”. It helps us track the common issues and escalate it to support as needed. (end of symantec blog article)

Here are some great screenshots of some slides discussing some of the new features and enhancements to Backup Exec 2010.

VMware Consolidated Backup and User Access Control

Working with a customer recently I got to spend some quality time troubleshooting VMware Consolidated Backup framework.  Generally VCB is a very straight forward install and it pretty much “just works” – which made my recent experience very atypical (in my experience anyway).

Here’s the setup – we have a group of ESX servers, and a Windows Server 2008 Standard 64-bit system, all attached to the same Fibrechannel SAN, with everything zoned properly.  VCB is installed on the 2K8 system.  The 2K8 OS sees all of of the VMFS luns which are presented to it.  We are using Win2K8’s native MPIO stack.

Running VCB Mounter in SAN mode returns an error that there is no path to the device where the VM is stored.  Running it in NBD mode works great…except that it passes all of the traffic over the network which is not desirable.

Again, diskpart, and the disk Management MMC see all of the LUNs with no issues.

VCB’s vcbSanDbg.exe utility however see no storage.  None at all.

We tried various options – newer and older versions of the VCB framework (btw, only the latest 1.5 U1 version of VCB is supported on Win2K8).  We tried various ways of presenting the storage.  We even tried presenting up some iSCSI storage thinking maybe it was an issue with the systems’ HBA’s.

Ok, if you’ve read the subject of this post then you already know the answer.  In case you didn’t here it is – the system has User Access Control (UAC) enabled.   The user we’re running the framework as is a local administrator on the proxy, but that’s not enough to allow it to properly enumerate the disk devices.   In order for the VCB framework to work you either have to run it in a command window with the “run as administrator” option,  or turn off UAC on the server.  The former can be a little tricky to accomplish if you’re wanting to run the framework from inside a backup application, while the latter seems to be the most common approach.

That’s it.  Turn off UAC and reboot the computer.  Now VCB works great.