I can't install CASO.

[takaratta]

Now I evaluate BE2010 and Central Admin Server Option.

I prepared two servers. One is for central administration server, and another is for managed media server.

I use VMware for evaluation.

1. I installed Windows Server 2008 to Virtual Machine.

2. I changed Network Setting. (IP Adress, Computer Name, Join Domain, etc...)

3. I installed BE2010 (Include Deduplication Option).

About 1 - 3, I did same process for Server #1 and Server #2.

4. In additional, I installed Central Admin Server Option to Server #1.

        -> How to) "Tool" - "Install Options and License Keys on this Media Server"

5. I set as Managed Media Server to Server #2. But it is failed.

    Server #2 cannot find BKUPEXEC database of Server #1.

        -> How to) "Tool" - "Set Central Administration Server"

For your information,

  In my network, Firewall is disabled.

  I worked by Domain Administration User.

[Sush---]

First please check if you are able to ping Server#1 from Server#2 and vice versa.

 Then perform the UDL test from server#2 to connect to the SQL instance on Server#1.

Refer to this technote to perform the UDL test

http://www.symantec.com/docs/TECH24708 : How to perform a quick test connection to the Backup Exec SQL instance

Thanks,

-Sush...

[CraigV]

Hi there,

Using that method to join a CASO server, you need to restart your services manually.

If this doesn't work after a service restart, go into BEutility, and right-click your server. If your server hasn't joined the CASO server correctly, it will still allow that option.

If it has, it is joined out.

Another thing...a CASO environment allows you to store your catalogs and DB information in a number of ways. Where are you locating that information? Distributed between the 2 BE servers? Locally on the MMS, or centralised on the CASO?

I have also seen instances (I get it ALL the time) where the DB is located on the CASO, and not locally on the MMS itself. On a slow link it does cause DB disconnects. The only way around this is to relocate that information, using BEutility.exe, back to the MMS and making a registry change.

Thanks!

[takaratta]

> Refer to this technote to perform the UDL test
>
> http://www.symantec.com/docs/TECH24708 : How to perform a quick test connection to the Backup Exec SQL instance

I checked this UDL test.

Server #1 connected to Server #1 Database.

Server #2 connected to Server #2 Database.

But,

Server #1 connected to Server #2 Database.

Server #2 connected to Server #1 Database.

I checked the Microsoft Component Checker.

But, WinSV2008 don't exist in selection list.

But, I found the database component (DBNETLIB.DLL, SQLSRV32.DLL, SQLSRV32.RLL).

I run Backup Exec on Server #1 (CA Server).

I can find 'Media Server' tab.

I run BEUtility on Server #1 (CA Server).

I selected 'All Media Servers'.

Now there is one server name in right paine.

I right-clicked on the server name,

  - Set Central Administration Server

    -> This is disabled.

  - Remove Central Administration Server

    -> This is disabled.

  - Move Managed Media Server

  - Disable Communications with the Managed Media Server

    -> This is disabled.

  - Enable Communications with the Managed Media Server

    -> This is disabled.

  - Change Catalog Location...

    -> This is disabled.

  - Move Device and Media Data to Managed Media Srever

    -> This is disabled.

  - Move Device and Media Data to Central Administration Server

    -> This is disabled.

[CraigV]

...if Server1 is your CASO server, you cannot add it to itself. Those options will be greyed out. You need to do this on the MMS server...the server you want to add to the CASO. Please check there...

[Sush---]

I run Backup Exec on Server #1 (CA Server).

I can find 'Media Server' tab.

This confirms that the Server#1 is correctly installed as CASO server. So we need not worry about it.

Need to check why Server#2 can not connect to Server#1 as Managed Media server'

 Please check the BKUPINST.htm file o the Server#2 to check if there are any more error which will help to resolve.

Thanks,

-Sush...

[takaratta]

I tried to install as Managed Media Server to Server #2 (CASO).

But, it is failed.

The following message in 'Progress of the Operation'(!?) window.

My language of BE is not English.

I translate a displayed message.

[Status]

Change this server to Managed Media Server.

This server accessed a Registry Key of Server #2 which selected and failed to get version number of Backup Exec.

An error occurred by operation with Server #2 as media server of Central Administration Server (Server #1).

And where is 'BKUPINST.htm file'?

[CraigV]

...might be time to do a repair installation of BE on Server2. Once done, try again!

You can do a search for that file to locate it.

[takaratta]

I'm sorry. I made a mistake.

[Message]

Change this server to Managed Media Server.

This server accessed a Registry Key of Server #1 (CASO) which selected and failed to get version number of Backup Exec.

An error occurred by operation with Server #2 as media server of Central Administration Server (Server #1).

[takaratta]

I did a repair installation of BE for Server #2.

And I run BEUtility and change to MMS. But, it was failed.

Is the security that was strengthened for WinSV2008 problem, or not?

[CraigV]

Mmm...that shouldn't be an issue. I have a Windows Server 2008 R2 x64 VM acting as my CASO and Windows Server 2003 + Server 2008 R2 x64 servers connect in, so that isn't an issue.]

If security WERE an issue it might be because of a firewall or AV blocking ports or activity.

Check for those, and if need be, uninstall the CAS option from your CASO server, and then reinstall it before trying to add that MMS back.

[takaratta · Accepted solution]

I seem to be unstable in a network of VMware.

My environment is ...

  Host OS is Windows 7 32 bit version on Mobile PC. CPU is intel Core i5 U560.

  Guest OS is Windows Server 2008 R2 64 bit version.

There may be a problem in environment.

I try it in another environment.

I close this thread immediately because I cannot prepare for environment.