Restoring 8.3 MS-DOS format filenames - Veritas Backup Exec

This is a discussion on Restoring 8.3 MS-DOS format filenames - Veritas Backup Exec ; I've noticed a problem with registery entries containing 8.3 format names that upon restoration do not necessarily match those restored as they are re-ordered/named. Specifically MS Office has components that get confused. This must be a generic problem, any ideas?...

+ Reply to Thread
Results 1 to 7 of 7

Thread: Restoring 8.3 MS-DOS format filenames

  1. Restoring 8.3 MS-DOS format filenames


    I've noticed a problem with registery entries containing 8.3 format names
    that upon restoration do not necessarily match those restored as they are
    re-ordered/named.

    Specifically MS Office has components that get confused.

    This must be a generic problem, any ideas?

  2. Re: Restoring 8.3 MS-DOS format filenames

    I have had the same thing happen with both the NT backup applet and BENT.
    This is not specific to the MS Office directory, but any long filename where
    there are multiple directories with the same 6 characters followed by the
    tilde and a digit as the DOS name. If there are a several micros~n
    directories, the restore can give the directory a different 8.3 name. The
    only solution that I have seen is to run a Find on the registry and correct
    the entries. Another solution may be to fix the DOS name on the directory,
    but I do not recall how to do that, unless you want to lose the long
    filename.

    Alex

    "Adie" wrote in message
    news:3b8f7bcc$1@hronntp01....
    >
    > I've noticed a problem with registery entries containing 8.3 format names
    > that upon restoration do not necessarily match those restored as they are
    > re-ordered/named.
    >
    > Specifically MS Office has components that get confused.
    >
    > This must be a generic problem, any ideas?




  3. Re: Restoring 8.3 MS-DOS format filenames


    What a nightmare!

    In my innocence I would expect a backup/restore product to do just that not
    put it back differently so that in this case certain products/facilities
    don't work!



  4. Re: Restoring 8.3 MS-DOS format filenames


    So you are saying that if "xxxxxx~2" already exists, for what ever reason,
    on the restore target, that BENT should go ahead and restore a backed up
    xxxxxx~2, even though it is a different long file name?

    If not that, then how is BENT supposed to handle it if not to create a new
    (sequential) xxxxxx~n short filename?

    "Adie" wrote:
    >
    >What a nightmare!
    >
    >In my innocence I would expect a backup/restore product to do just that

    not
    >put it back differently so that in this case certain products/facilities
    >don't work!
    >
    >



  5. Re: Restoring 8.3 MS-DOS format filenames

    This is not actually an issue of the backup software, it is a Microsoft
    issue of how the 8.3 name is generated. See these links from Microsoft.


    http://support.microsoft.com/support.../Q240/2/40.ASP
    http://support.microsoft.com/support.../Q176/0/14.ASP


    Microsoft has has written there SDK so that 8.3 names are not used in the
    registry going forward, so hopefully this will nat be a problem in Whistler
    & .NET.


    Microsoft Platform SDK

    Do Not Store Short File Names in the Registry, Files, or Databases
    Long file names and printer names were introduced with Windows NT and
    Windows 95. When an application creates a file or directory that has a long
    file name, the system automatically generates a corresponding alias for that
    file or directory using the standard 8.3 format. For information, see File
    Name Aliases.

    An application should never rely on an automatically generated short file
    name being the same for all copies and versions of a given file.
    Applications should not store the short file name in the registry, files, or
    databases for later use. Instead, the application should store the long file
    name, enclosed in quotes, in the registry, files, or databases.

    For example, if an application writes two files, "THIS IS A LONG NAME1.TXT"
    and "THIS IS A LONG NAME ALSO.TEXT," into the directory MyDir. The system
    generates a short file name for the first file, "THISIS~1.TXT." and
    generates a short file name for the second file "THISIS~2.TXT". The
    application then stores "THISIS~1.TXT" in the registry and deletes the files
    from MyDir. If a user later gets these two files from a backup media, but
    copies them into MyDir in the reverse order, the system generates the short
    file names "THISIS~1.TXT" for the file "THIS IS A LONG NAME ALSO.TEXT" and
    "THISIS~2.TXT" for "THIS IS A LONG NAME1.TXT." If the application reads the
    previously saved registry key, it gets the wrong file. The solution is to
    store only a long file name, enclosed by quotes, in the registry.

    For more information, see Long File Names under File Name Conventions.




    "Adie" wrote in message
    news:3b8fe930$1@hronntp01....
    >
    > What a nightmare!
    >
    > In my innocence I would expect a backup/restore product to do just that

    not
    > put it back differently so that in this case certain products/facilities
    > don't work!
    >
    >




  6. Re: Restoring 8.3 MS-DOS format filenames


    It's interesting that Microsoft break there own rules then since Professional
    2000 stores some short file names in the registery!

    Even so, I am flabbergasted that if I do a complete disaster recovery from
    a single full backup it may or may not work depending on what order the files
    are restored in.

    Obviously if individual files are restored there may be incompatibilites
    if previous versions exists etc etc. But not a disaster recovery. That must
    work. Do Veritas put in any small print that it may not work due to 8.3 filenames?

  7. Re: Restoring 8.3 MS-DOS format filenames


    I just ran into this "feature" - doing a test restore of a SQL/Server. SQL
    2000 refused to start because it STORES THE SHORT FILE NAME in the services
    portion of the registry. So Microsoft really breaks their own rules.....

    Does the latest version of BackupExec IDR fix this - we are using 8.5 at
    the moment.

    Dougal

    "Adie" wrote:
    >
    >It's interesting that Microsoft break there own rules then since Professional
    >2000 stores some short file names in the registery!
    >
    >Even so, I am flabbergasted that if I do a complete disaster recovery from
    >a single full backup it may or may not work depending on what order the

    files
    >are restored in.
    >
    >Obviously if individual files are restored there may be incompatibilites
    >if previous versions exists etc etc. But not a disaster recovery. That must
    >work. Do Veritas put in any small print that it may not work due to 8.3

    filenames?


+ Reply to Thread