- How to change the hostname of an existing license
- From the License Support menu select List License
- Select the checkbox for the license you want to change (you can only do one license at a time)
- Click the Action dropdown and select Repair
- Enter the new hostname
- Select Repair then select Complete
- From the License Support menu select List License
- How to deploy OpenJDK on LifeKeeper
-
Download OpenJDK, the Windows x64 Installer, from https://openjdk.java.net/
Deploy the software on the Target node first
In LifeKeeper, perform a switchover/In-Service
Repeat the steps above on other Target(s) after the switchovers are completed
Note: This is a Highly Available deployment as you are never installing the software on the Source/Active node.
From a Command Prompt
type javac -version
Your output should be as follows:
“C:\Windows\system32>javac -version javac 14.0.1”
If not, you may need to add the following to your Systems Variable PATH/environment:
- Control Panel\System and Security\System\System Properties\
- Select the Advance Tab
- Select Startup and Recovery
- Select Environment Variables…
- Select Path and then Edit
Add C:\Program Files\Java\jdk-14.0.1\bin to your string to reflect the following in the example below:
C:\Program Files (x86)\Common
Files\Oracle\Java\javapath;SystemRoot%\system32;%SystemRoot;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program
Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\;C:\Program
Files (x86)\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files\Java\jdk-14.0.1\bin
Perform the aforementioned on all nodes in your cluster(s).
- How to recreate a mirror for an existing clustered DataKeeper Resource
Problem:
A customer may have experienced some issues where a DataKeeper Resource is listed as Offline via Windows Server Failover Cluster.
Note: An existing job in the DataKeeper GUI will most likely have a RED X status
Solution:
Remove all of the old mirror remnants from the Source and Target nodes Manually recreate the mirror via the emcmd . createmirror command
To remove the mirror configuration from both nodes:
- cd %extmirrbase%/support (This is a shortcut to the DataKeeper\Support directory)
- run “cleanupmirror (drive letter)” Note: Run this command on the Source first. This command performs the following:
- deletes the local mirror only (NO DATA)
- resets the switchover flag
- notifies the driver and service that no mirror is present
To verify that the mirror has been properly removed, execute the following:
- cd extmirrbase (This is a shortcut to the DataKeeper directory)
- run “emcmd . getmirrorvolinfo (drive letter)”
The output should reflect no mirror e.g. 0 servername 0
Now you are in a position to manually recreate the mirror.
The syntax is as follows:
- emcmd (Source IP) createmirror (drive letter) (Target IP) A or S (Async mirror/Sync Mirror)
Upon completion, the DataKeeper UI will now reflect a Resyncing status. This can also can be verified from a command line by executing: - emcmd . getmirrorvolinfo e
The output will reflect “E: 1 servername (Target IP) 2, where 2 is a mirror definition, indicating a Resyncing status
Return to Windows Failover Clustering and online the Failed DataKeeper Resource
- How to determine what GPOs have been applied to a server
Problem:
Group Policy Objects are sometimes deployed or redeployed after a server is rebooted impacting the way the LifeKeeper (GUI) or DataKeeper may or may not perform.
Solution:
There are two methods:
From Start\Run enter rsop.msc- The console will provide a list of policies that have been applied to a server
- This output will display a list of policies that have been applied to a server
Note: To determine what GPOs are being enforced per a user, enter gpresult /Scope user /v
Post your comment on this topic.