On Mon, Feb 09, 2009 at 11:56:54AM -0800, Gordon Johnson wrote:
> I hope this thread catches someone's attention. I've reviewed the root pool
> recovery guide as posted. It presupposes a certain level of network support,
> for backup and restore, that many opensolaris users may not have.
I di
Hi Gordon,
We are working toward making the root pool recovery process easier
in the future, for everyone. In the meantime, this is awesome work.
After I run through these steps myself, I would like to add this
procedure to the ZFS t/s wiki.
Thanks,
Cindy
Gordon Johnson wrote:
> I hope this t
I hope this thread catches someone's attention. I've reviewed the root pool
recovery guide as posted. It presupposes a certain level of network support,
for backup and restore, that many opensolaris users may not have.
For an administrator who is working in the context of a data center or a
Hi Marlanne,
Excellent question and thank you for asking...
We have a set of instructions for creating root pool snapshots and
root pool recovery, here:
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#ZFS_Root_Pool_Recovery
The zfs send and recv options used in this wik
On Mon, Nov 3, 2008 at 6:17 AM, Richard Elling <[EMAIL PROTECTED]>wrote:
> Cesare wrote:
>
>> Hi all,
>>
>> I've recently started down to put on production use for zfs and I'm
>> looking to how doing a backup of filesystem. I've more than one server to
>> migrate to ZFS and not so more server wher
Cesare wrote:
> Hi all,
>
> I've recently started down to put on production use for zfs and I'm
> looking to how doing a backup of filesystem. I've more than one server
> to migrate to ZFS and not so more server where there is a tape backup.
> So I've put a L280 tape drive on one server and use
[EMAIL PROTECTED] said:
> . . .
> We don't want to buy an Legato solution This will be overkill and is too
> expensive. Scripting with tar and other archievers is not the best solution
> for doing a backup.
Gerrit,
It seems you/they must already be scripting with ufsdump now. It's no
more diffi
Hello Gerrit,
Friday, January 19, 2007, 5:24:47 PM, you wrote:
GS> Hi,
GS> With the Flemish government we have more then 100 sites. Most of
GS> the time the backup is done on a DLT7000 or LTO tape device. A few
GS> sites are bigger and have a Legato backup solution.
GS> With UFS, the restore is
[EMAIL PROTECTED] wrote on 01/19/2007 10:24:47 AM:
> Hi,
>
> With the Flemish government we have more then 100 sites. Most of the
> time the backup is done on a DLT7000 or LTO tape device. A few sites
> are bigger and have a Legato backup solution.
>
> With UFS, the restore is easy on those s
On Tue, May 30, 2006 at 12:30:50PM +0200, Constantin Gonzalez Schmitz wrote:
> Hi,
>
> >>Yes, a trivial wrapper could:
> >>1. Store all property values in a file in the fs
> >>2. zfs send...
> >>3. zfs receive...
> >>4. Set all the properties stored in that file
> >
> >IMHO 3. and 4. need to be sw
Hi,
Yes, a trivial wrapper could:
1. Store all property values in a file in the fs
2. zfs send...
3. zfs receive...
4. Set all the properties stored in that file
IMHO 3. and 4. need to be swapped - otherwise e.g. files will
not be compressed when restored.
hmm, I assumed that the ZFS stream
On Tue, May 30, 2006 at 04:11:13AM +0200, Franz Haberhauer wrote:
> Is the idea of 'zfs send -p' to only send the properities in addition
> to the content or without content? Actually I would expect sending the
> poperties as the default for send and an option for receive not to
> apply the propert
Is the idea of 'zfs send -p' to only send the properities in addition to
the content or
without content? Actually I would expect sending the poperties as the
default for send
and an option for receive not to apply the properties - and have an
option (-p) for
send to send only the properties e.g.
Yep, thanks for digging that up. FYI, this is RFE 6421959 "want zfs
send to preserve properties ('zfs send -p')".
--matt
On Mon, May 29, 2006 at 02:21:44PM -0400, Jeff Victor wrote:
> An earlier response from Matt Ahrens, to a similar question:
>
> > 'zfs backup/restore' (now 'zfs send/receive'
Jeff Victor wrote:
Yes, a trivial wrapper could:
1. Store all property values in a file in the fs
2. zfs send...
3. zfs receive...
4. Set all the properties stored in that file
IMHO 3. and 4. need to be swapped - otherwise e.g. files will
not be compressed when restored.
- Franz
Franz Habe
Yes, a trivial wrapper could:
1. Store all property values in a file in the fs
2. zfs send...
3. zfs receive...
4. Set all the properties stored in that file
Franz Haberhauer wrote:
Jeff Victor wrote:
An earlier response from Matt Ahrens, to a similar question:
> 'zfs backup/restore' (now 'zf
Jeff Victor wrote:
An earlier response from Matt Ahrens, to a similar question:
> 'zfs backup/restore' (now 'zfs send/receive') currently only sends the
> filesystem's contents, and not its settings. This is useful if, for
> example, you want to use different settings on the remote side (eg.
An earlier response from Matt Ahrens, to a similar question:
> 'zfs backup/restore' (now 'zfs send/receive') currently only sends the
> filesystem's contents, and not its settings. This is useful if, for
> example, you want to use different settings on the remote side (eg. turn
> on compression)
18 matches
Mail list logo
