MindShield
LoginRequest demo
Request demo
Documentation / Getting started

Getting started

Prepare the Windows host, install the agent, activate the assigned license and confirm SQL Server access before creating backup policies.

System requirements

Use a supported 64-bit Windows workstation or server that can run the MindShield Agent as a Windows service. The host needs reliable outbound HTTPS connectivity to the configured MindShield API, sufficient local or approved backup storage, and access to the SQL Server instances selected for protection.

Before installation
  • Confirm the device is authorized for enrollment.
  • Obtain the correct license or activation information.
  • Identify SQL Server instance names and database owners.
  • Approve the service identity and required database permissions.

Agent installation

  1. Run the approved MindShield SQL Agent installer with administrative privileges.
  2. Review the installation location and the locked production API endpoint.
  3. Allow the installer to create and start the MindShieldAgent Windows service.
  4. Confirm the service startup type is Automatic and that the installation completes without an error.

Do not copy an installed agent directory between devices. Each device must be installed and registered through the approved workflow.

License activation and device registration

  1. Enter the license information supplied for the customer or organization.
  2. Submit activation while the host has outbound API connectivity.
  3. Confirm that registration creates the intended device record.
  4. Verify the device appears online in the authorized dashboard context.

Activation identifies entitlement; device registration identifies the protected host. Both stages must complete before normal policy delivery and monitoring.

SQL Server discovery

The installer or agent discovery workflow identifies locally available SQL Server instances and their databases. Review instance names carefully, especially where default and named instances coexist.

  • Confirm the expected SQL Server service is running.
  • Confirm network protocols and local connections are allowed as required by the environment.
  • Remove duplicate or stale selections before policy creation.
  • Do not assume discovery alone proves backup permission.

SQL Server permissions

The agent service identity or approved SQL credential must have only the permissions necessary to enumerate selected databases and perform the configured backup operation. Permission design should be reviewed by the database owner.

Security boundary

Do not grant broad server privileges merely to bypass a setup error. Record the failing operation, review the SQL Server error log and apply the minimum approved permission.

Database selection

  1. Review discovered instances and database names.
  2. Exclude system, test or retired databases unless they are intentionally protected.
  3. Confirm storage capacity and policy limits.
  4. Save the approved selection and verify that the dashboard reflects it.
Next guideConfigure backup operations →