Sponsored Content
Full Discussion: Backup sun Solaris Server
Operating Systems Solaris Backup sun Solaris Server Post 302984147 by Laila on Friday 21st of October 2016 05:50:01 AM
Old 10-21-2016
it is an UFS filesystems
 

6 More Discussions You Might Find Interesting

1. Solaris

Getting Server Model from Sun Solaris

What command to get server model from a solaris 5.10? (4 Replies)
Discussion started by: ryandegreat25
4 Replies

2. Solaris

How to boot a sun Solaris server?

Hi everyone, I have searched on google and sun documentation but it's still not clear for me; how do we boot a sun Solaris server? I know what to do but only from this step: 1- start /SYS 2- start /SP/console The system go to to the prompt OK, then we use the BOOT command. My... (9 Replies)
Discussion started by: adilyos
9 Replies

3. UNIX for Advanced & Expert Users

Backup Win server 08 onto Solaris

Greetings fellows, So, we have a Win8 server which is a profile server; its main purpose is to have a shared disc called Homes for roaming profiles. We want to create a backup, and copy files from this "Homes" drive onto SOlaris. We have read we could do it with rsync. Another engineer,... (1 Reply)
Discussion started by: sanz.rigo
1 Replies

4. Solaris

Making HDD backup in sun Solaris system

Hello to all, I have Fujitsu Celzius M470 workstation which has Sun solaris system installed and want to make a complete backup of the hard drive. The existing HDD is SATA II, 500 GB. I don't have much experience working with SUN solaris systems (not at all) but have some experience with... (5 Replies)
Discussion started by: Mick
5 Replies

5. Solaris

Solaris 11 AI Server Backup existing servers?

Hey Guys i've got a question about the AI Server. Is there any possibility to backup existing servers to reinstall them automaticly by using the AI Server? Regards Marcus (3 Replies)
Discussion started by: Marcusg562
3 Replies

6. Solaris

Sun Server and Solaris 7 Inquiry

Greetings! Will be firing up the good ole pizza box, soon. Does anyone know if Solaris 7 is still okay to use? Last time I attempted was 2006. Thank you in advance, ControlTomato (6 Replies)
Discussion started by: ControlTomato
6 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 12:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy