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
pkh | 21 Nov 2010 | 0 comments

If you are using policies to create your jobs, are you aware that you can edit the job properties of job that is scheduled to run next?  Here is what editing the next run will do

I use this feature a lot to edit my pre- and post- commands.  Sometimes, I want them to skip a run.  I will delete them from the job properities of the next run and I don't have to worry about re-instating them for subsequent runs.  The edit next run feature also works great for temporarily changing the target media set.

This is easier than editing the policy to make the change.  If you change the policy, you got to edit the policy again after the next run to reverse the change .

To edit the next run, right-click on the scheduled policy job in the Job Monitor tab and select Edit Next Run.

pkh | 19 Nov 2010 | 0 comments

Q.  I know I did the backup, but the data is not displayed when I try to restore it.

A. You got to ensure that the Beginning Backup Date and Ending Backup data are set wide enough.  See the diagram below

 

This is applicable to situation whether the backup is an old one or the server date is wrong.

pkh | 18 Nov 2010 | 0 comments

Q. Can I delete an item from a backup?

A. No.  It is not possible to delete an item from a backup.  The only way is to restore the entire backup, delete the item and then backing up the rest of the data again.

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:

Hywel Mallett | 19 Oct 2010 | 0 comments

 

Many of the problems people encounter with Backup Exec aren't technical problems, but issues with understanding how the software works, or how to get the best out of it. Here are 10 tips you won't find in the manual.
  1. Don't buy Backup Exec (yet). If you're installing Backup Exec for the first time, make use of the 60 day trial. Evaluate which agents and options you need to buy for the first 30 days or so, then buy what you need and enter the license keys before the 60 days is up. By buying once, and buying the right options, you minimise wasted expenditure, and simplify relicensing in the future, when it all needs renewing at the same time.
  2. Start simple. Before you install all the agents and options in the trial, and select every tickbox, just install the core components to start. Make sure you understand them before you add the agents and options, and then add them one-by-one. Backup Exec's design allows you...
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...