Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Moving Site Collections with STSADM

  Asked By: Sondra    Date: Jul 28    Category: Sharepoint    Views: 2424

I currently have a single-server farm and I need to upgrade to a more
robust environment. I've created a new farm on a new server with the
databases on a separate clustered SQL Server. I need to move my site
collections to the new server. Due to security restrictions, I don't
have file-level access to the new database server, so I'm using the
STSADM -export command with the intention of importing them into my new

Here's my problem: Even though the content database is only 18 GB and I
have over 230 GB of free space on the D: drive that I've designated for
the export file, I'm getting the following error when I run the export
"FatalError: There is not enough space on the disk."

My best guess is that STSADM is swapping data on the C: drive which only
has 7 GB free. Is this true? If so how can I keep it from doing this?
It's a serious limitation if I need to have that much room on the C:



4 Answers Found

Answer #1    Answered By: Breann Beach     Answered On: Jul 28

First, if you want to move  the entire site  collection, use stsadm  -o
backup instead. That will give you a fuller fidelity backup than -o
export will.

Second, yes, it's spooling to the C drive. I can't remember for sure
which location it uses, but I'd start with moving  the temp directories.
From the command  prompt type "SET" to see which variables are set and
where they are pointing. I don't know of an easier way to relocate
where it spools those, sorry.

Answer #2    Answered By: Timothy Hall     Answered On: Jul 28

If you want to move  entire site  collections then
the best command  to use is the stsadm  -o backup and restore. Now I
have a question for you.

While the process of backup and restore are time consuming, I am
wondering why you are not backing up and restoring the entire content
database. This would be a lot better and faster than any other option
and you will minimize the down time.

All you would have to do is perform a SQL backup in your current
environment then take that BAK file and place it in your new
environment then perform a SQL restore. Once this is restored you just
add that content  DB to your new web app. This is a simple task that
you or the SQL DBAs can perform.

Answer #3    Answered By: Ian Powell     Answered On: Jul 28

I agree that moving  the Content database  is the best way, but he said he
didn't have access  to the SQL server, so I didn't figure that was an

If it is, do that. And if this is MOSS run "stsadm -o preparetomove"
against the databases before you detach them. You'll be sorry if you

Answer #4    Answered By: Osvaldo Winters     Answered On: Jul 28

I did say I didn't have file access  to the SQL Server.
That's why I couldn't just move  the DB's. I may try to get around that
given the issues you've brought up. In case I can't, do you have any
idea which SET parameter is determining where STSADM is spooling?

Didn't find what you were looking for? Find more on Moving Site Collections with STSADM Or get search suggestion and latest updates.