A slightly modified version of a scriptingGuy post to find NetApp software installed from a csv file (export from active directory) Read More

I was asked the other day what happens with maxfiles. Maxfiles has to do with inodes on the NetApp. This can get full due to many small files in a volume and you can still have plenty of space but not have enough inodes.

Basically, increasing the maxfiles cannot be reversed, however when you grow a volume the maxfiles grows as well. When you shrink a volume the maxfiles is still set at what it was and is not shrunk.

The maxfiles also grows if you’ve set a higher maxfiles than what the volume would originally specify but you grow the volume and the new maxfiles for that volume size is higher than what you’ve previously set. Read More

This is to match what System Manger 2.2 creates as a vol type but via CLI, some of us still batch out our commands in notepad so here yah go: Read More

I ran into the issue where Windows was not mounting the Phone’s SD card within windows, so I had to revert back to using adb. This method requires that you’ve download the drivers for your phone, along with the android sdk (http://developer.android.com/sdk/index.html). The SDK will download and you extract to any location of your choosing. adb is located in {directory}\sdk\platform-tools\

In case you have an issue with getting your remote device to show up for /sdcard/ the following commands will help you out:

Read More

Ever had a system where you were running 7.3.x and got a new disk shelf intended for a 8.x release and the disks show as broken? Read More

A quick command that I always forget to remember when you want to unown disks from a NetApp where nether filer owns the disks. This can happen when you move a shelf from one controller pair to another.

Read More

There’s quite a lot of information out there on backup tasks, my biggest frustration is that the wizard is not very standard on creating the backup tasks, it’s much easier if you know what you’re doing to create the tasks manually and leave the backup wizard outta the picture.

Here’s the common command line arguments that come with the new-backup cmdlet

new-backup -Clusteraware 'True|False' -lcr 'True|False' -VerifyOnDestVolumes 'src_storage_system_list:src_vol:dest_storage_system:dest_vol' -Verify 'True|False' -Server 'server_name' -StorageGroup 'storage_grp1, storage_grp2, ...' -ManagementGroup 'Standard|Weekly|Daily' -ActiveDatabaseOnly 'True|False' -PassiveDatabaseOnly 'True|False' -BackupTargetServer 'server name' -ActivationPreference 'ActivationPreferenceNum' -UpdateMirror 'True|False' -VerDestVolume 'True|False' -NoUTMRestore 'True|False' -NoTruncateLogs 'False' -Throttle 'throttle_val' -VerificationServer 'server_name' -UseMountPoint 'True|False' -CCRActiveNode Boolean 'True|False' -MountPointDir 'mountpoint_dir' -RetainBackups 'no_of_days_to_retain_backup' -RetainDays 'no_of_days_delete_backup' -Command 'True|False' -RunCommand 'win_path_and_script_name' -GenericNaming 'True|False' -BackupCopyRemoteCCRNode Boolean 'True|False' -RecoveryPoint 'win_path_and_script_name' -ReportProgress 'True|False' -ArchiveBackup 'True|False' -ArchiveBackupCopyRemoteCCRNode 'True|False' -ArchivedBackupRetention 'Hourly|Monthly|Daily|Weekly|Unlimited' -RetainUtmBackups 'no_of_log_backups_to_retain'

I’ve found this one to be useful to backup all members of a DAG, active databases are full backups, secondary/passive databases are copy based backups, no up to the minute backups:

new-backup –Server 'dagname' –ClusterAware –ManagementGroup 'Standard/Daily/Weekly' –RetainDays xx –NoUTMRestore –ActiveDatabaseOnly -UseMountPoint –MountPointDir 'C:\Program Files\NetApp\Snap Manager for Exchange\SnapMgrMountPoint' –RemoteAdditionalCopyBackup $True –RetainRemoteAdditionalCopyBackupDays xx

This one requires an individual task on every server in the DAG however this task will only run on one of the servers, the server that holds the cluster role. This allows for all databases to be backed up and still be able to backup your databases if your nodes fail. This command also allows you to add databases to your exchange environment and not have to modify your backup jobs.

I’ve always wondered where the autosupports were held on the NetApp, specifically to see if my autosupports are being processed on new client sites. I’m not sure about other releases but on 8.x releases (they’re most likely in the same location) they’re stored here:


NetApp has released some commands in the 8.1.x code line release to check autosupport information.

netapp> autosupport
autosupport destinations
autosupport history
autosupport manifest
autosupport trigger

you get some outputs like this:

netapp> autosupport history show
Seq                                    Attempt Last
Num   Destination Status               Count   Update
----- ----------- -------------------- ------- --------------------
      smtp        ignore               1       2/6/2013 09:35:46
      http        sent-successful      1       2/6/2013 09:35:49
      noteto      ignore               1       2/6/2013 09:35:46
      smtp        collection-failed    -       2/6/2013 09:34:51
      http        collection-failed    -       2/6/2013 09:34:51
      noteto      collection-failed    -       2/6/2013 09:34:51