SAN Client can't detect FT Media server
I experiance some issues in a SAN client. There's an VCS 2 nodes cluster for Oracle DB on Solaris system, and the SAN backups were running well before. Recently, I've changed the hostname of these NBU clients, and the SAN clients can't detecet FT media server anymore. These clients just only can backup using LAN instead of SAN now Belows are some informations and screenshots OS version and NetBackup version: Master server: RedHat 6.5, NBU 7.7.3 3 Media Servers: Solaris 10 U11, NBU 7.7.3 2 Clients: Solaris 10 U11, NBU 7.7.3 Cluster name and hostname: cluster name: fhsoms node1: fhsoms001 node2: fhsoms002 nbemmcmd -listhosts -verbose I didn't edit /kernel/drv/st.conf after I changed the hostname of the NBU clients. Because there's no any words about hostname in this file. I tried to delete cbn file in /dev/rmt on NBU clients, and rescan the drive devices I use vxlogview -o 200 to check nbftclnt logs, and it seems the client can discover the archive python devices Although I rescan the FT devices via GUI and excute rescan command on Master server and 3 Media servers, the SAN clients still can't detect FT media server I tried to restart NBU service and PBX on client, reboot OS and rebuilt zone on SAN switch,but it seems not work Any inputs by you experts is highly appreciated.
NetBackup SAN Client slow scanning /dev/sg devices
Hi folks Is there any way to tune the SAN client, specifically its initial scanning of /dev/sg devices? Can we specifiy what devices to scan, or types of devices to ignore? Our initial scan takes ~2.5hrs (~1100 /dev/sg devices, 99% of which it retries 10x times..) Log filled with the following type messages: 0,51216,200,200,1463,1536330116729,71722,139769537492800,0:,83:called from DiscoverDevices EVPD Page 0x83 "" device name /dev/sg621 2 retries left,13:DeviceInquiry,1 0,51216,200,200,1464,1536330117730,71722,139769537492800,0:,83:called from DiscoverDevices EVPD Page 0x83 "" device name /dev/sg621 1 retries left,13:DeviceInquiry,1 0,51216,200,200,1465,1536330118730,71722,139769537492800,0:,83:called from DiscoverDevices EVPD Page 0x83 "" device name /dev/sg621 0 retries left,13:DeviceInquiry,1 0,51216,200,200,1466,1536330118731,71722,139769537492800,0:,80:Device type 0 found on /dev/sg621 Vendor/Product: "IBM 2810XIV 000 ",16:StdDeviceInquiry,1 0,51216,200,200,1467,1536330118731,71722,139769537492800,0:,83:called from DiscoverDevices EVPD Page 0x83 "" device name /dev/sg620 9 retries left,13:DeviceInquiry,1 0,51216,200,200,1468,1536330119731,71722,139769537492800,0:,83:called from DiscoverDevices EVPD Page 0x83 "" device name /dev/sg620 8 retries left,13:DeviceInquiry,1 0,51216,200,200,1469,1536330120732,71722,139769537492800,0:,83:called from DiscoverDevices EVPD Page 0x83 "" device name /dev/sg620 7 retries left,13:DeviceInquiry,1 0,51216,200,200,1470,1536330121733,71722,139769537492800,0:,83:called from DiscoverDevices EVPD Page 0x83 "" device name /dev/sg620 6 retries left,13:DeviceInquiry,1 0,51216,200,200,1471,1536330122733,71722,139769537492800,0:,83:called from DiscoverDevices EVPD Page 0x83 "" device name /dev/sg620 5 retries left,13:DeviceInquiry,1 0,51216,200,200,1472,1536330123734,71722,139769537492800,0:,83:called from DiscoverDevices EVPD Page 0x83 "" device name /dev/sg620 4 retries left,13:DeviceInquiry,1 Starts at the highest sg number, and doesnt permit any FT backups to proceed until its hit sg1 (about 2.5hrs later) It seems very strange, as I can immediately query the tape devices, eg: lsscsi | grep tape [3:0:6:0] tape ARCHIVE Python V000 /dev/st0 [3:0:6:1] tape ARCHIVE Python V000 /dev/st1 [4:0:6:0] tape ARCHIVE Python V000 /dev/st2 [4:0:6:1] tape ARCHIVE Python V000 /dev/st3 or: ls -l /dev/sg* | grep tape crw-rw----. 1 root tape 21, 1049 Sep 7 13:15 /dev/sg1049 crw-rw----. 1 root tape 21, 1050 Sep 7 13:15 /dev/sg1050 crw-rw----. 1 root tape 21, 887 Sep 7 13:15 /dev/sg887 crw-rw----. 1 root tape 21, 888 Sep 7 13:15 /dev/sg888 I found this post with similar symptoms, marked solved, but since we're already at NetBackup 8.. https://vox.veritas.com/t5/NetBackup/SAN-Client-service-takes-a-long-time-to-start/td-p/650362 Any help appreciated! Many thanks, Ian
All new NetBackup 5220: The complete and purpose-built backup appliance
IDC defines(1) a purpose-built backup appliance as a disk-based solution that utilizes software, disk arrays, server engine(s), or nodes that are used for a target for backup data and specifically data coming from a backup application (e.g., NetBackup, Backup Exec, Networker etc.). These products are stand-alone disk systems purpose built to serve as a target for backup. Symantec’s NetBackup 5200 series appliances, while purpose built for backups, are much more than a traditional PBBA. For example, the all new NetBackup 5220 appliance can be deployed as a NetBackup master server, media server or both. This modular appliance can be used for implementing a brand new NetBackup domain for a remote office or enterprise without needing additional software based backup application to manage data protection for clients. NetBackup 5220 is not just a purpose built backup target, it is a complete backup solution by itself. NetBackup 5220 is the newest member in NetBackup appliances family. The system features v 2.0 of appliance software which is based on NetBackup 7.1.0.1 code. The appliance starts at 4TB of deduplication storage which is ideal for remote office/branch office use cases. As mentioned earlier, the appliance can function as an independent all-in-one NetBackup system or it can be configured as a media server reporting to a central data center. The Auto Image Replication (A.I.R) feature makes it possible for these appliances to replicate to remote NetBackup domains for Disaster Recovery readiness. There is no need to have a backup server and a duplication appliance as in the case of using a traditional PBBA. Moreover, the 4TB model may also be used as the driver for NetBackup 5000 series based global deduplication appliances thereby providing 192TB of deduplication pool. The storage on NetBackup 5220 can be expanded up to 36 TB by adding a Symantec Storage Shelf. Another key feature for NetBackup 5220 is the support for SAN Client. We will talk about this in a separate blog. Thanks to Symantec V-Ray, NetBackup 5220 appliances provide unprecedented visibility into virtual machines, giving you faster recovery and reduced storage costs in virtual environments. Whether you have Hyper-V or VMware (or even both), the appliance understands the data stream with embedded stream handlers whereby it can identify the file boundaries and strip out the meta data before deduplicating the segments. This level of content intelligence makes it possible to deduplicate across virtual, physical, application and NAS systems without brute force resource intensive processing. VMware Intelligent Policy makes it possible to set data protection in auto pilot mode, no need to manually add/remove virtual machines into backup policies. Highly customized rules can be engaged to ensure visibility while automating protection. Do you know that NetBackup 5220 is designed to kill the VTL? We will talk about it next week! 1 Worldwide Purpose-Built Backup Appliance 2011–2015 Forecast and 2010 Vendor Shares, Robert Amatruda, IDC Research Director, Data Protection and Recovery, May 2011
