Rollback RX v10.x (Home & Professional)

Hi guys

Thank you for the answers . So there is mixed answers in the thread saying basicly it works but it is inadequate .
I only use my pc for some surfing a couple of hours each day and now and then installing a program out of curiousity for inspection and then uninstalling it and that is where RBRX comes in so i am thinking that it might be adequate for that to do the uninstal/reinstall manouver once a month...yes/no ?

If it is not adequate can the disc get permanently damaged because of that ?
What do i have to do to do an adequate handling of the item ?

Uninstall and reinstall and loosing the snaps is fine with me .

 

For what you are describing in terms of use I would suggest that Macrium V6 will do the trick for you. I have some 250 gigs of data on my drive (2 partitions) and a manual (incremental) snap takes under 2 min to perform. To restore to this snap after testing software takes under 3 min. If thats not fast enough for you then I guess you will need a program like Rx but it seems like a lot of bother and concern for the few minutes difference in speed. Of course if you already own an Rx licence then I can see where you would want to use it.

I had not had issues with the program (Rx) in particular (HDS is another story) until I saw Froggies SSD/TRIM test. Personally I would not use Rx with SSDs until it has been shown that HDS has resolved the problem Froggie has demonstrated. For those who are not using SSDs Rx is fine as long as you know the various pitfalls associated with the program and take steps to protect against them.

 

If you mean Rollback works as a snapshot program... that's correct. If you mean it's inadequate in its responsibilities to allow for the proper management of Solid State Drives... you are also correct. Will that lack of proper management of SSDs affect its long term life and speed... the answer is yes.

With what you describe as your system usage above, I do not foresee any major problems with lack of proper TRIM management of your SSD. That type of usage generates very little WRITE DATA over that 1-mo. time span... not enough to affect much of anything. BUT, if your SSD is currently pretty FULL, then there will be some indications of issues in the months ahead... it all depends on how much data you WRITE along the way.

Once again, with your described usage, any shortened lifespan due to excessive WRITEs of your SSD will not occur for a long, long time.

If Horizon DataSys doesn't fix this problem, the obvious move in the long term is to stop using Rollback and activate a different form of snapshotting based on imaging technology as BG suggested earlier in this thread.

There are a few options in this area with "Macrium Reflect" being one of the excellent choices. For an imaging technology solution, Macrium offers an excellent alternative to Rollback RX. It's RAPID DATA RESTORE technology has proven to be superior to the few other image offerings of this type out there. Using this technology, returning to a recent snapshot will take 1-2 minutes, even a bit faster when using your SSD... just not the "seconds" that Rollback claims.

I have been using Macrium's technology since its "unintended" BETA process was leaked in the Wilders arena and have found it to be an excellent replacement for Rollback as a snapshot tool, especially for what you describe above as your main reason for using it. The reason... I have the patience to wait 1-2 minutes for that "rollback" operation instead of the 45-sec or so with Rollback RX . In addition, Macrium gives me the necessary imaging technology which will allow for the reconstruction of my system upon any catastrophic failure... basically both tools in one application.

But, in the meantime... the non-TRIMming Rollback should suffice as a snapshot tool without issue on your configuration, even without monthly Rollback unInstalls. But pls remember, Rollback is NOT a backup solution... you still need to have that System partition protected in some way so you can reconstruct that system easily upon catastrophic failure.

 

Hi Mr Frog

My disc is currently used to about 35 - 40% of 128Gb and that is pretty much a constant . I use Macrium free as the basic image program and image newly c:a once a month and RBRX free as an equivalent to Windows restore point function a couple of times a month . After reading your post i get it that i am pretty much in the clear - yes ?

Sidenote ; i have been using AX64 for some time but i have to abandon it since it always corrupts my Os after a couple of restores so i always have to run DISM to repair it .

 

Yup, you're fine. But since you're RBrx free when you do the Macrium image, I would reBOOT after the RBrx unInstall and TRIM your SSD ("SSDtool" with W7, Windows OPTIMIZE with W8 ) before (or after) you do your Macrium image.

 

Nice to hear - thank you .

 

PB1, this casual usage you describe above should be trouble free for you, BUT... you must realize that the Macrium image you're taking monthly from your LIVE Windows system will not be restorable in an emergency if the image was taken while Rollback was installed. If you're not familiar with this phenomenon, see Item #7 of the following PDF document, "Rollback RX™ - The “unOfishul” FAQ," for a good basic description of the issues involved.

 

Hello all,

As of late, I've been PM'd on here, asked in our chat, phoned, and emailed asking the question "When Will RollBack Rx Support Windows 10"

For those who are curious, we are actively working on getting a build of our software ready to work with Windows 10. It won’t be ready for some time, as we need to make sure that the software is up to the high standard that both we expect. Also, some infrastructure changes to Windows 10 are causing us to re-evaluate and re-format some of RollBack Rx's features.

We are recommending that any customer wishing to install Windows 10 on a machine uninstall RollBack Rx first. As having the software installed when you go to install Windows 10 will lead to critical stability issues. This goes for installing RollBack Rx on a machine with Windows 10 installed already.

I would recommend bookmarking our blog. We will be announcing the release date for the upcoming Windows 10 builds on said blog, which you can find here: http://blog.horizondatasys.com/

If you have any other questions about our software, I’d be happy to assist you further as always*.

Cheers.

*Unless it's about SSD Trim, to which I'll say it's still being looked over by our Development Team.

 

Kurtis, Thanks for the update but that is a problem for many. Most programs are already compatable with W10. So, if I am using RRX and I want to upgrade to W10, I can't unless I want to uninstall RRX? HDS has a horrendous record of either missing deadlines by miles or just not communicating release dates at all. I can easily see a W10 compatible version of RRX being released more than 1 year after W10 is released. How is DC6 coming along? Missed that mark by more than 1 year. My guess is there will be no DC6 before W10 is released and then the clock starts again. 1 year, 2 years, what do you think?

 

DC V6 will definitely be out soon. We're preparing marketing materials for it (video, newsletter, banners). We wouldn't be doing that if we knew it was going to be a year or two more. I won't say before or after W10 as I honestly don't know, but I'll say that you'll definitely be able to gift Drive Cloner V6 as a x-mas gift this year. You might even see a familiar face in the DC V6 promo material

As someone who's familiar with HDS history, you probably also recall the launch of Version 10 and Windows 8. I get groans from everyone I ask about that, product was rushed and launched to coincide with Windows 8 and there were a myriad of issues. People are still on the early V10 builds and it's a headache for everyone involved. We're aiming to get it out soon after launch of W10, but for the sake of everyones sanity we want to make sure it's done right. If I was betting on it, I'd wager 6 months post-W10 launch.

 

I assume the DC6 release will be W8.1 compatible and not W10 compatible. So the Looooooong wait restarts.

 

MB, DCrxv6 is just another imaging program, even with its "new" capability to image snapshots. Getting it to run under W10 shouldn't be a big deal... nowhere near as big as getting RBrx to do the same. And its snapshot capability under W10 will be useless until RBrx gets there anyway.

Even though I'm one of their "chosen" BETA testers, I have no idea how far the DCrxv6BETA has progressed (don't ask )... but it has had some movement since the process started.

If you're looking for RBrx snapshot imaging under W10 anytime soon... I'd just chill and have a 'rita.

 

Yes, I agree but.... the delays seen to be getting DC6 to cooperate with RRX. If they will be updating RRX for W10, then I assume they will next work on DX6 being compatible with that new version. Look how long they have been working on that with the current ver of RRX. I don't see the pair of RRX and DC ever keeping up with the Windows updates. They will always be behind constantly updating and testing one or the other.

 

Well that's sort of the point no? I mean, as RollBack Rx updates we want Drive Cloner to adapt to that. I think in terms of updates though, they'll be small incrimental updates (i.e. RollBack Rx V11.1, Drive Cloner V6.1).

We haven't tested Drive Cloner Rx V6 on Windows 10 yet, mainly because we don't have a final build yet. However if someone has a Windows 10 build on a VM and would like to test this for us, I'd be happy to shoot them an NFR license for their efforts. PM me if you'd be interested.

I can tell you we're getting close to a finished build. Our Dev Team has really appreciated the feedback provided from Jira, and while sometimes you may not get a response, I can guarantee he sees everything there.

 

@Kurtis Smejkal what will be the turnaround time for Drive Cloner on Windows 10?

Also, SSD Trim update?

 

Hey Overclocker,

Not long, since it's a Windows app, not something like our other software which relies on the surrounding infrastructure. We'll have something very close to post W10 launch.

As for SSD Trim...oh boy haha. I know emotions are extremely high regarding this issue. Right now we're looking strictly at facts, not opinions or anything else. Just facts. When we have the facts, we'll make a conclusion and share it. for now just please exercise some patience as we get the definitive word on this.

 

OK, I have RBRx installed on an SSD and haven't noticed any problems but if there's longer lasting issues I may want to know.

 

You should read the following threads regarding this question and then decide for yourself if Rx is safe to run on with SSDs.

https://www.wilderssecurity.com/threads/rollback-rx-vs-trim-revisited.375823/

https://www.wilderssecurity.com/threads/is-rollback-rx-safe-on-ssd.376826/

 

I am pretty sure HDS has the facts.

BTW Kurtis, did you try to replicate Froggies demo as he invited you to?

 

We are. Still no update.

 

Very revealing...
A team gets decimated to one single person within the same sentence. Maybe HDS should hire a few more developers and fire some marketing people instead.


Cheers
manolito

 

Or you know, ask me for clarification . We do have a Dev Team, the lead developer is the one checking Jira.

 

That does not ans my question or deal with my statement in any way.

 

Your one funny man Kurtis, clarification is something we seldom get from you. By way of example look at your reply to my previous post. Clear as mud.

 

Perhaps you should re-read it. We're testing it, but until we've come to a conclusion it's still ongoing in terms of testing. Despite what some users may think