Host Properties for Backup Exec

The Backup Exec UNIX agent identifies itself to the Backup Exec server using a GRFS advertised name. The advertised name may not have been the same as the real machine name and path.

NetBackup must know what the advertised name is, along with the actual client name and path in order to create accurate .f file paths.

This is done by setting the GRFS Advertised Name, Actual Client, and Actual Path properties in the Backup Exec Tape Reader host proprerties. If no entries are indicated, NetBackup assumes that the advertised name is the same as the real machine name and the advertised path is the same as the real path.

The following items should be taken into consideration when importing Backup Exec media:

• It is not possible to restore UNIX data to Windows systems, Windows data to UNIX systems, Windows data to Netware systems and UNIX data to Netware systems.
• Importing from Backup Exec media does not convert or migrate Backup Exec job history, job schedules, or job descriptions to NetBackup.
• Importing from Backup Exec media does not convert Backup Exec application setup or configuration information to NetBackup.
• Intelligent Disaster Recovery (IDR) operations using the NetBackup IDR wizard and Backup Exec media is not supported. This includes both local and remote IDR restores.
• To restore media written by Backup Exec using an RSM-controlled standalone drive or robot, the media must be put in a compatible non-RSM standalone drive or a library.
• It is not possible to restore Backup Exec backups taken with the Intelligent Image Option.
• If Backup Exec hardlink backups are redirected and restored to partitions or drives other than the source partition or drive, the hardlinks are not restored, even though the progress log shows that the hardlinks were restored successfully.