Share via

Crashed 2TB SSD M.2 disk memory after created backup (.bak) file by SSMS.

Patryk Parzoch 1 Reputation point
2021-10-15T21:20:51.27+00:00

Hi!

I have PNY 2TB M.2 PCIe Gen4 NVMe XLR8 CS3040 Heatsink disk. When I run creating .bak file by SSMS (SQL Server Management Studio) direct to M.2 disk. After created .bak file, my memory of M.2 has been corrupted (some files has been lost and installed OS has been corrupted on that disk).
Someone has similar problems with this?

Best regards, Patrick.

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories


2 answers

Sort by: Most helpful
  1. Seeya Xi-MSFT 16,756 Reputation points
    2021-10-18T06:02:51.883+00:00

    Hi @Patryk Parzoch ,

    Agree with Erland. > SQL Server does not corrupt the disk, but writing large amount of data, can put a little stress on the disk.
    If you don't get an error message during the backup process, you should not blame SQL Server for the problem.

    Best regards,
    Seeya


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments No comments

  2. Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator
    2021-10-15T21:53:14.87+00:00

    Sounds like you disk is faulty and you need to replace it. SQL Server does not corrupt the disk, but writing large amount of data, can put a little stress on the disk.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.