@airvb the influx backup and influx restore commands use the server’s API to download/upload data, so you’ll need to leave the server running to use them.
If you’re willing to stop the DB as part of the moving process, I’d instead recommend a simpler approach:
Stop the DB
Use cp or mv to relocate your /home/airvb/.influxdbv2 to /media/influxdbv2
Edit your config file to point at the new location
Start the DB
Once you’ve verified things are working, delete the old directory (if you used cp instead of mv)
No, you’ll need to restart the DB at some point for the config-change to be picked up, and I don’t think it’s safe to cp the files from under a running DB since it bypasses in-process locks and the cache.
You could try backing up from your current server and restoring into a new instance, configured to store data at the new paths. The downside of this would be that you’ll miss out on any new data written after you’ve taken the backup.