Data Backup and Recovery

0001-855 Admin error: No host interface can see storage system si9068

urs_jutzi
2,981 Views

Hi,

We are currently making a first test with oracle snapmanager for oracle 2.2.0.

The database to be backup is a 11g version running on Redhat 5.

The backup procedure fails with "0001-855  Admin error: No host interface can see storage system si9068"

Accordind to:

http://communities.netapp.com/message/8853

we check the network but we dont find something wrong .

Any idea ?

Rgds

[root@si1464 INT etc]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:21:5E:98:E7:04
          inet addr:10.88.26.140  Bcast:10.88.26.255  Mask:255.255.255.0
          inet6 addr: fe80::221:5eff:fe98:e704/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:21677205 errors:0 dropped:1279642 overruns:0 frame:0
          TX packets:24972750 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10138187559 (9.4 GiB)  TX bytes:20755477997 (19.3 GiB)
          Interrupt:193 Memory:92000000-92012800

eth1      Link encap:Ethernet  HWaddr 00:21:5E:98:E7:06
          inet addr:74.53.96.18  Bcast:74.53.96.255  Mask:255.255.255.0
          inet6 addr: fe80::221:5eff:fe98:e706/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:239172 errors:0 dropped:10161 overruns:0 frame:0
          TX packets:585 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15371403 (14.6 MiB)  TX bytes:37548 (36.6 KiB)
          Interrupt:146 Memory:94000000-94012800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:80218 errors:0 dropped:0 overruns:0 frame:0
          TX packets:80218 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:32419619 (30.9 MiB)  TX bytes:32419619 (30.9 MiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

usb0      Link encap:Ethernet  HWaddr 02:21:5E:9C:E6:E7
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@si1464 INT etc]# cat /etc/hosts
127.0.0.1       localhost.localdomain           localhost
10.88.26.140    si1464.corproot.net             si1464
74.53.96.18     si1464-b
172.28.114.175  si9068.intitoper.local si9068

--SMO-13046 [INFO ]: Operation GUID 8ad89a0c289564de01289564e21d0001 starting on Profile TEST_PROFILE

--SMO-13505 [INFO ]: Snapdrive verification passed.

--SMO-12136 [INFO ]: ORACLE_HOME "/opt/oracle/product/ora11107ee" is version 11.1.0.7.0.

--SMO-13506 [INFO ]: SQLPlus verification for database SID "TT" passed.  Environment: [ORACLE_HOME=/opt/oracle/product/ora11107ee]

--SMO-12101 [INFO ]: Querying database version.

--SMO-13507 [INFO ]: JDBC verification for "admin@TT/si1464.corproot.net:1521" passed.

--SMO-13508 [INFO ]: RMAN verification using control file passed.

--SMO-07127 [INFO ]: Locked database for SnapManager operations - created lock file "/opt/oracle/product/ora11107ee/dbs/.sm_lock_TT".

--SMO-07431 [INFO ]: Saving starting state of the local database instance: OPEN.

--SMO-07100 [INFO ]: Placing database "TT" into online backup mode.

--SMO-08005 [INFO ]: Beginning snapshot with name smo_test_profile_tt_f_h_1_8ad89a0c289564de01289564e21d0001_0 for filesystem(s) [/oradata/TT/part01] and device(s) [].

--SMO-08020 [INFO ]: Querying for snapshot "si9068:/vol/si9068_01:smo_test_profile_tt_f_h_1_8ad89a0c289564de01289564e21d0001_0".

--SMO-08022 [INFO ]: Finished querying for snapshot "si9068:/vol/si9068_01:smo_test_profile_tt_f_h_1_8ad89a0c289564de01289564e21d0001_0".

--SMO-08006 [INFO ]: Created snapshot with name smo_test_profile_tt_f_h_1_8ad89a0c289564de01289564e21d0001_0 for filesystem(s) [/oradata/TT/part01] and device(s) [].

--SMO-07101 [INFO ]: Taking database "TT" out of online backup mode.

--SMO-07106 [INFO ]: Forcing log archival on database "TT".

--SMO-07107 [INFO ]: Backing up control file for database "TT" to "/oradata/TT/part01/TT/SMOBakCtl_1273816768407_0".

--SMO-07107 [INFO ]: Backing up control file for database "TT" to "/oradata/TT/part01/TT/SMOBakCtl_1273816769250_1".

--SMO-07107 [INFO ]: Backing up control file for database "TT" to "/oradata/TT/part01/TT/SMOBakCtl_1273816770085_2".

--SMO-08005 [INFO ]: Beginning snapshot with name smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0 for filesystem(s) [/oradata/TT/part00, /oradata/TT/part01] and device(s) [].

--SMO-08020 [INFO ]: Querying for snapshot "si9068:/vol/si9068_01:smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0".

--SMO-08022 [INFO ]: Finished querying for snapshot "si9068:/vol/si9068_01:smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0".

--SMO-08006 [INFO ]: Created snapshot with name smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0 for filesystem(s) [/oradata/TT/part00, /oradata/TT/part01] and device(s) [].

--SMO-07108 [INFO ]: Deleting backup control file "/oradata/TT/part01/TT/SMOBakCtl_1273816768407_0".

--SMO-07108 [INFO ]: Deleting backup control file "/oradata/TT/part01/TT/SMOBakCtl_1273816769250_1".

--SMO-07108 [INFO ]: Deleting backup control file "/oradata/TT/part01/TT/SMOBakCtl_1273816770085_2".

--SMO-08025 [INFO ]: Beginning to connect filesystem [/oradata/TT/part00] from snapshot smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0.

--SMO-08026 [ERROR]: Error connecting filesystem [/oradata/TT/part00] from snapshot smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0. SMO-12111: Error executing snapdrive command "/usr/sbin/snapdrive snap connect -fs /oradata/TT/part00 /opt/NetApp/smo/mnt/_oradata_TT_part00_smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001 -snapname si9068:/vol/si9068_01:smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0 -nopersist -autorename -noreserve": 0001-855 Admin error: No host interface can see storage system si9068

--SMO-13032 [FATAL]: Cannot perform operation: Backup Create.  Root cause: SMO-08026: Error connecting filesystem [/oradata/TT/part00] from snapshot smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0. SMO-12111: Error executing snapdrive command "/usr/sbin/snapdrive snap connect -fs /oradata/TT/part00 /opt/NetApp/smo/mnt/_oradata_TT_part00_smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001 -snapname si9068:/vol/si9068_01:smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0 -nopersist -autorename -noreserve": 0001-855 Admin error: No host interface can see storage system si9068

--SMO-08012 [INFO ]: Beginning deletion of snapshot si9068:/vol/si9068_01:smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0.

--SMO-08013 [INFO ]: Deleted snapshot si9068:/vol/si9068_01:smo_test_profile_tt_f_h_2_8ad89a0c289564de01289564e21d0001_0.

--SMO-08012 [INFO ]: Beginning deletion of snapshot si9068:/vol/si9068_01:smo_test_profile_tt_f_h_1_8ad89a0c289564de01289564e21d0001_0.

--SMO-08013 [INFO ]: Deleted snapshot si9068:/vol/si9068_01:smo_test_profile_tt_f_h_1_8ad89a0c289564de01289564e21d0001_0.

--SMO-07433 [INFO ]: Returning the local database instance to its initial state: OPEN.

--SMO-07131 [INFO ]: Unlocked database for SnapManager operations - removed lock file "/opt/oracle/product/ora11107ee/dbs/.sm_lock_TT" on host si1464.corproot.net.

--SMO-13039 [INFO ]: Successfully aborted operation: Backup Create

--SMO-13048 [ERROR]: Backup Create Operation Status: FAILED

--SMO-13049 [INFO ]: Elapsed Time: 0:02:05.774

3 REPLIES 3

jessick
2,981 Views

That error is more likely the result of an issue with your hba/driver or

your SnapDrive for Unix configuration.

One note. For Oracle 11g you need to be running at least SMO 3.0.2 if

you have 11gR1 instances of Oracle.

If you are using 11gR2, then you need SMO 3.0.3.

In both cases, those SMO versions require SDU 4.1.1.

Please check the NetApp Support Matrix for the details of your specific

RHEL 5 Update for use with SnapDrive and SMO:

http://now.netapp.com/matrix/mtx/login.do

You can also download and run the SnapDrive ConfigChecker from the NOW

toolchest and run it. It will tell you if your host config is supported

by SnapDrive.

>From there, pay close attention to the SDU IAG and make sure your

snapdrive.conf file is properly configured and that the access method

(http or https) to the NetApp Storage is as you expect it to be. Lastly

make sure snapdrive config set ... runs correctly.

If you are still having problems, contact the NetApp Support Center and

open a case.

Provide the snapdrive.dc and the smo operation dump output from your

system at that time.

-Mark

ogra
2,981 Views

another quick way is to check if you running with supported HBA firmwares, they cause loads of pain.

urs_jutzi
2,981 Views

Hi, I found the solution for the problem - ping ICMP was dropped by the firewall, after enabling this the snapdrive snap connect is working fine

15:48:13 05/17/10 [f7f5cb90]v,2,17,Filer::ping , ip:10.88.26.140, alive: false

15:48:13 05/17/10 [f7f5cb90]i,2,6,Operation::addErrorReport: (1) Filer:172.28.114.175 18 1855:No host interface can see storage system 172.28.114.1750 [f7f5cb90]?,2,2,Job tag: M3Z5zxlPr7

15:48:13 05/17/10 [f7f5cb90]i,2,6,Operation::addErrorReport: (2) ???:SnapOperation 18 1869:Unable to check if NFS is enabled on storage system

thanks for your support

regards Urs

Public