Posts Tagged ‘zerto’

 
Enabling vCenter Server Data Collection
 
To enable vCenter Server data collection:
1.Connect to the vCenter Server.
2 In the Administration menu item, selectvCenter Server Settings  The vCenter Server Settings dialog is displayed.
3. Select Statistics.

 
4. Make sure that the Statistics Level value for all interval durations up to and including the one day duration is at least 2. If any of the durations have a value less than 2, do the following, starting with the smallest interval:
a) Select the interval and clickEdit
b) Change Statistics Level to Level 2
c) Click OK

 
5. Repeat step 4 for all the values up to and including the 1 day interval duration.
6. Click OK and wait for at least a day before using the aggregate usage data. Collecting Data Characteristics for VMs
You can collect data characteristics for the virtual machines in a VPG in one of the following ways:
 
Via vSphere Client console performance statistics.
 
By running a script to collect the data characteristics.
 
Note: The script samples supplied with the download, require vSphere PowerCLI and permissions to access the vCenter Server using the script.
 
8 By using operating system performance monitors, such as the Microsoft Performance Monitor utility for Windows operating systems or the iostat command for Linux operating systems. Collect data for a minimum of one day. Collecting this information impacts on performance and therefore the collection period should be long enough to gather a true representation of usage but not too long. The first procedure described below, to collect data characteristics for the VMs via the vSphere Client console performance statistics, uses
a timeframe of one day and the second procedure, to collect data characteristics for the VMs by running a scri pt to collect the data characteristics uses a timeframe of seven days.
 
Note: When running vCenter Server versions before version 5.x, if any of the virtual machines use NFS storage, metrics for the
NFS storage are not generated by the vCenter Server. To collect data characteristics for the VMs via the vSphere Client console performance statistics:
1. In the vSphere Client console select the VM and open the Performance tab.
2. Click Advanced
3 . Click the Charts Options link. The Customize Performance Chart dialog is displayed.

4. In Chart Options , drill-down in Disk and select Past day
5. In Counters , click None to clear all the selections and then select Disk Write Rate or Write Rate
6. Click OK
 
9 A chart similar to the following is generated:

Use the chart for the average write rate of the VM.
To collect data characteristics for the VMs via a script:
Note:
The following script and the samples supplied with the download, require vSphere PowerCLI and permissions to access
the vCenter Server using the script.
 
Run a script similar to the following:
 
$report = @()
Get-VM | %{
$stats = Get-Stat -Entity $ -Stat disk.write.average -Start (Get-Date).adddays(-7) –
ErrorAction SilentlyContinue
if($stats){
$statsGrouped = $stats | Group-Object -Property MetricId
$row = “” | Select Name, WriteAvgKBps, WriteAvgMBps
$row.Name = $_.Name
$row.WriteAvgKBps = ($statsGrouped |
where {$_.Name -eq “disk.write.average”} |
%{$_.Group | Measure-Object -Property Value -Average}).Average
$row.WriteAvgMBps = $row.WriteAvgKBps/1024
$row.WriteAvgKBps = “{0:N2}” -f $row.WriteAvgKbps
$row.WriteAvgMBps = “{0:N2}” -f $row.WriteAvgMBps
$report += $row
}
}
$report | Export-Csv “C:\ZertoOutput.csv”
 
 
 
 
Note: If you want a value other than seven days, change the value of the adddays() function. For example to collect data
for three days, use adddays(-3)
 
Use the resulting file, C:\ZertoOutput.csv , for the average write rate of the VM.
Note: Versions of this script are included in the download with this document
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Upgrade VCenter

In order to ensure protection is not affected when upgrading or replacing a vCenter, the vCenter database should be preserved

Upgrade then make sure Replication all comes back green

 

Upgrade Hosts

Before Upgrading the Hosts to the latest ESXi , double check the current version of Zerto supports the version you are putting on or you will get the error on Upgrade “VRA unsupported esx version”

Migrate all VM’s to other VPG’s , migrate 6 VM’s at a time

Once VM’s migrated , shutdown VRA and VRAH , restart upgrade host

You can migrated VCC machines to other hosts without effecting replication

https://nolabnoparty.com/en/vsphere-6-7-upgrade-esxi-6-5-to-6-7-pt-3/

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I tried to stop a VPG in Zerto after some DR testing, however, the Stop failed and the errors showing where : 

Forcibly delete VPG in Error State : Undo Log Isn’t Empty can’t start new transaction

After lodging a call with Zerto Support, we had to forcibly remove the VPG Via Powershell and Re-Add it back

**Before you do this I recommend you log down all the VM’s in the VPG and the Temp Data Drives

You will need to download and install the Zerto Powershell Tools : Zerto.PS.Commands.Installer for your version

After this is run you need to Open the Zerto Powershell and run 

ForceRemove-ProtectionGroup

Enter the VPG Name without Quotes

Enter the IP of the Zerto Server and username and password ( admin / password ) 

Once removed you can use the Zerto Virtual Replication Diagnostic Tool to import the VPG from the old setting file :

Then navigate to : 

C:\Program Files\Zerto\Zerto Virtual Replication\ExportedSettings

Find the latest backup and try and re-import the VPG

If this fails for whatever reason you will need to use the GUI at the customer side to recreate manually hence Note to backup VM names and Temp Data Drivers

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently had a few Zerto Recovery Groups ( VPG’s ) came up with the state 

Recovery is possible. (0%)

Connecivity to the VM’s where ok , and when I ran through the Wizard after Editing the VPG is came back with all ticks. A reboot of the server and SCVMM server did not clear the issue either

In the end we had to perform a “Force Sync” to resync the delta’s

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

If you have a server which isn’t syncing and there is an Active Alert on the VPG Page stating the VM is powered off and you have confirmed it is on, try the following.

 
Log into ZertoServer – Stop the Zerto Virtual Manager service. From the following location, rename the following folders to “orignalName”_backup; PublicCloudReflection,VCDReflection & VCenterReflection. Start the Service. New folders should appear and start populating.
 

Migrate the server from one host to another & refresh the Zerto management page. The alert for the server being offline should be gone,

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)