#cross-volume copying?
1 messages · Page 1 of 1 (latest)
If you're doing a wholesale 1:1, create a clone.
Otherwise nothing thats exposed easily or advisable to consider running without extreme guidance from support in emergency cases -- As I understand it.
That said, Robocopy, NetApp XCP, cp, rsync, etc.
Yeap I'd clone or mirror the volume and just delete what I don't need anymore.
You can do RAPID deletes with robocopy too, that's some fun stuff
curl --location 'https://192.168.0.101/api/private/cli/vol/file/copy/start' --header 'Authorization: Basic ' --header 'Content-Type: text/plain' --data '{ "source-paths": [ "svm1_cluster1:test/file1.txt" ], "destination-paths": [ "svm1_cluster1:test/new" ]}'
that's potentially a lot of changed blocks between snapshots. I've observed deletions fill volumes.
non-protocol. These files are not accessible to the host running the powershell terminal. Even if they were, that's traversing the network twice.
I'm gunna see if there's a powershell-native command for this. if not, raw API testing is next.
I would imagine this would be a task that is being done by Administrators and you could just delete the snapshots...
I wouldn’t assume it’s okay to delete the snapshot(s). It may not be. In my scenario, it would not be. Also, it would have to be all snapshots to actually release those changes. Changes will “roll” to the prior snapshot until there are no more snapshots.