This is a multi-part message in MIME format.
------_=_NextPart_001_01C40935.CCFF7980
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hello fellows,
During last week's NetBackup 5 implementation for widows we have
discovered couple of issues which I believe haven't been posted yet with
this list. The first issue is looks like a bug to me and affects how you
specify exact object name (file name, mailbox name) during search or
specifying backup selection. The issue was discovered on both Windows
2000 and Windows 2003 platforms, but my be also present on others.
If you try to search in Backup and Recovery client GUI for exact file
name, for example "boot.ini", without specifying the full path to the
file, NetBackup client will not find that file. However if you replace
one of the characters with a wild card (*), for example " boot.in* " or
" boot* ", etc. than NetBackup client finds the file(s).=20
Similarly, specifying exact mailbox name under Exchange policy such as:
Microsoft Exchange Mailboxes:\John Doe , the backup failed. But using a
wild card in the mailbox name: Microsoft Exchange Mailboxes:\John Do* ,
backup finds the object and succeeded.=20
Its looks to me that both those issues are some how tied up to each
other, that's why I am suggesting that specifying other objects with the
exact name under NetBackup 5 could affected the backup or recovery
processes. We reported the issue to our local Veritas pre-sales engineer
and he was able to reproduce the error in his environment. Veritas
engineering team was notified. =20
Regards,
George Lavrov
glavrov AT mail DOT com
------_=_NextPart_001_01C40935.CCFF7980
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.6944.0">
<TITLE>NetBackup 5 search for a file issue</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=3D2 FACE=3D"Arial">Hello fellows,</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">During last week's NetBackup 5 =
implementation for widows we have discovered couple of issues which I =
believe haven't been posted yet with this list. The first issue is looks =
like a bug to me and affects how you specify exact object name (file =
name, mailbox name) during search or specifying backup selection. The =
issue was discovered on both Windows 2000 and Windows 2003 platforms, =
but my be also present on others.</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">If you try to search in Backup and =
Recovery client GUI for exact file name, for example =
"boot.ini", without specifying the full path to the file, =
NetBackup client will not find that file. However if you replace one of =
the characters with a wild card (*), for example " boot.in* " =
or " boot* ", etc. than NetBackup client finds the file(s). =
</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Similarly, specifying exact mailbox =
name under Exchange policy such as: Microsoft Exchange =
Mailboxes:\John Doe , the backup failed. But using a wild card in the =
mailbox name: Microsoft Exchange Mailboxes:\John Do* , backup finds the =
object and succeeded. </FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Its looks to me that both those issues =
are some how tied up to each other, that’s why I am suggesting =
that specifying other objects with the exact name under NetBackup 5 =
could affected the backup or recovery processes. We reported the issue =
to our local Veritas pre-sales engineer and he was able to reproduce the =
error in his environment. Veritas engineering team was notified. =
</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">George Lavrov</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">glavrov AT mail DOT com</FONT>
</P>
<BR>
</BODY>
</HTML>
------_=_NextPart_001_01C40935.CCFF7980--
|
