Script for updating OpsCenter server entry on multiple Backup domain
I have to add new OpsCenter server entry in matser server properties for 500+ Backup domains. Could you please share if any script or easiest way to update the same instead of manully logging on each master and update through GUI (Hostproerties --> servers --> OpsCenter Servers).
OpsCenter WebServer Service Not Starting
I've been tasked to install OpsCenter onto a VM. The install completed successfully, but when I try to connect to the applicaiton I'm unable to. I've checked the services, and everything except the OpsCenter WebServer Service is running. OpsCenter is installed and running in another environment. I've compaired the configuration in both VMs and I've not been able to find any differences at this time. This is for OpsCenter 7.5 running on a VM Windows 2008. In the OpsCenterWebSrvService log I did find this: Command to Run: "D:\Program Files\Symantec\OpsCenter\gui\WEBSERVER\bin\catalina.bat" run Executed in D:\Program Files\Symantec\OpsCener\gui\ Process : "D:\Program Files\Symantec\OpsCenter\gui\WEBSERVER\bin\catalina.bat" run Created with Process ID: 288 ---- Command output log --- Error:Process exited with error code = 255 CProcessMgmt[Exit]::CreateProcess CProcessMgmt[Exit]::ApplyEnvValuesAndLaunchProcess The process has been either terminated explicity or the process itself threw and exception & thus terminated CProcessMgmt[Exit]::StartProcess StartProcess API call failed CServiceWrapper[Exit]::StartProcess CServiceWrapper[Entry]::StopService CServiceWrapper[Entry]::StopService- OpsCenterWebServer Anyone have any ideas?
BUG: OpsCenter 7.1 Installation (error: incorrect format: unknown tag)
New installation of OpsCenter 7.1 on Red Hat Enterprise Linux Server release 6.0 (Santiago). Problem: During installation of OpsCenter 7.1 you may receive the below output and error messages: ------------------------------- Performing configurations on <server name> Setting environment variables sh -x error: incorrect format: unknown tag/SYMCOpsCenterServer/bin/configureEnv.sh -jreHome error: incorrect format: unknown tag/latest -platform Linux_x86_64 -serverInstallDir error: incorrect format: unknown tag/SYMCOpsCenterServer -guiInstallDir error: incorrect format: unknown tag/SYMCOpsCenterGUI -atServerInstallDir error: incorrect format: unknown tag/VRTSat/ -installationType 2 -configDir error: incorrect format: unknown tag/SYMCOpsCenterServer -opsCenterHostName whqnbu01p -isClustered 2 sh -x error: incorrect format: unknown tag/SYMCOpsCenterGUI/bin/configureEnv.sh -jreHome error: incorrect format: unknown tag/latest -platform Linux_x86_64 -serverInstallDir error: incorrect format: unknown tag/SYMCOpsCenterServer -guiInstallDir error: incorrect format: unknown tag/SYMCOpsCenterGUI -atServerInstallDir error: incorrect format: unknown tag/VRTSat/ -installationType 2 -configDir error: incorrect format: unknown tag/SYMCOpsCenterServer -opsCenterHostName whqnbu01p -isClustered 2 Copying war file Setting up GUI error: incorrect format: unknown tag/SYMCOpsCenterGUI/bin/goodies/configureGUI.sh error: incorrect format: unknown tag/SYMCOpsCenterGUI/bin/goodies/createSSLStore.sh error: incorrect format: unknown tag/SYMCOpsCenterGUI/bin/goodies/configureWSDefaults.sh error: incorrect format: unknown tag/SYMCOpsCenterGUI/bin/goodies/configurePorts.sh -httpPort 80 -httpsPort 443 -shutdownPort 8105 -keystoreFile error: incorrect format: unknown tag/SYMCOpsCenterGUI/Security/keystore error: incorrect format: unknown tag/SYMCOpsCenterGUI/bin/goodies/configureMemory.sh Setting up PBX Setting up links Setting PostInstall Configurations error: incorrect format: unknown tag/SYMCOpsCenterServer/bin/postinstall.sh Setting up the Database error: incorrect format: unknown tag/SYMCOpsCenterServer/bin/configureDb.sh -dbDataFileLocation "/var/symantec/OpsCenterServer" -dbTempFileLocation "/var/symantec/OpsCenterServer" -clusterMode "2" Creating Links for dbsrv11 and dbsrv11.lic Configuring VxAT Updating VxAT parameters error: incorrect format: unknown tag/SYMCOpsCenterServer/bin/configureAt.sh -installationType 2 -vxssHostname localhost -vxssPort 2821 -vxssPbxPort 1556 -vxssUsername admin -vxssPassword Vxadmin -vxssDomain broker ------------------------------- --Installation log file: (bold text) 9:40:41 exec LANG=C /bin/rpm -q VRTSatServer 2>&1 9:40:41 VRTSatServer-4.3.46.0-0.i386 9:40:41 exit=0 9:40:41 exec LANG=C /bin/rpm -q --queryformat '%{INSTALLPREFIX}' VRTSatServer 2>&1 9:40:41 error: incorrect format: unknown tag 9:40:41 exit=0 9:40:41 exec LANG=C /bin/ls /var/VRTSat/.VRTSat/profile/VRTSatlocal.conf 2>/dev/null 9:40:41 /var/VRTSat/.VRTSat/profile/VRTSatlocal.conf 9:40:41 exit=0 9:40:41 exec LANG=C /bin/grep Mode "/var/VRTSat/.VRTSat/profile/VRTSatlocal.conf" 2>&1 9:40:41 "Mode"=dword:00000000 9:40:41 exit=0 9:40:41 Mode is [0] 9:40:41 exec LANG=C /bin/ls /etc/vx/VRTSnom/InstallPath 2>/dev/null 9:40:41 9:40:41 exit=2 9:40:41 exec LANG=C /bin/rpm -q VRTSccsvs 2>&1 9:40:41 package VRTSccsvs is not installed 9:40:41 exit=1 9:40:41 exec LANG=C /bin/ls /etc/SuSE-release 2>/dev/null 9:40:41 9:40:41 exit=2 9:40:41 exec LANG=C /bin/ls /etc/redhat-release 2>/dev/null 9:40:41 /etc/redhat-release 9:40:41 exit=0 Cause: rpm querytag INSTALLPREFIX is no longer a valid tag with rpm-4.8.0-12 or greater. Fix: Either Symantec will update the below recommendation with a patch release or you'll have the edit the file manually by change the querytag from INSTALLPREFIX to PREFIXES. Update below Perl script: (Within the OpsCenter extraction) 1. Edit the below file: OpsCenter_7.1_X64/LinuxR_x86_64/Server/scripts/CPI/prod/common/Utils.pm 2. Find the below line: (around lines 49) if ($CPI::SYS{$sys}{OS} eq "Linux"){ $baseDir = CPI::do_sys($sys, "$CPI::PLAT{Linux}{RPM} -q $pkg"); if ($baseDir =~ /not installed/){ $baseDir=""; }else{ # Need to write in a hack for VEA here # The rpm doesn't have INSTALLPREFIX defined # so rpm returns "(none)" which causes problems. # B/c it's non-relocatable, let's just set to /opt if ($pkg eq "VRTSob"){ $baseDir="/opt"; } else { $baseDir = CPI::do_sys($sys, "$CPI::PLAT{Linux}{RPM} -q --queryformat '%{INSTALLPREFIX}\n' $pkg"); } } } 3. Change the above lines to the BOLD lines below: if ($CPI::SYS{$sys}{OS} eq "Linux"){ $baseDir = CPI::do_sys($sys, "$CPI::PLAT{Linux}{RPM} -q $pkg"); if ($baseDir =~ /not installed/){ $baseDir=""; }else{ # Need to write in a hack for VEA here # The rpm doesn't have INSTALLPREFIX defined # so rpm returns "(none)" which causes problems. # B/c it's non-relocatable, let's just set to /opt if ($pkg eq "VRTSob"){ $baseDir="/opt"; } else { $baseDir = CPI::do_sys($sys, "$CPI::PLAT{Linux}{RPM} -q --queryformat '%{PREFIXES}\n' $pkg"); } } } 4. Save & Exit, re-run installation
OpsCenter 7.6 Upgrade Purge Setting Changes - Important for Analytics Users - Please Read!
In OpsCenter 7.6, purge settings will change from 420 to 220 days. For fresh 7.6 installations, there should be no cause for concern. However, upgrades from previous versions of OpsCenter, could cause a large amount of historical job information to be purged from OpsCenter. Symantec NetBackup OpsCenter 7.6 Administrator's Guide PDF http://www.symantec.com/docs/DOC5042 pg. 254 Note: Before OpsCenter 7.6,the default data purge period for the backup jobs data was 420 days. In case of OpsCenter 7.6 upgrade, the default data purge period that is displayed for backup jobs data depends on what you had in the previous OpsCenter version. If you retained the default data purge period in the previous OpsCenter version (that is 420 days), in OpsCenter 7.6, it is set to 220 days. If you changed the default data purge period in the previous OpsCenter version, the same period is displayed in OpsCenter 7.6. For example: If you changed the default period in OpsCenter 7.5 from 420 to 500 days, in OpsCenter 7.6, it is set to 500 days In short, if you have never changed your default purge settings from 420 days (default) in OpsCenter 7.0, 7.1, or 7.5, and upgrade to 7.6, your default will become 220 days. When OpsCenter triggers its purge cycle, 200 days of historical information will be lost. Please Note: This is only for users that have never modified the default purge setting of 420 days, in previous releases.
can't install OPS centers + error 1719
I am trying to install OpsCenter 7.5 Server onWin_2K8_R2 SP1, but can't complete. Error 1719. The Windows installer services could not be accessed. This can occur if you are running windows in safe mode, or if the windows installer is not corectly installed. contact your support personnel for assistance pls help me!
