Slowly Boot

[Werderforever]

Hi,

my computer is booting very slowly. From Rollback Subconsole to appearing colouredt tray icon of Rollback it takes 5 or 6 minutes, sometimes 7 minutes.
(The grey icon of Rollback appears about 2 minutes earlier)

I don´t have so much services and systemstarts, disabling those don´t reduces the boot time relevant.

I have observed that there are many, many hard disk activities.

I have the suspicion that the long boot time belongs to Rollback.

What can I do? Do you have had any problems like this with Rollback?

I have attached two screenshots.

Two snapshots are very big. Number two = 20009 and Number five = 42649 MB.

Is it possible that these snapshots slows down pc boot?
Is it reasonable to create a new baseline?

Or do you have another idea?

Many thanks for help!

Werderforever

[Froggie]

Greetings WerderForever! It is not normal for Rollback to add that much time to your BOOT process... mine adds about 10-sec at the most.

I noticed you hadn't taken a snapshot for 3-mo, and when you did, it was over 42gB in size... that's pretty big. I also noticed that including that snapshot, you took 3 more. One of Rollback's DEFAULT options has those snapshots being automatically defragmented after taking 4 snapshots. What you may have seen is that 1-time process by Rollback doing its defragmenting and cleanup. If that's the case, you won't see it again 'til you create some BIG snapshots.

I would also suggest an "UPDATE Baseline" operation (not a "RESET to Baseline) since you've gone so long without taking a snapshot...

Other than the above, I can't think of anything Rollback can do to you in that area...

[Werderforever]

Originally Posted by Froggie

I noticed you hadn't taken a snapshot for 3-mo, and when you did, it was over 42gB in size... that's pretty big.

Snapshots are done automatically each hour. But I have deleted the old snapshots because they are not important for me.
After deleting some of these snapshots some other snapshots were going bigger an bigger...

Werderforever

[Froggie]

Originally Posted by Werderforever

Snapshots are done automatically each hour. But I have deleted the old snapshots because they are not important for me.
After deleting some of these snapshots some other snapshots were going bigger an bigger...

That's what's supposed to happen. If the data in the old snapshot is replicated in the newer snapshot, the newer one will get bigger when you delete the old ones.

It's hard to believe you've had 45gB of "changes" on that system through normal operation. My guess is that you might have run (or are running automatically) some disk defragging operation OUTSIDE of Rollback. If so, that will generate some very large snapshots. It's not necessary to do that when running Rollback. Also, if you didn't shut off SYSTEM RESTORE when you installed RB, that will also create large snapshots.

For sure you should UPDATE BASELINE on your machine and see if the looooooong BOOT time continues. Also look for those defragging processes and stop them (NORTON or somebody in the AV business does some of this stuff automatically. I don't use it so I'm not sure what it may be... others may be able to chime in and give some details).

[carfal]

I find that over time from when i first install Rollback that the boot times does get longer and longer. I've gladly accepted this as a compromise. However my boot times have never gotten as long as you describe.

By the fourth month of Rollback use my boot times may reach about 3min (from a 1 minute boot time at first install). At this point there's usually is a new build release at which time i proceed to do the ritual uninstall, chkdsk, defrag and finally reinstall of Rollback. Updating the baseline as Froggie suggests will work as well but i find that taking the opportunity to defrag while Rollback is uninstalled invaluable.

Originally Posted by Werderforever

After deleting some of these snapshots some other snapshots were going bigger an bigger...

Again as Froggie has stated this is normal. The reason is that each snapshot builds upon the previous snapshot along the same tree. Think about it.

1.Lets say you've just taken SS1 (SnapShot 1).
2.Now you create a new file (say 2GB...call this File1) and take SS2.
3.Now you create another file (say 4GB...call this File2) and take SS3.


Size of SS2 will be 2GB because this is where you created the new File1
Size of SS3 will be 4GB because this is where you created the new File2. You are still able to see File1 in SS3 because SS3 is a child snapshot of SS2. However for now File1 actually occupies space in SS2.

If you delete SS2, File1 will "migrate" and now belongs to SS3. SS3 will increase in size by 2GB to become 6GB in total size.

The above principle is a "simple" explanation as to why a snapshot that directly follows another snapshot you delete suddenly jumps in size.

There's nothing simple about describing how Rollback works as the above example shows.

I just hope your not scratching you head even more.

[Werderforever]

Originally Posted by Froggie

It's hard to believe you've had 45gB of "changes" on that system through normal operation. My guess is that you might have run (or are running automatically) some disk defragging operation OUTSIDE of Rollback.

No, I have installed my OS and all programs. A lot of programs I have tested and then "rollbacked" the system.
Only Windows Defrag, but I think, that Rollback "blocks" Defragmentation?

Originally Posted by Froggie

Also, if you didn't shut off SYSTEM RESTORE when you installed RB, that will also create large snapshots.

I have don´t disabled it during installation, because I need the function "Previous Versions" from System Restore for Drive D, which is not under protection of Rollback.

Originally Posted by Froggie

Also look for those defragging processes and stop them (NORTON or somebody in the AV business does some of this stuff automatically. I don't use it so I'm not sure what it may be... others may be able to chime in and give some details).

No Norton or others.

Many thanks for your help!
Werderforever

[Werderforever]

Originally Posted by carfal

Size of SS2 will be 2GB because this is where you created the new File1
Size of SS3 will be 4GB because this is where you created the new File2. You are still able to see File1 in SS3 because SS3 is a child snapshot of SS2. However for now File1 actually occupies space in SS2.

If you delete SS2, File1 will "migrate" and now belongs to SS3. SS3 will increase in size by 2GB to become 6GB in total size.

The above principle is a "simple" explanation as to why a snapshot that directly follows another snapshot you delete suddenly jumps in size.

Many thanks for your explanation, that´s very interesting for me.
To understand Rollback "system" is not easy.

Werderforever

[carfal]

Originally Posted by Werderforever

Only Windows Defrag, but I think, that Rollback "blocks" Defragmentation?

Yes, Rollback does block actual defragmentation to occur when using external defraggers. So why waste precious resources by allowing the task to run for drive C: ??

Originally Posted by Werderforever

I have don´t disabled it during installation, because I need the function "Previous Versions" from System Restore for Drive D, which is not under protection of Rollback.

System Restore will use a big chunk of your disk space on Drive C:. It's a clue as to the large disk usage. System Restore allows you to choose which drives you want protected. You should choose to only protect Drive D: and leave C: for Rollback to look after.

Originally Posted by Werderforever

Many thanks for your explanation

Your welcome.

[Werderforever]

Now I have disabled Defragging and System restore for Drive C:

But another question: I want to update the baseline with the hope, that boot time will be reduced.

Are there some risk to update baseline like for example a-non-booting-pc or something like that?

I´m using Rollback since 3 or 4 months and I have to learn something more about it.

Many thanks...

Werderforever

[Froggie]

WF... most of us re-baseline (Update Baseline) our systems regularly (without issue), mainly 'cause we really don't need all those snapshots for anything if all is going well... what I would call a PERIODIC CLEANUP.

If you have all defragging OFF and SYSTEM RESTORE activated for only non-Rollback protected volumes, a re-baseline is a fairly threat free function and your BOOT times should return close to normal (for Rollback... mine are about 15-20 sec. longer than a bare system).