Делаю миграцию сапы 4.0 на новый сервер с целью дальнейшего обновления. У сапа указано два пути: через backup/restore, через export/import.

Исходя из этого есть вопросы:
1) Можно ли обойтись бэкапом (full offlie database+redo log), если у нас идет переход на новую версию ОС: HP-UX B11.00 (32) -> HP-UX B11.11 (64)?

2) Если не вышло 1, то можно ли поставить 4.0 на новый сервер и с помощью Remote Copy перенести манданты? Перенесутся ли настройки, абап программы?

По 1. - можно
По 2. - копирование клиента не переносит АБАПы

Which is better or faster, a client transport or a remote copy?

Before Release 4. 6, there are no differences concerning the runtime.The advantage of a client transport is that the source client is available again for users relatively soon after the export of the data, while with the remote copy, you are only allowed to work in the source client when the copy has been completed.

In addition, during the client transport you have a 'frozen' dataset of the client that can no longer be changed, and which you can access or restart again and again during the import.

Prior to Release WAS 6. 10, a client transport is more error-tolerant where there are differences in the table definitions (DDIC).Before WAS 6.10, only individual tables can be ignored in the source system if you are included in the exception list in the source system (note 70290).As of Release WAS 6.10, complete development packages (formerly development classes) can be included in an exception list.There is also a special option that prevents a termination altogether.

With parallel processes from Release 4. 6, the remote copy is faster than a client transport. Usually the entire copying time for a remote copy is in fact well below the pure export time of a client transport. However, a LAN link is required for this.With a remote copy via a WAN, you must check very critically whether the link does not slow down the copy too much.

You will find further information on client transports and remote copies in note 70547 or 557132.