High,
I'm very new to disparity, looking for something like snapraid but with a friendly UI side . I'm wondering, is there a way to shedule or remotely update the parity information?
Thanks!
MaD
disParity » General Discussion
shedule/remotely update
(11 posts)-
Posted 2 years ago #
-
You can't schedule automatic updates in the current version but I plan to add support for that soon as it is a frequently requested feature.
Posted 2 years ago # -
Superb!
Can't wait for that feature! I think you allready made a great piece of software.
I did however found a bug or an issue I would like to report to you.I had a 2 drive parity going on and was testing it's behaviour when the drive(the one with the original data, not the parity drive) would die (I deleted it's partition to simulate).
I then tried to 'restore' (right clicking on the drive, then restore). And it kept on 'scanning'. When I repeated the process however but allready had made a new partition on the drive and added it as a drive in disParity, with a different name and letter to simulate a fresh disk, it did restore the single test file I had stored almost instantaniously.
Did I do something wrong?
Thank you very much and good luck!
ps: If you would ever need a Dutch translator(website/helpfile/program), I'm your guy, happy to help out ;)Edit: missing information
Posted 2 years ago # -
There is no "restore" command, I assume you mean "recover", correct?
When you choose "Recover...", the first thing disParity does is a scan, to make sure that a full recover of the drive is possible, so that's normal behavior. After that, it should have prompted you for a location to place the recovered files. Did you not get the dialog asking you to choose a location for the files?
Posted 2 years ago # -
Correct,
and in the first situation it seemed like it was taking waaay too long and never got the dialog, in the second however it was almost instantanious.Posted 2 years ago # -
That's a good point, if scanning takes a long time, doing a scan immediately after selecting "Recover..." may not be the best user experience. I'll have to think about a better way of handling that.
Posted 2 years ago # -
You could always have a pop up box appear if it detects changes which says something like "Changes have been detected, do you wish to perform an Update? Yes / No. If Yes, then have it skip the scan and use the results of the just finished scan. If no, return the user to the main interface and act as it currently does. That way it is up to the user if he wants to do an immediate update or not - if he does not, then a scan needs to be performed again since we do not know what may have changed.
A warning about what Update does, with regards to undelete and recovery, might be in order as well, just not sure how to word it.
Posted 2 years ago # -
Is your suggestion about what happens when the user selects "Recover..." (as we've been discussing here) or for some other part of the app?
There's a difference between a scan and an update. A scan has to be performed to even know whether there are changes or not. Update then processes the changes. The last scan may have been performed a long time ago so disParity doesn't know if the drives have changed since then and can't just use the results of the last scan. It's possible that drives have changed in such a way that a full recover may not be possible (e.g. files were deleted from other drives) but there's no way to know without doing a scan, so that's why "Recover..." triggers a scan first.
BTW this may all change anyway in the "automatic update" version (still tinkering with that, sorry for the delay folks) because with that feature enabled, disParity will know instantly whether changes have occurred on any drive. It won't know what the changes are, but it will at least know whether or not a scan even needs to be performed.
Posted 2 years ago # -
OOPS! Sorry about that, I lost the train of the thread. I somehow shifted to update, my bad. The issue is that when you start the program it automatically does a scan and tells me there are differences. When I click the update, it scans again. Why scan it twice? Since I am turning all my blurays into sparse files, it takes a LONG time for each scan - and then when I click update it does the exact same long scan again before even starting the update. If it gave me a popup asking if I wanted to update, it could skip the scan since it knows it was just done. That would same me a lot of time.
Sorry for the confusion!
Posted 2 years ago # -
I aggree with cybrsage, such a popup is a good idea.
For now I'm use to cancel the first scan as soon as I can and clic update.
The little problem is : I don't see the changes (even if I know what I changed it is a little control)Posted 2 years ago # -
The issue is that when you start the program it automatically does a scan and tells me there are differences. When I click the update, it scans again. Why scan it twice?
Keep in mind that disParity is meant to be left running. It doesn't have to be, but that's how I designed it to be used. So, you only launch in once in a while, but you run "Update" all the time.
It does a scan when you first launch the app so that it can update the status of all the drives. If it doesn't do a scan at launch time, all the drive status indicators would just sit in the "unknown" state.
It also always does a scan as part of a every Update since it needs to make sure it is processing the latest and greatest changes. Any amount of time may have elapsed between when you first launched disParity and when you start an Update, so any number of changes may have occurred between the two.
Now, in your case, if the second scan is taking a long time with sparse files, then something is still wrong. The test version I sent you was supposed to fix that issue. Can you confirm that the second scan (the one that is part of the update) is still showing that bug?
And again, as I said before, all this is going to change anyway with automatic updates. With that feature enabled, disParity will always know whether anything has changed on a drive, and can skip a lot of unnecessary scans.
Posted 2 years ago #
Reply
You must log in to post.