Hi!
Using TSM 5, MS-Exchange 2003 and NetApp with SnapManager for Exchange I do have the following question:
How am I able to automate the NDMP-backup process?
Scenario:
1. TSM-Server
2. NetApp-Filer
3. Windows-2003 Box with Exchange 2003 and NetApp's SnapManager for Exchange
At a given time SnapManager for Exchange initiates a backup on the NetApp Filer, so I have a consistent view of the Exchange databases and TX-log files. When this is done (and perhaps verification of the db-consistency has been successful) the TSM-client==Windows-box tries to call the TSM-server using "DSMC BACKUP NAS" that it could start the NDMP-backup of the according volumes.
This works fine, except that I have to give an administrative user-id and its password to the TSM-server. Do you know of any mean to let the TSM-server know, that it is O.K. to let node "MS-Exchange server" start a NDMP-backup? Or do you have any other idea?
Using a TSM-server script calling the SnapManager routine brings me into trouble to start the needed processes with the right permissions/roles it needs to fumble around with exchange :-(
Any ideas ( even in the next year ;-) ) appreciated.
Best regards,
Dirk
Using TSM 5, MS-Exchange 2003 and NetApp with SnapManager for Exchange I do have the following question:
How am I able to automate the NDMP-backup process?
Scenario:
1. TSM-Server
2. NetApp-Filer
3. Windows-2003 Box with Exchange 2003 and NetApp's SnapManager for Exchange
At a given time SnapManager for Exchange initiates a backup on the NetApp Filer, so I have a consistent view of the Exchange databases and TX-log files. When this is done (and perhaps verification of the db-consistency has been successful) the TSM-client==Windows-box tries to call the TSM-server using "DSMC BACKUP NAS" that it could start the NDMP-backup of the according volumes.
This works fine, except that I have to give an administrative user-id and its password to the TSM-server. Do you know of any mean to let the TSM-server know, that it is O.K. to let node "MS-Exchange server" start a NDMP-backup? Or do you have any other idea?
Using a TSM-server script calling the SnapManager routine brings me into trouble to start the needed processes with the right permissions/roles it needs to fumble around with exchange :-(
Any ideas ( even in the next year ;-) ) appreciated.
Best regards,
Dirk