There is currently no way to set a maximum size on the log but stopping and
restarting the VEA service (via Control Panel > Services or "net stop vxob",
"net start vxob" will reset the log.

KM


"Davide" wrote in message
news:3e676790$1@hronntp01....
>
> Hello,
> I found out my vxisys.log is filling up my C: drive. How can I reduce its
> size???
>
> Thanks
> Davide

If I stop the VEA service do I loose connection to the disks?
Thanks!!
Davide

"KM" wrote:
>There is currently no way to set a maximum size on the log but stopping
and
>restarting the VEA service (via Control Panel > Services or "net stop vxob",
>"net start vxob" will reset the log.
>
>KM
>
>
>"Davide" wrote in message
>news:3e676790$1@hronntp01....
>>
>> Hello,
>> I found out my vxisys.log is filling up my C: drive. How can I reduce
its
>> size???
>>
>> Thanks
>> Davide
>
>

No, it won't affect access to any disks or volumes.


KM


"Davide" wrote in message
news:3e685a33$1@hronntp01....
>
> If I stop the VEA service do I loose connection to the disks?
> Thanks!!
> Davide
>
> "KM" wrote:
> >There is currently no way to set a maximum size on the log but stopping
> and
> >restarting the VEA service (via Control Panel > Services or "net stop
vxob",
> >"net start vxob" will reset the log.
> >
> >KM
> >
> >
> >"Davide" wrote in message
> >news:3e676790$1@hronntp01....
> >>
> >> Hello,
> >> I found out my vxisys.log is filling up my C: drive. How can I reduce
> its
> >> size???
> >>
> >> Thanks
> >> Davide
> >
> >
>

Hi Davide

Tjeck the value of:

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentV ersion\Tracing\vxisis

If you set it to 6, it should reduce your logging.

I have the same problem with the logfile, and i'm waiting for a solution.

KM wrote:
> No, it won't affect access to any disks or volumes.
>
>
> KM
>
>
> "Davide" wrote in message
> news:3e685a33$1@hronntp01....
>
>>If I stop the VEA service do I loose connection to the disks?
>>Thanks!!
>>Davide
>>
>>"KM" wrote:
>>
>>>There is currently no way to set a maximum size on the log but stopping
>>
>>and
>>
>>>restarting the VEA service (via Control Panel > Services or "net stop
>>
> vxob",
>
>>>"net start vxob" will reset the log.
>>>
>>>KM
>>>
>>>
>>>"Davide" wrote in message
>>>news:3e676790$1@hronntp01....
>>>
>>>>Hello,
>>>>I found out my vxisys.log is filling up my C: drive. How can I reduce
>>>
>>its
>>
>>>>size???
>>>>
>>>>Thanks
>>>>Davide
>>>
>>>
>
>

Yes, it does!!
On our test environment it caused the failover of all disks to the second
node!

"KM" wrote:
>No, it won't affect access to any disks or volumes.
>
>
>KM
>
>
>"Davide" wrote in message
>news:3e685a33$1@hronntp01....
>>
>> If I stop the VEA service do I loose connection to the disks?
>> Thanks!!
>> Davide
>>
>> "KM" wrote:
>> >There is currently no way to set a maximum size on the log but stopping
>> and
>> >restarting the VEA service (via Control Panel > Services or "net stop
>vxob",
>> >"net start vxob" will reset the log.
>> >
>> >KM
>> >
>> >
>> >"Davide" wrote in message
>> >news:3e676790$1@hronntp01....
>> >>
>> >> Hello,
>> >> I found out my vxisys.log is filling up my C: drive. How can I reduce
>> its
>> >> size???
>> >>
>> >> Thanks
>> >> Davide
>> >
>> >
>>
>
>

If you aren't using clustering then it won't affect access to the disks or
volumes. Vxob is responsible for dynamic disk group resources so if it does
not reply to MSCS during a monitoring cycle then the resource will fail.

KM


"Davide" wrote in message
news:3e706186$1@hronntp01....
>
> Yes, it does!!
> On our test environment it caused the failover of all disks to the second
> node!
>
> "KM" wrote:
> >No, it won't affect access to any disks or volumes.
> >
> >
> >KM
> >
> >
> >"Davide" wrote in message
> >news:3e685a33$1@hronntp01....
> >>
> >> If I stop the VEA service do I loose connection to the disks?
> >> Thanks!!
> >> Davide
> >>
> >> "KM" wrote:
> >> >There is currently no way to set a maximum size on the log but
stopping
> >> and
> >> >restarting the VEA service (via Control Panel > Services or "net stop
> >vxob",
> >> >"net start vxob" will reset the log.
> >> >
> >> >KM
> >> >
> >> >
> >> >"Davide" wrote in message
> >> >news:3e676790$1@hronntp01....
> >> >>
> >> >> Hello,
> >> >> I found out my vxisys.log is filling up my C: drive. How can I
reduce
> >> its
> >> >> size???
> >> >>
> >> >> Thanks
> >> >> Davide
> >> >
> >> >
> >>
> >
> >
>

Is'nt that a bug?

KM wrote:
> If you aren't using clustering then it won't affect access to the disks or
> volumes. Vxob is responsible for dynamic disk group resources so if it does
> not reply to MSCS during a monitoring cycle then the resource will fail.
>
> KM
>
>
> "Davide" wrote in message
> news:3e706186$1@hronntp01....
>
>>Yes, it does!!
>>On our test environment it caused the failover of all disks to the second
>>node!
>>
>>"KM" wrote:
>>
>>>No, it won't affect access to any disks or volumes.
>>>
>>>
>>>KM
>>>
>>>
>>>"Davide" wrote in message
>>>news:3e685a33$1@hronntp01....
>>>
>>>>If I stop the VEA service do I loose connection to the disks?
>>>>Thanks!!
>>>>Davide
>>>>
>>>>"KM" wrote:
>>>>
>>>>>There is currently no way to set a maximum size on the log but
>>>>
> stopping
>
>>>>and
>>>>
>>>>>restarting the VEA service (via Control Panel > Services or "net stop
>>>>
>>>vxob",
>>>
>>>>>"net start vxob" will reset the log.
>>>>>
>>>>>KM
>>>>>
>>>>>
>>>>>"Davide" wrote in message
>>>>>news:3e676790$1@hronntp01....
>>>>>
>>>>>>Hello,
>>>>>>I found out my vxisys.log is filling up my C: drive. How can I
>>>>>
> reduce
>
>>>>its
>>>>
>>>>>>size???
>>>>>>
>>>>>>Thanks
>>>>>>Davide
>>>>>
>>>>>
>>>
>
>

No, it's a feature! ;o)

It's just the way Volume Manager must interact with MSCS.


KM


"RRE" wrote in message
news:3E75E82F.80106@eilersen.net...
> Is'nt that a bug?
>
> KM wrote:
> > If you aren't using clustering then it won't affect access to the disks
or
> > volumes. Vxob is responsible for dynamic disk group resources so if it
does
> > not reply to MSCS during a monitoring cycle then the resource will fail.
> >
> > KM
> >
> >
> > "Davide" wrote in message
> > news:3e706186$1@hronntp01....
> >
> >>Yes, it does!!
> >>On our test environment it caused the failover of all disks to the
second
> >>node!
> >>
> >>"KM" wrote:
> >>
> >>>No, it won't affect access to any disks or volumes.
> >>>
> >>>
> >>>KM
> >>>
> >>>
> >>>"Davide" wrote in message
> >>>news:3e685a33$1@hronntp01....
> >>>
> >>>>If I stop the VEA service do I loose connection to the disks?
> >>>>Thanks!!
> >>>>Davide
> >>>>
> >>>>"KM" wrote:
> >>>>
> >>>>>There is currently no way to set a maximum size on the log but
> >>>>
> > stopping
> >
> >>>>and
> >>>>
> >>>>>restarting the VEA service (via Control Panel > Services or "net stop
> >>>>
> >>>vxob",
> >>>
> >>>>>"net start vxob" will reset the log.
> >>>>>
> >>>>>KM
> >>>>>
> >>>>>
> >>>>>"Davide" wrote in message
> >>>>>news:3e676790$1@hronntp01....
> >>>>>
> >>>>>>Hello,
> >>>>>>I found out my vxisys.log is filling up my C: drive. How can I
> >>>>>
> > reduce
> >
> >>>>its
> >>>>
> >>>>>>size???
> >>>>>>
> >>>>>>Thanks
> >>>>>>Davide
> >>>>>
> >>>>>
> >>>
> >
> >
>

Ohhhh, feature, I knew you would say that :-)

Then there is no other way than to boot the machines once a week when you
are running MSCS?

RRE

"KM" wrote in message
news:3e77e0d5@hronntp01....
> No, it's a feature! ;o)
>
> It's just the way Volume Manager must interact with MSCS.
>
>
> KM
>
>
> "RRE" wrote in message
> news:3E75E82F.80106@eilersen.net...
> > Is'nt that a bug?
> >
> > KM wrote:
> > > If you aren't using clustering then it won't affect access to the
disks
> or
> > > volumes. Vxob is responsible for dynamic disk group resources so if
it
> does
> > > not reply to MSCS during a monitoring cycle then the resource will
fail.
> > >
> > > KM
> > >
> > >
> > > "Davide" wrote in message
> > > news:3e706186$1@hronntp01....
> > >
> > >>Yes, it does!!
> > >>On our test environment it caused the failover of all disks to the
> second
> > >>node!
> > >>
> > >>"KM" wrote:
> > >>
> > >>>No, it won't affect access to any disks or volumes.
> > >>>
> > >>>
> > >>>KM
> > >>>
> > >>>
> > >>>"Davide" wrote in message
> > >>>news:3e685a33$1@hronntp01....
> > >>>
> > >>>>If I stop the VEA service do I loose connection to the disks?
> > >>>>Thanks!!
> > >>>>Davide
> > >>>>
> > >>>>"KM" wrote:
> > >>>>
> > >>>>>There is currently no way to set a maximum size on the log but
> > >>>>
> > > stopping
> > >
> > >>>>and
> > >>>>
> > >>>>>restarting the VEA service (via Control Panel > Services or "net
stop
> > >>>>
> > >>>vxob",
> > >>>
> > >>>>>"net start vxob" will reset the log.
> > >>>>>
> > >>>>>KM
> > >>>>>
> > >>>>>
> > >>>>>"Davide" wrote in message
> > >>>>>news:3e676790$1@hronntp01....
> > >>>>>
> > >>>>>>Hello,
> > >>>>>>I found out my vxisys.log is filling up my C: drive. How can I
> > >>>>>
> > > reduce
> > >
> > >>>>its
> > >>>>
> > >>>>>>size???
> > >>>>>>
> > >>>>>>Thanks
> > >>>>>>Davide
> > >>>>>
> > >>>>>
> > >>>
> > >
> > >
> >
>
>

Or you can just delete the file manually!


KM


"Rasmus Rask Eilersen" wrote in message
news:3e79b006@hronntp01....
> Ohhhh, feature, I knew you would say that :-)
>
> Then there is no other way than to boot the machines once a week when you
> are running MSCS?
>
> RRE
>
> "KM" wrote in message
> news:3e77e0d5@hronntp01....
> > No, it's a feature! ;o)
> >
> > It's just the way Volume Manager must interact with MSCS.
> >
> >
> > KM
> >
> >
> > "RRE" wrote in message
> > news:3E75E82F.80106@eilersen.net...
> > > Is'nt that a bug?
> > >
> > > KM wrote:
> > > > If you aren't using clustering then it won't affect access to the
> disks
> > or
> > > > volumes. Vxob is responsible for dynamic disk group resources so if
> it
> > does
> > > > not reply to MSCS during a monitoring cycle then the resource will
> fail.
> > > >
> > > > KM
> > > >
> > > >
> > > > "Davide" wrote in message
> > > > news:3e706186$1@hronntp01....
> > > >
> > > >>Yes, it does!!
> > > >>On our test environment it caused the failover of all disks to the
> > second
> > > >>node!
> > > >>
> > > >>"KM" wrote:
> > > >>
> > > >>>No, it won't affect access to any disks or volumes.
> > > >>>
> > > >>>
> > > >>>KM
> > > >>>
> > > >>>
> > > >>>"Davide" wrote in message
> > > >>>news:3e685a33$1@hronntp01....
> > > >>>
> > > >>>>If I stop the VEA service do I loose connection to the disks?
> > > >>>>Thanks!!
> > > >>>>Davide
> > > >>>>
> > > >>>>"KM" wrote:
> > > >>>>
> > > >>>>>There is currently no way to set a maximum size on the log but
> > > >>>>
> > > > stopping
> > > >
> > > >>>>and
> > > >>>>
> > > >>>>>restarting the VEA service (via Control Panel > Services or "net
> stop
> > > >>>>
> > > >>>vxob",
> > > >>>
> > > >>>>>"net start vxob" will reset the log.
> > > >>>>>
> > > >>>>>KM
> > > >>>>>
> > > >>>>>
> > > >>>>>"Davide" wrote in message
> > > >>>>>news:3e676790$1@hronntp01....
> > > >>>>>
> > > >>>>>>Hello,
> > > >>>>>>I found out my vxisys.log is filling up my C: drive. How can I
> > > >>>>>
> > > > reduce
> > > >
> > > >>>>its
> > > >>>>
> > > >>>>>>size???
> > > >>>>>>
> > > >>>>>>Thanks
> > > >>>>>>Davide
> > > >>>>>
> > > >>>>>
> > > >>>
> > > >
> > > >
> > >
> >
> >
>
>