Recovery Pending
When a Nodinite database enters the Recovery Pending state, it signals a critical issue that can disrupt your business operations. This guide empowers you to quickly restore service continuity and minimize downtime.
Tip
✅ Step-by-step instructions for safe database recovery
✅ Minimize data loss and restore Nodinite services fast
✅ Best practices for SQL Server troubleshooting
✅ Direct links to support and further resources
Important
- If you are reading this, something really bad has happened to one or more databases. Please contact our support for further technical assistance.
- Always ensure you have a recent SQL backup and sysadmin privileges before executing any recovery commands. Proceed with caution to avoid potential data loss.
Troubleshooting
1. Stop all Nodinite related services
First, stop all Nodinite related services to prevent further issues:
- Logging Service
- Monitoring Service
- App Pools (the name depends on your installation). Review the IIS Authentication settings user guide for additional information
App Pools for Nodinite services in IIS - Monitoring Agents (if any are installed)
- Pickup Log Events Service Logging Agent (if installed)
2. Recover the database
To recover the affected database, run the following SQL script. Replace [NodiniteConfig_Test] with your actual database name:
ALTER DATABASE [NodiniteConfig_Test] SET EMERGENCY;
GO
ALTER DATABASE [NodiniteConfig_Test] SET SINGLE_USER;
GO
DBCC CHECKDB ([NodiniteConfig_Test], REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS;
GO
ALTER DATABASE [NodiniteConfig_Test] SET MULTI_USER;
GO
Note
The
REPAIR_ALLOW_DATA_LOSSoption may result in some data loss. Always restore from backup if possible.
3. Restart Nodinite services
Restart all Nodinite services in the following order:
- App Pools (see IIS Authentication settings for details)
- Monitoring Service
- Logging Service
- Monitoring Agents and any other services you stopped earlier