VVEngine is a new add-on for ViceVersa PRO. VVEngine lets you create profile chains and categories to run sequentially.
Download VVEngine from the VVEngine Home Page See the extra features VVEngine offers VV PRO users in the Scheduling Comparison Chart
To run VVEngine you need ViceVersa PRO 2 or newer installed (VVEngine is a ViceVersa PRO add-on). VVEngine runs on Windows 11, 10, Windows 8, Windows 7, Windows Vista, Windows XP, Windows 2000, Windows Server 2003, Windows Server 2008 (all editions of these operative systems, including R2), Windows Server 2012 (all editions, including R2), Windows Server 2016 (all editions), Windows Server 2019 (all editions), Windows Server 2022 (all editions), Windows Home Server and Windows Small Business Server. VVEngine does not run on Windows 98, Me or 95. VVEngine is a 32-bit application, compatible with both Windows 32-bit and 64-bit. To control VVEngine you need an Internet browser: Microsoft Internet Explorer 5.5 (or later), FireFox 1.5 (or later), Chrome, Opera or Edge.
All modern browsers are supported, such as FireFox, Chrome or Edge.
You connect to VVEngine with your Internet Browser. Start the browser (e.g. Internet Explorer or FireFox) and type http://127.0.0.1:8001 in the address bar. This unique address opens the VVEngine interface. Notes:
Yes. Once VVEngine is installed, it will automatically start when you start Windows.
By default, VVEngine uses port 8001 and the HTTP protocol to communicate with your web browser. To connect to VVEngine, type http://127.0.0.1:8001 into your web browser address bar. N.B.: By default, VVEngine only allows connections from the local computer (127.0.0.1). To allow connections from other computers, see: http://www.tgrmn.com/web/kb/item54.htm
*** Requires VVEngine 1.1 or any later version *** Yes, you can connect to VVEngine from a remote computer. You will need to change the default VVEngine settings in order to do this, because, by default, VVEngine only allows web browser connections from the local computer (IP 127.0.0.1).
After this change, to connect from a remote computer, type http://<ip>:<port> into the web browser address bar on the remote computer.
To allow only the local computer to connect to VVEngine (default):
Yes, you can add profiles to VVEngine without them being part of a schedule and run them manually. You do this by clicking on 'Run Profile'. Profiles without a schedule have the text 'Manually' written in the 'Next Run' field. This allows you to organize your profiles into categories and see the profile history for the last 15 runs.
Your profile has now been added to the VVEngine list. As soon as all the sources and targets in the profile are accessible VVEngine starts the profile to synchronize, replicate or backup your files.
Your profile is added to the VVEngine list. As soon as all the sources and targets in the profile are accessible, VVEngine starts the profile to synchronize, replicate or backup your files. Note: network detection can take a couple of minutes. If you want to start the profile only once an hour, once a day or once a week (i.e. you disconnect and reconnect to the network multiple times but only want the profile to start every hour, day or week) select 'Hourly', 'Daily' or 'Weekly' instead of 'Immediately'.
With VVEngine you can run multiple ViceVersa profiles sequentially. Manual Runs: Add the ViceVersa profiles to VVEngine with no scheduling options set and make all of them part of the same category. When you want to run all the profiles in the category, select the category and click on "Run All" in VVEngine. "Run All" runs all the profiles in the current category. Scheduled: Add the ViceVersa profiles to VVEngine. For the first profile, change the schedule and set the "After this profile, run ..." to the profile name of the second profile. Then open the second profile's schedule and set the "After this profile, run ..." to the profile name of the third profile and so on. Note that only the first profile needs to have a schedule set, because the second, third, etc. will run sequentially after the first one.
Running VVEngine on a Windows Server as a Windows Service allows you to keep VVEngine running even when no one is logged onto the server. It also allows you to run VVEngine under a different account from the current logged-in account. See How Do I Install VVEngine as a Windows Service? and Control VVEngine From a Remote Computer
*** Requires VVEngine 1.1 or any later version ***
Please Note: VVEngine saves its settings and the profile list in a file called VVEngine.xml This file is kept in the folder c:\Documents and Settings\<account>\Application Data\VVEngine (where <account> is the account name running VVEngine). Additional Information:
You can remove VVEngine like any other Windows program. The uninstall procedure will completely and cleanly remove VVEngine from your computer. Windows 11, Windows 10, Windows 8, Windows 7, Windows Vista, Windows Server 2022, 2019 / 2016 / 2012 / 2008
Windows XP, Windows Server 2003, Windows Server 2000
To schedule a profile to run at a specific time, for example once a week, on Monday at 2 PM, set the profile schedule as follows:
This schedule will run the profile every Monday at 2 PM.
See the extra features VVEngine offers in the Scheduling Comparison Chart
By default VVEngine uses the HTTP protocol on port 8001 to communicate with your browser. If you are unable to access VVEngine on http://127.0.0.1:8001 with your browser, make sure your firewall is not blocking VVEngine. See also http://www.tgrmn.com/web/kb/item50.htm
*** Requires VVEngine 1.1 or any later version *** Yes, you can restrict access to VVEngine with a password. To setup a password, follow the steps below:
VVEngine will now require a password when connecting with a web browser.
*** Requires VVEngine 1.1 or any later version *** Yes, you can change the HTTP port used by VVEngine.
*** Requires VVEngine 1.1 or any later version *** VVEngine supports two RSS feeds (three since version 2.0) that can report the latest run for each enabled profile in VVEngine. The VVEngine feeds are accessible via any RSS reader. The feeds are accessible at: http://<ip>:<port>/rss.xml (eg http://127.0.0.1:8001/rss.xml or from a remote computer http://192.168.1.1:8001/rss.xml) and http://<ip>:<port>/errors.xml (eg http://127.0.0.1:8001/errors.xml or from a remote computer http://192.168.1.1:8001/errors.xml, this feed only reports profiles with errors) and http://<ip>:<port>/rssall.xml (eg http://127.0.0.1:8001/rssall.xml or from a remote computer http://192.168.1.1:8001/rssall.xml, this feed reports all profiles, including disabled profiles. This feed is only available in VVEngine version 2.0 or newer) VVEngine RSS Examples Google Desktop Gadget OneFeed showing VVEngine RSS feed
Windows Vista Sidebar Gadget showing VVEngine RSS feed
This issue is caused by a new security feature added to Internet Explorer 8. Updating to VVEngine 1.1 Build 07 (or newer) fixes this problem. http://www.tgrmn.com/web/vvengine/vvengine.htm
*** Requires VVEngine 2.0 or any later version *** Keep an eye on VVEngine! The VVEngine Gadget puts VVEngine right on your desktop. You can keep track of what's happening in VVEngine while you work. You can run and check profiles right from your desktop. You can position the gadget anywhere on the screen, move it and resize it as you like. The VVEngine Gadget is available for Windows 7, Vista or newer. It requires VVEngine 2.0 or newer to be installed.
NEW: Real-Time, Super-Fast, No Rescanning Execution. Monitor source and/or target folders for changes at file or subfolder level, and then backup, synchronize, replicate files without folder rescanning. Essential over slow connections and for real-time execution with a large amount of files. Plus VVEngine keeps track of all the changes happening so they can be reviewed. *** Requires VVEngine 2.1 or newer, Server Premium Edition or Client Edition ***
Overview of the New VVEngine Real-Time Functionality In the standard backup / replication / synchronization routine, Source and Target folders are analyzed to look for file changes. The folders are scanned, their content is compared file-by-file and a list of file changes is built based on timestamps and/or size. Then the new files, or the files that have changed, are copied or deleted, as needed. This process works well, but it is suboptimal in some circumstances where repetitive rescanning of source and target folders takes a long time. For example:
For improving performance in the above situations, VVEngine 2.1 now offers some new capabilities which are described below. The first time the profile runs, source and target folders are fully scanned and analyzed. However, after the first run VVEngine no longer scans source and target. Instead, it monitors source and target and keeps track of all file changes. Then, when the profile runs, VVEngine and ViceVersa use this information to apply the changes without the need to re-analyze the entire file set. This means that the total amount of files to backup, replicate or synchronize is no longer a factor, as changes are detected in “real-time”. Plus all of this happens without using extra computer resources: the file monitoring relies entirely on the standard Windows functionality and does not need any new file system driver or special service to be installed. This new “real-time” capability is implemented as a new option in the VVEngine scheduling settings. The option is called "Monitoring Level". Monitoring level can be set to one of the following values: Full Rescan: When a file change is detected, a profile run is initiated. The source and target folders are fully rescanned to find out which files have changed since the last run. This is the standard change detection functionality: source and target are fully rescanned on change detection. Subfolder Level: Changes are detected and tracked at subfolder level. When a file change is detected, a profile run is initiated. However only the sub-folders where the file changes have occurred are rescanned which significantly improves performance. This is part of the new real-time capability of VVEngine. File Level: Changes are detected and tracked at file level. When a file change is detected, a profile run is initiated. However only the files with changes are rescanned. This speeds up the profile execution significantly. This is part of the new real-time capability of VVEngine. The new Subfolder Level and File Level monitoring do not require full rescanning of source or target like Full Rescan. This speeds up execution substantially especially over slow connections or when dealing with a large amount of files. Note: Subfolder Level and File Level detection options are only available in the VVEngine Server Premium edition or in VVEngine for Windows 11, 10, 8, 7, Vista, XP, 2000. They are not available in the VVEngine Server edition. The following PDF document contains detailed instructions on how to setup Real-Time backup for Continuous Data Protection, replication or synchronization in VVEngine:
An easy way to monitor all ViceVersa and VVEngine profiles that are running on multiple servers from a single central server, is to use the Windows Server Manager. Just add all the servers that need monitoring to the Server Manager on the main server and once that is done all VVEngine profiles running locally or remotely can be monitored from there. How? VVEngine logs all profile failure events in the Windows Application Log. These events can be shown in the Server Manager, collected from multiple servers. If an error with a profile that is running on a remote VVEngine is detected, it is then possible for the server admin to connect to that specific VVEngine to see all the details with a Web Browser, using IP address plus the VVEngine port. Also if VVEngine is setup to run as a service, then any service failure with starting/stopping can be monitored locally and remotely via the Server Manager. There are also other ways to report failures. For instance, an e-mail can be sent by each profile in case of profile failure to a specific e-mail address. E-Mail notifications are set in the profile settings.
NOTE: You can also use the new VVEngine REST API to monitor multiple VVEngine installations on your network, in combination with your network monitoring tool.
The new Microsoft Edge is based on Chromium and was released on January 15, 2020. It is compatible with all supported versions of Windows. Downloading the browser will replace the legacy version of Microsoft Edge on Windows 10 PCs. VVEngine is fully compatible with the new Microsoft Edge based on Chromium.
Starting with version 2.2, Build 2230, VVEngine now supports querying the status of its scheduled profiles via a REST API. The returned information is formatted as JSON objects. The status of the profiles can be queried at URLs /profiles/ and/or /profiles/status/. This is useful for remote monitoring of multiple VVEngine installations running on the network, using server monitoring software and/or network sensors. It is recommended that you use the new VVEngine REST API and its JSON returned objects to monitor multiple VVEngine remotely. Here is an example of a query via HTTP: returning JSON: or returning: If this exact string is not returned {"have_any_errors_or_disabled":0} then VVEngine is down or there are some profiles that have errors or are disabled. Full description of the VVEngine REST API is available in the VVEngine manual.
Starting with version 2.2, build 2230, VVEngine now considers the file and subfolder filters present in the profile settings also during real-time change detection. If a change happens to an excluded file or in an excluded subfolder, it is then excluded from change detection too, which means that a change to an excluded file or in an excluded subfolder does not trigger a superfluous extra profile run anymore. When a filter is not taken into consideration, the change will be detected to a file or in a subfolder even if it is excluded in the profile settings and ViceVersa will run and will then exclude that file/subfolder anyway during execution: this might result in an unnecessary extra run. Before VVEngine version 2.2 (build 2230) all filters were ignored during change detection and the profile would always run. More information is available in the VVEngine manual. | |||||||||||||||||||||||||||||||
