The following topics describe differences between Backup Exec and NetBackup when importing, browsing, and restoring images:

• Run vmphyinv for Backup Exec media

  To import Backup Exec media requires vmphyinv to update the Backup Exec media GUID in the NetBackup Media Manager database. Create the media IDs in the NetBackup Media Manager database, run the command, then perform Phase I and Phase II import operations.

• To import and restore QIC media

  Backup Exec Quarter Inch Cartridge (QIC) media that was written in tape block sizes more than 512 bytes must be imported and restored using a NetBackup Windows media server. A NetBackup UNIX media server cannot import and restore the media in this case.

• Spanned media: Importing differences

  To import a Backup Exec backup that spans multiple media, run a Phase I import on the first media of the spanned backup set. Then, run a Phase I import on the remaining media of the spanned backup set in any order.

  The Backup Exec import process differs from the NetBackup import process. In that NetBackup import process, Phase I can be run in any order in case the image spans multiple media.

• SQL: Browsing and restoring differences

  Backup Exec SQL images are browsed, then restored using the NetBackup Backup, Archive, and Restore client interface.

  NetBackup SQL images are browsed, then restored using the NetBackup SQL interface.

• File level objects: Browsing and restoring differences

  When a user selects a Backup Exec file to restore, the directory where that file is located is restored.

  When a user selects a NetBackup file to restore, only the single file is restored.

• NetWare: Restoring differences

  NetBackup does not support restoring Backup Exec NetWare non-SMS backups that were created using the NetWare redirector.

  Storage Management Services (SMS) software allows data to be stored and retrieved on NetWare servers independent of the file system the data is maintained in.

• Restoring NTFS hard links, NTFS SIS files, and Exchange SIS mail messages

  • When Backup Exec NTFS images are restored, any directory named SIS Common Store is restored. The directory named SIS Common Store is restored whether or not it is the actual NTFS single instance storage common store directory. The directory is restored even if the file was not specifically selected for restore.

  • Under some circumstances, additional objects are sent to the client, even though the objects were not selected for restore. The items are sent to the client when objects are restored from any backups that contain NTFS hard links, NTFS SIS files, or Exchange SIS mail messages. These additional objects are skipped by the client and are not restored. The job is considered partially successful because some objects (though not selected by the user), are skipped.

  • When NTFS hard links or SIS files, or Exchange SIS mailboxes are redirected for restore, all or some of the files should be redirected to any location on the source drive. Or, you also can redirect all files to a single location on a different drive.

    For example, if the following hard link or SIS files are backed up:

    C:\hard_links\one.txt
    C:\hard_links\two.txt
    C:\hard_links\three.txt
    

    Upon restore, either the files can be redirected to any location on C:\, or all the files must be redirected to a different drive.

    The following combination would be unsuccessful:

    C:\hard_links\one.txt to a location on C:\

    C:\hard_links\two.txt to a location on D:\

    If all the files are to be redirected to a different drive, specify that C:\ be replaced with D:\in the redirection paths.

    Unsuccessful:

    The redirection paths specify that C:\hard_links be replaced with D:\hard_links.

    Successful:

    The redirection paths specify that C:\hard_links be replaced with C:\redir_hard_links.