Re: [IUG] Turnkey Site and Enterprise Backup API


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
I have talked to Doug Randall at III today, and he showed me that there is one avenue left to us that doesn't require loading NFS modules for which we'd then be responsible for updates, or having more local diskspace (we had considered the USB option, but this didn't look promising with Solaris 9, and I didn't want to test on my production box). It involves piping to a cat > tar on a remote Unix/Linux box. This is beyond my Linux skills, and requires maintaining updates, security on another Linux box. I will be talking to our campus IT people to see if they'll maintain a box I can use for that purpose. So don't let me discourage any other turnkey sites that would like to try Enterprise Backup. I do apologize for my testiness that indicated that "III should have known", but I had been hitting dead-ends since last fall!

-----Original Message-----
From: innopac-bounces at innopacusers dot org [mailto:innopac-bounces at innopacusers dot org] On Behalf Of Cindy Harper
Sent: Monday, November 24, 2008 3:24 PM
To: 'IUG INNOPAC List'
Subject: Re: [IUG] Turnkey Site and Enterprise Backup API

I'm very interested to see this question. We are a turnkey site, and purchased Enterprise backup more than a year ago, but I have yet to find a way that doesn't result in some obstacle for backing up our system. I at first assumed that we would be backing up to a network share, only to find that on turnkey systems, III doesn't load all of the NFS client modules, so we would have to go it alone on security if we loaded those modules, I fear. I am still awaiting a reply on whether there is a solution to tha problem. My other concern with an NFS share was whether all permissions and ownership data would be retained. Meanwhile, I had to load Windows Server 2003 R2 in order to create an external server I could use for a backup.

I also tried to follow Mike Lynch's (Middlebury) script for backing up to the local filesystem, but of course, III didn't create a filesystem that would be 1) outside the standard backup paths and 2) have enough space for a backup. III answered that they would not deviate from the standard filesystem setup for a turnkey site.

I have asked III whether we can get a credit for this software, since they should have known we'd run into these obstacles, and have no magic to solve them and still be a turnkey site.

Cindy Harper
Systems Librarian
Colgate University
charper at colgate dot edu

-----Original Message-----
From: innopac-bounces at innopacusers dot org [mailto:innopac-bounces at innopacusers dot org] On Behalf Of Vicky Munda
Sent: Monday, November 24, 2008 12:34 PM
To: innopac at innopacusers dot org
Cc: ryant at csulb dot edu
Subject: [IUG] Turnkey Site and Enterprise Backup API

A member of our Systems Team asked me to post the message below on this
listserv.

Are there any organizations out there who are turnkey sites AND use the
Enterprise Backup API? We are a turnkey site and have been using Legato
Networker for some time to back up our III server. My organization has
made the switch to Symantec Backup Exec and we are talking to III about
switching our backups to Backup Exec.

We'd like some feedback from other users who may be using Backup Exec to
backup the III server, especially if you are a turnkey system. Are you
using it to back up other servers in your datacenter, and are you having a
problem with your backup window? Especially for turnkey sites, how did
you talk Innovative into letting you back up to Backup Exec (back when we
started using Legato, that was the only choice given to us that they would
support)? Has anyone else switched from Legato Networker to Backup Exec
(or perhaps the other way around)? Thanks for the information.

Vicky (for Ryan Tapp)


- - - - - - - - - -
Victoria J. Munda
Access Services Coordinator, University Library
California State University, Long Beach
1250 Bellflower Blvd.
Long Beach, CA 90840
(562) 985-5567 voice
(562) 985-2340 fax

--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies: INNOPAC at innopacusers dot org
Update your subscription options: http://innopacusers.org/mailman/listinfo/innopac

--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies: INNOPAC at innopacusers dot org
Update your subscription options: http://innopacusers.org/mailman/listinfo/innopac