Jump to content
Division-M Community

jeremy.green

Members
  • Content Count

    14
  • Joined

  • Last visited

About jeremy.green

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Ely, UK
  • Interests
    Mapping
  1. I have 4 servers running driver bender. All are windows 2012 r2 core (2 virtual + 2 physical) One victual server just seems to get into a situation where the driver bender service runs @ 100% cpu. I can kill the server, start the service an all in once more @ about 2-3% or less. Cannot find any event logs for drive bender with errors or not **not sure where to look next**
  2. Thanks for the feedback and explanation on how files systems work. I assume that there was some underling magic that immediately worked out that there would be insufficient room!
  3. Looks to be an issue with rdp as was using the admin console via a rdp session to a virtualised windows 2012 R2 server The RDP session is set to auto scale depending on the monitor I'm using. Looks like the management console does a good job at scaling just somehow got stuck on one of the servers. Fixed by going full screen, closing and then reopening the management console.
  4. Ok will check this out as its not config Ok on windows 10 at 250%
  5. found this on support https://support.division-m.com/hc/en-us/articles/214026643?input_string=landing+zone+size
  6. Add further rules to the landing zone a. Any files smaller than [landing zone fee space] would get written to the landing zone. b. If the landing zone reaches a % of [landing zone capacity] then balancing would occur immediately based on balancing rules. c. If the file is larger than the [landing zone capacity], the landing zone would get bypassed based on balancing rules. This would allow the landing zone to still improve the performance for small file writes and support slower very large file writes.
  7. @w3wilkes thanks for the suggestion Currently removed the landing zone from the backup server. Wanted to check with the community that I wasn't a complete idiot (just mostly)
  8. On one system I can see running tasks and not especially well formatted version number in the GUI of a remote server From another system with the same version of client 2.8.00 no links Is this a client setting?
  9. Yes the balancing is enabled and set to clear at midnight, so the landing zone not clearing is a different issue I think (mapped the drive to see what the files were and they are old 2017) In my case the landing zone might never be big enough when backing up servers (using WBADMIN to do the backup typically once per week). Would be good If it fails gracefully into a most space balance mode so option b.
  10. I have also observed that the landing zone is not clearing (will need to find out what is in it)
  11. I have made a few assumption (which I think are wrong but need some help) about the pool configuration. I have used a SSD for the landing zone to speed up writing of backup files The SSD is only 20gb There are 4 further disks each of which is 2Tb a. I assumed that any files smaller than 20gb would get written to the landing zone initially. b. If the landing zone filled then balancing would occur immediately or a larger disk would be selected based on available space. c. If the file is larger than 20gb again the landing zone would get bypassed. Is any of this true? What I'm observing if that large files (>20gb as they are backups) are not getting copied over and there is an insufficient disk space warning. So does the landing zone have to be much bigger, and how much bigger if a. b. or c. don't happen.
  12. Did your landing zone every empty as mine still has items in it.
×
×
  • Create New...