- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Re: How to remove VM-level backup policy and retur...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2021 09:25 AM - last edited on 11-12-2021 05:39 AM by support_s
11-10-2021 09:25 AM - last edited on 11-12-2021 05:39 AM by support_s
How to remove VM-level backup policy and return to inherited datastore policy?
I'm a Simplivity newbie and am working on our backup policies. I have applied a certain policy to a set of VMs specifically at the VM level because I needed them to be different than the default policy that's applied at the Datastore.
Since then, I've moved them to a different datastore with a new default datstore-level backup policy. They are, as expected, retaining the more specific policy that was previously applied to them at the VM object level. Is it possible for me to remove this more specific policy application so that they return to inherting the policy from the datastore level?
To be clear, I'm not looking to delete the policy altogether, just how it's being applied to the VM.
- Tags:
- SimpliVity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2021 05:37 AM
11-12-2021 05:37 AM
Re: How to remove VM-level backup policy and return to inherited datastore policy?
Hello @koal ,
Thank you for using HPE Simplivity Forum.
What procedure did you use to move the VM to the new datastore? I tested this using the "Move Virtual Machine" option in the Simplivity menu, and successfully got the VM to inherit the backup policy from the datastore when it moved. The VM must be shutdown though.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2021 01:11 AM
11-13-2021 01:11 AM
Re: How to remove VM-level backup policy and return to inherited datastore policy?
I am using a regular vSphere storage migration because I need to do a live migration of the machine. Using the non-Simplivity migration, if a VM did not have a backup policy applied at the VM-level, it will inherit the default storage-level backup policy when it's moved. The issue was only popping up if the policy was applied at the VM-level originally.
After testing though, it looks like using the Simplivity move will force the policy to the destination datastores default backup policy regardless of how the policy was originally applied to the VM.
I suppose that means, in this particular scenario, I'll just have to keep that in mind when using the standard non-Simplivity move.