Importing on a VM on the target machine, which is primary controller of the same Domain as the VM on source PC

Jun 4, 2009 at 2:24 PM

 

I have two actual PCs - let's call them DevPC and TargetPC.

Apart from one exception, each PC has the same VM on it (using VirtualPC), which defines the same domain ("LITWARE"), and is primary domain controller of it.

The exception is that I've added a web application and a site to the TargetPC on port 1800, and just a web application (port 8100) on TargetPC.  I'm not sure if the port numbers have to match.

When I try to import, I set the URLs as

Site URL = http://DevPC:8100

Import URL http://TargetPC:1800/mysite

 

I get two errors saying: "Wrong URL"; and a longer error message about not having the permissions to run the command (use "run as .." etc).  I am logged in as Administrator on both VMs, so I'm not sure it the second error is caused by the first.

We're guessing that both VMs on the two machines think that they are the primary domain controller of LITWARE domain, but obviously "there can be only one".

We could try making the DevPC VM a secondary domain controller and use only the TargetPC as primary domain controller, but we're probably not allowed to, and I'm not sure if that would help.

What's wrong with the URL? Are the ports included in the URL?

I'm quite new to stsadm exports and backups, so I also have more general questions :

Am I right in thinking that the CMP file depends on the DevPC ("Site URL") as a source of up to date content?  

Is the difference between an exported CMP file and a backup .dat file (as created by stsadm -o backup) really that the backup includes ALL of the content, and none of the physical files

Aside from the contentdb, do exports and backups both include all the same information about the site structure?

 

Jun 11, 2009 at 10:05 PM

Graham,

Sorry for the delay - I missed your question first time round, just caught it cleaning up my inbox just now.

First off, there is no dependency on the domain when exporting/importing content - so you won't have to change anything there. Your problem simply seems to be that you've misinterpreted what the 'Site URL' and 'Import web URL' values expect. Here's a summary:

Export:

Site URL - enter the site collection URL you wish to export from
Import Web URL - [will be disabled]

Import:

Site URL - enter the site collection URL you wish to import to
Import Web URL - if you do not wish to import to the root, specify the URL of the web to import to (known as "re-parenting"). So if you wish to import to say http://TargetPC:1800/mysite/child1, you'd need to specify this because otherwise the content would end up in http://TargetPC:1800/mysite if you left it blank. Leaving it blank is what'd you'd do normally though, i.e. when not re-parenting content to a child web.

So it isn't the case that the 'Site URL' refers to your "source" site but the 'Import Web URL' refers your "target" site as I think you imagined.

Other notes:

  • No need to specify ports in the URL
  • A .cmp file is a "snapshot export" of the site data at that time - it is different to backup because it's designed to be imported to another environment, and as such doesn't contain some things like the SharePoint change log/audit trail etc.
  • Otherwise yes, a .cmp file does contain mostly similar data to what's in an STSADM backup file

HTH,

Chris.