Ejecting tapes manually from a tape library connected to Netbackup

Today i have ejected tapes from my tape library i am sharing the procedure with you all.

1) From the Netbackup Admin Java console click on media and choose which tapes you wish to eject from the library and the right click on the tape and select " Eject Volumes From Robot "

Now select to eject 

You may see message like "media eject in transit" or "in transit".

Once all the tapes are put in the I/O station, you will see a message on the console "Remove ejected media from media access port. Do you wish to continue with the eject?"

Do not click anywhere (Clicking Yes Before removing the tape from the library will occur error which may cause ROBOT to freeze). Go to the library and remove all the tapes from I/O station. Once done, click "Yes" on the message.

CAUTION :- Clicking Yes Before removing the tape from the library will occur error which may cause ROBOT to freeze

In brocade to list all zones to which a WWPN belong to

Today one of my Systems admin want to know what are all the Zones to which a WWPN of particular server HBA belong, this can be obtained by the command below in Brocade

To see all the zones to which the WWPN belongs to

#nodefind WWPN 

e.g: nodefind 10:37:24:45:30:22:10:12:A2 


We will be having one alias name for this say it as "LINUX_HBA2"



Then to see list of all the zones to which the above WWPN belongs

#cfgshow | grep  "LINUX_HBA2" 

Netbackup Error 830 All Compatible Drive Paths are Down

Earlier today i had a request from my client to Snapvault one of our DB Volume and backup it to tapes Via NDMP in order to send those tapes to offsite. When i was done with Snapvaulting i was about to kick start the NDMP backup but backup failed with the below error :(

 Error 

NBU status: 830 , EMM status : All Compatible Drive Paths are Down Failed to get status code information (830).

Solution

As a part of troubleshooting i have checked the policy later i found i have selected the wrong media server which was not configured to this particular filer :) The backup kick started once after changing the media server :)

1.    Check the Server Policy.

2.    Policy -> Policy name -> Policy Properties.

If still doesn't help try the below steps :- 

     1.    Check Policy Storage Media server available or not.

     2.    Login the client Server.

3.    Restart the netback up service.

Appreciation from my Employer :)

Not able to add Filer in to Netapp On command System Manager

If you are not able to add your filer in to the Netapp on command System manager probably your SSL was not configured , Once you configure it you will be able to add the filer. This is what i have faced today.

Configuring SSL

Filer1> secureadmin setup ssl
Country Name (2 letter code) [US]: IND
State or Province Name (full name) [California]: Andhra Pradesh
Locality Name (city, town, etc.) [Santa Clara]: Hyderabad
Organization Name (company) [Your Company]: Shaik
Organization Unit Name (division):  IT
Common Name (fully qualified domain name) [filer1.Sahik.corp]:
Administrator email:
Days until expires [5475] :
Key length (bits) [512] :
Wed Jul  3 14:00:42 IST [secureadmin.ssl.setup.success:info]: Starting SSL with new certificate.

Netapp DSM error " "Internal Error: Access is Denied" during installation on Windows 2008 R2

Today i have faced this error while installing my DSM on one of my windows 2008 R2 server i was scratching my head to find out the reason as the same user account worked well with SNAP DRIVE installation on the same server but DSM failing with Acces Denied Error , Later after checking with netapp i found out this was a bug and has to follow work around to fix this

Work Around 

There are two workarounds for this issue:

1) Run the installation from an elevated command prompt.  This is done by clicking

 Start, then right-clicking on Command Prompt and selecting "Run as Administrator."

 Once presented with a command prompt, you may execute the installation package

 by navigating to the directory containing the package and entering it on the 

 command line. 

C:\desktop> msiexec /a  <netapp Mpio Pkg>

/a  --> to run the installation as Administrator 

2) Disable User Access Control.  Administrators can do this by going into the

 Control Panel, selecting User Accounts, then "Turn User Account Control on or off".

 In the next dialog, uncheck the box stating "Use User Access Control (UAC) to help

 protect your computer" then click OK.

Please Note :- Modifying the second option requires a reboot
And Of course you must reboot once done with you installation for your NETAPP MPIO to detect your LUNS.

Netapp Reference link :- http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=312358

Not able to Access Netapp Filer Via SSH PUTTY

If you have issue accessing Netapp filers using SSH Putty. When  you try to log  into the filer with a Putty session would get an access denied or the Putty session will close. Later i came to know that OnCommand System Manager setting that was caching my password. Once i clear the cache and un select the box “Enable Password Caching “ then I am able to access filer through my SSH.

      

      1.   Open OnCommand System Manager in browser and login to filer

2.   In the top left corner you will have option called “TOOLS” select it.

3.   Now click on Clear Existing Passwords and save it.

Now you will be able to access the filer.

Netbackup Unable to login, Status 525 Cannot connect to the NB-Java authentication

If you see the error above stating VNETD failed, but  you are able to see the VNETD service running on your master server wondering what went wrong ?? 

It means your VNETD service got freezed now you need to restart the VNETD service then only you will be able to access your java console.

What Is the option called Minra in Netapp

MINRA is nothing but you can control your "prefetch" wen you enable this option the filer performs minimal file read-ahead on the volume. By default, this option is off which means your filer always performs prefetch if any data updated. If you enable this option it may degrade your filer performance as "prefetch" will be off causing the data not available readily in the CACHE.

Netbackup Oracle DB backup failing with error 6

Error 6 is a generic DB backup error which cause the DB jobs to fail. To further troubleshoot this we have to first look in to the RMAN log and see what its saying , I mean find out the error. If your RMAN log showing the same as below and your Oracle version is V10203. Then  follow the troubleshooting steps below to fix this.

RMAN Log:- 

Script /opt/rman_script/DBold_oracle_full.sh

==== started on Tue May 28 14:59:30 SGT 2013 ====

RMAN: /OraBase/V10203/bin/rman

ORACLE_SID: DBold

ORACLE_USER: oracle

ORACLE_HOME: /OraBase/V10203

NB_ORA_FULL: 1

NB_ORA_INCR: 0

NB_ORA_CINC: 0

NB_ORA_SERV: DBMSTR

NB_ORA_POLICY: DBold_oracle_daily

Full backup requested

Sun Microsystems Inc.   SunOS 5.10         Generic                January 2005

You have new mail.

RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> RMAN> ed.

connected to target database: DBold (DBID=990954548)

connected to recovery catalog database

RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33>

allocated channel: ch00

channel ch00: sid=136 devtype=SBT_TAPE

channel ch00: VERITAS NetBackup for Oracle - Release 6.0 (2007070504)

sent command to channel: ch00

Starting backup at 28-MAY-13

released channel: ch00

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of backup command at 05/28/2013 14:59:36

RMAN-03014: implicit resync of recovery catalog failed

RMAN-06004: ORACLE error from recovery catalog database: RMAN-20035: invalid high recid

RMAN>

Recovery Manager complete.

Script /opt/rman_script/DBold_oracle_full.sh

==== ended in error on Tue May 28 14:59:36 SGT 2013 ====

Steps to Troubleshoot:-

1.       Backup the existing user using Oracle exp.

exp userid=Dbusr/Dbusr file=DBOld_catalog.dmp

2.       Backup the dump file using NetBackup, set to permanent retention.

3.       Disable login for the original user.

sqlplus ‘/ as sysdba’

alter user DBusr account disable;

4.       Create a new user on the database, eg rmanuser

To create a New User :- 

1. Set up an Oracle database (with the user datafiles and listener).

2. Create a tablespace for the RMAN catalog (modify the path and instance name of the

RMAN catalog database where required):

SQL> create tablespace RMAN_TAB datafile

'D:\Oracle\Oradata\RCATP\TAB01\RMAN_TAB01.dbf' size 300m;

Tablespace created.

SQL>

3. Create the RMAN user as a schema owner for the RMAN tablespace.

SQL> create user rmanuser identified by rmanuser default

tablespace RMAN_TAB temporary tablespace TEMP;

User created.

SQL>

4. Grant unlimited quota to the RMAN user on the RMAN tablespace.

SQL> alter user rmanuser quota unlimited on RMAN_TAB;

User altered.

SQL>

5. Grant the recovery_catalog_owner permission.

SQL> grant recovery_catalog_owner to rmanuser;

Grant succeeded.

SQL>

6. Create the RMAN objects and schema.

D:\Oracle\Product\11.2.0\BIN>rman catalog rmanuser/rmanuser@rcatp

Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jan 27

17:05:14 2011

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All

rights reserved.

connected to recovery catalog database

RMAN> create catalog;

recovery catalog created

RMAN>

5.       Register the target database to the catalog.

On DBOld database server:

su - oracle

DBOld

rman target / catalog DBNWusr/DBNWusr@(rman catalog instance)

register database;

To register a database

Connect into RMAN.

D:\Oracle\Product\11.2.0\BIN>rman target / catalog

rmanuser/rmanuser@rcatp

Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jan 27

17:10:17 2011

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All

rights reserved.

connected to target database: ORADB1P (DBID=2937678513)

connected to recovery catalog database

RMAN>

2. Register the target database with the catalog.

RMAN> register database;

database registered in recovery catalog

starting full resync of recovery catalog

full resync complete

RMAN>

3. You can also list out the RMAN parameters.

.

RMAN> show all;

RMAN configuration parameters for database with db_unique_name

ORADB1P are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO

'%F'; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO

BACKUPSET; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; #

default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; #

default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT'

OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO

D:\ORACLE\PRODUCT\11.2.0\DATABASE\SNCFORADB1P.ORA'; # default

RMAN>

6.       Update all RMAN backup scripts to use the new username and password.

7.       Retry backup in NetBackup.