Video Screencast Help
Search Video Help Close Back
to help

Backup and Recovery Community Blog

Showing posts tagged with 2010
Showing posts in English
SeanRegan | 21 Jun 2011 | 4 comments

I noticed an interesting tweet today from Rachel Dines @Forester. It quoted Carl Meadows @SungardAS. 

 

"Common misconception: cloud solves our sys admin problems. Wrong! Cloud requires more skilled sys admins." 

I have been thinking about this a lot lately as I drive down 101 to Mountain View from SF.  Each day someone gets in a fender bender and traffic continues around them. Sure, life is disrupted but it's par for the course. Sometimes car accidents happen. As I drive south I also pass under SFO. Each day 100s of planes take off. The expectation is that these planes will almost never have an accident. They are piloted by highly trained pilot while the car on 101 is piloted by someone like you and me. 

Cars are like servers.  Planes are like Clouds. 

  • When a plane crashes the media shows up at the scene, the bloggers speculate....
Elizabeth Teffner | 17 Jun 2011 | 3 comments

The Backup Exec Usability Team is interested in your feedback! 

We are holding remote usability sessions to gather user feedback on a new single server edition of Backup Exec. This upcoming edition is targeted for customers who only have a few servers to back up.

These sessions will be conducted via WebEx and only take 1 hour of your time.

If you are interested in participating in this usability study, please click here to view available session times. The sessions are offered at various times from June 21st, to June 24th.

This is your opportunity to help shape the future of Backup Exec.

SeanRegan | 15 Jun 2011 | 4 comments

We have seen some bombastic marketing over the last several months in the data protection space.  One vendor stuffed 26 women in a Mini Cooper, and Veeam called platform proliferation “the next big thing” when they announced intentions to deliver Hyper-V support in December of 2011 – despite it being available for the past three years from Symantec. Let’s cut through noise and look at some of the underlying facts.

Innovative, Established and Proven

•                Over 15,000 companies already leverage Symantec’s Backup Exec for Hyper-V support. What Veeam has announced has been in the market for 3 years with Symantec Backup Exec. 

•                Backup Exec protects over 75,000 virtual hosts (approx 60,...

pkh | 04 Jun 2011 | 0 comments

If you are using barcode labels and a HP tape library, you might be interested in the attached document from HP.   In particular, on page 11, there is a table which specify which suffix denotes which kind of tape.

28Tech | 12 May 2011 | 1 comment

I have recentely been experiencing a series of errors with Backupexec on my HP Proliant DL380 G5 Servers.

The errors are almost exclusively related to backing up exchange to tape.

I have found the problem to be solved by disabling the "HP WMI Storage Providers" service.

 

The Error code was E00084F9

 

I hope this post helps someone who has been banging their head against a wall as hard as I have!

 

Cheers

Ben Turvill

28 Technology Ltd

un baiat | 06 May 2011 | 0 comments

Made a short tuorial on how to solve the problem. hope it helps. 

Here is the link to my blog post:

http://www.lo0.ro/2011/solving-lotus-domino-backup-exec-unable-to-attach-to-a-resource-v-79-57344-33932-unable-to-attach-to-a-resource-v-79-57344-33932/

and here is the solution:

Edit the job. go to Settings -> Advanced -> Open file backup when Advanced Open File Option is not used.
Change With a lock check box to Without a lock.

Kiran Bandi | 07 Apr 2011 | 1 comment

How to configure Backup-Disk jobs,media sets & Backup Exec for proper overwriting of backup sets?

Media Overwrite Protection Level: FULL. (From tools --> Options --> Media Management)

Job should start as Overwrite Only. (Backup job properties)

Media Set Configurations:

For daily backups with one week retension: OPP 6 days & AP None

For Weekly backups with a month of retension: OPP 4 weeks & AP None

For Monthly Backups with a Year retension: OPP 360 days (some value less than an year but more than 11 months) & AP None.

With all the above settings, each B2D job will create a separate backup set (.bkf file) and from the starting of second cycle BE starts overwriting the oldest among the recyclable media.

Regards....

Kiran Bandi | 29 Mar 2011 | 3 comments

Some of the main differences between Backup Exec and Backup Exec System Recovery:

1) Backup Exec is a backup and restore software, whereas Backup exec System Recovery is a recovery software.

2) BESR can write data only to disks not to tapes, whereas BE can write to both.

3) BE works at file level whereas BESRworks at block level.

4) One of the main features of BESR is dissimilar hardware restore technology. One can perform a Bare Metal Restore of a system with Backup Exec also, but mostly onto a similar hardware.

5) BESR can perform Physical to Virtual conversations, BE cannot.

Regards...

macpiano | 27 Mar 2011 | 6 comments

I have decided to start a blog for my experiences with dedupe.

My setup right now is 2 Dedupe servers in 2 buildings with a 100MB wan. One building has a file server with 2.2 TB of data and several other smaller servers. Both dedupe servers are housing the dedupe folder in both buildings with about 4 TB available. 

I have a tape drive attached to both but what I want is mainly in the second building.

My finding(s) at least to me.

1. Live Update. That was the first hurdle. It was necessary to go to the control panel, live update then manually add the proxy exception, using IE settings did not work. I also changed the cache size to 100 MB just to be sure.

2. Remote Agent has to be manually removed from each server then the new agent installed. I was going from 2010 to R2 so your milage may vary.

3. I am using Backup to dedupe, duplicate that dedupe job to the other dedupe folder in the other building, then backup to tape in the second...

Kiran Bandi | 18 Mar 2011 | 2 comments

Most common issues with tape devices:

1) Tape drive asks for cleaning more frequently.

2) Media will be marked as full after writing very less amount of data to it. (Will happen with all the media in the library)

3) Media requested by BE may not be inserted properly into the drive.

The first two indicates that there is a problem with tape drive. Investigation has to be done with tools provided by the vendor. Like HPLTT tools for HP drives, IBM ITDT tool for IBM make etc... Perform a write test also along with the general investigations. And some times the drive temperature also create problems. (Drive fan assembly may be having issues). If any problems reported during the testing by using vendor tools, contact the vendor and ask for a replacement.

The third indicates there may be a problem with robot. In this case you can see something like "Stow operation failed at slot XX"...