Jump to content

Maser

Members
  • Posts

    2,054
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by Maser

  1. In order to do a full catalog rebuild (which I've done many times) -- make sure you remove all the .session files before you do the rebuild.    It's also possible that after the groom, one of your .rdb files is hosed (I had that happen and had to go through a whole bunch of iterations to figure out which one was messed up -- and it ended up being some 11K .rdb file causing my rebuilds to fail...)

  2. I run Proactive Backup scripts for 100% of my clients.  Most of them are laptops so there is no possible way of knowing when they'll be on line.

     

    In general, though, you can try to schedule upcoming backups (in the Activities section of the Console) if you want to *try* to get them to back up at an approximate time.

     

    i've had zero downside to running Proactive backups and have been doing it that way ever since Retrospect introduced the concept.

  3. Yeah, I never manually groomed immediately after removing past backups.   I have monthly groom scripts that run, so if I have a need to manually groom out a specific backup, then I just remove the backup and wait for the script to take care of the grooming.

     

    *Sometimes* (but usually not), there is an error in grooming that requires a catalog rebuild after the groom.  That's fairly rare, though.

  4. Unlock your media set -- if it's locked.   Then go to "Past Backups" in the console.  You'll see all the backups for your media set (well, I guess it depends on your groom settings).

     

    You can select a past backup and click "Remove".   Then when you groom the media set, it will groom out that specific backup.

     

    My media sets are configured to keep X backups (rather than the "Defined Policy"), so YMMV on what you see in "Past Backups", I guess...

  5. So, FWIW, I had a similar (but not quite) problem after updating from 10.11.2 to 10.11.3.

     

    Normally, I stop the engine in the Sys Pref, but leave it checked to start at system startup.  I did this as usual prior to updating to 10.11.3.   I thought Retrospect was fine -- but it wasn't until a couple of days later that I noticed that none of my proactive backup scripts were working?

     

    Things only started working when a scheduled *groom* script ran -- then as soon as that finished, all the proactive scripts started working again.    I've reported this, but I don't know how easy it is to reproduce...

     

    Bottom line -- it probably makes sense to reboot twice after any 10.11 OS upgrade these days...

×
×
  • Create New...