Yes. Starting with ViceVersa PRO version 2, the Volume Shadow Service is used to copy files and databases while they are in-use or locked. See http://www.tgrmn.com/web/kb/item33.htm for more information.
Yes. Starting with ViceVersa PRO version 2, the Volume Shadow Service is used to copy files and databases while they are in-use or locked. See http://www.tgrmn.com/web/kb/item33.htm for more information.
Yes, you can set up automatic file synchronization, file replication or file backup, using one of the following tools: 1) Use the Windows Task Scheduler and the ViceVersa Command Line (ViceVersa PRO and PLUS). Command line options for ViceVersa are documented in the help file. 2) Use VVScheduler (ViceVersa PRO). VVScheduler is included in the ViceVersa PRO download and can be accessed from the 'Tools' menu. VVScheduler can schedule multiple profiles to run periodically at a certain time. 3) Use VVLauncher (ViceVersa PRO). VVLauncher is included in the ViceVersa PRO download. VVLauncher can schedule one profile at a time and can run it as soon as file changes are detected in folders. 4) Use VVEngine See the different tools' capabilities in the Scheduling Comparison Chart
It is quite rare to exceed 259 characters for a file path name. If that is needed, ViceVersa PRO 2 now supports long path names exceeding 259 chars. To enable this in a specific folder use the prefix "\\?\". To specify a UNC path, use the "\\?\UNC\" prefix.
ViceVersa treats Outlook Files (.PST) as any other file. When synchronization is activated, ViceVersa overwrites the older PST file with the newer PST file, based on the files' timestamps. Please note: ViceVersa does not synchronize individual Outlook e-mails, contacts, appointments.
Yes. ViceVersa PRO is designed to run on Windows 2003 Server (and on Windows 2000 Server). ViceVersa PRO can be setup to run continuously as a Windows Service using the VVLauncher tool (included in the ViceVersa PRO download) or using our most advanced scheduling tool VVEngine ViceVersa PRO supports also the 64-bit version of Windows 2003 Server: more info
Yes, ViceVersa works with CD/DVD Recordable/ReWritable drives (CD-R/CD-RW/DVD-RW) if a proper device driver is installed and configured with your drive. The driver should make the CD/DVD behave like a large floppy disk. Nero InCD (part of Nero 6 or later) and Roxio DirectCD (part of Easy Media Creator) are two products that work with various CD/DVD drives and makes them look like large floppy disks. Check with your CD/DVD documentation.
Please refer to the following article at http://www.ezlan.net/direct.html www.ezlan.net has lots of useful information regarding HOME and SOHO networking issues. TGRMN Software highly recommends ezlan.net.
ViceVersa uses the timestamp that Windows assigns to every file. To identify file conflicts, i.e. files that have changed both in source and in target, and to keep track of file deletions, ViceVersa PRO uses a tracking database.
Every time you run a project/profile, ViceVersa compares the files in source and in target to see if they have changed. ViceVersa powerful preview feature shows you exactly what is going to happen before any files are touched. Preview even gives you the possibility to copy/delete individual files and to reconcile file conflicts. ViceVersa PRO can also be scheduled using VVScheduler or run at Windows' start-up, shut-down or as soon file changes are detected using VVLauncher (included in the ViceVersa PRO download). See List of ViceVersa PRO and PLUS features
This error does not happen when you run ViceVersa manually by clicking on "Compare". This can occur if you are working with a mapped network drive. Drive mappings may not be available when a scheduled task runs even if you set up the task to log in with your user name and password. Solution:
When ViceVersa overwrites an older file with a newer file, first it copies the new file to a temporary file in the destination folder. Only after the copy operation completes successfully, ViceVersa replaces the older file with the temporary file. So, in case of a connection failure only the temporary file is affected. Just run ViceVersa again when the connection is restored, the temporary file will be removed.
During file synchronization a file conflict occurs when a file has changed in both locations (source and target) since the last sync, making it difficult to determine which version should be left unchanged and which version should be updated. For example, if you've changed a document on your desktop computer since the last synchronization and also made a different change to the same document on your laptop, a file conflict will occur. ViceVersa PRO (ViceVersa Plus does not track file conflicts) will mark file conflicts in the comparison window with a ** in front of the name and will also report conflicts in the log file and the scheduler, so that you can decide which version you want to keep and which version you want to update.
In one-way sync, files are copied only from a primary location (source) to a secondary location (target) in one direction, but no files are ever copied back to the primary location. Replication and Backup (=Mirroring) are one-way sync methods in ViceVersa. In two-way sync, ViceVersa copies files in both directions, keeping the two locations in sync with each other. Synchronization and Consolidation are two-way sync methods in ViceVersa. You might set up a one-way sync to backup your files to the network, for example, where ViceVersa will copy every new files from your computer to the network but never to copy files in the other direction (from the network to your computer). When files are deleted from your computer they are also deleted from the network. You might set up a two-way sync between a desktop and a laptop computer, for example, where ViceVersa will copy the newest version of any file it finds to the other location, overwriting any older versions of the same file. This is a good way to sync if you work with the same files on both computers and want to make sure you always have the most recent version of every file you have worked on, no matter which computer you are using. During a two-way sync, ViceVersa will alert you whenever it finds a conflict, which typically occurs when a file has changed in both locations since the last sync. Rather than overwrite either of the files that have been updated since the last sync, ViceVersa will show the conflict and you can decide which version to keep.
* The special ViceVersa PRO 2 installer for Windows 64-bit can be downloaded from here: http://www.tgrmn.com/web/kb/item74.htm For other operating systems such as Unix, Linux or Netware, as long as the machines running these platforms are visible to the Windows machine, ViceVersa can synchronize and replicate files. ViceVersa must run on one of the supported operating systems listed above.
When using VSS Volume Shadow Copies in Vista, ViceVersa PRO gives this error message if you try to copy an Outlook OST file: This is by design in Windows Vista. Windows Vista Volume Shadow Copies do not include Outlook OST files. << Maintaining changes to .ost files within shadow copies is expensive in terms of space and I/O activity. The performance impact doesn’t occur during the image backup itself--the only extra work at backup time is backing up the .ost file as part of the image. Instead, the performance impact occurs during the ongoing, everyday I/O to the .ost file when Outlook is running. If the .ost changes were kept in shadow copies, then every time Outlook writes to the .ost file, the result is a copy-on-write I/O hit (2 writes, 1 read). Although we have worked to reduce the impact of copy-on-writes on shadow copies, a heavily churned file like an .ost file could still cause problems. For these reasons, and the fact that .ost files can be regenerated, we chose to delete .ost files from the shadow copy before the image is created. Even if the performance issues didn’t exist, there are situations where Exchange will, after an .ost is restored, detect a “future” version of the .ost file and force you to delete and then regenerate the local .ost file. Therefore, it’s still preferable to regenerate an .ost file instead of restoring it. >> Hence, OST files cannot be copied with ViceVersa PRO using VSS Volume Shadow Copies, on Windows Vista. To prevent ViceVersa PRO from reporting this error with OST files and VSS, exclude the OST file from the profile. Add an exclude file filter to exclude the file "outlook.ost", under profile settings -> file filters.
Yes, when you can "see" the source and target folders using Windows Explorer and you can manually copy/move/delete files between the two machines. ViceVersa will have no problem in synchronizing or mirroring the folders. The type of connection is not important. This includes connections such as LAN, WAN, VPN, Bluetooth and also storage media such as external Hard Disks, Network Disks, USB Disks, Zip Drives, USB Keys, CD-R, CD-RW, DVD, etc.
ViceVersa PRO 2 is available as a 64-bit application for 64-bit Windows, specifically for
The special installer for ViceVersa PRO 2 64-bit can be downloaded here: http://www.tgrmn.com/web/downloads/vvpro64.exe
By default the VVLauncher service is installed under the LocalSystem account. The LocalSystem account does NOT have access to network drives. To access the network you need to run the VVLauncher service under a user account which has access to the network drive.
Note: Do not use mapped drives to access the network. Instead use UNC paths ( eg \\server\share\ ). Services do not recognize mapped drives.
You are probably running the VVLauncher service under the "Local System" account. The "Local System" account does not have access to network resources. This is causing the error. | |||||||||||||||||||||||||
(ViceVersa PRO). VVEngine is our most advanced scheduling tool for ViceVersa PRO, available as a separate download. With VVEngine you can manage multiple profiles using the Internet Browser; organize profiles into categories; set profiles to run every X minutes, every X hours, every X days; set your profiles to run at startup or as soon as file changes are detected; detect external drives and network connections, re-run profiles on error and much more ...