Jeff,
No worries man. I have the same problem from time to time without
a drink ;-) I do appreciate your reply! I new it was right because all the
other 493 vmx files had backed up without error. I have to admit I'm a
newbee to NBU. I'm way more comfortable with Legato. That said, does
If I understand your question the answer is yes.
That is to say that NBU builds the list of files to backup at the
beginning of the backup. If you change something after the backup has
started it isn't unusual to see an error. Since you say the engineer
admitted to making the change after
Thanks Jeff, I figured NBU created some kind of file list before
execution. Yes, the scheduled backup last night worked fine and the file
was backed up in the new location.
Jeff Lightner [EMAIL PROTECTED]
04/03/2008 11:05 AM
To
[EMAIL PROTECTED]
cc
VERITAS-BU@mailman.eng.auburn.edu
On Thu, Apr 03, 2008 at 10:23:21AM -0400, [EMAIL PROTECTED] wrote:
That said, does NBU
create a file list it keeps in memory on the client, media or master
server of the files it knows it needs to backup before actually executing
the backup?
It has the list of backup files that you pass
Your pattern shouldn't have matched the old path or the new path
/vmfs/volumes/ on both and explicit in your selection so matches the
literal.
QAVOL4/DCTZIQPVIEW02/ (old) and QAVOL3/DCTZIQPVIEW02/ (new) would match
your [a-zA-Z]*/
The DCTZIQPVIEW02.vmx at end would be matched by the *
My apologies.
It has been pointed out that I missed the first / after QAVOL3 or
QAVOL4. Your selection was correct.
Apparently I need new glasses - looked at it multiple times before
sending.
From: Jeff Lightner
Sent: Wednesday, April 02, 2008 1:50
Not sure why it missed it, but from my understanding of the include /
exclude list formats
*.vmx should be all you need in your include list to backup any .vmx
file anywhere on that system that is on a filesystem you have selected.
I use this same entry well almost in my exludes. *.dbf
This
