IN a nutshell:
We currently have 4Tb of backup storage (B2D-Data and B2D-GRT folders)
Due to some company growth and so forth - we keep running out of disk space during both incremental and full backups.
2 days ago, as a short term "band aid" we installed an F-SATA controller card and hung a 1 TB HDD off the back of the system, which actually gives us plenty of space for the short term.
My question is on configuration. Here is how I configured the "new" drive.
EXISITING:
On server - 4 TB with
B2D-DATA (folder)
B2D-GRT (folder)
NEW - 1 TB with
B2D-Data-ESATA (folder)
B2D-GRT-ESATA (folder)
We created 2 seperate device Pools - one that includes the Data folders from both drives - and one that includes the GRT folders from both drives. (See Graphic below)
BACKUPEXEC - when it starts a job - picks one of the folders from one of the drives - and starts backing up to it, seemingly randomly
The problem is that the original 4tb hard drive fills up and errors out because it's out of disk space - and the backup halts. I assumed that, just like the Tape duplicate jobs, which when a tape is full - loads another and continues - the same would occur on the backup portion: HDD fill up - and job just continues on external drive.
So - that's the question. Can I configure BE to "see" the external drive as a contiguous disk? Or at least treat it like an overflow instead of halting on the job due to a "disk full" alert?
THANKS for any insight!!!!
