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 the backup started it
would explain why you got the 71 error AND why you didn’t backup what he
created – the newly created directory wasn’t there at the time it
created the list for backup.
Have you attempted to run the backup since
the original 71 error? If the above was the issue then it should work
this time (assuming he doesn’t again change something in mid-stream).
From:
Norman_Ellis AT discovery DOT com [mailto:Norman_Ellis AT discovery DOT com]
Sent: Thursday, April 03, 2008
10:23 AM
To: Jeff Lightner
Cc: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Question
regarding (71) none of the files in the filelist exist
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 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? I sort
of put the engineer up on the stand a bit yesterday and dug into our VMWare
Virtual Center logs a little deeper and found he actually deleted the VM within
minutes after the policy started. I think this explains why NBU thought the
file was suppose to be in the original path. The backups for this ESX client
had no errors last night and the vmx file in question got backed up in the new
path.
"Jeff Lightner"
<jlightner AT water DOT com>
04/02/2008 03:50 PM
|
To
|
<Norman_Ellis AT discovery DOT com>,
<VERITAS-BU AT mailman.eng.auburn DOT edu>
|
cc
|
|
Subject
|
RE: [Veritas-bu] Question regarding (71) none
of the files in the filelist exist
|
|
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 PM
To: 'Norman_Ellis AT discovery DOT com'; VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Question regarding (71) none of the files
in the filelist exist
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 *
Leaving NOTHING to be matched by the *.vmx at the end.
However, since your selection specifies there MUST be a *.vmx
at the end the above pattern would NOT match because it is expecting it to be
AFTER the item that already has the *.vmx in its name.
Your pattern should be:
/vmfs/volumes/[a-zA-Z]*/*.vmx (that is you need to.
lose the middle * and /)
I suspect that if this was working before your
“old” path isn’t what you listed but had another subdirectory
before the file name.
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Norman_Ellis AT discovery DOT com
Sent: Wednesday, April 02, 2008 11:59 AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Question regarding (71) none of the files in
the filelist exist
We use this wild card in our backup selection /vmfs/volumes/[a-zA-Z]*/*/*.vmx
to backup just the vmx files from a single ESX host. In troubleshooting why I
received this error, I learned that between the backup window for the ESX
client, an engineer deleted the original VM (DCTZIQPVIEW02) and then
re-provisioned a new VM on a different LUN using the same server name. Anyone
have a clue as to why would I get this error? I would've thought by using the
wild card that NBU wouldn't care where the file existed from one backup to the
next of a specific file.
Old path to the file which the error 71 was generated.
/vmfs/volumes/QAVOL4/DCTZIQPVIEW02/DCTZIQPVIEW02.vmx
New path to the file where the re-provisioned VM was created.
/vmfs/volumes/QAVOL3/DCTZIQPVIEW02/DCTZIQPVIEW02.vmx
Own the landmark Planet Earth series on DVD! Find more great gifts by
shopping online at http://discoverystore.com
This e-mail, and any attachment, is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged material.
Any review, re-transmission, copying, dissemination or other use of this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and delete
the material from any computer. The contents of this message may contain
personal views which are not the views of Discovery Communications, LLC.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
information and is for the sole use of the intended recipient(s). If you are
not the intended recipient, any disclosure, copying, distribution, or use of
the contents of this information is prohibited and may be unlawful. If you have
received this electronic transmission in error, please reply immediately to the
sender that you have received the message in error, and delete it. Thank you.
----------------------------------
Own the landmark Planet Earth series on DVD!
Find more great gifts by shopping online at http://discoverystore.com
This e-mail, and any attachment, is intended only for the
person or entity to which it is addressed and may contain confidential and/or
privileged material. Any review, re-transmission, copying, dissemination or
other use of this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact the
sender and delete the material from any computer. The contents of this message
may contain personal views which are not the views of Discovery Communications,
LLC.