Need to restore database - will layout/channels just come back?

Hello, everyone! ☺ There is a script in /usr/luminis/bin called addnewbookmark. Has anyone ever used it?

I ran it in our development environment (without fully knowing the implications). NOT a good idea.

This script dropped, created and indexed all of the tables in the luminis database. We lost our fragments (tabs, etc), channel definitions, on and on. I had mistakenly thought (assumed)  it was a convenience script for adding a default bookmark in the bookmarks plus channel. As for the database, we have daily backups -- and our DBA will recreate the database from yesterday's on Monday

Some questions:

  • Does anyone know the extent of the work that needs to get done to restore our development portal the way it was ? For example, will we need to recreate our channels in the Content Manager again or will Luminis pick these up when we restart the system with the backup?
  • We have our Targeted Content channels all defined in /usr/luminis/shared/content ... will we need to recreate those too?  Luckily we can copy/paste these, but we'd have to redefine the audiences?

Thanks, Carol

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Hello, all. Has anyone ever

Hello, all.
Has anyone ever restored their luminis database to a previous version?
If so, does the layout, channels (all types) etc get restored without further work? Would the channels, audiences, etc need to be redefined?
Does anything special have to be done (except a restart)?

Thanks
Carol
SHU, NJ

restoring db from backup

If you restore your DB from backup, everything should be back to normal.

The only way that things would get out of sync, is if prior to the db restore, you were working in the portal recreating layouts/channels/etc... In that case, the new ldap entires for channels would not match up with some of the information contained the older restored db.

Luminis has so many interdependent parts, that virtualization and the ability to "snapshot" an entire working system, makes working with it a ton easier.

DB restore should work

After a similar accident with $CP_ROOT/bin/addcpipwebproxy, we recovered fully by shutting down all components, restoring the DB from the previous night's backup, and restarting.

I wonder what the purpose of those scripts are.

Syndicate content