Disk/Tape backup?

Hi, All:
We have a new system installed Oracle 8.1.6. Now we are considering the method of Backup/Recovery.
In our system 2 disks and 1 tape device can be used for backup. And I think there are 2 ways to use them:
1). 1 disk : archive log;
1 disk : backup using by RMAN;
1 tape : backup's backup
2). 1 disk : archive log;
1 disk : the copy of the archive log;
1 tape : backup using by RMAN;
I don't know which is better? which is common?(The data size is about 20GB)
Can anybody give me some advices?
Thanks.
null

All you need to do is take the backup file from FRA to tape.
HTH--

Similar Messages

Database disk/tape backup

Hi,
Could someone help me as to weather the following is a plausable scenario.
-Lets say we have We have one database using ASM, ..
-Database is backed up to disk (+FRA) - regular intervals eacj day
-Database is then backed up to tape every 2 days
When the database is backed up to tape.. would it be normal to back up an entire copy of both the data disks and the FRA? or just the data disks? or just the backups currently on disk in the FRA?
High level (very simplistic) overview I know, but would appriciate any opinions
Thanks

All you need to do is take the backup file from FRA to tape.
HTH--

Hard disk crashed, restored data from tape backup, Firefox not showing bookmarks. What is the location of bookmarks & favourites to ensure I have restored the correct file?

Hard disk crashed (XP), restored files from tape backup using Retrospect onto new Windows 7 laptop. Started up Mozilla after restore but bookmarks and favourites are missing.
I still have access to the backup tape and files. I was wondering whether the bookmarks are kept anywhere special other than the Mozilla program file that I restored.

http://support.mozilla.com/en-US/kb/Recovering+important+data+from+an+old+profile

Removing disk backups after implementing Veritas tape backups

I was using RMAN with a catalog to backup to disk. Now we implemented RMAN backups using Veritas tape backup using the same catalog and I want to remove the old disk backups.
When I "crosscheck backup" and "crosscheck archivelog all" then "delete obsolete" it errored with the following:
==================================================================
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 08/29/2005 13:53:39
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
================================================================
I assume it is seeing one of the tape backups and wants to detete it.
How can I clearout these unnecessary disk backup sets without causing any problems?
Thank You,
.....Kevin

I found the solution:
RMAN> crosscheck backup;
RMAN> crosscheck archivelog all;
RMAN> delete obsolete device type disk;
-- Assuming redundency was 1 only one set is left in the disk directory...
RMAN> list backup;
-- Find the backup set key which lists the DISK backups.
-- List all the BSKeys
RMAN> delete backupset key1, key2, ..., keyn;
-- The files are gone...

How to manually run a Yearly Tape backup of a Volume in DPM?

I can run a manual tape backup by right clicking on the volume and choosing Long term backup, but it only runs the monthly tape backup job.
How can I manually run a Yearly Tape backup job?
I am using DPM 2010.
There must be a way to create a job that uses Yearly backup settings.
Or an alternative is to change the expiry date of the Backup if that is possible.
Thanks,

Although you cannot pick the recovery point date in the past to make a new recovery point from, you can run the DPM Power shell script in this
post to select a recovery goal to make a current backup for. The recovery point date would be that of the latest disk based recovery point for any goal selected.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Restore controlfile from leagato tape backup

I am using legato tool to perform rman tape backup.
I use the following script on legato to get the controlfile backup.
"backup current controlfile format '%d_%s_%p.ctrl'; "
If I lost the controlfile how do i restore controlfile from the tape. Assume that the DB in nomount stage.

Hi,
backing up autobackup controlfiles to legato is possible. All you have to do is to configure autobackup accordingly. By default autobackup controlfiles will get written to disk.
However i strongly recommend to use a rman backup catalog. This will save you a lot of time consuming trouble if you need to restore your database.
The rman catalog database itself does not need any license and is rather small (5 GB on disk, 512 MB memory).
Restoring the control file will be something like this:
set controlfile autobackup format for device type sbt to '%F';
restore controlfile from autobackup;
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de

Recovery window for tape backups

Hope someone can answer to my questions.
With RMAN you can maintain the number of tape backups that are needed for recovery purpose through the “delete obsolete recovery window” command. E.g. the command below ensures tape backups be kept for recovery within 31 days:
delete noprompt obsolete recovery window of 31 days device type 'SBT_TAPE';
Q:
1) If I use a disk area as pseudo tape area in my backups (through ORACLE.DISKSBT library parameter), I guess the above "delete noprompt obsolete recovery window" command would work on the pseudo tape area as well?
2) At my site the pseudo tape area is backed up to tape nightly through the system backup job, and the tape backups are kept for about 1 month by the tape system. To save space in the pseudo tape area on disk can I just set a small recovery window in the above DELETE command (say 1 day) , and relies on the actual tape system retention policy for oracle backups? How would this affect oracle’s ability to do recovery?
Thanks

1) I would never use a 'faked' tape as a permanent solution - only to test tape backup scripts - , as it slows down the backup/recovery process. From RMAN's point of view a pseudo tape works like a real tape, so all valid commands apply.
2) When you delete a backup, RMAN forgets it. RMAN is not aware of still available backups in the tape system, you have to recatalog the backups. That means overhead in manual maintenance and a source for possible errors.
Werner

Error in RMAN TAPE BACKUP

Dear Gurus,
I got the following error in RMAN TAPE backup.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on default channel at 09/20/2011 02:36:58
ORA-15028: ASM file '+ASMFLASH/gcprod/archivelog/2011_09_15/thread_2_seq_55857.2176.761912673' not dropped; currently being accessed
RMAN>
Recovery Manager complete.my RMAN BACKUP Script is:
rman target sys/*****@gcprod1 nocatalog << EOF
spool log to $v_bdest/clean_catalog_TAPE.log append;
run {
allocate channel c1 type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
#crosscheck backupset;
#crosscheck copy;
#crosscheck archivelog all;
# included on 21Jan2011 at 9:18 PM
#delete noprompt expired backup;
delete noprompt obsolete;
#delete noprompt expired archivelog all;
# included on 21Jan2011 at 9:18 PM
release channel c1;
exit
EOFMy RMAN RETENTION POLICY IS:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/app/oracle/product/10.2.0.1/db_1/dbs/snapcf_gcprod1.f';According to retention policy archivelogs of past 3 days should be present rest and all , i have written a script to delete and it is performing well from past 6 months, but now recently we got this error
we have enough archivelog space.
and the archive log pointing in this error is on 15th september archivelog.....today date is 20th september....
My archive log was stored in asm .... i went there and saw that still 15th september archivelogs are present there.
Please help me regarding this
Regards,
Vamsi.....

For RMAN topics, please use: {forum:id=74}.

FRA´s datafile directory and tape backups

Hi again,
I have tried to find relevant information for my question, but instead of finding answers (again) which may or may not be helpful I hope someone can explain me.
We are running 10Gr2 databases with FRA´s enabled, currently backupping all using Oracle´s suggested backup to Disk devices.
Since we have copies of the datafiles in the FRA which takes up quite some (productional) storage space we are asked to stop the Disk backups, and backup things up to the tape device, which underwater is a TSM library.
How would this affect the occupance of the FRA? Will the datafile directory in the FRA be moved to the "tape" device if we implement (solely) tape backups; or is it only the backupsets and autobackups which would then be moved to tape?
I have tried several setups for which I wanted to set the datafile, backupset and autobackup directory out of the FRA, but I have not found a (working) way yet to set the datafile directory apart from it.
Advice or help are greatly appreciated.
Robin

Changing the backup location from FRA to an external device will only effect backups (backupsets or image copies of datafiles,controlfiles,spfile,archivelogs). Possible (but not mandatory) components of FRA are archivelogs,backup pieces,controlfiles,online logs,image copies and flashback logs.
For performance reasons it's better to continue using the FRA as first backup device. Extend your backup strategy by backing the FRA itself to tape in regular intervals.
'BACKUP RECOVERY AREA' backs up recovery files created in the current and all previous flash recovery area destinations. Recovery files are full and incremental backup sets, control file autobackups, archived logs, and datafile copies. Flashback logs, the current control file, and online redo logs are not backed up.
The backup must go to a tape device, so RMAN issues an error if no sbt channels are allocated or configured.
Or use
'BACKUP RECOVERY FILES'. It backs up all recovery files on disk, whether they are stored in the flash recovery area or another locations on disk. Recovery files include full and incremental backup sets, control file autobackups, archived logs, and datafile copies.
Werner

Tape backups "stuck" in controlfile

At one point, there was a tape backup device configured and working. This tape device has since been removed, but there are still backups that were done to tape that are in the controlfile. These backups are quite old and rman knows they are obsolete, but it can't delete them, since the tape device (and channel) no longer exists.
I have tried many ways of trying to delete them, but I consistently end up with the same result of:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 09/11/2007 13:10:06
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
I am able to allocate a channel type of disk, but not sbt because it is not there, so I am having trouble getting rid of these entries. Any help is appreciated. Here is my configuration:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup1/oracle/%U';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/backup1/oracle/%U';
CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT '/backup1/oracle/%U';
CONFIGURE CHANNEL 4 DEVICE TYPE DISK FORMAT '/backup1/oracle/%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0.2/dbs/snapcf_test1.f'; # default

I was encountering the same:
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=149 devtype=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 1385 17-DEC-09
Backup Piece 1385 17-DEC-09 BE_bcl15skg_1_1
Backup Set 1386 17-DEC-09
Backup Piece 1386 17-DEC-09 BE_bdl15sog_1_1
Backup Set 1387 17-DEC-09
Backup Piece 1387 17-DEC-09 BE_bel15t6o_1_1
Backup Set 1570 08-FEB-10
Backup Piece 1570 08-FEB-10 BE_h5l5hl8f_1_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 02/18/2010 16:12:29
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
1387 B 0 U SBT_TAPE 17-DEC-09 1 1 NO TAG20091217T230904
1390 B A U SBT_TAPE 18-DEC-09 1 1 NO TAG20091218T230709
1392 B 0 U SBT_TAPE 18-DEC-09 1 1 NO TAG20091218T231024
1393 B A U SBT_TAPE 18-DEC-09 1 1 NO TAG20091218T231803
1395 B A U SBT_TAPE 21-DEC-09 1 1 NO TAG20091221T230506
1397 B 0 U SBT_TAPE 21-DEC-09 1 1 NO TAG20091221T230700
1398 B A U SBT_TAPE 21-DEC-09 1 1 NO TAG20091221T231439
1564 B A U SBT_TAPE 05-FEB-10 1 1 NO TAG20100205T232055
1565 B F U SBT_TAPE 05-FEB-10 1 1 NO TAG20100205T232057
1566 B A U SBT_TAPE 08-FEB-10 1 1 NO TAG20100208T230856
1569 B A U SBT_TAPE 08-FEB-10 1 1 NO TAG20100208T231941
1570 B F U SBT_TAPE 08-FEB-10 1 1 NO TAG20100208T231943
RMAN> change backuppiece tag 'TAG20091217T230904' uncatalog;
uncataloged backuppiece
backup piece handle=BE_bel15t6o_1_1 recid=1387 stamp=705885402
uncataloged backuppiece
backup piece handle=BE_bdl15sog_1_1 recid=1386 stamp=705884946
Uncataloged 2 objects
RMAN> change backuppiece tag 'TAG20091218T230709' uncatalog;
uncataloged backuppiece
backup piece handle=BE_bhl18h1g_1_1 recid=1390 stamp=705971249
Uncataloged 1 objects
RMAN> change backuppiece tag 'TAG20100208T231943' uncatalog;
uncataloged backuppiece
backup piece handle=BE_h5l5hl8f_1_1 recid=1570 stamp=710464784
Uncataloged 1 objects
RMAN> list backup summary;
RMAN> list backup;
RMAN> list backupset;
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 1385 17-DEC-09
Backup Piece 1385 17-DEC-09 BE_bcl15skg_1_1
Backup Set 1388 17-DEC-09
Backup Piece 1388 17-DEC-09 BE_bfl15t70_1_1
Backup Set 1389 17-DEC-09
Backup Piece 1389 17-DEC-09 BE_bgl15t75_1_1
Backup Set 1394 18-DEC-09
Backup Piece 1394 18-DEC-09 BE_bll18hle_1_1
Backup Set 1399 21-DEC-09
Backup Piece 1399 21-DEC-09 BE_bql1gej1_1_1
Backup Set 1404 22-DEC-09
Backup Piece 1404 22-DEC-09 BE_bvl1j2ra_1_1
Backup Set 1409 23-DEC-09
Backup Piece 1409 23-DEC-09 BE_c4l1lnak_1_1
Backup Set 1414 24-DEC-09
Backup Piece 1414 24-DEC-09 BE_c9l1obqf_1_1
Backup Set 1419 25-DEC-09
Backup Piece 1419 25-DEC-09 BE_cel1r0a2_1_1
Backup Set 1424 28-DEC-09
Backup Piece 1424 28-DEC-09 BE_cjl22t64_1_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 02/18/2010 16:15:05
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
RMAN> change backuppiece 'BE_bcl15skg_1_1' unavailable;
changed backup piece unavailable
backup piece handle=BE_bcl15skg_1_1 recid=1385 stamp=705884819
Changed 1 objects to UNAVAILABLE status
RMAN> change backuppiece 'BE_bcl15skg_1_1' unavailable;
changed backup piece unavailable
backup piece handle=BE_bcl15skg_1_1 recid=1385 stamp=705884819
Changed 1 objects to UNAVAILABLE status
RMAN> change backuppiece 'BE_bcl15skg_1_1' uncatalog;
uncataloged backuppiece
backup piece handle=BE_bcl15skg_1_1 recid=1385 stamp=705884819
Uncataloged 1 objects
RMAN> change backuppiece 'BE_bfl15t70_1_1' uncatalog;
uncataloged backuppiece
backup piece handle=BE_bfl15t70_1_1 recid=1388 stamp=705885409
Uncataloged 1 objects
RMAN> delete obsolete ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
no obsolete backups found
FINALLY FIXED!!!

RMAN with Netbackup - ALL Tape backups expired

Hello,
I am currently experiencing some issues between Netbackup and RMAN.
A bounce of the Netbackup server seems to have marked all our tape backups managed by RMAN as 'Expired'. This means RMAN can no longer locate any of the tape backups.
We have checked the rentention periods and the physical backups on the tapes and they seem to be ok. Therefore it would suggest a link problem between Netbackup and RMAN. We have tried bouncing the Netbackup servers again but this has not resolved the situation.
However sometimes the tape backups become available and but then become expired again.
I have also tried backing up to Tape since the bounce and the backup is successful, however 24 hours later it becomes expired despite Retention policy set to 4 weeks on both RMAN and Netbackup.
Please help!
Thank you

Hey;
I tried the delete obsolete; command initially. Admittedly, I didn't report that - so here's the output:
RMAN> delete obsolete;
using target database control file instead of recovery catalog
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=137 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=132 devtype=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 6 10-SEP-09
Backup Piece 6 10-SEP-09 c-1369681761-20090910-00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 07/24/2010 21:36:58
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
As for the changing default device type: someone had mentioned that the default device type was disk so I changed it to tape, tried the command, failed, then switched it back.
Just to reiterate: I don't have a tape drive on this box; never did. I'm not sure how two tape backups could have gotten there in the first place.
The oracle version is:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
and the OS version is:
$ uname -r; cat /etc/redhat-release
2.6.18-128.el5xen
Red Hat Enterprise Linux Server release 5.3 (Tikanga)
If push comes to shove, I can leave those two backups. There were a rather large number of them that I did successfully make go away. It just seems odd that I can't make these guys go away.
Thanks for the help; I appreciate it.
Doug

Advice on having a control file (online) on the same disk as backups

The following database files layout provides a no data loss configuration if the DiskArray #1, which stores the database, fails.
I have every think I need in the flash recovery area (DiskArray #2): backups, archived logs and online redo.
DiskArray #1:
- datafiles
- control file (mirror copy 1)
- Online redo log (mirror copy 1)
DiskArray #2: (flash recovery area)
- control file (mirror copy 2)
- Online redo log (mirror copy 2)
- archived logs
- backups
But some one raise the following scenario:
What happen if the diskArray #2, which has one control file copy, fails?
The instance should abort. Can it corrupt the current online redo, controlfile or a datafile?
If it does I would be in a dead end; of course I have regular offsite backups, but I may lose up to two weeks.
Lossing the database because the backup array fails is not acceptable.
Should I avoid any control file in the backup array?
Oracle recommend having control file copies in separate disk location and one of it in the flash recovery area.
Anyone have suggestions.
I am a bit scared

Can it corrupt the current online redo, controlfile or a datafile?Could that someone tell you why he thinks so ? I have seen loss of controlfile and loss of mirrored (duplexed) redo logs but that doesn't corrupt the good controlfile and redo logs and datafiles. unless someone or some process copies the corrupted files over to the good array !
You'd have to restart the instance with that controlfile excluded from the parameter file.
You'd lose your archivelogs and backups. If you have no tape backups you'd lose the ability to restore as well (being another "someone", I will ask "What happen if the diskArray #1 fails at the same time or 5 minutes after or 6 hours after diskArray #2 ?").
Hemant K Chitale
http://hemantoracledba.blogspot.com

RMAN restore from monthly tape backup

hello!
i have one more question regarding rman and tape backups: we don't want to store the rman recovery information in a separate database, so all the information is in the control files. but for revision we need to save one full backup per month. in addition to the databases we need files from different servers etc. on this tape-backups. so we decided to keep one tape set per month in a safe place -> is it possible to restore a rman backup from this tapes, e.g. 3 years afterwards (on a different machine)? thanks.
bye,
christian

Hi christian,
Can you give more info?
As I understand it you do not want to use a recovery catalog ("we don't want to store the rman recovery information in a separate database").
But if you store the rman backup info in the controlfile only you will limit the amount of rman information to your init parameter control_file_record_keep_time.
Do you make rman backups to tape directly using a MML or do you make rman backups to disk which than get copied to tape (OS backup)?
Regards,
Tycho

Performance issue in tape backup

Friends,
Our tape backup is implemented with help of Veritas Netbackup,for one of our servers,tape backup is taking too much long time. I generated AWR report during the ongoing backup and noticed the below stats:-
Top 5 Timed Events
Event
Waits
Time(s)
Avg Wait(ms)
% Total Call Time
Wait Class
Backup: sbtwrite2
36,186
300,497
8,100
1,442.5
Administrative
CPU time
17,920
85.4
Backup: sbtbackup
38
1,892
48,000
9.0
Administrative
log file parallel write
112,632
1,378
12
6.6
System I/O
control file parallel write
57,983
1,075
19
5.1
System I/O
What will be the next troubleshooting steps ?
Any guidance will be highly appreciated.
Thanks in advance.

The tape drive is likely the constraint. It cannot write fast enough to handle 4 channels streaming datafiles to it.
I would guess that the datafiles are also going over the network to the media manager. You need to check the network throughput for that link as well.
Hemant K Chitale

How do I use a Mac Mini + Airport Express + Time Machine disk to backup another iMac

How do I use a Mac Mini + Airport Express + Time Machine disk to backup another iMac?
The question pretty much says it all.
I have a Mac Mini with an attached 3TB Hard Drive used for Time Machine Backups.
I have an Airport Extreme base station which services that machine plus several others.
I would like to backup my new iMac and a MacBook Pro to the Mac Mini.
What do I need to do on the mini to export that hard drive so that it can be used as a Time Machine target from the other systems?
All systems are running 10.6.8.

Well you would have to do backups over a network which is much slower and has highest chance of becoming corrupt. I think your best option would be to get an apple time capsule to act as a network and back if thats how you wanna do that

Disk/Tape backup?

Similar Messages

Maybe you are looking for