Question on backup and restore process using Velero

After reading thru the [Influxdb3 core backup and restore process documentation](https://docs.influxdata.com/influxdb3/core/admin/backup-restore/), I understand that the gist of it all is to stop the server process, copy the data folders in a specific order then copy them in the exact opposite order for the restore, then start the server back up.

I was considering using [Velero](https://github.com/vmware-tanzu/velero) for a full Kubernetes PV (persistent volume) backup and restore process, but now I am realizing it may not respect any sort of copy order.

So my question is: would it just not be recommended to do that? I suppose I can create a script that does that work for me without velero.

Thanks!

Start with the linked InfluxDB 3 core backup and restore documentation and Velero documentation, focusing on persistent-volume snapshot and restore behavior. The issue names no source files or tests; it would need a documented, validated recommendation for using Velero with InfluxDB backups, or a clearly scoped alternative.

Written by the indexing model from the issue text.