How to remove the Catalog job which is not present in the BE console

-
Backup Technology: Symantec Backup Exec

This will not require any server reboot. But, it may require BE service restart.
Also, perform this task only when there are no backup jobs are running.

ISSUE: (Job: "Catalog JOB") the job missed its scheduled start time by more than 1 day.

ISSUE Description:  

Catalog job 'Catalog JOB’ is not visible in the backup exec console. But we are receiving the error message “(Job: "Catalog JOB") the job missed its scheduled start time by more than 1 day” continuously.
We need to follow the below steps to resolve this issue.

SOLUTION:

If backup job is not visible in the BE console or not found under any of the storage devices. Then, we consider as this is orphaned job and traces are left in BE database and need to remove from the BE database.
To remove the orphaned catalog job from the BE database, we need to raise a case with Symantec and remove the job.

Note: We should take help from Symantec Backup Exec support for doing any changed in the BE database.

Symantec Support Team will delete the orphaned catalog job from the BE database by running the command (in command prompt only).

Comments

Post a Comment

Popular posts from this blog

Veeam Guest Agent is not started

-
Backup Technology: - Veeam Issue: - Veeam job failed with below error message. ------------------- VMware Tools are not running. Guest processing skipped. Failed to prepare guest for hot backup. Error: Veeam Guest Agent is not started ------------------- Cause :- -        VM might be rebooted or down during backup job running. -        Veeam run time agent service stuck on VM server. -        VSS writers might be in failed status. Solution :- 1. Login to the effected VM and verity the uptime. If the VM is rebooted during backup job running then it will completed successfully in next retry attempt or next run. or 2. If you found any VSS writers are in failed status then reboot the server to resolve VSS writers issue. or 3. If Veeam run time agent service “VeeamVssSupport” stuck or not deleted after the veeam job completed then you need to delete the service manually or reboot the server.
Read more

VeeamVssSupport Service not found

-
Backup Technology:- VEEAM Issue: - Backup job failed with below error message. Error: Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [x.x.x.x]. The specified service has been marked for deletion. Code:1072 Cannot create service. Win32 error:The specified service has been marked for deletion. Code: 1072. Error: Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [x.x.x.x]. The specified service has been marked for deletion. Code:1072 Cannot create service. Win32 error:The specified service has been marked for deletion. Code: 1072. Vvv Cause: - The VeeamVssSupport service cannot be installed because it was never uninstalled. It was marked for deletion instead of being deleted. It cannot be removed, but will be removed automatically when the guest OS reboots. Typically this is due to one of the following programs being open at the time the deletion command w
Read more

Veem job Failed to prepare guest for freeze, wait timeout 900 sec

-
Backup Technology: Veeam Sometimes Veeam backup jobs failed on VM with below error message continuously. Failed to prepare guest for host backup. Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec We need to follow the below steps to resolve the issue. Cause: This issue typically involves a very active transactional application running in the virtual machine, and it is taking longer than expected per the default timeout to freeze the I/O for this application/VM Solution You can change this timeout by modifying the value in the registry of the server where Veeam Backup & Replication is installed as follows: 1.        Go to Veeam registry path HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication. 2.        Add a DWORD (32-bit) value named VssPreparationTimeout. The value is in milliseconds (decimal), the default timeout is 900000, which equa
Read more