Method 1

Method 1
Prev	Backing Up Raw Partitions	Next

Use MUPIP BACKUP -INCREMENTAL and RESTORE. Refer to the "MUPIP" chapter for more information. To save information since the last incremental backup, specify the -SINCE=INCREMENTAL flag. If you do not specify this flag, the entire raw partition is saved.


	You may only use MUPIP RESTORE to restore to a raw partition that is at least as large as the one that was backed up. If you have a MUPIP BACKUP from a raw partition, you may restore to a smaller partition by first restoring to a file, then using MUPIP EXTRACT and LOAD to go from that file to the new partition.

Example 1 (backup to a tape device):

        
	% mupip backup -incr DEFAULT /dev/rmt/0m
	MUPIP backup of database file /dev/dsk/c201d5s0 to /dev/ rmt/0m
	DB file /dev/dsk/c201d5s0 incrementally backed up in file /dev/rmt/0m
	832 blocks saved.
	% mupip create
	Database already exists on device /dev/dsk/c201d5s0
	Do you wish to re-initialize (all current data will be lost) [y/n] ? y
	Determining size of raw device...
	Raw device size is 426570K, 416570 GDS blocks
	Created file /dev/dsk/c201d5s0
	% mupip restore /dev/dsk/c201d5s0 /dev/rmt/0m
	RESTORE COMPLETED
	832 blocks restored

Example 2 (backup to multiple files):

        % mupip backup -incr DEFAULT db1.out
	MUPIP backup of database file /dev/dsk/c201d5s0 to db1.out
	DB file /dev/dsk/c201d5s0 incrementally backed up in file db1.out
	832 blocks saved.
	BACKUP COMPLETED.
	<updates made to the database>
	% mupip backup -incr -since=incr DEFAULT db2.out
	MUPIP backup of database file /dev/dsk/c201d5s0 to db2.out
	DB file /dev/dsk/c201d5s0 incrementally backed up in file db2.out
	817 blocks saved.
	% mupip create
	Database already exists on device /dev/dsk/c201d5s0
	Do you wish to re-initialize (all current data will be lost) [y/n] ? y
	Determining size of raw device...
	Raw device size is 426570K, 416570 GDS blocks
	Created file /dev/dsk/c201d5s0
	% mupip restore /dev/dsk/c201d5s0 db1.out,db2.out
	RESTORE COMPLETED
	1649 blocks restored