Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore from SMB file share snapshot feature #136

Closed
andyzhangx opened this issue Nov 30, 2019 · 34 comments · Fixed by #1466
Closed

Restore from SMB file share snapshot feature #136

andyzhangx opened this issue Nov 30, 2019 · 34 comments · Fixed by #1466
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@andyzhangx
Copy link
Member

andyzhangx commented Nov 30, 2019

Is your feature request related to a problem?/Why is this needed

Describe the solution you'd like in detail

Currently azure file don't have a restore from snapshot SDK, need to implement that when it's available.
als see ref: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/issues/13#issuecomment-528861659

https://docs.microsoft.com/en-us/azure/backup/restore-afs
https://docs.microsoft.com/en-us/azure/backup/restore-azure-file-share-rest-api

Describe alternatives you've considered

Additional context

@andyzhangx andyzhangx added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Nov 30, 2019
levimm pushed a commit to levimm/azurefile-csi-driver that referenced this issue Dec 25, 2019
…visioned_reclaim_policy

test: add e2e test "dynamically_provisioned_reclaim_policy_test"
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 28, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 29, 2020
@ialidzhikov
Copy link
Contributor

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Apr 26, 2020
@ialidzhikov
Copy link
Contributor

@andyzhangx, does it make sense to put lifecycle/frozen on this issue?

@andyzhangx
Copy link
Member Author

looks like there is still no snapshot restore API: https://docs.microsoft.com/en-us/rest/api/storageservices/snapshot-share

cc @RenaShahMSFT any progress on azure file snapshot API v2?

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 26, 2020
@andyzhangx andyzhangx removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 26, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 24, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 23, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

azure file driver project automation moved this from To do to Done Dec 23, 2020
@andyzhangx andyzhangx reopened this Dec 23, 2020
azure file driver project automation moved this from Done to In progress Dec 23, 2020
@andyzhangx andyzhangx removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 5, 2021
RomanBednar added a commit to RomanBednar/azure-file-csi-driver-operator that referenced this issue Apr 19, 2022
Currently there is a limitation in Azure SDK and snapshots can only
be created, not restored. We don't want users to be able to create
snapshots when there is no use for them at this point.

Disable snapshots by removing volume snapshot class resource and
removing snapshotter sidecars.

PR for tracking snapshot restore:
kubernetes-sigs/azurefile-csi-driver#136
RomanBednar added a commit to RomanBednar/azure-file-csi-driver-operator that referenced this issue Apr 26, 2022
Currently there is a limitation in Azure SDK and snapshots can only
be created, not restored. We don't want users to be able to create
snapshots when there is no use for them at this point.

Disable snapshots by removing volume snapshot class resource and
removing snapshotter sidecars.

PR for tracking snapshot restore:
kubernetes-sigs/azurefile-csi-driver#136
RomanBednar added a commit to RomanBednar/azure-file-csi-driver-operator that referenced this issue Apr 26, 2022
Currently there is a limitation in Azure SDK and snapshots can only
be created, not restored. We don't want users to be able to create
snapshots when there is no use for them at this point.

Disable snapshots by removing volume snapshot class resource and
removing snapshotter sidecars.

PR for tracking snapshot restore:
kubernetes-sigs/azurefile-csi-driver#136
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 16, 2022
@aslafy-z
Copy link
Contributor

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 17, 2022
@akankshakumari393
Copy link
Member

Do we know when can we have the support for restore feature?

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 3, 2022
@aslafy-z
Copy link
Contributor

aslafy-z commented Nov 3, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 3, 2022
@aslafy-z
Copy link
Contributor

@andyzhangx any news please?

@andyzhangx andyzhangx changed the title Restore from snapshot feature Restore from SMB file share snapshot feature Feb 9, 2023
@Satsank
Copy link

Satsank commented Feb 22, 2023

I apologize if this isn't allowed here. For those looking at alternatives to take Azure Files Snapshot and Restore, the team at CloudCasa.io added native support for it recently. Snapshots are taken using CSI driver, but the Restores are done using native AzureFiles Integration(must provide adequate permissions through an ARM template). It's a work around available through CloudCasa until the CSI driver natively supports this functionality. Hope this helps! https://cloudcasa.io/blog/automating-azure-files-restore-in-aks/

@andyzhangx
Copy link
Member Author

I apologize if this isn't allowed here. For those looking at alternatives to take Azure Files Snapshot and Restore, the team at CloudCasa.io added native support for it recently. Snapshots are taken using CSI driver, but the Restores are done using native AzureFiles Integration(must provide adequate permissions through an ARM template). It's a work around available through CloudCasa until the CSI driver natively supports this functionality. Hope this helps! https://cloudcasa.io/blog/automating-azure-files-restore-in-aks/

@Satsank thanks for the sharing. Do you have more details about Restores are done using native AzureFiles Integration(must provide adequate permissions through an ARM template)? is it copy file one by one under one file share? Thanks.

@0x113
Copy link

0x113 commented Feb 22, 2023

Hi @andyzhangx, I'm the developer behind automated Azure Files restore and I'll be more than happy to answer the questions.

Firstly, there's no need to provide any permissions with an ARM template for Azure Files restore. It's recommended for backing up and restoring AKS clusters infrastructure, but for just Azure Files, it's not mandatory.
As you may know, Azure files create a Kubernetes secret in the namespace of PVC in the following format: azure-storage-account-<storage-account-name>-secret. Our Azure Files mover looks for the right Secret, and it retrieves the credentials from there.

When it comes to the restore, CloudCasa uses the native Azure SDK to copy the files. Once CloudCasa finds the right snapshot for the PVC, it iterates through the files and copies them one by one to the destination file share. In the case of directories, it recreates the directory and then copies all the files.
I hope this helps!

@aslafy-z
Copy link
Contributor

aslafy-z commented May 17, 2023

Any updates so far? Was there any progress on the Azure SDK side? Is there some public facing ticket for that SDK that we can track? Thanks

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2024
@aslafy-z
Copy link
Contributor

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2024
azure file driver project automation moved this from To do to Done Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Development

Successfully merging a pull request may close this issue.

9 participants