It seems like the zpool export will ques the drives and mark the pool
as exported. This would be good if we wanted to move the pool at that
time but we are thinking of a disaster recovery scenario. It would be
nice to export just the config to where if our controller dies, we can
use the
Sorry if this has been dicussed before. I tried searching but I
couldn't find any info about it. We would like to export our ZFS
configurations in case we need to import the pool onto another box. We
do not want to backup the actual data in the zfs pool, that is already
handled through
It seems like the zpool export will ques the drives and mark the pool as
exported. This would be good if we wanted to move the pool at that time but we
are thinking of a disaster recovery scenario. It would be nice to export just
the config to where if our controller dies, we can use the zpool
On Mar 25, 2010, at 6:11 AM, Wolfraider wrote:
It seems like the zpool export will ques the drives and mark the pool as
exported. This would be good if we wanted to move the pool at that time but
we are thinking of a disaster recovery scenario. It would be nice to export
just the config to
This assumes that you have the storage to replicate or at least restore all
data to a DR site. While this is another way to do it, it is not really cost
effective in our situation.
What I am thinking is basically having 2 servers. One has the zpool attached
and sharing out our data. The other
On Thu, March 25, 2010 10:20, Wolfraider wrote:
What I am thinking is basically having 2 servers. One has the zpool
attached and sharing out our data. The other is a cold spare. The zpool is
stored on 3 JBOD chassis attached with Fibrechannel. I would like to
export the config at specific
On Mar 25, 2010, at 7:20 AM, Wolfraider wrote:
This assumes that you have the storage to replicate or at least restore all
data to a DR site. While this is another way to do it, it is not really cost
effective in our situation.
If the primary and DR site aren't compatible, then it won't be
On Mar 25, 2010, at 7:20 AM, Wolfraider wrote:
This assumes that you have the storage to replicate
or at least restore all data to a DR site. While this
is another way to do it, it is not really cost
effective in our situation.
If the primary and DR site aren't compatible, then it
won't
On Thu, March 25, 2010 11:28, Wolfraider wrote:
Which, when I asked the question, I wasn't sure how it all worked. I
didn't know if the import process need a config file or not. I am learning
alot, very quickly. We will be looking into the HA cluster in the future.
The spare is a cold spare
We are sharing the LUNS out with Comstar from 1 big pool. In essence, we
created our own low cost SAN. We currently have our windows clients connected
with Fibrechannel to the COMSTAR target.
--
This message posted from opensolaris.org
___
zfs-discuss
On Mar 25, 2010, at 8:28 AM, Wolfraider wrote:
Which, when I asked the question, I wasn't sure how it all worked. I didn't
know if the import process need a config file or not. I am learning alot,
very quickly. We will be looking into the HA cluster in the future. The spare
is a cold spare
On Wed, Mar 24 at 12:20, Wolfraider wrote:
Sorry if this has been dicussed before. I tried searching but I
couldn't find any info about it. We would like to export our ZFS
configurations in case we need to import the pool onto another
box. We do not want to backup the actual data in the zfs
Yes, I think Eric is correct.
Funny, this is an adjunct to the thread I started entitled Thoughts on ZFS
Pool
Backup Strategies. I was going to include this point in that thread but
thought
better of it.
It would be nice if there were an easy way to extract a pool configuration,
with
all of the
On Wed, Mar 24, 2010 at 4:00 PM, Khyron khyron4...@gmail.com wrote:
Yes, I think Eric is correct.
Funny, this is an adjunct to the thread I started entitled Thoughts on ZFS
Pool
Backup Strategies. I was going to include this point in that thread but
thought
better of it.
It would be
14 matches
Mail list logo
