---
# System prepended metadata

title: replicated/local-volume-provider upstream integration
tags: [Design_Prep]

---

# Velero NFS/PVC/Local File System as target Support

## Phase 1 - Add [local-volume-provider](https://github.com/replicatedhq/local-volume-provider) to e2e, Download Request Server
- Ensure existing local-volume-provider works for existing users on supported velero versions until a transition plan is available.
- Add local-volume-provider to velero e2e suite to support existing features.
    - restic backup
    - target
        - NFS
        - PVC
        - Local Filesystem (hostPath)
    - This should free up dev time to focus on other tasks related to the transition
- Download request server for velero client
    - https://github.com/vmware-tanzu/velero/issues/6167
    - Meet compliance requirements, IP, port, authentication, etc.
    - This removes the need for local-volume-provider to maintain a fileserver or expose port and brings the plugin more in-line with other velero storage plugins
## Phase 2 - Kopia Filesystem Backup and Volume Snapshot Data Movement
- This is to support future velero versions where restic file system backup is removed
- https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
- Ensure the [volume snapshot data movement](https://github.com/vmware-tanzu/velero/blob/main/design/volume-snapshot-data-movement/volume-snapshot-data-movement.md) works with local-volume-provider plugin
    - pre-requisite: kopia support
## Phase 3 - local-volume-provider or equivalent is supported by Velero
- Long term goals
    - When adding BSL, velero/node-agent pod should not restart
    - Velero Download Server responds to Velero Client download requests, not LVP plugin specific code.

Phase 2/3 can be swapped as needed.