The file server is a virtual machine on one of our ESX servers. The VM is a
single processor (2.5GHz Xeon), 768M RAM - SAN storage controlled by a
FAStT700.
The secret ingredient may lie in the often shunned 'memoryefficient yes' in
the client's dsm.opt.
-Ken
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Troy Frank
Sent: Thursday, March 09, 2006 1:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Journaling/Linux
Ditto. on one of our bigger file servers, ~1.3million files, 2-cpu
2.4ghz, 2.5GB RAM, SAN attached storage (that gets ~100MB/sec
throughput), it take us 45min to get through a backup. This seems to be
almost 20X that fast.
>>> bbullock AT MICRON DOT COM 03/09/06 10:23 AM >>>
Wow,
I don't think I have ever seen 20 million objects examined and
processed in 2 hours. What kind of hardware do you have behind that?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of
Mueller, Ken
Sent: Thursday, March 09, 2006 8:23 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Journaling/Linux
We have numerous Linux/Samba file servers in production running under
VMWare ESX (we run almost everything under ESX). Here are the results
from our largest document imaging server (lots of small files - ext3
file system):
03/09/2006 00:24:41 --- SCHEDULEREC STATUS BEGIN
03/09/2006 00:24:41 Total number of objects inspected: 20,622,343
03/09/2006 00:24:41 Total number of objects backed up: 19,769
03/09/2006 00:24:41 Total number of objects updated: 0
03/09/2006 00:24:41 Total number of objects rebound: 0
03/09/2006 00:24:41 Total number of objects deleted: 0
03/09/2006 00:24:41 Total number of objects expired: 2,432
03/09/2006 00:24:41 Total number of objects failed: 1
03/09/2006 00:24:41 Total number of bytes transferred: 1.25 GB
03/09/2006 00:24:41 Data transfer time: 40.49 sec
03/09/2006 00:24:41 Network data transfer rate: 32,469.21 KB/sec
03/09/2006 00:24:41 Aggregate data transfer rate: 157.78 KB/sec
03/09/2006 00:24:41 Objects compressed by: 0%
03/09/2006 00:24:41 Elapsed processing time: 02:18:52
03/09/2006 00:24:41 --- SCHEDULEREC STATUS END
Client - 5.2.2.0
Server - 5.2.4.2
-Ken Mueller
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf
Of
Gill, Geoffrey L.
Sent: Wednesday, March 08, 2006 3:36 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Journaling/Linux
All indications from searching manuals seem to indicate Journaling is
not available on anything except Windows clients. If this is true why
hasn't IBM moved this utility into other platforms? It's not like came
out this year.
I've got a Windows box with over a million files that is moving to
Linux.
Before we installed the Journaling service this box took over 12 hours
to back up and now its about an hour. How will TSM handle this on a
Linux platform? Anyone with a similar situation?
The reason for the stupid question is because I'm told that Netbackup
has it available for Linux, and as usual around here I get the bad
wrap
and they claim to be so much better.
Thanks,
Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: < mailto:geoffrey.l.gill AT saic DOT com > geoffrey.l.gill AT saic DOT
com
Confidentiality Notice follows:
The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.
|
