Shadow Copy Exclusions

Discussion in 'Windows Server' started by paperhat, Jun 9, 2009.

  1. paperhat

    paperhat Guest

    Hi,

    I am looking to deploy Shadow Copies of Shared folders on a Windows Server
    2003 SP1. During configuration i would like to exclude pst files from the
    shadow copy snapshot. After some research i read an article
    "http://msdn.microsoft.com/en-us/library/aa819132(VS.85).aspx" that
    instructed me to edit a registry setting

    "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot".
    The problem i have is that the above path does not exist within the registry.
    I have "HKLM\System\CurrentControlSet\Control\BackupRestore".
    I created the FilesNotToSnapshot manually and then created the REG_MULTI_SZ
    with the value of F:\*.pst
    This does not appear to work.

    Any help would be greatly appreciated.

    Matt
     
    paperhat, Jun 9, 2009
    #1
    1. Advertisements

  2. paperhat

    paperhat Guest

    I didn't know this. Unfortunately pst's are heavily used in this way in my
    environment.
    As these get backed up in the regular daily backups i would like to exclude
    these when enabling Shadow Copies for Shared Folders.
    The majority of data held on the file server is made up of pst's and that is
    why i would like to exclude these from the shadow copy snapshot
    The implementation of the Shadow Copies is basically to be used as an added
    feature for the end user to restore there own files and at the same time
    lowering the amount of restore requests for the backup/restore team.
     
    paperhat, Jun 9, 2009
    #2
    1. Advertisements

  3. OK - so now you know it's time to stop doing that. :)

    Personal folder files are unsupported over a LAN or over a WAN link
    http://support.microsoft.com/?id=297019

    Time to get Exchange. If you can't implement it in-house, get hosted
    Exchange. If you can't swing that, get Google Apps or Zimbra or something.
    But ban PST files and POP mail....they aren't suitable for a corporate
    network. Also see PST=BAD at
    http://www.exchangefaq.org/faq/Exchange-5.5/Why-PST-=-BAD-/q/Why-PST-=-BAD/qid/1209

    Yes, agreed - it's great. Just make sure you disable the Restore button or
    you will soon have a nightmare on your hands (someone will inevitably
    restore an entire folder from a snapshot, overwriting other users'
    subsequent changes).

    From an old post ...

    -----------------------------------------
    For the benefit of the group...

    I installed an updated version of twext.dll from
    http://support.microsoft.com/kb/903234 and now the registry tweaks all
    work. So... I must have previously had a different version of twext.dll
    when I had it working earlier.

    I will push out the hotfix listed at
    http://support.microsoft.com/kb/903234 which seems to add the ability
    to disable the restore button, or the whole tab, on clients.

    So the twext.dll was updated.
     
    Lanwench [MVP - Exchange], Jun 9, 2009
    #3
  4. paperhat

    paperhat Guest

    We already have Exchange 2003 but users are insistent in using psts for
    archiving mail as we do not have an archiving solution.
    Anyway i still don't have a solution to excluding psts from shadow copy
    snapshots so can anyone enlighten me?

    Thanks
     
    paperhat, Jun 9, 2009
    #4
  5. Sorry, but this is not a decision for end users to make. If your management
    understands that the company IT department cannot reasonably be expected to
    manage and support PST files (which you can't - they must be on the local
    hard drive) they may make a decision not to support them at all. If the data
    is important enough to keep, it's important enough to keep in managed
    storage. Otherwise, ditch it. Talk to your management; you're running with
    scissors here.
    I'm sure someone else will reply and again sorry for the thread hijack. You
    may want to repost a new message :)
     
    Lanwench [MVP - Exchange], Jun 9, 2009
    #5

  6. I've actually recommended every customer that I've had to get away from PSTs
    because of their cumbersome file structure, easily corruptable, only
    available at work and not through OWA or an ActiceSync handheld, or through
    Outlook Anywhere, and if you lose them and the PST is not recoverable, there
    goes all your emails.

    I've also tried searching on this to see how to exclude PSTs based on the
    original question, and all if not most of what I've found is folks speaking
    of having problems with PSTs and not real answer other than physically right
    clicking on the PST file and making sure it is not included for Shadow
    Copies.

    I do hope you can speak to the powers that be, and not the users, and
    explain the downside of using PSTs.

    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
    Microsoft Certified Trainer


    For urgent issues, you may want to contact Microsoft PSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    "Efficiency is doing things right; effectiveness is doing the right
    things." - Peter F. Drucker
    http://twitter.com/acefekay
     
    Ace Fekay [Microsoft Certified Trainer], Jun 9, 2009
    #6
  7. paperhat

    kj [SBS MVP] Guest


    Instead of; F:\*.pst

    use;

    F:\*.pst /s

    to apply to subs as well.

    References copied below.

    .....better yet get pst's off the network and discontinue their use in user
    outlook profiles.

    (echoing LW and Ace's advice)




    Files can be deleted from a shadow copy during shadow copy creation by using
    the following registry key:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot

    This registry key has REG_MULTI_SZ (multi string) values for each
    application whose files can be excluded. The files are specified by fully
    qualified paths, which can contain the * wildcard. If a fully qualified
    cannot be specified, then a path can also be implied by using the
    $UserProfile$ or $AllVolumes$ variable. For example:

    a.. UserProfile$\Directory\Subdirectory\FileName.*
    b.. $AllVolumes$\TemporaryFiles\*.*
    To make the path recursive, append " /s" to the end. For example:

    a.. $UserProfile$\Directory\Subdirectory\FileName.* /s
    b.. $AllVolumes$\TemporaryFiles\*.* /s
    In all cases, the entry is ignored if there are no files that match the path
    string. Note that the exclusion (or rather the deletion of the files from
    the Shadow Copy repository during creation by the shadow copy optimization
    writer) of the files been added to the appropriate registry key value, is on
    a best-effort basis.
     
    kj [SBS MVP], Jun 9, 2009
    #7
  8. paperhat

    paperhat Guest

    I already tried the F:\*.pst /s to no avail however i do intend to try the
    $ALLVolumes$\*.pst /s.
     
    paperhat, Jun 10, 2009
    #8
  9. paperhat

    kj [SBS MVP] Guest

    Please report back if you are succesfull using that approach.
     
    kj [SBS MVP], Jun 10, 2009
    #9
  10. paperhat

    paperhat Guest

    Hi,

    Just to confirm that i have now tested the following:

    $AllVolumes$\Groups\*.pst /s

    This has also failed.
    Any further assistance regarding this would be greatly appreciated

    Matt
     
    paperhat, Jun 18, 2009
    #10
  11. paperhat

    kj [SBS MVP] Guest

    Well's run dry regarding my ideas on this. Perhaps post some specifics
    (steps you are taking to configure) and results (validation of behavior not
    expected) and perhaps someone can reproduce. If it can repro it then maybe a
    bug report can be filed.
     
    kj [SBS MVP], Jun 18, 2009
    #11
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.