Server crash again.
This time a different one, but in the same 'set' as last time.
It's a NAS (network attached storage) - last week datamover 1 crashed. This time it's datamover 2. Very similar problems. Crash, failover, standby crashes too, and then the phonecalls start.
I'm 'concerned'. I have expressed my concern to the vendor in question. (And even did so without swearwords). If, as seems to be the case, we have 'problems' with filesystem corruption, I'm deeply worried. Data integrity is something that we really cannot afford to lose, simply because there's no way in hell of verifying every single byte on 2Tb of data.
It's starting to make me think that the (recently upgraded) backup server is at fault - crashes have occurred overnight, at around backup o'clock. Which is another thing that upsets me. Worse, the upgrade was a couple of weeks ago now, and if our last 'definite good' was that long ago, that's really an awfully big problem.
The prospect of my backup server going through all 30Tb of my network, and systematically (or even sporadically) fucking it is enough to make me think that a 1 way trip to ... well anywhere the first plane goes ... is probably a good idea.
This time a different one, but in the same 'set' as last time.
It's a NAS (network attached storage) - last week datamover 1 crashed. This time it's datamover 2. Very similar problems. Crash, failover, standby crashes too, and then the phonecalls start.
I'm 'concerned'. I have expressed my concern to the vendor in question. (And even did so without swearwords). If, as seems to be the case, we have 'problems' with filesystem corruption, I'm deeply worried. Data integrity is something that we really cannot afford to lose, simply because there's no way in hell of verifying every single byte on 2Tb of data.
It's starting to make me think that the (recently upgraded) backup server is at fault - crashes have occurred overnight, at around backup o'clock. Which is another thing that upsets me. Worse, the upgrade was a couple of weeks ago now, and if our last 'definite good' was that long ago, that's really an awfully big problem.
The prospect of my backup server going through all 30Tb of my network, and systematically (or even sporadically) fucking it is enough to make me think that a 1 way trip to ... well anywhere the first plane goes ... is probably a good idea.
no subject
Date: 2005-06-15 03:55 pm (UTC)no subject
Date: 2005-06-15 10:45 pm (UTC)Its not YOUR problem. Ok, so your neck will be on the line, but its THEIR system which is at fault. Yes, YOU might have selected the system based on the information given, which was considered acceptable at the time.
So - don't lose sleep about it. If the worst comes to the worst, you can have a few days off with a migraine from just thinking about it all!
This is an antiquated idea, but can you roll back your backup system to one that works?! Backup the backup ... !!
no subject
Date: 2005-06-16 04:35 pm (UTC)no subject
Date: 2005-06-18 08:36 pm (UTC)The former is good because it allows 'symmpath' backups. Copying data across a Storage area network, rather than the 'main' network, at 4Gb/s.
TSM is one that despite it being a pain, also does 'incremental forever' backups. Which if setup correctly, means your backup overhead is relatively low, if your data are fairly static.
We're looking (in the near future) at anothre TSM server and library, to backup 6Tb of lotus notes a night. That'll also be SAN attached, and transferring data at 4Gb/sec, to LTO3 tapes.