Forum Discussion
CraigV
15 years agoModerator
Hi,
No. When a disk target is created, you create a B2D folder on that specific disk. The job is then targetted at that, and will cease to write data to the drive once it has hit its limit that you would have specified.
It doesn't automacially move on to another folder like a tape to my knowledge, unless set up correctly.
You would need to look at your overwrite protection period, and make sure that is correct. If those settings aren't, and it isn't returning *.bkf files to scratch, it will fill up to the point of no further backups until you do something manually. Check that, and your append periods, and make sure they are correct.
You don't say how much space you are backing up, or what your process is (Full, Incremental or Differential).
In this case, as an easy fix, I would target the 1TB drive first. Maybe look at splitting some days off onto the smaller drive as well (like a weekly/monthly job).
Having internal drives doesn't mean a definite no-no, but RAID does help your protection of disks though. If you COULD do it, I would suggest that.
However, the guy above you has it all wrong too...tape is DEFINITELY not the way of the future. When you move on to BEWS 2010, and want to use data deduplication, you can only do this on disk. Restores are easier from disk; staging Information Store restores are easier when done to disk first; disk is considered faster than tape when backing up and restoring (for now...LTO5 is out!), so there are a lot of reasons for using disks.
Added protection of your data would see you stream the files off to tape once you have finished your B2D...
No. When a disk target is created, you create a B2D folder on that specific disk. The job is then targetted at that, and will cease to write data to the drive once it has hit its limit that you would have specified.
It doesn't automacially move on to another folder like a tape to my knowledge, unless set up correctly.
You would need to look at your overwrite protection period, and make sure that is correct. If those settings aren't, and it isn't returning *.bkf files to scratch, it will fill up to the point of no further backups until you do something manually. Check that, and your append periods, and make sure they are correct.
You don't say how much space you are backing up, or what your process is (Full, Incremental or Differential).
In this case, as an easy fix, I would target the 1TB drive first. Maybe look at splitting some days off onto the smaller drive as well (like a weekly/monthly job).
Having internal drives doesn't mean a definite no-no, but RAID does help your protection of disks though. If you COULD do it, I would suggest that.
However, the guy above you has it all wrong too...tape is DEFINITELY not the way of the future. When you move on to BEWS 2010, and want to use data deduplication, you can only do this on disk. Restores are easier from disk; staging Information Store restores are easier when done to disk first; disk is considered faster than tape when backing up and restoring (for now...LTO5 is out!), so there are a lot of reasons for using disks.
Added protection of your data would see you stream the files off to tape once you have finished your B2D...
Related Content
- 11 months ago
- 2 years ago
- 9 years ago