Moving 6.1 to a new server

Yahoo Archive
1
Todd,

You could name the server whatever you wanted with whatever static
IP. Then create a DNS entry that pointed "Vantage" to whatever
server you listed in DNS.

I did this a while ago on a generic load balancing (round robin)
setup on 2 terminal servers. The idea is that the clients connect
to "Vantage" and the DNS entries let you connect to whatever you
enter for "Vantage"

I would have to dig up the specifics, but it could be done through
DNS.

My 2 cents
Jeff


--- In vantage@yahoogroups.com, Todd Caughey <caugheyt@...> wrote:
>
> 6.1 has become so slow for us, especially with 1st day of month
reports like today, that I've ordered a new server. The venerable
old Xeon 550Mhz 1GB IBM Server that we started Vantage 4.0 on 7 years
ago just can't hack it anymore. Didn't get the OK for the fully V8
ready server I wanted but did get a promise if this new one can't
stand up to 8.x I can get one that can later. Ordered instead HP
DL380 G5 with Dual Quad core 2.66Ghz, 8GB, Win2k3 Enterprise and six
15K 72GB SAS disks (to RAID 1 as three volumes). Main thing lacking
was ability to expand "in the box" in future.
>
> Now the fun begins...how to move 6.1 to the new server. Loading
vantage and restoring the DB are OK but I'm looking for advice on not
having to touch all the clients. I've seen posts about version
upgrades combined with moving to a new machine but can't recall a
plain machine move. If I carefully manage the server naming (and
renaming) and the timing would it be possible to name (and re-IP) the
new server the same as the old one so that the clients don't know the
difference? There's nothing in the DB or registry when setting up
Vantage that locks in the server name when Vantage is installed, is
there?
>
> If I have to visit every client I need to reserve a lot more time
than a quick server rename & swap but I don't want to land in a
minefield for the sake of saving a weekend. Anyone else successfuly
do a name swap machine migration?
>
> Thanks,
> Todd Caughey
> Harvey Vogel Mfg. Co.
>
>
>
>
> [Non-text portions of this message have been removed]
>
2
6.1 has become so slow for us, especially with 1st day of month reports like today, that I've ordered a new server. The venerable old Xeon 550Mhz 1GB IBM Server that we started Vantage 4.0 on 7 years ago just can't hack it anymore. Didn't get the OK for the fully V8 ready server I wanted but did get a promise if this new one can't stand up to 8.x I can get one that can later. Ordered instead HP DL380 G5 with Dual Quad core 2.66Ghz, 8GB, Win2k3 Enterprise and six 15K 72GB SAS disks (to RAID 1 as three volumes). Main thing lacking was ability to expand "in the box" in future.

Now the fun begins...how to move 6.1 to the new server. Loading vantage and restoring the DB are OK but I'm looking for advice on not having to touch all the clients. I've seen posts about version upgrades combined with moving to a new machine but can't recall a plain machine move. If I carefully manage the server naming (and renaming) and the timing would it be possible to name (and re-IP) the new server the same as the old one so that the clients don't know the difference? There's nothing in the DB or registry when setting up Vantage that locks in the server name when Vantage is installed, is there?

If I have to visit every client I need to reserve a lot more time than a quick server rename & swap but I don't want to land in a minefield for the sake of saving a weekend. Anyone else successfuly do a name swap machine migration?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.




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



I am looking at a similar problem. Can you email and/or post a budget
number I could expect to pay for a similar server?



Sincerely,



Mitchell Kirby

Riten Industries, Inc.

<http://www.riten.com/> www.riten.com



740-333-8719 Direct

800-338-0027 Sales

800-338-0717 FAX

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Todd Caughey
Sent: Thursday, November 01, 2007 9:56 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Moving 6.1 to a new server



6.1 has become so slow for us, especially with 1st day of month reports like
today, that I've ordered a new server. The venerable old Xeon 550Mhz 1GB IBM
Server that we started Vantage 4.0 on 7 years ago just can't hack it
anymore. Didn't get the OK for the fully V8 ready server I wanted but did
get a promise if this new one can't stand up to 8.x I can get one that can
later. Ordered instead HP DL380 G5 with Dual Quad core 2.66Ghz, 8GB, Win2k3
Enterprise and six 15K 72GB SAS disks (to RAID 1 as three volumes). Main
thing lacking was ability to expand "in the box" in future.

Now the fun begins...how to move 6.1 to the new server. Loading vantage and
restoring the DB are OK but I'm looking for advice on not having to touch
all the clients. I've seen posts about version upgrades combined with moving
to a new machine but can't recall a plain machine move. If I carefully
manage the server naming (and renaming) and the timing would it be possible
to name (and re-IP) the new server the same as the old one so that the
clients don't know the difference? There's nothing in the DB or registry
when setting up Vantage that locks in the server name when Vantage is
installed, is there?

If I have to visit every client I need to reserve a lot more time than a
quick server rename & swap but I don't want to land in a minefield for the
sake of saving a weekend. Anyone else successfuly do a name swap machine
migration?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.

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





[Non-text portions of this message have been removed]
4
Gosh, we did this a couple of years ago, and I really
think all I had to do was to go to the workstations
and re-set the mapped drive to the new server name (we
kept both servers up and running for awhile).

Good luck.

DJ



__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
5
Todd,

I started by pointing the client to the new server and I ended up
uninstalling the old and installing the new Vantage client. In my
experience, you may or may not be able to uninstall the client, so my
recourse was to clean it from the registry (most of my users). If
cleaning the register (just want progress and vantage not listed when
you go to add-remove programs in the control panel even with admin
rights) also look for the old server name entries (not that many). I
would delete the client temporary folder c:\epicor\mfgwrk61\ as well. It
works well specially when you want a clean start. After a while, I was
doing 1 client in 5 minutes or less. If you have enough terminal server
licenses, you can move first TS and then allow users to connect
temporarily while you make the necessary changes.

Good luck!

PS - I have a dell as main server. I have 2 HPs for TS servers. The
problem with these HPs is that they are loud when temperature changes
even a few degrees...

Mario E. Aguirre - IT Manager
Lakin General Corporation, Inc.

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Todd Caughey
Sent: Thursday, November 01, 2007 9:56 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Moving 6.1 to a new server



6.1 has become so slow for us, especially with 1st day of month reports
like today, that I've ordered a new server. The venerable old Xeon
550Mhz 1GB IBM Server that we started Vantage 4.0 on 7 years ago just
can't hack it anymore. Didn't get the OK for the fully V8 ready server I
wanted but did get a promise if this new one can't stand up to 8.x I can
get one that can later. Ordered instead HP DL380 G5 with Dual Quad core
2.66Ghz, 8GB, Win2k3 Enterprise and six 15K 72GB SAS disks (to RAID 1 as
three volumes). Main thing lacking was ability to expand "in the box" in
future.

Now the fun begins...how to move 6.1 to the new server. Loading vantage
and restoring the DB are OK but I'm looking for advice on not having to
touch all the clients. I've seen posts about version upgrades combined
with moving to a new machine but can't recall a plain machine move. If I
carefully manage the server naming (and renaming) and the timing would
it be possible to name (and re-IP) the new server the same as the old
one so that the clients don't know the difference? There's nothing in
the DB or registry when setting up Vantage that locks in the server name
when Vantage is installed, is there?

If I have to visit every client I need to reserve a lot more time than a
quick server rename & swap but I don't want to land in a minefield for
the sake of saving a weekend. Anyone else successfuly do a name swap
machine migration?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.

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






[Non-text portions of this message have been removed]
6
Todd,
I have some good news!
I did exactly the process you are asking about for my great server raid
crash a little over a year ago. I set up a laptop, installed Vantage,
restored the last database backup. I removed the old Wins information and
removed the old server from the domain (NT4 Domain).
Then I renamed and reIPed the laptop to the same as the old server (I think
I might have removed the laptop from the Domain before the rename/reIP, and
then joined the domain as the new name and IP). I think I might have had to
have the clients reboot, but I did not have to touch the Vantage client for
anything else.
I also used the same process when I brought the fixed server back online.

If you don't mind me asking, why do you choose to RAID1 3 separate volumes
instead of RAID1 a system volume and then RAID10 the other 4 drives into a
single large and very fast volume for Vantage?
Aaron Hoyt
Vantage Plastics

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf Of
Todd Caughey
Sent: Thursday, November 01, 2007 10:56 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Moving 6.1 to a new server


6.1 has become so slow for us, especially with 1st day of month reports
like today, that I've ordered a new server. The venerable old Xeon 550Mhz
1GB IBM Server that we started Vantage 4.0 on 7 years ago just can't hack it
anymore. Didn't get the OK for the fully V8 ready server I wanted but did
get a promise if this new one can't stand up to 8.x I can get one that can
later. Ordered instead HP DL380 G5 with Dual Quad core 2.66Ghz, 8GB, Win2k3
Enterprise and six 15K 72GB SAS disks (to RAID 1 as three volumes). Main
thing lacking was ability to expand "in the box" in future.

Now the fun begins...how to move 6.1 to the new server. Loading vantage
and restoring the DB are OK but I'm looking for advice on not having to
touch all the clients. I've seen posts about version upgrades combined with
moving to a new machine but can't recall a plain machine move. If I
carefully manage the server naming (and renaming) and the timing would it be
possible to name (and re-IP) the new server the same as the old one so that
the clients don't know the difference? There's nothing in the DB or registry
when setting up Vantage that locks in the server name when Vantage is
installed, is there?

If I have to visit every client I need to reserve a lot more time than a
quick server rename & swap but I don't want to land in a minefield for the
sake of saving a weekend. Anyone else successfuly do a name swap machine
migration?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.

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






[Non-text portions of this message have been removed]
7
Want to do the same thing around XMAS time. Now I haven't even started
a game plan yet but here are some of my thoughts.

1 If you are going to drop the old server off the network then all you
would need to do is do a final full backup of the entire server. Take
it off line remove it from the domain. Name the new server the same
name as the old server and add it back into the domain. Restore the
database and all should be good. As long as the new server has the
same name, same directory structure and shares as the old folder the
clients won't know the difference.

2 If your like me where our current Vantage server is also our file
and print server then there are more issues to deal with like..
The new server will have a new name and IP address. Since you have to
input a server name and IP address (if you don't click the Use DNS
check box) the clients will need to be changed. Now I don't know if
this can be don with a script or Active Directory Group Policy
hopefully it can otherwise you have to touch every client to make the
changes. I'm guessing the easiest way would be just to run the client
install program over the top of the existing program and input the new
server.
You would also have to change the map drive but that can be done with
a log on script.
Does anyone know how reports would be affected by a new server?

-- In vantage@yahoogroups.com, Todd Caughey <caugheyt@...> wrote:
>
> 6.1 has become so slow for us, especially with 1st day of month
reports like today, that I've ordered a new server. The venerable old
Xeon 550Mhz 1GB IBM Server that we started Vantage 4.0 on 7 years ago
just can't hack it anymore. Didn't get the OK for the fully V8 ready
server I wanted but did get a promise if this new one can't stand up
to 8.x I can get one that can later. Ordered instead HP DL380 G5 with
Dual Quad core 2.66Ghz, 8GB, Win2k3 Enterprise and six 15K 72GB SAS
disks (to RAID 1 as three volumes). Main thing lacking was ability to
expand "in the box" in future.
>
> Now the fun begins...how to move 6.1 to the new server. Loading
vantage and restoring the DB are OK but I'm looking for advice on not
having to touch all the clients. I've seen posts about version
upgrades combined with moving to a new machine but can't recall a
plain machine move. If I carefully manage the server naming (and
renaming) and the timing would it be possible to name (and re-IP) the
new server the same as the old one so that the clients don't know the
difference? There's nothing in the DB or registry when setting up
Vantage that locks in the server name when Vantage is installed, is there?
>
> If I have to visit every client I need to reserve a lot more time
than a quick server rename & swap but I don't want to land in a
minefield for the sake of saving a weekend. Anyone else successfuly
do a name swap machine migration?
>
> Thanks,
> Todd Caughey
> Harvey Vogel Mfg. Co.
>
>
>
>
> [Non-text portions of this message have been removed]
>
8
Great. The less I have to touch the clients the better...and their PCs too. ;)

I mis-spoke on the disks. Two volumes RAID 1. The other two disks are warm spares and/or work space. I need to see if one disk can act as failover spare for either of the other two volumes....then I can have one for stuff like snapshot backups or anything else I want actually on the same server bus for speed. Maybe even get CorVu configured correctly.

-Todd C.

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Aaron Hoyt
Sent: Thursday, November 01, 2007 2:56 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Moving 6.1 to a new server


Todd,
I have some good news!
I did exactly the process you are asking about for my great server raid
crash a little over a year ago. I set up a laptop, installed Vantage,
restored the last database backup. I removed the old Wins information and
removed the old server from the domain (NT4 Domain).
Then I renamed and reIPed the laptop to the same as the old server (I think
I might have removed the laptop from the Domain before the rename/reIP, and
then joined the domain as the new name and IP). I think I might have had to
have the clients reboot, but I did not have to touch the Vantage client for
anything else.
I also used the same process when I brought the fixed server back online.

If you don't mind me asking, why do you choose to RAID1 3 separate volumes
instead of RAID1 a system volume and then RAID10 the other 4 drives into a
single large and very fast volume for Vantage?
Aaron Hoyt
Vantage Plastics

-----Original Message-----
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>]On Behalf Of
Todd Caughey
Sent: Thursday, November 01, 2007 10:56 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Moving 6.1 to a new server

6.1 has become so slow for us, especially with 1st day of month reports
like today, that I've ordered a new server. The venerable old Xeon 550Mhz
1GB IBM Server that we started Vantage 4.0 on 7 years ago just can't hack it
anymore. Didn't get the OK for the fully V8 ready server I wanted but did
get a promise if this new one can't stand up to 8.x I can get one that can
later. Ordered instead HP DL380 G5 with Dual Quad core 2.66Ghz, 8GB, Win2k3
Enterprise and six 15K 72GB SAS disks (to RAID 1 as three volumes). Main
thing lacking was ability to expand "in the box" in future.

Now the fun begins...how to move 6.1 to the new server. Loading vantage
and restoring the DB are OK but I'm looking for advice on not having to
touch all the clients. I've seen posts about version upgrades combined with
moving to a new machine but can't recall a plain machine move. If I
carefully manage the server naming (and renaming) and the timing would it be
possible to name (and re-IP) the new server the same as the old one so that
the clients don't know the difference? There's nothing in the DB or registry
when setting up Vantage that locks in the server name when Vantage is
installed, is there?

If I have to visit every client I need to reserve a lot more time than a
quick server rename & swap but I don't want to land in a minefield for the
sake of saving a weekend. Anyone else successfuly do a name swap machine
migration?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.

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

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





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