Durgarao

Backup Technology : VEEAM ISSUE: Job fails with the following error message, “Task failed Error: Object <vmname> not found” Check the log file for the following entries: Error    Failed to expand object added to the job. Object: 'Object, id: , name: <vmname>, type: VM, vi type: VirtualMachine, host name: ’. Error    Object <vmname> not found. (System.Exception) The most direct resolution can be verified by editing the job, selecting the “Virtual Machines” tab, then selecting recalculate. Below is the screenshot for the same. If any VM whose size comes back as “Not Available”, one should attempt the below as a resolution . Cause: This error is caused by the VM’s unique inventory reference identification number (MOREF, or Managed Object Reference) changing within the virtual infrastructure, or the VM having been deleted. Veeam is still attempting to find the VM by its old reference ID number based on a “find ...

SQL Versions – Sql 2005 and Above Backup Technology – Symantec Backup Exec Scenario 1: SQL Backup will complete successfully. However, with below exceptions, V-79-57344-33959 - The master database only supports full backups. Differential and log backups cannot be performed on the master database. Scenario 2: SQL Backup will complete successfully. However, with below exceptions – V-79-57344-33960 - A log backup was attempted on database msdb that is not configured to support log backups. To change the configuration, use the SQL administration tools to set the recovery mode to Full. A new full backup should be performed if this setting is changed before a log backup is run. First Understand, Backup Schedules for SQL. Most Scenarios will contain two SQL Backups (FULL + Log files Backups). Reason why we see above error exception: SQL Databases maintains their own recovery model like Simple, FULL & Bulk Logged through which logs o...

Backup Technology:  Symantec Backup Exec Issue: Log backup of SQL database fails with the error "BACKUP LOG cannot be performed because there is no current database backup" Job Error message: V-79-65323-4214 - An error occurred on a query to database "Database Name" V-79-65323-4214 - BACKUP LOG cannot be performed because there is no current database backup. Solution: 1. Ensure no SQL backups run outside Backup Exec (including SQL in-built utility for Backups and Restores) as that would interrupt the continuity of SQL backups within Backup Exec schedule causing the job to fail. 2. Run Full database backup. 3. Perform Transaction log backup, it should complete without any errors.

Backup Technology : Symantec Backup Exec This will not require any server reboot. But, it may require BE service restart. Also, perform this task only when there are no backup jobs are running. ISSUE:  (Job: "Catalog JOB") the job missed its scheduled start time by more than 1 day. ISSUE Description:   Catalog job 'Catalog JOB’ is not visible in the backup exec console. But we are receiving the error message “(Job: "Catalog JOB") the job missed its scheduled start time by more than 1 day” continuously. We need to follow the below steps to resolve this issue. SOLUTION: If backup job is not visible in the BE console or not found under any of the storage devices. Then, we consider as this is orphaned job and traces are left in BE database and need to remove from the BE database. To remove the orphaned catalog job from the BE database, we need to raise a case with Symantec and remove the job. Note:  We should take help from Symant...

How to install Backup Exec Remote Agent for Windows Servers (RAWS) and/or Advanced Open File Option (AOFO) for Backup Exec 11d - 2010 R3. We can install BE Agent in 3 way.  Please follow the below instructions on how to install Backup Exec Remote Agent for Windows System (RAWS):    1.  Automated (push) Installation.  ( to be performed from the Backup Exec media server )     2.  Local (manual) installation.  ( to be performed on the remote machine )     3.  Silent (command line) installation.  ( to be performed on the remote machine ) 1. Automated (Push) Installation of RAWS:   On the media server, open the  Backup Exec console .   Go to  Tools -   Install Agents & Media Servers on Other Servers  Note:  For Backup Exec 11d / 10.x go to  Tools - Install Remote Agents. On the 'Remote Install' / 'Remote Server' section perform one of the followi...

Sometimes you will not able to figure out the Symantec Backup Exec license information on the console to contact with support. In such a cases, we need to run the Backup Exec license tool to know the Backup Exec license information. Below are the steps, how to run the Symantec license tool. Steps1:-  Click on Backup Exec home  à  Select Installation and Licensing  à  and click on Backup Exec License Assessment Tool. Step2:-  Backup Exec License Assessment Tool dialogue box will be opened (shown in below fig). Click Next. Step3:-  Select create a new license scan and click next. Step4:-  Select Save this scan check box and click Next. Step5:-  Leave the default settings below and click Next. Step6:-  Select Search for specific computers and click Next. Step7:-  Click on Add computers and select only Backup Exec server then click ok. Step8:-  Cl...

LOG Locations in Backup Exec: Backup Exec Support Log (SymHelp): Default Directory:  C:\Program Files\Symantec\Backup Exec Filename:  <Servername>__<Date>__<Time>.sdbz Usage: Symantec Help  ( SymHelp ) is a utility designed to quickly and efficiently diagnose common issues encountered with supported Symantec products.  SymHelp can be used either to diagnose problems that you encounter, or proactively to ensure that your computer is ready to install the supported Symantec product. The Backup Exec Support Tool  ( BE_ST ) is a standalone tool that diagnoses many common issues found in Backup Exec environments and also for few other Symantec products. If after reviewing the reports generated by the tool, you are still unable to resolve the issue, the tool will also assist with gathering appropriate logs to send to technical support should you decide to open a technical support case. If an internet connection is present, the tool wi...