VV6 - Optimising deletion of remote files & folders

[Alice]

Hey there. VV6 is fast, super-fast !! That's been established.

With that in mind I am seeking to increase the speed of deletions on a Windows Server (the Destination) by running an initial VV Job to delete the data held there....rather than using DOS 'RD S:\-Serv~1\Utils\Image /S /Q' or similar, then I will run a second VV Job to copy data to the Destination.

Way back I remember you telling me a quick method to delete data with VV is to 'Mirror Copy' an empty folder to the Destination, thereby wiping its contents ? With multi-threading that should be mega-fast.

So is that concept 'sound' ?

I run a batch file which calls the 'copy data' VV Job, that VV Job runs the 'wipe data' VV Job via another batch file call in 'Run scripts before comparison'.

I need to consider 'silent' running for the 'wipe' VV Job via /hiddenautoexec ? How does the 'copy data' VV Job know the 'wipe data' VV Job has completed, before it tries to start ?

[TGRMN Software]

Hi Alice,

[Alice]

Thank you for your help.

Right, so there are two .fsf files.

Blank-Images-Folder.fsf

which Mirror copies an empty folder to the Destination in order to clear it of data.

Then a second .fsf file that copies a C: drive folder with its files to the now empty Destination :

Utclup.fsf

If I run them manually and in sequence (ie the first has to complete before the second one executes), using my own fair hands, obviously they work So the issue is around how to 'call' them and have them run in sequence. I guess I could use VVengine (as we own v 3.0), but this copy is user-initiated, ie its run 'as and when' a person chooses to do it and they also get to see what it is actually going to do before pressing 'Execute' (via /autocompare), so therefore cannot be easily scheduled.

Ideally I need a batch file to run this two-step activity (the previous batch file works fine at the moment cos it just calls Utclup.fsf which runs a second 'RD' batch file via 'Run scripts before comparison' before it itself starts to copy data). Perfect.

But I'm struggling to get the Utclup.fsf to call the same 'wipe' batch file in the same way, but this time it needs to run VV Profile Blank-Images-Folder.fsf instead of an RD DOS command.

The initial batch file to begin the whole process contains :

start "viceversa" "c:\Apps\ViceVersa Pro\ViceVersa.exe" "C:\Data2\Publishers\Tgrmn\ViceVersa Pro Profiles & .bats\PC\Profiles\utclup.fsf"/autocompare
exit

then within the Utclup.fsf (via 'Run scripts before comparison') it calls another batch file to start the wipe, it contains :

start "viceversa" "c:\Apps\ViceVersa Pro\ViceVersa.exe" "C:\Data2\Publishers\Tgrmn\ViceVersa Pro Profiles & .bats\PC\Profiles\Blank-Images-Folder.fsf" /wait /hiddenautoexec
exit

what this actually does is, it silently starts to wipe the Destination data but fails to wait for it to complete, before switching to the display of the data copy element of utclup.fsf. But that display will be wrong as the deletion has not yet completed.

Doubtless I'm doing something wrong or in the wrong order, apologies

[TGRMN Software]

Hi Alice,

in VVEngine you can setup profiles without a schedule, and then run them manually. Can also run profiles in VVEngine via the external console.exe program , which controls VVEngine.

However, it is also possible via a simple batch.

In your example you have:

start "viceversa" "c:\Apps\ViceVersa Pro\ViceVersa.exe" "C:\Data2\Publishers\Tgrmn\ViceVersa Pro Profiles & .bats\PC\Profiles\Blank-Images-Folder.fsf" /wait /hiddenautoexec
exit

however /wait is a flag of cmd command START not ViceVersa:
https://ss64.com/nt/start.html

Please trry with /wait after start in the batch.

---
www.tgrmn.com
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[TGRMN Software]

See also

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/start

---
www.tgrmn.com

[Alice]

Ok, thanks for the reply and advice.

moving '/wait' to just after the 'Start' command did work. But its worth noting that the VV Help file, under 'Command Line Parameters', gives this example :

[TGRMN Software]

Ah, yes, you are right.
The /wait flag in ViceVersa has a different meaning: