Documentation
Installation, activation, database discovery, backup operations, verification and troubleshooting guidance.
Open documentationSupport
Clear guidance for installation, operations and recovery readiness.
Use the documentation for routine administration, contact product support for platform issues, or involve Mind Merge Data Recovery Services when an incident requires specialist recovery work.
Choose a path
Start with the support route that matches the situation.
Routine questions should begin with documentation. Operational faults should include evidence. Recovery incidents should prioritize preservation of the original data.
Product support
Help with agent connectivity, service startup, backup failures, configuration questions and support escalation.
Contact product supportEmergency recovery assistance
Specialist assistance for failed storage, damaged databases, ransomware incidents and urgent recovery cases through Mind Merge Data Recovery Services.
Visit Mind MergePrepare the case
Useful evidence helps support distinguish configuration faults from recovery incidents.
Do not include passwords, private keys, encryption keys or customer data in an initial support message.
- 1
Record the device name, affected database and approximate failure time.
- 2
Preserve the original error message and relevant agent or SQL Server logs.
- 3
Avoid deleting backup files, reinstalling the agent or repeatedly changing permissions before review.
- 4
For suspected storage damage or ransomware, stop unnecessary writes and isolate affected systems where operationally safe.
Escalation
Emergency recovery assistanceSuspect physical failure, corruption or ransomware?
Normal software troubleshooting may increase risk when the source storage is unstable. Preserve evidence, avoid unnecessary writes and request a recovery assessment through Mind Merge Data Recovery Services.