Postoffice-startup-file not copied from SYS-volume

Question

We migrated a Groupwise 7.02-postoffice from a Netware 6.5-Sp5-server to a
SLES10-SP1-server with the Novell GroupWise Migration Utility.
When we started gwpoa the postoffice-startup-file was not
in /opt/novell/groupwise/agenst/share/
We looked in the migration-logfile and we saw these messages
10/27/07 02:32:23 Configuring agent(s)...
10/27/07 02:32:23 Running remote command:
sh /tmp/groupwise/software/addagent.sh -
b /opt/novell/groupwise/agents/bin/gwpoa -
s /tmp/groupwise/software/p006.poa -h /var/opt/novell/groupwise/mail/p006 -
v 7
/tmp/groupwise/software/addagent.sh: line
135: /tmp/groupwise/software/p006.poa: No such file or directory
mv: cannot stat `/tmp/p006.poa.tmp.16849': No such file or
directory
cp: cannot stat `/tmp/groupwise/software/p006.poa': No such file
or directory
10/27/07 02:32:25 Remote command failed (1)
This is were our sourcefiles were:
Post Office:
Source database path: \\fileserver\VOL1\DATA\GRPWISE\P006\
Destination path: /var/opt/novell/groupwise/mail/p006
Agents:
Post Office Agent:
Path to startup file: \\fileserver\SYS\SYSTEM\p006.poa
As you see, our startup-file was on another volume then the postoffice.
In the migration-log we only saw a mount of the postoffice-volume, so we
think there is a bug in the migration utility. It does not copy the
startup-file if it is on another volume (in this case on the SYS-volume).
Or did we something wrong?
At last we solved our problem by copying (and editing) a startup-file
to /opt/novell/groupwise/agenst/share/
Regards,
Jeroen van der Klaauw

Answer 1

It happens between the full dbcopy and the incremental dbcopy, when the
agent is configured.
Jeroen van der Klaauw
> When the migration agent finishes the migration of the data there are
> the second and third phases that the application runs through - 2) to
> install the agents and 3) configure them. If you bombed out before
> that third phase then I would understand...
>
>
>
> On Mon, 29 Oct 2007 15:55:53 GMT, [email protected] wrote:
>
> >We migrated a Groupwise 7.02-postoffice from a Netware 6.5-Sp5-server
to a
> >SLES10-SP1-server with the Novell GroupWise Migration Utility.
> >When we started gwpoa the postoffice-startup-file was not
> >in /opt/novell/groupwise/agenst/share/
> >We looked in the migration-logfile and we saw these messages
> >
> >10/27/07 02:32:23 Configuring agent(s)...
> >10/27/07 02:32:23 Running remote command:
> >sh /tmp/groupwise/software/addagent.sh -
> >b /opt/novell/groupwise/agents/bin/gwpoa -
> >s /tmp/groupwise/software/p006.poa -
h /var/opt/novell/groupwise/mail/p006 -
> >v 7
> > /tmp/groupwise/software/addagent.sh: line
> >135: /tmp/groupwise/software/p006.poa: No such file or directory
> > mv: cannot stat `/tmp/p006.poa.tmp.16849': No such file or
> >directory
> > cp: cannot stat `/tmp/groupwise/software/p006.poa': No such file
> >or directory
> >10/27/07 02:32:25 Remote command failed (1)
> >
> >This is were our sourcefiles were:
> >
> >Post Office:
> > Source database path: \\fileserver\VOL1\DATA\GRPWISE\P006\
> > Destination path: /var/opt/novell/groupwise/mail/p006
> >
> >Agents:
> > Post Office Agent:
> > Path to startup file: \\fileserver\SYS\SYSTEM\p006.poa
> >
> >As you see, our startup-file was on another volume then the postoffice.
> >In the migration-log we only saw a mount of the postoffice-volume, so
we
> >think there is a bug in the migration utility. It does not copy the
> >startup-file if it is on another volume (in this case on the SYS-
volume).
> >Or did we something wrong?
> >
> >
> >At last we solved our problem by copying (and editing) a startup-file
> >to /opt/novell/groupwise/agenst/share/
> >
> >Regards,
> >
> >Jeroen van der Klaauw
> Tim
> ___________________
> Tim Heywood (SYSOP)
> NDS8
> Scotland
> (God's Country)
> www.nds8.co.uk
> ___________________
>
> In theory, practice and theory are the same
> In Practice, they are different