Forum Discussion
There's absolutely nothing wrong with your English.
Thanks for a detailed description of your issue.
My guess is that nobody here has seen or experienced this issue, mainly because hardly anyone I know is using the 'postpone' function.
I am wondering if this issue is caused by the same Java bug as per this TN:
Unable to edit backup window on calendar based schedule in Java GUI
https://www.veritas.com/support/en_US/article.000109333
- MasterBlaster7 years agoLevel 3
Hi Marianne and thanks for the feedback, valuable as always :)
I seem to recall we've already experimented that inconsistence when editing the window of a calendar based schedule with Java GUI, maybe something like a couple of years ago, just after the 7.7.2 upgrade (that was solved with the EEB if I remember well).
By the way, I opened a case in the meanwhile because the disk pools were nearly saturated: I'll update the results as soon as I have some news.
Bye!
M.
- mph9997 years agoLevel 6
You should have some news soon, as I was talking about this with the TSE who has the case.
What I would like to see, is what is happening with the NBDB, which is where the 'Deferred Duplication' setting is held.
What is neededWith the 'Postpone creation of this copy until until the source copy is about to expire' (also known as Deferred duplication) NOT set for a SLP secondary operation, save the output of:Next, set the 'Postpone creation of this copy until until the source copy is about to expire' feature and if possible grab a screen shot of this.Immediately run:nbdb_unload c:\tmp\nbdb_output_deferred_setWait the required time for the issue to occur and then run this command:nbdb_unload c:\tmp\nbdb_output_afterThis should create three dirs, with three nbdb_unloads, which will show what is hapening in the DB during the issue.
Related Content
- 8 years ago
- 12 years ago