Hi Guys
Does someone knows if it is possible to disable the automatic export-policy update when you do a FLR from a Netapp storage snapshot?
Our policy will get a ro rule if we want to do a FLR.
Regards
Dario
-
- Service Provider
- Posts: 6
- Liked: never
- Joined: Oct 05, 2015 11:14 am
- Full Name: Dario Furigo
- Contact:
Veeam restore from storage snapshot
VMWare VCP-DCV
NetApp NCDA, NCIE, NCSIE
https://virtualsyntaxerror.wordpress.com/
NetApp NCDA, NCIE, NCSIE
https://virtualsyntaxerror.wordpress.com/
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Veeam restore from storage snapshot
Hi Dario, no, this is not possible. Veeam B&R always adds its export rules at the beginning of the list during backup/restore/rescan operations involving storage snapshots.
-
- Service Provider
- Posts: 6
- Liked: never
- Joined: Oct 05, 2015 11:14 am
- Full Name: Dario Furigo
- Contact:
Re: Veeam restore from storage snapshot
Hi foggy
Thx for the reply. Is this a known bug that we get a ro rule in the export policy and the cloned datastore cannot be attached and the productive datastore which has the same export policy gets inaccessible...
Thx for the reply. Is this a known bug that we get a ro rule in the export policy and the cloned datastore cannot be attached and the productive datastore which has the same export policy gets inaccessible...
VMWare VCP-DCV
NetApp NCDA, NCIE, NCSIE
https://virtualsyntaxerror.wordpress.com/
NetApp NCDA, NCIE, NCSIE
https://virtualsyntaxerror.wordpress.com/
-
- Service Provider
- Posts: 6
- Liked: never
- Joined: Oct 05, 2015 11:14 am
- Full Name: Dario Furigo
- Contact:
Re: Veeam restore from storage snapshot
To specify the problem:
The cloned volume gets the normal export-policy and veeam updates the exports as expected but the root policy of the NetApp SVM gets the following export rule:
esx-nfs-ip ro=never,rw=any,superuser=none
esx-mgmt-ip ro=any,rw=any,superuser=any
esx-vmotion-ip ro=any,rw=any,superuser=any
So veeam is not able to attach the newly created clone to that ESXi because of the rules above. That makes no sense to me.
I've tested it with a customer and their facing the same problem with a fresh install of B&R 9.5 and a upgrade version of B&R 9.5
The cloned volume gets the normal export-policy and veeam updates the exports as expected but the root policy of the NetApp SVM gets the following export rule:
esx-nfs-ip ro=never,rw=any,superuser=none
esx-mgmt-ip ro=any,rw=any,superuser=any
esx-vmotion-ip ro=any,rw=any,superuser=any
So veeam is not able to attach the newly created clone to that ESXi because of the rules above. That makes no sense to me.
I've tested it with a customer and their facing the same problem with a fresh install of B&R 9.5 and a upgrade version of B&R 9.5
VMWare VCP-DCV
NetApp NCDA, NCIE, NCSIE
https://virtualsyntaxerror.wordpress.com/
NetApp NCDA, NCIE, NCSIE
https://virtualsyntaxerror.wordpress.com/
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Veeam restore from storage snapshot
Please contact technical support with this.
Who is online
Users browsing this forum: Bing [Bot], Semrush [Bot] and 60 guests