LMS 2.6 - 3.0.1 migration fails

vergeerf · ‎06-30-2008

I have a problem to perform a remote restore of a LMS 2.6 backup into a clean LMS 3.0.1. I used the wrapper.pl to prepare the backup and copied it to the remote machine. The RME restore stops at 30% (see below). The log files don't show any failure.

doRestore of [Common Services] has completed.

doRestore of [Resource Manager Essentials] has started.

10% of RME Restore completed

30% of RME Restore completed

ERROR: doRestore of [Resource Manager Essentials] had some errors.

Check the log file for details

Restore failed. Previous system data may be lost due to failed restore. To avoid

this, perform a successful restore.

---

The wrapper however complains 'bout a missing rbackup.exe (which is in place)

===

processed file: d:\software\migrate\backup\0\rmeng\fcss\datafiles.txt

processed file: d:\software\migrate\backup\0\rmeng\misc\datafiles.txt

processed file: d:\software\migrate\backup\0\rmeng\sla\datafiles.txt

processed file: d:\software\migrate\backup\0\rmeng\slc\datafiles.txt

Backup completed: at [Mon Jun 30 15:46:15 2008]

************************************************************

Return status of CS backup script is: 0

Backing up CiscoView data now

6 File(s) copied

Backing up CiscoView done

IPM backup starts now

Exiting the backup process.

Reason: rbackup.exe is not available

C:\Program Files\CSCOpx\bin>

Joe Clarke · ‎06-30-2008

You need to post the migration.log.

vergeerf · ‎07-01-2008

There was no migration.log generated :-(

I've uploaded the restorebackup.log =

I don't know if this is related to the issue, but I checked the LMS 2.6 system by running the selftest, it says: the database.pl

WARN No Data Source Found, No Database Self Test is performed. Maybe the backup (created by using wrapper.pl) was not ok or the RME database is corrupt, the system however seems to work fine.

Joe Clarke · ‎07-02-2008

There does appear to be an RME database problem. Since it sounds like the 2.6 server is still up, try taking another wrapper.pl backup. Post the resulting log file.

vergeerf · ‎07-04-2008

since we didn't want to lose more time on troubleshooting this, we've decided to only export the DCR and start a new (RME) database on the CWLMS 3.0.1 server, thanks for your help anyway ;-)