<?xml version="1.0" encoding="iso-8859-1"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
<channel>
<atom:link xmlns:atom="http://www.w3.org/2005/Atom" rel="hub" href="https://pubsubhubbub.appspot.com/" />
<atom:link xmlns:atom="http://www.w3.org/2005/Atom" type="application/rss+xml" rel="self" href="http://backupforum.progforums.com/BackupForum/rss.php?tid=113" /> 
<title>Backup forum : IDrive : Glitches or Snags : Verify backup set not occurring when it should</title>
<link>https://backupforum.progforums.com/BackupForum</link>
<description> Backup forum</description>
<language>en</language>
<docs>http://backend.userland.com/rss</docs>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=989#p989</link>
<guid isPermaLink="false">989@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: I just looked at my Tracefile.txt and the Verify process is still happening at odd times, so the bug is still in there. But that doesn't really explain why your backup set isn't being verified at all. It should happen automatically at some point.
</description>
<pubDate>Tue, 10 Dec 2024 14:28:57 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=988#p988</link>
<guid isPermaLink="false">988@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: IDrive support isn't much help.&#160; All I ever get from them is &#34;install the latest update&#34;.&#160; I've learned more from this thread than I've learned from IDrive support.The good thing is that *I think* files that get missed from a backup do get picked up with the next day's backup.
</description>
<pubDate>Tue, 10 Dec 2024 14:21:26 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=987#p987</link>
<guid isPermaLink="false">987@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: With my situation, it was as if when I slept my PC the timer stopped counting and the verify happened at weird times, but I could predict when that would be depending on how long my computer was asleep for. I don't know why IDrive used a timer rather than a time-of-day trigger for the Verify operation.
</description>
<pubDate>Tue, 10 Dec 2024 13:46:18 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=986#p986</link>
<guid isPermaLink="false">986@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: Here are the most recent entries in tracefile.txt.&#160; Note that there is no entry for the 7th.&#160; The most recent backup that said &#34;0 files backed up&#34; was at 3AM on the 8th.There seems to be no correlation between the &#34;timer set to&#34; time and the timestamp of each of these lines.2024-12-04 20:10:00,089 INFO&#160; [69] - [Verify Backupset]: Timer set to: 0 Days: 23 Hours: 59 Minutes: 59 Seconds2024-12-05 16:52:41,875 INFO&#160; [38] - [Verify Backupset]: Timer set to: 0 Days: 3 Hours: 17 Minutes: 18 Seconds2024-12-05 20:10:00,111 INFO&#160; [62] - [Verify Backupset]: Timer set to: 0 Days: 23 Hours: 59 Minutes: 59 Seconds2024-12-06 20:10:00,092 INFO&#160; [36] - [Verify Backupset]: Timer set to: 0 Days: 23 Hours: 59 Minutes: 59 Seconds2024-12-08 06:58:02,606 INFO&#160; [77] - [Verify Backupset]: Timer set to: 0 Days: 13 Hours: 11 Minutes: 57 Seconds2024-12-08 08:08:27,062 INFO&#160; [38] - [Verify Backupset]: Timer set to: 0 Days: 12 Hours: 1 Minutes: 32 Seconds2024-12-08 08:19:25,115 INFO&#160; [71] - [Verify Backupset]: Timer set to: 0 Days: 11 Hours: 50 Minutes: 34 Seconds2024-12-08 20:09:59,004 INFO&#160; [5] - [Verify Backupset]: Timer set to: 0 Days: 0 Hours: 0 Minutes: 1 Seconds2024-12-08 20:10:00,026 INFO&#160; [70] - [Verify Backupset]: Timer set to: 0 Days: 23 Hours: 59 Minutes: 59 Seconds2024-12-09 06:44:50,189 INFO&#160; [74] - [Verify Backupset]: Timer set to: 0 Days: 13 Hours: 25 Minutes: 9 Seconds2024-12-09 11:42:26,054 INFO&#160; [68] - [Verify Backupset]: Timer set to: 0 Days: 8 Hours: 27 Minutes: 33 Seconds2024-12-09 20:10:00,056 INFO&#160; [6] - [Verify Backupset]: Timer set to: 0 Days: 23 Hours: 59 Minutes: 59 Seconds2024-12-09 20:42:34,901 INFO&#160; [70] - [Verify Backupset]: Timer set to: 0 Days: 23 Hours: 27 Minutes: 25 SecondsI'm having to retry each of my posts several times to get one to finally post.
</description>
<pubDate>Tue, 10 Dec 2024 13:27:27 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=985#p985</link>
<guid isPermaLink="false">985@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: I don't know what to suggest other than contacting IDrive support, not that they are necessarily helpful.When I encounted a problem like this, I believe they said that installing the latest update isn't sufficient and that I needed to actually uninstall and reinstall it:
As per the update from the back-end team we request you to perform clean installtion of the IDrive application using the below steps.1. Uninstall the IDrive application2. Rename the &#34;IDriveWindows&#34; folder to &#34;IDriveWindowsOLD&#34; in the installation path [C: Program Files (x86)IDriveWindows]3. Click on Start &#62; Open Run &#62; Type &#34; appdata &#34; and Hit on &#34; Enter &#34; &#62; Go to Local &#62; find &#34; IDrive &#34; folder and rename it to &#34; IDriveOLD &#34;4. Download the latest version of &#34;IDrive Windows&#34; application using the link given below:https://www.IDrive.com/thankyou_win5. After downloading the latest version of IDrive, Right-click on the setup and select 'run as administrator' to install the application.Please run the backup and check and let us know if you are still facing any issue.
Of course that was years ago so the process may have changed. Again, as I recall, this didn't fix the problem, but one day it just went away.
</description>
<pubDate>Tue, 10 Dec 2024 13:25:11 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=984#p984</link>
<guid isPermaLink="false">984@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: Yes, I've rebooted.&#160; I also installed the latest update just a couple days ago, 7.0.0.19.&#160; I'll try to attach a screenshot.&#160; I see 6 copies of tracefile.txt.&#160; The only one that is up to date is the one in ibcommon itself.
</description>
<pubDate>Tue, 10 Dec 2024 05:02:11 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=983#p983</link>
<guid isPermaLink="false">983@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: tlveik wrote:...The log file you referred to, Tracefile.txt, seems to have been abandoned since the last entry in it is dated 09/22/2024. ....
On my system I see five different Tracefile.txt files in different locations within IBCOMMON. But the ones for the two Windows users on my PC both show that they were modified today. So IDrive is still using Tracefile.txt. Make sure you're looking in your username's folder. The three other Tracefile.txt files I see (one is in the SYSTEM folder, one is in IBCOMMON itself) show old modification dates.Have you tried rebooting? I vaguely remember having a similar problem years ago, and IDrive support wanted me to reinstall the application. Not a great solution, but maybe it helps some people. Is the clock on your PC accurate?
</description>
<pubDate>Tue, 10 Dec 2024 02:27:01 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=982#p982</link>
<guid isPermaLink="false">982@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: Ah nice, you're still here.For reference...The log file you referred to, Tracefile.txt, seems to have been abandoned since the last entry in it is dated 09/22/2024.When IDrive reports that 0 files have been backed up, I can go into IDrive, manually do a &#34;Verify Backup&#34;, then manually initiate another Backup, then IDrive does indeed backup the files that it missed with its automatic scheduled backup.&#160; So that seems to imply that the daily scheduled &#34;Verify Backup&#34; step gets missed sometimes for some reason.Why that additional step is necessary, I don't know.&#160; It must try to learn on the fly which files need to be backed up and this &#34;Verify Backup&#34; step is just a safeguard if its on-the-fly method misses something?&#160; Who knows.
</description>
<pubDate>Tue, 10 Dec 2024 02:14:43 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=981#p981</link>
<guid isPermaLink="false">981@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: I'm still here!My backups have been working fairly well over the past year, and the issues I was seeing when I first started this thread seem to have disappeared. Sorry you're having trouble, @tlveik. Wish I had more I could share with you.
</description>
<pubDate>Tue, 10 Dec 2024 01:51:39 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=980#p980</link>
<guid isPermaLink="false">980@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: I think I'm having a similar issue with IDrive.&#160; Each morning it reports on the previous nights backup results.&#160; Sometimes it will say than 0 files were backed up because none needed to be backed up.&#160; This is never true for me.I didn't know that a backup needed to be preceded by a &#34;Verify Backup&#34;.&#160; I have that scheduled to run once each day.&#160; Perhaps that step gets missed somehow sometimes?I know this thread is old.&#160; Are you still here Astuff?&#160; Have you learned any more about this issue?
</description>
<pubDate>Tue, 10 Dec 2024 01:03:17 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=411#p411</link>
<guid isPermaLink="false">411@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: Virtualbox and VMWare.I couldn't get Virtualbox to work reliably with USB devices so I moved some of my Linux VMs to VMWare.
</description>
<pubDate>Thu, 25 Mar 2021 19:25:05 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=410#p410</link>
<guid isPermaLink="false">410@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: OK, well, thank you...this is definitely good enough for me to assume it's IDrive's problem, and I can stop feeling paranoid, at least. :-)Out of curiosity, what are you using for your VM...is it VirtualBox, Hyper-V, VMWare...?
</description>
<pubDate>Thu, 25 Mar 2021 18:25:12 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=409#p409</link>
<guid isPermaLink="false">409@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: Astuff wrote:Interesting development. I wonder how accurately pausing the VM mimics sleep. When you unpaused the VM, did the time of day correct instantly? If so, this kinda confirms that they aren't purely using time-of-day to trigger the Verify.
Yes and no!I've always had a problem with my W10 VM time, so I have a background app running that keeps it correct by synchronizing with Internet time servers.So when I unpaused it, the time was behind, but updated itself after a couple of minutes. It was certainly correct before the scheduled verify time was reached.
</description>
<pubDate>Thu, 25 Mar 2021 18:13:18 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=408#p408</link>
<guid isPermaLink="false">408@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: Interesting development. I wonder how accurately pausing the VM mimics sleep. When you unpaused the VM, did the time of day correct instantly? If so, this kinda confirms that they aren't purely using time-of-day to trigger the Verify.It does look like Win10 20H2 did change the sleep/standby mechanisms, I think making &#34;Modern Sleep&#34; or &#34;Modern Standby&#34; the default when possible. I'm running on a PC that can't do Modern Sleep. Purely speculating here, but maybe whatever mechanism IDrive uses to count down its Verify timer continues counting during Modern Sleep, but doesn't count down during Standard (S3) sleep, and the IDrive programmers are assuming all Win10 20H2 systems use Modern Sleep.
</description>
<pubDate>Thu, 25 Mar 2021 18:05:51 +0000</pubDate>
</item>
<item>
<title>Verify backup set not occurring when it should in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=403#p403</link>
<guid isPermaLink="false">403@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Verify backup set not occurring when it should

Message: Update:I now suspect Windows 10 is the problem! I simulated sleep by pausing the Guest OS for 5 minutes. After resuming it, the Verify ran 5 minutes late.Very strange.My Windows 10 VM has the latest feature update, 20H2. Maybe Microsoft have changed something about the way the time is reported.
</description>
<pubDate>Thu, 25 Mar 2021 17:48:23 +0000</pubDate>
</item>
</channel>
</rss>
