Jump to content
Division-M Community

Search the Community

Showing results for tags 'landing zone'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Anvil File Security
    • General Discussion
    • Help and Support
  • Drive Bender
    • Beta Versions
    • General Discussion
    • Help and Support
    • Feature Request
  • Cloud Xtender
    • Beta Versions
    • General Discussion
    • Help and Support
    • Feature Request
  • General
    • Announcements and News

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. I mistakenly posted a question to the Cloud Xtender subforum a few days ago and it doesn't look like the mods are going to move it for me so I'll repeat my most pressing question here: I'm trying to use DriveBender's landing zone so that downloaded files are are collected on an internal drive throughout the day, and my external enclosure only has to spin up to accept the day's files in one go each night. Problem is, DriveBender's duplicate folder structure means that although the new FILES are being placed the landing zone, it spins up all 8 of my external hard drives just to create the new folders! Is there a hack / tweak / registry setting I can employ to defeat this folder/file structure from power cycling my poor drives?
  2. 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.
  3. 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.
  4. Hi I have an issue that crops up too often and when I look at what's going on it seems to be a conflict of disk access. It seems that when there's a background operation being performed by DriveBender, like drive balancing or file validation, and myself or a program moves or adds a large file to the pool, a random drive will go off line and DriveBender will drop into read only mode. After doing some reading I've come across the idea of setting a fast drive as a landing zone drive as this may offer a buffer. I've tried to find a detailed explanation of what setting a drive as a landing zone actually does. I eventually found the user manual, but that makes no mention of the landing zone feature. So, some questions: Question 1: If I have a program, like Acronis True Image, making an image of C drive into a folder on D drive (D drive is my pool) and I have a drive selected as a landing zone, my understanding is that the image file (at the moment a 130GB file) will be copied onto the landing zone then at a predetermined time after the image is finished it will be copied to the pool? Question 2: Does DriveBender wait to clear the landing zone until any drive balancing or file validation operations are finished? or does it just do when scheduled? Question 3: Is the landing zone invisible? By this I mean if I or a program copies files to specific folders on D drive does the files go to the landing zone first and when appropriate move it to the correct location but that I don't see this happening? (and that it appears to go straight into the folder chosen?) Solution, If answers make sense: Purchase something like a WD 1 or 2TB black drive, add it to the pool and set this up as the landing zone. (DB Version 2.5.0.0) TIA D
  5. I have 9 drives in DriveBender on my Win10 desktop: -5 USB2 -3 internal 7200rpm -1 insternal SSD (set as landing zone) I use this for all file storage as well as location where my VMs run. I would like the ability to "pin" certain files (or a folder) to the SSD drive so they stay there - I have about 10GB of VHDs that represent my currently running test machines and I want to make sure they stay on the SSD. Thanks, Tolli
  6. I'm thinking about adding a small'ish SSD to the pool and set it as a landing zone. But... that would only make sense if Drivebender would "empty" the drive when re-balancing, or at least run it down to its custom target percentage. Seems like a practical feature, right?!
×
×
  • Create New...