Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
  3. Troubleshooting
  4. The VM takes long time for booting after BMR Physical backup conversion to virtual machine is performed on 32-bit architecture Windows OS
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

The VM takes long time for booting after BMR Physical backup conversion to virtual machine is performed on 32-bit architecture Windows OS

During VM boot up time, post-login, Windows pops up New Hardware Found and Configuration window. It prompts to configure device driver for SAS Controller - Base System Device. This windows dialog gives two options for new device configuration, which are, Auto search and configure and Skip prompting for these devices. If you select any one of these options then Windows makes error in SAS controller VMWare PVSCI device driver configuration. Due to this problem next boot may result in BSOD.

Do not take any action for the New hardware configuration dialog. Close this dialog window by using the Window cross button. You can ignore this dialog. This process may need to be done every time during VM boot up.

Feedback

Was this page helpful?
Previous

Verify backup failure while recovering Windows client

Next

BMR-enabled physical backup to Virtual Machine conversion job fails on Windows platform

Feedback

Was this page helpful?