Forum Discussion
5 Replies
- MarianneLevel 6
This should only apply to the parent job. The child jobs should all display the schedule name.
Similar to this screenshot (borrowed from Internet):Can you show us a screenshot of your Activity Monitor?
- GoodBkpDudeLevel 2
Yea i know, we have this logic already applied, but now I am searching for the solution if there are not child jobs and there is schedule with dash.
For example we have backup failing:
JobID,state,status,scheduleName,client,parentJobID
-----------------------------------------------------------------
8752517,3,4239,-,CLIENT,8752517
8733585,3,4239,-,CLIENT,8733585
8715368,3,4239,-,CLIENT,8715368
8695268,3,4239,-,CLIENT,8695268
8581863,3,4239,-,CLIENT,8581863
8543391,3,4239,-,CLIENT,8543391and there are no child jobs, so we are not able to find schedule name from the childjobs. (this is custom PS script) is there any way, how to determine it? It should be good if there is any solution how to find what schedule had to run exact day. As support team have a lot of old tickets and database is cleanedup after 7days or something...
Thanks a lot!
- MarianneLevel 6
My guess is that the process flow with VMware policies is probably a bit different - that the clients are first of all validated.
So, if the client name is invalid (Unable to find the virtual machine), the schedule name becomes irrelevant.
Well, that is my view. You may want to check with Veritas Support.
Related Content
- 6 years ago
- 9 years ago
- 10 years ago