Symantec Backup Exec 2012 User Manual

Posted on by
  1. Symantec Backup Exec 2015 Pricing
  2. Symantec Backup Exec 2012 User Guide
  3. Symantec Backup Exec 2015
  4. Backup Exec 2010 User Guide

View & download of more than 291 Symantec PDF user manuals, service manuals, operating guides. Software user manuals, operating guides & specifications. I This guide is for ETERNUS CS800 S6 3.2 Software. Symantec OST (Open Storage) allows NetBackup and Backup Exec to seamlessly integrate with an ETERNUS CS800 S6 disk backup system. On ce installed an d configured, NetBackup or Backup Exec can. Jul 13, 2012 In the end, to be able to install Backup Exec 2012 I had to manually, piece by piece, remove all traces of the previous version(s) of Backup Exec that were on the server. This was because BE 2012 wouldn’t upgrade the 10d installation, wouldn’t allow a parallel installation and the upgrade path Symantec outlined didn’t work. Symantec Internet Security 2012. 0 mb; 334 pages; Symantec Internet Security For Mac. 0 mb; 20 pages; Symantec Norton 360. 0 mb; 584 pages; Symantec Norton 360 (2013) 0 mb; 44 pages; show all Antivirus software Symantec user manuals. Assistance programme. Symantec Norton Utilities. 0 mb; 36 pages. Symantec BACKUP EXEC 11D. 0.19 mb; 18 pages. See “Additions to the Backup Exec 2012 Administrator's Guide” on page 15. The user account must be included in the Backup Operators group on all computers where Enterprise Vault databases reside. Symantec Backup Exec Central Admin Server Option ChangingaBackupExecserverto. Courses to prepare for this exam include: Symantec Backup Exec 2012: Administration course or Install and Configure + Manage and Administer courses. The product documentation for this exam is: Symantec Backup Exec 2012 Customer Licensing Guide Symantec Backup Exec 2012 Readme First Release Notes.

Honest backup solutions are the best ones. Not allowing the user to completely uninstall anything he doesn’t longer need is definitely is a bad taste. But at the end of the day maintaining the computer is still a user business. So, how can the life become easier, at least, a little bit?

Are you looking to find information related to Backup Exec 2012? If so, here is a list for your reference. Bookmark now! Backup Exec 2012 Training: Backup Exec 2012 Administration course (5-day instructor led or virtual) Backup Exec Tech Center (a library of self-paced video learning modules).

Handy Backup is among the fair-players. When you select the “Uninstall” option, there wont be anything reminding you of our solution in less, than five minutes. But, unfortunately, not everyone can boast with such an attitude.

Unfortunately, you may meet up some Symantec Backup Exec issues during its using.

So, how to completely uninstall, say, Symantec Backup Exec? The answer is right here!

Ssi open water diver manual download. This globally-recognized certification program is the best way to begin your life-long adventure as a certified scuba diver. Personalized training is combined with in-water practice sessions to ensure you have the skills and experience required to become truly comfortable underwater. You will earn the SSI Open Water Diver certification.

Symantec Backup Exec Uninstall Instruction

Method 1

NOTE: This process will replace any missing or corrupted files and registry keys and a complete re-configuration.

  1. Reinstall Backup Exec 11d and above with same settings as the previous installation.
  2. When prompted to select a BEDB (Backup Exec Database) Database Server select the same option as used with the prior installation.
  3. Uninstall Backup Exec through Add / Remove Programs. (Programs and Features in Windows 2008/Vista/7)

Method 2(use only if Method 1 is unsuccessful):

Symantec Backup Exec 2015 Pricing

  1. Save any need items of the BE environment. (Settings, Database, Job Logs, Catalogs, Reports, etc)
  2. Stop all Backup Exec Services, SQL Server (BKUPEXEC), MSSQL$BKUPEXEC, and MSSQL$BKUPEXECDLO Services.

    Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

  3. Remove the following Backup Exec Registry Keys:
    HKEY_LOCAL_MACHINESOFTWARESymantecBackup Exec for Windows
    HKEY_LOCAL_MACHINESOFTWARESymantecDLO
    HKEY_LOCAL_MACHINESOFTWARESymantecVxPush
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstallSymantec Backup Exec 11.0
  4. Delete any folders identified as Backup Exec or SQL, if SQL is also being uninstalled.
    HKEY_LOCAL_MACHINESoftwareClassesInstallerProducts
    -27C846ACBA6625648A529949BAF5D651
    -30BF39ED4133E2E4F8549EDB77C6D152
  5. Also search through the other GUIDs to find all the ones for Backup Exec (Right click the HKEY_LOCAL_MACHINEsoftwareclassesInstallerProducts key, Click Find , Type Backup, Click Find, Now check every Key that it finds before deleting. Check the right hand pane, look for the key “ProductName” It should say “Symantec Backup Exec Media Server or Remote Agent depending on what was installed. Make Sure to Right Click on the GUID in the left hand pane and Delete.”)
    Please Note : Do not remove the following registry key, if Backup Exec needs to be installed again:
    287320 HKEY_LOCAL_MACHINESoftwareSymantecCRF
    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSCSIChanger
    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices    (delete each key in the list below)
    ● Backup Exec
    ● BackupExecAgentAccelerator
    ● BackupExecAgentBrowser
    ● BackupExecDeviceMediaService
    ● BackupExecJobEngine
    ● BackupExecManagementService
    ● BackupExecRPCService
    ● bedbg
    ● bevssprovider
    ● Backup Exec VSS Provider
    ● DLOAdminSvcu
    ● DLOMaintananceSvc
    ● SCSIChanger
    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSNMPParametersExtensionAgents(delete each key in the list below)
    • Value key:
      SoftwareSymantecBackup Exec For WindowsBackup ExecSNMPEvents
    • Value key:
      SoftwareSymantecBackup Exec For WindowsBackup ExecSNMPTapeAlert
  6. Remove the SQL Instance in one of the following ways:

    a. If there is no other SQL instance on this machine delete:
    • HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server

    ---OR---

    b. If there are other SQL Instances, follow this procedure:

    • Navigate to:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server

    • i. Right-click the InstalledInstances value, and then click Modify from the shortcut menu. The Edit Binary Value dialog box appears.
    • ii. Remove the BKUPEXEC from the Value data box, and then click OK.
    • iii. Right-click the BKUPEXEC key, and then click Delete from the shortcut menu. The Confirm Key Delete dialog box appears.
    • iv. Click Yes.
    • v. Navigate to the following registry location, and delete BKUPEXEC from the Default value.
      - HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server80ToolsService Manager
    • vi. Right-click the Default value if it is BKUPEXEC, and then click Delete from the shortcut menu. The Confirm Value Delete dialog box appears.
    • vii. Click Yes.

    • HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQLServerComponent Set

    • i. Perform a search in the registry by highlighting 'My Computer', by going to Tools - Find search for BKUPEXEC and Delete all values identified.

    NOTE: Be sure to Check “Keys”, “Values”. and “Data” under Tools Find Look at
    NOTE: You will not be able to delete any of the values identified as legacy registry keys. Just page through these to the next set.

    ---OR---

    c. If using a SQL instance other than the BKUPEXEC instance:

    • i. Detach the BEDB database. (Refer to SQL documentation on how to detach a database from a SQL instance.)
    • ii. Remove the BEDB files bedb_dat.mdf and bedb_log.ldf from SQL instance data and log folders.
    • iii. If there are additional SQL instances on this server other than BKUPEXEC,
      NOTE: Browse to Program FilesMicrosoft SQL Server. That folder contains all SQL instances on the server.
      Instances named MSSQL$BKUPEXEC are related to an install of Backup Exec 10.0 and SQL 2000 and can be removed without consequences.
      SQL instances for SQL 2005 will be named MSSQL.1. MSSQL.2 and so on for each instance.
      Inside each instance folder, the name of the instance will show (Eg. BKUPEXEC, ACT!, ETC)
    • iv. Delete the one that is identified as being the Backup Exec one and make note of the number.
      - HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server
    • v. Delete the SQL folder with the same MSSQL number that is identified in the Program Files folder
  7. Remove all Backup Exec files from install directories (Note: %SystemRoot% is typically C:Windows)
    • Backup Exec Installation Directory. The default installation directory is C:Program FilesSymantecBackup Exec
    • Backup Exec Maintenance Installation Files (if present)
      - %SystemRoot%Installer{BEA465C8-2923-42C6-9141-BE44739A6A80} (32-bit system)
      - %SystemRoot%Installer{ACE16FD9-EB87-42F4-9CB5-6FA8C820C9CD} (64-bit system)
    • Also, Create a new column in the installer by right-clicking on the column headers.
      - Choose “Author” Drag that column all the way to the left so that it is next to the MSI files.
      - Mouse over the msi files. if the MSI are identified as belonging to Backup Exec or Veritas, Delete them
    • Backup Exec Drivers located in %SystemRoot%System32Drivers
      - *.VSD (all files with a .vsd extension)
      - SCSICHNG.INF
      - SCSICHNG.SYS
      - oemtap.inf
      - oemtap0.inf
      - %systemroot% assembly, make sure there are no entries in there that are called Backup Exec or BKUPEXEC, if they are there, delete them.

      NOTE: If the SQL Services startup properly and there no SQL Warnings or errors in the Windows Event Log or SQL Error Logs, it may not be necessary to perform step 8. Also, if errors do occur while removing SQL Express, it is not recommend to delete or modify any SQL Files or registry values without first opening a support case with Microsoft.

    • Remove SQL Express BKUPEXEC and BKUPEXECDLO instances through Add/Remove Programs (Programs and Features in Windows 2008/Vista/7). These need to be removed in reverse order of how they appear in Add/Remove Programs (or Programs and Features)
      • Microsoft SQL Server 2005
      • Microsoft SQL Server Native Client
      • Microsoft SQL Server Setup Support Files (uninstallation of Microsoft SQL Server 2005 should remove this item)
      • Microsoft SQL Server VSS Writer (uninstallation of Microsoft SQL Server 2005 should remove this item)
    • Delete the Backup Exec icon from the Desktop.
    • Delete the Backup Exec program group from:
      • Documents and SettingsAll UsersStart MenuPrograms
    • Reboot the system.

Did you uninstall Symantec Backup Exec? Download Handy Backup right now!

Symantec Backup Exec 2012 User Guide

Preparing for a manual push-deployment of the Desktop Agent

Before you try a manual push deployment of the Desktop Agent, you should perform the following steps. These steps are not necessary when you use the Backup Exec push installer.

Table: How to prepare for a manual push-deployment of the Desktop Agent

Symantec Backup Exec 2015

Step

Action

Notes

Step 1

Locate the following files:

  • *.mst

  • *.cab

  • DLOBuildInfo.ini

  • *.msi

The files should be located in the <servername>DLOAgent directory.

Step 2

Run the msiexec command using the value in setup.ini from the cmdline key as a base:

/qf DEFAULTMEDIASERVER=”<From setup.INI File>” DLODBINSTANCENAME=”<FromSetup.INI File>” LAUNCHCLIENT=”1″ REQUIREDMDACVERSION=”2.8″ TRANSFORMS=”1033.mst” /l*v “%TEMP%DLOAgentInstall.log”

For a silent installation, replace /qf with /qn. To install without user interaction, but with a display of the installation progress, replace /qf with /qb.

If MDAC 2.7 is used, you must replace REQUIREDMDACVERSION=”2.8″ with REQUIREDMDACVERSION=”2.7″. No other values are valid. The installation fails if the MDAC version on target system is less than the REQUIREDMDACVERSION value.

The specification of the TRANSFORMS property is required. The property affects the installer user interface and the start menu shortcuts. The DLO Agent is installed with support for all eight languages, regardless of which transform is chosen.

See Values for the TRANSFORM property of the msiexec command.

MSI 3 . 1 is required on the target systems. The MSI 3.1 installer is included in the following directory:

Backup Exec 2010 User Guide

Preparing for a manual push-deployment of the Desktop Agent