Moving DB to new server - [V8.03.403D / OE 10.1B

Yahoo Archive
1
--- In vantage@yahoogroups.com, Charles Carden <ccarden@...> wrote:
>
>
> I do hope you went with a 64bit machine with plenty of memory for
you new server. I put 32GB of memory in our new server. What a
difference it made in certain areas, e.g. a full Regen of MRP went
from 8 hours to 2 hours (400% improvement).
>
>
>

Out of curiosity....

What value do you have set for # of Blocks in DB Buffer (and how much
memory is reported used by db)

I tried 240000 on my test 64 bit machine, that would load 1 GB of db
into memory and appservers refuse to start with a memory error

I lowered value to 180000 (756 MB) and the appservers start

OE10.1B SP3 HF9
2
Has anyone moved their installation of Vantage/Vista from one server
to another? And not just to a new box with the same server name.
Our existing installation is on \\FS1 and we have a new server \\APP1
just for Vantage.

So far the install of Progress and Vantage, plus a restore of our
live DB to the new server has gone smooth. But we've only tested
running vantage from the server itself, not from any clients.

Would it be better to restore \\FS1\epicor\MfgSys803\{all files &
subs} to \\APP1 (using our daily fileserver backup), or to just
retore the db (using Progress prorest.exe) and then manually copy all
the 'user files' (meaning our company as a Epicor user, not the
individual users).

So far I found that I'll need to copy:
1. Reports {\mfgSys803\Server\reports}
2. Attachments {\mfgSys803\Server\docmt}
3. BPM Code {\mfgSys803\bpm\bo}
4. Configurator Rules {\mfgSys803\Server\pcrules}
5. Alerts Code{\mfgSys803\Server\ud\alerts}
4. Configurator files {\mfgSys803\Server\ud\ProdCfg}


Anything else?

Thanks,

Calvin
3
I just did exactly that a few weeks ago. We replaced our old 32 bit server with a new 64 bit server.

I did a complete new installation of Open Edge and Vantage on the new server. I did all of the setup for the database and App servers manually on the new machine from within progress explorer. I then restored the database from the existing server to the new one. We spent a week or so testing on the new server just to ensure there were not issues. Yes, I did have to copy over the customer report folders, pcrules, etc, but that was a fairly simple process.

I actually made the change to the new server one evening after work. I did an offline backup of the database on the old server. I then renamed it and shut it down. I renamed the new server to the same name as our old one. I then modified the necessary configuration files on the server to indicate the new name. I restored the data I just backup up off the old server. I then started the database and all the appservers and we were up and going. This required approximately 30 minutes to perform. The users never knew the difference.

Since we used the same name as the old one I did not have to update any of the configuration files on the client machines.

I do hope you went with a 64bit machine with plenty of memory for you new server. I put 32GB of memory in our new server. What a difference it made in certain areas, e.g. a full Regen of MRP went from 8 hours to 2 hours (400% improvement).


From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Calvin Krusen
Sent: Tuesday, July 15, 2008 10:57 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Moving DB to new server - [V8.03.403D / OE 10.1B]


Has anyone moved their installation of Vantage/Vista from one server
to another? And not just to a new box with the same server name.
Our existing installation is on \\FS1 and we have a new server \\APP1
just for Vantage.

So far the install of Progress and Vantage, plus a restore of our
live DB to the new server has gone smooth. But we've only tested
running vantage from the server itself, not from any clients.

Would it be better to restore \\FS1\epicor\MfgSys803\{all files &
subs} to \\APP1 (using our daily fileserver backup), or to just
retore the db (using Progress prorest.exe) and then manually copy all
the 'user files' (meaning our company as a Epicor user, not the
individual users).

So far I found that I'll need to copy:
1. Reports {\mfgSys803\Server\reports}
2. Attachments {\mfgSys803\Server\docmt}
3. BPM Code {\mfgSys803\bpm\bo}
4. Configurator Rules {\mfgSys803\Server\pcrules}
5. Alerts Code{\mfgSys803\Server\ud\alerts}
4. Configurator files {\mfgSys803\Server\ud\ProdCfg}

Anything else?

Thanks,

Calvin


________________________________
DISCLAIMER:
This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.


[Non-text portions of this message have been removed]
4
Unfortunately, I can't keep the same server name, as our existing
Vantage server is also our main file server. So the new server for
vantage has to get renamed.

I was wondering what should be done on the client PCs to direct
everyone to the new server. I guess the safest thing to do is to
uninstall the 'Manufacturing Systems client' on each client and
reinstall from the new server.

What(if anything) is stored on the clients PC that would lost by
doing an unistall followed by a reinstall from a different server?

Thanks,

Calvin


--- In vantage@yahoogroups.com, Charles Carden <ccarden@...> wrote:
>
> I just did exactly that a few weeks ago. We replaced our old 32
bit server with a new 64 bit server.
>
> I did a complete new installation of Open Edge and Vantage on the
new server. I did all of the setup for the database and App servers
manually on the new machine from within progress explorer. I then
restored the database from the existing server to the new one. We
spent a week or so testing on the new server just to ensure there
were not issues. Yes, I did have to copy over the customer report
folders, pcrules, etc, but that was a fairly simple process.
>
> I actually made the change to the new server one evening after
work. I did an offline backup of the database on the old server. I
then renamed it and shut it down. I renamed the new server to the
same name as our old one. I then modified the necessary
configuration files on the server to indicate the new name. I
restored the data I just backup up off the old server. I then
started the database and all the appservers and we were up and
going. This required approximately 30 minutes to perform. The users
never knew the difference.
>
> Since we used the same name as the old one I did not have to update
any of the configuration files on the client machines.
>
> I do hope you went with a 64bit machine with plenty of memory for
you new server. I put 32GB of memory in our new server. What a
difference it made in certain areas, e.g. a full Regen of MRP went
from 8 hours to 2 hours (400% improvement).
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of Calvin Krusen
> Sent: Tuesday, July 15, 2008 10:57 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Moving DB to new server - [V8.03.403D / OE 10.1B]
>
>
> Has anyone moved their installation of Vantage/Vista from one server
> to another? And not just to a new box with the same server name.
> Our existing installation is on \\FS1 and we have a new server
\\APP1
> just for Vantage.
>
> So far the install of Progress and Vantage, plus a restore of our
> live DB to the new server has gone smooth. But we've only tested
> running vantage from the server itself, not from any clients.
>
> Would it be better to restore \\FS1\epicor\MfgSys803\{all files &
> subs} to \\APP1 (using our daily fileserver backup), or to just
> retore the db (using Progress prorest.exe) and then manually copy
all
> the 'user files' (meaning our company as a Epicor user, not the
> individual users).
>
> So far I found that I'll need to copy:
> 1. Reports {\mfgSys803\Server\reports}
> 2. Attachments {\mfgSys803\Server\docmt}
> 3. BPM Code {\mfgSys803\bpm\bo}
> 4. Configurator Rules {\mfgSys803\Server\pcrules}
> 5. Alerts Code{\mfgSys803\Server\ud\alerts}
> 4. Configurator files {\mfgSys803\Server\ud\ProdCfg}
>
> Anything else?
>
> Thanks,
>
> Calvin
>
>
> ________________________________
> DISCLAIMER:
> This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of
this e-mail is prohibited. If you have received this e-mail in error,
please notify the sender by replying to this message and delete this
e-mail immediately.
>
>
> [Non-text portions of this message have been removed]
>
5
You could probably just get away with replacing the default.mfgsys
file on the clients with the one from the new server - or at least
try on one client...

File is located at C:\Client803\Client\Config in a standard install
on the client

And \\<servername>\Epicor\Mfgsys803\Client on the server

As long as the version remained the same.

--- In vantage@yahoogroups.com, "Calvin Krusen" <ckrusen@...> wrote:
>
> Unfortunately, I can't keep the same server name, as our existing
> Vantage server is also our main file server. So the new server for
> vantage has to get renamed.
>
> I was wondering what should be done on the client PCs to direct
> everyone to the new server. I guess the safest thing to do is to
> uninstall the 'Manufacturing Systems client' on each client and
> reinstall from the new server.
>
> What(if anything) is stored on the clients PC that would lost by
> doing an unistall followed by a reinstall from a different server?
>
> Thanks,
>
> Calvin
>
>
> --- In vantage@yahoogroups.com, Charles Carden <ccarden@> wrote:
> >
> > I just did exactly that a few weeks ago. We replaced our old 32
> bit server with a new 64 bit server.
> >
> > I did a complete new installation of Open Edge and Vantage on the
> new server. I did all of the setup for the database and App
servers
> manually on the new machine from within progress explorer. I then
> restored the database from the existing server to the new one. We
> spent a week or so testing on the new server just to ensure there
> were not issues. Yes, I did have to copy over the customer report
> folders, pcrules, etc, but that was a fairly simple process.
> >
> > I actually made the change to the new server one evening after
> work. I did an offline backup of the database on the old server.
I
> then renamed it and shut it down. I renamed the new server to the
> same name as our old one. I then modified the necessary
> configuration files on the server to indicate the new name. I
> restored the data I just backup up off the old server. I then
> started the database and all the appservers and we were up and
> going. This required approximately 30 minutes to perform. The
users
> never knew the difference.
> >
> > Since we used the same name as the old one I did not have to
update
> any of the configuration files on the client machines.
> >
> > I do hope you went with a 64bit machine with plenty of memory for
> you new server. I put 32GB of memory in our new server. What a
> difference it made in certain areas, e.g. a full Regen of MRP went
> from 8 hours to 2 hours (400% improvement).
> >
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
> Behalf Of Calvin Krusen
> > Sent: Tuesday, July 15, 2008 10:57 AM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Moving DB to new server - [V8.03.403D / OE
10.1B]
> >
> >
> > Has anyone moved their installation of Vantage/Vista from one
server
> > to another? And not just to a new box with the same server name.
> > Our existing installation is on \\FS1 and we have a new server
> \\APP1
> > just for Vantage.
> >
> > So far the install of Progress and Vantage, plus a restore of our
> > live DB to the new server has gone smooth. But we've only tested
> > running vantage from the server itself, not from any clients.
> >
> > Would it be better to restore \\FS1\epicor\MfgSys803\{all files &
> > subs} to \\APP1 (using our daily fileserver backup), or to just
> > retore the db (using Progress prorest.exe) and then manually copy
> all
> > the 'user files' (meaning our company as a Epicor user, not the
> > individual users).
> >
> > So far I found that I'll need to copy:
> > 1. Reports {\mfgSys803\Server\reports}
> > 2. Attachments {\mfgSys803\Server\docmt}
> > 3. BPM Code {\mfgSys803\bpm\bo}
> > 4. Configurator Rules {\mfgSys803\Server\pcrules}
> > 5. Alerts Code{\mfgSys803\Server\ud\alerts}
> > 4. Configurator files {\mfgSys803\Server\ud\ProdCfg}
> >
> > Anything else?
> >
> > Thanks,
> >
> > Calvin
> >
> >
> > ________________________________
> > DISCLAIMER:
> > This e-mail, including attachments, may include confidential
and/or
> proprietary information, and may be used only by the person or
entity
> to which it is addressed. If the reader of this e-mail is not the
> intended recipient or his or her authorized agent, the reader is
> hereby notified that any dissemination, distribution or copying of
> this e-mail is prohibited. If you have received this e-mail in
error,
> please notify the sender by replying to this message and delete
this
> e-mail immediately.
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
6
What bw2868bond wrote below is correct. There are only two entries in the .mfgsys file that would need to be changed to point the user to the new server. The easiest method would be to copy. I most definitely would not do an uninstall and reinstall.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of bw2868bond
Sent: Wednesday, July 16, 2008 8:13 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Moving DB to new server - [V8.03.403D / OE 10.1B]


You could probably just get away with replacing the default.mfgsys
file on the clients with the one from the new server - or at least
try on one client...

File is located at C:\Client803\Client\Config in a standard install
on the client

And \\<servername>\Epicor\Mfgsys803\Client on the server

As long as the version remained the same.

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "Calvin Krusen" <ckrusen@...> wrote:
>
> Unfortunately, I can't keep the same server name, as our existing
> Vantage server is also our main file server. So the new server for
> vantage has to get renamed.
>
> I was wondering what should be done on the client PCs to direct
> everyone to the new server. I guess the safest thing to do is to
> uninstall the 'Manufacturing Systems client' on each client and
> reinstall from the new server.
>
> What(if anything) is stored on the clients PC that would lost by
> doing an unistall followed by a reinstall from a different server?
>
> Thanks,
>
> Calvin
>
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Charles Carden <ccarden@> wrote:
> >
> > I just did exactly that a few weeks ago. We replaced our old 32
> bit server with a new 64 bit server.
> >
> > I did a complete new installation of Open Edge and Vantage on the
> new server. I did all of the setup for the database and App
servers
> manually on the new machine from within progress explorer. I then
> restored the database from the existing server to the new one. We
> spent a week or so testing on the new server just to ensure there
> were not issues. Yes, I did have to copy over the customer report
> folders, pcrules, etc, but that was a fairly simple process.
> >
> > I actually made the change to the new server one evening after
> work. I did an offline backup of the database on the old server.
I
> then renamed it and shut it down. I renamed the new server to the
> same name as our old one. I then modified the necessary
> configuration files on the server to indicate the new name. I
> restored the data I just backup up off the old server. I then
> started the database and all the appservers and we were up and
> going. This required approximately 30 minutes to perform. The
users
> never knew the difference.
> >
> > Since we used the same name as the old one I did not have to
update
> any of the configuration files on the client machines.
> >
> > I do hope you went with a 64bit machine with plenty of memory for
> you new server. I put 32GB of memory in our new server. What a
> difference it made in certain areas, e.g. a full Regen of MRP went
> from 8 hours to 2 hours (400% improvement).
> >
> >
> > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On
> Behalf Of Calvin Krusen
> > Sent: Tuesday, July 15, 2008 10:57 AM
> > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Moving DB to new server - [V8.03.403D / OE
10.1B]
> >
> >
> > Has anyone moved their installation of Vantage/Vista from one
server
> > to another? And not just to a new box with the same server name.
> > Our existing installation is on \\FS1 and we have a new server
> \\APP1
> > just for Vantage.
> >
> > So far the install of Progress and Vantage, plus a restore of our
> > live DB to the new server has gone smooth. But we've only tested
> > running vantage from the server itself, not from any clients.
> >
> > Would it be better to restore \\FS1\epicor\MfgSys803\{all files &
> > subs} to \\APP1 (using our daily fileserver backup), or to just
> > retore the db (using Progress prorest.exe) and then manually copy
> all
> > the 'user files' (meaning our company as a Epicor user, not the
> > individual users).
> >
> > So far I found that I'll need to copy:
> > 1. Reports {\mfgSys803\Server\reports}
> > 2. Attachments {\mfgSys803\Server\docmt}
> > 3. BPM Code {\mfgSys803\bpm\bo}
> > 4. Configurator Rules {\mfgSys803\Server\pcrules}
> > 5. Alerts Code{\mfgSys803\Server\ud\alerts}
> > 4. Configurator files {\mfgSys803\Server\ud\ProdCfg}
> >
> > Anything else?
> >
> > Thanks,
> >
> > Calvin
> >
> >
> > ________________________________
> > DISCLAIMER:
> > This e-mail, including attachments, may include confidential
and/or
> proprietary information, and may be used only by the person or
entity
> to which it is addressed. If the reader of this e-mail is not the
> intended recipient or his or her authorized agent, the reader is
> hereby notified that any dissemination, distribution or copying of
> this e-mail is prohibited. If you have received this e-mail in
error,
> please notify the sender by replying to this message and delete
this
> e-mail immediately.
> >
> >
> > [Non-text portions of this message have been removed]
> >
>


________________________________
DISCLAIMER:
This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.


[Non-text portions of this message have been removed]