/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Kace backup sizes have tripled in 2 months after upgrade to Version 10.0.290

12/03/2019 112 views

I'd touched base with Kace Support and they basically said this just happens once they enabled HTML in the HelpDesk comments.  I have a really hard time believing that...  Hoping to poll the community.


Details:

We rebuilt the Hyper-V host that was running the K1000, then pulled in an older backup of the VM (roughly 3 days old at the time), followed by a restore of the DB (one day old) first of October.  Since that time, our backups have continued to increase exponentially with zero real change to our workflow.  We haven't added any new scripts or managed installs, haven't made any changes to the configuration, just regular old day in/day out inventories and HelpDesk usage.  10/8, I had a Base Image that was 2,075,106 KB and an incremental that was 2,752,425 KB.  Today, I've got a Base Image that's 2,085,044 KB and incremental that's 7,592,426 KB.  I can't see HTML in the HelpDesk accounting for that...

Like I said, initial support contact with Quest didn't really offer any insight, just a "whatevs" and a .kbin to run a daily size report script.  That doesn't shed a whole lot of light on anything... 

For example, 11/11/2019, size report is:

Filesystem    Size    Used   Avail Capacity  Mounted on

/dev/da0p3    3.9G    245M    3.3G     7%    /

devfs         1.0K    1.0K      0B   100%    /dev

/dev/da0p5     12G     50M     11G     0%    /tmp

/dev/da0p6     12G    106M     11G     1%    /var

/dev/da0p7     12G    3.8G    6.9G    36%    /usr

/dev/da0p8    899G    107G    720G    13%    /kbox

procfs        4.0K    4.0K      0B   100%    /proc

fdescfs       1.0K    1.0K      0B   100%    /dev/fd


Incremental for that day is 5,631,309 KB.


Size report for today:

Filesystem    Size    Used   Avail Capacity  Mounted on

/dev/da0p3    3.9G    245M    3.3G     7%    /

devfs         1.0K    1.0K      0B   100%    /dev

/dev/da0p5     12G     62M     11G     1%    /tmp

/dev/da0p6     12G    105M     11G     1%    /var

/dev/da0p7     12G    3.8G    6.9G    36%    /usr

/dev/da0p8    899G    106G    721G    13%    /kbox

procfs        4.0K    4.0K      0B   100%    /proc

fdescfs       1.0K    1.0K      0B   100%    /dev/fd


Incremental for today is 7,592,426 KB


/Kbox directory is actually lower on today's size report, but the incremental backup is almost 2GB larger...


Anyone out there think they can point me in the right direction?  Thanks in advance.

1 Comment   [ + ] Show comment

Comments

  • Can you give me the support ticket number.
    • It was via online chat with Raul, 2019.11.04. Online chat doesn't give a support ticket # that I know of, or at least not listed in the transcript.

All Answers

0

It appears that there is no associated support ticket that was opened with your chat.

If you open a support ticket we can further investigate.


If you are familiar with the tar command, you can look at the contents of the backup files to try to make a determination of the size requirements.



Answered 12/04/2019 by: KevinG
Fourth Degree Green Belt

  • How bout being familiar with the "concept" of the TAR command...but barely :D Just opened Support Ticket 4619175. Thank you!