1. what release of software are you running?
2. are you running a cluster with multiple nodes?
3. if the answer to #2 above is yes, then is disk space being used more heavily on the distributed nodes?
4. are you leveraging tde's?
Jeff Strauss, thanks for the help
1) 10.0.1 server
2) 3 node cluster
3) It does look like worker 1 is using a little more disk space, screenshot below
4) lots of .tde files, but we have done quite a bit of cleanup in the past few weeks which should have reduced their overall impact (deleting a few 3-4gb extracts)
There's a little difference in size of the Tableau folders, 197gb on worker1 and 184gb on worker2
edit to note that the primary differences between the two nodes are in: vizqlserver (w1 is1.7gb bigger), temp (w1 is 4gb bigger)
The backup picks up the tde's which I will assume in your instance is on worker1 and worker2. So if these have somehow grown (even with your cleanup activity in place), then this will cause backups to be larger. Also, I've seen mention in the Tableau release notes of patches mentioning clean up of temp space, old extracts, etc. But I can't find these right off hand since the release notes nowadays aren't so easily searchable.
Understood, I'm 100% sure that our extracts haven't grown by that much. I'm curious if there's an issue, when large tdes are deleted, of remnants of it remaining. I'm going to open a support case, will post back here if resolved.
one more thought for you. Are you using revision history? If so, this can cause backup size to grow as it keeps revisions of workbooks / datasources.
Ohhh, that's a promising idea...we are keeping revision history...and 25 of them at that. Looking into that now and will test taking that number down to 5 or so in our QA cluster to see what happens.
I have similar issue on my workers 1 getting fill disk space every time rebooted. We have 3 node distribution environments. Primary and 2 workers setup windows 12R Tableau server version 10.4
We do have schedule every night backups save on different drive. even though worker 1 space is Eveyday filling 0.5 to 1 GB which is bottom line in diagram range even weekends as well I know we don't have that many workbooks on this environments.
I create ticket with support they were came up with recommendations steps which is in below link.... even though tier-1 support team not able to resolved issue. They moved case to Tier-2.
Any other recommendations please advice.
Repository on worker 1. worker 2 and primary servers doesn't have any changes in disk space
Fist line -- Worker1
3rd one Worker2