Highlighted

Running out of storage space. What would you do?

Hey guys.

I just started working at a new company and the backup server is a mess. The 2 B2D drives are pretty much full.

The exchange GRT backups are stored to B2D drives that are running out and the rest go to Dedupelication drives (They have plenty of storage space left)

My question is, what would you do in this scenario? You can se the second server there but lets avoid that. Would like to hear some opinions. Thanks!

Untitled.png

 

1 Solution

Accepted Solutions
Accepted Solution!

In this scenario you'd either

In this scenario you'd either throw more disk space at the B2D jobs, or cut down on your retention time. Both would end up in increased disk space.

Alternatively, direct more backups to the dedupe folder if you can and decrease the reliance on B2D.

Thanks!

View solution in original post

4 Replies
Accepted Solution!

In this scenario you'd either

In this scenario you'd either throw more disk space at the B2D jobs, or cut down on your retention time. Both would end up in increased disk space.

Alternatively, direct more backups to the dedupe folder if you can and decrease the reliance on B2D.

Thanks!

View solution in original post

Thanks for the reply, isn't

Thanks for the reply, isn't it a bad idea to have exchange grt backups go to dedupe drives? 

I know there is a way to do this but I am not sure how exactly. Is there an article with instructions for the setup? 

 

Thanks

You'd simply change the

You'd simply change the backup destination for the Exchange job to point to the dedupe folder instead of the B2D. This gets done on the job definition.

Okay, I will give this a try.

Okay, I will give this a try. Thanks