Sponsored Content
Full Discussion: ZFS question.
Operating Systems Solaris ZFS question. Post 302370593 by jlliagre on Thursday 12th of November 2009 01:21:32 AM
Old 11-12-2009
Not only snapshots can't be written to but also ZFS pools can't be mounted more than once. I guess the OP want to send that snapshot to another server and then clone it to be used as regular read-write filesystem.

Back to the subjet, that kind of "backup" strategy should generally work but is quite risky with a database. What you are suggesting is exactly the same as asking if an application can recover from an abrupt power off (or a kernel panic). It might or it might not, and a database is probably more prone to data corruption than many other given the fact inconsistencies that might happen when a write operation is interrupted in the middle.
If you can stop the database, there is no doubt this will work. If you want to leave the application running, you should ask your DBA about how to properly hot-backup your configuration. Something like "being backup" or "archivelog" mode might help there.
 

10 More Discussions You Might Find Interesting

1. Solaris

ZFS question

How does one set a size limit on a ZFS filesystem? It seems every ZFS FS I create has the same size limit as the parent Zpool. I want to create an FS with a much smaller limit. how? Thanks in advance my friends. (3 Replies)
Discussion started by: akbar
3 Replies

2. Solaris

ZFS Question

We are looking into testing ZFS at our location. Because we are a government agency we have security and auditors breathing down our neck to make sure we are not opening any security holes. My question is are there any ports or security concerns I would need to address if implemnting a ZFS file... (3 Replies)
Discussion started by: rkruck
3 Replies

3. Solaris

ZFS pool question

I created a pool the other day. I created a 10 gig files just for a test, then deleted it. I proceeded to create a few files systems. But for some reason the pool shows 10% full, but the files systems are both at 1%? Both files systems share the same pool. When I ls -al the pool I just... (6 Replies)
Discussion started by: mrlayance
6 Replies

4. Solaris

zfs-acronym

zfs-zeta bye filesystem or zope filesystem which is correct (2 Replies)
Discussion started by: kishanreddy
2 Replies

5. Solaris

Are you using ZFS ?

With Solaris 11 coming out with a requirement of ZFS on the root disk, I was curious to know who is using the Zeta File System now? I have been using ZFS for the past year and don't plan to go back to UFS since ZFS is much more reliable and easier to maintain. (13 Replies)
Discussion started by: bluescreen
13 Replies

6. Solaris

ZFS

what are all the advantages of ZFS comparing to UFS SVM what is the use of creating file system in a file system in ZFS (15 Replies)
Discussion started by: dinu
15 Replies

7. Solaris

ZFS

Hi, I need some advice please. I have this server with a couple of zpools, lets call them pay_serv ukb_pool There are two zones attached to these pools. When I do a zfs list I see this pay_serv 8.41G 265G 8.41G /pay_serv ukb_pool 79.8G 194G 23K /ukb_pool ukb_pool/temp_ps 9.11G... (4 Replies)
Discussion started by: giles.cardew
4 Replies

8. Solaris

ZFS mirroring

Hello, I just build a Solaris 10 server on an x86 box. I forgot to mirror the two disks when I install the OS. Can I get some help with this? I have this # zpool list rpool 278G 5.77G 272G 2% ONLINE - # zpool status pool: online state: ONLINE scan: none requested config: ... (12 Replies)
Discussion started by: bitlord
12 Replies

9. Solaris

Solaris ZFS question

What I am trying to do is reuse space that was used from an old solaris zone and take that space used in the 2 disk mirror from the 2nd zpool and relocate it to /var/audit in the root pool. The pysical server has 4 disks. 2 disks are a mirrored root zone(c1t0d0s0,c1t1d0s0) and the other were the... (1 Reply)
Discussion started by: jpolachak
1 Replies

10. Solaris

Solaris ZFS and reservations question

I'm having trouble increasing my reservations on some ZFS filesystems, although there seems to be enough space in the zpool, and no constraints on the parent device. Note that I'm using refreservation instead of reservation, so I'm not constrained by the reservation on the parent device (or... (1 Reply)
Discussion started by: akbar
1 Replies
BACKUP_DBVERIFY(8)					       AFS Command Reference						BACKUP_DBVERIFY(8)

NAME
backup_dbverify - Checks the integrity of the Backup Database SYNOPSIS
backup dbverify [-detail] [-localauth] [-cell <cell name>] [-help] backup db [-d] [-l] [-c <cell name>] [-h] DESCRIPTION
The backup dbverify command checks the integrity of the Backup Database. The command's output indicates whether the Backup Database is damaged (data is corrupted) or not. If the Backup Database is undamaged, it is safe to continue using it. If it is corrupted, discontinue any backup operations until it is repaired. CAUTIONS
While this command runs, no other backup operation can access the Backup Database; the other commands do not run until this command completes. Avoid issuing this command when other backup operations are likely to run. The backup savedb command repairs some types of corruption. OPTIONS
-detail Reports the number of orphaned blocks found, any inconsistencies, and the name of the server machine running the Backup Server that is checking its copy of the database. -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more details, see backup(8). -cell <cell name> Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8). -help Prints the online help for this command. All other valid options are ignored. OUTPUT
The command displays one of the following two messages: Database OK The database is undamaged and can be used. Database not OK The database is damaged. You can use the backup savedb command to repair many kinds of corruption as it creates a backup copy. For more detailed instructions, see the OpenAFS Administration Guide chapter about performing backup operations. The -detail flag provides additional information: o The number of orphan blocks found. These are ranges of memory that the Backup Server preallocated in the database but cannot use. Orphan blocks do not interfere with database access, but do waste disk space. To free the unusable space, dump the database to tape by using the backup savedb command, and then restore it by using the backup restoredb command. o Any inconsistencies in the database, such as invalid hostnames for Tape Coordinator machines. o The name of the database server machine on which the Backup Database was checked, designated as the "Database checker". For a detailed trace of the verification operation, see the /var/log/openafs/BackupLog file on the indicated machine. You can use the bos getlog command to display it. EXAMPLES
The following command confirms that the Backup Database is undamaged: % backup dbverify Database OK The following command confirms that the Backup Database is undamaged and that it has no orphan blocks or invalid Tape Coordinator entries. The Backup Server running on the machine "db1.abc.com" checked its copy of the Database. % backup dbverify -detail Database OK Orphan blocks 0 Database checker was db1.abc.com PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged onto a server machine as the local superuser "root" if the -localauth flag is included. SEE ALSO
BackupLog(5), backup(8), backup_restoredb(8), backup_savedb(8), bos_getlog(8) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 BACKUP_DBVERIFY(8)
All times are GMT -4. The time now is 05:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy