Case #07753083 — After a failed Oracle RMAN export, several temporary services remain on the target server

[dnumrich]

We have recently been performing RMAN exports from Veeam. When those exports fail (usually due to user error on our side) some temporary services created by Veeam during the process are not cleaned up.

We have a workaround in place, where we use Powershell to find those services and if they are in the stopped state, delete them:

#clean up orphaned temp veeam oracle services
$svc_nm = (Get-Service | Where-Object {($_.Name -like "Veeam.Oracle.Service_*" -or $_.Name -like "OracleServiceVeeamTmp*" -or $_.Name -like "OracleVssWriterVeeamTmp*" -or $_.Name -like "OracleJobSchedulerVeeamTmp*") -and $_.Status -eq "Stopped"})
$svc_nm = $svc_nm.name

foreach ($svc in $svc_nm)
{
sc.exe delete $svc
}

This works well enough, so we don't really have an issue anymore. I thought I would submit this as a possible product improvement, whereby when an export is started, Veeam performs this action as its first step to ensure unneeded temporary services are cleaned up.

[PetrM]

Hi Duane,

I appreciate your willingness to share this feedback with us, it is undoubtedly very valuable. However, I must note that we cannot treat your question as a feature request because it concerns a technical issue and not by-design behavior. Nevertheless, I will share this information with my colleagues on the engineering team so we can address it in one of our future releases.

Thanks!