We have a large site collection that we are doing an stsadm -o export on. The STSADM.exe command is running in a CMD shell, and when the output gets to approx 19GB (closer to 19.5GB) to the Temp directory, the CPU usage drops to 0. Memory usage for the CMD is still around 156,xxx kb. After approx 2 hours, we don't notice a difference and stop the process. We do the same command on other smaller site collections without any problems. Any ideas? Is there an upper limit we're currently pushing? Would setting the cabsize differently make it go faster? Thank you.

For something like you are trying to do -- STSADM -o backup is a much better approach especially if you are trying to get the whole site collection. John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007