Enterprise Systems Backup and Recovery If you have an interest in, or work in data protection/backup and recovery environments, you should check out my book, Enterprise Systems Backup and Recovery: A Corporate Insurance Policy. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the human element to ensuring that your company has a suitable and working backup system.
|
Normally you don’t want to be in this position, but sometimes you’ll strike a situation where the only possible location of data that you need to get back is in a saveset that aborted (i.e., failed) during the backup process. Now, if the saveset/media is almost completely hosed, you’re probably going to need to recover [...]
For quite a while I worked under the assumption that you could do the following with directives in NetWorker:
<< /path >>
+skip: *.mp3
<< /path/subpath/criticalpath >>
forget
The logic of this is that it should be possible to skip files in one directory, but forget that directive in a lower directory and thus be able to still backup files [...]
Sometimes NetWorker may not want to cooperate when it comes to moving media in and out of drives, or around in a tape library. While nsrjb -n will do the trick for some media load operations where you don’t want to mount media, it’s not always available. Sometimes you will need to do a media [...]
While this is pertinent to all versions of NetWorker, it particularly seems relevant mentioning now, since as of 7.5.2, we’re now seeing revised messaging from NetWorker when a tape becomes prematurely full. These new messages now state:
nsrd media notice: LTO Ultrium-4 tape 800814L4 used 2039 MB of 800 GB capacity
nsrd media notice: NetWorker media: (Warning) [...]
The scenario:
A clone or stage operation has aborted (or otherwise failed)
It has been restarted
It hangs waiting for a new volume even though there’s a partially written volume available.
This is a relatively easy problem to explain. Let’s first look at the log messages that happens. To generate this error, I started cloning some data to the [...]
Looking at the stats both for this new site and the previous site, I’ve compiled a list of the top 10 read articles on The NetWorker Blog for 2009. The top 3 of course match the three articles that routinely turn out to be the most popular on any given month, which speaks something of [...]
Something that continues to periodically come up is the need to remind people running manual staging to ensure they specify both the SSID and the Clone ID when they stage. I did some initial coverage of this when I first started the blog, but I wanted to revisit and demonstrate exactly why this is necessary.
The [...]
When I was at University, a philosophy lecturer remarked rather sagely that University is the last place people can go to learn for the sake of learning.
That’s sort of correct, but not always so. People can fumble through their jobs on a day to day basis learning what they have to, but they can also [...]
Within NetWorker, data (savesets) can go through several stages in its lifecycle. Here’s a simple overview of those stages:
Basic data lifecycle
The first stage, obviously, is when data is initially being written – the “in progress” stage.
After the backup completes, data enters two stages – a browsable period and a retention period. These periods may [...]
Many of us with NetWorker have been in the situation where a backup has started (particularly when it’s for a newly configured group), and instead of going to the pool we want it to go to, it’s goes to the Default pool. For sites using multiple pools, it’s usually the case that no media will [...]
|
|