Migrating objects 1

[hanchilicious]

Hi,

I installed XI on a remote server and wanted to replicate the reports, instances and schedules from my local server.

So, I copied the Filestore directory, containing the Input, Output, and Temp dirs from the source server, and overwrote the target Filestore dir.

But the reports do not show up on the new installation.

Am I missing something? Is there a better way to migrate all this detail to a remote machine?

Thanks

 

[hanchilicious]

Sorry, I should mention, both machines have the same version of BOE. It's not an upgrade.

 

[gortuk]

Copying the Filestore directory won't do anything. What you need to use is the "Import Wizard" tool installed with BOE to migrate your objects from one CMS to the other. There should be some documentation on this tool on the BO site if you need it.

You should delete the Filestore information on your target system before you do this as those files won't be used in your migrated system.

 

[hanchilicious]

Hi gortuk,

Thanks for your response.

I did try with the import wizard, using \\ip_address\cms_name to identify the source box, but it never seemed to be able to see the machine, which is why I resorted to copying the filestore.

Is the way I was trying in the import wizard not the right way to point to a remote server?

 

[gortuk]

Try just using the CMS name - no need to enter the IP address. The documentation on the BO site for this tool should be of assistance here.

 

[hanchilicious]

You can't just enter the CMS without identifying the machine if it's on a remote server.

 

[gortuk]

By default the CMS name should be the same as the first server you installed it on; I've never had to specify an IP address with this setup. If you changed your CMS name and it's not finding it, try this:

http://technicalsupport.businessobj...iceId=&dialogID=11680270&stateId=1 0 11678399

 

[hanchilicious]

High five for you, Gortuk.

I managed to reference the server this way:

servername\cms_name
or
ip.address\cms_name

by dropping the first couple of \\ in my first example.

But updating the hosts file suggestion in your link is also a great idea, which I never thought of.

Cheers.

 

[jedownsjr]

We have done a similar thing in our Disaster Recovery planning, replicating our production system on another server. We accomplished this by doing a backup/restore of the filestore (input & output) plus the CMS database (SQL Server for our installation). Using the Import Wizard is probably still the best way if it is possible for you.