Jump to content
Division-M Community


  • Content Count

  • Joined

  • Last visited

  • Days Won


PeteCress last won the day on February 14 2017

PeteCress had the most liked content!

About PeteCress

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. I am using DriveBender on my backup file server. The "Production" server is a NAS box. Every so often an incremental backup job copies changed files to the DriveBender box. The utility I use ("SecondCopy") is a file-based backup and conveniently keeps superceeded versions of all files it backs up. ..... That makes it convenient to restore a single file from, say, 3 backups ago because all the versions are in one place. But one reality of encryption/ransom malware has finally dawned on me: my 24-7 PC becomes infected, the malware works through the PC's shares to the NAS box to encrypt files on the NAS box, and then the next backup cycle copies those encrypted files to the DriveBender box. In that case, onsies-twosies using from the superceeded version lists would not be realistic for 10+ TB of data and the need would be for a complete restore from the last backup before the malware infection and . So it seems that what is needed is something like Macrium Reflect where I can restore a complete image from a given incremental backup with a single click. The Question: Would it be practical to use Macrium Reflect to back up from my NAS box to the DriveBender box? We're talking 10+ TB of data divided among six shares on the NAS box and 12 drives on the DriveBender box....... So: six humongous files on the DriveBender box for the initial backup plus six more normal-sized files each day for incrementals...... My initial load of the DriveBender box via file copies took several days...and my experience with Macrium Reflect on about 1TB of data is that it's slow as death. Is anybody doing this?
  2. viz: https://photos.google.com/share/AF1QipMHDERDPAS7ZNjkd4SjIYEMJIXqtp_qKXEC3olBWOaR3vTHjLy8Ej0Zj0Nhs99Ubw/photo/AF1QipOlNerih-yG5GismmNTB-he8j0ujzJ9N8cySiuw?key=WDdSdm4wSG90UkNwMG1FMVdSQ2p0NEFRQThPRVJ3 Note That: This is a fresh build of windows and a fresh install of DB 2.5 . Windows sees all 13 of my DriveBender-pooled disks. DriveBender seems to know about them too because the pool (faux drive Z:) is shown by Windows and can be opened. In spite of all those good things, none of the pool's drives are shown on the Drive Bender screen. The three drives that are not in the pool are shown. We have re-booted twice, with the same results. Maybe some setting that determines whether-or-not pool drives are shown? Edit 2017 01-22 20:53: Got it!.... Pool Options | Switch to Pool | (Choose the Pool by name)
  3. No, just fired up the v2.5 exe and lit it rip. Will try the Uninstall/Install. Thanks.
  4. Per attached screen snaps. v2.4 was working for me. Upgraded to 2.5 and now I seem to be dead in the water. I note that Drive Bender Service is not running and will not start. OTOH, something called Drive Bender SMART Service is running. Can anybody shed some light?
  5. I am trying to take benchmarks of my pool drives and the balancing process is muddying the waters. Did a Settings | Balancing | Enable File Balancing = False | Apply, but the process continues. Seems like it's taking 80-file chunks and, when done with one, starts another. Should it stop after it is done with the current 80-file chunk? Or do I need to do something else? Edit 2016 12-05 15:42: May have answered my own question. .... Went out for awhile, came back, and the current batch had finished and no next batch had started.....
  6. That's interesting - in the context of my prior DriveBender (with drive letters assigned and, I am pretty sure, access to those drives from outside of DB) build having gotten weird on me. The rebuild, OTOH, has been running with no problems...... So I guess I will double down on not assigning drive letters.... -)
  7. That's what I was hoping to hear..... What I left out was that the DB box *is* the backup...... for a NAS box.... Thanks!!!!
  8. But a backup of what?...... Are we talking about the DriveBender database i was hypothesizing? If so where does it live? I'm looking at C:\Program FIles\Division-M\Drive Bender and nothing is jumping out at me. Or does importing the array re-create whatever it is ? i.e. What and why do I need to back up? My kneejerk would be to do a (browsable later) Macrium Reflect image of C:.
  9. If I want to upgrade my mobo - and, preseumably, re-build the system/re-install DB is there any way to keep the pool intact? Not a huge issue.... but my backup server's 10TB takes almost a week to load and it would be nice to not have that no-backup exposure. I'm thinking maybe there is a DriveBender database or something somewhere that I could backup and then restore on the new build.
  10. Makes sense - and, next morning, sure-enough the new drive was partially populated. Now I know what to expect. Thanks....
  11. Does anybody find benefit(s) in assigning drive letters to their pooled drives? I just removed all of mine to free up more letters for network drive mapping.... but now that I'm thinking about it, I cannot see why I assigned them in the first place. ??
  12. I finally have the DriveBender array loaded, duplication turned on for all folders, and the system quiesced... A dozen drives, about 10TB of data. But now I have just added a new, empty drive to the pool and it started "Scanning...." . .... Maybe 10 minutes later it has switched to "Validating.....".... with a file count of only 5,000-or-so..... so it's not scanning the entire pool. Is this Business As Usual? Or maybe do I have an option set somewhere that tells it to do a re-balance if/when a new drive is inserted?
  13. Got the part about writing SN's on tape affixed to the end of the drives and I have done that - although, at this time, I do not know the drive letters or drive names of each drive. But I am moving the mobo and drives to a new case with 20 hot-swappable bays. Just spent 5 days loading the array, so I would rather not hose it during the move. The drives, of course, are already assigned names: DB1, DB2, DB3.... and so-forth I want the drives to be in the new case's bays in order of name. I am tempted to: Install the mobo and System drive in the new case . Start the system (and without knowing how to suppress it, have DB start too) . Insert a drive. . See what comes up in Windows Explorer ("DB2", "DB1", or whatever) . Remove the drive. . Re-insert it into the appropriate bay (Bay#2, Bay#1, or whatever) . Repeat this with all the other drives. Does anybody expect a problem with this? My main reservation is that, unless somebody tells me how to keep it from loading, DriveBender will be up and running during all this confusing (?) activity and maybe the array will become compromised and I'll have to spend another 5 days re-loading it. Edit 2016 10-14 14:47 OK... No need to insert the drives into the DB machine.... any machine I insert them into will reveal the drive name as long as it does not duplicate an existing drive in the machine..... So that lays to rest the issue. But I would still like to know for future reference how recoverable the array is when populated drives are removed/reinserted.
  14. My agenda is that I want to identify which physical disk has been assigned which drive letter. Then I will slap a drive-letter label on each disk and then, if/when a disk goes South, I will be able to easily replace said disk after removing it from the pool. To the end of identifying the disks beforehand, I would shut DriveBender down and then pull the power plug on a disk and see which drive lettered disk goes away in the Windows Explorer device list. I guess I could open up the Services app and kill any services that look like DB.... But I am guessing there is a "Right" way to do this and I'd rather do it that way....
  15. Does anybody use Windows File Compression on their DriveBender pool discs?
  • Create New...