"Ryan, Lyle (US)" writes: >The server has an 11TB filesystem to store the backups in. I should >probably be fancier and split this up more, but not now. So I've got my >holding, state, and vtapes directories all in there.
In this scenario, I would think there's no point to a "holding" disk. I use a holding disk because my actual backup disk is external-USB and (comparatively) slow. So I backup to a holding disk on my internal SSD, releasing the client and the network as soon as possible, and then copy the backup to the backup drive afterwards. But in your case, I don't see any benefit. (But I'm certainly not an expert, so if somebody contradicts me, then follow their advice.) >And one bonus question: I'm assuming Amanda will just make vtapes as >necessary, but is there any guidance as to how many vtape slots I should >create ahead of time? If my dumpcycle=14, maybe create 14 slots just to >make tapes easier to find? If my memory is correct (I set mine up a long time ago), you would be better off just letting Amanda do what it wants/needs. That way, you don't have to worry about permissions / naming conventions / etc. --hymie!
