Virtual disk / cliché Consolidation Questions

Similar Questions

• Consolidation of Virtual Machine disk is necessary question

  Today, I have one of my virtual downwards because the error message that says that "there is no more space for disk virtual xxxxx - 000018.vmdk.» you might be able to continue this session by freeing up disk space on the relevant volume by clicking on try again"

  I want to know why this happened if I make my virtual with 1.5 to and my server is new... so for the most part the server have 300 GB in use... I also had 750 GB available for an another virtual and that the question, why this virtual grow too much and too quickly?

  Also when this happened how can I do to solve this problem, how disk space if I did a single data store with al the available space.

  The suggestions will be welcome.

  Thanks for you comments.

  Concerning

  JP

  In the files you posted, it appears that 000002 and 000007 files are not in use by the virtual machine, but the others are. What I recommend you do is to open the Snapshot Manager, create a new snapshot and then run "Delete All". This should clean all the snapshots except for the two mentioned above. If this is the case, shut down the virtual computer and move the two snapshots listed in a subfolder (to be able to restore them in case I'm wrong), then power on the virtual machine again. If there is no error, you can delete the moved files.

  Unfortunately I can't see any rule, snapshots are used and that have been created just for adding hot backup not, so you should always have to understand this from scratch. At least for the moment until Acronis comes up with a fix, you need to delete snapshots manually on a daily basis since the Snapshot Manager (create a new cliché-> Delete All) to avoid any trouble with too many active snapshot on the virtual computer.

  You have another virtual computer that has NOT "changed block Tracking" on, to see if the problem is related to the CBT!

  André

• question about creating virtual disks on my MD3220i

  I create a virtual disk where I put a SQL Server and it asks me to

  Choose the type of virtual disk IO characteristics. The file system (typical), database, multimedia and Custom options.

  I think the selection of data because it is a SQL Server. However I'm not sure because I have not much of

  experience with this. My question is that one should choose or perhaps not even matter?

  Thank you

  Being that the VD will be strictly for SQL, then you can go ahead and select the database option. Any other time, you must select the typical option. Please let me know if you have any questions or concerns.

• Question about virtual disk

  I have a qustion about virtual disks

  I assigned 5 GB on a virtual disk. Then I realized that I need more space, so I changed to 20 GB.

  When I have energised the VM, it always complained not enough space. Even if I 'clearpart-set' in the startup script.
  I ended up remove the virtual disk and create a new one to solve the problem.

  "It seems that this partition table/information is always on the disc and kickstart' cleartpart all ' did not clean.

  How to solve the problem? instead of creating a new virtual disk?

  Thank you!

  curiousmind999

  I'll answer my own question

  If DD \u003d/dev/zero of = path/to/file bs = 512 count = 1

  to clear the boot on the VD partition

• PowerEdge R720 virtual disk question

  Hi, our company has bought a Dell PowerEdge R720. I tried to use the lifecycle controller in RAID configuration. At the start, it has 3 500 GB SAS HARD drive, but I ordered 2 x 320 GB additional SAS being what I intend to do it, use the 2 x 320 GB like OS install as RAID 1 and RAID 5 on the default 3 x 500 GB, but for some reason any, whenever I have configure RAID , either on the two 320 or 3 x 500 GB, it shows just a virtual disk, 2 x 320 GB or 500 GB x 3, I see not two for RAID 1 and RAID 5 virtual disks. Am I missing something here? or I have to perform an extra step?

  Kind regards

  Jeff

  Hello Jeff,.

  If you try to install the operating system through the lifecycle controller method. You must have the latest lifecycle controller OS driver pack installed in your system. For the latest driver pack OS, please download from our support http://support.dell.com/ site by entering you service number and download OS Driver pack drivers.

  You can update the OS driver pack thorugh iDRAC GUI or through the lifecycle controller GUI and once after the OS driver pack update. When you try to deploy the operating system through the life cycle of the controller, you will appear on the list of supported operating systems and you can select the operating system you want to install by mounting the image operating system or DVD media connected to the system.

  Please let me know if you have any question.

  Thanks, Neeraj

• Consolidation of many to one of the virtual disks?

  Hello world

  I use a XP client inside a Windows 7 host (using 8 workstations).

  In the configuration of my XP virtual machine I previously assigned (of 50 gigabytes) of disk space into separate virtual folders, about 2 GB each, as shown below.

  

  I now want to have a single vmdk file, with the pre-allocated 50 GB of capacity.

  Is it possible that I can achieve this goal, while keeping my VM in tact? For example can I create a second virtual disk, and then use a cloning tool (from the client) BONE to make a copy to the new virtual drive?

  Here, any help will be greatly appreciated.

  Kind regards

  DAVO

  Hello world

  This can indeed be done! Because I started with a scalable, split, virtual disk, there were several steps; Here's the gist of these measures-

  (1) using the vmware-vdiskmanager merge files into a single.

  http://hostilecoding.blogspot.com.au/2013/06/VMware-merge-multiple-VMDKs-into-single.html

  Note: when running this utility do not forget to include the '2' parameter, which refers to the creation of a virtual disk prealloue, otherwise the following steps (use the shrinkvd program will NOT work!).

  Here is a screenshot of the order that worked for me-

  

  (2) add the newly created virtual disk, 'merged.vmdk' to the existing virtual machine, using these installation instructions.

  https://www.VMware.com/support/WS5/doc/ws_disk_add_virtual.html

  (3) remove the existing virtual machine virtual drive

  (4) to start the Virtual Machine (you will probably be asked if you have moved or copied the VM, I responded with "Proposed").

  (Optionally)-rename the virtual disk of "merged" into something else by renaming the files in the ".vmx" and "hard" files.

  (5) using the shrinkvd resize the virtual disk

  http://www.Softpedia.com/get/system/system-miscellaneous/shrinkvd.shtml

  

  Above, note that the first time, I ran the command it failed with the message "ddb.deletable" is the crux of the problem. I just deleted this line in the relevant file "hard" and the command is represented.

  Now, when I boot on my virtual XP I use only 24 GB of space, and I am able to transfer the Virtual Machine to a smaller drive. in this case a 30 Gig old SSD.

  I hope this helps others.

  Kind regards

  DAVO

• Simple question - virtual disks telling apart for VDR

  Have a server that has a few virtual disks that are found on my lower speed discs in my SAN and some discs that are in my speed drives higher on my SAN.  So my VM has the following readers:

  HD1 - 25GB vmname/vmname - WS.vmdk

  HD2 - 20GB vmname/vmname - WS_1.vmdk

  HD3 - 15 GB vmname/vmname - WS_2.vmdk

  HD4 - 200 GB vmname/vmname - WS.vmdk

  HD1 and HD2 are the discs that I am interested in the backup.  HD3 and HD4 are just full of data that I have been saved by our main backup structure.  When I add a task to backup for this virtual computer in my data recovery console, it gives me the choice to save the following readers:

  vmname - WS.vmdk

  vmname - WS.vmdk

  vmname - WS_1.vmdk

  vmname - WS_2.vmdk

  One of these vmname - WS.vmdk is a 25 GB disc which I don't back up, the other is a 200 GB drive that I can't save...  How do I know which is which?

  Of course you can.

  1. mark the restore point corresponding to the removal during the next audit of integrity if you don't know that it is to be the wrong drive.

  2. go in configuration/targets and launch an integrity check manual on target for removing running next time.

  3. Once complete integrity check Remove the wrong drive for your backup job and put the right one in.

  But attention to the fact that fill only restore points can be selected for deletion, not a single hard drive out of it.

  Then you should start the backup job after reconfiguration immediately to have a new backup near time.

  And that's all.

• MD3000 cannot change virtual disk ownership / preffered path - ERROR 29

  Current configuration

  PowerVault MD3000 (deleted by the moderator) - attached to two servers PowerEdge R610 using Dell SAS 5/e card in each r610. The R610s act as a host ESX VMWare ESXi 5.5.0

  We have created multiple LUNS on the storage array and noticed that traffice all happening through a RAID controller or another module (and it seems to me not change without prompting when you look at the storage Bay). I turned off a two different virtual machines to try to change the path and had an error with a certain delay - I stuck this error below. I also tried to redistribute virtual disks tab the MDSM software nothing works support.

  By reading, it seems that the LUN should be attributed to a particular raid controller before all I / 0, but I still feel like're missing us something as to why we cannot distribute the traffic properly.

  According to some records for a MD3200 -.

  "If the host has a path of data unique to the MD, the virtual disk storage array.
  must be owned by the controller to which the host is connected.
  That's what we're trying to accomplish. I don't know if the hosts are to be physically detached from the SAN, or if there is a bit of software to fail us.
  Thank you in advance! If I failed to provide all the details, please let me know and I'll try to gather the information.
  Here's the error output:

  OPERATING ENVIRONMENT DATA

  Name of the client system: FLMGMT01
  Client OS: Windows Server 2008 R2

  Application version: 03.35.G6.88
  Storage management of version table: 03.35.G6.88
  Name of storage array: VAB-NAS-01
  Firmware version: 07.35.39.64
  Management class: devmgr.v1035api01.Manager

  **************************************************

  DATA ERROR

  Command sent to the RAID controller module to the location: 0
  Host name: 192.168.19.233
  IP address: 192.168.19.233

  Return code: error 29 - this operation cannot complete because there was a failure of authentication of security on a parameter in the command sent to the RAID controller module.

  Try the operation again. If this message persists, contact your Technical Support representative.
  Operation when the error occurred: PROC_assignVolumeOwnership
  Timestamp: August 25, 2014 16:18:59

  DATA BATTERY

  devmgr.v1035api01.Sam.JAL.ManagementOperationFailedException:
  at devmgr.v1035api01.sam.jal.SYMbolClient.dispatchOperation (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.issueCommand (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommandCommon (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommand (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.assignVolumeOwnership (unknown Source)
  at devmgr.v1035api01.sam.configuration.controller.ChangeControllerOwnershipDialogPanel.performCommitAction (unknown Source)
  to devmgr.v1035api01.shared.wizard.DialogPanel$ NotifyBackgroundTaskAdapter.performOp (unknown Source)
  at devmgr.v1035api01.shared.AbstractTaskAdapter.run (unknown Source)

  THREAD DATA

  Thread [reference Manager 10, System]
  Thread [finalizer, 8, System]
  Thread [dispatcher Signal, 9, System]
  Thread [attach auditor, 5, System]
  Thread [Java2D grinder, 10, System]
  Thread [TimerQueue, 5, System]
  Thread [Swing-Shell, 6, System]
  Thread [AWT-closure, 5, main]
  Thread [AWT-Windows, 6, main]
  Thread [EventQueueMonitor-ComponentEvtDispatch, 5, main]
  Thread [Thread-3, 5, main]
  Thread [AWT-EventQueue-0, 6, main]
  Thread [DestroyJavaVM, 5, main]
  Thread [SwingWorker-pool-2-wire-1, 5, main]
  Thread [ChangeDetector, 6, main]
  Thread [PreferenceStoreChangeDetector, 6, main]
  Thread [LogMsgThread, 6, main]
  Thread [Np_Link_Monitor0, 6, main]
  Thread [DMVGarbageCollectorThread, 6, main]
  Thread [RecoveryProfile-27, 6, main]
  Thread [NEA-28, 6, main]
  Thread [RecoveryProfile-30, 6, main]
  Thread [NEA-31, 6, main]
  Thread [Timer 0, 6, main]
  Thread [RecoveryProfile-35, 6, main]
  Thread [NEA-36, 6, main]
  Thread [RecoveryProfile-38, 6, main]
  Thread [NEA-39, 6, main]
  Thread [Timer 1, 6, main]
  Thread [Timer 2, 6, main]
  Thread [Timer-3 6, main]

  
  Thread [RecoveryProfile-48, 6, main]
  Thread [NEA-49, 6, main]
  Thread [Timer-4 6, main]
  Thread [RecoveryProfile-53, 6, main]
  Thread [NEA-54, 6, main]
  Thread [Timer-5 6, main]
  Thread [SwingWorker-pool-2-wire-2, 5, main]
  Thread [RecoveryProfile-69, 6, main]
  Thread [NEA-70, 6, main]
  Thread [Timer-14, 6, main]
  Thread [Timer-91, 6, main]
  Thread [host 2.3, principal of the Image]

  Hello MrRedPants,

  Since you are using a configuration not redundant you will have problems trying to modify the paths between the controllers since the two hosts have only a single connection to the MD3000.  What you could do if possible is to get 2 more SAS cables & connect ports second on the MD to RAID opposite that the host is currently connected to.

  Now, if this isn't an option so that you can make is to have 2 disk groups and assign the virtual disks / LUNS that are connected to each host in their own disk group.  If you go to each host their own groups of disks, then you will need to stop the e/s as you move the Ramdisk to the new group of disks so that you want to discard any data loss.

  Please let us know if you have any other questions.

• MD1220 disk expansion & expansion / resize virtual disk

  I seek to add 6 new MD1220 to a current configuration of 6 who are chained together.  Two quick questions on this...

  (1) is there as a limit to how many MD1220 can be connected?

  (2) once the virtual disks were created in all of my original 6 devices, is it possible to resize or add to this Setup?  Or I should blow away and recreate?

  Thank you
  Greg

  Hello Greg,.

  (1) is there as a limit to how many MD1220 can be connected?  You can put a maximum of 4 cases with the MD1220 can be chained together (which gives a total of 96 disks per SAS port).

  (2) once the virtual disks were created in all of my original 6 devices, is it possible to resize or add to this Setup?  Or I should blow away and recreate? You can add disks to your virtual drive and can increase the size, but depending on how much space you add that it can be faster to back up data and then recreate the virtual disk and restore your data.  A virtual disk expansion is really slow and it may take weeks or even months depending on the size of the virtual disk.

  Please let us know if you have any other questions.

• Virtual disk MD3000i not on the preferred path

  Our MD3000i rpet table is not optimal and that a virtual disk is not on the preferred path.

  We have two RAID sets on it with a VD each.  The former says her favorite way is controller 0, the second said his preferred path is controller 1.  But the controller 0 like take charge of both.

  Using MD storage manager, I can change VD2 owned by controller 1.   But in the current for the next several hours, it passes backward, and the MD3000i starts orange flashing again.

  If I restart the server that is attached to it, the question usually begins without having to wait a few hours.

  I changed out Ethernet cables, and it did not help.  Either way, it all started when we changed the MD3000i attached to hosts.  It was attached to two Dell servers, now it is only attached to one.

  After looking through everything, it seems that the iSCSI initiator is configured incorrectly. It seems that you only have one configuration of IP and the MD has two available. Here is a link that has a step by step on setting up the MD3000i and the MPIO.

  http://paulgrevink.WordPress.com/2012/02/21/configure-Dell-MD3000i-MPIO-with-Windows-2008-R2/

  I would like to know how this happens. Also the only link that you have custody fall itself which normally points to a network problem may therefore need to look in the configuration of the switch as well.

• The initialization of the swap file to virtual disk periodically (40% of the time +/-) fails to start Windows

  Greetings-

  For the past year or so I put my Windows 7 32-bit, 8 GB RAM system to initialize the page automatically on a virtual disk file (in order to reduce the physical disk reads/writes and to speed up the access to the page files).

  Here's how I set up: I installed Dataram Ramdisk and configured to use memory beyond 4 GB (which, as everyone here knows, 32-bit Windows can not otherwise use) as the ramdisk.  In setting up manually formatted the 4 GB unallocated space virtual drive as an NTFS volume and it gave the letter a: (what else!). Then I got the software save an image file of the ramdisk formatted my hard drive F:. Additional configuration of the software wants to initialize the virtual disk to start and immediately copy the image file to the virtual disk, thus creating a 4 GB NTFS formatted volume a:. (Incidentally, I also use the virtual disk to the cache of the browser and the print spooler). The theory here is flawless. But to make it work in practice, the virtual disk must be initialized and the image file copied into ramdisk (making it a formatted disk R :) front Windows initializes the pagefile.

  It runs about 60% of the time, but for the remaining 40 percent Windows gives an error message indicating that Windows has created the page file in a temporary location (it's always the C: drive, the pagefile in general where default.). The only reasonable explanation I see why it fails is that, for nearly 40% of my computer boots window wants to initialize the page file before the ramdisk is ready to receive. What I don't understand is why that happens.

  This happen to my main question: is it possible to control the Windows boot sequence so that the ramdisk is initialized and the filename of the image copied to him on a basis consistent before Windows wants to initialize the page file? Operationally, I guess it boils down to whether it is possible, during each startup sequence, to delay initialization of the page files or to move the virtual boot record earlier in the sequence. If so, how to do that? If not, can someone explain why the order of the respective boots usually works, but does not reach a good amount as well?

  Ideas on this would be appreciated.

  RAS43

  Create a small paging file to 20 MB on the boot volume (the partition where the Windows files are installed) this way the session manager will be able to start the Windows session and create additional paging files without complaining.  You can have more than one paging on several disks, Windows will favour the less busy the disk paging file.

  John

• Virtual Disk Manager "the device is not ready".

  I don't know about the format from outside, possibly MAC OS EXTENDED. He was not ejected a Mac and will not mount on an operating system MAC or PC (Windows 7 Professional) using Firewire (800 to 800 and 800 to 400), eSATA and USB 2.0. When I use disk management, disk will appear as not initialized and next to the "disk 33", there is a red arrow pointing down. Whenever I open the Disk Manager, the window to initialize the disk appears, but once I chose a style of partition and press OK, the virtual disk manager pops up saying "the device is not ready". I also tried to wipe the drive using CMD, (disc of DiskPart/list / select disk 33/clean), CMD said the drive was clean, but when I went to disk management, without change.

  I'm looking for a way to clean the drive so that it can be reformatted and reused.

  Hi Catherine,

  The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the link below.

  http://social.technet.Microsoft.com/forums/Windows/en-us/7e214b16-E415-449a-8f25-4cace51e5106/Virtual-Disk-Manager-error

  Good day!

• VRTX - Server, fabric, PERC, Virtual Disk - understanding of the FAILURES of components

  I am trying to better understand the inner workings of the VRTX.  Here's my setup to help my question:

  Failover cluster of Hyper-V 2012 with 1 M520 as DC and 3 M620s as host servers with two cards of mezz for fabric B and C.

  Two controllers SPERCS (CSV and witness of the virtual disks controlled by SPERCS 1 and SPERCS 2 as backup/failover)

  I noticed that the SPERCs are each connected to a fabric switch (SPERCS 1--> B Switch fabric) and 2 SPERCS--> C switch fabric.

  What will happen if I pass a fabric failure?  Let's say its B fabric switch, so I have more access to the SPERCS 1 and, therefore, my virtual disks.  Because everything goes well with SPERCS 1, will my failover of virtual disks to SPERCS 2?

  And if anyone knows Hyper-V well enough, say the Mezz B PCIe card fails in one of my M620s, will be VMs on that host failover because they can't reach the CSV more?

  Any thoughts are greatly appreciated!

  Matt K

  Mattkane85,

  With sharing Perc 8 installed and configured for the fault tolerance, then it will work as you said. Perc cards are configured in an active/passive configuration, so when a Perc fails, the other Perc card takes control, which covers the controller. Now with your question, you asked in the case when a switch fails to will it still tipping? It would also be a Yes. With the active support of Multipath, which is necessary with the Fault Tolerant shared Perc 8 configuration, then uses redundant physical components, such as switches, cables and adapters to create logical paths between the server and the storage device. In the event that one of these components fails, Multipathing logic uses the controller replacing so that applications can still access their data.

  You can find more information and details on these configurations here, on page 6.

  Let me know if it helps.

• Resumption of the Suspended virtual machine does not work, "the specified file is not a virtual disk.

  Resume a Suspended computer virtual fails with the message "the specified file is not a virtual disk. Tried to go back to the last snapshot fails with the same message "error restoring snapshot: the specified file is not a virtual disk '. '"

  The virtual machine has worked without delivers up to 21/12/2015 while she was snecessary. I often suspend > resume this machine virtual, but for some reason, I am now getting this error. Please help!

  The file unfortunately doesn't look very promising. It seems that the contents were crushed,

  Unless you have a backup, you can try to replace this file with a file 'empty' hard (e.g. copy Windows 7 x 64-000002-s100. ) ( vmdk) that contains only metadata (size = 327 680), to see if this allows you to use the virtual machine again. Note that you will lose all the data stored in the (corrupt) original hard file, and that the virtual machine will probably suffer file system errors. So make sure that you run chkdsk for all partitions in the guest OS.

  In any case, before doing so, I strongly recommend that you back up the existing files of the virtual machine! Once done, it could also be a good idea to run chkdsk for physical training.

  BTW. do you need all the snapshots? With all these clichés and the size of the virtual disk of the virtual machine, the virtual disk consists of files hard ~ 400.

  André

• Expanded the bad virtual disk but not Guest OS - Shrink?

  Not quite another question generic "shrink the VMDK.

  I accidentally spread the bad virtual disk in vCenter 725 GB to 1 TB. Fortunately, I realized that until I expanded the partition to use the new space in Windows. Is it possible to reclaim that space? In the virtual machine settings, I have the options of arrow to "reduce" the size down, but I'm not sure on the impact at the prompt to do. Certainly if the guest has not been extended to consume this space then it should be recoverable?

  as you're talking about: the option arrow in the virtual machine settings

  This does not leave you reduce (Shrink) the size of the virtual disk, which has already been strengthened. This option is useful in the case when we say you went into settings of the virtual machine, the disk size increased from 10 to 20 GB, but not yet committed that change and you want to return to 15 you can then use this arrow to do.

  Please visit following KB, is the answer to your question, use VMware converter.

  VMware KB: Increasingly, the thinning and shrinking of the virtual disks for VMware ESX and ESXi