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

Tags: VMware

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.

After a failed raid array recovery my data store is missing

Hi all
I'm under ESXi at home, but I have a problem with that I need help
First of all, let me start with the specs:
ESXI: 5.1.0,799733
RAID Controller: Adaptec 6805 (driver of the community with the support)
Configuration of RAID: RAID 5 12,71 TB of disk
I had some problems with my RAID controller which I solved it using the Adaptec article: a table failed can be recovered? I ended up drop the table and re-create it.
The RAID array is now in OPTIMUM condition, so I started ESXi and connected using vSphere to find all my virtual machines as unknown (Inaccessible).
I started googling and found some information, but nothing so far to solve this problem.
I tried info from these links:
- Problems after RAID5 which are now resolved, I am not able to mount VMFS
- VMware KB: Re-create a missing partition of VMFS datastore in VMware vSphere 5.0/5.1/5.5
~ # df k
1 k-blocks used available use % mounted on file system
VMFS-5 483131392 319600640 163530752 /vmfs/volumes/500 GB 66%
vfat 4192960 141952 4051008 3% / vmfs/volumes/51f45583-c7047877-9ff7-0015178fcc59
vfat 255716 138872 116844 54% / vmfs/volumes/55f80475-edb62e49-366c-1f1975e107c2
vfat 255716 135420 120296 53% / vmfs/volumes/8367f77f-57cb0e3e - 888-b-046f29890a95
vfat 292688 206792 85896 71% / vmfs/volumes/51f4556a-e6c74124 - 5A 63-0015178fcc59
~ # fdisk-l
***
The fdisk command is deprecated: fdisk does not support GPT partitions. Thank you for using partedUtil
***
Disk/dev/disks/t10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000: 500,1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device boot start end blocks Id system
/ dev/Disks/T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p1 1 115 917504 5 extended
Partition 1 does not stop the limit of cylinder
/ dev/Disks/T10. 115 637 4193280 6 FAT16 ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p2
Partition 2 will not stop the limit of cylinder
/ dev/Disks/T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p3 637 60802 483271704 fb VMFS
/ dev/Disks/T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p4 * 1 1 4080 4 FAT16 < 32M
Partition 4 does not stop the limit of cylinder
/ dev/Disks/T10. 1 33 255984 6 FAT16 ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p5
/ dev/Disks/T10. 33 65 255984 6 FAT16 ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p6
/ dev/Disks/T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p7 65 79 112624 VMKcore fc
/ dev/Disks/T10. 79 115 292848 6 FAT16 ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p8
Partition table entries are not in the order of disc
Fdisk: device has more than 2 ^ 32 sectors, each of them is unusable
Found valid GPT with protective MBR; using GPT
Disk /dev/disks/mpx.vmhba1:C0:T0:L0: 4294967295 sectors, 4095 M
Logical sector size: 512
Identifier (GUID) of disc: 0652d5d8-10f3-4264-9d35-1e12b2d23b76
Partition table contains up to 128 entries
First usable sector is 34, last usable area is 27304898526
Starting number (sector) end (sector), Code name of size
1 2048 27304898526 25.4 G 0700
~ # esxcfg - volume - l
< no results >
# ls/vmfs/devices/drives.
MPX.vmhba1:C0:t0:l0 vml.0100000000343130313131435043353336363200000000000053414d53554e
MPX.vmhba1:C0:t0:l0:1 vml.0100000000343130313131435043353336363200000000000053414d53554e:1
T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000 vml.0100000000343130313131435043353336363200000000000053414d53554e:2
T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:1 vml.0100000000343130313131435043353336363200000000000053414d53554e:3
T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:2 vml.0100000000343130313131435043353336363200000000000053414d53554e:4
T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:3 vml.0100000000343130313131435043353336363200000000000053414d53554e:5
T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:4 vml.0100000000343130313131435043353336363200000000000053414d53554e:6
T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:5 vml.0100000000343130313131435043353336363200000000000053414d53554e:7
T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:6 vml.0100000000343130313131435043353336363200000000000053414d53554e:8
T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:7 vml.01000000003630356634396164524149443520
T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:8 vml.01000000003630356634396164524149443520:1
# partedUtil getptbl /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0
TPG
1699651 255 63 27304898560
1 2048 27304898526 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
[EDIT] I have not noticed before that the mpx.vmhba had an additional entry in/vmfs/devices/disks
# partedUtil getptbl /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:1
unknown
1699651 255 63 27304896479
I have attached vmkernel.log
I hope someone can point me in the right direction, I have a backup of my criticism/personal data, but it would be nice to recover the rest as well...
Thanks in advance for the help!
Post edited by: Sebastiaan Grob adding info on /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:1

Running orders more:

~ # esxcli instant vmfs storage list

51f4625a-6482a0da-c112-0015178fcc59

Volume name: Adaptec RAID 1

VMFS UUID: 51f4625a-6482a0da-c112-0015178fcc59

Can mount: true

Reason of mountability-United Nations:

Can will: true

Reason for non-resignaturability:

County of measure pending: 1

Then I tried add the option of storage as described in the present (KB VMware: vSphere management LUNS identified as LUN snapshot ) KB article and my data store is back, no loss!

Full SRM data store

Hello
Among the stores of data that we are replicating VMs is full. Can you be it someone please let me know the process to free up space?
We are at version 5.1, all areas.
SRM 5.1 with replication of vSphere.
Thank you, s
Peter.

Hello

Integration of VR with DTS on the target site is on the roadmap for future versions.

With the versions currently, including 5.1, you can reconfigure the replication (s) in another data target store, however, this internal stop old replication, delete all the files in the replica in the target data store and configure new replication to the new location of the target.

It could be faster, if you:

(1) take hard copy since the current target data store (without the hbr-... vmdk redo logs) to the new location.

(2) stop the existing replication (s).

(3) configure new replication and orient them on the already copied as initial seed discs.

This will happen again full-synchronization initial, but checksum is calculated on the disk blocks and that changes are transmitted over the network.

get the names of Get-ScsiLun data store

Im stuck here... Can anyone help me to get the names of data store for storage devices using the script below? My requirement is to get the naa (ConsoleDeviceName) address and the names of data store for each storage device.
$esxName = "esxsrv1".
$report = @)
Get-ScsiLun - VmHost $esxName - LunType "disk". %{
$row = "" | Select the host, ConsoleDeviceName, model, provider
$row.host = $esxName
$row. ConsoleDeviceName = $_. ConsoleDeviceName
$row.vendor = $_. Name of the vendor
$row.model = $_. Model
$report += $row
}
$report | Export Csv c:\Temp\results.csv - NoTypeInformation
Thank you very much, Kev - o

Try it like this
```
$esxName = "esxsrv1"

$dsTab = @{}
foreach($ds in (Get-Datastore -VMHost $esxName | where {$_.Type -eq "vmfs"})){
    $ds.Extensiondata.Info.Vmfs.Extent | %{
        $dsTab[$_.DiskName] = $ds.Name
    }
}

$report = @()
Get-ScsiLun -VmHost $esxName -LunType "disk" | %{

    $row = "" | Select Host, ConsoleDeviceName, Vendor, Model, Datastore    $row.host = $esxName    $row.ConsoleDeviceName = $_.ConsoleDeviceName
    $row.vendor = $_.Vendor
    $row.model = $_.Model
    $row.Datastore = &{
        if($dsTab.ContainsKey($_.CanonicalName)){
            $dsTab[$_.CanonicalName]
        }
    }
    $report += $row}

$report |Export-Csv c:\Temp\results.csv -NoTypeInformation
```
The script begins by creating a hash table where he maps the CanonicalName with the DatastoreName.

In the 2nd part of the script of the hash table is used to find the DatastoreName through the CanonicalName.

Machine virtual IOPS / s report, how to display the name of the data store?

Hi guys

I am new to the Foglight community, this is a great tool, and I learn a lot.

Currently I am trying to create a simple table that will show me metric of my VMware environment: Virtual Machine name, Datastore IOPS and data store.

However I can't find how to include data store name in the table, because it is not a measure of the Virtual Machine. I think I need to expand the scope of my table to include VMware Datastore, but I don't know how to do this.

-Mark

Check the options available it seems that it can be done with WCF (the frame behind the Foglight dashboards). We recommend generally customers who plan to build views WCF take adequate training or our PSO people engaged in it.

In any case I can help show a quick example of how it's done.

Please try this on a local/test server.

Go to Configuration > definition >

Make sure that you are in my definition, and click the icon to add a view. then choose from the tables and trees - oriented line table

Give a name to the view, go public and make a portlet/reportlet and apply

Switch to the configuration tab and click the change for the lines and choose a query

Under query, expand the VMware and scroll down

Until you can select the query for virtual machines

And press the set button.

Your view should look like this

Now you must select the columns.

Each column has a value you can edit and there is a button + to add additional columns.

Lets start with the name of the virtual machine - click on the button to change to your default column and choose the context.

Click on the drop down menu to enter key and choose the current line (virtual vmware machine)

Click on the drop down menu to access path and scroll down until you can select the name and then click on set.

You have created a table that lists the names of all virtual machines.

You can click on save. and then click test, choose a time and click the result. A new window will open a show the list you of virtual machines.
From here you can continue to add additional columns, each time choosing the key entry in the current line and the path to the metric/string to display.

For example, the name of the data store.
I change the module

Click the configuration tab and click the icon to add a column

For the column value, that I chose defined context once again, the key input is the current row and for the path, I expand the node for the data store

And scroll until I see the Proprietename

If you save and test you will see the result

Keep adding columns and the data you want, notice that you have arrows that allow you to control the order of the columns.

Note that you can click Show advanced configuration properties

This will give you the opportunity to see the properties of the extra table, such as header - giving you the opportunity to give a more meaningful name (name of the data store, the name of the virtual machine, etc.) to the column header.

You can now go you drag and drop the table edge/report and under my eyes, you will see your new view

Drop it in the main view

I hope this has given you the starting point to build this table.

As I said, I strongly recommend going through our WCF training if you plan build more custom views or hire software Dell PSO Organisation to help build you views that correspond to your need.

Best regards

Golan

Need a script to the list name VM, the guest operating system, data store...

I need to move a large number of virtual machines with MS Server 2008 to another storage.
Could someone provide me with a small script for the list: all VM with GuestOS Type (MS Server 2008 filtered), name of store data and the overall computer virtual size!
Thanks in advance

Hello, farkasharry-

How about something like:
```
Get-View -ViewType VirtualMachine -Property Name,Config.GuestFullName,Storage.PerDatastoreUsage,Summary.Storage -Filter @{"Config.GuestFullName" = "Windows.*2008.*"} | %{    ## get the name(s) of the datastores on which this VM resides    $strDatastoreNames = ($_.Storage.PerDatastoreUsage | %{Get-View -Id $_.Datastore -Property Name} | %{$_.Name}) -join ","    New-Object -TypeName PSObject -Property @{        Name = $_.Name        GuestOS = $_.Config.GuestFullName        "Datastore(s)" = $strDatastoreNames        ## the amount of storage that the VM is using        UsedGB = [Math]::Round($_.Summary.Storage.Committed / 1GB, 1)        ## the total amount of storage that the VM _could_ use        ProvisionedGB = [Math]::Round(($_.Summary.Storage.Committed + $_.Summary.Storage.Unommitted) / 1GB, 1)    } ## end new-object} | Select Name, GuestOS, "Datastore(s)", UsedGB, ProvisionedGB
```
It filters on the virtual machines with an OS name ("GuestFullName"), which corresponds to 'Windows.*2008. ' * ' and returns their name, the GuestFullName, the data store (s) on which they reside (maybe more), and the opportunity - and put into service in GB disk space.

Return items are objects, so that you can select export to formats the info as you please, using the, say, Format-Table, Select-Object, Export-Csv, etc.

And, because it uses the cmdlet Get-View, it should work pretty quickly.

How does do for you?

Help with the details of the data store

Hi all
Get the error for the name of the VM data store, below is the script
$report = @)
$vms = get - VM rpt01 | Get-View
foreach ($vm to $vms)
{
foreach ($dev in $vm. Config.Hardware.Device) {}
If (($dev.)) GetType()). {Name - eq "VirtualDisk")}
If (($dev.Backing.CompatibilityMode-eq "physicalMode") - or ($dev.Backing.CompatibilityMode - eq 'virtualMode')) {}
$row = "" | Select the Cluster folder VMHost, VMName, IP, Powerstate, HDMode, HDName, HDsize, MON, HDDisplayName, VMDataS
#$row = "" | Select VMHost VMName, HDName, MON, HDsize, HDMode, HDDisplayName, IP, Cluster, file
$row. VMName = $vm. Name
$esx is get-view $vm. Runtime.Host
$row. VMHost = ($esx). Name
$row. PowerState = $vm. Runtime.PowerState
$row. VMDataS = (Get-Datastore - VM $vm |) Select - 1 last). Name
$row. HDName = $dev. DeviceInfo.Label
$row. HDMode = $dev.Backing.CompatibilityMode
$row. HDSize = [system.math]: Round ($ dev.) CapacityInKB / 1048576)
$row. HDDisplayName = ($esx. Config.StorageDevice.ScsiLun | where {$_.} UUID - eq $dev. Backing.LunUuid}). CanonicalName
$lun = get-ScsiLun - VmHost $row. VMHost - CanonicalName $row. HDDisplayName
$row. LUN = $lun. RuntimeName.SubString ($lun. RuntimeName.LastIndexof ("L") + 1)
$row. IP = $vm.guest.IpAddress
$row. Cluster = (get - view - ViewType clustercomputeresource |?) {} $_ .moref-match $esx.parent.value}) .name
$row. Folder = (get - view - ViewType record |?) {} $_ .moref-match $vm.parent.value}) .name
$report += $row
}
}
}
}
get error below
Get-Datastore: cannot bind parameter 'RelatedObject. Could not convert the value of 'VMware.Vim.VirtualMachine' of type 'VMware.Vim.VirtualMachine' to type
'VMware.VimAutomation.ViCore.Types.V1.RelatedObject.DatastoreRelatedObjectBase '.
C:\VM_RDM_Info.ps1:16 tank: 39
+                 $row. VMDataS = (Get-Datastore - VM $vm |) Select - 1 last). Name
+                                                   ~~~
+ CategoryInfo: InvalidArgument: (:)) [Get-Datastore], ParameterBindingException)
+ FullyQualifiedErrorId: CannotConvertArgumentNoMessage, VMware.VimAutomation.ViCore.Cmdlets.Commands.GetDatastore
Get-Datastore: cannot bind parameter 'RelatedObject. Could not convert the value of 'VMware.Vim.VirtualMachine' of type 'VMware.Vim.VirtualMachine' to type
'VMware.VimAutomation.ViCore.Types.V1.RelatedObject.DatastoreRelatedObjectBase '.
C:\VM_RDM_Info.ps1:16 tank: 39
+                 $row. VMDataS = (Get-Datastore - VM $vm |) Select - 1 last). Name
+                                                   ~~~
+ CategoryInfo: InvalidArgument: (:)) [Get-Datastore], ParameterBindingException)
+ FullyQualifiedErrorId: CannotConvertArgumentNoMessage, VMware.VimAutomation.ViCore.Cmdlets.Commands.GetDatastore

Try to replace this:

$row. VMDataS = (Get-Datastore - VM $vm |) Select - 1 last). Name

with this:

$row. VMDataS = (Get-Datastore-Id $vm. Data store | Select - 1 last) .name

The problem is that Get-Datastore - vm expects the parameter - VM to be a type of virtual machine rather than the display type of the virtual machines that is referenced because the = get - vm rpt01 $vms | Get - view.

Move a virtual machine to a specified data store, creating thin discs

I apologize for the very basic question.
Can someone please provlde a working example of a command-line PowerCLI to move a given virtual machine (for example of the ' t "MY VM Sample" with spaces in the name) of a given data store (say, "Source_datastore", I should specify?) to a given data store (say, "Target_datastore") thin discs?
Concerning
Marius

Get - VM "name VM | Move-VM - Datastore (Get-VMHost "HostName" |) Get - Datastore - name of the "DatastoreName") DiskStorageFormat - slim

You could just specify the data store without having to get the VMhost initially, but if you have multiple clusters with the same name of data warehouses, he can't shoot straight.

Data store Clusters does not

I worked with one of the guys in another thread on get the script below works, but we used a work around on the section of the store of available data in a specific data store instead of a cluster data store. While it will work on a functional level, it fills a particular DS extension and allow now the DTS select the implementation at deployment time. Has anyone successfully supplied VMs in a cluster data store and may be able to give an overview on the excerpt below?
$hshNewVMParams = @ {}
Model = $strSourceTemplate
Name = $strNewVMName
# default pool of resources 'Resources', in order to put the desired cluster virtual machine
ResourcePool = Get-Cluster $strSomeCluster | Get-ResourcePool-name 'resources '.
Data store = "8000-10kSP1-LUN02.
DiskStorageFormat = $strStorageFormat
Location = Get-file $strDestinationFolder
OSCustomizationSpec = Get-OSCustomizationSpec-name $strOurCustSpecName
# Owner = $strVMNotes
} # end s.a.s..
# create new virtual machine
$vmNewOne = new machine Virtuelle-@hshNewVMParams
# define portgroup NIC and MAC addr
$vmNewOne | Get-NetworkAdapter | Together-NetworkAdapter NetworkName - $strSomePG - MacAddress $strNewMacAddr - confirm: $False | Owner of the whole Annotation-CustomAttribute-value $strVMOwner
# Start the virtual machine
Start-VM - VM $vmNewOne

Update: after a few tries and a support call with VMware, I could get this to work with a few workaround solutions.

1. the default action for a cluster of data (without specified DiskFormat) store, is to deploy the same format as the source. I suspected this, but did not confirm until a few weeks ago.

2. the VMware SDK engineer recommended running New - VM and specifying the format of disk, then Move-VM to have the DTS to implement its recommendations.

$csv = "C:\ANT_VMs.csv" of import-Csv - UseCulture | %{

{foreach ($line in $csv)

# Connect to a vCenter

SE connect-VIServer usddrmvctr1

# Clone VM model

$oNewVM = new-VM-name $_. Name - model $_. Model - ResourcePool (Get-Cluster $_.) Cluster | Get - ResourcePool - name 'Resources') - DiskStorageFormat $_. DiskFormat

# Reconfigure VM

$oNewVM | Get-NetworkAdapter | Together-NetworkAdapter - NetworkName $_. PortGroup-confirm: $false | Together-NetworkAdapter - MacAddress $_. MacAddress - StartConnected: $true - confirm: $false

# Reconfigure VM

$oNewVM | Move-VM - Datastore (Get-DatastoreCluster-Name $_.) Data store)

# Owner of the Annotation set

$oNewVM | Owner of the whole Annotation-CustomAttribute-value of $_. Owner

#Power on VM

Start-VM $oNewVM

}

}

How to specify the file of virtual hard disk when you create a new virtual machine using virtual hard disk on the data store?

I'm new to PowerCLI and find quite simple, but in the documentation I read, I don't see how to use a virtual hard drive, existing on a data store when you create a new virtual machine.
Is this simple registration on the virtual hard disk, or did I miss something?
My current create VM is the following statement:
New-VM

-Name $TargetHostName -host $TargetVMCenterHost -data store $TargetVMCenterDatastore DiskMB - 20000 -MemoryMB $TargetHostMemoryMB -NumCPU $TargetHostCPUs -ID $TargetHostOS -CD -Description $TargetHostName

Didn't notice this before, but I think that vSphere will use a backslash instead of a slash in the paths.

Script control? Relocation of the data store

Hi all
I am a beginner with PowerCLI and I'm interested in doing common tasks I would do in the PowerCLI Client. What I'm trying to accomplish is to get all of my ESX hosts in a cluster and remove a host data store.
Here's what I got after Connect-viserver using:
Get-Cluster "cluster name" | Get-VMHost | Remove-data store "DatastoreName".
I think it's that simple.
Thank you
Jim

I'm afraid it's a bit more complicated than that.

The cmdlet Remove-Datastore expects an object of data store via the parameter - store data or through the pipeline.

The parameter - VMHost does not take arguments pipeline.

If your data store is unique, you can do something like this
```
Get-Cluster 'cluster name' | Get-VMHost | %{
   Remove-Datastore 'DatastoreName' -VMHost $_
}
```
In this way, you use the object in the pipeline ($_) explicitly as an argument of the parameter - VMHost.

____________

Blog: LucD notes

Twitter: lucd22

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.

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.

Change of name of data store

Dear all,
I need to understand if this is possible or not, I have a data store who have a few VM in it, if for some reason any Naming Convention I want to rename the data store, it can be done without disruption of the VM? The confusion here is from VM disk shows that the data store in 'change settings' how this will change if the data store is renamed using vCenter server.
waiting for response.
Thank you

You can rename your store data without problems and with the virtual machines running on it, since vSphere using the UUID data store and not the display name.

Names of recovery SRM data store

Similar Questions

Maybe you are looking for