I'm struggling with Content Deployment tool on SP 2010 in these days, because it is the only way, how to repair our permission issue, however, it brings a lot of another small headaches with it even none of known issues stopped us. I know, CD deploys things that are stored in the Content db only, so we need scripts for recycle bin, alerts, master pages, versions (the most ilogical thing, because export can handle it itself with the right parameter) and we finally solved most of those things by scripts, but I cannot believe, why is sooo slooow.
There is no CPU, disks, memory or network or DB issues, it is inside one mid-size farm, deployed from one SC to another with a lot of disk space on app. server, but it seems that the job stops from time to time. Even results based on the some content are different, at the end of the day. SC with 420 000 objects ran for 4 hours, SC with 280 000 objects running for almost 6 hours right now and it is hardly in the middle (4000 objects in 30 minutes, in average). I read a lot of articles between the jobs and some of them writes about tricks with search, indexing or timer services, but nothing brings any clear solution. We have big problems to make one SC in three days (friday and weekend, there is no free time-window because of worldiwide offices), but yes, it finaly solves our issue...
I have listed many things in this question what we tried. Something is missing? Thank you for ANY clue, I'm desperate.
P.S. also if you have any idea how to move in-progress workflows (also via script, tool or something else) or workflow history, I would be grateful too. It is the only thing, that we cannot resolve now.