From one response it looks like I need to clarify this post. I do understand 
journaling does not work with a NAS, which is why I recommended using NDMP, but 
unfortunately they don't want that in this instance. Some of the data on the 
NAS is going to be moved to a physical server and will be backed up from 
there. My statement related to spreading the data across multiple drives did 
not make that clear unfortunately. 
 
Sorry for not being more specific. So based on that I was looking for anyone 
who might have a large single server they have something that at least works 
fairly well. It kind of makes sense to me to spread the data across multiple 
drives and run a seperate journal engine for each but I don't know if it helps 
having multiple compared to a single journal instance. I also thought using 
multiple drives could at least give them an option to back up drives at 
different times of the day, on their own specific schedule, so things 'sort of' 
get backed up more timely.
 
Hope that helps.

Thank You
Geoff Gill



________________________________
 From: Geoff Gill <avalnch...@yahoo.com>
To: "adsm-l@vm.marist.edu" <adsm-l@vm.marist.edu> 
Sent: Tuesday, July 31, 2012 9:35 AM
Subject: Multiple journal engines on a single server
  

Hi All,
 
Sometimes when I read things that make sense it causes me to question if it 
really works so I thought I'd throw this out there to see if anyone is doing it.
I've read that you can put up multiple journal engines on a single server and 
I'm wondering if anyone has tested it and I'm also curious if you have decided 
if it has any advantages or disadvantages. I was thinking, because NDMP has 
been squashed for a specific customer, I need to find out the best of what's 
left. Hearing statements like, "we want to move all the data curretly x number 
of servers currently access on the NAS to a single server", it makes me 
question how we're going to handle this single backup.

I currently can't tell you how many millions of files we're talking about nor 
can I say how much data we're talking about, but it seems to me that it would 
make sense to create multiple drives to spread it out to be able to use 
multiple journal engines to track everything, and I was hoping it might make it 
quicker. One other question is if it would be better to schedule seperate 
backup windows for those different drives to help spread things out and get it 
backed up "at least somewhat timely".

Any suggestions would be welcome.
Thank You
Geoff Gill

Reply via email to