3 Replies Latest reply: May 24, 2013 10:45 AM by framus RSS

Removing an unlisted backup job

framus
Currently Being Moderated

We added new NFS datastores into our newly upgraded VSphere 5.1 / VSC 4.0 environment and attempted to set up scheduled backup jobs. Discovered that we had to re-ip the new datastores, and subsequent attempts to add the scheduled backup fail with the error: "Failed to create the backup job. Reason: The backup or job name "jobname" already exists. Names must be unique. "

 

The job in question is unlisted in the Backup and Recovery tab, I know I could add the job with a different name, and probably will, but I am curious how to remove the existing yet missing job?

 

Thanks -

Steve

  • Re: Removing an unlisted backup job
    framus
    Currently Being Moderated

    I found a solution in this thread: https://communities.netapp.com/thread/8473

     

    - stop the NetApp vSphere Plugin Framework service,

    - stop the NetApp SnapManager for Virtual Infrastructure service

    - copy the %install%/smvi/server/repository/backups.xml file

    - use wordpad and edit the same file

    - remove the backup entry/ies starting from the "<backup uuid="" tag through to the </backup>

         (may look like "<backup mounted="false" uuid=.....> )

    - restart the SMVI and NVPF services

    • Re: Removing an unlisted backup job
      ydk
      Currently Being Moderated

      Steve, the steps you posted would change or remove backup entries and will not solve issues with backup jobs. Additionally, it is not recommended to edit the XML files directly. The right way to resolve your issue would be to edit backup job definition. Looks like missing backup jobs is real problem here. Do you remember what change made the backup jobs disappear?

      • Re: Removing an unlisted backup job
        framus
        Currently Being Moderated

        The job was never listed in the console – while creating the job it always failed to list the virtual entities available for selection, and I had to cancel.

        I am assuming this was because the ip address we used for the new datastore was already in use in another area of the country. So, it was a separate datacenter, both separate private networks, but both existing on the same virtual center and that must be what choked the new backup job creation, or at least stopped it right after recording the job’s name.

More Like This

  • Retrieving data ...