Differences Between Importing, Browsing and Restoring Backup Exec and NetBackup Images

There are some differences between Backup Exec and NetBackup when importing, browsing, and restoring images:

Importing and Restoring QIC Media

To import and restore Backup Exec Quarter Inch Cartridge (QIC) media written with tape block sizes more than 512 bytes, you must use a NetBackup Windows media server. A NetBackup UNIX media server will not work to import and restore the media in this case.

Spanned Media: Importing Differences

When importing a Backup Exec backup which spans multiple media, run a Phase 1 import on the first media of the spanned backup set. Then, run a Phase 1 import on the remaining media of the spanned backup set in any order.

This differs from the NetBackup process, where Phase1 import 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 for restoring, the directory where that file is located will also get restored.

When a user selects a NetBackup file for restoring, only that single file is restored.

NetWare: Restoring Differences

NetBackup will not support restoring Backup Exec Netware non-SMS backups 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.

NTFS Hard Links, NTFS SIS Files, and Exchange SIS Mail Messages: Restoring

• When restoring Backup Exec NTFS images, any backed up directory with the name SIS Common Store will be restored, whether or not it is the actual NTFS single instance storage common store directory. This occurs even though the file was not specifically selected for restore.
• When restoring objects from backups which contain NTFS hardlinks, NTFS SIS files or Exchange SIS mail messages, additional objects, which the user did not select for restore, may be sent to to the client. These additional objects will be skipped by the client and not restored. Although the objects which the user selected for restore are restored, the job is considered partially successful because some objects (though not selected by the user), were skipped.
• When redirecting NTFS hard links, NTFS SIS files or Exchange SIS mailboxes for restore:
• All or some of the files should be redirected to any location on the source drive, or
• all files should be redirected 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, some or all of 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.