Setting Maximum Jobs per Client on a per client basis in VERITAS NetBackup

Problem

Setting Maximum Jobs per Client on a per client basis in VERITAS NetBackup ™

Solution

Maximum Jobs per Client applies to all clients in all policies, so it is recommended that it be set to accommodate whichever client can handle the lowest number of concurrent jobs. In addition, it is most commonly recommended that the Maximum Jobs per Client global attribute is set to a higher value and the jobs per policy are restricted when tuning in this area is desired. 

However, there are scenarios in which time windows for backups, the amount of data backed up per client, or resource differences between clients can vary to such a degree as to cause under-utilization of resources. This can easily cause backups to take longer than expected. 

In these situations, the following can be done to tune Maximum Jobs per Client on a per client basis, using the -max_jobs option with the bpclient command, found in the/usr/openv/netbackup/bin/admincmd directory. 

To create a client entry in the NetBackup client catalog with the Maximum Jobs per Client attribute, run this command from the master server: 

bpclient -add -client <client name> -max_jobs # 

For example:   

cd /usr/openv/netbackup/bin/admincmd 

bpclient -add -client <client name> -max_jobs 5 

 

This creates the following directory in the NetBackup client catalog: 

/usr/openv/netbackup/db/client/<client name> 

for the client this command was run for. 

The host_info file is created in this directory with the following line: 

MAX_JOBS_THIS_CLIENT 5 

 

To change the Maximum Jobs per Client once it has been originally set: 

bpclient -client <client_name> -update -max_jobs # 

To delete a client entry: 

bpclient -delete -client <client_name> 

 

To list a client entry: 

bpclient -L -client <client_name> 

 

Note: This setting will override the maximum jobs settings on both the policy and the master server level. See article 267104 for further information. 

Read more

How to migrate Raspberry Pi 5 OS from micro SD to NVME m.2 SSD

首先我買了Raspberry Pi CM5後來買了Raspberry Pi CM5 I/O board來當個人電腦使用,系統是安裝在256GB SD卡上運行的很好。用久了在開啟較肥的程式像Web Browser或LiberOffice會有慢半拍的反應,而有了升級NVME m.2 SSD念頭。 因為Raspberry Pi 5支援的最快PCIe gen3 x 4就不去考慮快的Gen4 or Gen5 m.2 SSD。找了ADATA出的 LEGEND 710入門級的產品,會利用HMB(Host Memory Buffer)來加速I/O速度,因為是Raspberry Pi OS kernel會認不得而無法正常使用 事先在SD卡的/boot/firmware/cmdline.txt 加入 kernel command line參數如下,然後重開機m.

By Phillips Hsieh

How to document Home Lab and Network

運維機房和跨域的網路,會遇到各式需求與問題,用對工具才能分析問題,個人覺得最重要的是使用能處理問題的工具。 推薦目前想學和正在使用的平台與軟體,協助將公司/家用機房文件化 佈告欄任務管理 Focalboard 白板可管理任務指派 網路架構文件編寫 netbox 精細管理網路設備與連接線路 IP 資源管理 phpipam 專注網路IP分配 邏輯塊文件編寫 draw.io 視覺化概念圖 機房設備管理 ITDB 管理設備生命週期與使用者

By Phillips Hsieh

如何在Raspberry Pi4上安裝Proxmox for ARM64

第一步 準備好Raspberry Pi 4 / CM4 4GB RAM,這裡要留意CM4如果是買有內建eMMC storage會限制不能使用SD卡開機而限制本地空間容量,如果沒有NAS外接空間或使用USB開機的話,建議買CM4 Lite插上大容量SD卡 第二步 去Armbian官網下載最小化Debian bookworm image https://www.armbian.com/rpi4b/ Armbian 25.2.2 Bookworm Minimal / IOT 然後寫入SD/USB開機碟,寫入方法參考官方文件 https://github.com/raspberrypi/usbboot/blob/master/Readme.md Note: 官方提供的預先設定系統方法,可以在Armbian初次啟動自動化完成系統設定。連結在此 https://docs.armbian.com/User-Guide_Autoconfig/

By Phillips Hsieh