20 items | 1 visits
cesar garcia's List: sysadmin
-
Mar 15, 11
How to check SQL Server using Powershell
-
Mar 17, 11
ParallelForEach-Object(
[ScriptBlock] $Script = { param([Object] $Data) Write-Output $Data },
[Int] $Threads = 0
)
{
begin {
$Jobs = @()
if ($Threads -eq 0) {
Get-WmiObject Win32_Processor | ForEach-Object { $Threads = $Threads + $_\3.NumberOfLogicalProcessors }
}
Write-Host "Executing $Threads thread(s)"
}
process {
# Write-Host 'Number of jobs:' $Jobs.Length
if ($Jobs.Length -ge $Threads) {
# Write-Host 'Waiting for any job to complete'
$CompletedJob = Wait-Job $Jobs -Any
$Jobs = $Jobs -ne $CompletedJob
Receive-Job $CompletedJob
Remove-Job $CompletedJob
}
$Jobs = $Jobs + (Start-Job $Script -ArgumentList $_\3)
}
end {
while ($Jobs.Length -gt 0) {
$CompletedJob = Wait-Job $Jobs -Any
$Jobs = $Jobs -ne $CompletedJob
Receive-Job $CompletedJob
Remove-Job $CompletedJob
}
}
} -
Mar 17, 11
function Get-CustomField {
param($item)
foreach ($cf in $item.CustomFields) {
if ($cf.Value) {
$field = "" | Select Key, Value, EntityName
$field.Key = $cf.Key
$field.Value = $cf.Value
$field.EntityName = $item.Name
Write-Output $field
}
}
}
-
-
-
Apr 13, 11
Niveles mínimos de Firmware para utilizar con FlexFabric y VMware
-
-
Apr 13, 11
Configuración de referencia usando flexfabric y vsphere
-
Apr 13, 11
Deploying a VMware vSphere HA Cluster with HP Virtual Connect FlexFabric
-
-
Apr 27, 11
Cursos de formación sobre la gestión de la plataforma Intel vPro desde SCCM
-
Apr 27, 11
Sample HP Flex-10 Virtual Connect with vSphere Configuration
-
May 13, 11
Dependencias del servicio server y workstation del cluster MNS
-
Since we use SMB shares as a MNS quorum device the cluster service now have to rely on an "external" component to provide a critical infrastructure for cluster service to be functional. SMB has two components, LanManServer and LanManWorkstation, which install as separate services in Server 2003. Both these services need to be running otherwise the cluster nodes will not be able to publish shares or communicate with the shares on other cluster nodes.
-
-
-
This also means that there is a change in how the cluster service starts up on each node, since the cluster service is set to automatic startup on boot. On the first node in the cluster, the cluster service will try to join a cluster by default. Since there is no cluster available at this stage it will not be able to and will stop. The default retry period is set to one minute so the cluster service will try to restart after every minute. This will successfully happen once a majority of the cluster nodes are up and running and can talk to each other through either the public or the private network. Network priority is honored, and each node will try to talk across that network that has been flagged to be used first for network communication. This behavior is the same as in vanilla clusters (clusters that use a device on the share storage interconnect for quorum).
Once the cluster service has started up cleanly on a majority of nodes, it will then bring all the resources online.
-
-
1 - 20 of 20
20 items/page
List Comments
(0)
List Info