How do I get this to work? WHS DBBB

Justintoxicated

[H]F Junkie
Joined
Apr 10, 2002
Messages
14,522
I guess I still don't understand WHS.

I really want to add some redundancy so that if I lose a drive I don't lose all of my backups.

However I can't figure out how to get this plugin to do anything useful.

I get the following error.
Untitled-1.jpg


Untitled-2.jpg
 
That first screenshot indicates the size of your backup database is ~2TB? Also, you don't indicate where you are trying to create the BDBB backup, i.e to an external drive or a network share. If you're backing up to an external drive you'll need an external box that can do a raid volume bigger than 2 TB. If you're backing up to a network share, you must make sure your target share is bigger than 2 TB. Also, you should uncheck the duplication boxes. The first duplication box basically duplicates the WHS backup database just like duplication of your shares. You'll have two copies of your backups in your storage pool. The second duplication box, duplicates the BDBB backup. For most people, the BDBB backup is all that is needed. It allows you to have a backup of your backup database in a different location than the storage pool and enables you to restore the backup database in the even it gets corrupted or is lost due to a drive failure.
 
what exactly does the BDB contain? Mappings or actual data? I don't really know how it works. Does it work like a parity drive?

I guess there is no way I can backup then as I don't have any drives that are larger than 2 TB, and backing up to a raid-0 array would be stupid and more expensive. My server is entirely made of 1 TB drives so I guess it cannot be backed up.

I guess I just have to live with the fact that WHS isn't very good for backups since a single drive failure during a restore would be devastating. Is there a way I can tell it to only make certain drives or folder redundant?
 
what exactly does the BDB contain? Mappings or actual data? I don't really know how it works. Does it work like a parity drive?

I guess there is no way I can backup then as I don't have any drives that are larger than 2 TB, and backing up to a raid-0 array would be stupid and more expensive. My server is entirely made of 1 TB drives so I guess it cannot be backed up.

I guess I just have to live with the fact that WHS isn't very good for backups since a single drive failure during a restore would be devastating. Is there a way I can tell it to only make certain drives or folder redundant?

The backup database contains actual data. The backup database can be used for single file restore or to restore whole computers from the image, (os & data). The backup database does not work like a parity drive. That is a raid thing. WHS is actually excellent for backups. The question is: Why is your backup database ~2TB? That is a very large backup database. It seems like you're backing up all of your data into the backup database whereas you should be backing up only the OS & application drive and other critical data. All other non critical data can be stored in the shares on the WHS machine and duplicated so you will have 3 copies of your data, (one on the PC, and two in the WHS machine). You can use Synctoy to replicate and sync the data on your PC to the WHS shares and use WHS backup to backup the OS & applications.

The last question you ask doesn't make sense in relatation to the backups.
 
The backup database contains actual data. The backup database can be used for single file restore or to restore whole computers from the image, (os & data). The backup database does not work like a parity drive. That is a raid thing. WHS is actually excellent for backups. The question is: Why is your backup database ~2TB? That is a very large backup database. It seems like you're backing up all of your data into the backup database whereas you should be backing up only the OS & application drive and other critical data. All other non critical data can be stored in the shares on the WHS machine and duplicated so you will have 3 copies of your data, (one on the PC, and two in the WHS machine). You can use Synctoy to replicate and sync the data on your PC to the WHS shares and use WHS backup to backup the OS & applications.

The last question you ask doesn't make sense in relatation to the backups.

So basically I don't use WHS to do backups for data but a 3rd party app that needs to be installed on all 5 client machines?

Then the Important Data is not archived but instead synchronized, such that I would not be able to pull earlier versions or contents of the folders. (As in I accidentally deleted a large file and realize it is missing a few days later)?
 
The backup database contains actual data. The backup database can be used for single file restore or to restore whole computers from the image, (os & data). The backup database does not work like a parity drive. That is a raid thing. WHS is actually excellent for backups. The question is: Why is your backup database ~2TB? That is a very large backup database. It seems like you're backing up all of your data into the backup database whereas you should be backing up only the OS & application drive and other critical data. All other non critical data can be stored in the shares on the WHS machine and duplicated so you will have 3 copies of your data, (one on the PC, and two in the WHS machine). You can use Synctoy to replicate and sync the data on your PC to the WHS shares and use WHS backup to backup the OS & applications.

The last question you ask doesn't make sense in relatation to the backups.

Setup is as following.

5 client machines of various configurations one has about 4-5 TB of data. The Main PC is a Water-Cooled Stacker Case so it can hold all the storage I need, and isn't sharable to everyone on the network. This PC was the primary reason for needing a backup system.

The WHS box has 6TB of space and room for only one more drive.

So my understanding is that the storage pool on the WHS box should only be about 1TB-2TB, total meaning only 1-2 drives for applications and OS backups of all the client machines. Then I somehow need to split up the rest of the drives for backups of regular DATA?

This leads to the issue of organization.

1) How do I organize this is such a way that I can separate which the data is from each of the clients?

2) Also your suggesting I use 3rd party software to do each of the backups which gets away from WHS automation (Fair Enough)?. This requires 3rd party software to be installed on each of the client machines? If so then the WHS box would be the same as using any other server, but allows for enabling redundancy of these network shares? If I got this right that sounds pretty cool. I'm still not sure how to enable that redundancy for the network shares though? I really only have about 500 GB of Data that I want to enable the redundancy on.

So in the end I need a much more complex WHS config and likely a MUCH larger case to put all 12 1 TB drives into? And then, I still have the problem of permissions on the network shares and organization of the data. Which i do not have any idea how to solve.


Just to clarify my idea backup would work as follows. Use the large giant storage pool for automating backups. Then take the 500 GB of critical data that I do not want to lose, and enable redundancy on that data, in such a way that if I lose a drive I don't lose my entire backup.
 
Last edited:
So basically I don't use WHS to do backups for data but a 3rd party app that needs to be installed on all 5 client machines?

Then the Important Data is not archived but instead synchronized, such that I would not be able to pull earlier versions or contents of the folders. (As in I accidentally deleted a large file and realize it is missing a few days later)?

Synctoy is a free Microsoft product. You can configure it to keep data on the target drive even if its deleted on the source.
 
Setup is as following.

5 client machines of various configurations one has about 4-5 TB of data. The Main PC is a Water-Cooled Stacker Case so it can hold all the storage I need, and isn't sharable to everyone on the network. This PC was the primary reason for needing a backup system.

The WHS box has 6TB of space and room for only one more drive.

So my understanding is that the storage pool on the WHS box should only be about 1TB-2TB, total meaning only 1-2 drives for applications and OS backups of all the client machines. Then I somehow need to split up the rest of the drives for backups of regular DATA?

This leads to the issue of organization.

1) How do I organize this is such a way that I can separate which the data is from each of the clients?

2) Also your suggesting I use 3rd party software to do each of the backups which gets away from WHS automation (Fair Enough)?. This requires 3rd party software to be installed on each of the client machines? If so then the WHS box would be the same as using any other server, but allows for enabling redundancy of these network shares? If I got this right that sounds pretty cool. I'm still not sure how to enable that redundancy for the network shares though? I really only have about 500 GB of Data that I want to enable the redundancy on.

So in the end I need a much more complex WHS config and likely a MUCH larger case to put all 12 1 TB drives into? And then, I still have the problem of permissions on the network shares and organization of the data. Which i do not have any idea how to solve.


Just to clarify my idea backup would work as follows. Use the large giant storage pool for automating backups. Then take the 500 GB of critical data that I do not want to lose, and enable redundancy on that data, in such a way that if I lose a drive I don't lose my entire backup.

I think you've got it all pretty confused. See my PM to you a few minutes ago. WHS is pretty simple and easy to use.
 
Still have not figure out a perfect plan. I believe it serves me best to leave all my data in the backup database as well. Heres a situation that just happened to me over the weekend.

While I was at work my gf went through my PC and located old pictures. She deleted complete directories where I had photos of other girls in them (ex's or just random other girls etc.) Not knowing that my data had been messed with, I would have allowed the plugin to update the shared folders with the changes not knowing I was tossing out 10 years of photos.

However, if I was still storing data in the BDB, and I caught on within a few months, I would still be able to recover data from the BDB....

I'm thinking that I will use the shared folders for the data that I want to be redundant, but live with the fact that I can not backup the BDB....

Make sense or am I' still doing it wrong?
 
Why not just use an external drive and backup to there using some free program? I know its not the elegant all in one solution but it will work and be simple enough.
 
I'll try and make sense of all this -

You have 5tb of data on a client (in addition to other clients). You want this data to be redundant across spindles as well as have archived backups on WHS?

Out of the box the only way this makes sense in WHS land is you put all the data in WHS shares, and do backups of the WHS to an external drive. Except in this case your data is 4tb, and its not going to be a simple single drive solution.

Even with synctoy I don't think you are going to get the archive solution you want (recover a file x days after its deleted). You would get this only if you backup the WHS (as above), but again it comes down to needing a 4tb+ backup drive.

The quick solution is to have a multiple drive external raid solution (drobo, etc), that will give you a single 4tb+ external backup solution.
 
I think I'm going to just leave the entire PC backed up the the WHS BD. I will put my critical data into the shares in addition to what is in the BD, this way I can have my cake and eat it too. I guess its not the ideal way to do it but it makes the most sense for me right now. the only issue I'm going to have is keeping private data out of the BD, such that other people in the house do no have access to it, but no one else in the house knows how to use WHS anyways so I guess the problem isn't that great.
 
Thats a brilliant idea. I may do the same. Heck, I may even get a little crazy and turn duplication on or actually back my stuff up the right way rather then depend on a server for backup.

Whats wrong with depending on the server? The whole reason I built it was for a backup solution... Sure I could get a bundle of external drives and put them on timers to turn on and off, but then I still have the problem with creating a bad backup and overwriting a good one with bad data...Not to mention having to remember to turn the drives on and off all the time or run them off timers. And then theres the whole What happens when an error occures problem...
 
A server, esp WHS as of late, can be used as backup. But theres so many reasons its not a true backup solution. Lets go thru a quick rundown off the top of my head as to why......house fire, flood, hurricane, tornado, theft, lightning strike, user error.

All Im saying is if something is that important, you need to do a real backup. I have about 35 digital pictures of my dad. Hes dead. I will never ever ever get another picture of him. I have those photos backed up onto WHS and duplicated, they are also on a CD I reburn every year, and on a cd at another location and I have emailed them to myself thru yahoo/gmail, and back to myself thru gmail/yahoo. See, for me to lose those pics I would have to lose 2 drives on my server ( theft, fire, etc...) have my CD thats in my closet stolen ( once again, theft , fire, etc...) my mothers house would have to simultaneously lose my other CD, and yahoo and googles servers would have to die. Thats a backup solution. Copying them to a shared folder is not.
 
I didnt want to start a new thread for this, but does anyone know how the "Enable Duplication for WHS Backups" work? If I check this and WHS keeps its existing backups duplicated, how would you go about restoring them if the system drive goes out?
 
A server, esp WHS as of late, can be used as backup. But theres so many reasons its not a true backup solution. Lets go thru a quick rundown off the top of my head as to why......house fire, flood, hurricane, tornado, theft, lightning strike, user error.

All Im saying is if something is that important, you need to do a real backup. I have about 35 digital pictures of my dad. Hes dead. I will never ever ever get another picture of him. I have those photos backed up onto WHS and duplicated, they are also on a CD I reburn every year, and on a cd at another location and I have emailed them to myself thru yahoo/gmail, and back to myself thru gmail/yahoo. See, for me to lose those pics I would have to lose 2 drives on my server ( theft, fire, etc...) have my CD thats in my closet stolen ( once again, theft , fire, etc...) my mothers house would have to simultaneously lose my other CD, and yahoo and googles servers would have to die. Thats a backup solution. Copying them to a shared folder is not.

Can you elaborate on how WHS is not a true back up solution b/c of user error?
 
Can you elaborate on how WHS is not a true back up solution b/c of user error?


by default WHS will keep the montly backup 6 months, weekly 3 weeks and daily 5 days.

Delete a file, go thru the backups later, you might not have the snapshot you need to get it back. Also if 1 drive dies in the WHS, your backups go away, usually the shared folders are ok as long as you have duplication enabled.

Delete a file in the folder shares? Say goodbye, no backup for that. WHS is a good backup plan, I won't lie, its my only backup plan, but still takes just one burglar and i'm toast.
 
Back
Top