Open Discussion

Expand all | Collapse all

Device Backup Defaults

  • 1.  Device Backup Defaults

    Posted 04-19-2018 14:03
    Hi All,

    It was great meeting some of you at Evolution18, I am already looking forward to Evolution19!

    I have an odd need as a result of some decisions made by management that are causing me headaches, and I wonder if anyone has a solution for a similar problem.

    Problem:
    Management wants file selection unlocked, however, they are also mandating that at least the ":user" selection is backed up in order to get the cost incentives we are providing for using Code42 and other software that we are specifying.

    I am hoping there is some creative way to allow users to ONLY add selections to their file selection, and not uncheck their user profile. Might be wishful thinking...

    Thank you in advance!

    ------------------------------
    Josh Fischer
    Cornell University
    Ithaca, NY
    ------------------------------


  • 2.  RE: Device Backup Defaults

    Posted 04-19-2018 16:42
    Have you looked at Backup Sets?  It looks like you can lock the default or organization-level file selection in a backup set while allowing users to create another backup set that includes other files.  I haven't tested it, but it looks promising for your requirements.  Worth checking out in a test environment or organization.

    One thing: I believe it would still be possible for users to exclude their home directory by using file exclusions, since exclusions apply across backup sets pointing to the same destination.

    See the documentation here:
    https://support.code42.com/Administrator/6/Configuring/Backup_sets
    https://support.code42.com/CrashPlan/6/Configuring/Multiple_backup_sets_with_a_single_destination


    ------------------------------
    Brad Hodges
    Baylor University
    ------------------------------



  • 3.  RE: Device Backup Defaults

    Posted 04-20-2018 20:01

    Brad:

      Josh and I considered this, but (according to the TechExperts) unless the :user specification was part of the second backup set, backup set 1 would specify sending files for :user to the archive - and then backup set 2 would, by not specifying :user, cause those same files to be deleted from the archive.  Lots of churn - to the net loss of the user.

    Bob



    ------------------------------
    Robert Talda
    System Engineer IV
    Ithaca NY
    ------------------------------



  • 4.  RE: Device Backup Defaults

    Posted 04-23-2018 12:25
    Hi Brad,

    I had considered several odd ideas in order to get what I needed, but I hadn't thought of that yet. I will give this a test sometime this week, and let you know if that works for us! Thank you, for the suggestion!

    ------------------------------
    Josh Fischer
    Cornell University
    Ithaca, NY
    ------------------------------



  • 5.  RE: Device Backup Defaults

    Posted 04-25-2018 10:03
    Be careful with the performance impact Robert mentioned - that's something that may not come out in testing, but it could have a big impact for users with tons of data or slower computers (AKA your frequent callers to the help desk).

    As a case study, our file selection is unlocked, and I would say 95% of users do not change it.  You may want to add it to your monitoring on the other end.  So for example, monitor for users with 100% completion but very small archive size (:users has been removed from the backup set).  There will be some other problem cases you'll find that you can monitor for as well.  Professors can always find new and inventive ways to break things.

    ------------------------------
    Brad Hodges
    Baylor University
    ------------------------------