| Author |
Message |
Mark Smith
Joined: 04 Jul 2019
Posts: 8
|
 Posted: Sun Mar 15, 2020 11:07 am Post subject: Database signature incorrect. Stopping comparison. |
 |
|
I recently split up two very large folders containing a combined ~1.7 million .jpg files into 198 separate folders and setup 198 different VV profiles for each of these folders. (The two large folders were taking too long to sync.) Each profile has its own .tdb file. All of the .tdb files are stored in the same folder on an PCIe Intel Optane SSD. Each vvengine profile uses source file level monitoring.
I've been randomly getting tracking database errors like this:
| Quote: | Unable to open tracking database. It may be inaccessible or in use by another ViceVersa process.
Exit Code: 9
[ERROR] Invalid tracking database "x:\vice versa pro tracking db\vvdb-up-61.tdb". Database signature incorrect. Stopping comparison. Reset the tracking database in the profile settings.
|
What can I do to prevent this incorrect database signature problem from happening? I setup email alerts on failure so I can deal with this problems fairly quickly by resetting the tracking DB. It's happening 10 to 25 times per day since I split everything up. Resetting the tracking DB every time isn't a workable long-term solution. The files are being synced between two live production load-balanced web servers and when they fail it means new content isn't available on one of the two servers.
Server info:
VVEngine Version: v2.2 Server Premium (Build 2210)
VVEngine Max Profiles: Unlimited
System: Windows Server 2019, (Standard Edition), (HyperV), (x86-64 Processor) v10.0 Build:17763 - Emulated OS: Windows Server 2019, (Standard Edition), (HyperV), (x86-32 Processor) v10.0 Build:17763
Server has 192GB of RAM, typically 25 to 35 GB in use. Dual Xeon 5690,Dell R710. The SSD storing the .tdb files is using 3.9GB out of an available 260GB. I have moved the VVEngine Journal files to the same SSD but in a different folder. |
|
| Back to top |
|
 |
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8769
|
| Posted: Mon Mar 16, 2020 12:30 am Post subject: |
|
|
Hi, it sounds like the tracking DB is not saved properly.
For the profile where this happens:
| Quote: | Unable to open tracking database. It may be inaccessible or in use by another ViceVersa process.
Exit Code: 9
[ERROR] Invalid tracking database "x:\vice versa pro tracking db\vvdb-up-61.tdb". Database signature incorrect. Stopping comparison. Reset the tracking database in the profile settings. |
Does it show an error saving the tracking DB in the profile log for that profile?
thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com
Last edited by TGRMN Software on Tue Mar 17, 2020 12:19 am; edited 1 time in total |
|
| Back to top |
|
|
Mark Smith
Joined: 04 Jul 2019
Posts: 8
|
| Posted: Mon Mar 16, 2020 10:25 am Post subject: |
|
|
| I'll setup logging for all of the profiles and report back. At the moment I don't have it enabled. |
|
| Back to top |
|
|
Mark Smith
Joined: 04 Jul 2019
Posts: 8
|
| Posted: Tue Mar 17, 2020 5:15 pm Post subject: |
|
|
I haven't had another error since I enabled logging. When I added the log-file-per-profile settings I also enabled the "Minimize Memory Usage" option for all of the profiles. I think the memory setting has fixed my problem.
My server has 192GB of RAM with 20 to 35Gb in active use at any time. The File Cache Manager was chewing up most of the rest of the system's memory as Standby/cache. (as listed in Resource Monitor) I think VV was possibly bumping into out-of-memory issues launching new processes and not enough available Free memory to do so. |
|
| Back to top |
|
|
Mark Smith
Joined: 04 Jul 2019
Posts: 8
|
| Posted: Wed Mar 18, 2020 7:00 am Post subject: |
|
|
It happened again tonight. Nothing in the logs about not being able to save the tracking database. However this is the first time this particular profile is running since logging was enabled. It might have had a problem saving the tracking DB prior to enabling logging.
The server has 21.7GB of of Free RAM according to Resource Monitor. And the VVengine process has 778 active threads. Seems like a lot of threads. More than double the NT Kernel thread count at 308.
Here's what's in the log file for the failed profile: (edited some things out)
2020-03-18 01:15:12 :
2020-03-18 01:15:12 : -
2020-03-18 01:15:12 : START ID: 20203185159-3389343-1424
2020-03-18 01:15:12 : ************************************************************
2020-03-18 01:15:12 : Profile Started.
2020-03-18 01:15:12 : ************************************************************
2020-03-18 01:15:12 : Version: ViceVersa PRO 3.0 Build 3002 64-bit (SN469) [Registered][Server][Premium][mark-smith...]
2020-03-18 01:15:12 : Command Line: "2020-03-18 01:15:12 : START ID: 20203185159-3389343-1424
2020-03-18 01:15:12 : ************************************************************
2020-03-18 01:15:12 : Profile Started.
2020-03-18 01:15:12 : ************************************************************
2020-03-18 01:15:12 : Version: ViceVersa PRO 3.0 Build 3002 64-bit (SN469) [Registered][Server][Premium][mark-smith...]
2020-03-18 01:15:12 : Command Line: "[path]\VICEVERSA.EXE" "[path]\ViceVersa PRO\uploads-data-92.fsf" /hiddenautosync /vveng "/vvps:[path]94C73A86-E61548AF-E220A08D-5626D773-F7DB409A.vv.txt "
2020-03-18 01:15:12 : System: Windows Server 2019, (Standard Edition), (64 Bit Edition), (HyperV), (x86-64 Processor), (96dpi) v10.0 Build:17763
2020-03-18 01:15:12 : User: Administrator
2020-03-18 01:15:12 : Computer: computername
2020-03-18 01:15:12 : **** Profile: [path]\ViceVersa PRO\uploads-data-92.fsf
2020-03-18 01:15:12 : **** - Folders -
2020-03-18 01:15:12 : **** "[path]\uploads_data\92\" <to> "[path]\uploads_data\92\" (Include Subfolders)
2020-03-18 01:15:12 : **** - Comparison Settings -
2020-03-18 01:15:12 : **** Comparison Type: Size and Timestamp
2020-03-18 01:15:12 : **** - Execution Settings -
2020-03-18 01:15:12 : **** Method: Backup (Mirror Source to Target)
2020-03-18 01:15:12 : **** No overwrite / read-only / error confirmations
2020-03-18 01:15:12 : **** Tracking Database: "H:\vice versa pro tracking db\vvdb-up-92.tdb"
2020-03-18 01:15:12 : **** Do not rescan target
2020-03-18 01:15:12 : **** Log File: "[path]\vv_profile_logs\uploads-92.log" (max 10000 KB)
2020-03-18 01:15:12 : **** No archive for deleted/replaced source files
2020-03-18 01:15:12 : **** No archive for deleted/replaced target files
2020-03-18 01:15:12 : **** Process Priority: Realtime
2020-03-18 01:15:12 : **** Use Windows native file copy
2020-03-18 01:15:12 : **** Speed: 100
2020-03-18 01:15:12 : **** Network friendly folder scanning
2020-03-18 01:15:12 : **** Minimize Memory Usage
2020-03-18 01:15:12 : **** Copy files even if timestamp changes after initial comparison
2020-03-18 01:15:12 : **** Copy directly to destination file (do not use a temporary file)
2020-03-18 01:15:12 : **** Replace newer target files with older source files (backup only)
2020-03-18 01:15:12 : **** Send notification e-mail after execution to....[removed]
2020-03-18 01:15:12 : **** Authenticate using name and password. User name: [removed]
2020-03-18 01:15:12 : **** Use Secure Connection (SSL/TLS)
2020-03-18 01:15:12 : [Incremental (=partial) recomparison of source and target, based on VVEngine detected changes, activated]
2020-03-18 01:15:12 : [VVEngine incremental recomparison filters : 1 files, 0 subfolders]
2020-03-18 01:15:12 : [VVEngine detected changes: detailed list follows (files)]
2020-03-18 01:15:12 : Include: [path]\uploads_data\92\9246\c2cc2d41d4054d6e9f68370b32e32d2c7eb2e1632a7e48f-ds
2020-03-18 01:15:12 : [Total: 1 (1)]
2020-03-18 01:15:12 : [VVEngine detected changes: detailed list follows (subfolders)]
2020-03-18 01:15:12 : Include: [path]\uploads_data\92\9246\^
2020-03-18 01:15:12 : [Total: 1 (0)]
2020-03-18 01:15:12 : Minimizing memory usage...
2020-03-18 01:15:12 : Using network friendly folder scanning.
2020-03-18 01:15:12 : [ERROR] Invalid tracking database "[path]\vice versa pro tracking db\vvdb-up-92.tdb". Database signature incorrect. Stopping comparison. Reset the tracking database in the profile settings.
2020-03-18 01:15:12 : Aborted.
2020-03-18 01:15:12 : Exit Code: 9. Unable to open tracking database. It may be inaccessible or in use by another ViceVersa process. [ERROR]
2020-03-18 01:15:12 : Sending E-Mail ...
2020-03-18 01:15:12 : Connecting to SMTP server: [removed]
2020-03-18 01:15:12 : Sending E-Mail to: [removed]
2020-03-18 01:15:13 : Done.
2020-03-18 01:15:13 : [INFO] E-Mail sent successfully.
2020-03-18 01:15:13 : ************************************************************
2020-03-18 01:15:13 : END ID: 20203185159-3389343-1424 |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8769
|
| Posted: Wed Mar 18, 2020 12:09 pm Post subject: |
|
|
Hi, yes, there needs to a be a point in the log where there is an issue with saving the profile properly....
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
| Back to top |
|
|
Mark Smith
Joined: 04 Jul 2019
Posts: 8
|
| Posted: Wed Mar 18, 2020 12:18 pm Post subject: |
|
|
| what would a string of text be that I could use to search the log files for the saving error? I manually ran all of the vvengine 213 profiles so there's something in the log file for each of them. I have never had a vvengine profile go into error status on saving a file. I have only had errors for invalid tracking signatures. Would the failed save trigger an error state or silently log the error to the text file? |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8769
|
| Posted: Wed Mar 18, 2020 11:50 pm Post subject: |
|
|
If it happens again now for a profile please send log to support via e-mail we will check if any clues. thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
| Back to top |
|
|
|
ViceVersa HOME 
Forum FAQ
Search Forum
Register
Profile
Log in
