Video Screencast Help
Backup and Recovery Community Blog
Showing posts tagged with Backup Exec
Showing posts in English
pkh | 30 Nov 2010 | 0 comments

When your backup job failed with an error message, "Unable to connect to resource .....", you should expand the job log by clicking on the Expand All button and examining each of the resource that was backed up.  Do not rely on the resource given in the "unable to connect" message.

My BE media server is also my Lotus Domino server.  A couple of weeks ago, my job failed with "Unable to connect to resource C: drive".  This message makes no sense because the C: drive on my media server can definitely be accessed.  Otherwise, BE will not be able to run.  I ran a test to backup the C: drive and it did not fail, but the following night's backup again failed when it is unable to connect to the C: drive.  It took a couple of failure before I expanded the joblogs and saw that the C: drive backed up fine, but the Lotus Domino databases were not being backed up.  I realised that the jobs were unable to connect to...

pkh | 30 Nov 2010 | 2 comments

BE comes with a commandline line applet called BEMCMD.  This program is located in the BE installation directory, along with it manual.  One of the BEMCMD can be used to start jobs which were already created.  For example,

"C:\Program Files\Symantec\Backup Exec\bemcmd.exe" -o1 -j"Backup SQL Logs"

Backup SQL Logs is a job that has been submitted as Run Now and On Hold.  The full path is used above because the BE installation directory is not in the default path in Windows.

You can schedule BEMCMD to run at a particular time using the Windows scheduler or as a pre- or post- command in a BE job.

In the example above, when the backup job ends, Backup SQL Logs will be started.  In this way, you can chain jobs together.

You can also run BEMCMD from any Windows machine...

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: