Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Moving or migrating Deep Security or Vulnerability Protection database files (.mdf and .ldf) to another drive

    • Updated:
    • 4 Feb 2019
    • Product/Version:
    • Deep Security 10.0
    • Deep Security 10.1
    • Deep Security 10.2
    • Deep Security 10.3
    • Deep Security 11.0
    • Deep Security 11.1
    • Deep Security 11.2
    • Deep Security 11.3
    • Vulnerability Protection 2.0
    • Platform:
    • N/A N/A
Summary

Learn how to migrate a database file to another drive, which can be helpful during these scenarios:

  • Moving a file to another disk with larger capacity
  • Default drive has ran out of space
  • Database disk capacity can no longer be increased

This procedure only applies to Deep Security Manager (DSM) or Vulnerability Protection Manager (VPM) that uses Microsoft SQL as their database.

Details
Public
 
It is impossible to move the .ldf file only and leave the .mdf file on its original location, and vice-versa. Both .mdf and .ldf files must be on the same location (e.g. F:\databases\) when you re-attach it to the SQL instance.
In case you're not familiar with Microsoft SQL navigation, you may consult your database administrator.

To move a database file:

  1. Stop the Deep Security Manager service or Vulnerability Protection Manager service.
  2. Log in to SQL Server in the SQL Studio and then back up the database.
  3. Right-click the DSM or VPM database and click Task, then click Detach.

    Detach database

  4. Tick the Drop Connection checkbox and click OK.

    Drop connection

  5. On the SQL Studio, confirm that the database name is no longer existing in the Database list.
  6. Move the .mdf and .ldf files to another drive (e.g. F:\Databases\).
  7. On the SQL Studio, right-click the Databases and click Attach.

    Attach database

  8. Under Databases to attach, click Add.

    Add database

  9. Browse for the Database file (.mdf) from its new location (e.g. F:\Databases\) and click OK.

    Browse for the database file

  10. Verify the database details and location and click OK.

    Verify the database details

  11. On the SQL Studio, make sure the database name is back in the Database list.
  12. Start the Deep Security Manager service or Vulnerability Protection Manager service.
  13. Confirm that you can open the Deep Security Manager service or Vulnerability Protection Manager console.
Premium
Internal
Rating:
Category:
Migrate
Solution Id:
1122038
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.