NetBackup / bptestbpcd

NetBackup master sunucu ile client bağlatı durumunu kontrol etmek için admincmd altında aşağıdaki komutu çalıştırabilirz.

 Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd.exe -client client-name -debug -verbose

NetBackup / Registering authorized locations used by a NetBackup database script-based policy

Status Code: (5449) The script is not approved for execution.

To add an authorized location

1. Open a command prompt on the client.
2. Use nbsetconfig to enter values for an authorized location. The client privileged user must run these commands.

On UNIX, to update the bp.conf file:

# /usr/openv/netbackup/bin/nbsetconfig

nbsetconfig>DB_SCRIPT_PATH = /Oracle/scripts

nbsetconfig>DB_SCRIPT_PATH = /db/Oracle/scripts/full_backup.sh

nbsetconfig>
<ctrl-D>
 
On Windows, to update the registry with a new "String Value" Registry entry:
C:\Program Files\Veritas\NetBackup\bin>nbsetconfig
nbsetconfig>DB_SCRIPT_PATH=c:\db_scripts
nbsetconfig>DB_SCRIPT_PATH=e:\oracle\fullbackup\full_rman.sh
nbsetconfig>
<Ctrl+Z> and ENTER

https://www.veritas.com/support/en_US/article.100039639

NetBackup / Deleting an OpenStorage storage server

To delete an OpenStorage storage server

1. In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Credentials > Storage Servers
2. Select the storage server that you want to delete.
3. On the Edit menu, select Delete.
4. Click Yes in the confirmation dialog box.
5. On the NetBackup master server, use the following command to delete the storage server from the NetBackup EMM database:

Linux: /usr/openv/netbackup/bin/admincmd/nbemmcmd -deletehost -machinename storage_server_name -machinetype ndmp

Windows: install_path\NetBackup\bin\admincmd\nbemmcmd -deletehost -machinename storage_server_name -machinetype ndmp

https://www.veritas.com/support/en_US/doc/59118460-127355792-0/v15150143-127355792

Linux / Changing the Size of an XFS File System with xfs_growfs

The size of an XFS file system can be increased by using the xfs_growfs command when the file system is mounted. Reducing the size of an XFS file system is not possible.

servername:~ # sudo xfs_growfs -d /sapmnt

meta-data=/dev/mapper/sapmnt-lv0 isize=512    agcount=32, agsize=33554304 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=0 spinodes=0 rmapbt=0
         =                       reflink=0
data     =                       bsize=4096   blocks=1073737728, imaxpct=5
         =                       sunit=2      swidth=1024 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal               bsize=4096   blocks=521728, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 1073737728 to 1342172160

dosya sistemi 5TB a extend edilmiştir.

https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-resize-fs.html

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