ADSM-L

Re: [ADSM-L] best backup method for millions of small files?

2009-04-30 04:04:03
Subject: Re: [ADSM-L] best backup method for millions of small files?
From: "Cheung, Richard" <Richard.Cheung AT SANTOS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 30 Apr 2009 17:33:28 +0930
When you 'copied' the directory, did the DATE of the directory change?? 

Thats probably why it didn't back anything new up.. 

And thats why incrbydates shouldnt be relied upon always - should always
do normal incremental backups as well


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Mehdi Salehi
Sent: Thursday, 30 April 2009 5:30 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] best backup method for millions of small files?

Hi,
I enabled the journal service for drive F: of a test windows-based TSM
client. Here is the interesting test results:
1- total filesystem size:14GB
2- used space: 370MB (pdf, doc, exe and ... other ordinary files)
3- I enabled journal
4- snapshot image backup was successful
5- the .jbbdb file in journal directory got populated
6- I copies a directory from c: for f:
7- the size of .jbbdb file changed (means journal service is working)
8- I performed a incremental-by-date for image backup
9- NOTHING was backuped!

Do you have any explanation for this?

Regards,
Mehdi

<html>
<body>
<font face="arial" color=#808080 size="-2"><img
alt="Santos Logo" src="http://www.santos.com/library/logo.gif";>
<br>Santos Ltd A.B.N. 80 007 550 923<br>
Disclaimer: The information contained in this email is intended only for the 
use of the person(s) to whom it is addressed and may be confidential or contain 
privileged information. 
If you are not the intended recipient you are hereby notified that any perusal, 
use, distribution, copying or disclosure is strictly prohibited. 
If you have received this email in error please immediately advise us by return 
email and delete the email without making a copy.</font>
<font face="arial" color=#008000 size="-2">Please consider the environment 
before printing this email</font>
</body>
</html>