This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Stacey, > Yeah, we are pushing a lot of data through that machine. I think we > have just reached the limit of where the hard drive is having a hard > time keeping up. We store all radar products from all radar stations on > that machine as well as a lot more data like lightning and satellite > images. Looks like we'll have to look into upgrading the hardware. Alternatively, you could use that system as a "relay only" node (i.e., one that doesn't do any local processing) and have other systems connect to it. Each could request a subset of the data (e.g., only radar products), and each of those systems could file their data. Segregating systems by data-type is a common practice. A time-series plot of I/O activity on the system in question could prove enlightening. > Thanks, > Mr. Stacey Simmons > WeatherTAP.com Regards, Steve Emmerson Ticket Details =================== Ticket ID: BLB-756234 Department: Support LDM Priority: Normal Status: Closed