I beleive the OP is referring to backing up to a media server over the
fiber channel to (possibly) fiber channel drives.

In this case you would create a seperate zone that includes all backup
clients and the server. When it's time to do backups move all hosts
into this zone. This requires some scripting on the switch side but I
know of at least one person who does this exact config.

Obviously the backup zone needs to include any members that the client
communicated with in the non-backup zone.

~F

On Mon, 20 Oct 2003 16:47:08 +0200, "Rene Köhnen-Wiesemes"
wrote:

I'm new to SANs so please excuse my ignorance. I've been reading
about zoning and RSCNs. From what I've read RSCNs are sent to all
members of a zone after a change in the port status occurs on a port
in that zone. For example, if all servers are in the same zone, and
one of them is rebooted, an RSCN is sent to all the other hosts in
that same zone to notify them of the event. At this time are the
other hosts in the zone "knocked offline" termporarily while they do
name server refresh? How can you prevent this? I've read a post that
somebody said to create one zone per port, this way it won't affect
any other hosts.

Yes, thats true. You should define a zone allways with only one FC-HBA
member.

What can you do if you have a backup type
environment where all hosts need to speak to one host (the backup
server)?

Sorry, I don't understand this question. Why should the client hosts speak
to the backup server over FC? Most of this solutions I know talk via IP for
Information/Metadata Interchange. What specific solution is that you speak
about?

René

-TIA