![server 2008 unknown disk not initialized server 2008 unknown disk not initialized](https://docs.microsoft.com/en-us/troubleshoot/windows-server/backup-and-storage/media/support-for-hard-disks-exceeding-2-tb/initialize-disk-window.png)
Welcome to not only Friday, but according to Lonny6654 who wrote today's community-created Spark article, it is also World Bee Day.
![server 2008 unknown disk not initialized server 2008 unknown disk not initialized](https://cdn.wethegeek.com/wp-content/uploads/2020/07/Screenshot-2020-07-07-at-5.16.10-PM-min.png)
#Server 2008 unknown disk not initialized archive
In effect, all BUE does is look at the attached LUN and create a snapshot and then copy the original VMDK file off the SAN to the backup archive on the Server (which in my case is on a Dell MD1000 DAS with 12 7200RPM 500GB HDDs with a read write speed over 200MB's sustained).
#Server 2008 unknown disk not initialized windows
You said in a perfect world, windows WOULD be able to read directly from VMFS, is this not the case? I simply dont understand why it should be slow to backup the VM, If I create a NTFS formatted lun on the SAN, I can benchmark it and hit 240MB/s over the two iSCSI links from the backup server. The iSCSI link in on a dual port intel 1GB nic and I use flow control and jumbo accross the board, its enabled on the servers and SAN and switches. I have only the SAN transport option in the VMware tab in BUE 2010R3 selected. Thanks for your help, that information is very useful in understanding the system.įirst off, Our Company is small and I am the only person with access to said server as I am the only IT guy here. Some folks have used that with ASM/VE to create a more consistent snapshot, mounted it to the Linux server and used the BUE agent to back up the entire volume. It allows you to 'see' all the VM's and their associated config/log files. There is such a capability in Linux, called "VMFS-TOOLS". So you could safely browse and backup / restore VMs or entire VMFS volumes.
![server 2008 unknown disk not initialized server 2008 unknown disk not initialized](https://www.diskpart.com/screenshot/en/others/windows-10/disk-unknown-not-initialized.png)
In a perfect world, Windows would be able to directly read VMFS volumes. If your switch supports both Jumbo Frames and Flowcontrol, then enabling Jumbo Frames might give you an incremental improvement in performance. Make sure that the agent/BUE are running through the SAN subnet, not being routed over the LAN or other non iSCSI subnet. He only lost one VM, so he was very lucky.
![server 2008 unknown disk not initialized server 2008 unknown disk not initialized](https://michaelfirsov.files.wordpress.com/2017/04/pre21.png)
I have worked with customers who ran for over 6 months with re-partitioned VMFS volumes. One problem is that ESX doesn't routinely re-read the partition table info. So access to that server should be strictly controlled.Īs long as they don't show up as NTFS formatted volumes you should be OK. With automount disabled it's slightly more difficult but still can occur. There's no protection at the SAN level for that kind of thing. The danger is that someone could come along and format those VMFS volumes with NTFS. The size comes from the SCSI read capacity operation which is automatically done when any volume/disk is connected to a server.