George,
In the case where you lose the original, but still have the clone, mark the
savesets on the original tape "suspect". I believe that this will cause
NetWorker to ask for the clone tape by default. If you delete the original
tape from the media DB it will also delete the index files for the affected
savesets and you will have to recover them from the clone. If you still have
the original tape and want to re-label it for some reason, this will leave
the clone tape intact, and the indexes available for browsing.
For how the tapes are named, take the following example.
Assume all of your tapes fit in the range 000001 to 005000. You just label
them into whichever pools you see fit. Lets say NetWorker is cloning a tape
in the "Default" pool (volume 000123) to a tape in the "Default Clone" pool
(volume 000171) and runs out of space on the clone tape. It will merely
choose another tape in the correct clone pool "Default Clone" (perhaps
volume 001723).
In your case it sounds as if you have Auto-media management switched on and
expect NetWorker to label a blank tape. Using your example, the second tape
would be called "Full_clone.002". Remember, when you clone a volume, you are
really cloning all the savesets on the volume. When you tell NetWorker to
clone a volume, it makes a list of all the savesets on the volume and then
proceeds to copy the savesets, one by one, to the clone medium. The clone
tape will not be multiplexed and is therefore not an exact copy of the
original tape.
regards
Andrew McGeorge
-----Original Message-----
From: George Sinclair [mailto:George.Sinclair AT noaa DOT gov]
Sent: 16 April 2003 2:57:AM
To: Andrew McGeorge
Cc: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] A few questions on cloning
Thanks for your response, Andrew. In regards to question 1, I guess
you're suggesting that to control which Storage Node/library/device is
used for the clone, you have simply to select the appropriate devices
under the clone pool configuration and make sure that the ones you don't
want used are not selected since you might have eligible tapes in a
library that you don't want used but might otherwise be used if you
failed to discriminate.
For the question about removing the original volume, I meant either
removing it using the 'remove' feature under volumes window or
re-labeling the original tape. But in either case, I'm assuming you
don't have the original volume for what ever reasons, and all you have
is the clone. Can you recover from the clone same as the original.
For the last question, I was a little in t he dark about how NetWorker
identifies a clone volume or rather what naming convention does it use.
Regards,
George
Andrew McGeorge wrote:
>
> ----------------------------------------------------------------------
> This email message and attachments are confidential to our
> organisation and subject to legal privilege. If you have received
> this email in error, please advise the sender immediately and destroy
> the message and any attachments. If you are not the intended recipient
> you are notified that any use, distribution, amendment, copying or any
> action taken or omitted to be taken in reliance of this message or
> attachments is prohibited. You can read our Privacy Policy here:
> www.asbbank.co.nz/privacystatement.stm
> ----------------------------------------------------------------------
>
> ---------------------------------------------------------------
>
> -----Original Message-----
> From: George Sinclair [mailto:George.Sinclair AT NOAA DOT GOV]
> Sent: 15 April 2003 10:22:AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: [Networker] A few questions on cloning
>
> Hello,
>
> I'm considering cloning some volumes, but I've never used this
> capability of NetWorker before, so I had a few questions before
> attempting this:
>
> 1. Is it possible to clone an LTO tape to an SDLT or vice versa if the
> drives are in different libraries, both attached to the storage node
> server? Here, I'm assuming that there would be enough space on the
> target tape to hold the source. We don't have mixed drives in any of our
> libraries so the operation would have to be able to communicate across
> libraries.
>
> Yes it is. If it is a manual cloning operation, use the pool definition to
> ensure which SN is used. If it is an automatic cloning operation at the
end
> of a savegrp, specify the "Clone Storage Node".
>
> 2. When cloning a volume, is there a way to specify which tape to use
> for the clone?
> For example, let's suppose I create a clone pool named Full_clone, and I
> have a label template named Full_clone using .001-999 (typical volume
> would look like Full_clone.001) and I want to clone source volume
> Full.001, then how do I tell it to clone this to say Full_clone.005
> rather than Full_clone.001?
>
> I find that it if you mount the Clone tape before you start cloning, this
> works,
>
> 3. Is there a way to specify the device to use for the clone tape?
>
> Pool definition.
>
> 4. What happens if you remove the original volume, but you still have
> the clone volume? Can this be mounted and read from just as if it was
> the original?
>
> By remove, do you mean "delete from the media db and file index"? If so
this
> will make the index for the savesets on that tape become "recoverable".
The
> clone tape will still be good though.
> If you want to scratch the original tape, just label it.
>
> 5. Will the cloning operation span tapes if the target tape is unable to
> hold all the source tape?
>
> Yes, no problem.
>
> 6. If this happens, what should the next clone volume be called? For
> example, if your template looked like "Full_clone.001-999", and you
> hadn't used any of these yet, and you cloned Full.001, but it was unable
> to fit on the first clone tape (Full_clone.001) then would NetWorker put
> the rest on Full_clone.002, or would it refer to the second volume also
> as Full_clone.001? I don't use barcodes on the tapes that I will be
> cloning -- these have stick labels I create manually -- so I just wanted
> to know what label names I should put on the clone volumes.
>
> It is important to remember that you are not cloning volumes. When you
> select a volume to clone, a list of all savesets on the volume is created,
> and all savesets are copied to another volume.
>
> regards
> Andrew McGeorge
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
========================================================================================
This email message and attachments are confidential to our organisation and
subject to legal privilege. If you have received this email in error, please
advise the sender immediately and destroy the message and any attachments. If
you are not the intended recipient you are notified that any use, distribution,
amendment, copying or any action taken or omitted to be taken in reliance of
this message or attachments is prohibited. You can read our Privacy Policy
here: <http://www.asbbank.co.nz/privacystatement.stm>
=========================================================================================
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
