Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Strategies\s+for\s+DR\s+recovery\s+of\s+large\s+clients\s*$/: 8 ]

Total 8 documents matching your query.

1. Strategies for DR recovery of large clients (score: 1)
Author: Werner Kliewer <VKliewer AT MPI.MB DOT CA>
Date: Tue, 10 Sep 2002 10:29:48 -0500
I am working on our first TSM based DR plan for our data centre. We currently have a successfully tested several times plan using system specific tools, such as Sysback/6000 for AIX, BRM for AS/400,
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00339.html (16,301 bytes)

2. Re: Strategies for DR recovery of large clients (score: 1)
Author: Robin Sharpe <Robin_Sharpe AT BERLEX DOT COM>
Date: Tue, 10 Sep 2002 12:02:46 -0400
Werner, I feel your pain... ;) You have hit most of the major issues of disaster recovery with TSM squarely on the head. We have had similar experience in our testing... 4-6 hours to get the TSM serv
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00343.html (13,232 bytes)

3. Re: Strategies for DR recovery of large clients (score: 1)
Author: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>
Date: Tue, 10 Sep 2002 14:43:38 -0400
should one we An alternative which does not involve client resources is to do a move nodedata command to consolidate a node's data onto a set of tapes. David Ehresman
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00348.html (11,885 bytes)

4. Re: Strategies for DR recovery of large clients (score: 1)
Author: Steve Harris <Steve_Harris AT HEALTH.QLD.GOV DOT AU>
Date: Wed, 11 Sep 2002 09:32:05 +1000
Werner Robin suggests periodic full backups by changing the mode. A less intensive approach is to run selectives over parts of of your node every day, so that over a week/fortnight/ month you will ha
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00354.html (14,550 bytes)

5. Re: Strategies for DR recovery of large clients (score: 1)
Author: Salak Juraj <j.salak AT ASAMER DOT AT>
Date: Wed, 11 Sep 2002 12:07:11 +0200
Just 2 cents: Assuming that search for files spread over tape and tapes consumes much of your restore time, so that many small files count for significant amount of restore time while large files cou
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00363.html (18,756 bytes)

6. Re: Strategies for DR recovery of large clients (score: 1)
Author: Robin Sharpe <Robin_Sharpe AT BERLEX DOT COM>
Date: Wed, 11 Sep 2002 09:42:03 -0400
Juraj, Your scenario would be helpful to recover a lost filesystem or a lost client in the datacenter, but for Disaster Recovery, we must assume we'll be rebuilding the TSM server plus several critic
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00372.html (11,501 bytes)

7. Re: Strategies for DR recovery of large clients (score: 1)
Author: Salak Juraj <j.salak AT ASAMER DOT AT>
Date: Wed, 11 Sep 2002 17:08:15 +0200
Okay, I should have read your requirements more carefully, sorry Juraj
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00375.html (12,011 bytes)

8. Re: Strategies for DR recovery of large clients (score: 1)
Author: "Kauffman, Tom" <KauffmanT AT NIBCO DOT COM>
Date: Wed, 11 Sep 2002 09:54:23 -0500
Werner -- My experience is that a point-in-time restore will use what already exists as a starting point. We have several large AIX filesystems with a great deal of daily activity (delete/create file
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00378.html (14,238 bytes)


This search system is powered by Namazu