ZENworks Database and Primary Servers / Scheduled Reboot

Hi all,

I hope I got the correct forum for my questions. If not could an admin be so good to move me to the correct one?

We've got a ZENworks 11.3.1 Zone with 4 Primary Severs (SLES 11SP3) and up to 25 Satellites (mixed OS). The Databases are on MS SQL.

Some times we get very strange behaviour of bundles, policies and ZCC is slow. After taking the Databases down and reboot the four primaries the zone is working fine again for a time.

My question is: Do you reboot your Zone daily/weekly? I did'nt find any recommendations in the documentation.

Thanks in advance for letting me know how you handle this.

Kind regards
Sebastian
Parents
  • tbargfrede <tbargfrede@no-mx.forums.novell.com> wrote:
    > Hi all,
    >
    > I hope I got the correct forum for my questions. If not could an admin
    > be so good to move me to the correct one?
    >
    > We've got a ZENworks 11.3.1 Zone with 4 Primary Severs (SLES 11SP3) and
    > up to 25 Satellites (mixed OS). The Databases are on MS SQL.
    >
    > Some times we get very strange behaviour of bundles, policies and ZCC is
    > slow. After taking the Databases down and reboot the four primaries the
    > zone is working fine again for a time.
    >
    > My question is: Do you reboot your Zone daily/weekly? I did'nt find any
    > recommendations in the documentation.
    >
    > Thanks in advance for letting me know how you handle this.
    >
    > Kind regards
    > Sebastian
    >


    Right place :)

    No, you should not need to reboot every Day, week or even month. Using a
    lot of RAM?

    What about your DB's maintenace plan? How does this look?

    --
    Nops
  • nop1983;2330117 wrote:
    tbargfrede <tbargfrede@no-mx.forums.novell.com> wrote:
    > Hi all,
    >
    > I hope I got the correct forum for my questions. If not could an admin
    > be so good to move me to the correct one?
    >
    > We've got a ZENworks 11.3.1 Zone with 4 Primary Severs (SLES 11SP3) and
    > up to 25 Satellites (mixed OS). The Databases are on MS SQL.
    >
    > Some times we get very strange behaviour of bundles, policies and ZCC is
    > slow. After taking the Databases down and reboot the four primaries the
    > zone is working fine again for a time.
    >
    > My question is: Do you reboot your Zone daily/weekly? I did'nt find any
    > recommendations in the documentation.
    >
    > Thanks in advance for letting me know how you handle this.
    >
    > Kind regards
    > Sebastian
    >


    Right place :)

    No, you should not need to reboot every Day, week or even month. Using a
    lot of RAM?

    What about your DB's maintenace plan? How does this look?

    --
    Nops


    All primaries got up to 6GB RAM which is used normally 50-70%.
    The Database MS SQL Server uses RAM 70-80%

    Database maintenance plan: backup every day, shrink every day.

    Devices in zone: >2000
    Database size: 23GB
Reply
  • nop1983;2330117 wrote:
    tbargfrede <tbargfrede@no-mx.forums.novell.com> wrote:
    > Hi all,
    >
    > I hope I got the correct forum for my questions. If not could an admin
    > be so good to move me to the correct one?
    >
    > We've got a ZENworks 11.3.1 Zone with 4 Primary Severs (SLES 11SP3) and
    > up to 25 Satellites (mixed OS). The Databases are on MS SQL.
    >
    > Some times we get very strange behaviour of bundles, policies and ZCC is
    > slow. After taking the Databases down and reboot the four primaries the
    > zone is working fine again for a time.
    >
    > My question is: Do you reboot your Zone daily/weekly? I did'nt find any
    > recommendations in the documentation.
    >
    > Thanks in advance for letting me know how you handle this.
    >
    > Kind regards
    > Sebastian
    >


    Right place :)

    No, you should not need to reboot every Day, week or even month. Using a
    lot of RAM?

    What about your DB's maintenace plan? How does this look?

    --
    Nops


    All primaries got up to 6GB RAM which is used normally 50-70%.
    The Database MS SQL Server uses RAM 70-80%

    Database maintenance plan: backup every day, shrink every day.

    Devices in zone: >2000
    Database size: 23GB
Children
  • tbargfrede <tbargfrede@no-mx.forums.novell.com> wrote:
    > nop1983;2330117 Wrote:
    >> tbargfrede <tbargfrede@no-mx.forums.novell.com> wrote:
    >>> Hi all,
    >>>
    >>> I hope I got the correct forum for my questions. If not could an

    >> admin
    >>> be so good to move me to the correct one?
    >>>
    >>> We've got a ZENworks 11.3.1 Zone with 4 Primary Severs (SLES 11SP3)

    >> and
    >>> up to 25 Satellites (mixed OS). The Databases are on MS SQL.
    >>>
    >>> Some times we get very strange behaviour of bundles, policies and ZCC

    >> is
    >>> slow. After taking the Databases down and reboot the four primaries

    >> the
    >>> zone is working fine again for a time.
    >>>
    >>> My question is: Do you reboot your Zone daily/weekly? I did'nt find

    >> any
    >>> recommendations in the documentation.
    >>>
    >>> Thanks in advance for letting me know how you handle this.
    >>>
    >>> Kind regards
    >>> Sebastian
    >>>

    >>
    >> Right place :)
    >>
    >> No, you should not need to reboot every Day, week or even month. Using
    >> a
    >> lot of RAM?
    >>
    >> What about your DB's maintenace plan? How does this look?
    >>
    >> --
    >> Nops

    >
    > All primaries got up to 6GB RAM which is used normally 50-70%.
    > The Database MS SQL Server uses RAM 70-80%
    >
    > Database maintenance plan: backup every day, shrink every day.
    >
    > Devices in zone: >2000
    > Database size: 23GB
    >


    Hey

    Zpm in place? Thats a large DB, I see 9GB with 2700 devices on sql.

    This from the docs:
    Check database integrity
    Shrink database
    Reorganize index
    Rebuild index
    Update statistics
    Back up database

    Do you do any of the above? You could give it a try? :)

    --
    Nops
  • >>Shrink database<<

    A properly maintained SQL database should not need to be shrunk daily!

    All this accomplishes is to cause the DB to slow down when it needs more space as it allocates the space you just removed - so this gets into a daily loop of shrink, grow, shrink, grow...fragmenting the files and disks.

    I only on rare occasions manually run the commands to shrink my databases and then only when there has been a large amount of data purged from the system which permanently reduces the need of space in the data files OR some extensive operation has caused the log file to grow much bigger than it needs to be on a normal day to day basis.

    Proper growth settings are also important - the defaults of 10% can get unwieldy - so in a 23 GB database this grows 2.3 GB when it may only need 1 more byte!

    Regards,

    Dave