cloning staging strategy

Question

We have to implement cloning and staging so We thought about two ways. 1) writing to disk1, cloning from disk1 to disk2, and than staging from disk1 to pool1 and from disk2 to pool2 2)writing to disk1 then staging to pool1 and finally clone from pool1 to pool2. Can you please advise? has anyone tried such ways? thanks

DavidHampson · Accepted Answer

In your script check the number of copies in the mminfo output you use to generate your clone/stage list - if copies=1 then it is uncloned, if copies>1 then it has been cloned. You also may wish to keep the backup on disk for several days to facilitate recoveries, make your tape clone copy immediately for offsite backups, then stage the data to onsite tape after several days to free up disk space.

The clone will be identical to the original, that is why it is a clone?

DavidHampson · Answer

I would suggest;* write to disk 1 (and possibly disk 2)* clone disk 1 to pool 1* stage disk 1 to pool 2The reasoning would be that virtual devices tend to be cheaper and thus you may have more available so can match 1 to 1 devices with physical devices, plus there would be some benefits regarding tape handling.

yassine2 · Answer

thank you David for your help How can I be sure that data won't be staged before being cloned so that clone won't be identical to origin?

ble1 · Answer

You can't be sure as that depends on staging policy and available space on disk in the first place. What is always a good practice is to have script which checks disk and tape; if it was staged before cloned that script checking up tapes will pick it up.

yassine2 · Answer

Now I have to learn Windows Scripting to do that.thank you David.If you have some script it will be great.anyway thank you very muchregards

DavidHampson · Answer

Well my scripting is Solaris and it may not fit what you wish to do anyway (plus it will be over 700 lines long when I get the load balancing function in it so it will be pretty confusing for you).

NetWorker

Was this post helpful?