Short 8.3 file names on restore from NTBackup

[Charlie]

I had to use NT Backup on an XP machine to back up and restore a large amount
of data on a Windows 2000 SP4 server. The user data on the server was full
of files with really long names with unusual characters. Upon restore I got
the following message in the restore log for many of the files:
Warning: Unable to set the short 8.3 name for "<FILENAME>".
Reason: The parameter is incorrect.
I understand that this shouldn't be a problem as long as there are no 16 bit
programs trying to access the files. Is that correct and should I be
concerned?

Thanks.

[Wesley Vogel]

> Warning: Unable to set the short 8.3 name for "<FILENAME>".
> Reason: The parameter is incorrect.

According to David Candy...

<quote>
They are Warnings not errors. And I suspect the shortname already exists
(there is nothing that keeps short names the same in windows - windows will
change it whenever it needs to).
<quote>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Charlie > hunted and pecked:
> I had to use NT Backup on an XP machine to back up and restore a large
> amount of data on a Windows 2000 SP4 server. The user data on the server
> was full of files with really long names with unusual characters. Upon
> restore I got the following message in the restore log for many of the
> files:
> Warning: Unable to set the short 8.3 name for "<FILENAME>".
> Reason: The parameter is incorrect.
> I understand that this shouldn't be a problem as long as there are no 16
> bit programs trying to access the files. Is that correct and should I be
> concerned?
>
> Thanks.

[Ken Zhao [MSFT]]

Hello,

Thank you for using newsgroup!

Based on my research, Ntbackup in Windows 2000 does not back up short file
names when you back up files. Only way to do this is to copy the files from
one place to another. There is not programmatically way to traverse through
all files, and add the short file attribute. This has been fixed in Windows
XP and Windows 2003 Server in which we added the function
SetFileShortName(). This allows applications (in this case NTBACKUP) to
explicitly set the short name on a file. In other words, we do backup up
the 8.3 short file names.

Besides the workarounds in KB814848, you could modify the registry entries
that use the 8.3 short file names to point to the new short file names. The
following registry keys may use the 8.3 short file names:

A default instance of SQL Server
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLSERVER (value
ImagePath)
-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLSERVER\Performance
(value Library)
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLSERVERAGENT
(value ImagePath)

A named instance of SQL Server
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$instance_name
(value ImagePath)
-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$instance_name\Per
formance (value Library)
- HKEY_LOCAL_MACHINE\SYSTE

More Reference:
===============
240240: Programs Do Not Work After Restoring Computer with Backup
http://support.microsoft.com/kb/240240/en-us

814848: SQL Server 2000 may not start after you use the Windows Backup
system tool
http://support.microsoft.com/kb/814848/en-us

Hope the information can address your concern.

Thanks & Regards,

Ken Zhao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.




--------------------
| Thread-Topic: Short 8.3 file names on restore from NTBackup
| thread-index: AcbEtDD7C76LA9cfRS6R6QESwnchzA==
| X-WBNR-Posting-Host: 24.218.218.243
| From: =?Utf-8?B?Q2hhcmxpZQ==?= >
| Subject: Short 8.3 file names on restore from NTBackup
| Date: Sun, 20 Aug 2006 16:56:02 -0700
| Lines: 11
| Message-ID: >
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windowsxp.security_admin
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windowsxp.security_admin:188853
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windowsxp.security_admin
|
| I had to use NT Backup on an XP machine to back up and restore a large
amount
| of data on a Windows 2000 SP4 server. The user data on the server was
full
| of files with really long names with unusual characters. Upon restore I
got
| the following message in the restore log for many of the files:
| Warning: Unable to set the short 8.3 name for "<FILENAME>".
| Reason: The parameter is incorrect.
| I understand that this shouldn't be a problem as long as there are no 16
bit
| programs trying to access the files. Is that correct and should I be
| concerned?
|
| Thanks.
|

[Ian]

Actually, XCOPY is no better. On XCopied files, the order of the short names
may not be the same as it was originally, e.g.

Original:

Long File Name One = LONGFI~2
Long File Name Two = LONGFI~1

Copy:

Long File Name One = LONGFI~1
Long File Name Two = LONGFI~2

[Wesley Vogel]

http://www.xxcopy.com/xxcopy03.htm

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Ian > hunted and pecked:
> Actually, XCOPY is no better. On XCopied files, the order of the short
> names may not be the same as it was originally, e.g.
>
> Original:
>
> Long File Name One = LONGFI~2
> Long File Name Two = LONGFI~1
>
> Copy:
>
> Long File Name One = LONGFI~1
> Long File Name Two = LONGFI~2

[Ken Zhao [MSFT]]

Thanks Ian & Wes for your experience sharing here.

Have a nice day!

Thanks & Regards,

Ken Zhao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.





--------------------
| From: "Wesley Vogel" >
| References: >
>
>
| Subject: Re: Short 8.3 file names on restore from NTBackup
| Date: Mon, 21 Aug 2006 19:54:48 -0600
| Lines: 22
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Windows-1252"
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
| Message-ID: >
| Newsgroups: microsoft.public.windowsxp.security_admin
| NNTP-Posting-Host: c-24-9-192-96.hsd1.co.comcast.net 24.9.192.96
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFT NGP04.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windowsxp.security_admin:188951
| X-Tomcat-NG: microsoft.public.windowsxp.security_admin
|
| http://www.xxcopy.com/xxcopy03.htm
|
| --
| Hope this helps. Let us know.
|
| Wes
| MS-MVP Windows Shell/User
|
| In ,
| Ian > hunted and pecked:
| > Actually, XCOPY is no better. On XCopied files, the order of the short
| > names may not be the same as it was originally, e.g.
| >
| > Original:
| >
| > Long File Name One = LONGFI~2
| > Long File Name Two = LONGFI~1
| >
| > Copy:
| >
| > Long File Name One = LONGFI~1
| > Long File Name Two = LONGFI~2
|

[Charlie]

Sorry, I haven't gotten to this in a while.
Thanks for all the responses.

Although the file server is Windows 2000, the server that was running
NTBackup was Windows 2003 and had a mapped drive to the Windows 2000 Server
that was being backed up, so I don't know if the problem really has been
fixed in the newer version of the app.

The reason I use NTBackup for this purpose is because I have been burned by
using Robocopy or XCopy as far as "access denied" goes, including when files
are encrypted. Also, from my experience, backup apps tend to be much faster.

Thanks for the info regarding XXCopy though. I will check it out.

Regards.

""Ken Zhao [MSFT]"" wrote:

> Thanks Ian & Wes for your experience sharing here.
>
> Have a nice day!
>
> Thanks & Regards,
>
> Ken Zhao
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
>
> --------------------
> | From: "Wesley Vogel" >
> | References: >
> >
> >
> | Subject: Re: Short 8.3 file names on restore from NTBackup
> | Date: Mon, 21 Aug 2006 19:54:48 -0600
> | Lines: 22
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Windows-1252"
> | Content-Transfer-Encoding: 7bit
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
> | Message-ID: >
> | Newsgroups: microsoft.public.windowsxp.security_admin
> | NNTP-Posting-Host: c-24-9-192-96.hsd1.co.comcast.net 24.9.192.96
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFT NGP04.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.windowsxp.security_admin:188951
> | X-Tomcat-NG: microsoft.public.windowsxp.security_admin
> |
> | http://www.xxcopy.com/xxcopy03.htm
> |
> | --
> | Hope this helps. Let us know.
> |
> | Wes
> | MS-MVP Windows Shell/User
> |
> | In ,
> | Ian > hunted and pecked:
> | > Actually, XCOPY is no better. On XCopied files, the order of the short
> | > names may not be the same as it was originally, e.g.
> | >
> | > Original:
> | >
> | > Long File Name One = LONGFI~2
> | > Long File Name Two = LONGFI~1
> | >
> | > Copy:
> | >
> | > Long File Name One = LONGFI~1
> | > Long File Name Two = LONGFI~2
> |
>
>

[Ken Zhao [MSFT]]

Hello,

Thanks for your response!

I hope the information helps. If you have any other questions, feel free to
post back.

Thanks & Regards,

Ken Zhao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.





--------------------
| Thread-Topic: Short 8.3 file names on restore from NTBackup
| thread-index: AcbgEubqoYbWRHBJRh+bw+Hd0W+aNQ==
| X-WBNR-Posting-Host: 136.167.76.86
| From: =?Utf-8?B?Q2hhcmxpZQ==?= >
| References: >
>
>
>
>
| Subject: Re: Short 8.3 file names on restore from NTBackup
| Date: Sun, 24 Sep 2006 12:52:01 -0700
| Lines: 88
| Message-ID: >
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windowsxp.security_admin
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windowsxp.security_admin:190521
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windowsxp.security_admin
|
| Sorry, I haven't gotten to this in a while.
| Thanks for all the responses.
|
| Although the file server is Windows 2000, the server that was running
| NTBackup was Windows 2003 and had a mapped drive to the Windows 2000
Server
| that was being backed up, so I don't know if the problem really has been
| fixed in the newer version of the app.
|
| The reason I use NTBackup for this purpose is because I have been burned
by
| using Robocopy or XCopy as far as "access denied" goes, including when
files
| are encrypted. Also, from my experience, backup apps tend to be much
faster.
|
| Thanks for the info regarding XXCopy though. I will check it out.
|
| Regards.
|
| ""Ken Zhao [MSFT]"" wrote:
|
| > Thanks Ian & Wes for your experience sharing here.
| >
| > Have a nice day!
| >
| > Thanks & Regards,
| >
| > Ken Zhao
| >
| > Microsoft Online Partner Support
| > Get Secure! - www.microsoft.com/security
| >
| > ================================================== ===
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| > ================================================== ===
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| >
| >
| >
| >
| > --------------------
| > | From: "Wesley Vogel" >
| > | References: >
| > >
| > >
| > | Subject: Re: Short 8.3 file names on restore from NTBackup
| > | Date: Mon, 21 Aug 2006 19:54:48 -0600
| > | Lines: 22
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Windows-1252"
| > | Content-Transfer-Encoding: 7bit
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
| > | Message-ID: >
| > | Newsgroups: microsoft.public.windowsxp.security_admin
| > | NNTP-Posting-Host: c-24-9-192-96.hsd1.co.comcast.net 24.9.192.96
| > | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFT NGP04.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl
| > microsoft.public.windowsxp.security_admin:188951
| > | X-Tomcat-NG: microsoft.public.windowsxp.security_admin
| > |
| > | http://www.xxcopy.com/xxcopy03.htm
| > |
| > | --
| > | Hope this helps. Let us know.
| > |
| > | Wes
| > | MS-MVP Windows Shell/User
| > |
| > | In ,
| > | Ian > hunted and pecked:
| > | > Actually, XCOPY is no better. On XCopied files, the order of the
short
| > | > names may not be the same as it was originally, e.g.
| > | >
| > | > Original:
| > | >
| > | > Long File Name One = LONGFI~2
| > | > Long File Name Two = LONGFI~1
| > | >
| > | > Copy:
| > | >
| > | > Long File Name One = LONGFI~1
| > | > Long File Name Two = LONGFI~2
| > |
| >
| >
|