Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog
Showing posts tagged with 2010
Showing posts in English
pkh | 18 Nov 2010 | 0 comments

Q. Why does BE use new .bkf files, rather than overwriting old ones?

A. Go to Tools --> Options ---> Media Management and check that the following is set

 

If you set it to overwrite recycleable media, then it will not create any new .bkf files if there is a .bkf in the B2D folder that can be overwritten.

Setting this option to overwrite scratch media (1st option) can cause BE to create more and more .bkf until the disk is full.

pkh | 18 Nov 2010 | 2 comments

Q. Why did BE use tape from a media set which is not targeted by the job?

A. When BE needs a tape to write to, it will first search for it in the following media set in the sequence listed below

1) the targeted media set

2) the scratch media set

3) any other media set

This is by design and is to ensure that the job completes successfully.

This problem will not occur if the Overwrite Protection Period (OPP) of the targeted media set is set correctly.  The most common mistake is not to cater for the time the job needs to complete.  The OPP starts from the end of the job, not the beginning.  Suppose the OPP is set to 1 day.  If your daily job is set to start at 10 p.m. and it takes an hour to complete, then the tape will be write protected until 11 p.m. the next day.  When the job runs again tomorrow at 10 p.m. the tape is still write-protected.  If the OPP is set to, say, 22 hours, then...

pkh | 17 Nov 2010 | 1 comment

If you are using the modified time method to do your incremental backups, do take note that the scans done by some anti-virus software can cause your incremental backups to become full backups.  When the anti-virus scans a file, the Last Access Date is changed to the time of the scan.  The anti-virus software may modify this date to what it was before the scan and triggering the modified time in the USN to change.  This results in the file being backed up during the next incremental backup even though it has not been modified.

Read the document below for a way to solve this problem if you are using Symantec Endpoint Protection

http://www.symantec.com/business/support/index?page=content&id=TECH102698&locale=en_US

If you encounter this problem and is using other anti-virus products, you should contact the vendor to see whether...

Terry Cutler | 29 Oct 2010 | 0 comments

Intel will be making Symantec Backup Exec 2010 available to its system builder partners through its network of authorized distributors. The addition of Symantec Backup Exec expands Intel's software offering for channel partners that are part of the chipmaker’s Enabled Solutions Acceleration Alliance(ESAA).

For following are a series of articles on this exciting announcement:

Mahesh Roja | 07 Oct 2010 | 1 comment

 

Refer this Tip If you faced Error during (Unable to prep database instances for upgrade)Upgrade from Backup Exec 2010 to 2010 R2

 

  1. Read ou the SCL list from Symantec site before start migrating.
  2. Back up all your data: in SQL server an your backup server.
  3. Prepare new OS and install there Backup Exec 2010 with default preferences (it installs local MSSQL 2005 Express).
  4. Stop Backup Exec services on old machine and on new machine.
  5. Copy DB(through Backup-Restore or Detach-Attach) from remote server to your local MSSQL installation on new machine.
  6. Edit tables [Device] and [DataPartition] and change old machine name to new one there.
  7. Delete in registry HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\DataPartitionGUID key.
  8. Launch services on new machine...
Stronty | 21 Sep 2010 | 1 comment

Here is a fix for the 0xe000fedl - a failure occured querying the Writer status.

We have seen this error a fair amount recently and mainly on customers Hyper-V environments. All the fixes that Symantec suggests have been tried but non of them work.

This particular fix is for VMs that have been created by doing a Physical to virtual conversion of a server. The reason the above error occurs when you run a backup of these Virtual Machines is due to them having the same disk ID as the host server. This is normaly 00000080.

If you use Diskpart to examine the disk IDs of the Host server and the virtual servers you will probably notice that the disk IDs are the same (00000080). This is due to the Physical to Virtual conversion.

To fix this you can use a tool called dumpcfg.exe which will allow you change the disk ID of the Virtual server. You will need to do this with each Virtual Machine that you have done a Physical to Virtual conversion of on your Host...

marucho | 02 Sep 2010 | 0 comments

I've been a backup exec user since the seagate days. Over the last decade I've been really impressed with the innovation and features available now in current disaster recovery tools. It actually seems a lot easier now to achieve near 100% up-time. I'm a big fan of appliance based backup solutions with vm fallback and bare metal restore options. I'm guessing it's just a matter of time before tape backup is phased out of mainstream DR processes.

Swathi Turlapaty | 02 Aug 2010 | 44 comments

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.

...

Martin_Forster | 08 Jul 2010 | 0 comments

Hello, i write this blog for my own record, and for symantec.
I was asked to write a summary of my issues, after i tried to give back my dedupe licenses. So here we go.

1.) frownGRT Backups work only once and then fails with "An error occurred in the PDVFS driver: PdvfsOpendir: failed errno=2"

2.) frownRestore of Single Files only works with the fast "Use Fast File Restore" Option switched off. HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Tape Format

3.) frown...

Katie Beck | 22 Jun 2010 | 2 comments

Earlier this month, Symantec Backup Exec 2010 was recognized as the Best of Tech·Ed 2010 award winner by Penton Media’s Windows IT Pro and SQL Server Magazine at the Microsoft Tech·Ed North America 2010 IT Pro Conference in New Orleans.  Backup Exec 2010 was awarded the top honor in the backup and recovery category based on its innovation, strategic importance to the market, competitive advantage and exceptional value to customers.  
 
Backup Exec 2010 (BE 2010) is the latest update to Symantec’s industry leading Backup Exec product and became generally available earlier this year.  BE 2010 helps mid-sized businesses save time and money by protecting more data and utilize less storage through fully integrated data deduplication and archiving technologies.  It also helps organizations eliminate duplicate data with a simple three-step process that does not require an additional point product.  With Backup Exec...