Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog
Showing posts tagged with Backup Exec
Showing posts in English
Solange Deschatres | 28 May 2014 | 0 comments

At Symantec, we often talk about information and data as the lifeblood of the business, especially in today’s digital world. Whether it’s in the form of financial reports, emails or software — information powers our world. If companies lose that information, or worse yet, entire platforms running that data, business comes to a screeching halt.

Imagine for a moment that your Microsoft Exchange email service is disrupted by data loss – months of information gone. With your system down, you’ve not only lost work but you have to stop doing business, selling products and communicating with your customers. The disruption isn’t just a headache for your IT department; downtime causes frustration across the company. Ultimately, data loss, either accidental or deliberate, costs your business valuable time and money so it’s essential that you protect your information before disaster strikes.

The majority of yesterday’s backup technology isn’t sophisticated enough to protect...

Daeyoung_Chun | 06 Apr 2014 | 3 comments

I want to share the following simple tip.
This is to query the BE SQL DB(BEDB) for check the file name for the catalog.
This information will not be directly supported by Symantec.
In addition, this feature is not available directly from Backup Exec.
Symantec is not responsible for any issue caused by a use of it as well.

 

select cr.MachineName,
       cr.ResourceName,
       ci.HistoryFileName,
       ci.ImageName,
       cm.MediaName,
       ci.EngineName,
       cf.MediaID,
       ci.ImageNumber,
       cm.CartridgeLabel,
       cm.MediaType,
       cm.Location,...

ramcm | 02 Apr 2014 | 2 comments

Registrations for Symantec DLO 7.6 Beta program is now open. Click here to register...

https://symbeta.symantec.com/callout/?callid=86FFCE8379A949318C954A79957EF283

Artegic | 01 Apr 2014 | 0 comments

In https://www-secure.symantec.com/connect/forums/lin... I reported being surprised by my Backup Exec 2012 installation accusing me of a license violation (translated from German):

     Message:       Linux Media Server Option-License Violation
                    The trial period for the Linux Media Server Option has expired.
                    You must acquire the Linux Media Server Option or deactivate the devices.
        ...

Hadley Robinson | 14 Mar 2014 | 0 comments

I followed every thread all over the world to attempt a fix for this error "V-79-57344-65245 - A failure occurred accessing the object list" that was being thrown in the following environment while backing up a remote server.  This is a generic error when VSS is having problems accessing mounted volumes/directories/files.

Backup Exec Server: Windows 2003 SP2 Backup Exec v12.5 with all patches, hotfixes, and updates  PDC
Remote Server: Windows 2003 SP2 w Exchange 2003 BDC

Backup Exec could backup files that were not open on the remote server and in use.  Anything that needed AOFO (VSS) would throw the error.  The system log on the remote server would throw the Ntfs 55 error (corrupted disk).

None of the published fixes worked including /../ entries that might be...

4L SpA | 28 Dec 2013 | 0 comments

Workaround to Event 57802 and 57804, catalog mistmatch (Following a successful upgrade, the Backup Exec Server Service fails to start and the event logs report an error "The Backup Exec Server Service detected a schema version mismatch)

 

1.- Upgrade existing BE 2010 R3 to 2012

2.- Using existing procedure, copy folders Catalog and Data to safe place or shared drive

3.- Install brand new Windows Server, with the EXACTLY same name as the old one, as on step 1.

4.- Copy the folders Catalog and Data from step 2.- using procedure accordingly

5.- Start services of the new BE 2012

6.- That's it!

Digital_Kru | 13 Dec 2013 | 0 comments

Welcome to the second installation of the DRT Dozen.

1)       Another dirty secret of DR plans – too many of them ignore or underestimate the importance of security. A recent SANS Institute (www.sans.org) report provided some key recommendations for how to implement security successfully.  Starting from an approach of Layered Security – it is a defensive strategy that uses multiple technologies to block access.  The key is to understand that security isn’t just antivirus; in fact, antivirus isn’t even the first layer.

 

layered security_1.JPG

Network Controls: Firewalls, Intrusion Detection Systems, and DLP (Data Loss Prevention)

Antivirus: Polymorphic code (changes in the executable), and Hueristics (identifies hostile behavior...

Ketan Pachpande | 13 Nov 2013 | 0 comments

 

Differences and Similarities between Quick Erase & Long Erase options in Backup Exec 2010 & 2012

Backup Exec 2010 R3:

Erasing Media.jpg

Backup Exec 2012:

Erasing Media 2012.jpg

In BE 2012:

      Quick Erase option has been renamed to 'Erase media now'

      Long Erase option  has been renamed to 'Long erase media now' 

 

 
Sr no

Quick Erase (2010) /

Erase media now (2012)

Long Erase (2010) /

Long erase media now (2012)...

Digital_Kru | 30 Oct 2013 | 3 comments

Welcome to the first installation in a series of blogs that will detail 12 topics around disaster recovery technology – thus the DRT ;)  These topics will cover industry trends, best practices, and relevant news on the topic that I feel you may also enjoy.

I’ll start with a brief introduction of myself.  My name is Michael Krutikov, and I have been in the IT field for over 14 years; in sales, training, out in the field as a systems consultant and VAR account executive, in product management and now in marketing. Through a constant learning journey that is driven through thousands of meetings with partners and customers, my mission is to deliver solutions for customer’s problems, challenges and goals.  

1)       Virtualization is the reality; not only is it an increasingly popular way to run your IT, but it can and should save you money while improving functionality. It almost goes without saying that if you’re not using...

Ketan Pachpande | 29 Oct 2013 | 2 comments

In Backup Exec 2012, if you get the time out error as: 

The request channel timed out while waiting for a reply after 00:09:59.9980000. Increase the timeout value passed to the call to Request or Increase the sendTimeout value on the Binding. The time alloted to this operation may have been  a portion of a longer timeout.

 

Error Backup.JPG

 

This means, the UI of Backup Exec 2012 has waited for 10 minutes for the underlaying services to reply back.

If you want BE UI to wait for longer time (let us say 20 minutes),

  1. Stop the UI.
  2. Open the file BackupExec.exe.config (located at Program Files/Symantec/Backup Exec)
  3. Replance all the occurrences of 00:10:00 with 00:20:00
  4. Start the UI.

 

My Senario:...