ADSM-L

Re: Backup taking too long

2005-08-01 13:11:27
Subject: Re: Backup taking too long
From: Ben Bullock <bbullock AT MICRON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 1 Aug 2005 11:11:09 -0600
        I'd be careful about the "Disable the back-up of security info" 
suggestion. In this world of SOX, HIPPA, and other govt. regulations, if the 
auditors find out you could possibly restore a critical file from TSM that does 
not have the correct ACLs, it could cause you a lot of pain and suffering on 
your hands. 

Ben


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Bos, Karel
Sent: Monday, August 01, 2005 10:54 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Backup taking too long

Hi,

Disable the back-up of security info and split your back-up into multiple 
domains/over multiple nodes. Also, you don't want to use memory eff. Back-ups 
and resourceutil will only go up to 10.

Regards,

Karel
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Scott Foley
Sent: maandag 1 augustus 2005 18:19
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Backup taking too long

I am backing up a large number of files and directories located on a Network 
Appliance.  I am using a Windows 2000 client to do this.  It is taking over 40 
hours to do the backup.  I also run out of memory at
times (ANS1028S).   Journaling worked great when the files were on a
Windows system, but journaling works only on a local file system.  I don't 
think I can use NDMP because the tape library is connected only to the Tivoli 
server.  Most of the time (and memory) is spent determining what files should 
be backed up.  There are over 1 million directories.


Total number of objects inspected: 7,819,693 Total number of objects backed up: 
 260,984
Total number of bytes transferred:    36.22 GB
Data transfer time:                4,579.15 sec
Elapsed processing time:           40:10:58

There are about 36 "root" directories so I could configure the Network 
Appliance to have 36 shares and back up each separately if that would help.  I 
think this would help with the memory problem.  I would
probably need to run multiple backups simultaneously though.    

I have added the following to the dsm.opt file

RESOURceutilization 14
MEMORYEFFICIENTBACKUP yes

Any suggestions on how to speed the backup up?  


Windows 2000 SP2 with 512 Meg of Memory
Client  Version 5, Release 1, Level 7.0
Server  Version 5, Release 1, Level 9.0

Scott Foley

<Prev in Thread] Current Thread [Next in Thread>