Re: How can I backup my virtual hostname on a W2k3 cluster on a private VLAN??
From: SA (nospam_at_nospam.nospam)
Date: 07/14/04
- Next message: Morten: "Re: Split brain scenario in cluster server system"
- Previous message: Jason Nash [MSFT]: "Re: Split brain scenario in cluster server system"
- In reply to: Jason Nash [MSFT]: "Re: How can I backup my virtual hostname on a W2k3 cluster on a private VLAN??"
- Next in thread: Matthew Walker [MSFT]: "Re: How can I backup my virtual hostname on a W2k3 cluster on a private VLAN??"
- Reply: Matthew Walker [MSFT]: "Re: How can I backup my virtual hostname on a W2k3 cluster on a private VLAN??"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 14 Jul 2004 10:59:54 -0400
Jason,
Thanks for the effort. Here it is:
00000714.00000260::2004/07/14-08:49:09.785 INFO [NM] Started failure
isolation timer (60000ms) for network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f
(Netbackup)
00000714.00000260::2004/07/14-08:49:09.785 INFO [NM] Connectivity failure
scope determination complete for network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.00000260::2004/07/14-08:49:09.785 INFO [NM] Worker thread finished
processing network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.0000026c::2004/07/14-08:50:12.269 INFO [NM] Failure isolation timer
expired for network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f (Netbackup).
00000714.0000026c::2004/07/14-08:50:12.269 INFO [NM] Scheduled worker thread
to service network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Worker thread
processing network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Beginning phase 1 of
state computation for network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Examining connectivity
data for interface 0 (d0123a96-d5db-44e5-807d-c477d282e40d) on network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Interface 1 reports
interface 0 is unreachable on network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Interface 0
(d0123a96-d5db-44e5-807d-c477d282e40d) is unreachable on network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Examining connectivity
data for interface 1 (d5eee5db-b1d0-42d6-966c-60cc013cdddc) on network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Interface 0 reports
interface 1 is unreachable on network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Interface 1
(d5eee5db-b1d0-42d6-966c-60cc013cdddc) is unreachable on network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Completed phase 1 of
state computation for network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Unavailable=0, Failed =
0, Unreachable=2, Reachable=0, Up=0 on network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Trying to determine
scope of connectivity failure for 2 interfaces on network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Unreachable interface 1
= d0123a96-d5db-44e5-807d-c477d282e40d on network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f
00000714.00000260::2004/07/14-08:50:12.269 INFO [NM] Unreachable interface 2
= d5eee5db-b1d0-42d6-966c-60cc013cdddc on network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f
00000714.00000260::2004/07/14-08:50:12.331 INFO [NM] Found address
192.168.2.3 for interface d0123a96-d5db-44e5-807d-c477d282e40d.
00000714.00000260::2004/07/14-08:50:12.331 INFO [NM] Online enum for
interface d0123a96-d5db-44e5-807d-c477d282e40d contains 1 addresses
00000714.00000260::2004/07/14-08:50:12.394 INFO [NM] Online enum for
interface d5eee5db-b1d0-42d6-966c-60cc013cdddc contains 1 addresses
00000714.00000260::2004/07/14-08:50:12.394 INFO [NM] Total online address
count for network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f is 2
00000714.00000260::2004/07/14-08:50:12.394 INFO [NM] Ping enum for interface
d0123a96-d5db-44e5-807d-c477d282e40d contains 0 addresses
00000714.00000260::2004/07/14-08:50:12.394 INFO [NM] Ping enum for interface
d5eee5db-b1d0-42d6-966c-60cc013cdddc contains 0 addresses
00000714.00000260::2004/07/14-08:50:12.394 INFO [NM] Total ping address
count for network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f is 0
00000714.00000260::2004/07/14-08:50:12.410 WARN [NM] Network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f state is indeterminate, Scheduling
Failure Isolation poll
00000714.00000260::2004/07/14-08:50:12.410 WARN [NM] Failed to read
IsolationPollTimerValue or value out of range,status 2 using default 60000
ms
00000714.00000260::2004/07/14-08:50:12.410 INFO [NM] Started failure
isolation timer (60000ms) for network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f
(Netbackup)
00000714.00000260::2004/07/14-08:50:12.410 INFO [NM] Connectivity failure
scope determination complete for network
70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.00000260::2004/07/14-08:50:12.410 INFO [NM] Worker thread finished
processing network 70f5fb12-6adc-45eb-b398-1b6b083b8a8f.
00000714.0000014c::2004/07/14-08:51:13.206 INFO [Qfs] GetDiskFreeSpaceEx
Q:\MSCS\, status 0
-SA.
"Jason Nash [MSFT]" <jasnas@online.microsoft.com> wrote in message
news:40f543c3$1@news.microsoft.com...
> IP addresses should never depend on a physical disk. In fact, IP address
> should not depend on anything, but that isn't likely causing the failure.
>
> If you can, try to bring the IP address online. Immediately after it
fails,
> open the cluster.log in the %systemroot%\cluster folder. Search from the
> bottom to the top for the friendly name of the IP address. You should see
> the failure. Grab that information and some of the preceding and trailing
> entries around the failure event and post in the newsgroup. We will try
to
> determine why the IP is failing.
>
> --
>
> Jason Nash [MSFT]
> **Please do not send e-mail directly to this alias. This alias is for
> newsgroup purposes only***
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> http://www.microsoft.com/info/cpyright.htm
>
>
>
> "SA" <nospam@nospam.nospam> wrote in message
> news:O2bM3haaEHA.2488@tk2msftngp13.phx.gbl...
> > Matthew,
> > Thats exactly what I tried. But the second IP resource on the private
> > VLAN
> > does not come online and eventually comes up failed.
> >
> > I created the second virtual IP and the only dependency I had it set on
> > was
> > the physical disk in the group. What am I doing wrong?
> >
> > -SA.
> >
> >
> > "Matthew Walker [MSFT]" <mwalker@online.microsoft.com> wrote in message
> > news:40f466af@news.microsoft.com...
> >> Another possibility is to add an additional IP resource in the group
that
> > is
> >> on the backup network. As long as the cluster service recognizes the
> >> network and can bind the IP we can have a single name bound to 2 IPs.
> >>
> >> Matthew [MSFT]
> >> --
> >> **Please do not send e-mail directly to this alias. This alias is for
> >> newsgroup purposes only***
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >> http://www.microsoft.com/info/cpyright.htm
> >>
> >>
> >> --
> >> **Please do not send e-mail directly to this alias. This alias is for
> >> newsgroup purposes only***
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >> http://www.microsoft.com/info/cpyright.htm
> >>
> >> "Jason [MSFT]" <jasnas@online.microsoft.com> wrote in message
> >> news:40f45980$1@news.microsoft.com...
> >> > If you cannot access the Virtual Server's IP address then you aren't
> >> > not
> >> > going to be able to backup using the Virtual Server connection. The
> > only
> >> > way would be to backup via the node name that has ownership of the
> >> > resources. This is not optimal, but is better than no backup at all!
> >> >
> >> > --
> >> >
> >> >
> >> > Jason [MSFT]
> >> > **Please do not send e-mail directly to this alias. This alias is for
> >> > newsgroup purposes only***
> >> > This posting is provided "AS IS" with no warranties, and confers no
> >> > rights. http://www.microsoft.com/info/cpyright.htm
> >> >
> >> >
> >> >
> >> > "SA" <nospam@nospam.nospam> wrote in message
> >> > news:%23N8RfaQaEHA.2520@TK2MSFTNGP12.phx.gbl...
> >> >> Hi all,
> >> >> I want to backup my cluster using Veritas Netbackup. I have a
> > dedicated
> >> >> private VLAN setup for all my backups. The problem here is that I
> > setup
> >> >> a
> >> >> private IP on a separate network interface for my local nodes but I
am
> >> >> stumped as to what to do for my virtual servers. I mean the virtual
> > IP's
> >> >> are not visible on the private VLAN, so how would netbackup resolve
> > this?
> >> >>
> >> >> Please let me know if I am not explaining myself well enough and
> >> >> thanks
> >> >> for
> >> >> all the help.
> >> >>
> >> >> Thanks,
> >> >> -SA.
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>
- Next message: Morten: "Re: Split brain scenario in cluster server system"
- Previous message: Jason Nash [MSFT]: "Re: Split brain scenario in cluster server system"
- In reply to: Jason Nash [MSFT]: "Re: How can I backup my virtual hostname on a W2k3 cluster on a private VLAN??"
- Next in thread: Matthew Walker [MSFT]: "Re: How can I backup my virtual hostname on a W2k3 cluster on a private VLAN??"
- Reply: Matthew Walker [MSFT]: "Re: How can I backup my virtual hostname on a W2k3 cluster on a private VLAN??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
