Sponsored Content
Operating Systems Solaris Local Full Backup and Restore ZFS Post 302390486 by tien86 on Thursday 28th of January 2010 05:42:42 AM
Old 01-28-2010
Thx man. I have a idea that use disk1 UFS filesystem and it can be mount when i boot -s by cdrom.

I did test work well but its looks not OK when combine UFS with ZFS jobs.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Full System Restore from 250 - V280R

Hello, Here is what I am trying to do. We have an old Enterprise 250 which we want to phase out. So plan is to move everything running on the 250 to an unused Sun Fire V280R. Here is what I decided to do: 1. Fresh Solaris 8 install on Sun 280R (disk0). Configure network and install... (1 Reply)
Discussion started by: mshafi
1 Replies

2. Solaris

Full backup and Restore

Dear All ; first how are you every body I'm just subscribed in your forum and i hope i found what i searched for along time . I'm not a Solaris specialist but i read more to build a Network Management Station depends on Solaris as OS and it is working good now . my problem is how to perform... (16 Replies)
Discussion started by: Basha
16 Replies

3. Solaris

after ZFS can not restore VTOC of disk..

I tried to use zfs .. only for test ..so when I take my test disks into zfs pool their VTOC changed .. and 7th slice does not appear now. How can I restore default VTOC to my disks. my machine is x86 .. SunFire X4200 .. so this disks do not have slices like sparc machines .. they have... (6 Replies)
Discussion started by: samar
6 Replies

4. Solaris

ZFS Restore Attempt

We currently have T2000 servers attached to Sun 3320 Storage Arrays. We run a database on the 3320 devices with the storage created through ZFS. We use 3 RAIDZ2 pools and then create our partitions from those. Now onto the question. If our T2000 fails and we swap out machines is there a way... (1 Reply)
Discussion started by: buckhtr77
1 Replies

5. Solaris

Restore from Flash Archive on local filesystem

I am doing a practice restore using a test UNIX(Solaris) system, and a SCSI Hard Drive whose slice 5 contains the Flash Archive file that I need to restore from. The test system is offline( no network ) and does not have external devices, such as tape drive. My goal is to somehow restore the... (9 Replies)
Discussion started by: the.gooch
9 Replies

6. Solaris

Emergency - restore a deleted zfs snapshot

Hi, I deleted a zfs snapshot because it was as big as the original zfs. After the snapshot was removed, all the data in the original zfs is gone. How this happened? Can I restore the snapshot? Please help. Thanks a lot! (5 Replies)
Discussion started by: aixlover
5 Replies

7. Solaris

Full zfs - cannot import

I installed Solaris 11 Express on my machine and created a raidz2 filesystem over 5 harddrives. Thas was a few months ago. Unfortunately, yesterday I made a mistake in free space calculation and tried to copy more data to the fs than how much space there was. When the fs got full, the... (5 Replies)
Discussion started by: RychnD
5 Replies

8. Solaris

New ZFS FS not seen on local zone

Hi , I added a new fs to the global zone and also did the zonecfg to add the FS to the zone but finally I do not see the new "FS" on the local zone. Even in th e/etc/zones/zone.xml the fs and the correct directory is mentioned. Any Idea please ? (4 Replies)
Discussion started by: manni2
4 Replies

9. UNIX and Linux Applications

Deja-dup make my / full. So I cannot restore my back up

The problematic directory is the following: /root/.cache/deja-dup This directory grows until my "/" is full and then the restoring activity fails. I already tried to create a symbolic link with origin another partition where I have more space. However during the restoring activity ... (4 Replies)
Discussion started by: puertas12
4 Replies
BACKUP_JOBS(8)						       AFS Command Reference						    BACKUP_JOBS(8)

NAME
backup_jobs - Lists pending and running operations in interactive mode SYNOPSIS
jobs [-help] j [-h] DESCRIPTION
The backup jobs command lists the job ID number and status of each backup operation running or pending in the current interactive session. This command can be issued in interactive mode only. If the issuer of the backup interactive command included the -localauth flag, the -cell argument, or both, those settings apply to this command also. To terminate operations that appear in the output, issue the backup kill command and identify the operation to cancel with the job ID number from this command's output. To check the status of a Tape Coordinator, rather than of a certain operation, use the backup status command. OPTIONS
-help Prints the online help for this command. All other valid options are ignored. OUTPUT
The output always includes the expiration date and time of the tokens that the backup command interpreter is using during the current interactive session, in the following format: <date> <time>: TOKEN EXPIRATION If the execution date and time specified for a scheduled dump operation is later than <date time>, then its individual line (as described in the following paragraphs) appears below this line to indicate that the current tokens will not be available to it. If the issuer of the backup command included the -localauth flag when entering interactive mode, the line instead reads as follows: : TOKEN NEVER EXPIRES The entry for a scheduled dump operation has the following format: Job <job_ID>: <timestamp>: dump <volume_set> <dump_level> where <job_ID> Is a job identification number assigned by the Backup System. <timestamp> Indicates the date and time the dump operation is to begin, in the format month/date/year hours:minutes (in 24-hour format) <volume_set> Indicates the volume set to dump. <dump_level> Indicates the dump level at which to perform the dump operation. The line for a pending or running operation of any other type has the following format: Job <job_ID>: <operation> <status> where <job_ID> Is a job identification number assigned by the Backup System. <operation> Identifies the operation the Tape Coordinator is performing, which is initiated by the indicated command: Dump (dump name) Initiated by the backup dump command. The dump name has the following format: <volume_set_name>.<dump_level_name> Restore Initiated by the backup diskrestore, backup volrestore, or backup volsetrestore command. Labeltape (tape_label) Initiated by the backup labeltapen command. The tape_label is the name specified by the backup labeltape command's -name or -pname argument. Scantape Initiated by the backup scantape command. SaveDb Initiated by the backup savedb command. RestoreDb Initiated by the backup restoredb command. <status> Indicates the job's current status in one of the following messages. If no message appears, the job is either still pending or has finished. number Kbytes, volume volume_name For a running dump operation, indicates the number of kilobytes copied to tape or a backup data file so far, and the volume currently being dumped. number Kbytes, restore.volume For a running restore operation, indicates the number of kilobytes copied into AFS from a tape or a backup data file so far. [abort requested] The backup kill command was issued, but the termination signal has yet to reach the Tape Coordinator. [abort sent] The operation is canceled by the backup kill command. Once the Backup System removes an operation from the queue or stops it from running, it no longer appears at all in the output from the command. [butc contact lost] The backup command interpreter cannot reach the Tape Coordinator. The message can mean either that the Tape Coordinator handling the operation was terminated or failed while the operation was running, or that the connection to the Tape Coordinator timed out. [done] The Tape Coordinator has finished the operation. [drive wait] The operation is waiting for the specified tape drive to become free. [operator wait] The Tape Coordinator is waiting for the backup operator to insert a tape in the drive. EXAMPLES
The following example shows that two restore operations and one dump operation are running (presumably on different Tape Coordinators) and that the backup command interpreter's tokens expire on 22 April 1999 at 10:45 am: backup> jobs Job 1: Restore, 1306 Kbytes, restore.volume Job 2: Dump (user.sunday1), 34 Kbytes, volume user.pat.backup Job 3: Restore, 2498 Kbytes, restore.volume 04/22/1999 10:45: TOKEN EXPIRATION PRIVILEGE REQUIRED
None. However, queuing any operation requires privilege, and it is possible to issue this command only within the interactive session in which the jobs are queued. SEE ALSO
backup(8), backup_interactive(8), backup_kill(8), backup_quit(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_JOBS(8)
All times are GMT -4. The time now is 02:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy