Archive

Archive for the ‘NetApp’ Category

How to Access NetApp SnapShots

07/14/2010 Leave a comment

The following explains the process of accessing NetApp snapshots on a filer form a client machine.

Prerequisites: The volume option nosnapdir=off must be set. To check the nosnapdir option log into the CLI and run:

vol option volname

Snapshots without a qtree:

  1. From a Windows Client, Click Start > Run
  2. Enter the UNC \\filer\~snapshots
  3. Click ok or hit Enter
  4. The browser open presenting the available snapshots

Snapshots with a qtree:

  1. From a Windows Client, Click Start > Run
  2. Enter the UNC \\filer\qtree\~snapshots
  3. Click ok or hit Enter
  4. The browser open presenting the available snapshots
Categories: NetApp Tags:

Script NetApp SnapDrive Commands

06/22/2010 Leave a comment

To script NetApp SnapDrive commands you must use the “sdcli” or SnapDrive Command Line Interface. 

The sdcli commands consist of three input parameters, which must be specified in the correct order, followed by one or more command-line switches. You can specify the command-line switches in any order.  

Before You Begin

When you use the sdcli command-line utility on a Windows 2008 server, you must be logged in as Administrator, not as a user with administrative rights.  

Considerations

Command-line switches are case-sensitive. For instance, the -d switch refers to a single drive letter, while the -D switch refers to one or more drive letters separated by spaces.

Steps

  1. Using a host that has SnapDrive installed, select Start > Run.
  2. Type cmdin the dialog box entry field, and then click OK.
  3. After the Windows command prompt window opens, navigate to the directory on your host where SnapDrive is installed.Example C:  cd \Program Files\NetApp\SnapDrive\   
  4. Enter the individual command you want to run. Make sure to include all input parameters in the proper order and to specify both required and desired command-line switches in any order.Example sdcli disk disconnect -d R Alternatively, enter the name and path of the automation script you want to run. Example C:\SnapDrive Scripts\disconnect_R_from_host4.bat  
Categories: NetApp Tags: , ,

Move MOSS Propagation Index to Support SMMOSS 5.0

06/21/2010 Leave a comment

In order to support NetApp SMMOSS 5.0, the index file folder “propagationlocation” created on the Query server within a MOSS farm must be on a LUN. In the following scenario, the Index service and Query service reside on separate dedicated servers. The Index server copied contents of the “C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications” folder to the share on the Query server which is named “searchindexpropagation”. The location of the actual “searchindexpropagation” share is the same path as the Index server by default “C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications”.

Steps:

  1. On your NetApp SAN, create a new vol. I first checked the size of my Index files to determine how large of a vol would be needed. My index files located at “C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications” were about 3.5GB in size, so I created a 25GB vol with volume reservations and 20% snapshot reserve.
  2. Create a qtree on the new vol.
  3. Install Microsoft iSCSI Initiator on server and configure to connect to the NetApp SAN that will host your new vol.
  4. Reboot Server after install & config of iSCSI Initiator.
  5. Install SnapDrive 6.1.0.x onto the MOSS query server.
  6. Use SnapDrive to create a new LUN on your new vol.
  7. Once complete, your LUN is presented to the server as a new drive.
  8. Create a folder on your new drive. In my example, my new drive letter is “e:”. I created a folder named “propagationlocation” which results in the following new path “e:\ propagationlocation”.
  9. You can move the propagationlocation folder to a new location via Central Administration of command line.
  • Central Administration:
    • Access the Search Service Settings page for the Query Server:
      “Central Administration > Operations > Services on Server > Office SharePoint Server Search Service Settings”
    • Change the default location within the “Query server index file location:” filed to your new location, in my example that is: e:\ propagationlocation
  • STSADM.EXE
    • On the Query Server navigate to:
      “cd %commonprogramfiles%\Microsoft Shared\Web Server extensions\12\Bin”
    • Enter the following command:
      “STSADM.EXE –o osearch –propagationlocation e:\ propagationlocation”

To confirm your changes, go to Central Administration > Operations > Services on Server > Office SharePoint Server Search Service Settings and look to see if the “Query server index file location:” filed has been updated. You can also check the original location “C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications” which should no longer contain files. Latly, check the new folder location to insure the files are present e:\ propagationlocation .

How to use the option cifs.home_dir_namestyle domain

06/10/2010 Leave a comment
Symptoms
Example of how to enable CIFS homedir with the home_dir_namestyle option set to domain.
Solution
1. Edit the /etc/cifs_homedir.cfg file to represent a path where home directories will exist.

 Note:  The home directories will actually exist within folders named the NetBios name of the domain that each user belongs to.

 >wrfile /etc/cifs_homedir.cfg /vol/vol1/homedir

2. Create a folder for each domain in the directory that you entered in the /etc/cifs_homedir.cfg file.

3. Name each folder the same name as the Netbios domain name of each domain that the users will belong to HQ UK (example)

You will now have folders like the following:

/vol/vol1/homedir/hq/ /vol/vol1/homedir/uk/

4. Create a folder for each user within the correct domain named folder.

5. For a user in the HQ domain, create a folder in the HQ folder.

6. For a user in the UK domain, create a folder in the UK folder.

You will now have folders like the following:

/vol/vol1/homedir/hq/hq_user /vol/vol1/homedir/uk/uk_user

 7. Load the new CIFS homedir configuration into the filer

 >cifs homedir load -f 

8. Test that the CIFS homedir domain name style is working:

 >cifs homedir showuser hq/hq_user

>cifs homedir showuser uk/uk_user

Categories: NetApp Tags: ,

SnapDrive Web Service failed to start: ‘Failed to create SDAPI web services

06/05/2010 Leave a comment
Symptoms
Unable to start SnapDrive. The event logs show the following:

Date: 08/12/09 Source: SnapDrive
Time: 00:00:09 Category: Generic event
Type: Error Event: 101
User: NA Computer: xxxxxxx
SnapDrive service failed to start. Error code : SnapDrive Web Service failed to start
Reason: ‘Failed to create SDAPI web services’

SnapDrive Web Service failed to start: ‘Failed to create SDAPI web services’
Cause of this problem
In SnapDrive 6.1, a feature was added to use web services. This requires using HTTP SSL service. If IIS Admin is installed, HTTP SSL service becomes dependent on IIS Admin. If IIS Admin is disabled, then HTTP SSL service will not start, causing SnapDrive to not start.
Solution
There are three options:
 1. Enable IIS Admin.
 2. Uninstall IIS Admin if not used.
 3. Remove the HTTP SSL service’s dependency on IIS Admin in the registry and reboot.
Categories: NetApp Tags:

“SnapDrive installation fails with “Error 1920: Service could not start”

06/05/2010 Leave a comment
Symptoms
The SnapDrive for Windows installer fails, then reports the following error message:

Error 1920: Service could not start

SnapDrive installation fails with “Error 1920: Service could not start”
Keywords :  iscsi
Cause of this problem
The SnapDrive installer is dependent on many services. If any are stopped or disabled, the installation will fail.
Solution
  1. Verify that your configuration is supported on the NetApp SAN interoperability matrix, and that you have all necessary hotfixes installed.
  2. Make sure that the account tied to the SnapDrive service is legitimate, has appropriate security privileges, a working password, etc.
  3. Follow the installation process as described in the Installation and Administration Guide for the version of SnapDrive that you are using. Do not skip any steps.
  4. Open the Services MMC on your Windows host and verify whether the required services are enabled and started. SnapDrive requires that the following services be started:
  • Install Driver Table Manager
  • Windows Management Instrumentation Driver service 
  • Virtual Disk Service – Virtual Disk Service requires the following services:
    • Plug and Play Service
    • RPC Service

      Note:
      If any of the services listed above are disabled, you will see the above Error 1920 – “Service could not start” errors. If these services are disabled, enable them. If they are stopped, start them.

  1. Look in the host’s Application and Event logs for related information that may be of assistance.
  2. Check that the following hot fixes are applied on Windows 2003 OS: 919117, 931300, 932755, & 937382. Most importantly, ensure .NET 3.0 SP1 is installed. The SD service would not start with version 3.0 but was successful with 3.0 SP1

The Microsoft ISCSI initiator may be a culprit. Uninstalling and reinstalling it could also resolve this issue.

Categories: NetApp Tags:

Error when trying to create a FlexClone of a Volume SnapMirror destination: ‘Can’t create snapshot for operation’

06/04/2010 Leave a comment
Symptoms
Error when trying to create a FlexClone of a Volume SnapMirror destination: ‘Can’t create snapshot for operation’
Cause of this problem
For snapshot creation failures one would normally check the following:

  • The amount of free disk space (using df) on the volume, making sure that there is space for a snapshot to be created.
  • Volume snapshot limit is not exceeded.
  • If there are LUNs on the volume, make sure that space is available so that overwrite reserve does not circumvent snapshot creation.

In the case of a VSM destination, an existing snapshot has to be designated in the clone creation command.

Solution
Follow these steps:

Run vol clone create <clonevolume> -b <destinationvolume> <existingsnapshot>

A vol status will now show a clone dependant on the existing snapshot in the restricted volume.

A snapmirror status will show the relationship as idle.

Do not expect to be able to update the relationship until the clone is either destroyed via vol destroy or vol split.  On snapmirror update <destination>, you will receive an error that the snapshot that the flexclone depends on in the destination volume is in use and cannot be deleted.

To start updating the relationship again, destroy the clone of the destination or split it off. Note that splitting is not instantaneous.

Categories: NetApp Tags: ,

How to Create a NetApp FlexClone volume

06/04/2010 Leave a comment

If you need a temporary copy of your data that can be made quickly and without using a lot of disk space, you can create a FlexClone volume. A FlexClone volume shares its space with its parent, as long as their data does not change.

Before You Begin 

Ensure that you have the flex_clone license installed.Enter the following command to clone the volume:
vol clone create clone_name [-s {volume|file|none}] -b parent_name [parent_snap] 

clone_name is the name of the FlexClone volume that you want to create. -s {volume | file | none} specifies the space guarantee setting for the new FlexClone volume. If no value is specified, the FlexClone volume is given the same space guarantee setting as its parent. 

 parent_name is the name of the FlexVol volume that you intend to clone. 

 parent_snap is the name of the base Snapshot copy of the parent FlexVol volume. 

If no name is specified, Data ONTAP creates a base Snapshot copy with the name clone_ cl_name_prefix.id, where cl_name_prefix is the up to 16 characters of the name of the new FlexClone volume and id is a unique digit identifier (for example 1,2, and so on). 

Note: The base Snapshot copy cannot be deleted as long as any clones based on that Snapshot copy exist. 

 The FlexClone volume is created and, if NFS is in use, an entry is added to the /etc/exports file for every entry found for the parent volume. 

 The base Snapshot copy becomes a shared Snapshot copy between the FlexClone volume and its parent. 

 Example 

To create a FlexClone volume named newclone from the parent FlexVol volume flexvol1, you would enter the following command:
vol clone create newclone -b flexvol1 

Note: The Snapshot copy created by Data ONTAP is named clone_newclone.1.  

After You Finish

You can verify the status of the new FlexClone volume by using the vol status -v command.

Categories: NetApp Tags:

Creating a static or dynamic multimode vif

05/19/2010 Leave a comment

About creating a multimode vif  

This procedure enables you to create a static or dynamic multimode vif on your storage system. By default, the IP-address-based load-balancing method is used for a multimode vif. However, you can select another method while creating the vif. After a load-balancing method has been assigned to a vif, it cannot be changed.

Note
Do not select the MAC-address based load-balancing method when creating vifs on a storage system that connects directly to a router. In such a setup, for every outgoing IP frame, the destination MAC address will be the MAC address of the router. As a result, only one interface of the vif will be used.

Prerequisites

You need to meet the following prerequisites to create a multimode vif:

  • Identify or install a switch that supports link aggregation (for static multimode vifs) or LACP (for dynamic multimode vifs) over multiple port connections in your network, configured according to your switch vendor’s instructions.
  • Decide on a case-sensitive name for the vif that meets the following criteria:
    • It must begin with a letter.
    • It must not contain a space.
    • It must not contain more than 15 characters.
    • It must not already be in use for a vif.
  • Decide on the interfaces you want the vif to consist of.
  • Configure all interfaces that will be included in the vif to be down using the ifconfig command.

Creating a multimode vif  

To create a multimode vif in which all interfaces are active at once, complete the following steps

The operation performed using the vif create command is not persistent across reboots unless the command is added to the /etc/rc file.

Step1

To create a static multimode vif, enter the following command:

vif create multi vif_name -b {rr|mac|ip} [interface_list]

Or to create a dynamic multimode vif, enter the following command:

vif create lacp vif_name -b {rr|mac|ip} [interface_list]

-b specifies the type of load-balancing method:

  • rr–Round robin
  • mac–MAC-address based
  • ip–IP-address based (default)

Note
For dynamic multimode vifs, you should use the IP-address-based load-balancing method.

vif_name is the name of the vif.

interface_list is a list of the interfaces that make up the vif.

Note
You must ensure that all interfaces to be included in the vif are configured down. You can use the ifconfig command to configure an interface down.

Example

You can create a multimode vif, comprising interfaces e0, e1, e2, and e3 and using MAC-based load balancing, with the following command:

vif create multi MultiTrunk1 -b mac e0 e1 e2 e3

Step2

Enter the following command:

ifconfig vifname IP_address netmask mask

vifname is the name of the vif.

IP_address is the IP address for this interface.

mask is the network mask for this interface.

Categories: NetApp Tags: , ,

Vista users unable to access CIFS shares

05/18/2010 Leave a comment
NetApp Solution ID: kb46660
Symptoms
The following error appears when Vista users try to access CIFS shares:  The Mapped network drive could not be created because the following error occurred:
  The account is not authorized to log in from this station.
Vista users unable to access CIFS shares.
Cause of this problem
Verify the configurarion security setting by opening the appropriate policy and expanding the console tree such as the following:
Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (always) – Controls whether or not the client-side SMB component requires packet signing.
If Microsoft network client:Digitally sign communication is set to always change the cifs.signing.enable from off to on.
Solution
Change cifs.signing.enable off to the following:options cifs.signing.enable on

NOTE: Changing this option has no effect on non-Vista clients. However, they may have to reboot once the change is made.

Source: https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb46660

Categories: NetApp Tags: , ,
Follow

Get every new post delivered to your Inbox.