Bootstrap after cloning

Question

Hello,

Does anybody know why bootstrap can't go on a volume, that have just been cloned?
I backup few servers into one backup pool with 7 empty volumes, and then I clone them automatically to clone pool with 7 volumes also.
The whole backup takes 6 full volumes and about 75% of the last one volume, so there is some space left.
The problem is that I get an alert that NetWorker needs a volume from backup pool to write bootstrap on it, after clone operation is finished.
The last one volume from backup pool is 75% full and mounted as read-only, while the volume from clone pool is mounted as write-enabled.
So what should I do to make NW change the status of this volume after finishing cloning to writable and write down boostrap?

regards,
WS

ble1 · Answer

With automatic cloning you will see following: data saving, then data cloning, then bootstrap and then bootstrap cloning. To change and make it the way you want use script - what you see with automatic cloning is expected behaviour.

vsemaska · Answer

I'm glad I read this forum. We use scripts to clone our backups but never thought to clone the bootstraps. I'll have to add that. Should I clone all bootstraps I find or only the latest one?

I do have another question. We use our clones for DR, they're stored off-site. What I want to know is should we also clone the file indexes that are on the tapes as well. In case of disaster would that speed up recovery?

Thanks,
Vic

Message was edited by:
Victor Semaska

ble1 · Answer

Clone them all - they are not big.As for index cloning, I would suggest to do that too.

vsemaska · Answer

Thanks Hrvoje,As for the indexes a lot of them are huge. I assume cloning just the latest version would be OK?Vic

ble1 · Answer

It depends on their retention, but if you start now I believe everything should be fine.

NetWorker

Bootstrap after cloning

Was this post helpful?