Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Windows Server General Help » Shadow Copy Exclusions
Shadow Copy Exclusions [message #163878] Tue, 09 June 2009 13:30 Go to next message
paperhat  is currently offline paperhat
Messages: 10
Registered: June 2009
Junior Member
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\BackupRe store\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
MCP, MCDST
Re: Shadow Copy Exclusions [message #163893 is a reply to message #163878] Tue, 09 June 2009 17:42 Go to previous messageGo to next message
KevinJ.SBS  is currently offline KevinJ.SBS  United States
Messages: 653
Registered: July 2009
Senior Member
paperhat wrote:
> 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\BackupRe store\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


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\BackupRe store\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
Re: Shadow Copy Exclusions [message #163968 is a reply to message #163893] Wed, 10 June 2009 16:04 Go to previous messageGo to next message
paperhat  is currently offline paperhat
Messages: 10
Registered: June 2009
Junior Member
I already tried the F:\*.pst /s to no avail however i do intend to try the
$ALLVolumes$\*.pst /s.

--
Matt


"kj [SBS MVP]" wrote:

> paperhat wrote:
> > 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\BackupRe store\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
>
>
> 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\BackupRe store\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
>
>
>
Re: Shadow Copy Exclusions [message #163969 is a reply to message #163968] Wed, 10 June 2009 16:23 Go to previous messageGo to next message
KevinJ.SBS  is currently offline KevinJ.SBS  United States
Messages: 653
Registered: July 2009
Senior Member
paperhat wrote:
> I already tried the F:\*.pst /s to no avail however i do intend to
> try the $ALLVolumes$\*.pst /s.

Please report back if you are succesfull using that approach.


>
>
>> paperhat wrote:
>>> 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\BackupRe store\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
>>
>>
>> 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\BackupRe store\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

--
/kj
Re: Shadow Copy Exclusions [message #164258 is a reply to message #163969] Thu, 18 June 2009 16:13 Go to previous message
KevinJ.SBS  is currently offline KevinJ.SBS  United States
Messages: 653
Registered: July 2009
Senior Member
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.

paperhat wrote:
> 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 wrote:
>>> I already tried the F:\*.pst /s to no avail however i do intend to
>>> try the $ALLVolumes$\*.pst /s.
>>
>> Please report back if you are succesfull using that approach.
>>
>>
>>>
>>>
>>>> paperhat wrote:
>>>>> 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\BackupRe store\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
>>>>
>>>>
>>>> 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\BackupRe store\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
>>
>> --
>> /kj

--
/kj
Re: Shadow Copy Exclusions [message #164259 is a reply to message #163969] Thu, 18 June 2009 15:44 Go to previous message
paperhat  is currently offline paperhat
Messages: 10
Registered: June 2009
Junior Member
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
--



"kj [SBS MVP]" wrote:

> paperhat wrote:
> > I already tried the F:\*.pst /s to no avail however i do intend to
> > try the $ALLVolumes$\*.pst /s.
>
> Please report back if you are succesfull using that approach.
>
>
> >
> >
> >> paperhat wrote:
> >>> 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\BackupRe store\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
> >>
> >>
> >> 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\BackupRe store\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
>
> --
> /kj
>
>
>
Previous Topic:Seven and Win2003 sp2 AD
Next Topic:Re: how can I know my windows 2003 is activated by MSDN key or not?
Goto Forum:
  


Current Time: Tue Aug 22 03:18:16 EDT 2017

Total time taken to generate the page: 0.04913 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software