Bug Report :JOBHISTORY_GUID do not work anymore

[yann_ARMAND]

Hi,
I updated my server to V11.
Now when I use bemcmd -o90 -fmyscript.txt with the old way :

...

JOBHISTORY_GUID={7F3F28E5-F675-40B7-8ECA-142EFC43087D}
...
(I got this history GUID using bemcmd -o21)

The response is always an error :
"The backup selection list that you have selected does not exist."

Does anyone succeeded in using JOBHISTORY_GUID ?

[Bradley_Willads]

Yann,

Let me look into this to see if that functionality was removed.

[Bradley_Willads]

Yann,

This should work. Can you please post your script file, so I can attempt to reproduce your behavior? Thanks!

[Bradley_Willads]

Yann,

How are you getting the JOBHISTORY_GUID? The proper way to retrieve this is to first retreive the Job Instance GUID using the -o23 parameter, and then using the Job Instance GUID in -o21 to get the Job History GUID.

If that is the case, can you run -o21 -hi to make sure it reports back the Job History Record, and it's not a bogus GUID?

[yann_ARMAND]

Bradley,

here is my script :

JOB_TYPE=Restore
JOB_NAME=test-BEMCMD-O90-6

RESTORE_SECURITY=YES
RESTORE_PRESERVE=1

JOBHISTORY_GUID={A3F2D591-73F5-415E-8713-DFEF26967BFD}
SELECTION1=\\ERIKTEST32\C:\yann_test\help.txt

HOLD=YES

To verify my Job History GUID, I tryed :
bemcmd -o21 -hi:{A3F2D591-73F5-415E-8713-DFEF26967BFD}
It works and give me all infos.

[Bradley_Willads]

Yann,

Hmmm...I just ran this in my enviornment, and it worked perfectly fine. Can you please post the outputs of your Bemcmd -o21 and Bemcmd -o23?

[yann_ARMAND]

The -o23 call :

C:\PROGRA~1\Symantec\Backup Exec>bemcmd -o23 -i -j

JOB ID: {C320FE2C-5553-4A0A-A505-25F490FF5104}
JOB NAME: Backup 00001

JOB ID: {7F3F28E5-F675-40B7-8ECA-142EFC43087D}
JOB NAME: Backup 00003

JOB ID: {CA62F185-112A-4C6C-AA42-E00B07E98342}
JOB NAME: test-BEMCMD-O90

JOB ID: {DA413D13-C9D6-41DA-BB87-89058987662D}
JOB NAME: test-BEMCMD-O90-2

JOB ID: {89EF38CC-49AA-430E-9661-1B9AD138A9D9}
JOB NAME: test-BEMCMD-O90-3

JOB ID: {F266886A-A1E1-4BA3-A788-5A9D2419C6B6}
JOB NAME: test-BEMCMD-O90-6

NUMBER OF OBJECTS: 6

RETURN VALUE: 1
============================
I'm interested in Backup 00003, so here is the -o21 :

C:\PROGRA~1\Symantec\Backup Exec>bemcmd -o21 -i:{7F3F28E5-F675-40B7-8ECA-142EFC43087D}

JOB ID: {A3F2D591-73F5-415E-8713-DFEF26967BFD}
JOB NAME: Backup 00003
JOB ACTUAL START TIME: 02/05/07 17:13:33

JOB ID: {C99DC329-9748-4031-8247-CAEECFA6FD76}
JOB NAME: Backup 00003
JOB ACTUAL START TIME: 02/05/07 17:16:58

NUMBER OF OBJECTS: 2

RETURN VALUE: 1
===============================

and now the -o21 -hi :
C:\PROGRA~1\Symantec\Backup Exec>bemcmd -o21 -i:{7F3F28E5-F675-40B7-8ECA-142EFC4
3087D}

JOB ID: {A3F2D591-73F5-415E-8713-DFEF26967BFD}
JOB NAME: Backup 00003
JOB ACTUAL START TIME: 02/05/07 17:13:33

JOB ID: {C99DC329-9748-4031-8247-CAEECFA6FD76}
JOB NAME: Backup 00003
JOB ACTUAL START TIME: 02/05/07 17:16:58

NUMBER OF OBJECTS: 2

RETURN VALUE: 1

[Bradley_Willads]

Yann,

You can only have JobHistory_GUID or SelectionX, not both. Please remove one or the other, and let me know if that resolves your issue.

[yann_ARMAND]

Oh sorry, I send you qnthoer test script.
the correct one I tested qnd doesn't work is :

JOB_TYPE=Restore
JOB_NAME=test-BEMCMD-O90-6

RESTORE_SECURITY=YES
RESTORE_PRESERVE=1

JOBHISTORY_GUID={A3F2D591-73F5-415E-8713-DFEF26967BFD}

HOLD=YES

[Bradley_Willads]

If you use {C99DC329-9748-4031-8247-CAEECFA6FD76}, does it work?

[yann_ARMAND]

no more love with {9110D226-FD6B-4167-AE16-BAE5113A50CB}.

But I tried on another machine I updraded from v10, and it works fine.

I have the same error message if I try to create a job after emptying monitor log.
And that push me to my other post.
http://forums.symantec.com/discussions/thread.jspa?threadID=72120&tstart=15
In that particular case of log cleanning, my only way to restore is to use the date selection.

[Bradley_Willads]

Yann,

Where did {9110D226-FD6B-4167-AE16-BAE5113A50CB} come from? I didn't see that GUID posted any where in your results.

If you delete all your Job Histories, you won't be able to use that GUID to restore your data.

To use the Start/End times, you will need to use the SelectionX option.

If you weren't aware, use the -v switch with BEMCMD and it will spit out more detailed information as to what is occurring.

[yann_ARMAND]

Bradley,

sorry, it was a bad copy/paste, the ID I used was :
{C99DC329-9748-4031-8247-CAEECFA6FD76}.
Om 3 testing machines, 2 works and 1 doesn't.


thanks, I'm aware of -v flags.

About SelectionX, I succesfully used it, but when I also use START_DATE / END_DATE,
I would like to be more precise than 1 day, because I can have several backub job in one day.
This is the purpose of my other thread :
http://forums.symantec.com/discussions/thread.jspa?threadID=72120
Could we switch the discussion here ?

[Bradley_Willads]

Yann,

I'm confused now. You said that it wasn't working at all, and now you state that it's working on 2, and not the other?

On the one that isn't working, have you tried more than one job? I can't seem to reproduce the failure you're seeing, unless the job no longer exists in the database.

As for the START_DATE/END_DATE, you cannot get any more granular than that. I would suggest adding this as an enhancement to the product. You can visit http://enhancement.veritas.com/ to submit this.

[yann_ARMAND]

So do I about confusion.

I done severals test on different machine, and have very strange behaviors.

About Historical GUID it mostly works instead of the first machine we tested it.
btw, we won't use this method anymore because emptying monitor log break the stuff.

Now about SelectionX method which we have problems too, I have to make some clear testing to report you usable infos.

[yann_ARMAND]

Now really have problems with SELECTION1 usage,
opening a new thread.