Contents

  1. Netbakcup how to
    1. How to prepare for NetBackup Master/Media Server upgrade
      1. There are some standard steps which you should do
    2. restart netbackup appliacne services
    3. upgrade HP MSL6400 firmware
    4. List Configured Tape driver and robots
    5. List devices
    6. 确认Devices Unit
    7. 确认Media Unit
    8. List all media
    9. 确认license
    10. 检查设备配置
    11. 授予 NetBackup 对 NAS (NDMP) 主机的访问权限
    12. UNIX/Linux Administration Console
    13. How does NetBackup for SQL Server back up a database?
  2. Troubleshooting
    1. status 2074 disk volume is down
    2. Recall Trash
    3. Running NBSU
    4. View processes
    5. Show Error
    6. Restore must be resumed prior to first image expiration
    7. An error occurred during the installation of assembly
      1. Cause
      2. Solution
    8. verify media/TAPE

Netbakcup how to

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/

restart netbackup appliacne services

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

确认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.

Troubleshooting

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 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}

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