networker migration to an existing backup server

There are several issues here:

• You must configure the same core resources - clients, workflows, (compatible) devices? etc. on the new backup server
• Then you must add the backup volumes and save sets on the new server. The only method you can use here is running "scanner" on a compatible device. This is the only way to add those to the media index. Just copying the index files will not help at all.
• You may need to purchase additional licenses. This of course depends in you licensing method.

Depending on the size of your backup server, this could result in a huge amount of work. So you need to think whether it might be better to just add the clients to the new backup server and keep the old one for recoveries as long as all those save sets will have expired.

@hend_bs, We do not yet have an option to merge the media databases from 2 different datazones. So the only option to transfer the media database information is to scan the tapes used in the old datazone, on the new datazone once you have the client instances with the same clientid created.

Hello,

Thanks for the answer.

Actually, the old backup server has only 3 clients including itself and the target has already 6 clients including itself.

we plan just to transfer the clients to the new backup server and not the library or tapes, but we need to maintain the information needed to perform recovery tasks.

so just merging the two index files, res and mm will make recoveries work?