Problem with Backup on SAN

[Bhavin Shah]

Dear All,

I hv got 4 HP-UX(L2000) 1 running SAP R/3 Database, 2 R/3 Application servers & 1 running SAP BIW(Database+Application) & 1 HP netserver LH6000 running SAP APO(Database+Application), a HP Surestore 2/20 DLT Library & a EMC Clariion 4500 SAN box all connected to a fibre switch. Database is orcale. I have got 350GB of R/3 Data, 150GB of BIW & 80GB of APO on SAN box. Since last 2 weeks by R/3 database backup is getting failed(Not at any specific time) earlier it was intermittent. At the same time mt BIW & APO backup is going smoothly on the same library.

There is no zoning configured in the EMC switch. I have also checked the R/3 database for consistency that is ok.

There is some error i'm getting is syslog file, I'm not sure what it is.

I'm attaching the syslog file.

Pl. revert ASAP.

Regards
Bhavin Shah

[Paul R. Dittrich]

I think the clues are in your syslog file:

file: /cm/nav/prod/share/raid/src/rgfact.cxx, line: 2258: Requested RAID group does not exist

Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 96141342 -r /storage/events/disks/default/0_4_0_0.8.0.1.0.0.1 -n 96141365 -a

To obtain a list of currently monitored resources, execute the following: /opt/resmon/bin/resdata -M 1998375097

Paul

[Eugeny Brychkov]

Bhavin,
you're telling about fibre switch. Then why host log was taken from works in private loop? It should work in fabric. There're issues with loop backups - if someone on the loop issues bus reset command then all devices on the loop got reset. And, of course, all backups aborted/failed.
So please review your SAN configuration.
Note: changing from loop to fabric mode will change harware paths to all FC resources, and thus SAN-residing VGs may not activate after change. Use vgexport (with map file) and vgimport
Eugeny

[Michael Steele_2]

This is the syslog.log file after reboot or panic? Could you attach the OLDsyslog.log file?

While reading this the complaints begin with nettl at run level 2. This indicates that you're not even all the way up before the problem begins with your LAN. Please run this command for me:

nettl -LN -f /var/adm/nettl.LOG* >file

...and attach or search for disaster, error, cable, etc.

Also attach your /etc/rc.log file and inspect this for errors.

As well as your inetd.conf file. What is line 42 and 720 (???)

Off hand, your inetd.conf file is corrupt. Compare it to a backed up tape version and the /usr/newconfig/etc/inetd.conf file.

Also try:

cat /etc/inetd.conf | col -b > file

Compare file and inetd.conf for control char.

When was your last reboot before this?