|
![](/i/fill.gif) |
> Uhhh. Probably, yeah. I'm not sure if you're using Exchange why you'd be
> storing the definitive version of .pst files on the laptop. Why not store
> them on the exchange server?
Because we only get allocated a certain amount of space on Exchange, and
most people quickly go over that limit within a few months of emails.
Everyone I know that works here moves files off into local PSTs to be able
to keep emails longer than that (which is essential in this job). Some
people keep one huge PST (which I think is a bad idea) others like me have
several PST files for different areas of the job, and the big ones I usually
split up by year or even by quarter if there is a large volume of data.
> I'm glad. It's a bit of a bugger to track down vshadow.exe, but it sounds
> like you got it going. The /Z option to robocopy is handy too.
I got vshadow from the vss sdk which was a small free download from MS. So
far I've just been hacking about with the standard copy command to check
that vshadow works, will look into robocopy later, it's on my list of things
I know are possible but just need to be implemented now :-)
Post a reply to this message
|
![](/i/fill.gif) |