Follow by Email

Wednesday, July 31, 2013

Netapp Vol Copy Abort Error

Today when i was performing vol copy  on one of my volumes using command

Filer1> vol copy start -S Old_Volume New_Volume ( Destination volume should be in RESTRICT state )

-S --> to copy all snapshots as well

One of our user was accessing the filer and he issued the signal CTRL+C to stop some output on the filer  which aborted the vol copy operation , later i logged in to my On command system manager to check how much of data has been copied for that i tried to online the destination volume which was in restricted state but was not able to do it getting error as below according to the error if vol copy is aborted there is no way we can restart the copy again or online the same destination volume the only way is to destroy the destination volume and create a new and start the copy again.

Tuesday, July 30, 2013

What is the logic used by netbackup to freeze the media

Netbackup uses the parameters TIME_WINDOW and MEDIA_ERROR_THRESHOLD to determine if a media has to be frozen.

- Netbackup freezes media on the third time a error is ecountered in 12 hours on a media.
- Default Media Error threshold is 2 and time window for error is 12 hours

If you wish change above parameters can be tuned as follows

in Netbackup 6.x
nbemmcmd -changesetting -machinename <hostname>  -TIME_WINDOW <no. of hours>
nbemmcmd -changesetting -machinename <hostname> - MEDIA_ERROR_THRESHOLD <value>

If you wish to check the error files can be checked from 

Netbackup records the failure(write failure, position error) on every media server at the following location

On unix:
/usr/openv/netbackup/db/media and the file name is errors.
On Windows:
install_path\Netbackup\db\Media and the file name is errors.

Monday, July 29, 2013

Error while performing NetBackup LiveUpdate

I am trying to run LiveUpdate on my NetBackup server and it keeps failing with the following error log 
29/7/2013 10:34:55 AM - requesting resource
29/7/2013 10:34:55 AM - granted resource
29/7/2013 10:34:55 AM - started process RUNCMD (5956)
29/7/2013 10:34:55 AM - ended process 0 (5956)
29/7/2013 10:35:04 AM - Info nbliveup(pid=1556) Updating LiveUpdate Server location to:    
29/7/2013 10:35:13 AM - Error nbliveup(pid=1556) Error executing "C:\Program Files (x86)\Symantec\LiveUpdate\LUALL.EXE" -s -h "C:\Program Files\VERITAS\NetBackup\LiveUpdateHost.hst", stopping update. 
29/7/2013 10:35:23 AM - Info nbliveup(pid=1556) Start of the pack summary file:    
29/7/2013 10:35:23 AM - Info nbliveup(pid=1556) (09/28/11 11:52:32) Installed Veritas NetBackup 6.5.5 (6.5 Release Update 5) ()
29/7/2013 10:35:23 AM - Info nbliveup(pid=1556) 01/06/12 10:17:08 Installed Symantec NetBackup (7.1 Release Update 0 HotFix 2) (NB_71_0_2_H)
29/7/2013 10:35:23 AM - Info nbliveup(pid=1556) End of the pack summary file:    
29/7/2013 10:35:23 AM - Warning nbliveup(pid=1556) Directory C:\Program Files\VERITAS\NetBackup\Logs\LiveUpdate doesn't exist, cannot copy the installation logs  
29/7/2013 10:35:23 AM - Info nbliveup(pid=1556) EXIT STATUS 77       
execution of the specified system command returned a nonzero status(77)

NetBackup LiveUpdate apparently only checks for the "LiveUpdateHost.hst" file in the C:\Program Files\Veritas\NetBackup folder on your LiveUpdate server no matter if NetBackup is installed on said server or not. NetBackup is not required to be installed on your LiveUpdate server, but apparently, it still looks for this file in that path. In our case, we used a separate media server as the LiveUpdate server. NetBackup is still installed on the D: drive of the media server, so to fix the issue, I just created the same folder structure \Program Files\Veritas\NetBackup on the C: drive and copied the file from D:\Program Files\Veritas\NetBackup to the newly created C:\Program Files\Veritas\NetBackup folder. That fixed the first issue in bold above.
The 2nd issue in bold resulted from not having the upgrade packages unzipped correctly in the source folder on my LiveUpdate server. The documentation states that you need to unzip the files into the source folder, but it doesn't state that ALL files from ALL packages need to be unzipped into the SAME folder. I unzipped each one individually, which created a subfolder under the source folder, and the files resided under each subfolder. I had to move ALL of the files from each package's subfolder to the same source folder.
For example, if you have a source folder called C:\LiveUpdate and you unzip the package files for 32bit and 64bit Windows clients, you might end up with a "C:\LiveUpdate\32bit-client" folder and "C:\LiveUpdate\64bit-client" folder, with files from each package in their respective subfolders. You have to move the files under "32bit-client" to directly under C:\LiveUpdate, and the same for the files under "64bit-client" folder.

Wednesday, July 24, 2013

Vol Move Command in Netapp

Today i have faced a situation where i need to increase a size of a volume but i don't have enough space in that particular aggregate all that i can do now is move volume to another aggregate which is having enough space and then increase the volume size.

please remember these handful condition while performing the vol move 

Before you move a volume nondisruptively, you must be aware of the type of volumes you can move and the operations that might conflict with the volume move. The volume move does not start if the volume has unsupported settings or if there are conflicting operations.

  • Your FAS system or V-Series system must be running Data ONTAP 8.0.1 7-Mode or later.
  • You can move only one 7-Mode FlexVol volume at a time.
  • The volume must be online.
  • You cannot move the following types of volumes:
    • A root volume
    • A FlexClone volume
    • A FlexCache volume
    • A volume that is the destination of any replication relationship, such as volume SnapMirror or qtree SnapMirror
    • A volume that is a SnapVault destination
      Note: During a volume move, you must not initiate qtree SnapMirror or SnapVault relationships from the destination volume.
    • A read-only volume
    • A volume in a nondefault vFiler unit
    • A volume from a 32-bit aggregate to a 64-bit aggregate, or from a 64-bit aggregate to a 32-bit aggregate
  • The data in the volume must not be compressed using the data compression feature.
  • The source volume should not be exported to NFS or CIFS clients when the volume move operation is in progress.
    There is a small window of time when you can export the source volume over NFS or CIFS before the volume move enters the cutover phase. However, if you do so, the cutover phase might not be successfully completed. If the cutover phase is not completed, there is no disruption to SCSI clients because the volume move rolls back to continue with the data copy phase.
  • The source volume must be consistent.
  • The volume guarantee option must not be set to file.
  • Deduplication operations must not be running on the source volume.
    If deduplication is active, the volume move is paused and the cutover phase is not initiated.
    For more information about deduplication operation, see the Data ONTAP 7-Mode Storage Management Guide.
  • The following conflicting operations must not be running:
    • SnapRestore of the source volume or the containing aggregate
    • WAFLIron operation on the source or the destination aggregate
    • Active LUN clone split operations on the source volume
    • Revert operation on the storage system

We can nondisruptively move a volume from one aggregate to another within a storage system. You can continue to access data in the LUNs during the volume move.

  1. Start the volume move by entering the following command:vol move start srcvol dstaggr [-k] [-m | -r num_cutover_attempts] [-w cutover_window] [-o] [-d]
    srcvol specifies the source volume.
    dstaggr specifies the destination aggregate.
    -k retains the source volume after a successful move. The source volume remains offline.
    -m specifies that the volume move does not initiate automatic cutover. The system continuously runs updates and you can initiate manual cutover at any point during the volume move.
    num_cutover_attempts specifies the number of cutover attempts. The minimum number of cutover attempts is one and the default number of attempts is three. If cutover cannot be completed in the specified number of attempts, then the volume move is paused.
    cutover_window specifies the duration of the cutover window. The default and minimum value is 60 seconds.
    -o displays warning messages on the console and the operation continues.
    -d runs all the data copy phase checks. If any of the checks fail, error messages are displayed on the console and the operation is terminated.


If the volume move is successful, the destination volume retains the following:
  • Snapshot copies of the source volume
  • Attributes of the LUNs from the source volume in the corresponding LUNs in the destination volume

Monday, July 8, 2013

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

Saturday, July 6, 2013

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" 

Thursday, July 4, 2013

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 :(
NBU status: 830 , EMM status : All Compatible Drive Paths are Down Failed to get status code information (830).
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 :)

Wednesday, July 3, 2013

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.