Hi,

We have new Network infratructure being implemented where the traditional method of stacking switches to allow us to LACP across multiple switches, has been replaced with a new NEXUS 9000 setup which now uses something call VPC (Virtual Port Channelling).

I dont know much about this but have been asked by the Technical Architects to confirm that the VPC is supported by the Netbackup appliances?

Our appliances are 5230 at version 2.6.0.2 (7.6.0.2)

Hopefully someone has come across this before and can help ?

Thanks

Nick

The IP addresses and URL's that Appliances use to phone home are changing:

https://support.symantec.com/en_US/article.INFO280...

Dear Experts

Trying to configure backup windows file system backup ( win 2008)  for two  SAN attached drives which get mount & unmount every night calling a another script within bpstart & bpend notify and have done similar on 5 more hosts using same scrirpts which having successful backup, except only 1 server i.e.,  server018.

Here are the logs from last bakcup

09/10/2015 01:30:45 - Info bpbrm (pid=27131978) server018 is the host to backup data from
09/10/2015 01:30:45 - Info bpbrm (pid=27131978) reading file list from client
09/10/2015 01:30:45 - connecting
09/10/2015 01:30:48 - Info bpbrm (pid=27131978) starting bpbkar on client
09/10/2015 01:30:48 - connected; connect time: 0:00:00
09/10/2015 01:45:48 - Error bpbrm (pid=27131978) socket read failed: errno = 119 - System call timed out
09/10/2015 01:45:50 - Info bpbkar (pid=0) done. status: 13: file read failed
09/10/2015 01:45:50 - end writing
file read failed  (13)

Note  I have already increased the client read timeout to 1800 from 300 , and set the snapshot provider in   WOFB  to VSS,

Master Server : Linux  with 7.5.0.7

Media Server : AIX with 7.5.0.7

Client : Win 2008 with 7.5.0.1 ( Blade Server)

Back end storage : IBM ProtecTIER ( OST type)

Please advise as we  may do one more test tonight

Thanks All in advance

Regards

Hi.

Evnironment: MasterServer: Linux SLES11

RemoteConsoleServer: Windows 2008R2 (virtual machine) - is use for manage environment, backup polices, etc

MediaServers & Storage: 2x NetBacakup Appliance 5230 

NetBackup ver 7.6.0.3 is installd on all servers & clients.

Problem:the restore is failed on the same host but for different location.

8/26/2015 8:29:49 AM - Info bpbrm(pid=11935) "ClientName" is the host to restore to      
8/26/2015 8:29:49 AM - Info bpbrm(pid=11935) reading file list for client        
8/26/2015 8:29:50 AM - Error bpbrm(pid=11935) Request from host "MediaServer_Name" to host "RemoteConsoleServer_Name" is not allowed access. Host "MediaSerever_Name" is not an authorized server for host "MasterServer_Name".
8/26/2015 8:29:50 AM - Error bpbrm(pid=11935) bpcd on "MasterServer_Name" exited with status 59: access to the client was not allowed
8/26/2015 8:29:50 AM - Error bpbrm(pid=11935) cannot put rename file on "ClientName" 
8/26/2015 8:29:50 AM - Info tar(pid=0) done. status: 59: access to the client was not allowed   
8/26/2015 8:29:50 AM - Error bpbrm(pid=11935) client restore EXIT STATUS 59: access to the client was not allowed
8/26/2015 8:41:35 AM - begin Restore
8/26/2015 8:41:35 AM - restoring image "ClientName"_1440178202
8/26/2015 8:41:36 AM - Info bprd(pid=1693) Restoring from copy 1 of image created Fri Aug 21 19:30:02 2015 from policy "PolicyName"
8/26/2015 8:41:36 AM - requesting resource @aaaab
8/26/2015 8:41:36 AM - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool="DiskPool_Name";Path=PureDiskVolume;StorageServer="StorageServer_Name";MediaServer="MediaServer_Name"
8/26/2015 8:41:39 AM - restored image "ClientName"_1440178202 - (access to the client was not allowed(59)); restore time 0:00:04
8/26/2015 8:41:39 AM - Warning bprd(pid=1693) Restore must be resumed prior to first image expiration on Mon Sep 21 19:30:02 2015
8/26/2015 8:41:39 AM - end Restore; elapsed time: 0:00:04
MS-Windows policy restore error(2808)

What I've verified:

Host Propeties:

Master Server have all media & remote console on Additional Servers list

Media Servers have all media & remote console on Additional Servers list

Client have all media & remote console on Additional Servers list

Restore to the source place (original) is succesfully completed(0), but the same error is existing in logs

Problem existing for Windows & Linux clients. I don't check NDMP, SQL or VM yet.

Hello all

I have SLP configured to replicate DC backups on DR appliance,Now i want to verify the backups replicated on DR site appliance.

need help , ehich command will show me the required output .

like: backup policy, date , client , data selected etc......

We have configured new 5230 appliance recently and SAP Online backup and Oracle Archive logs backup.

i want to verify or view the contenet backuped up by these policies.

like client wise list of backuped up archive logs, list of all backuped up archive logs from-to date.

i have never used SAP agent backup and want to confirm that we are not missing any logson production

thank you in advance...

Hi there,

I've got a netbackup appliance 5230 software version 2.6.1.1. I wanted to migrate it to 2.6.1.2 but I realized there is a "clean up work in post-upgrade" since I updated it time ago and I can't download the new version. I tried to cancel it using putty from Manage>Software but I'm not able to find out how to do that.

How can I stop it? Is there any risk?

Thanks in advance for your help.

Hi,

We have a 5230 running 2.6.0.2 and are trying to install more recent patches on it. The first available patch is SYMC_NBAPP_update-2.6.0.3-1.x86_64.rpm. When we check the DownloadProgress, it says its stopped. Any ideas why this would be so?

Thanks.

Fozzie

Hi All, 

This is to share with you the Long pending issue which we faced in our environment for 6 months . Our Duplication Jobs started running slow and we started seeing backlog of Duplication jobs building up on daily basis which went up to 500 TB.

Earlier Setup :-

Duplication Jobs Window - 24x7 

Replication Jobs Window - 24x7 

Storage Unit groups Used for Disk Pool Storage units and Tape Storage units.

Netbackup Appliance 5230 ( 2.6.0.2 )- 1 Master Appliance , 1 Media Appliance  in Primary Site , 1 in Remote site for DR.

Netbackup Version - 7.6.0.2.

We started seeing Backlog increase slowly which began to increase to huge size over the period of few months. Backups also were running slow and Replication also went slow. Overall Appliances Performance became very slow.

Case raised with Symantec and worked with Backline To resolve this Performance issue.

Did Data Collects , Logs collected and Sent to Symantec multiple Times.

Actions Taken:

1. Replaced predictive disk failures for 2 disks in Master appliance on two occasions.

2. Upgraded Netbackup patch to 7.6.0.4

3. Changed the NUMBER_DATA_BUFFERS and NUMBER_DATA_BUFFERS_DISK to 32 to avoid long delays.

4. Broke the Stu Group and Started using Netbackup Disk Storage Unit and Tape Storage Unit for Backup and Duplication respectively.

5. Added Alternate read server in SLP as same as the one used for backup to overcome Data travelling from appliance to other for duplication to tape.

6. /usr/openv/lib/ost-plugins/pd.conf  changed from PREFETCH_SIZE = 33554432  to PREFETCH_SIZE = 67108864

7. /disk/etc/puredisk/contentrouter.cfg  changed from PrefetchThreadNum=8   to PrefetchThreadNum=16

8. Changed the Max duplication to 5 TB and Min to 500 GB

9. Changed the Replication window and Duplication window such that they dont Overlap. 

10. Upgraded the Appliances BIOS and RAID Software

11. Upgraded the Netbackup software to 7.6.1.2 Version

Now After the Upgrade to 7.6.1.2 Version , The performance has improved Drastically and we are seeing Backlog decreasing rapidly with 50TB per day using 10 Tape drives.

Replication performance has also increased and Backups are completing well within time.

Cheers and thanks to Symantec Support and all others who helped us in this issue.

In my environment we have to netbackup appliances in to different locations where on replicates to the other. The issue is that all the other metrics match between the two appliances pure disk and Advanced Disk but pure disk disk pool used capacity does not have the same number and it should. Server 22 used pure Disk capactity is 38,318.494.13 MB and the percentage disk pool usage is 75.92, now with server 24 the pureDisk disk pool used capacity is 33,863,213.09 MB and the Percentage of the disk pool used is 67.09 but they both have hav a disk pool usable size of 50,471,198,73.  We contacted netbackup and they did not find any orphan images. now running a images on disk report. 

I also uploaded a copy of the disk pool capacity report,

If Anyone have any useful information I would greatly appreciate it,

Thanks in advance 

Hi,

Recently added and configured de SNMP Traps on the appliance and all hardware test were OK. The only problem is the software trap that i don't receive anything. I Stopped all process on Appliance and didn't appear any trap.
I have Launched a Backup that finally finish with error 6 and neither appear any trap.

The appliace is a 5230 with Netbackup 7.6.0.4

Regards

Hello.

i need a script for restore a virtual machine using bprestore with a different name.

i need an automatic restore with cron in appliance.

somebody has a script for run this?

Thanks.

All - I have had recurring issues with MSDP pools going down during periods of high usage.  Per a number of Technote recommendations as well as forum discussions, I raised these parameters on my appliances (5220 running 2.6.1.2) from 1800 to 3600.

This has cut down the number of "Disk Volume: PureDiskVolume Down" alerts, but has not eliminated them.

My question - does anyone know for sure if 3600 is the maximum value.  It *appears* from discussions that it may be the max, but I was hoping someone at Symantec could verify.

If it is not the max, perhaps I could bump it up to 4500 and see if it eliminates my PureDisk Volume Down states for good...

Hi troops,

IHAC who found one of the two 5220 2.6.1.1 appliance turned off twice and he had to power it off from the display since IMPI was not responfing either.

They opened a case with Symantec but since in the logs there was nothing relevant, Support could not provide a RCA. I looked at the logs myself and apart from the gap in the messages logs I did not find any specific errors.

Have you ever seen this ?

Below is Support's responce and the messages log, the carsh must have occurre on the 29th August at about 21.42.01

var messages
****************
Aug 29 21:42:01 nbami-5220 smbd[745]: [2015/08/29 21:42:01,  0] printing/print_cups.c:463(cups_async_callback)
Aug 29 21:42:01 nbami-5220 smbd[745]:   failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL
Aug 31 08:34:11 nbami-5220 syslog-ng[6216]: syslog-ng starting up; version='2.0.9'
Aug 31 08:34:11 nbami-5220 SMmonitor: SMmonitor started. PID=6243
Aug 31 08:34:12 nbami-5220 logger: sisids.init: Using driver version 2.6.32.43/sisfim-x86_64-default.ko
Aug 31 08:34:15 localhost StorageArray: ESM AutoSync Mode = Enabled, started on 8/31/15 8:34 AM
Aug 31 08:34:15 nbami-5220 syslog-ng[6216]: Configuration reload request received, reloading configuration;

Symantec Support reply:

*****************************

• Appliance Details: 

Compute Node nbami-5220 

NetBackup Model = 5220 

Nbapp-release = 2.6.1.1 

Serial Number = SYM1000789 

Bios Version = S5500.86B.01.00.0057.031020111721 

Firmware = 2.120.63-1242/ 1.41.372-2527 

\\pun-evidence.pun.spt.symantec.com\evidence\pun\62\09190462\2015-07-29\ 





• Node does not have any errors. -> Time Monitoring Ran: Mon Jul 27 2015 13:01:26 UTC 



• There is nothing logged in the messages log since Jul 25 07:24:01 and Jul 26 19:42:50 



Jul 25 07:24:01 nbami-5220 /usr/sbin/cron[7188]: (root) CMD (PATH=/opt/VRTSperl/bin:/sbin:/usr/sbin:$PATH; export PATH; . /opt/NBUAppliance/db/nbappdb_env.sh > /dev/null 2>&1; /opt/NBUAppliance/bin/perl -I/opt/NBUAppliance/scripts/ /opt/NBUAppliance/scripts//hwmon/callhome.pl > /dev/null 2>&1) 

Reboot occurred here 

Jul 26 19:42:50 nbami-5220 syslog-ng[6285]: syslog-ng starting up; version='2.0.9' 



Raid Card FW Term Log shows during that time CC check was running: 

\\pun-evidence.pun.spt.symantec.com\evidence\pun\62\09190462\2015-07-29\DataCollect\SYM1000789\Raid-Card-FW-Term-Log_07-27-2015_12.55.55.log 

07/25/15 7:14:03: EVT#93269-07/25/15 7:14:03: 94=Patrol Read progress on PD 17(e0x18/s16) is 69.99%(14699s) 

07/25/15 7:15:13: EVT#93270-07/25/15 7:15:13: 65=Consistency Check progress on VD 00/0 is 10.19%(15313s) 

07/25/15 7:15:53: EVT#93271-07/25/15 7:15:53: 65=Consistency Check progress on VD 01/1 is 28.60%(15353s) 

07/25/15 7:18:07: EVT#93272-07/25/15 7:18:07: 65=Consistency Check progress on VD 01/1 is 28.85%(15487s) 





• Alarm-Log_07-27-2015_12.55.55.log shows many repeated messages like below 

137 06/30/2015 14:15:29 Voltage #0x16 Upper Non-critical going high 

138 06/30/2015 15:34:19 Voltage #0x1c Upper Non-critical going high 



155 06/30/2015 18:22:34 Voltage #0x1c Upper Critical going high 

156 06/30/2015 18:22:51 Voltage #0x1c Upper Critical going high 



197 06/30/2015 20:11:16 Voltage #0x1c Upper Critical going high 

198 06/30/2015 20:13:13 Voltage #0x1c Upper Critical going high 



Getting Logged everyday till 13th July: 

e36 07/13/2015 03:54:37 Voltage #0x1c Upper Critical going high 

e37 07/13/2015 03:54:46 Voltage #0x1c Upper Critical going high 





• Checked on another customers machine. 

# ipmitool sdr list -verbose 

Sensor ID : BB +3.3V (0x16) 

Entity ID : 7.1 (System Board) 

Sensor Type (Analog) : Voltage 



Sensor ID : BB -12.0V (0x1c) 

Entity ID : 7.1 (System Board) 

Sensor Type (Analog) : Voltage 



30 

Requested for below outputs from customer 

# ipmiutil fru > /tmp/ipmi_events/ipmi_events fru.out 

# ipmiutil fru > /tmp/ipmi_events/ipmi_events fru.out 

# ipmiutil health > /tmp/ipmi_events/ipmi_events_health.out 

# ipmiutil sensor > /tmp/ipmi_events/sensor.out 

# ipmiutil sel > /tmp/ipmi_events/sel.out 

# ipmitool sdr list –verbose > /tmp/ipmi_events/sd_list_verbose.out 

# ipmitool sdr elist full > /tmp/ipmi_events/sdr_elist_full.out 

# ipmitool sdr list compact > /tmp/ipmi_events/srd_list_compact.out 

# ipmitool chassis status 

# ipmitool mc selftest 









3/8 



Customer confirmed that the backups are working fine and operation is normal but one LED on Power Supply is Blinking 

The backup operation are normal. One LED on Power Supply is blinking 







asked customer to confirm if the LED is blinking amber 

• LED is amber 

o Indication: The current power supply has failed. The other power supply in the unit is on. 

o Recommended actions: 

1. Check if the AC power cord is unplugged. 

2. Check if the AC is lost. Critical event causing an AC lost may include: over current protection (OCP), over voltage protection (OVP), over temperature protection (OVP). 



Customer mentioned that the LED is Blinking Green 

• LED is blinking green 

o Indication: AC present, only 12VSB on. Power supply is off or in cold redundant state. 





Customer provided DataCollect Log which is on fileshare ,, 

\\pun-evidence.pun.spt.symantec.com\evidence\pun\62\09190462\2015-08-03 





06/08 

checked datacollect and all hw components are showing ok 

checking further 



14/08 

emailed customer to know if the Appliance gone down again since last time.. these are old logs and nothing in particular seen during the time of hang 



- Also see message like below which may or may not have anything to do with the hung appliance that happened in July . 

messages/var/log/kernel_messages.out:May 14 11:53:38 nbami-5220 kernel: [ 1799.582514] :megasr[ahci]: port [1] encountered a hard error:[0x40000001] during NCQ operation, performing an explicit reset 

messages/var/log/kernel_messages.out:May 14 11:53:38 nbami-5220 kernel: [ 1799.582519] :megasr[ahci]: warning PortReset called for port[1] 

messages/var/log/kernel_messages.out:May 14 11:53:38 nbami-5220 kernel: [ 1799.594016] :megasr[ahci]: device on port:[1] online:[0x123] [0] milliseconds after reset 

messages/var/log/kernel_messages.out:May 14 11:53:38 nbami-5220 kernel: [ 1800.638618] :megasr[ahci]: converting NCQ hal packet [ffff880037876e48] to N-NCQ for error recovery owner:6 start block:0x681900 

messages/var/log/kernel_messages.out:May 14 11:53:38 nbami-5220 kernel: [ 1800.638627] :megasr[ahci]: port [0x1] is paused for read log ext 

messages/var/log/kernel_messages.out:May 14 11:53:39 nbami-5220 kernel: [ 1800.649104] :megasr[ahci]: port [0] encountered a hard error:[0x40000001] during NCQ operation, performing an explicit reset 

messages/var/log/kernel_messages.out:May 14 11:53:39 nbami-5220 kernel: [ 1800.649107] :megasr[ahci]: warning PortReset called for port[0] 

messages/var/log/kernel_messages.out:May 14 11:53:39 nbami-5220 kernel: [ 1800.660604] :megasr[ahci]: device on port:[0] online:[0x123] [0] milliseconds after reset 

messages/var/log/kernel_messages.out:May 14 11:53:39 nbami-5220 kernel: [ 1801.705206] :megasr[ahci]: converting NCQ hal packet [ffff88003788c868] to N-NCQ for error recovery owner:4 start block:0x3621623a 

messages/var/log/kernel_messages.out:May 14 11:53:39 nbami-5220 kernel: [ 1801.705211] :megasr[ahci]: port [0x0] is paused for read log ext 

messages/var/log/kernel_messages.out:May 14 11:53:39 nbami-5220 kernel: [ 1801.705229] :megasr[ahci]: port [0x1] is restarted after read log ext 

messages/var/log/kernel_messages.out:May 14 11:53:39 nbami-5220 kernel: [ 1801.705637] :megasr[ahci]: port [0x0] is restarted after read log ext 

messages/var/log/kernel_messages.out:May 14 11:53:59 nbami-5220 kernel: [ 1819.537935] :megasr[ahci]: hal packet [ffff880037872bb8] owner:46 start block:0x1200 timeout detected. 

messages/var/log/kernel_messages.out:May 14 11:53:59 nbami-5220 kernel: [ 1819.537940] :megasr[ahci]: hal_pkt[ffff880037872bb8:ffff880037872bb8] in port[0] list [1] getting timed out 

messages/var/log/kernel_messages.out:May 14 11:53:59 nbami-5220 kernel: [ 1819.537945] :megasr[ahci]: hal_pkt[ffff880037872bb8:ffff880037851738] in port[0] list [2] getting timed out 

messages/var/log/kernel_messages.out:May 14 11:53:59 nbami-5220 kernel: [ 1819.537948] :megasr[ahci]: hal_pkt[ffff880037872bb8:ffff88003786e928] in port[0] list [2] getting timed out 

messages/var/log/kernel_messages.out:May 14 11:53:59 nbami-5220 kernel: [ 1819.537952] :megasr[ahci]: hal packet [ffff880037887f30] owner:46 start block:0x1200 timeout detected. 

messages/var/log/kernel_messages.out:May 14 11:54:32 nbami-5220 kernel: [ 1819.537956] :megasr[ahci]: hal_pkt[ffff880037887f30:ffff880037887f30] in port[1] list [1] getting timed out 

messages/var/log/kernel_messages.out:May 14 11:54:32 nbami-5220 kernel: [ 1819.537959] :megasr[ahci]: warning PortReset called for port[0] 



wikipedia 

Native Command Queuing (NCQ) is an extension of the Serial ATA protocol allowing hard disk drives to internally optimize the order in which received read and write commands are executed. 

This can reduce the amount of unnecessary drive head movement, resulting in increased performance (and slightly decreased wear of the drive) for workloads where multiple simultaneous read/write requests are outstanding, most often occurring in server-type applications. 







- messages log May 14 showed catalog volume full. 

messages/var/log/kernel_messages.out:May 14 17:38:25 nbami-5220 kernel: [22454.498786] vxfs: msgcnt 1 mesg 001: V-2-1: vx_nospace - /dev/vx/dsk/nbuapp/pdcatvol file system full (2 block extent) 





since there is nothing logged at the time of hang ,, unable to provide a root cause analysis. 

Its been 3 weeks since that the appliance is working fine hence customer gave consent to close the case . 

They will reference this case in future if happen to see the same scenario again.

Thanks for your help,

Francesco

Hello

This is in reference to the now-closed http://www.symantec.com/connect/forums/configure-entire-space-puredisk-appliance-5230-netbackup-7601

We are running a windows master server with NBU 7.6.1.2 with a 5230 appliance running 2.6.1.2 - the previous MSDP size was 64TB (the max prior to 7.6) - so we followed the procedure to resize it via the web console --- which we did from 64 to 70TB.

Restarted the appliance, the master, etc... yet the master continues to show the old size under Devices \ Disk Pools (64TB) - ran disk inventory, refresh, restarted appliance and master once again, still nothing. The appliance continues to show the new size under the web console as well as via the CLISH.

Have we missed something?

Hello, 

I have some Duplication jobs that failed because the remote appliance was shut down for maintenance.

They now restart every X time and will fail again until the remote appliance is up, fine, that's the expected behavior in normal case.

My question is how to stop them from restarting ? I have no Cancel Job possible, I don't see them in a sort of Pending Retry state...

Is there any command line to list the Jobs pending a restart and stop them ? (I'm ok with elevation etc...)

Appliance is a 5220, running Ver. 2.6.1.2

Thank you

Hi

Just wondering if anybody was successfully monitoring Netbackup Appliances using SCOM 2012 R2.

I tried using the SCOm Discovery to monitor one of ours, treating it just like a linux server, and received an error saying that the server refused to start a shell/command.

Not necessarily after a resolution to the error, but would be interested to know whether anybody has got this sort of monitoring working.

Thanks

Ian

hi,

can some one share the path where i download the "Java 7.6.1 Administration Console"?

Netbackup Appliance deduplication/re-hydration problem

Netbackup Master Server Version: 7.5.0.7
Netbackup Appliance 2530, Version 2.5.4
Netbackup Appliance Media Server Version 7.5.0.7

Backup Type: Exchange DB Backup (DAG) with GRT
Client OS/Version: Windows Server 2008 RT, Netbackup

Help! One of our Netbackup appliance hosts Exchange Database backup (DAG) with GRT... Backups do run with good speed and without any issues during normal circumstances... These backups are set to duplicate to tape (managed via SLP), everyweek... As soon as the SLP starts to copy the data from MSDP to tape, the backups' speed becomes haywire and runs extremely slowly.. As soon as I kill off the duplication job, the backups revert to normal again...

Another problem is that, whenever the duplication run the exchange backups fail with error code 24 or 42 (Network Write error or Network Read error).. This doesnt happen during normal backups... Please help on this.

Also, it would be highly helpful if someone could explain de-duplication/dehydration workflow and duplication to tape workflow (via SLP)...

Hi,

We are running several NBU 5230 Appliances (Current version 2.6.1.1)

From support we have heard that our (RAID) firmware and BIOS levels are not current.

My questions:

• What RAID firmware should we be running?
• What BIOS level should the 5230 units have?
• Do disk firmware levels also need updating and what level should they have?
• If RAID firmware is updated, should drivers be running a certain version as well? If yes, what version is best?
• Where can we obtain these updates?
• If we would go to 2.6.1.2, will any firmware/BIOS levels be updated during the upgrade process? (Probably not, I suspect)
• Has anybody performed these upgrades and encountered any issues?

Thanks for any help!
 

Fred