Video Screencast Help
Backup and Recovery Community Blog
Showing posts in English
Melite | 01 Dec 2009 | 0 comments

Hi everyone,

Being new to the role of admin as well as Backup Exec 12.5 and finding both "interesting" (reads as challenging) I have decided to start this blog.

In it I'm going to track my path from Newbie status, through Lowbie status to hopefully becoming Elite.

So far learning about Backup Exec has been rather frustrating, there is very little information out there for an admin at my level. This is not a whinge-fest just an observation and I think Symantec would do well to encourage the next generation of admins.

That said, here are some details to fill you in. I have 2 identical servers, brand-spanking-new HP ML150 G6's each with 8 GIG's of RAM and 500GB drives. 1 is located at a live site, the other at a remote site. My mission is to backup the required info at the live site and restore it to the server at the remote site.

This just cant be that hard, I can do it with a USB key, so why not with...

DominikG | 25 Nov 2009 | 0 comments
The available knowledge base article to move a Backup Exec server to another machine does not help you, if the new machine runs on a different OS, e.g. 64-bit operating system.
I noticed that many users do not know of a useful option in Backup Exec, named “copy server configurations”. With this free option and my following guide, you will be able to copy your existing Backup Exec server onto a new machine with different operating system.
 
If both servers are present, you could use the following steps to copy your data:

please note:

Go to "Tools" -> "Install options and license keys on this media server" and check if the free option to copy server configuration, named "copy server configurations", is installed on the media server. If not, please install it.

copy the data:

...
DominikG | 21 Nov 2009 | 3 comments
So, like you perhaps already know, the new version of Backup Exec System Recovery got released; Backup Exec System Recovery 2010. Some things changed, that are really important. For example the Manager no longer exists. This solution got replaced by Backup Exec System Recovery Management Solution.
I do not want to give a summary of the differences or pros and contras, I only want to talk about one fact that, in my opinion, is a absolute disaster:
 
If I'm not wrong (and I really searched all the information to this issue) you will not be able to migrate your storage destinations, jobs, schedules and so on from the Manager into the Management Solution. This means, that you will have to re-create you whole backups again!
Why in the world is that not possible? I already know customers of ours who will definitely go crazy.
 
The only information I found is, that you can migrate from BESR Solution to BESR Management...
DominikG | 19 Nov 2009 | 2 comments

Many users of Backup Exec are annoyed by the recommendation to apply all hotfixes made to the server also to the remote agent. I think this is quite understandable, because in daily business it is in most cases simply not easy to do it because of other, higher priority topics.

With this short piece of text I would like to change your point of view.
Please consider the following facts:

1. Many problems of backups with BE result out of a mismatch of server and RAWS.
2. Hotfixes are hotfixes, because they fix important issues.
3. If you have to call tech support, they will definitely check the version of server and RAWS and in case they do not match advise you to update.
4. This is really important: If you are waiting too long, the number of updates that have to be applied increase that much that a push update will no longer be possible.

The last point is really important. My investigations showed that somewhere between 8 (result of tech...

Zahid.Haseeb | 10 Nov 2009 | 0 comments

 Today in my BLOG i would like to discuss a topic in which Windows could not start due to an error while booting from a RAMDISK..

Environment

Veritas Netbackup Server OS # Win2003 Server R2
Veritas Netbackup Server version # 6.5
BMR backup image OS version # Domain Controller on Win2003 R2

Problem

Windows could not start due to an errorwhile booting from a RAMDISK..Windows failed to open the RAMDISK image

File PC-ABC\PC-ABC.ISO could not be loaded
The error Code is 21

Setup cannot continue. press any key to exit 

Resolution


Actually i have more drivers in the packages as you can see in the below picture. So what i did, i removed all un necessary drivers from the packages which does not need for the required image. See the below picture. i have highlighted the drivers packages...

Zahid.Haseeb | 10 Nov 2009 | 0 comments

 Today i would like to share some information which i had been facing when i was tried to boot my client to restore BMR backup

Environment

Veritas NetbackupOS win2003 R2
Veritas Netbackup Server version is 6.5
Veritas Netbackup Server is also the DHCP Server

Problem

i had been facing some problem when i was tried to boot my client to restore BMR backup

Errors

PXE-E74 : Bad or missing PXE menu and/or prompt information
PXE-E55 : ProxyDHCP service did not reply to the request on port 4011

Work Around

I also tried the below link but i have not found any success. even though the below link is also informative
http://seer.entsupport.symantec.com/docs/309201.htm

Resolution

I remove the SRT and created a new SRT and my...

LyNeTtE-sKi23 | 04 Nov 2009 | 1 comment

Symantec Backup Exec System Recovery 2010 (BESR 2010)
 Symantec Backup Exec System Recovery 2010 is the upgrade from Symantec Backup Exec System Recovery 8.5.

Functionality:

Ø  Symantec Backup Exec System Recovery 2010 is a simple, cost-effective backup and recovery solution for small businesses that helps minimize downtime and avoid disaster by easily recovering data or complete Windows systems in minutes, even to different hardware or virtual environments

Ø  Symantec Backup Exec System Recovery protects your organization proactively by capturing automated backups –  without disrupting productivity.

Ø  Flexible recovery capabilities then allow you to recover what you need, when and where you need it.

Ø  Backup Exec System Recovery is the perfect standalone solution for small business customers with 1 – 4 Windows servers and can...

Zahid.Haseeb | 04 Nov 2009 | 2 comments

 Today in my BLOG i will discuss an error which i was facing in "prepare to restore" name [Error] V-126-3 'bmrprep' could not complete the requested operation""

Environment

Veritas Netbackup Server 6.5
OS win2003 R2
Client OS whose backup i willing to restore win2003R2 

Problem

I was facing an error when i was doing a ""prepare to restore"" so i can restore the BMR backup. As i click on ""Prepare to Restore"" i face the error  
[Error] V-126-3 'bmrprep' could not complete the requested operation""

Note:-
I also got a document which was saying me to upgrade Veritas 6.5 to Veritas 6.5.4 and the problem will be resolved
http://seer.entsupport.symantec.com/docs/329920.htm

Resolution

Actually...

Zahid.Haseeb | 04 Nov 2009 | 1 comment

 Today in my BLOG i would like to discuss an error which i have been facing while taking the BMR backup in Veritas Netbackup Server 6.5

ENVIRONMENT

Server

Windows 2003 Server R2
Netbackup Server 6.5

Client

Windows2003 Server R2

PROBLEM

Today i was facing an error while taking the backup of BMR. You can see the below error messages of ACTIVITY MONITOR

ACTIVITY MONITOR

11/4/2009 12:33:22 PM - estimated 0 kbytes needed

11/4/2009 12:33:22 PM - started process bpbrm (2220)
11/4/2009 12:33:30 PM - connecting
11/4/2009 12:33:31 PM - connected; connect time: 00:00:01
11/4/2009 12:33:34 PM - begin writing
11/4/2009 12:34:15 PM - Warning bpbrm(pid=2220) from client tpspdc: WRN - can't open file: C:\Documents and Settings\Administrator.TPSONLINE\Local Settings\Temp\1\mmc02E58B32.xml (WIN32 32: The process cannot access the...
Zahid.Haseeb | 04 Nov 2009 | 5 comments

Today in my BLOG i would like to discuss the ""socket write failed(24)"" shown in the Activity Monitor in the result of a failed backup job

ENVIRONMENT

Server
Windows 2003 Server R2
Netbackup Server 6.5

Client
Windows2003 Server R2

PROBLEM

I was facing the error socket write failed(24)  when i initiated a job and faced the mentioned error in Activity Monitor

RESOLUTION 

I simply changed the property values from Enable to Disable from the NIC card properties. You can see the below picture for your help

untitled.JPG 

Forum DIscussion

...