Unsolved
This post is more than 5 years old
13 Posts
0
2977
December 20th, 2007 16:00
Can NetWorker backup a SAN directly?
Our organisation has many SAN's across multiple sites. As SAN disk usage has increased some of these sites are experiencing an increase in backup times for big LUNs (e.g. 1 - 2 TB). These are predominatly windows file servers, I am finding that due to having something like 3 million files on these LUNs, I presume the bottle neck has become the trawling/indexing of all these little files, as the backup speed (around 30MB/s) is no where near max capacity.
Does NetWorker (7.3.3) have some facility to backup SAN LUNs directly, so that we can bypass the file server? We have been considering using DDS and turning the file servers into storage nodes, but I don't think that will make much of a difference.
Does NetWorker (7.3.3) have some facility to backup SAN LUNs directly, so that we can bypass the file server? We have been considering using DDS and turning the file servers into storage nodes, but I don't think that will make much of a difference.
0 events found
No Events found!


andreas.scht
2 Intern
•
219 Posts
0
December 21st, 2007 03:00
The only way I know to bypass direct, is to do an RAW Device Backup of this SAN-Luns.
What OS have your NetWorker server?
andreas.scht
2 Intern
•
219 Posts
1
December 21st, 2007 04:00
RAW backup by directive is also possible by 7.X.
jsperanz
13 Posts
0
December 21st, 2007 04:00
Also, the reason I think turning the file server into a storage node will not make much improvement is that other partitions on the same server backup much faster, and indeed even the 1Tb+ partitions occasionally "burst" to faster speeds, presumamby when it is backing up larger files rather than many small ones. Its quite noticable when this happens, there is a big jump in speed for a while, and then its back down to a trickle again.
And yes I know of using direct SCSI, but 1) This is (I think?) only available on 7.4, and 2) more importantly, we must keep indexes.
I know this whole thing is probably wishful thinking anyway, but I thought there was no harm in asking
nicbone
116 Posts
0
December 28th, 2007 02:00
Our large windows file & print use DDS drives mapped to a UNIX hosted autochanger to get the throughput we need. Same sort of situations - LUNS up to 1.6TB & millions of files per LUN.
Rgds
Nick
ChooseAnAlias1
44 Posts
1
December 28th, 2007 18:00
A raw backup is probably a bad idea, since you lose the ability to do a file level restore... restoration times would be awful. I'd try SnapImage first, it's intended for exactly this problem (assuming the problem is indeed trawling/indexing all the little files).
FYI, something like Avamar nodes might be a better fit, but SnapImage would be a lot less effort to deploy.
jsperanz
13 Posts
0
January 3rd, 2008 17:00
It seems that there is no easy way out of this.
Doing a raw backup is easiest and the closest fit to what I want but does not provide file indexes, which are mandatory.
We have a lot of IBM FastT so we could use PowerSnap, but we don't have the capacity to be snaping LUNs (its not our hardware, so we can't just upgrade). Also, we are migrating to HP hardware now and there is no PowerSnap module for HP SANs that I know of, so we would have to get the SAN to do the snapshots. But at the end of the day, the trawling/indexing won't increase in speed, but there will be less impact since the LUN is not a production LUN.
SnapImage would probably work best, but it is not without problems either, such as the requirement to have its own driver for tracking disk changes (how much can you trust that?) and the fact that there is no incremental backup, only diff and full (I can understand why, since it is doing things on a block level, but it's still annoying). Anyone have any experience with SnapImage? Is it reliable?
tkutil1
5 Posts
0
January 25th, 2008 08:00
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
January 27th, 2008 15:00
p.s. tkutil, looks like you missed the thread, didn't you?