Re: Moving Maxdb to a New Server

[Chris Parsons]

I think we figured it out. It looks like the problem was with the backup file itself. I assumed that since I used my login on both the old server and the new server that permissions weren't an issue, especially since the errors did not seem to indicate that. I did a chmod 777 on the backup file that I copied over to the new server and was able to restore it. At least, it is in the process of restoring, so I think it will work.


Chris Parsons wrote:
> Both servers are identical IBM P5 machines with
> Suse 9 Enterprise Server. The source server has
> MaxDB 7.5 and the destination has MaxDB 7.6.
>
> The source database "WAREHOUS" has 3 data volumes
> and 1 log volume. That is the only database we are
> trying to migrate.
>
> These are the steps I am taking:
> 1. From the source 7.5 server, backup source
> database to a file called: warehous_full
> 2. Copy warehous_full from source server to
> destination server.
> 3. Create new database on destination 7.6 server
> with default settings. Create1 large data volume
> and 1 log volume.
> 4. Create backup medium on destination and point
> to "warehous_full" backup file copied from
> source.
> 5. Try to restore.
> 6. Get error that says:
> "-24988 Sql Error ; -903,Host file I/O error,
> could not open volume"
>
> I get the same error if on the destination backup
> medium, I click the Read Label button. If I click
> the Read Label button on the source backup medium,
> the Label Information field is populated.
>
> Edit :
> I went back to see if I could just create a
> database and run a backup on the destination, and
> I couldn't even do that. I created a database
> called WAREHOUS and created a backup medium. When
> I try to run a complete backup, I get almost the
> same error:
> "-24988 Sql error ; -903,Host file I/O error,No
> more devices"
>
> So it looks like something is wrong on the
> destination side.
>
> Any ideas?
>
> Thanks
>
>
>
> Edited 2 times. Last edit at 09/26/05 03:58PM by
> Chris Parsons.