• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 26 subscribers
  • Views 5322 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Feature Request: Build in check to Rapid Recovery to avoid a new base image on every dirty reboot

mmacdonald31
over 8 years ago

All, I would like there to be some checks in place to confirm the integrity of a back up after an OS is not cleanly shutdown to avoid new base images all the time.

  • 0 over 8 years ago

    YES!!!!!  We need 100% control over new bases.  I have seen bases get created even when the OS has had no bad shutdowns.

  • 0 over 8 years ago

    There are multiple reasons for base image creations, many of them unrelated to bad shutdowns. Basically there are 3 categories of issues conucive of base images all related to the so called change logs (located in the System Volume Information of each volume):

    1. The change logs are not updated while there are blocks changed on the volume (most common case a system crash)

    2. The change logs cannot be read (common issue -- anti virus locking the change logs)

    3. The amount of change on the volume is more than the Agent can process (the rule of thumb is 40% on a good size volume but there are many other factors, like system load).

    There is always the possibility that the change logs get corrupted but this happens rarely -- i.e. the change logs are locked long enough that the changed volume blocks are lost -- this may be the result of AV or some other third party software.

    In my opinion, the ideal for getting read of unwanted base images would be a new operation -- let's call it rolldown that would compare the base image with the data already present in the repository and transform it into an incremental. Other option that nay be of interest would be agent side deduplication.

  • 0 over 8 years ago

    Hi Tudor, thanks for the thorough response.  I agree on the rolldown concept.  Can  you move that detail into the feature request?  Base image creation is pretty impactful.

  • 0 over 8 years ago

    DELL-Tudor P said:
    In my opinion, the ideal for getting read of unwanted base images would be a new operation -- let's call it rolldown that would compare the base image with the data already present in the repository and transform it into an incremental.

    You mean like how They used to do it in Replay4 and that we've been asking for since they stopped doing it in version 5 (and didn't use in version 6). Yes, that'd be awesome.

    This would solve so many issues, like not requiring large dedupe cache to help when new base images are taken, wow, what a concept.

    Can't see this request making it though, since Dell are concentrating on agent side dedupe.  Not sure how that will help replication though so not really a solution to the problem unless i'm mistaken.  maybe the new repository will fix that but lots of things to fix something that used to work and does for multiple competing products