Re: Files to Recycle Bin

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Greg,

Thanks for posting here! Also thanks for Dave's input.

For your description, I understand that you want to recover some items in
My Documents folders. If I am off base, please don't hesitate to let me
know.

For you have enabled My Documents redirection, you can use Shadow Copies to
recover the deleted item in the My Documents. By default the Shadow Copies
is enabled, if you have not manually disabled it you can recover items from
Shadow Copies. I will give you a reference for Shadow Copies of Shared
Folders.

I. Shadow Copies of Shared Folders provides point-in-time copies of files
that are located on shared resources, such as a file server. With Shadow
Copies of Shared Folders, you can view shared files and folders as they
existed at points of time in the past. Accessing previous versions of your
files, or shadow copies, is useful because you can:

**Recover files that were accidentally deleted. If you accidentally delete
a file, you can open a previous version and copy it to a safe location.
**Recover from accidentally overwriting a file. If you accidentally
overwrite a file, you can recover a previous version of the file.
**Compare versions of file while working. You can use previous versions
when you want to check what has changed between two versions of a file.

You can access the server portion of Shadow Copies of Shared Folders
through the Shadow Copies tab of the Local Disk Properties dialog box. For
more information about how to use Shadow Copies of Shared Folders, see How
to.

The client software for Shadow Copies of Shared Folders is located on the
server and must be deployed to client computers. You can access the client
view of shadow copies through the Previous Versions tab of the Properties
dialog box of the shared file or folder.

*Notes:

A new button has been added to the Shadow Copies tab for Windows Server
2003 with Service Pack 1 (SP1). You can use the Revert button to revert an
entire volume back to an earlier point in time. Reverting the entire volume
will undo any changes that were made to files and folders on the volume
since the selected snapshot was taken. If you revert a volume, you cannot
undo the action later. You should not use Revert on volumes that contain
data stores like Active Directory or Exchange.

Physical access to a server is a high security risk. To maintain a more
secure environment, you must restrict physical access to all servers and
network hardware.

When you restore a file, the file permissions will not be changed.
Permissions will remain the same as they were before the restore. When you
recover a file that was accidently deleted, the file permissions will be
set to the default permissions for the directory.

When storage area limits are reached, the oldest shadow copy will be
deleted and cannot be retrieved.
There is a limit of 64 shadow copies per volume that can be stored. When
this limit is reached, the oldest shadow copy will be deleted and cannot be
retrieved.

Shadow copies are read-only. You cannot edit the contents of a shadow copy.
You can only enable Shadow Copies of Shared Folders on a per-volume basis;
that is, you cannot select specific shared folders and files on a volume to
be copied or not copied.

II. Best practices of Shadow Copies of Shared Folders

1. Select a separate volume on another disk as the storage area for shadow
copies.
Select a storage area on a volume that is not being shadow copied. Using a
separate volume on another disk provides two advantages. First, it
eliminates the possibility that high I/O load will cause shadow copies to
be deleted. Second, this configuration provides better performance. This is
the recommended configuration for heavily used file servers.

2. Consider how your clients will be using a shared resource before you
enable Shadow Copies of Shared Folders and set scheduling options.
Adjust the shadow copy schedule to fit the work patterns of your clients.
For more information about scheduling shadow copies, see Defining a
schedule for shadow copies.

3. Do not enable shadow copies on volumes that use mount points.
The mounted drive will not be included when shadow copies are taken. Enable
shadow copies only on volumes without mount points or when you do not want
the shared resources on the mounted volume to be shadow copied.

4. Do not enable shadow copies on dual-booting computers.
If you have enabled dual-booting into previous versions of Windows (such as
Windows NT 4.0), the shadow copies which persist while restarting the older
version might be corrupted and unusable when the computer is started again
with Windows Server 2003.
Use Backup to perform regular backups of your file server.
Shadow Copies of Shared Folders is not a replacement for performing regular
backups. Use a backup utility in coordination with Shadow Copies of Shared
Folders as your best preparation for restoring.

5. Do not schedule copies to occur more often than once per hour.
The default schedule is 7:00 A.M. and 12:00 noon, Monday through Friday. If
you decide that you need copies to be taken more often, verify that you
have allotted enough storage space and that you do not take copies so often
that server performance degrades. There is also an upper limit of 64 copies
per volume that can be stored before the oldest copy is deleted. If shadow
copies are taken too often, this limit might be reached very quickly, and
older copies could be lost at a rapid rate.

5. Before deleting a volume that is being shadow copied, delete the
scheduled task for creating shadow copies.
If the volume is deleted without deleting the shadow copy task, the
scheduled task will fail and an Event ID: 7001 error will be written to the
event log. Delete the task before deleting the volume to avoid filling the
event log with these errors.

6. Use an allocation unit size of 16 kilobytes (KB) or larger when
formatting a source volume on which Shadow Copies of Shared Folders will be
enabled.
If you plan to defragment the source volume on which Shadow Copies of
Shared Folders is enabled, it is recommended that you set the cluster
allocation unit size to be 16 KB or larger when you initially format the
source volume. If you do not, the number of changes caused by
defragmentation can cause previous versions of files to be deleted.

7. If you require NTFS file compression on the source volume, you cannot
use an allocation unit size larger than 4 KB. In this case, when you
defragment a volume that is very fragmented, you may lose older shadow
copies faster than expected.

Hope above information helps! if you have any further concern or question
on the issue please feel free to let me know. I am looking forward to your
reply!

Have a nice day!

Best Regards,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

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

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.

Quantcast