Full SRM data store

Similar Questions

• Reconfigured HP Data Replication Group does not present as a group of SRM data store

  Hello

  I configured in two data centers with an EVA4000 on the source site and an EVA4400 on the destination site, countered with Continuous Access EVA of SRM.

  I had replicated two EVA virtual disks (and ESX data warehouses) on the EVA4000 Source called EXCHANGE01 and EXCHANGE02 that have been configured in separate groups, data replication (named EXCHANGE01-GROUP and EXCHANGE02 GROUP) of the HP Command View EVA. These have been picked up properly by SRM as replicated data stores.

  So I decided that it would be preferable to not not two data stores more as a single unit and therefore re-configured continued access by removing the virtual disk EXCHANGE02 of its data replication group and adding as a member of a GROUP named EXCHANGE01. After that, the GROUP named EXCHANGE01 is fail-over for Command View EVA unit and contains EXCHANGE01 to virtual disks and EXCHANGE02. The problem is that when I use the "Rescan replicated storage" option in SRM, you can still see the two Datastores EXCHANGE01 and EXCHANGE02. As it is, I need to create two groups, one by the data store, while in reality a continuous access switch the two as a single unit. The MRS server has been restarted, the berries reread several times, and in fact the EVA4000 has been restarted.

  Two things, I guess. Am I right in thinking that SRM should report to the Group of data replication HP (despite the fact that he refers to it as a\ group data store)? If I am, is there a way I can fix it (preference to short to remove all the replication groups in Command View EVA, a new analysis in the MRS and re - duplicate records?

  I have attached two screenshots - one to SRM showing the list of groups of data store after a new analysis and the other from Command View EVA, showing the Group of data recovery

  AX

  Hi Bob.

  The term SRM data store group is intentionally generic because MRS. support many different providers, and all could use a term "Replication group" as EVA does. If MRS. may correspond to a data store that was created on a LUN that the one being replicated is returned by the adapter, it considers that the store of data as being replicated. It's the storage provider for code adapter for return information LUN appropriate to their table - if you look at the SRM newspapers you will see EVA adapter returns each LUN replicated individually with no information about the relationship of Group of replication at all, so it would be impossible for SRM to have knowledge of this relationship as well.

  Although the LUN in a replication failover as one group power group, they can be taken individually for use during the test of SRM, so maybe it's one of the reasons why HP choice to list each ONE separately.

  In all cases, you have several alternatives: one is to keep your existing environment and configure two groups of protection; on the side of recovery, you can set up a restoration plan unique to switch both of these groups; In addition, you may have configured 2 other recovery plans, one for each protection group, which would be only used for the test, and which would test each LUN and virtual machines on it individually - this could reduce the load on the DR ESX servers during the test rather than to test simultaneously. Of course, you can create a single LUN as well and that of course would make the theoretical discussion - it could be better if your virtual machines must be tested together because the application dependencies.

  You might consider following up with HP if you want more insight as to the relationship of EVA "Replication groups" viz SRM, which is why they chose to not to expose information to the replication group.

• Names of recovery SRM data store

  I just did a full restore on some demo servers and data warehouses on the side of recovery mounted with snap-< number > - DatastoreName...  Is this normal?

  Yes this is normal - ESX on any volume resigned proceeds to indicate that it was a copy and has a new signature. See the thread next to the advanced option to change it.

  http://communities.VMware.com/message/1876460

• Mappings of data store for replication Multi VM in SRM 6.1

  In an earlier version of MRS. datastore mapping was necessary if someone wants to replicate several virtual machines of VR. But how to do this in 6.1 SRM?

  VR is a replication solution that does not require "datastore mapping" just VM source and target data store.  Just several virtual machines with RV replication requires selecting the same target for all that are selected at the same time data store. This does not change 6.1 RVing and SRM has no impact on this.

• SRM 5.8 requires me to burn the data store storage in both placeholders?

  Honestly, I'm having a nightmare of a time finding documentation on how all the pieces of 5.8 SRM relate to each other.  I try to use the VSphere vs array based replication and I deployed on two sites and "twinned" replication servers, but nothing more.

  So I'm at the point where I have to "Configure Placeholder Datastore", which States:

  You specify a placeholder for data store Site Recovery Manager use to back up virtual machines placeholder on the recovering site.

  You must configure a data store space on the two sites of the pair to establish a bidirectional protection and restore.

  Well I don't see where I could specify that if I do two-way or reprotect, however, when I go to configure the placeholder data store it lists only data warehouses that are connected to my SOURCE site.  If am only go simple failover to my protect site dealing so how do I enter my site protect data above warehouses?

  You can specify the inventory maps and data warehousing space reserved for both sites, but you must first select the desired site.

  Hope this helps,

  Daniel G.

• Data store is full

  Whenever data store is about full then vm is suspended but how it can create the VMS file at this point if no free room isn't.

  If the data store is running out of space, the virtual machine that requires additional disk space is "Paused" rather than "suspended", so you should not see a file .vmss for them.

  André

• [SRM 4.1] Configuration files on the data store separate - anything to be aware of

  Hi all

  Right almost about to deploy it now, just do a prep work behind the scenes on the storage, consolidate space provisioned but unused. One thing I noticed on the environment, is that a separate data store has been implemented for config (nvram, vmsd, vmx, vmxf) files.

  I think it was just a matter of preference at the time of installation. Are there any special requirements that I need to know about the above with SRM? I usually have all the files of the virtual machine in a data store, and the file to make relatively easy failover. But if we have several virtual machines with configs on different data warehouses, it could get a little complicated. Should I consolidate them all back first?

  Thanks for any advice in the meantime.

  Hello

  All virtual machines have their residing on this unique data store config files?

  If Yes, then you will be able to have a single protection group and thus you will only be able to failover all virtual machines, losing a granularity.

  Michael.

• alarm data store (if the data store is 90% full)

  I would like to receive an alarm email if my data stores are 90% full.

  any help would be appreciated

  First, we will eliminate any potential problems with the SW forum and the copy that you made.

  I have attached the script, see if that also returns an empty mail.

  To ensure that we use the same VITK can you do a Get-VIToolkitVersion

  Made this comeback

  VI Toolkit Version
  -----
  VMware VI Toolkit for Windows 1.5 build 142961
  

  And the fact that the return values

  Get-Datastore | Select Name, Type, CapacityMB, FreeSpaceMB
  

• Delete a snapshot in ESXi 5 when data store is almost full

  I'm very skiddish on use or deletion of snapshots after a disaster, I had with them last year. So, I thought I would get your recommendation before you continue.

  I have a virtual machine running on the host with about 700 GB of total space on the data store. The virtual machine uses about 500GB and there is only a snapshot of the virtual machine. The virtual machine uses a disc thin provisioned. I received a warning that there is insufficient data on the space store and there are only about 120 GB left. Is it safe to remove the snapshot? Should we double the size of the virtual machine to "consolidate? The last time I did it with multiple snapshots and a lot less space, it's disaster.

  Edit: Here's what's on the data store (for this virtual machine). There is an another VM on the same data store which shows it takes 40 GB of space.

  

  Here's what it says on the storage to Apollo (the virtual computer name) under summary in vSphere:

  

  The basic disk can only 'baloon' upward only by the amount of data in the snapshot, which is 214 GB function provided screenshot and to be on the safe side, you have to assume that he will do. If you need to at least 214 (I'd Go 220) free on the data store for a safe removal-snapshot operation.

  Worse: these 214 GBs are given new, added after the creation of the snap. You the kickoff of the removal process. Basic disk to grow per GB 214. Currently, it consumes 355 GB so it will grow up to 569GB. Only one time all the data of the snap is committed to basic disk, the snapshot will be deleted. This is why you need some 220 GB free and available on the data store to start the removal process.

  Instant deletion on an engine out of VM might help a little, but looks like not as much as you want.

  If you shut down the virtual, pagefile will be deleted which will free up to 4 GB.

  Also if you delete a wink on the virtual machine performance, actually another cliché will be created to store the changes that VM is done during the delete operation. According to the rate of change of data within your VM and the time required for the delete operation, it will take little extra space on the data store as well. This need for extra space can be avoided by removing the snap while the VM is turned off.

  However, in your case the virtual computer power on off won't help

  Bottomline - if you can, find a way to get 220 + GB of free space on your data store before you delete the snapshot. Otherwise, the next option is VM migration to a different data store with storage vMotion (without interruption) and deletion of snapshots there (once again, potentially without interruption). A last - cloning in another data store that involves downtime.

  And you cannot clone to USB.

• How can I remove snapshots when the data store is full?

  Hello

  With the help of ESXi 4.0.0 build 171294

  I have a virtual machine with a number of snapshots that became very large (rookie mistake I know). Finally, missed data store.

  Delete all the snapshots of the apparently successful Snapshot Manager but has not not any space free, and watching the VM directory via ssh show the delta files always there.

  I tried following the instructions in http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & externalId = 1007849

  but the I am always left with a complete and all data store the remaining delta files.

  I also tried renaming the file .vmsd and create another snapshot as suggest in this slideshow:

  http://communities.VMware.com/servlet/JiveServlet/download/978799-10548/200704231611490.TSX2007-Top_Support_Issues_-_part2.ppt

  After remove it all the snapshots returned instantly, of course, not doing any consolidation.

  1. Is there an any hope of consolidating these shots?
  2. If this is not possible, there is a way to roll back all the way to the original disk file?
  3. Update the firmware of ESXi at this stage would help?

  Thank you very much

  Alex

  According to the vmdk files, the virtual disk of 250 GB is thin provisioned. Please take a look in the browser of data store to see the current size of the virtual disk. Commit a snapshot to a thin provisioned disk can consume additional disk space (which you do not have).

  André

• data store full, okay do storage vmotion?

  I have a virtual machine with a data disc on a complete data store (approximately 180 MB free). I thought I was doing a hot storage vmotion in another data store. Assming target data store has enough room, it will work?

  I check the process of storage vmotion does use all the disk space on the source (I think the process consider the block on the source changes). It comes to ESXi 4.1

  Hello

  If you have virtual machines running on the data store you can stop them (snack if it's possible) which will give you more space on the data store that it will remove the swap for the virtual machine files.

  Also if possible please get a number of additional logical unit presented and extend the data store.

  Concerning

• ESXi data store on virtual drive

  Client a BE7K servers (M4 UCS C-240), it came pre-installed with ESXi 5.5 and 4 virtual drives, each virtual drive is configured with RAID 5. Now, we need to install a UC application that requires RAID 10. We use not one of the data store for any guest operating system so our plan is to remove this DS and respective Virtual Drive, break this RAID and rebuild than RAID 10 is here the challenge how can we identify which Datastore, mapped with which virtual drive? My understanding is that ESXi does not map 1-1 (IE VD0 = DS1). If anyone can shed some light on to identify what would be really appreciated.

  Thank you.. !

  I hope it's a little more concise:

  Take the exit of

  ~ # esxcfg-scsidevs - m

  NAA.678da6e715d760101f0aa4a61d982f63:1/vmfs/devices/disks/naa. 678da6e715d760101f0aa4a61d982f63: 1 5777f3b3-7bd4c97a-4ba0-a0369f9400b4 0 datastore4

  Then this match with the release of the list of esxcli storage base path:

  Unknown.vmhba1 - unknown.2:2 -naa.678da6e715d760101f0aa4a61d982f63

  UID: unknown.vmhba1 - unknown.2:2 - naa.678da6e715d760101f0aa4a61d982f63

  The Runtime name: vmhba1:C2:T2: L0

  Feature: naa.678da6e715d760101f0aa4a61d982f63

  Full device name: Cisco's Local disk (naa.678da6e715d760101f0aa4a61d982f63)

  Adapter: vmhba1

  Channels: 2

  Target: 2

  LUN: 0

  ... snip

  This must match your 3rd VD, since the target and VD #s start with 0.

  It confirmed in the laboratory: see below

  vd_order_1.jpg

  

  VD0 (1 virtual drive created) corresponds to T0... and VD3 corresponds to T3.

  These figures are of course unique to each hba/controller if you want to ensure the vhba # and controller # (vmhba1 and C2 in my example) come from the device even when they match.

  Kirk...

• ESXi 5.5 only 4 TB usable for the data store

  Hi all

  Although in vSphere Client 5,46 TB of capacity is visible, I can only use 3.64 TB to a data store.

  Configuration:

  -HP Proliant Microserver N40L

  -HP Smart Array P410/512 MB BBWC, FW 3.66 Controller

  -4 x 2 TB as a Raid5

  HP-ESXi - 5.5.0 - iso - 5.72 A

  I read a lot of articles on > limits of 2 TB of older versions of ESXi or controllers, limitation of 4 TB of c# vSphere Client, old firmware and esxi driver problems, etc.

  But I could not understand the problem.

  The P410 controller shows 5.5 TB:

  ~ # esxcli hpssacli cmd - q "controller connector = 1 see the config.

  Smart Array P410 in slot 1 (sn: PACCRID110510NR)

  Array A (SATA, used space: 0 MB)

  logicaldrive 1 (5.5 TB, RAID 5, OK)

  then 2I:0:5 (port 2I:box 0:bay 5, SATA, 2 TB, OK)

  then 2I:0:6 (port 2I:box 0:bay 6, SATA, 2 TB, OK)

  then 2I:0:7 (port 2I:box 0:bay 7, SATA, 2 TB, OK)

  then 2I:0:8 (port 2I:box 0:bay 8, SATA, 2 TB, OK)

  MS (Vendor ID PMCSIERA, model SRC 8x6G) 250 (WWID: 5001438013D9F37F)

  ESXi obviously knows the same size:

  ~ # Esxcli storage core devices list

  NAA.600508b1001ca5e68adc0bc4bc508d6e

  Full name: Serial Attached SCSI disk HP (naa.600508b1001ca5e68adc0bc4bc508d6e)

  Definable display name: true

     Size: 5723091

  Device type: Direct access

  Multichannel plugin: NMP

  Devfs Path: /vmfs/devices/disks/naa.600508b1001ca5e68adc0bc4bc508d6e

  Vendor: HP

  Model: VOLUME LOGIC

  Review: 3.66

  SCSI level: 5

  (etc.)

  But does that 4 TB:

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 T 3.6 2.1 T 1. 5 t 58% / vmfs/volumes/mainstorage

  vfat 249.7 M 177.2 M 72.6 M 71% / vmfs/volumes/aeda2aeb-c934ad60-46ce-cb77abdfabaa

  vfat 249.7 M 175.9 M 73.9 M 70% / vmfs/volumes/c8ace7e9-a96a5914-16 d 4-a697ad4634d9

  vfat 285.8 M 191.4 M 94.4 M 67% / vmfs/volumes/55d7af6e-a25f7c97-c3ec-6805ca0de93c

  I tried to increase the size of the data store, last used area was 11720890367 and last sector was 11720890510 which doesn't really seem to translate into an increase of 1.8 to.

  Thanks for your help.

  DC

  Your output, it shows that there are two partitions vmfs

  3 10229760 3907029134 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  4 3907031040 11720890367 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  A partition with 1.8 to and another with 3.8 to.   That's the reason why you see only 3.8 to

  I don't know why the 1.8 to vmfs volume is not list anywhere (which does not appear in the list of file system of storage of esxcli also). Do you have any before partition created manually. If you think that if there is no data in this 1.8 to vmfs partition you can remove it by using the partedutil command and then use this free space to extend the existing 3.8 to. But do not forget before you delete the partitiaon

• Newly created data store only appear not

  I am building a new LUN NetApp that must be replicated on our site of Dr. I have create volume, LUN and configured the SnapMirror relationship. The SnapMirror runs successfully as expected. When I went to create the Group of Protection of RS, I had no options to select groups of any data store.

  I don't know there is something that I'm on. What should I do to get the data store to show as an option?

  We have a pretty standard setup.

  vSphere/Center 5.5

  5.8 SRM

  NetApp 8.2.3

  After further research, I noticed one of my hosts pointed out my LUN as "snap_xxxxxx" so I started to question the storage configuration. I built a new LUN, install the SnapMirror and SRM was happy.

• Disc SSD data store unavailable after reboot

  I have a Kingston SSD drive installed in a Dell T620 SAS (Controller H710) basket bottom. It is configured RAID 0 (disk). Therefore, it is OK, and I created a data store using the full disc. It works very well in the virtual machine that it is assigned to you. However, when I reboot and look in the configuration of the storage is not there. I can add and it remembers. The bad news is that the virtual machine, it is affected to cannot start as long as I add back in manually.

  A look at the list of devices, it shows that mounted. The difference between it and other readers is it says unknown partition format, it also says non - ssd.

  I'm just against a unit of failure in charge here? I do not see the SSD drives listed in the list of supported devices, but I hardly find this page.

  < small mug shot >

  Why he let me a second hard drive configured to use the rest of a store of data and then not start because there is not enough room for the Swap and not remove the second disk hard when I tell him?

  < / small rant >

  Hi Lou

  Why do not connect you to a port SATA (my last one)?

  This seems to fix. Also, he appeared as an SSD and remembered all the stuff.

  I guess it has to do with the SAS/RAID connection. Will try another drive to be sure.

  Lou