[root@nbuserver ~]# /usr/openv/volmgr/bin/vmupdate -rt tld -rn 0 -recommend
Generating list of recommended changes ...
Proposed Change(s) to Update the Volume Configuration
=====================================================
Logically move media ID O502L5 (barcode LTO502L5) from standalone to slot 3.
[root@nbuserver ~]#
変更がない場合は以下のようになる。
[root@nbuserver ~]# /usr/openv/volmgr/bin/vmupdate -rt tld -rn 0 -recommend
Generating list of recommended changes ...
Proposed Change(s) to Update the Volume Configuration
=====================================================
Volume configuration is up-to-date with robot contents.
[root@nbuserver ~]#
[root@nbuserver ~]# /usr/openv/volmgr/bin/vmupdate -rt tld -rn 0
Generating list of recommended changes ...
Proposed Change(s) to Update the Volume Configuration
=====================================================
Logically move media ID O502L5 (barcode LTO502L5) from standalone to slot 3.
Updating volume configuration ...
Processing existing media added to or moved within the robotic library by
logically moving media as follows...
Media ID Slot
======== ====
O502L5 3
Volume configuration successfully updated.
[root@nbuserver ~]#
[root@nbuserver ~]# /usr/openv/volmgr/bin/vmquery -b -rt NONE
media media robot robot robot side/ optical # mounts/ last
ID type type # slot face partner cleanings mount time
-------------------------------------------------------------------------------
O502L5 HCART2 NONE - - - - 0 0000/00/00 00:00
[root@nbuserver ~]#
Renaming a Master Server under NetBackup 6.0 requires making some updates to the EMM database and EMM configration files as well as the changes to configuration files and registry entries required for earlier versions of NetBackup. The steps involved are:
1. Shut down NetBackup on the Master Server. 2. Change the various entries for the Master Server and EMM server in bp.conf and vm.conf (or the registry on a Windows server). 3. Change the value of VXDBMS_NB_SERVER in the vxdbms.conf file (located in /usr/openv/db/data on UNIX and <install path>\VERITAS\NetBackupDB\data on Windows) to reflect the name of the new Master Server. 4. Change the corresponding value found the server.conf file (located in /usr/openv/var/global on UNIX and <install path>\VERITAS\NetBackupDB\conf on Windows) 5. Rename the server and restart it. 6. Re-start NetBackup 7. Run nbemmcmd –renamehost –machinename <old master> -newmachinename <new master> – machinetype master 8. Re-start NetBackup again 9. Run the command nbemmcmd –listhosts –verbose on the Master Server to confirm that the entries for ‘server’ and ‘master’ reflect the new Master Server name. 10. Run nbemmcmd –setemmserver –emmserver <old master> -newemmserver <new master> on each media server 11. Update the entries for the master server in bp.conf and vm.conf (or the registry on a Windows server) on each media server 12. Update the entries for the master server in bp.conf (or the registry on a Windows server) on each client server Note: The process described here cannot be used to change a non-clustered Master Server to a clustered Master Server. This change involves a separate procedure covered in the document NBU_non-cluster-to-cluster guide which can be found in the data protection operational documents area of the CoE web site. Note: Due to limitations in the nbemmcmd –rename command this process cannot be used to rename clusters on versions below 6.0 MP6, if the Master Server is clustered we recommend moving to another cluster rather than renaming the existing cluster.
# /usr/openv/netbackup/bin/nbcertcmd -getCertificate -host NBUクライアント -server NBUサーバ
nbcertcmd: The -getCertificate operation failed for server NBUサーバ
EXIT STATUS 8500: Connection with the web service was not established.
#
今回はWindows Server上だったので、Windows FIrewallに対して、ポート1556とポート13724を開けた。(NetBackup master server portsをみるともポート 13782 もあった方がよさそう)
再実行すると下記となる
# /usr/openv/netbackup/bin/nbcertcmd -getCertificate -host NBUクライアント -server NBUサーバ
nbcertcmd: The -getCertificate operation failed for server NBUサーバ.
EXIT STATUS 8508: List of trusted Certificate Authorities could not be fetched.
#
これは証明書管理にホストが登録されていないために発生しています
新規トークンを発行します
ここで表示されるトークン値を使います
# /usr/openv/netbackup/bin/nbcertcmd -getCertificate -token QWRNKOHALAKDPAGF
nbcertcmd: The -getCertificate operation failed for server NBUサーバ.
EXIT STATUS 8508: List of trusted Certificate Authorities could not be fetched.
#
# /usr/openv/netbackup/bin/nbcertcmd -displayCACertDetail -server NBUサーバ
CA Certificate received successfully from server NBUサーバ.
Subject Name : /CN=nbatd/OU=root@NBUサーバ/O=vx
Start Date : 10月 20 04:36:48 2022 GMT
Expiry Date : 10月 15 05:51:48 2042 GMT
SHA1 Fingerprint : E4:3C:2E:12:4C:66:DF:62:28:98:C1:D3:EB:5A:E0:44:4F:52:64:62
CA Certificate State : Not Trusted
# /usr/openv/netbackup/bin/nbcertcmd -displayCACertDetail -server NBUサーバ.adosakana.local
The target server NBUサーバ.adosakana.local could not be authenticated.
The server name does not match any of the host names listed in the server's certificate.
Names listed in the server's certificate are:
DNS:NBUサーバ
Failed to display CA certificate details
nbcertcmd: The -displayCACertDetail operation failed.
EXIT STATUS 8509: The specified server name was not found in the web service certificate
#
# /usr/openv/netbackup/bin/nbcertcmd -getCertificate -token QWRNKOHALAKDPAGF -force
nbcertcmd: The -getCertificate operation failed for server NBUサーバ.
EXIT STATUS 8508: List of trusted Certificate Authorities could not be fetched.
#
# /usr/openv/netbackup/bin/nbcertcmd -getCACertificate
Authenticity of root certificate cannot be established.
The SHA1 fingerprint of root certificate is E4:3C:2E:12:4C:66:DF:62:28:98:C1:D3:EB:5A:E0:44:4F:52:64:62.
Are you sure you want to continue using this certificate ? (y/n): y
The validation of root certificate fingerprint is successful.
CA certificate stored successfully from server NBUサーバ.
# /usr/openv/netbackup/bin/nbcertcmd -getCertificate -token
QWRNKOHALAKDPAGF -force
Host certificate and certificate revocation list received successfully from server NBUサーバ
#
