Remove-MemoryDump
The Remove-MemoryDump PowerShell cmdlet is a specialized maintenance utility used to delete diagnostic memory dump files from NCache server nodes. Memory dumps (generated via the Get-MemoryDump tool) are vital for deep-dive troubleshooting and crash analysis, but they consume significant disk space. Once diagnostic analysis is complete, administrators use this command to free up storage resources and maintain system hygiene without needing manual file-system access. This cmdlet ensures that sensitive diagnostic data is removed securely and efficiently across both Windows and Linux environments.
Remove-MemoryDump -Server -FileName [-Port] [-Credentials] [-NoLogo]
Examples
- This command deletes the dump file created on server 20.200.20.11 with specified name.
Remove-MemoryDump -Server 20.200.20.11 -FileName dumpFile.dmp
- This command deletes the dump file on server 20.200.20.11 with specified name without prompting the user to cancel it.
Remove-MemoryDump -Server 20.200.20.11 -FileName dumpFile.dmp -Force
- This command deletes the dump file created on server 20.200.20.11 with specified name, using security credentials.
Remove-MemoryDump -Server 20.200.20.11 -FileName dumpFile.dmp -Credentials(Get-Credential john_smith)
Properties
Note
The parameters with asterisk (*) on their names are the required parameters and the rest are optional.
| Parameters | Data Types | Description | Default Value |
|---|---|---|---|
-Server* |
<String> |
Specifies a server name where the NCache Service is running and a cache with the specified cache-name is registered and the dump was created. | - |
-FileName* |
<String> |
Specifies the name of memory dump file that is to be deleted. | - |
-NoLogo |
<SwitchParameter> |
Suppresses display of the logo banner. | False |
-Port |
<Integer> |
Specifies the server port where NCache Service is listening. | 8250 |
-Credentials |
<pscredential> |
Specifies the user credentials required to authorize access for the specified operation. These credentials should belong to a user with the appropriate permissions at the node. | - |