Is backupexec reaaly this bad ? Several Issues...

[Datong]

I am using BE9.1 for Windows 2003 Servers.
1) When I install the remote agent to the Netware server the info box says install failed but gives not reason and the log file is not updated, but when I check the server the files have installed and seem to be running ok ?
2) I installed the RA and the AOFA agents to the remote Windows servers and rebooted, but there doesn't seem to be a way to check that the AOFO agent is running ?
3) After installing the latest service pack 2 I ran the update check from the web, it says that there are no fixes to be installed for my product then proceeds to list 3 patches including the one I just applied that need to be downloaded and installed. WTF is going on ?
4) When connecting to remote servers whilst creating a backup job does BE ask me for an accounr with sufficient rights to the object when I am the DC controller and have all the f****** rights I need !!!
5) How can I tell which fixes have been applied and are working ?

If anyone can shed some light on these questions I would be most grateful.
Thanks

 

[Datong]

Oh and one I forgot,

if I install the patches ie SP2 and it updates my installation files, and then I must re-install the RA and AOFA agents to the servers does it recognise the new drivers and install them or does it use the old drivers as it asked me for the location of the original CD? and seemed to install them from there.
Maybe there is someone at Veritas listening who might wish to impart some knowledge to its confused users.

 

[ymeq123]

I've just gone through some of this.

1. Can't really help with the Netware issue but for the remote Windows agent install BE leaves a log file called bkupinst.log. It has the log of the installation and would have the failure reason in it. I do not know if or where the NW server would have this file.

2. If you open the Services MMC from inside Administrative Tools there should be a service called Backup Exec Remote Agent for Windows. It will show you if it is running.

3. From the Veritas Update page I believe it is showing you the patches you have already installed. I just ran this and it said on the web page that I had no updates and also showed "Installed patches"

4. It is asking you what user ID it should use to login to the remote server. That is very necessary in larger organizations where the are many admins, backup operators and support personnel who may need to specify different user ID's for different servers and so on and so on........

5. I just ran the Vertias Update and this is what I got.

Product: VERITAS Backup Exec for Windows Servers, Version 9.1

No current updates are available for this product.

Installed Updates:

It then showed my installed patches. You should be seeing the same type of info.


6. For the update of the remote windows agents you select Tools --> Serial numbers and Installation from inside of Backup Exec, Turn off local install and turn on Remote Install. BE should install the updated remote agents from your updated BE installation.


Hope this helps (and made sense!)


Good luck!

 

[SQLBill]

4) When connecting to remote servers whilst creating a backup job does BE ask me for an accounr with sufficient rights to the object when I am the DC controller and have all the f****** rights I need !!!

You have the rights, but does the Backup Exec JOB AGENT service, which WILL RUN the job, have the proper permissions or is it just running as local admin?

-SQLBill

Posting advice: FAQ481-4875

 

[ymeq123]

Good point Bill!

 

[Datong]

Thanks for the replies.
SQLBill - yes the agents do have the right permissions, the problem only seeme to occur when I want to select the MS exchange mailboxes to be backed up. Even though I can check the other devices/options on the same server it always asks for a use with permissions to the mailboxs. I have checked all the rights and permissions on the exchange box but as I said I am the DC controller anyway. What seems to be happening is that the (former) administartors account is the only one BE will accept. I have tried adding and changing the access account but no joy. Its just lucky they kept his account and password. Does this mean I may have to re-install BE to get round this. (May not be a bad idea anyway as the whole thing is in a bloody mess!)

Thanks all for your help.

 

[steveot]

So the issue seems to be mostly Exchange.
The backup exec service account must a mailbox that is visible in the GLA.
Here are two technotes of intrest.

http://seer.support.veritas.com/docs/266074.htm

http://seer.support.veritas.com/docs/249456.htm

As far as the fixes I would use the Veritas Direct assist - its free and will query the right information.

Backup Exec 10.x the fixes/patches intalled are listed in Help-about