Video Screencast Help
Backup and Recovery Community Blog
Showing posts in English
Alex Sakaguchi | 29 Apr 2013 | 0 comments


Didn't get to attend a session at Vision 2013 that you wanted to? 

Or maybe this year you didn't get to attend Vision at all?  We've decided to take some of our top non-security Vision sessions and make them available through Google+ Hangouts On Air. Topics will focus on backup and recovery, archiving and eDiscovery, and business continuity and disaster recovery.

Each session will be broadcasted free to give you an opportunity to hear about the technology from the experts, get some insight into the roadmap and futures, and get your questions answered live.

Here's what you should do:

Click on the links in the Google+ Event Page column that corresponds with a session you're interested in.  The link will provide more information about the session, including participants, the date and...

inn_kam | 29 Apr 2013 | 1 comment

Hi Guys

i want to mention a very special step which we need to take care about,when upgrading VBR To Ops Center

as when we upgrade OpsCenter from VBR ,And go to internet explorer ,it shows Server not found

when we checked the services Ops Center Services were not starting 

so i took help from symantec 

they resolve this and told that donot uninstall the VBR Server, and told us to follow the steps: 


Use the following procedure to uninstall VBR after upgrading to OpsCenter server on Windows platforms:
1.  Select Control Panel > Administrative Tools > Services and stop the Symantec Product Authentication Service. 
2.  Navigate to the following location after upgrading from VBR to OpsCenter server: <install_path>\VERITAS\Security\Authentication
Note: On a 32-bit system the...
drhartman | 26 Apr 2013 | 1 comment

The backups have begun to fail consistently with the following error:
Error bpbrm (pid=16758) db_FLISTsend failed: system call failed (11)

I have found that the directory, /opt/openv/netbackup/db/images, is pegged at 100%. What suggestions might you have to recover from this situation?


Thank you,


Krishna Pratap Singh | 25 Apr 2013 | 1 comment

Symantec Backup Exec Management Plug-in 1.1 for Kaseya until the recent past was supporting the following Kaseya versions namely Kaseya Server v 6.1 and Kaseya  Server v6.2. The release of Kaseya Server v6.3 in first quarter of this year changed the scenario a bit and the existing plug-in was no longer compatible. However with the release of service pack (SP1) for  Symantec Backup Exec  Management Plug-in 1.1 the wait for Kaseya 6.3 support is finally over. 


So What’s New?

This release of the plug-in includes following new features and capabilities

  • Platform Support for Kaseya Server 6.3
  • Support for Windows Server 2012
  • Support for MS-SQL Server 2012

It is important to understand that the SP1 release of the Symantec Backup Exec Management Plug-in 1.1 for Kaseya is just a platform support release for Kaseya 6.3.The earlier version of the plug-in...

AshutoshTamhankar | 23 Apr 2013 | 0 comments


Snapshots created for a virtual machine on an ESX host, may not be deleted after a backup if the remote agent crashes abnormally during the backup operation. So that such orphaned backup exec snapshots can be deleted automatically, following registry key could be set:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\VMware Agent
Key name Value Data type
AutoOrphanSnapshotRemoval 1 = Orphaned snapshots created by Backup Exec are deleted at the beginning of the backup. REG_DWORD


More information here:

inn_kam | 18 Apr 2013 | 2 comments

This article is taken from symantec special hidden document


Ops Center (Free Product)

OpsCenter is a free product which gives you the ability to monitor, alert and do operational reporting on NetBackup, Enterprise Vault, Backup Exec and PureDisk. OpsCenter server is part of NetBackup and can be deployed on master server for managing a single domain, or independently for managing multiple NetBackup Domains. It also allows you to do minor management tasks such as “upping” tape drives, restarting failed jobs, freezing/unfreezing and other tape functions, restarting services/daemons on Masters etc. The free version limits historical reporting.

OpsCenter Analytics (Licensed...

inn_kam | 18 Apr 2013 | 2 comments


i have searched and also use this tech note for my SQL server troublehooting 

this is KB Article and very hidden article by symantec but its very useful for the users taking Backups of SQL Databases

So  just for easiness of users i am publishing it, will help all SQL users who are backing thier data bases through Netbackup


How to troubleshoot Microsoft SQL Server database backup issues

Article:TECH38369  |  Created: 2005-01-13  |  Updated: 2012-09-10  | 

Article URL





How to troubleshoot Microsoft SQL Server database backup issues...

inn_kam | 18 Apr 2013 | 0 comments

In Netbackup ,the most common issue came i.e EMM Server is down , 

So i search in Symantec , and very hidden article came up,by Symantec, and its not easy to find this article 

So i am sharing this , its excellent one. i resolved a lot from this


How to troubleshoot NetBackup Enterprise Media Manager (EMM) startup issues

Article:HOWTO61176  |  Created: 2011-12-02  |  Updated: 2012-09-27  |  Article URL


Note: It is not a comprehensive Process Flow for all issues, related to EMM, but does provide basic...

AshutoshTamhankar | 18 Apr 2013 | 8 comments


Simplified Disaster Recovery (SDR) works with Backup Exec when you run backup jobs that include all critical system component selections. For each computer that you protect with this type of backup job, Backup Exec creates a disaster recovery information file for that computer. A disaster recovery information file contains computer-specific information for the computer being backed up. Computer-specific information includes details such as hard disk layout, storage drivers, network drivers, and system version details. It also includes Backup Exec catalog details such as backup set information and recovery point details. Each disaster information recovery file uses the file name <computer_name>.DR.
If you uncheck files/folders from a critical resource, the green light for SDR goes off and no .DR file is create for the backup. Sometimes you might want to exclude files/folders which are temporary for example. Following registry change...
AshutoshTamhankar | 17 Apr 2013 | 0 comments
The size of the read and write buffers used for the VWware API (VDDK) by Backup Exec can be tuned using the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\VMware Agent
"Enable Buffered Reads"=dword:00000001
"Number of Read Buffers"=dword:00000004
"Size of Read Buffers"=dword:00000400
"Enable Buffered Writes"=dword:00000001
"Number of Write Buffers"=dword:00000004
"Size of Write Buffers"=dword:00000400

More info

If you are looking at tuning performance of your backups generally, recommend you to go through the Backup Exec 2012 performance tuning guide: