Solaris 11.3 -- I'm trying to create ZFS snapshots and backing them up to another pool...

Laserbeak · 04-29-2017, 11:06 AM

But I ran into a bunch of problems. I eventually solved all of them (I thought), but then when I restarted, I got a ton of errors..

Turns out that Solaris was trying to mount the same mountpoints from both the original pool and the pool with just backup snapshots on it. I got some to not mount by setting the mountpoint to "legacy" but it didn't seem to work with all the directories.

In the end, I had to run:

Code:

# zfs destroy snap

Does anyone backup their disk like this using zfs pools? Sun documentation says it's possible, but they prefer to save the pool to another computer. But mine is just on a second hard drive. I should have just disconnected it from the VM instead of destroying the pool. Maybe that's what you're supposed to do, back up then disconnect drive. Never have the drive connected at boot time... sorry for the rambling!

jlliagre · 04-30-2017, 03:32 AM

Quote:

Originally Posted by Laserbeak

But I ran into a bunch of problems. I eventually solved all of them (I thought), but then when I restarted, I got a ton of errors..

What problems?
What errors?

Quote:

Turns out that Solaris was trying to mount the same mountpoints from both the original pool and the pool with just backup snapshots on it. I got some to not mount by setting the mountpoint to "legacy" but it didn't seem to work with all the directories.

So what commands did you ran and what did they output?

Quote:

Code:

# zfs destroy snap

You can't destroy a snapshot that way, is "snap" a pool?

Quote:

Does anyone backup their disk like this using zfs pools?

You don't backup disks but file systems or volumes. Although recommended and more convenient if you want to restore individual files, there is no requirement to receive the exported pool, you can just save the stream sent to a file. Alternatively, you might disable the mountpoint property when receiving the stream using the "zfs receive -x mountpoint" option. See https://docs.oracle.com/cd/E53394_01...801/gbchx.html

Quote:

says it's possible, but they prefer to save the pool to another computer.

That makes sense. Storing the backup on a remote server is more secure.

Quote:

But mine is just on a second hard drive. I should have just disconnected it from the VM instead of destroying the pool. Maybe that's what you're supposed to do, back up then disconnect drive. Never have the drive connected at boot time... sorry for the rambling!

If disconnecting the drive is a mandatory post backup step, what's the point doing backups... ;-)

Laserbeak · 04-30-2017, 09:53 AM

Quote:

Originally Posted by jlliagre

What problems?
What errors?

So what commands did you ran and what did they output?

You can't destroy a snapshot that way, is "snap" a pool?

You don't backup disks but file systems or volumes. Although recommended and more convenient if you want to restore individual files, there is no requirement to receive the exported pool, you can just save the stream sent to a file. Alternatively, you might disable the mountpoint property when receiving the stream using the "zfs receive -x mountpoint" option. See http://<br /> ://docs.oracle.com/cd...801/gbchx.html

That makes sense. Storing the backup on a remote server is more secure.

If disconnecting the drive is a mandatory post backup step, what's the point doing backups... ;-)

Yes "snap" was a separate pool that contained a different hard drive. I don't recall the exact command I used but I gleaned it from the Sun (actually ORACLE) documentation to back it up. It was something along the lines of this, where rpool@rpool.04-28-2017 is a snapshot:

Code:

zfs send -Rv rpool@rpool.04-28-2017  | zfs receive snap