How to manually delete NetApp SnapMirror snapshots

The other day, one of our volumes in the lab environment filled up. This volume has a couple large VM’s on it, coupled with a couple different Veeam backup jobs running using the native Veeam backup methods as well as using NetApp snap mirror to snapshot the volume and then using Veeam to ship it out to Azure.

At any rate the volume filled up to the point where vCenter wasn’t allowing me to migrate VM’s off the datastore. I really didn’t want to expand the volume just so I could move VM’s off of it.

Instead, I decided to delete some of the older proof of concept snapshots from SnapMirror. Below are the quick and easy steps to clear up some un-used snapshots and free up some space on the datastore.

How to manually delete NetApp SnapMirror snapshots

  1. First, SSH into your NetApp using PuTTY or any other preferred terminal.
  2. Then type the following to get a list of all the SnapMirror snapshots.
    snap show

    NetApp snap show

  3. Now we need to enter diagnostic mode by typing:
    set diag

    NetApp set diag

  4. Finally, delete your desired snapshot by typing the below and pressing Y at the confirmation.
    snapshot delete -vserver Vservername -volume Volumename -snapshot nameofsnapshot -ignore-owners true

    NetApp snapshot delete

Deleting the POC snapshot freed up a few hundred gigs of space. From that point I was able to move some VM’s around and everything was back to normal.

Similar Posts

  • VMware View client now availabe for Android!

    VMware has announced that they have released a View Client for Android tablets available on the Android Market now. Here are just a few of the features found on the new client.

    • A new look and feel – The View Client for Android features the NEW blue look and feel of the VMware View clients!
    • Multiple broker support – If you have more than one VMware View broker in your organization, you can can easily access your desktop from all of them via the Android client
    • Desktop Shortcuts – Quickly connect with as many as four recent desktop via shortcuts
    • Virtual trackpad – Control your desktop on a granular level just like you would control the mouse on a laptop
    • Custom keyboard toolbar – Super easy access to all of the special keys not found on the Android default keynboard
    • Honeycomb 3.x support – Made from the ground up for the new generation of Android tablets
    • Custom gestures – Invoke keyboard, scrolling, etc are as easy as ever and simple to use
    • VMware View Security Server support (best experience) – No need to have VPN when you use VMware View Security Server
    • Background tasking – Switch between apps on your tablet and come right back
  • How to change vCenter Operations Manager session timeout

    I’ve been using vCenter Operations Manager for a while now at work for all the great information that can be found about our environment so I tend to log into vCOp at the start of the morning and then come back to as I may or may not need it thoughout the day. One thing that has kind of annoyed me is having to constantly log into the standard UI multiple times a day due to the default 30 minute timeout value.

    Luckily, with a bit of SSH and a few commands we can increase this timeout to anything we like or even disable it all together!

    Read More “How to change vCenter Operations Manager session timeout”

  • How to fix vRealize Orchestrator 6 appliance, weak ephemeral Diffie-Hellman key

    vrealize orchestrator chrome error

    I’ve recently deployed the vRealize Orchestrator appliance (6.0.2) and noticed right away that my default browser Firefox, would not load the Orchestrator appliance web panel. Firefox always complained about a weak Diffie-Hellman key.

    An error occurred during a connection to ip-address:8281. SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key)

    At the time I simply ignored it and just tried Google Chrome which it worked fine. That was until the latest release also broke with the same type of error message:

    Server has a weak ephemeral Diffie-Hellman public key“.

    I now had a problem and contacted VMware support, below is the very easy fix to make vCO 6 work in both the latest version of Firefox and Chrome!

    Read More “How to fix vRealize Orchestrator 6 appliance, weak ephemeral Diffie-Hellman key”

  • Another CBT bug found in VMware ESXi 6.0

    VMware

    VMware just published KB 2136854 regarding a new bug found in ESXi 6.0 that causes virtual machine backups, which use Changed Block Tracking (CBT), to be inconsistent. VMware says the cause of the issue is this:

    This issue occurs due to an issue with CBT in the disklib area, this causes the change tracking information of I/Os that occur during snapshot consolidation to be lost. The main backup payload data is never lost and it is always written to the backend device. However, the corresponding change tracking information entries which occur during the consolidation task are missed. Subsequent QueryDiskChangedAreas() calls do not include these missed blocks, hence a backup based on this CBT data is inconsistent.

    Read More “Another CBT bug found in VMware ESXi 6.0”

  • How to easily add an ESXi SSH login message banner

    ESXi issues message

    Preparing for some upcoming audits, I noticed one of the checkpoints was to ensure each ESXi host was configured with a warning banner stating the machine is being monitored and audited when someone logs into the ESXi host via SSH. This type of message is something you see on most any company or government computer before you login.

    There are two message types that can be used to achieve this, the first being login banner (/etc/issue) and MOTD (/etc/motd). The difference between the two are where they are shown. The login banner is shown between the username and password inputs during login, while the MOTD is displayed after a user has successfully logged into SSH.

    Read More “How to easily add an ESXi SSH login message banner”

  • Restore a VM using the {vm}-flat.vmdk file

    missing vmdk file error

    A couple days ago I was asked the question “An admin deleted the vmdk file associated with a VM, there are no snapshots or backups of the VM . Can we restore this VM somehow?“. I believe in backups, I like to have my VM’s backed up so that I can depend on them for events just like this very issue. At first I was stumped, until the {vm-name}.flat.vmdk was mentioned. That’s when I remembered a method to recover a VM using the vm-flat.vmdk file that I had actually done 2-3 years ago.

    Read More “Restore a VM using the {vm}-flat.vmdk file”

Leave a Reply

Your email address will not be published. Required fields are marked *