Command line export archive
Created: 26 Aug 2010 | Updated: 05 Jul 2011 | 8 comments
Status:
In Review
It should be possible to export an archive via a command line (or Powershell commandlet) so that administrators can script it.
Idea Filed Under:
Comments 8 Comments • Jump to latest comment
Bump. Totally agree. Managment of this product is a bit rediculous.
Thanks Aaron. Are there specific other areas? We could create additional "ideas" in this area of the forum for those.
Many Thanks,
Rob
www.quadrotech-it.com - All your EV Tools
PS I hope that the post proves helpful.
Importing PST files and Exporting Archives are the primary task that needs to be done in bulk.... so Powershell would be very useful there....Other than that things are easy in the GUI.
I have a list of about 200 archives that need to be removed completly from the system; it would be nice if I could just pipe those names into PS and have them exported somewhere and then deleted...
Good ideas Aaron
Many Thanks,
Rob
www.quadrotech-it.com - All your EV Tools
PS I hope that the post proves helpful.
Hi,
Would you want to export just for Exchange or would the other archive types be of interest?
If others are of interest what priority would you assign and what would the use case be? If FSA and SharePoint are of interest, what would the export container be? .zip or just a new folder?
Thoughts?
--Andy
I only use EV for Exchange so I can't really comment on the other bits. I think you should be able to use a powershell command line to do anything you can do in the GUI wizard for import/export.
We could use a powershell to export our mailboxes, would make our live easier
Could you add some error-checking for bad savesets, or create another process to find them before attempting the export?
I'm attempting to do some exports, but it keeps failing.
I've opened a ticket with support, and they stated that the only way to find the bad savesets is to keep attempting exports.
But then I keep accumulating copies of the objects that are successfully exported.
Example:
First pass: I export 7,000 of 200,000 objects, then it fails and i fix that bad object/saveset @ 7,001.
Second pass: I export 14,000 of the 200,000, then it fails and I fix that bad object/saveset @ 14,001.
Third pass: I export 21,000 of the 200,000, then it fails and I fix that bad object/saveset @ 21,001.
Now, I have three copies of the first 7000 objects and two copies of the second 7000 objects...
This will keep happening and increasing in copies of messsages, as I attempt to export the whole 200,000 objects.
This is insane.
Any suggestions?
Troy
Would you like to reply?
Login or Register to post your comment.