Video Screencast Help
Search Video Help Close Back
to help

PST Centralization & Collection Issues

Created: 19 Apr 2012 | 4 comments
AKL's picture
0 0 Votes
Login to vote

Hello All

Just in middle of business day at work so kind off exhausted. We're running effort to centralize PST files in environment into Enterprise vault (9.0.1.1073)

The PST locator task has been running fine - it went out and found over 12TB files so far and still running. We started through pilot phase as well. We're relying on Server driven migration as our primary way of centralization.

The collector task is configured to run in off business hours. We've sent out note to concerned persons to leave their workstations online while this centralization effort completes. However we do not see Collector task copying lot of files. The holding folder has limit of 40GB (whch I increased to 200GB today) and we observed that Migrator task is able to process about 35GB in 2 hours.

The majority of error that I see in collector task log is:

Could not copy PST file: \\Client01\C$\Documents and Settings\dduck\Local Settings\Application Data\Microsoft\Outlook\Archive.pst : Could not access PST to set it to be read-only. Check that the PST Collector task's log on account has write access to the PST. **

Migration Status of PST: \\Client01\C$\Documents and Settings\dduck\Local Settings\Application Data\Microsoft\Outlook\Archive.pst has been reset to: Ready to Copy

The failure text in SQL PST File table says:

Could not copy PST file: \\Client01\C$\Documents and Settings\dduck\Local Settings\Application Data\Microsoft\Outlook\Archive.pst : Could not access PST to set it to be read-only. Check that the PST Collector task's log on account has write access to the PST.
 

The account I am running collector task under is an Domain administrator and we've Domain admins have full admin access to all workstations in environmment.

I am planning to run DTrace through tonight to see if it logs any additional details around it but anyone having ideas on above that could point in right direction?

Do we expect same log lines if workstation is offline? (content of error kind of indicates permission issue but just confirming if same error will come if workstation is offline)

Thanks in advance !

Comments 4 CommentsJump to latest comment

TonySterling's picture

Are your users actually closing Outlook?

Tony Sterling
www.bluesource.net or www.bluesource.co.uk
Offices in the US and the UK

0
Login to vote
  • Actions
AKL's picture

I believe they confirmed that Outlook client was closed but I'll surely ask them to re-confirm.

Thank You

AKL

0
Login to vote
  • Actions
AndrewB's picture

AKL - if you're seeing this a lot then it might make sense to identify all the users with this error and enable them for client-side migration.

 

just out of curiosity since i havent seen this before first hand but *shouldnt* it say that the file is "in use" as opposed to "read only" ?

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

0
Login to vote
  • Actions
AKL's picture

Since PST collector task tries to enable read only attribute on file before starting the copying, that's reason we see "Could not access PST to set it to be read-only" - i.e it was not able to enable read-only on the file in focus.

And I just posted client migration thing as well in different post as that's a different issue:

https://www-secure.symantec.com/connect/forums/pst-centralization-server-driven-client-driven-together

Thank You

AKL

0
Login to vote
  • Actions