Clustered installation of Netbackup 7.1 fails!

[Fred2010]

Hi all,

I have a problem with a fresh install of the new Netbackup 7.1 on our cluster.

We have the following setup:

3 x Windows 2008 R2 SP1 x64 Enterprise server (Fully patched)
Installed Veritas Storage Foundation HA 5.1 SP2

When I install Netbackup 7.1 on top of the VSF HA cluster, according to the install process everything is fine & dandy. When I check the cluster administrator however, I notice that the most important resource of all is missing: The NETBACKUP one!

Furthermore, the installer did not install ANY software on the middle node (Even though it reported as succesful at the end of the install)

I've removed everything and reinstalled again, this time only installing the FIRST node only, hoping that would solve the problem, but unfortunately to no avail :(

I've included a screenshot to show what was created in the cluster administrator, to show what is missing (Indictaed by the red ?). Because of the missing part NONE of the Netbackup Services get started!

I've opened an urgent case with Symantec yesterday (Case 414-229-690).

Today, again, I am trying to get in contact with support now, but I figure maybe posting my problem here might resolve the issue quicker...

Hope somebody has some suggestions...

Fred

[Marianne]

I hope that you managed to get through to an engineer by now...

First thing that you need to check with them is Compatibility:

The latest SF/HA version that is listed in the Cluster Compatibility Guide is 5.1 SP1 AP1 (no 5.1 SP2) : http://www.symantec.com/docs/TECH126902

Not only was the NetBackup resource not created, the service group was configured for a single node only (APP0401).

There are so many things that can go wrong with this whole processes - we will need to understand all the steps that were performed - right from preparation for SF/HA installation (heartbeats, storage device compatibility, etc) installation steps, initial cluster config, plus preparation for NBU install (shared disk, user priveleges, etc) selections and input throughout the installation processes. After selecting/specifying cluster nodes from Available Nodes, did the NBU system and license check complete successfully for each node? Input in Cluster Setting screens?
After you clicked  Install, did you see a dialog box that showed the installation progress for each computer?

Do you have a tasklist/worksheet that you have used for preparation/installation that you can share with us?

The installation log might also be useful - located %ALLUSERSPROFILE%\Symantec\NetBackup\InstallLogs\
Note:  Each computer that you selected for installation contains its own installation log file.

Also in install guide:

MSCS and VCS clusters
Under normal circumstances, cluster configuration is one of the final steps when you install NetBackup in a cluster. If this step is not done or does not complete successfully, you can use the bpclusterutil command from the active node to perform this step.
For information on how to run bpclusterutil, see the NetBackup High Availability Administrator's Guide.
 

[Fred2010]

Hi Marianne,

Thanks for your reply... I did get through to support in the end and we managed to get it installed (But not working!)

I've reinstalled a fresh image on the machines, and tried a fresh install of node APP0401

We indeed did a single node Cluster install, to first solve the 'local' problems (After which I'd install the other two nodes, joining the existing cluster)

But it got even worse: Now it even can't install the LOCAL node!!! I don't think the SFW HA 5.1 SP2 is the issue (No major new stuff in there)

I think it is some rights issue with Windows 2008 R2 that is stopping me now (Although I have no idea what...)

- I am Local Administrator
- I run the installer with RUN AS ADMINISTRATOR
- The installation software is LOCAL on the very same node I am installing (On the desktop)

Yet still it fails during the pushing of the software (See BEPUSHES.LOG below)...

I Googled the error, and get someone with Backup Exec having the exact same errors that are in the log below. Unfortunately their solution doesn't work for me...

Hope you can help with this...

Fred

1:(03/27/11 16:25:21)->Log Started: ID:1
1:(03/27/11 16:25:32)->Creating destination connection: APP0401,
1:(03/27/11 16:25:32)->Connecting to local WMI service...
1:(03/27/11 16:25:32)->Connecting: \\.\root\cimv2, (null), (null)
1:(03/27/11 16:25:32)->Connecting to local registry...
1:(03/27/11 16:25:32)->Connecting: \\.\root\default, (null), (null)
1:(03/27/11 16:25:32)->Querying remote drives...
1:(03/27/11 16:25:32)->Creating remote install directory...
1:(03/27/11 16:25:32)->Creating folder: C:\BEW-ED996622E08842C5B8CB3BDF3A480994
1:(03/27/11 16:25:32)->Creating process: cmd.exe /c md C:\BEW-ED996622E08842C5B8CB3BDF3A480994
1:(03/27/11 16:25:34)->Creating share: BEW-ED996622E08842C5B8CB3BDF3A480994, C:\BEW-ED996622E08842C5B8CB3BDF3A480994, BEWPush Temporary Directory
1:(03/27/11 16:25:34)->Creating security descriptor...
1:(03/27/11 16:25:34)->Creating security DACL...
1:(03/27/11 16:25:35)->Establishing connection to network resource: \\APP0401\BEW-ED996622E08842C5B8CB3BDF3A480994,
1:(03/27/11 16:25:35)->Connection has been established: \\APP0401\BEW-ED996622E08842C5B8CB3BDF3A480994, (null)
1:(03/27/11 16:27:47)->Getting server information...
1:(03/27/11 16:27:47)->ERROR: Code(-2147417848): executing query: select * from Win32_OperatingSystem
1:(03/27/11 16:27:47)->Pushing files: C:\Users\ADM-60~1\AppData\Local\Temp\NBStaging\x64\NBUPush_INFRA_APP0401.lst
1:(03/27/11 16:27:47)->Reading push files: C:\Users\ADM-60~1\AppData\Local\Temp\NBStaging\x64\NBUPush_INFRA_APP0401.lst
1:(03/27/11 16:27:47)->Adding push file: \NBStaging\x64\Bkupinst.xsl, \temp\nbusetup\Bkupinst.xsl, 1
1:(03/27/11 16:27:47)->Adding push file: \NBStaging\x64\data1.cab, \temp\nbuSetup\data1.cab, 1
1:(03/27/11 16:27:47)->Adding push file: \NBStaging\x64\NBUPush_INFRA_APP0401.resp, \temp\nbuSetup\NBUPush_INFRA_APP0401.resp, 1
1:(03/27/11 16:27:47)->Adding push file: \NBStaging\x64\setup.exe, \temp\nbuSetup\setup.exe, 1
1:(03/27/11 16:27:47)->Adding push file: \NBStaging\x64\strpimon.exe, \temp\nbuSetup\strpimon.exe, 1
1:(03/27/11 16:27:47)->Adding push file: \NBStaging\x64\VxLogServer.exe, \temp\nbuSetup\VxLogServer.exe, 1
1:(03/27/11 16:27:47)->Adding push file: \NBStaging\x64\VxSetup.ini, \temp\nbuSetup\VxSetup.ini, 1
1:(03/27/11 16:27:47)->Adding push file: \NBStaging\x64\Symantec NetBackup.msi, \temp\nbuSetup\Symantec NetBackup.msi, 1
1:(03/27/11 16:27:47)->Pushing files...
1:(03/27/11 16:27:47)->Disconnecting from network resource: \\APP0401\BEW-ED996622E08842C5B8CB3BDF3A480994
1:(03/27/11 16:27:47)->Disconnected from network resource: \\APP0401\BEW-ED996622E08842C5B8CB3BDF3A480994
1:(03/27/11 16:27:47)->Deleting remote share...
1:(03/27/11 16:27:47)->Connecting to local WMI service...
1:(03/27/11 16:27:47)->Connecting: \\.\root\cimv2, (null), (null)
1:(03/27/11 16:27:47)->Connecting to local registry...
1:(03/27/11 16:27:47)->Connecting: \\.\root\default, (null), (null)
1:(03/27/11 16:27:50)->Deleting remote share...
1:(03/27/11 16:27:50)->Deleting entire folder: C:\BEW-ED996622E08842C5B8CB3BDF3A480994
1:(03/27/11 16:27:50)->Deleting entire folder by api: C:\BEW-ED996622E08842C5B8CB3BDF3A480994
1:(03/27/11 16:27:50)->Deleting folder files: C:\BEW-ED996622E08842C5B8CB3BDF3A480994
1:(03/27/11 16:27:50)->Getting sub folders: C:\BEW-ED996622E08842C5B8CB3BDF3A480994
1:(03/27/11 16:27:50)->Deleting folder: C:\BEW-ED996622E08842C5B8CB3BDF3A480994
1:(03/27/11 16:27:50)->Querying remote drives...
1:(03/27/11 16:27:50)->Creating remote install directory...
1:(03/27/11 16:27:50)->Creating folder: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:27:50)->Creating process: cmd.exe /c md C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:27:52)->Creating share: BEW-A8E24D4A9C6D4F68B783325F484A6E29, C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29, BEWPush Temporary Directory
1:(03/27/11 16:27:52)->Creating security descriptor...
1:(03/27/11 16:27:52)->Creating security DACL...
1:(03/27/11 16:27:52)->Establishing connection to network resource: \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29,
1:(03/27/11 16:27:52)->Connection has been established: \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29, (null)
1:(03/27/11 16:27:52)->Copying files to machine: APP0401
1:(03/27/11 16:27:52)->Creating directory: \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp
1:(03/27/11 16:27:52)->Creating directory: \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\nbusetup
1:(03/27/11 16:27:52)->Copying file: C:\Users\ADM-60~1\AppData\Local\Temp\\NBStaging\x64\Bkupinst.xsl, \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\nbusetup\Bkupinst.xsl, 1
1:(03/27/11 16:27:52)->Copying file: C:\Users\ADM-60~1\AppData\Local\Temp\\NBStaging\x64\data1.cab, \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\nbuSetup\data1.cab, 1
1:(03/27/11 16:27:53)->Copying file: C:\Users\ADM-60~1\AppData\Local\Temp\\NBStaging\x64\NBUPush_INFRA_APP0401.resp, \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\nbuSetup\NBUPush_INFRA_APP0401.resp, 1
1:(03/27/11 16:27:53)->Copying file: C:\Users\ADM-60~1\AppData\Local\Temp\\NBStaging\x64\setup.exe, \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\nbuSetup\setup.exe, 1
1:(03/27/11 16:27:53)->Copying file: C:\Users\ADM-60~1\AppData\Local\Temp\\NBStaging\x64\strpimon.exe, \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\nbuSetup\strpimon.exe, 1
1:(03/27/11 16:27:53)->Copying file: C:\Users\ADM-60~1\AppData\Local\Temp\\NBStaging\x64\VxLogServer.exe, \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\nbuSetup\VxLogServer.exe, 1
1:(03/27/11 16:27:53)->Copying file: C:\Users\ADM-60~1\AppData\Local\Temp\\NBStaging\x64\VxSetup.ini, \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\nbuSetup\VxSetup.ini, 1
1:(03/27/11 16:27:53)->Copying file: C:\Users\ADM-60~1\AppData\Local\Temp\\NBStaging\x64\Symantec NetBackup.msi, \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\nbuSetup\Symantec NetBackup.msi, 1
1:(03/27/11 16:27:57)->Starting Install: \temp\NBUSetup\strpimon.exe /k SOFTWARE\Veritas\BU\STATUS /i "setup.exe -s /RESPFILE:'NBUPush_INFRA_APP0401.resp'"
1:(03/27/11 16:27:57)->Connecting to local WMI service...
1:(03/27/11 16:27:57)->Connecting: \\.\root\cimv2, (null), (null)
1:(03/27/11 16:27:57)->Connecting to local registry...
1:(03/27/11 16:27:57)->Connecting: \\.\root\default, (null), (null)
1:(03/27/11 16:28:00)->Creating process: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29\temp\NBUSetup\strpimon.exe /k SOFTWARE\Veritas\BU\STATUS /i "setup.exe -s /RESPFILE:'NBUPush_INFRA_APP0401.resp'"
1:(03/27/11 16:28:09)->Cleaning up push install...
1:(03/27/11 16:28:09)->Deleting registry key: -2147483646, SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Install\PushStatus
1:(03/27/11 16:28:09)->ERROR: Code(-2147417848): getting parameter object: StdRegProv, DeleteKey
1:(03/27/11 16:28:09)->Disconnecting from network resource: \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:09)->Disconnected from network resource: \\APP0401\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:09)->Deleting remote share...
1:(03/27/11 16:28:09)->Connecting to local WMI service...
1:(03/27/11 16:28:09)->Connecting: \\.\root\cimv2, (null), (null)
1:(03/27/11 16:28:09)->Connecting to local registry...
1:(03/27/11 16:28:09)->Connecting: \\.\root\default, (null), (null)
1:(03/27/11 16:28:12)->Deleting remote share...
1:(03/27/11 16:28:12)->Deleting entire folder: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:12)->Deleting entire folder by api: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:12)->Deleting folder files: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:12)->Getting sub folders: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:12)->Deleting entire folder by api: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp
1:(03/27/11 16:28:12)->Deleting folder files: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp
1:(03/27/11 16:28:12)->Getting sub folders: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp
1:(03/27/11 16:28:12)->Deleting entire folder by api: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup
1:(03/27/11 16:28:12)->Deleting folder files: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup
1:(03/27/11 16:28:12)->Deleting file: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup\bkupinst.xsl
1:(03/27/11 16:28:12)->Deleting file: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup\data1.cab
1:(03/27/11 16:28:13)->Deleting file: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup\nbupush_infra_app0401.resp
1:(03/27/11 16:28:13)->Deleting file: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup\setup.exe
1:(03/27/11 16:28:13)->Deleting file: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup\strpimon.exe
1:(03/27/11 16:28:13)->Deleting file: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup\symantec netbackup.msi
1:(03/27/11 16:28:13)->Deleting file: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup\vxlogserver.exe
1:(03/27/11 16:28:13)->Deleting file: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup\vxsetup.ini
1:(03/27/11 16:28:13)->Getting sub folders: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup
1:(03/27/11 16:28:13)->Deleting folder: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp\nbusetup
1:(03/27/11 16:28:13)->Deleting folder: c:\bew-a8e24d4a9c6d4f68b783325f484a6e29\temp
1:(03/27/11 16:28:13)->Deleting folder: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:13)->Deleting remote share...
1:(03/27/11 16:28:13)->Connecting to local WMI service...
1:(03/27/11 16:28:13)->Connecting: \\.\root\cimv2, (null), (null)
1:(03/27/11 16:28:13)->Connecting to local registry...
1:(03/27/11 16:28:13)->Connecting: \\.\root\default, (null), (null)
1:(03/27/11 16:28:16)->Deleting remote share...
1:(03/27/11 16:28:16)->ERROR: Code(-1): cleaning push install: could not delete folder share
1:(03/27/11 16:28:16)->Deleting entire folder: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:16)->Deleting entire folder by api: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:16)->Deleting folder files: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:16)->ERROR: Code(-2147217406): executing query: ASSOCIATORS OF {Win32_Directory.Name='C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29'} Where ResultClass = CIM_DataFile
1:(03/27/11 16:28:16)->Deleting entire folder by process: C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:16)->Creating process: cmd.exe /c rmdir /S /Q C:\BEW-A8E24D4A9C6D4F68B783325F484A6E29
1:(03/27/11 16:28:16)->Push install cleaned.
 

[Nuno_Grave]

I have the same problem. but I associated the problem to some changes in windows and in vcs.

 How is a new backup server I reinstalled the two nodes.

Tomorrow I will try reinstalling. Do you have any useful information they can share or is a widespread problem.

[Marianne]

Probably an overkill, but for each SFW/HA installation that I have assisted with, I have always requested a domain admin to login and perform the installation as this account. Also verify that this account has local admin rights on each node.

I have not yet tried NBU 7.1 cluster installation - my last involvement was 6.5 with something like SFW/HA 5.0.

In what state is VCS?  Did initial cluster config complete successfully?

Please post output of:

gabconfig -a

hastatus -sum

[Fred2010]

Hi Marianne,

Please read my response to Nuno above...

I got the cluster working (Although I am not fully happy with it yet...). I am in the process of a reinstall (This time nice & clean).

Will post results tomorrow...

Thanks

Fred

[Fred2010]

Hi Nuno,

Actually I have some news:

I've managed to do the install after a tip from support and some trials by myself:

- If you do not use IPv6 disable it fully (Not just unbinding it from your network adapters, but in registry). Windows 2008 leaves the IPv6 running even if it is unbound:

Try a PING HOST (Do it on the same HOST you are pinging, so PING itsself) and you'll see it is still running, as the output won't make any sense...

Now apply the registry change (Use the 0xffffffff one) in & boot the host:

http://support.microsoft.com/kb/929852

Then try PINGing again and you'll see that made a change. Make sure you do that on ALL hosts in the cluster & boot them

- I found the in this version of Netbackup it won't even INSTALL on the nodes if you don't use FQDN (Although 6.5.x I could use short names). So use FQDN for every entry of a HOSTNAME (It won't let you in one screen, coz VCS does not support FQDN names, but it will warn you for it and change it back)

- On all nodes, I've added the nodenames (Including the virtual one) to the HOSTS file (C:\Windows\System32\Drivers\ETC\HOSTS)

- Be sure you have plenty rights (Domain Admin if possible)

- Always start the installer with RUN AS ADMIN (Even if you are logged in as one)

- Have the install software locally on the machine, and install from that folder

After these changes I did a NODE-BY-NODE install (Instead of installing all at the same time). So I installed one, then onto the next, (Joining the existing cluster) etc. Each time I worked from the node I am installing.

The first few object in VCS are created when you press the CLUSTER CONFIGURATION button, but the Netbackup object gets made after the FIRST node is fully complete and online. Like Marianne says: The Netbackup object of the cluster is almost the last thing the installer does...

I have a working Cluster now, but...:

In the MASTER SERVER PROPERTIES I still don't see which node is active and the clustername. Also the double COGWHEEL is missing on the Virtual Hostname in the overview window where you see all nodes.

As too much stuff has happened om my servers for my liking, I will also reinstall tomorrow...

Hope this helps you further buddy!

Fred

[Fred2010]

Just finished doing a reinstall, whilst installing ALL 3 nodes at the same time...

Unfortunately, I get exactly the same error...

Seems to me there is a serious error in the installer (That still reports everything is fine, by the way).

I've collected new logs and sent them off to Symantec with the question to escalate this problem to backline engineering...

Fred

[Dan_Sutherland]

Hello.  The NetBackup installation team has been involved with this support case, and the support engineer recently made us aware of this forum thread.

There were significant changes surrounding cluster installations introduced with the 7.1 Windows package.  As Marianne indicates, the process of installing and configuring a cluster involves a number of steps.  Before NetBackup 7.1, the cluster configuration step was exercised through a pop-up dialog that would be displayed at the conclusion of the install.  You would click OK, and wait for a period of time while these operations happened behind the scenes.  If any one of the steps was insuccessful, you would be forced to uninstall the entire product, address any cluster or environment issues that may have been responsible for the installation failure, and reattempt the installation.

With 7.1, we attempt to validate the readiness of a cluster at the soonest point possible.  This is expressed through the modified cluster settings dialog in the setup wizard.  You are now forced to run a Cluster Configuration step that performs preliminary cluster configuration operations.  If anything goes wrong, you have an opportunity to correct it before the installation begins.  The intent of this was to save users from having to uninstall and reinstall in the event that a failure occurs during cluster configuration.

My interpretation of the issue is that there are two unique problems.  One is that following a successful cluster installation (as reported by the installers), the NetBackupVCS component is missing from the NetBackup cluster group in the VCS console.  My understanding is that this issue is currently being investigated by our cluster team.  This issue has been reported previously, but has been seen on an extremely intermittent basis.

The second issue (or symptom of the issue) is that the cogwheel icon is missing from the Master (virtual) Server.  I believe the cluster team is actively investigating this as part of the support case.

I'm sorry to hear that we're having issues like this with our 7.1 packages.  Much time and effort was dedicated during development of 7.1 to simplify the cluster installation process on Windows.  The installation team will be monitoring this forum thread and the associated support case to record pain points.  Any suggestions you have for improving the manner in which clusters are installed will be considered.

Thanks much,

Dan

[Fred2010]

Hi Dan,

You have correctly summarized the problems I have seen during my attempts of installations

I've seen several 'versions' of the FIRST problem:

1) One node getting skipped Entirely during installation + Netbackup object missing
2) Three nodes get installed, but Netbackup object missing
3) Three nodes get installed, Netbackup object is created, but not linked to other cluster objects
4) Three nodes get installed, Netbackup object is created/linked, but is missing parameters (Like Clustername)
5) Three nodes get installed, Netbackup object is created/linked and seems correct

Each of these installations reported as being 100% succesful

On each of these attempts, I've noticed the SECOND problem (Which seems to be in the presentation/GUI only?):

1) Double Cog wheel is missing from the activity monitor overview
2) Masterserver properties in Netbackup do not show Active Node & Clustername

To me the cluster configuration is done in 2 steps:

Step 1: Before any software is installed, the cluster configuration is checked during the installation (Button). Here it created ALL, but the last object

Step 2: At the end of the installation (After Software push),  the Netbackup object gets created.

I think the issue is only in this LAST step...

As for the presentation issue: No idea why that is happening...

regards,

Fred

[Dan_Sutherland]

Hello, Fred.  Thanks for the quick reply.

I meant to elaborate on your earlier multi-node problems and neglected to in my initial response.  The bulk of the cluster configuration occurs on the active node - that is, the node where the shared disk is online.  We document that any clustered installation should be launched from the active node itself.  This is the only node where database operations (creation and upgrade) are performed, as the database resides on the cluster shared disk.  For the other nodes (hereafter referred to as inactive nodes), very little cluster configuration takes place.  Certain registry values are updated on the inactive nodes to indicate they belong to a NetBackup cluster.  Your earlier indication that the installation on the inactive nodes appeared to be incomplete could be expected behavior.  The installation on the inactive nodes is expected to complete first, given that the lengthier database-related steps occur on the active node.

"One node getting skipped Entirely during installation" - this is troubling.  Are we certain the host was included in the list of install targets?  The summary screen report saved to %ALLUSERSPROFILE%\Symantec\NetBackup could confirm this for us.

Thank you,

Dan

[Fred2010]

Hi Dan,

One node not receiveing any software happened only once actually.

For the last installation, I actually made some movie files of the cluster software installation and the Netbackup installation as well...

During this last installation, the cluster object got created and linked as it should. I have no idea whether any subsequent installations will be OK as well

Only problem during this last installation that is still there, are the missing Cogwheels and the Masterserver properties being incorrect.

Today, Chirag Patel from Symantec Engineering is researching this issue and has collected WINGUI logs.

Whether this also resolves the installation issue of the Netbackup object not getting created (correctly) I don't know.

Please feel free to request the Movie files that I made of the installation process. They should be attached to the case...

Regards,

Fred

[Dan_Sutherland]

Hello, Fred.  Yes, I saw the movies.  The support engineer provided a link to them.  Thanks much for providing those, they answered many questions and were quite helpful.  The install team will be monitoring Chirag's findings.  We hope to provide you with a solution in the near future, thanks for your patience thus far.

- Dan

[Dan_Sutherland]

The service request has been handled internally, and my understanding is that the issue has been resolved.  If this isn't the case, please let us know.

Thank you,
Dan

[Michael_G_Ander]

We have a similar problem on MSCS 2008 R2, when upgrading from Netbackup 7.0.1 to 7.1.

Only the ip address and name cluster resource is created. After that the installation rolled back, but that means the not even the 7.0.1 works any more

[CRZ]

Hi Michael,

This thread is over six months old.  Normally I'd recommend you start a new thread, but we should probably skip that step and go right to "please open a support case" if you haven't already.  I don't think you'll be able to resolve your cluster issues here on Connect.

[Michael_G_Ander]

I know, but often get faster/better reponse here than thorugh a support case