H
Hank Arnold
I have a situation that I need to work around. I'm not completely up all the
specific technical details on how it's currently being done, so bear with
me...
We have a server that has a bunch of shares. They are all pointing to sub
folders of one folder called USERDATA (shared as USERDATA on the server). Of
course, I can map a network drive to these shares by using
\\servername\ShareName
A couple of years ago, we set up (with the help of a vendor) a second server
and assigned it as a High Availability "standby" server using software
called LifeKeeper (similar to Double Take). The software monitors a
"heartbeat" over a crossover cable and if it detects that the other server
has gone off line, it does a whole bunch of stuff and brings the "standby"
server up as the primary and restores access without any apparent change to
the users (other than a temp loss of connectivity).
This failover had to include the shares I was mentioning. What was done was
we set up a LANMAN name in DNS called USERFILES and assigned it an IP
address. Then the software was set up to create a resource that essentially
created a "global" share called "USERFILES" and assigned the local share
(USERDATA), drive and IP address to it. This allows the shares to be
accessed via
\\USERFILES\ShareName
When the system fails over, it moves and activates the resource on the
standby server before it brings it online, thus allowing the drive mappings
to work w/o impacting the clients.
My problem (finally!) is that I need to break this HA cluster and leave the
primary as a standalone server. Unfortunately, this means removing the
software that is creating the share I need. What I need it a way to create a
way for the
\\USERFILES\ShareName
to continue work on the server without the vendor software. It might be
obvious, but how can I do this??
specific technical details on how it's currently being done, so bear with
me...
We have a server that has a bunch of shares. They are all pointing to sub
folders of one folder called USERDATA (shared as USERDATA on the server). Of
course, I can map a network drive to these shares by using
\\servername\ShareName
A couple of years ago, we set up (with the help of a vendor) a second server
and assigned it as a High Availability "standby" server using software
called LifeKeeper (similar to Double Take). The software monitors a
"heartbeat" over a crossover cable and if it detects that the other server
has gone off line, it does a whole bunch of stuff and brings the "standby"
server up as the primary and restores access without any apparent change to
the users (other than a temp loss of connectivity).
This failover had to include the shares I was mentioning. What was done was
we set up a LANMAN name in DNS called USERFILES and assigned it an IP
address. Then the software was set up to create a resource that essentially
created a "global" share called "USERFILES" and assigned the local share
(USERDATA), drive and IP address to it. This allows the shares to be
accessed via
\\USERFILES\ShareName
When the system fails over, it moves and activates the resource on the
standby server before it brings it online, thus allowing the drive mappings
to work w/o impacting the clients.
My problem (finally!) is that I need to break this HA cluster and leave the
primary as a standalone server. Unfortunately, this means removing the
software that is creating the share I need. What I need it a way to create a
way for the
\\USERFILES\ShareName
to continue work on the server without the vendor software. It might be
obvious, but how can I do this??