OpsCenter etiketine sahip kayıtlar gösteriliyor. Tüm kayıtları göster
OpsCenter etiketine sahip kayıtlar gösteriliyor. Tüm kayıtları göster

2 Nisan 2025 Çarşamba

NetBackup | Register OpsCenter

NetBackup master sunucusunu OpsCenter sistemine register etmek için aşağıdaki komutu kullanabiliriz.

nbregopsc -add <Name of the OpsCenter Server> 

D:\Program Files\Veritas\NetBackup\bin\admincmd>nbregopsc.exe

ERROR: No options selected

Usage: nbregopsc [-help]

[-addnb <OpsCenter server name>] Registers NetBackup with the specified OpsCenter server
[-addopscenter <OpsCenter server name>] Registers the OpsCenter server with NetBackup
[-add <OpsCenter server name>] Performs both -addnb and -addopscenter
[-preferred_network <OpsCenter server IP Address>] Optional OpsCenter server IP (applicable only for -add and -addnb)

26 Mart 2023 Pazar

NetBackup / Registering NB with OpsCenter

bash-4.2# pwd

/usr/openv/netbackup/bin/admincmd

bash-4.2# ./nbregopsc -addopscenter servername

Registering opscenter (opscenter servername) with NB

Successfully registered

Registering NB with opscenter (opscenter servername)

Successfully registered


26 Mayıs 2021 Çarşamba

OpsCenter / OpsCenter Tuning Status


OpsCenter Tuning Status kısmından şuanki memory ayarlarını ve önerilen değerleri kontrol edebiliriz. INSTALL_PATH\OpsCenter\server\db\conf\server.conf  dosyasını düzenleyerek istenilen ayarları tanımlayabiliriz.

Varsayılan ayarlar aşağıdaki gibi:
-n OPSCENTER_<HOST_NAME> -x tcpip(LocalOnly=YES;BROADCASTLISTENER=0;DOBROADCAST=NO;ME=127.0.0.1;ServerPort=13786) -gd DBA -gk DBA -gl DBA -gp 4096 -ti 0 -c 256M -ch 1024M -cl 256M -zl -os 1M -m  -o "<INSTALL_PATH>\OpsCenter\server\db\log\server.log"

Örnek olarak, initial ve minumum değerinin 1G ve maximum değerinin 7G olması için aşağıdaki şekilde düzenleme yaptık:

-n OPSCENTER_<HOST_NAME> -x tcpip(LocalOnly=YES;BROADCASTLISTENER=0;DOBROADCAST=NO;ME=127.0.0.1;ServerPort=13786) -gd DBA -gk DBA -gl DBA -gp 4096 -ti 0 -c 1G -ch 7G -cl 1G -zl -os 1M -m  -o "<INSTALL_PATH>\OpsCenter\server\db\log\server.log"

-c 256M indicates the initial memory that is reserved for caching database pages and other server information. The default value is 256 MB.

-cl 256M indicates the minimum cache size, as a limit to automatic cache resizing. The default minimum cache size is 256 MB.

-ch 1024M indicates the maximum cache size, as a limit to automatic cache growth. The default maximum cache size is1024 MB.


https://www.veritas.com/content/support/en_US/doc/91541840-127431414-0/v92697731-127431414

24 Ekim 2020 Cumartesi

OpsCenter / Data collection failing after upgrade to OpsCenter 8.3.1

8.3.1 upgrdae sonrası datacollection sorunu içi aşağıdaki şekilde adımlar uygulanabilir.

1. OpsCenter üzerinde tüm master sunucular için data collection disable edilir

2. Update için Update_SQL.sql dosyası, delete için de Delete_SQL.sql C:\Temp altında oluşturulur

update domain_Entity set entityType = 14 where id in (select id from domain_MasterServer); commit;

delete from nb_VirtualMachines where clientId in (select id from domain_MasterServer); commit;

3. C:\Program Files\Symantec\Opscenter\server\bin altından çalıştırılır

Open cmd as administrator and run: 
C:\Program Files\Symantec\Opscenter\server\bin\loadsql.bat "C:\Temp\Update_SQL.sql" 
C:\Program Files\Symantec\Opscenter\server\bin\loadsql.bat "C:\Temp\Delete_SQL.sql" 


Problem

After upgrading an OpsCenter server to version 8.3, data collection stops.

However, note that data collection is being performed, but the data is not visible in the OpsCenter web GUI.

After the upgrade, all master servers would show in Monitor > Hosts > Masters. After data collection is re-enabled, they would disappear from Monitor > Hosts > Masters as their entitytype was changing.

Cause

This issue was caused by a regression of VMWare Aliasing related changes to the 8.3 code base.

Solution

Veritas is aware of this issue and is working on integrating the solution into an upcoming release. Until then, the following steps may be performed.

1. Make a copy of the OpsCenter database using the dbbackup command (just in case!).

2. Disable OpsCenter data collection for all masters.

3. Run the following SQL script (see below note Running SQL scripts for more information):

update domain_Entity set entityType = 14 where id in (select id from domain_MasterServer); commit;

4. Run the following SQL script (see below note Running SQL scripts for more information):

delete from nb_VirtualMachines where clientId in (select id from domain_MasterServer); commit;

5. Restart OpsCenter Services

6. Enable OpsCenter data collection and verify proper operation.


Note: Running SQL scripts

You may use any of the following methods:

Sybase Central

dbisql

loadsql

Note that loadsql (.bat for Windows, .sh for Linux) requires that the scripts shown should be written to a file with a .sql or .txt extension.

Sybase Central is a free download, but customers may not allow additional software such as this to be installed, whereas loadsql and dbisql are included with the OpsCenter installation. See relevant documentation on the use of these tools.

If you do not feel confident performing these steps, please contact Veritas Support Services and/or open a support case for assistance.

https://www.veritas.com/content/support/en_US/article.100048466


28 Kasım 2017 Salı

OPSCenter / service stop start

1) Stop OpsCenter services:
<install_path>\OpsCenter\server\bin>opsadmin stop
Stopping the OpsCenter Web Console Service...
Stopping the OpsCenter Server...
Stopping the OpsCenter database...
2) Start OpsCenter services:
 <install_path>\OpsCenter\server\bin>opsadmin start 
Starting the OpsCenter Database... 
The Veritas OpsCenter Database Server service is starting. 
The Veritas OpsCenter Database Server service was started successfully.
Starting the OpsCenter Server... 
The Veritas OpsCenter Server Service service is starting. 
The Veritas OpsCenter Server Service service was started successfully.
Starting OpsCenter Web Console Service... 
The Veritas OpsCenter WebServer Service service is starting. 
The Veritas OpsCenter WebServer Service service was started successfully.


18 Haziran 2015 Perşembe

OpsCenter - An unknown exception has occurred. To continue, click on any tab.

An unknown exception has occurred.
To continue, click on any tab.

[root@opsserver bin]# ./opsadmin.sh monitor
PBX service is up
Symantec NetBackup OpsCenter Authentication Service is down
Symantec NetBackup OpsCenter Database Server Service is up
Symantec NetBackup OpsCenter Server Service is up
Symantec NetBackup OpsCenter WebServer Service is up


[root@opsserver bin]# ./opsadmin.sh stop
Stopping Symantec NetBackup OpsCenter Services

Stopping Symantec NetBackup OpsCenter WebServer Service
Stopping Symantec NetBackup OpsCenter Server Service
Stopping Symantec NetBackup OpsCenter Server (15) ...
Stopping Symantec NetBackup OpsCenter Database Server Service
SQL Anywhere Stop Server Utility Version 16.0.0.2034
Stopping Symantec NetBackup OpsCenter Authentication Service
Stopping Symantec NetBackup OpsCenter Authentication (15) ...

[root@opsserver bin]# ./opsadmin.sh start
Starting Symantec NetBackup OpsCenter Services

Starting PBX Service
Starting Symantec NetBackup OpsCenter Authentication Service
Symantec NetBackup OpsCenter Authentication started, pid = 3018
Starting Symantec NetBackup OpsCenter Database Server Service
SQL Anywhere Start Server In Background Utility Version 16.0.0.2034
Symantec NetBackup OpsCenter Database Server started
Starting Symantec NetBackup OpsCenter Server Service
Starting Symantec NetBackup OpsCenter Server...
Symantec NetBackup OpsCenter Server started, pid = 3110
Starting Symantec NetBackup OpsCenter WebServer Service
[root@opsserver bin]#

Raporları oluşturmak için Flex üzerindeki master server'a PuTTY üzerinden appadmin ile giriş yapın ve "sudo -i" ile root kulla...