Dear Sequoia team, please look at the next problem of recovering from MS SQL Server failure(stopping win service).
LOG of controller at 192.168.0.2: Started collocated controller at 192.168.0.3. Then started the same one at 192.168.0.2 14:20:15,890 INFO controller.core.Controller Sequoia controller (3.0-beta2) 14:20:16,234 INFO controller.core.Controller Loading configuration file: xml\pcController.xml 14:20:16,468 INFO controller.core.Controller JMX is enabled 14:20:16,562 INFO controller.core.Controller Starting JMX server on host: 192.168.0.2:1090 14:20:17,468 INFO controller.backup.BackupManager Registering backuper MSSQLServer to handle format MSSQL raw dump 14:20:17,531 INFO backend.DatabaseBackend.mainPCDB Adding connection manager for virtual user "sa" 14:20:18,593 INFO sequoia.controller.recoverylog Creating recovery log table: RECOVERY 14:20:18,750 INFO sequoia.controller.recoverylog Creating checkpoint table: CHECKPOINT 14:20:18,765 INFO sequoia.controller.recoverylog Creating backend table: BACKEND 14:20:18,765 INFO sequoia.controller.recoverylog Creating dump table: DUMP 14:20:18,875 INFO controller.RequestManager.VirtualDatabase Request manager will parse requests with the following granularity: TABLE 14:20:18,906 INFO controller.virtualdatabase.VirtualDatabase Using Hedera properties file: /hedera_appia.properties 14:20:19,328 INFO appia.xml.AppiaXML Loading XML configuration from file: C:\sequoia\config\my_appia.xml 14:20:19,968 INFO continuent.hedera.appia AppiaThread: Starting Appia. 14:20:22,218 INFO controller.virtualdatabase.VirtualDatabase Group VirtualDatabase connected to Member(address=/192.168.0.2:2519, uid= 192.168.0.2:2519) 14:20:22,218 INFO controller.virtualdatabase.VirtualDatabase Group now contains 2 controllers. 14:20:22,218 INFO controller.virtualdatabase.VirtualDatabase Checking virtual database configuration with remote controllers. 14:20:22,546 INFO controller.virtualdatabase.VirtualDatabase Updating backend list for controller Member(address=/192.168.0.3:1175, uid= 192.168.0.3:1175) 14:20:22,578 WARN controller.virtualdatabase.VirtualDatabase Some virtual database users are missing from this configuration, trying to create them transparently... 14:20:22,578 INFO controller.virtualdatabase.VirtualDatabase Virtual database configuration is compatible with other controllers. 14:20:22,578 INFO controller.virtualdatabase.VirtualDatabase Controller identifier is set to: 1 14:20:22,593 INFO controller.virtualdatabase.VirtualDatabase Resyncing recovery log ... 14:20:22,609 INFO controller.virtualdatabase.VirtualDatabase No shutdown checkpoint found in recovery log. Clearing recovery log (dirty). 14:20:22,609 INFO controller.virtualdatabase.VirtualDatabase Please resync manually using 'recover log'. 14:20:22,609 INFO controller.virtualdatabase.VirtualDatabase Resyncing recovery log done 14:20:22,625 WARN controller.virtualdatabase.VirtualDatabase Cannot enable backend mainPCDB from a known state. Resynchronize this backend by restoring a dump. 14:20:22,625 INFO controller.core.Controller Adding VirtualDatabase VirtualDatabase 14:20:22,656 INFO controller.core.Controller Waiting for connections on 0.0.0.0:25322 14:20:22,656 INFO controller.core.Controller Controller started on 2007.01.31 05 at 02:20:22 PM EET 14:20:22,656 INFO controller.core.Controller Controller mainPCController ready, listening to requests ... VirtualDatabase(admin) > backup mainPCDB init_dump MSSQLServer \tmp 14:20:41,812 INFO controller.RequestManager.VirtualDatabase Starting backup of backend mainPCDB 14:20:46,828 INFO controller.RequestManager.VirtualDatabase Backup has completed. 14:20:47,062 INFO backend.DatabaseBackend.mainPCDB Detected backend as: Microsoft SQL Server 14:21:09,421 INFO controller.RequestManager.VirtualDatabase Setting new virtual database schema. 14:21:09,484 INFO controller.recoverylog.RecoverThread Starting recovery 14:21:09,656 INFO controller.RequestManager.VirtualDatabase All activity is suspended for VirtualDatabase 14:21:09,671 INFO controller.recoverylog.RecoverThread Recovery completed VirtualDatabase(admin) > enable mainPCDB 14:21:18,765 INFO controller.recoverylog.RecoverThread Database backend mainPCDB is now enabled VirtualDatabase(admin) > backup mainPCDB first_dump MSSQLServer \tmp 14:21:30,656 INFO controller.RequestManager.VirtualDatabase All activity is suspended for VirtualDatabase 14:21:30,671 INFO controller.virtualdatabase.VirtualDatabase Checkpoint now-mainPCController-20070131142130625+0200 was stored 14:21:30,671 WARN controller.virtualdatabase.VirtualDatabase No information has been found for remote controller Member(address=/192.168.0.2:2519, uid= 192.168.0.2:2519) 14:25:04,000 INFO controller.RequestManager.VirtualDatabase All activity is suspended for VirtualDatabase 14:25:04,015 INFO controller.virtualdatabase.VirtualDatabase Checkpoint backup first_dump-mainPCController-20070131142503953+0200 was stored 14:25:04,015 INFO controller.virtualdatabase.VirtualDatabase Disabling backend mainPCDB, waiting for current transaction to complete on this backend 14:25:04,031 INFO controller.RequestManager.VirtualDatabase Setting new virtual database schema. 14:25:04,046 INFO sequoia.controller.connection 5 connections freed on "jdbc:jtds:sqlserver://192.168.0.2/VirtualDatabase" 14:25:04,265 INFO controller.virtualdatabase.VirtualDatabase Backend mainPCDB is now disabled 14:25:04,265 WARN controller.virtualdatabase.VirtualDatabase Updating backend list with unknown backend mainPCDB disabled on controller Member(address=/192.168.0.2:2519, uid=192.168.0.2:2519) 14:25:04,312 INFO controller.RequestManager.VirtualDatabase Backend mainPCDB is now disabled 14:25:04,312 INFO controller.RequestManager.VirtualDatabase Starting backup of backend mainPCDB 14:25:06,500 INFO controller.RequestManager.VirtualDatabase Backup has completed. "create_table" from console was executed successfully VirtualDatabase(admin) > restore backend mainPCDB first_dump 14:25:06,640 INFO controller.recoverylog.RecoverThread Starting recovery 14:25:06,843 INFO controller.RequestManager.VirtualDatabase All activity is suspended for VirtualDatabase 14:25:06,843 INFO controller.recoverylog.RecoverThread Recovery completed 14:25:06,890 INFO controller.recoverylog.RecoverThread Database backend mainPCDB is now enabled 14:30:13,515 ERROR sequoia.controller.connection Backend mainPCDB is no more accessible. 14:30:13,546 INFO controller.RequestManager.VirtualDatabase Setting new virtual database schema. 14:33:51,140 INFO controller.RequestManager.VirtualDatabase Recovery of backend mainPCDB done. VirtualDatabase(admin) > enable mainPCDB Enabling backend mainPCDB from its last known checkpoint Hanging......... 14:34:41,187 ERROR backend.DatabaseBackend.mainPCDB Unable to get a connection to gather database schema. 14:34:41,187 WARN backend.DatabaseBackend.mainPCDB Unable to gather schema from database meta data: java.sql.SQLException: Failed to get information about database schema: java.sql.SQLException: Unable to get a connection to gather database schem 14:34:41,187 ERROR backend.DatabaseBackend.mainPCDB Unable to get a connection to gather database schema. 14:34:41,203 WARN backend.DatabaseBackend.mainPCDB Unable to gather schema from database meta data: java.sql.SQLException: Failed to get information about database schema: java.sql.SQLException: Unable to get a connection to gather database schem 14:34:41,203 WARN controller.virtualdatabase.VirtualDatabase Backend mainPCDB has no defined schema. I've closed console and opened new one. VirtualDatabase(admin) > enable mainPCDB Enabling backend mainPCDB from its last known checkpoint Virtual database VirtualDatabase failed to enable database backend mainPCDB from checkpoint (because of : java.sql.SQLException: Invalid state of backend mainPCDB) Next restore is successful again. And enabling again repeats the same exceptions. -- Best regards, Denis Garyachy.
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
