Unable to Edit/Suspend/Delete NetApp VSC Backup Job


In my previous post I had outlined that I was going through a filer migration and I have just come across another small issue with regards to my VMware world!


The Issue

Via the NetApp VSC (Virtual Storage Console) I have a number of backups configured and I needed to take this into consideration when I was setting a volume to "Offline".  I needed to carry out a number of preparation tasks within the VMware world, mainly:
  • Update the backup policies within VSC to remove any trace of a datastore hosted on said volumes
  • Detach the datastore from all ESX hosts
Now, being extremely excited and buzzing with anticipation of having the old filer completely unreferenced from my virtual world I inadvertently offlined a volume and deleted it a few weeks later as there had been no issues, alarms, alerts, fires, explosions etc.


Noticed this week that one of the VSC backup policies still references one of the old datastores.  Thought I would try a few simples things to workaround the issue:


1st thought: I will just Edit the backup policy and remove the interfering datastore
Result:  Failed to determine privileges for operation


2nd thought:  I will just Suspend the sucker.  If it isn't running, it can't complain!
Result:  Failed to determine privileges for operation


3rd thought:  I will just Delete the a-hole.  It's not needed now and I can create a new policy for the new datastore!
Result:  Failed to determine privileges for operation


4th thought:  Ah shit!  Now I have to actually think about what I am doing!


The Solution

The solution to this problem is very simple.  No re-attaching old datastores (which is handy when you have fully deleted the volume is was served from), no ESX command-line jiggery-pokery etc.  The solution is to edit your scheduledBackups.xml file which is stored on your vCenter server.  To achieve this complete the following steps:
  • Log into vCenter server
  • Stop the NetApp SnapManager for Virtual Infrastructure service
  • Make a backup of the scheduledBackups.xml file
    • %ProgramFiles%\NetApp\Virtual Storage Console\smvi\server\repository\scheduledBackups.xml
  • Run Notepad as Administrator
  • Open the scheduledBackups.xml file located at:
    • %ProgramFiles%\NetApp\Virtual Storage Console\smvi\server\repository\scheduledBackups.xml
  • Find and remove the backup policy which is causing the issue (Example at bottom of screen)
    • Starts with <backupJob>
    • Ends with </backupJob>
  • Save the scheduledBackups.xml file when finished
  • Start the NetApp SnapManager for Virtual Infrastructure service
  • Refresh the Backup Jobs screen within the NetApp plug-in via vSphere client
  • Backup job should be gone


Backup Entry Example

<backupJob>
        <jobId>048e082d-d547-49d5-a775-2ead21ec8c0e</jobId>
        <entities>
            <entity>
                <uuid>netfs://[IP Address]//[Datastore name]</uuid>
                <type>DATASTORE</type>
                <name>[Datastore name]</name>
            </entity>
            <entity>
                <uuid>netfs://[IP Address]//[Obsolete Datastore name]</uuid>
                <type>DATASTORE</type>
                <name>[Obsolete Datastore name]</name>
            </entity>
        </entities>
        <weeklySchedule>
            <startHour>15</startHour>
            <startMinute>45</startMinute>
            <startDate>2015-01-19T00:00:00Z</startDate>
            <daysOfWeek>Sun</daysOfWeek>
        </weeklySchedule>
        <retention>
            <count>7</count>
            <type>TIME</type>
        </retention>
        <notification>
            <addresses>
                <address>alerts@vsc.com</address>
            </addresses>
            <smtphost>[SMTP Host IP]</smtphost>
            <fromAddress>vmsnaps@vsc.com</fromAddress>
            <type>NO_NOTIFICATION</type>
        </notification>
        <scripts/>
        <jobname>[Job Name]</jobname>
        <noVmSnaps>true</noVmSnaps>
        <updateMirror>true</updateMirror>
        <jobState>ACTIVE</jobState>
        <includeIndependentDisks>false</includeIndependentDisks>
        <excludeDatastores/>
    </backupJob>



Hopefully you find this entry long before the posts calling for you to create new volumes, datastores etc!

Comments

Post a Comment

Popular posts from this blog

Add Multiple Alias Email Addresses to Exchange Online/Office 365 Mailbox

I will keep the BS short for this one BUT there are a few points to mention.  Please read as it will save you time in the long run! When running through this process you MUST specify ALL email addresses that are to be associated with the mailbox you are updating It will overwrite anything that currently exists within the Email Addresses section When specifying the email addresses be sure to pay attention to SMTP and smtp Being an absolute 1337 n00b myself, I originally ran through the process to add additional email aliases to the mailbox.  Unbeknownst to me at the time, running through this process completely overwrites what is associated with the mailbox.  So, my advice?  Create the entire Set-Mailbox  string for all email addresses before starting the process. Anyway, onto the process! If you want to add multiple alias email addresses to an Exchange Online/Office 365 account run through the following: Open Powershell Type the following comman...
Read more

WHM/cPanel/Exim Mail Server // Relaying email for specific domain(s) or email address to SMTP Smart Host or remote SMTP server

As with most of my posts, scroll to the Solution  section if you are only here for a quick fix.  BUT be sure to check out the Examples at the end of the post!    WARNING:  You will bypass my attempts at humour to make this read interesting if you skip! I recently came up against a scenario whereby a client who uses a WHM/cPanel server as a dedicated mail server.  Fine.  Easy Peasy, no issues there. These guys wanted to relay their mail through an online service for reporting and reputation reasons.  Fine, again, simple. Naive little me thought "Simple, all I gotta do is log into WHM and tell Exim where to push the mail in their sweet little web interface".  Turned out to be not so straight forward. The Scenario (long-story-short) Client uses WHM/cPanel system as dedicated mail server (Exim) Wanted to send email for specific domain to specific IP address Wanted to relay all other outbound mail via 3rd party relay serv...
Read more

Re-instating "Send As" privilege Windows 2003 Server // GOOD ForEnterprise

You may recall that I had a wonderful time troubleshooting issues with the GOOD for Enterprise service, whereby user's GOOD profiles were falling into a paused state as the service was unable to successfully send emails from the user's Android & iOS apps. GOOD For Enterprise have now outlined a permanent fix for this issue. Using the following fix will re-instate the Send As permissions for the required user accounts that the GOOD app uses to remotely send emails from their handheld apps, therefore eliminating the need to go through the workaround which I had outlined in my previous post . The Permanent Fix In order to achieve a permanent fix for this issue we need to re-instate the Send As ability that the required user accounts had before a certain Windows update removed this right, this is done using the DSACLS utility. The syntax for the correct command is as follows: dsacls "cn=adminsdholder,cn=system,dc=domainname,dc=com" /G "\GoodAdmin:CA;S...
Read more