On Mon, 20 Apr 1998, Stephen Manley wrote:
Depends. What version of ONTAP are you running right now that you see this behavior?
sorry, good question. 4.3.1D5, and possibly also with 4.3.3.
The basic data I know, Data ONTAP 5.0 runs significantly faster (50%?) than 4.3. Furthermore, it should not crank at 100% CPU for minutes/hours at a time. We've gotten to the point here that people don't really notice an effect when we run dumps, anymore.
Also, if I could ask a survey question of people (if this is not an acceptable forum for this, just flame me ;) How do people out there use dump?
- rsh to local drive.
Currently our only backup possibility, it's working fairly well for now but as I've mentioned previsouly we're looking to seriously load our filers (before getting some more 8) and the backup times are looking daft! Specially as we do full backups every night, and will continue to do so until such time as we have a sterling installation of something like Veritas such that incrementals become manageable and reliable.
- rsh to remote drive.
Why? streaming across the main network is a bad idea (tm) and CIFS put paid to the utility of the technique anyhow.
- NDMP to local drive.
This is what I want to move toward, using tape-drives attached to the filer (ie where the data lives) and control across the network to a Veritas/other control box, where the indexes get kept.
- NDMP to remote drive.
Doh! Only when we've got our dedicated Gigabit Ethernet backup network in place, which current estimates place around the next ice-age.
- I don't.
Inquiring engineering minds are curious to know. :)
Forgive my sarcasm in the above - you wouldn't believe the angst the word 'backup' causes around here at times. Plus I think I got out the cynical side of my bed this morning.
Sm