We're using NDMP to backup from a nearstore device.
Our legato software was / is having problems when backing up the volumes that I have CIFS stuff on. Legato would time out and not complete a full. Legato did not have problems doing an incremental on those volumes.
Turns out our problem was a timeout on catalogue creation. Legato would pause for a good hour before starting to transfer data to tape. The problem got worse when we added more and more users to the volume.
We had to modify the time out values in legato to allow it to finish creating the catalogue. As far as I know legato still behaves this way. I don't have current figures on how long legato is now taking to create the catalogue currently.
We finally tracked this down to the thousands of small files that our windows users keep in their home folders. Our UNIX files take up more room but they are fewer and bigger than the windows files so we don't have the legato issue on the volume we use for NFS.
NOTICE - This communication is intended ONLY for the use of the person or entity named above and may contain information that is confidential or legally privileged. If you are not the intended recipient named above or a person responsible for delivering messages or communications to the intended recipient, YOU ARE HEREBY NOTIFIED that any use, distribution, or copying of this communication or any of the information contained in it is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone and then destroy or delete this communication, or return it to us by mail if requested by us. The City of Calgary thanks you for your attention and cooperation.
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of markallen@micron.com Sent: Friday, June 03, 2005 8:30 AM To: toasters@mathworks.com Cc: bbullock@micron.com Subject: NDMP with TSM on Solaris
All:
We recently started backing up data from an R200 using NDMP and TSM running on Solaris. The Solaris system is a V240 with 2CPU's and 4GB of memory. Everything is connected via a fabric.
Backups seem to perform reasonably well when we are not getting a table of contents. Since we need a table of contents for individual file restores it is must to have this. When creating a table of contents backup's slow down by a factor of 5X. Has anyone else experienced this issue? Any help or direction would be greatly appreciated.
-Mark