Contents

  1. Netbakcup how to
    1. NetBackup SAN Client requirements
    2. Netbackup Appliance Protection Override
    3. NetBackup for Oracle: Example of restoring a database in a RAC environment
    4. How to configure NetBackup policy to backup VMware VMs
    5. Applying the full License
    6. How to prepare for NetBackup Master/Media Server upgrade
      1. There are some standard steps which you should do
      2. OpsCenter upgrade Notes
        1. To move the OpsCenter database to a different hard disk on Windows
        2. Verify OpsCenter
      3. Master Upgrade
        1. Notes
        2. To disable data collection for a master server
        3. Run Precheck tools
    7. restart netbackup appliacne services
    8. upgrade HP MSL6400 firmware
    9. List Configured Tape driver and robots
    10. List devices
    11. 确认Devices Unit
    12. 确认Media Unit
    13. List all media
    14. List all backup about Client
    15. 确认license
    16. 检查设备配置
    17. 授予 NetBackup 对 NAS (NDMP) 主机的访问权限
    18. UNIX/Linux Administration Console
    19. How does NetBackup for SQL Server back up a database?
  2. Report
    1. Storage summary
  3. Troubleshooting
    1. pbx_exchange
    2. xx
    3. RMAN-06094
    4. EXIT STATUS 5940
    5. Catalog backup fails with status code: 35
      1. STATUS CODE 227
    6. All compatible drive paths are down but media is available
    7. Status Code: 13 File read failed
    8. Waiting in NetBackup scheduler work queue on server
      1. About the NetBackup Client Job Tracker
    9. Error bptm media manager terminated by parent process
    10. MSSQL Client log VxBSACreateObject Erroror
      1. Waiting in NetBackup schedule work queue on server
    11. Trace the network issue
    12. status 2074 disk volume is down
    13. Recall Trash
    14. Running NBSU
    15. View processes
    16. Show jobs info
    17. Show Error
    18. Restore must be resumed prior to first image expiration
    19. An error occurred during the installation of assembly
      1. Cause
      2. Solution
    20. verify media/TAPE

Netbakcup how to

NetBackup SAN Client requirements

  1. NetBackup master server and all NetBackup media servers that use the feature must be at NetBackup 6.5 or later.

  2. HBAs and their drivers must support 256K size buffers for data transfer.

  3. For the connections to the SAN clients, use a QLogic HBA that NetBackup supports for Fibre Transport. For these HBAs, you must configure them to use the NetBackup target mode driver.

  4. Only 64bit Solaris SPARC and Linux x86_64 platforms are supported as Fibre Transport servers.
  5. PBX service must run on the SAN clients.
  6. Enter an Enterprise Client license key on Master server to activate SAN Client.
    • NBU licenses needed:
    • Enterprise Client
    • Shared Storage Option

Netbackup Appliance Protection Override

<NBU-Appliance-Hostname>.Main_Menu> Support
<NBU-Appliance-Hostname>.Support> Maintenance
<!-- Maintenance Mode --!>
maintenance's password: <password>
(this script was for 2.6)
maintenance-!> /opt/Symantec/scspagent/IPS/sisipsoverride.sh
bash: /opt/Symantec/scspagent/IPS/sisipsoverride.sh: No such file or directory

(this is the right script for 2.7)
maintenance-!> /opt/Symantec/sdcssagent/IPS/sisipsoverride.sh
Symantec Data Center Security Server Policy Override

NetBackup for Oracle: Example of restoring a database in a RAC environment

Restoring the database from the nodes where the backup was performed is straightforward and identical to a typical RMAN restore.

In this example, the backup images to be restored must all be accessible by the client name saturn in the image database on the master server jupiter.

Note:

This example works only if the backup is not load balanced across multiple nodes. The reason is because NB_ORA_CLIENT=$NB_ORA_CLIENT evaluates only to the node on which the RMAN script is executed.

The following example restores the entire database from any node: 

RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
SEND 'NB_ORA_CLIENT=saturn,NB_ORA_SERV=jupiter';
RESTORE
      DATABASE;
RECOVER
      DATABASE;
RELEASE CHANNEL ch00;
}

How to configure NetBackup policy to backup VMware VMs

http://www.settlersoman.com/how-to-configure-netbackup-policy-to-backup-vmware-vms/

Applying the full License

NetBackup Self Service 7.7.3 is shipped with a 60-day trial license. A production license is available from your Customer Care team.

Access the NetBackup Self Service portal to apply the license.

Restart the Windows service after you apply the license key. If the application runs in a server farm environment, all application pools must be restarted. In the License page, a message at the top of the page reports that other features are not included. All features that are required to operate a fully configured NetBackup Self Service solution are, however, included.

How to prepare for NetBackup Master/Media Server upgrade

The high level order of upgrade steps

This is a very high level of NetBackup upgrade steps:

  1. Upgrade NetBackup OpsCenter (if exists).

  2. Upgrade NetBackup Master Server.

  3. Upgrade NetBackup Media Server(s).

  4. Upgrade NetBackup Clients.

There are some standard steps which you should do

  1. Check hardware compatibility
  2. Check Operation System compatibility
  3. Before starting upgrading to the new version, run a Catalog Backup.

  4. Depending on NetBackup Catalog Size, the upgrade from 7.1 to 7.5 would need much time.

  5. Read Release Notes and following steps mentioned in the Upgrade Guide.

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

https://sort.veritas.com/checklist/install#report

http://www.settlersoman.com/how-to-upgrade-netbackup-mastermedia-server/

OpsCenter upgrade Notes

Note: The Custom option is disabled when you upgrade to OpsCenter. You cannot customize the default settings, locations, or port numbers while upgrading to OpsCenter.

The installation logs are generated in the following location: %ALLUSERSPROFILE%\Symantec\OpsCenter\INSTALLLOGS\OpsCenterServerInstallLog.htm

Note: In OpsCenter, the database upgrade logs are stored at the following location: %ALLUSERSPROFILE%\Symantec\OpsCenter\INSTALLLOGS\pre-install-config\db\log

To move the OpsCenter database to a different hard disk on Windows

  1. Stop all OpsCenter services. Enter the following command:

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop

  1. Open the databases.conf file with a text editor like notepad from the following directory:

INSTALL_PATH\OpsCenter\server\db\conf

This file has the following contents:

This path specifies the default location of the OpsCenter database.

  1. To move the database to a custom location like E:\Database, replace the contents of the file with the following:

"E:\Database\vxpmdb.db"

  1. Restart all OpsCenter server services. To restart all OpsCenter services, enter the following command:

    INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

Verify OpsCenter

https://<server-host>/opscenter

On Windows: <INSTALL_PATH>\OpsCenter\gui\bin\goodies\configurePorts.bat -status

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop

Master Upgrade

Notes

Note: The computer must have sufficient disk space available in thedatadirectory to create an additional copy of all.dbfiles. By default, thedatadirectory is located ininstall_path\Veritas\NetBackupDB\for Windows and/usr/openv/db/for UNIX/Linux.

To disable data collection for a master server

  1. In the OpsCenter console, select Settings > Configurations > NetBackup.

  2. 2Use the checkbox to select one or more master servers from the Master Server

Name column.

  1. 3Click Disable Data Collection.

Run Precheck tools

Note: Veritas recommends that after you install or upgrade NetBackup server software, you should uninstall older versions of the Remote Administration Console (Windows and Java) present on the host. If the native NetBackup Administration Console for Windows is present, it is automatically uninstalled when you install or upgrade the NetBackup server software.

restart netbackup appliacne services

To manually stop NetBackup processes on NetBackup Appliance 5220, complete the following steps:

To manually start NetBackup processes on NetBackup Appliance 5220 after loggin on as admin via SSH, 

netbackup stop
netbackup show 
netbackup start

,if above not gracefull stop,then try following command 

bp.kill_all

upgrade HP MSL6400 firmware

  1. DOWN Driver

  2. 升级HP微码,备份配制文件->执行升级。

  3. appliance重新扫描SCSI设备 

 lsscisi -g 
 scan -changer
            
 tpautoconf -r
 tpautoconf -t

重新走一遍"添加磁带库"配制向导。 

# stop
ps -ef | grep bprd
bprdreq -teminate

# netbackup start

List Configured Tape driver and robots

tpconfig -d

List devices

scan
tpautoconf -t
tpautoconf -r

确认Devices Unit

vmoprcmd

确认Media Unit

bpstulist

List all media

List all backup about Client

/usr/openv/netbackup/bin/bplist -S nbumaster -C mls-rac01 -t 4 -l -R /

确认license

/usr/openv/netbackup/bin/admincmd/get_license_key

检查设备配置

 /usr/openv/volmgr/bin/vmd
 491954762
 9200

授予 NetBackup 对 NAS (NDMP) 主机的访问权限

NetBackup 必须具有对 NAS（或 NDMP）主机的访问权限，然后才能使用 NDMP 

授予 NetBackup 对 NDMP 主机的访问权限
1 在 NetBackup 服务器上的 NetBackup 管理控制台中，展开“介质和设备管
理”>“凭据”>“NDMP 主机”。
2 在“操作”菜单下，选择“新建”>“新建 NDMP 主机”。
3 在“添加 NDMP 主机”对话框中，输入 NetBackup 要备份的 NDMP 服务器的名称

UNIX/Linux Administration Console

/usr/openv/java/jnbSA &

How does NetBackup for SQL Server back up a database?

From the NetBackup Microsoft SQL Client you can select the databases or the database components that you want to back up. When you select an object for backup, the GUI creates a batch file that contains a script. The SQL Server database agent interprets this script. You can either execute the script immediately or save it to run later. You can run a script later by including it in the backup selections list of a backup policy. 

When a backup script is executed, NetBackup for SQL Server does the following:
generates an SQL backup statement, logs into SQL Server, and delivers the SQL
statement to SQL Server through ODBC. Next, the database agent connects to
SQL Server through one or more VDI objects. One virtual device is created per
backup stripe. In addition, a VxBSA session is initiated for each stripe. These
separate sessions allow NetBackup to start a backup job for each stream that is
generated from SQL Server.

When the backup completes, the database agent obtains detailed properties of the
object that was backed up, including its relationships to other objects. The agent
writes this information to the NetBackup catalog and associates it with the backup
image. If there are multiple stripes, then the metadata is associated with the first
backup image. The adjunct stripes are associated with one another based upon a
common naming convention.

Report

Storage summary

# View storage units
bpstulist -U

# View potential free space in a BasicDisk storage unit
nbdevquery -listdv -D

Troubleshooting

pbx_exchange

To stop the pbx_exchange daemon:
#/opt/VRTSpbx/bin/vxpbx_exchanged stop

To start the pbx_exchange daemon:
#/opt/VRTSpbx/bin/vxpbx_exchanged start

xx

RMAN-06094

run {
2> ALLOCATE  CHANNEL ch00  TYPE 'SBT_TAPE'parms 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64';
3> send 'NB_ORA_SERV=nbu-5240,NB_ORA_CLIENT=zsoda0';
recover database;
5> RELEASE CHANNEL ch00;
6> }

分配的通道: ch00
通道 ch00: SID=2641 设备类型=SBT_TAPE
通道ch00: Veritas NetBackup for Oracle - Release 8.1.1 (2018020320)

向通道发命令: ch00

启动 recover 于 2019/07/10 09:44:49
释放的通道: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: recover 命令 (在 07/10/2019 09:44:50 上) 失败
RMAN-06094: 数据文件1必须重新存储

RMAN> switch database to copy;

数据文件 1 已切换成数据文件副本 "/oradata/MESDB/datafile/system.256.948384113"
数据文件 2 已切换成数据文件副本 "/oradata/MESDB/datafile/sysaux.257.948384113"
数据文件 3 已切换成数据文件副本 "/oradata/MESDB/datafile/undotbs1.258.948384113"
数据文件 4 已切换成数据文件副本 "/oradata/MESDB/datafile/users.259.948384113"

EXIT STATUS 5940

EXIT STATUS 5940: Reissue token is mandatory, please provide a reissue token. An authorization token is required in order to get the host certificate for this host. At the prompt, enter the authorization token or q to skip the question. NOTE: The authorization token entered will not be displayed to the terminal. Enter the authorization token for client or q to skip:

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

Catalog backup fails with status code: 35

STATUS CODE 227

When using Veritas NetBackup (tm), the parent job for a hot catalog backup fails with a Status 227, even though the child jobs complete with a Status 0 (successful).

加了这个disaster path到nbumaster的/home/nbu-catalog-disaster之后备份正常

All compatible drive paths are down but media is available

The tape drive had to be removed from the NetBackup configuration, followed by a restart of the NetBackup Device Manager, followed by the 'Configure Storage Devices' wizard, which also restarts the Device Manager. This implies there was some non drive path error for the tape drive in EMM. By removing and recreating the device record, NetBackup was again able to use the tape drive.

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

Status Code: 13 File read failed

http://all-about-symantec-netbackup.blogspot.com/2015/08/status-code-13-file-read-failed.html

Waiting in NetBackup scheduler work queue on server

There is a combination of issues here.

  1. Max jobs per policy is being met so we can't allow more jobs to go active for the specified policy.
  2. Max jobs per client is met, so again, we can't allow more jobs to go active for the specified client.
  3. Duplication jobs are running for long periods and they are causing contention (as one duplication is using a media required by another...)
  4. Scsi errors reported in the messages file.

#1 Maybe

Using the same command, change the Max drives this master to zero:

This is the maximum drives for this master, the maximum number of drives for this master and remote media server cluster that the master server should consider available when scheduling backups. Drives is a non-negative integer. The default is 0 (unlimited).

}}}

About the NetBackup Client Job Tracker

Microsoft Windows systems only.

The NetBackup Client Job Tracker reports on the status of server-directed or user-directed client operations. The job tracker runs as a background process from the system tray. The job tracker only reports on the operations that occur after the job tracker is started.

For backups, the job tracker does not update the status after the job is sent to the NetBackup server. Once the client sends the data to be backed up to the server, the job tracker reports the backup status as successful. If an error occurs on the server that causes the backup to fail, the error is not reported to the job tracker.

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

https://vox.veritas.com/t5/NetBackup/How-stop-quot-In-Progress-quot-Backup-Job/td-p/35171

Error bptm media manager terminated by parent process

http://kmit4u.blogspot.com/2010/07/netbackup-ms-sql-backup-client-hold.html 

2017-1-11 14:18:22 - Info nbjm (pid=63136) starting backup job (jobid=328596) for client server007.meizu.com, policy server007_mssql_log_8h_1m, schedule Log-Application-Backup
2017-1-11 14:18:22 - Info nbjm (pid=63136) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=328596, request id:{C0AD3716-D7C5-11E6-AA1A-E0AA1A227C83})
2017-1-11 14:18:22 - requesting resource stu_disk_it-nbu-01
2017-1-11 14:18:22 - requesting resource it-nbu-01.NBU_CLIENT.MAXJOBS.server007.meizu.com
2017-1-11 14:18:22 - requesting resource it-nbu-01.NBU_POLICY.MAXJOBS.server007_mssql_log_8h_1m
2017-1-11 14:18:22 - awaiting resource stu_disk_it-nbu-01. Maximum job count has been reached for the storage unit.
2017-1-11 14:20:22 - Info nbjm (pid=63136) Waiting in NetBackup scheduler work queue on server it-nbu-01
2017-1-11 14:22:22 - Info nbjm (pid=63136) Waiting in NetBackup scheduler work queue on server it-nbu-01
2017-1-11 14:24:22 - Info nbjm (pid=63136) Waiting in NetBackup scheduler work queue on server it-nbu-01
2017-1-11 14:24:45 - Info bpbrm (pid=109201) server007.meizu.com is the host to backup data from
2017-1-11 14:24:45 - Info bpbrm (pid=109201) reading file list for client
2017-1-11 14:24:45 - granted resource  it-nbu-01.NBU_CLIENT.MAXJOBS.server007.meizu.com
2017-1-11 14:24:45 - granted resource  it-nbu-01.NBU_POLICY.MAXJOBS.server007_mssql_log_8h_1m
2017-1-11 14:24:45 - granted resource  MediaID=@aaaaf;DiskVolume=PureDiskVolume;DiskPool=dp_disk_it-nbu-01;Path=PureDiskVolume;StorageServer=it-nbu-01;MediaServer=it-nbu-01
2017-1-11 14:24:45 - granted resource  stu_disk_it-nbu-01
2017-1-11 14:24:45 - estimated 0 kbytes needed
2017-1-11 14:24:45 - Info nbjm (pid=63136) started backup (backupid=server007.meizu.com_1484115885) job for client server007.meizu.com, policy server007_mssql_log_8h_1m, schedule Log-Application-Backup on storage unit stu_disk_it-nbu-01
2017-1-11 14:24:45 - started process bpbrm (pid=109201)
2017-1-11 14:24:45 - connecting
2017-1-11 14:24:46 - Info bpbrm (pid=109201) listening for client connection
2017-1-11 14:24:47 - Info bpbrm (pid=109201) INF - Client read timeout = 7200
2017-1-11 14:24:48 - Info bpbrm (pid=109201) accepted connection from client
2017-1-11 14:24:48 - Info dbclient (pid=1680) Backup started
2017-1-11 14:24:48 - Info bpbrm (pid=109201) bptm pid: 109203
2017-1-11 14:24:48 - Info bptm (pid=109203) start
2017-1-11 14:24:48 - Info bptm (pid=109203) using 1048576 data buffer size
2017-1-11 14:24:48 - connected; connect time: 0:00:00
2017-1-11 14:24:49 - Info bptm (pid=109203) using 64 data buffers
2017-1-11 14:24:49 - Info bptm (pid=109203) start backup
2017-1-11 14:54:52 - Info dbclient (pid=1680) done. status: 6

2017-1-11 15:34:56 - Info bptm (pid=109203) backup child process is pid 131564
2017-1-11 15:34:56 - begin writing
2017-1-11 15:34:58 - Error bptm (pid=109203) media manager terminated by parent process
2017-1-11 15:35:00 - Info it-nbu-01 (pid=109203) StorageServer=PureDisk:it-nbu-01; Report=PDDO Stats for (it-nbu-01): scanned: 4 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache hits: 0 (0.0%)
2017-1-11 15:35:00 - Info dbclient (pid=1680) done. status: 6: the backup failed to back up the requested files
2017-1-11 15:35:00 - end writing; write time: 0:00:04
the backup failed to back up the requested files  (6)

MSSQL Client log VxBSACreateObject Erroror

INF - Created VDI object for SQL Server instance <IT-K3-1-243>. Connection timeout is <300> seconds.
ERR - Error in VxBSACreateObject: 3.
    CONTINUATION: - System detected error, operation aborted.
    ERR - Error in GetCommand: 0x80770004.
        CONTINUATION: - An abort request is preventing anything except termination actions.
        DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3202><[Microsoft][ODBC SQL Server Driver][SQL Server]在 "VNBU0-5372-8416-1484093136" 上写入失败: 995(由于线程退出或应用程序请求，已中止 I/O 操作。
        )>.
        DBMS MSG - SQL Message <3271><[Microsoft][ODBC SQL Server Driver][SQL Server]在文件 "VNBU0-5372-8416-1484093136" 上发生不可恢复的 I/O 错误: 995(由于线程退出或应用程序请求，已中止 I/O 操作。)。>
        DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG 正在异常终止。>
        ERR - Error found executing <backup log "AIS20130321213128" to VIRTUAL_DEVICE='VNBU0-5372-8416-1484093136' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2>.
        ERR - Internal error. See the dbclient log for more information.
        INF - OPERATION #2 of batch C:\Program Files\Veritas\SQLScripts\log.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 314(314) seconds.
        INF - BACKUP STARTED USING

Waiting in NetBackup schedule work queue on server

13:11:49 INF - Beginning backup on server it-nbu-01 of client IT-K3-1-243.MEIZU.COM
13:11:52.414 [10224.6608] <4> : 13:11:51 INF - Waiting in NetBackup scheduler work queue on server it-nbu-01
13:11:52.414 [10224.6316] <4> : 13:11:51 INF - Waiting in NetBackup scheduler work queue on server it-nbu-01
13:13:52.068 [10224.6608] <4> : 13:13:51 INF - Waiting in NetBackup scheduler work queue on server it-nbu-01
13:13:52.068 [10224.6316] <4> : 13:13:51 INF - Waiting in NetBackup scheduler work queue on server it-nbu-01
13:15:52.737 [10224.6608] <4> : 13:15:52 INF - Waiting in NetBackup scheduler work queue on server it-nbu-01
13:15:52.737 [10224.6316] <4> : 13:15:52 INF - Waiting in NetBackup scheduler work queue on server it-nbu-01
13:17:53.405 [10224.6608] <4> : 13:17:53 INF - Waiting in NetBackup scheduler work queue on server it-nbu-01
13:17:53.405 [10224.6316] <4> : 13:17:52 INF - Waiting in NetBackup scheduler work queue on server it-nbu-01
13:19:42.919 [10224.6608] <4> : 13:19:42 INF - Server status = 2106
ERR - Error in VxBSACreateObject: 3.
13:19:42.919 [10224.6316] <4> : 13:19:42 INF - Server status = 2106
ERR - Error in VxBSACreateObject: 3.
    CONTINUATION: - System detected error, operation aborted.
        CONTINUATION: - System detected error, operation aborted.
        ERR - Error in GetCommand: 0x80770004.
        ERR - Error in GetCommand: 0x80770004.
            CONTINUATION: - An abort request is preventing anything except termination actions.
                CONTINUATION: - An abort request is preventing anything except termination actions.
                DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3202><[Microsoft][ODBC SQL Server Driver][SQL Server]在 "VNBU0-10224-4172-1484195146" 上写入失败: 995(由于线程退出或应用程序请求，已中止 I/O 操作
                )>.
                DBMS MSG - SQL Message <3271><[Microsoft][ODBC SQL Server Driver][SQL Server]在文件 "VNBU0-10224-4172-1484195146" 上发生不可恢复的 I/O 错误: 995(由于线程退出或应用程序请求，已中止 I/O 操作。)。>
                DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE 正在异常终止。>
                ERR - Error found executing <backup database "AIS20130321213128" to VIRTUAL_DEVICE='VNBU0-10224-4172-1484195146', VIRTUAL_DEVICE='VNBU1-10224-4172-1484195146' with  stats = 10, blocksize = 65536, maxtransfersize 
                = 4194304, buffercount = 4>.

Trace the network issue

run:

from client:
bpclntcmd -pn
bpclntcmd -self
bpclntcmd -hn <master server>
bpclntcmd -hn <media server>
bpclntcmd -ip <master IP>
bpclntcmd -ip <media IP>

from master:
traceroute <client name>
ping -s -i <nic> -p 13782 <client name> 65000 4
bpgetconfig -M <client name> -x
bptestbpcd -client <client name> -verbose

from media:
traceroute <client name>
ping -s -i <nic> -p 13782 <client name> 65000 4
bpgetconfig -M <client name> -x
bptestbpcd -client <client name> -verbose

status 2074 disk volume is down

01/05/2017 19:38:27 - Info it-nbu-01(pid=217530) StorageServer=PureDisk:it-nbu-01; Report=PDDO Stats for (it-nbu-01): scanned: 813 KB, CR sent: 38 KB, CR sent over FC: 0 KB, dedup: 95.3%, cache disabled
01/05/2017 19:38:41 - Info bpdm(pid=217530) EXITING with status 0
01/05/2017 19:38:44 - Info bpdm(pid=44644) started
01/05/2017 19:38:44 - started process bpdm (44644)
01/05/2017 19:38:45 - Error bpdm(pid=44644) NBJM returned an extended error status: Disk volume is down (2074)
01/05/2017 19:38:45 - Error nbreplicate(pid=217494) ReplicationJob::Replicate: Replication failed for backup id IT-INFO-1-238.MEIZU.COM_1483556372: media open error (83)
01/05/2017 19:38:45 - requesting resource @aaaaf
01/05/2017 19:38:45 - Error nbjm(pid=11252) NBU status: 2074\, EMM status: Disk volume is down
01/05/2017 19:38:46 - Info bpdm(pid=44660) started

The option "This directory can exist on the root file system or system disk" need to be checked on the Storage Unit Disk properties.

  1. Run the following commands to query and update the disk pool device status on the netbackup server end. To check the state of the disk pool:

    • nbdevquery -listdp -stype PureDisk -U

      • nbdevquery -liststs -U
        • nbdevquery -listdp -U

          • nbdevquery -listdv -stype <disk pool type> -U

  2. To check the state of the disk volume:

    • nbdevquery -listdv -stype PureDisk -dp <disk Pool name> -dv <disk volume name> -U

      • Note - the disk volume name in the command above was found in the NetBackup Admin Console in the All diskpools selection.

  3. To bring up the disk volume state:

    • ./NetBackup/bin/admincmd/nbdevconfig -changestate -stype PureDisk -dp <Disk Pool name> -dv <disk volume name> -state UP

      • Note - If the above commands do not help for getting the status to update for the diskpool volumes or the diskpool continues to go down in the NetBackup console, recycle the services of netbackup which will update the status as per the high watermark settings at the PureDisk end for the disk volume.

Recall Trash

Image过期产生了垃圾
检查消重存储池队列(TLOG文件)
ls -l /disk/queue/
执行队列处理
/usr/openv/pdde/pdcr/bin/crcontrol --processqueue
监控队列处理
tail -f /disk/log/spoold/storaged.log
垃圾回收
/usr/openv/pdde/pdcr/bin/crcollect -v -m +1,+2
重复2-5步骤直至TLOG处理完
检查Used和Space available within containers的空间
/usr/openv/pdde/pdcr/bin/crcontrol --dsstat
如果Space needs compaction的值很高，则执行压缩
/usr/openv/pdde/pdcr/bin/crcontrol --compactstart

Running NBSU

nbsu
nbsu -l -nozip

View processes

# Acitive processes
bpps -a
bpps -x

# only Media Manager
vmps

Show jobs info

bpdpjobs -report -all_columns

Show Error

bperror -all -U 
bperror -backstat -U
bperror -problems -U
bperror -media -U
bperror -disk

Restore must be resumed prior to first image expiration

http://www.symantec.com/connect/forums/restore-must-be-resumed-prior-first-image-expiration

An error occurred during the installation of assembly

MSI (s) (90:2C) [13:59:03:465]: Product: Symantec NetBackup Client -- Error 1935.An error occurred during the installation of assembly 'Microsoft.VC80.CRT,type="win32",version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64"'. Please refer to Help and Support for more information. HRESULT: 0x80070005. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {844EFBA7-1C24-93B2-A01F-C8B3B9A1E18E}

In the NetBackup Administration Console, expand Security Management > Certificate Management > Token Management.
On the Actions menu, select New Token.
The Create Token dialog box is displayed.


nbcertcmd -listCertDetail

Cause

This error has been observed when the insufficient permissions exist on this folder: C:\Windows\winsxs\InstallTemp 

The minimum needed (and default) permissions are:
Read & execute
List folder contents
Read
Write
Special permissions

Solution

The user logged in performing the install must have the above permissions for the folder C:\Windows\winsxs\InstallTemp.

verify media/TAPE

Please paste output from nbemmcmd -listmedia -mediaid ID -verbose

https://vox.veritas.com/t5/NetBackup/how-to-find-out-if-my-tapes-have-images-data-on-them-bulk-search/td-p/336469/page/3

désert/Netbackup (last edited 2019-09-11 02:38:39 by 192)