paullord
asked on
e000848f - Insufficient disk space
I'm running backup exec 11d on W2k3 server SP2. I'm attempting an incremental backup to disk with the "enable the restore of individual mail messages" options selected. The backup back ups about 20GB and then times out with the following error "e000848f - Insufficient disk space" This is despite there been over 6GB of space remaining on the disk.
Any help appriciated!!
Any help appriciated!!
I think that your disk space problem is on client(agent) rather than on Media server -> look there...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have 0GB set as the amount to reserve on the disk. I stuck with the default backup file size of 1GB. I'm backing up to a SAN drive (Drive D) the client is installed on the C drive of the W2k3 server
So you are backing up the C: drive to the D: drive (which is your SAN)?
ASKER
No, the C drive does not get backed up.
"I'm backing up to a SAN drive (Drive D) the client is installed on the C drive of the W2k3 server"
What does that mean, then? The client you are backing up is a W2k3 server and the Backup Exec server is one as well, correct? The Backup Exec server runs a backup job against the W2k3 server C: drive to the Backup Exec server's D: drive, which is set up as a disk-to-disk backup, correct?
Just for safety, I would not set the reserve to 0Gb. It is never a good idea to completely fill a disk, even a SAN connected disk. At least set it to have a reserve of 2 or 3 gigs. Optimally, it is not a good idea to get below 15% of a disk being managed by Windows. Regardless of this, though, it still sounds like there is a job setup or something that hits a 5G limit and since you are using the default 1G file sizes, it stops and waits for disk space to be cleared up. After waiting for the time specified by you in the job setup, it times out and fails the job due to disk space.
What does that mean, then? The client you are backing up is a W2k3 server and the Backup Exec server is one as well, correct? The Backup Exec server runs a backup job against the W2k3 server C: drive to the Backup Exec server's D: drive, which is set up as a disk-to-disk backup, correct?
Just for safety, I would not set the reserve to 0Gb. It is never a good idea to completely fill a disk, even a SAN connected disk. At least set it to have a reserve of 2 or 3 gigs. Optimally, it is not a good idea to get below 15% of a disk being managed by Windows. Regardless of this, though, it still sounds like there is a job setup or something that hits a 5G limit and since you are using the default 1G file sizes, it stops and waits for disk space to be cleared up. After waiting for the time specified by you in the job setup, it times out and fails the job due to disk space.