Setting up NDMP is almost a trivial task when using TSM V5.4 and NetApp filers.
There is no device driver set up on the filer - just enable NDMP. Schedule snapshots if you want to backup a snapshot for a specific time. Create two primary storage pools (one for data one for the table of contents of the data) and a copy pool on the TSM server (disk, tape - your choice), create a datamover and node and virtualfsmapping for that node if you will be backing up snapshots, volume subdirectories or Qtrees. Create a schedule that runs the "backup node..." command. If you need to recover a single file from a NAS share, the table of contents will allow you to pick that file out and restore it. Use the Windows WEB client - not the installed GUI to see the NDMP node data. You can recover data another filer simply by creating a volume on that filer and updating the datamover address to the destination filer - and then running restore. Yes it places TSM into a relatively simple data repository since you cannot control versioning of specific files, and you have to be aware that the backups will be full or differential but, for some environments, this setup provides needed backup with minimal impact on the TSM database and does not require filling the ethernet with CIFS/NFS traffic to backup from a remote node. It can also be used to backup LUNs that have been snapshot, greatly reducing the impact of backups on the hosting system. The previous requirement of attaching tape to the filer and creating special storage pools that could not be copied goes away with TSM V5.4 and NDMP over ethernet. For some environments NDMP over ethernet is worthy of consideration. Cheers, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Thursday, February 14, 2008 10:41 AM To: [email protected] Subject: Re: [ADSM-L] Backing up PST files >> On Wed, 13 Feb 2008 21:23:25 -0500, "Strand, Neil B." <[EMAIL PROTECTED]> said: > Have you looked into ndmp from the filer to your tsm server? If you > are at TSM V5.4 you can do this over ethernet and handle the data just > like any other node - move, copy etc. It also minimizes impact on DB > size. The trick is to recognize ndmp full/differential methodology in > the TSM incremental methodology climate. NDMP: Avoid, avoid, avoid. I've elaborated on this opinion in the past, but the succinct summary is that NDMP turns all your fancy TSM infrastructure into a big remote-tape structure. Only the very most recent and fancy NDMP clients even give TSM any sense of the contents of the data. You have to come up with device drivers on all your NDMP clients. Ick. Assiduously investigate other options before discarding all the advantages TSM gives you. I spent years doing rmt on unix: I don't want to go back, and you don't want to go there. - Allen S. Rout IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
