ADSM-L

[ADSM-L] TSM 6.1 de-duplication scenario

2009-05-03 06:26:14
Subject: [ADSM-L] TSM 6.1 de-duplication scenario
From: Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sun, 3 May 2009 13:22:01 +0300
Hello Everybody,
I am testing TSM 6.1 de-duplication in TSM Server 6.1 for AIX and TSM Client 
6.1 for AIX.
After careful reading TSM Server Administration Guide, which is quite weak from 
de-duplication point of view, I tried to test next scenario:

1.     Environment preparation:
-         define FILE device class for primary backup pool;
-         define primary backup pool DBK1 (device class FILE, RECLAIM=60, 
DEDUPLICATE=yes, IDENTIFYPROCCESS=0);
-         define TAPE device class for copy pools;
-         define on-site copy pool DCP1 (device class TAPE, DEDUPLICATE=no);
-         define out-of-country copy pool DCP2 (device class TAPE, 
DEDUPLICATE=no);
-         define disaster site copy pool DCP3 (device class TAPE, 
DEDUPLICATE=no);

2.     Running backups (no client compression):
-         run full backup for databases and selective backup for file systems 
(the first time and periodically later - for example, 2 times per month);
-         run incremental backups for databases and file systems all the other 
days;
-         copy DBK1 to on-site copy pool DCP1;
-         copy DBK1 to out-of country copy pool DCP2 and check out FULL and 
FILLING volumes by MOVE DRDATA;
-         copy DBK1 to disaster site copy pool DCP3 and check out FULL and 
FILLING volumes by MOVE DRDATA;
-         backup TSM database to tape;
-         enable de-duplication by IDENTIFY DUPLICATE DBK1 NUMPROCESS=1;
-         stop idle de-duplication process by IDENTIFY DUPLICATE DBK1 
NUMPROCESS=0;
-         start reclaim process by RECLAIM STGPOOL DBK1.

Expectations:
1)     full or incremental backups are running without de-duplication process 
for best performance;
2)     copy operations are running without de-duplication process for best 
performance;
3)     all copy pools contain data without de-duplication for safety;
4)     data in DBK1 is de-duplicated after completion of all copy operations;
5)     disk space is released in DBK1 by reclaim process on TSM server;
6)     de-duplication process in DBK1 is not changing status of DCP1, DCP2 and 
DCP3 copy pools.

 It looks as working scenario, but I will deeply appreciate any comments and 
suggestions.
Kindest regards,


Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme 
DOT com<mailto:G.Solonovitch AT bkme DOT com>

Please consider the environment before printing this Email


Please consider the environment before printing this Email.

________________________________
"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."

<Prev in Thread] Current Thread [Next in Thread>
  • [ADSM-L] TSM 6.1 de-duplication scenario, Grigori Solonovitch <=