Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Need Novell OES11 on SLES11 support

Created: 30 Jan 2012 | 42 comments
Viktor Tanin's picture
10 Agree
0 Disagree
+10 10 Votes
Login to vote

Need full support for Novell OES11 on SLES11 in 64-bit environment, NSS volumes, etc. At this point of time no way to make backup in such environment.

Current SCL for BE 2012 says, "Supported with Novell Open Enterprise Server (OES) 2.0 SP2-SP4, with NSS, NDS, GroupWise and iFolder on 32 and 64-bit platforms for SUSE 10 only." We need SUSE (SLES) 11 and OES 11.

Comments 42 CommentsJump to latest comment

muinfotech's picture

Definitely agree. I know a lot of other Novell customers want and need this too!

+3
Login to vote
Allen.D's picture

Same here.  We have been in contact with Symantec and they have yet to be responsive to our collective requests to update RALUS.  Pretty sad considering they are a Novell partner.  This product update is long overdue.

+1
Login to vote
mcguirwl's picture

My company is also in the same boat. One of our admin's just brought up a SLES 11 64-bit box with OES and we ran into this issue. Those of you who are experiencing this issue, have you deployed any work around in the mean time to backup your systems while waiting for Symantec to catch up?

+1
Login to vote
Allen.D's picture

mcguirwl.... yes we did.... sort of.... since our SLES 11/OES11 servers are running as VMware vms, we back them up using the Agent for VMware Virtual Infrastructure.  That works fine and serves the purpose of being able to restore a vm (in total) however it is the granular backup solution (RALUS) for OES11 we all need here (e.g. incremental backups).  There are a large number of us here at our institution that are committed to using Novell products and have been litterally hounding Symantec for a solution.  After all, they are a Novell partner...

I've heard through one of my peers that there is a workaround.  Renaming a version file (not sure which version file the peer is referring to) allows you to not only see the directory structure when browsing the backup seletction list with RALUS installed but allows for GRT, both backup and restore to include file/folder attributes and rights.  I'll have to find out what version file he is referring to and post back.

+1
Login to vote
mcguirwl's picture

Thanks for responding Allen. Unfortunately all of our SLES installations are all on physical boxes (management seems to be anti virtualization for some reason). In the mean time I found that another product (Retrospect) that my company uses on a much smaller scale seems to work. Until Backup Exec becomes compatible we'll likely be stuck with that solution for the moment.

I also ran into a post in regards to renaming a version file to resolve some 64-bit incompatibilities. I tried finding it prior to this post but couldn't. If memory serves me write it involved renaming one of the SO libraries. If I'm able to find the file information I'll post back.

+1
Login to vote
Allen.D's picture

mcguirwl.... there is another product out there called SEP Sesam that will work.  I just saw a quote for the product from one of my peers... somewhat pricey particularly if you want to use it to backup GroupWise and use Tape Libraries as a target but a Novell Certified Partner nonetheless.  My apologies if you are already aware of it.

Ironically.....

Just received upgrade notification to BE 2012 and behold..... no longer support for NetWare (no agent).  So not only do we pay for maintenance but now stuck between a rock and a hard place.  Can't migrate to OES11 because a viable agent does not yet exist for backing up NSS volumes and can't upgrade to BE 2012 because current NetWare production servers no longer supported with BE 2012.

+1
Login to vote
Allen.D's picture

Yesterday I modified the novell-release file (/etc) to include what is listed in this forum post.  Was able to backup and restore files on our pre-production (migrated from NetWare 6.5 SP8) OES 11 server.  Keeping a close eye on any issues that may arise with this "temprorary work around solution".

http://forums.novell.com/novell/novell-product-dis...

+1
Login to vote
klin8251's picture

For some reason I did not see the work around in your posted URL.  Would you mind pasting the solution that you used?

 

+1
Login to vote
Stephen Gardiner's picture

I guess as they don't support NSS on OES2 64bit and OES11 is 64 bit only it is a problem with the RALUS agent and 64 bit support in general.  Come on symantec lets get this fixed.

0
Login to vote
Allen.D's picture

Hmmm. 

Here is the part of the forum thread on this topic that discusses the "fix":

Hi all, just in case someone comes along this post in looking for an answer to how to backup OES11 NSS volumes with Backup Exec 2010. First off, Symantec says it is not supported. However, it will work if you change the novell-release file in /etc to an OES2 info. Make sure you upgrade the BE2010 to version R3. It doesn't upgrade through LiveUpdate, you have to download from fileconnect.symantec.com.

Novell Open Enterprise Server 2.0.3 (x86_64)
VERSION = 2.0.3
PATCHLEVEL = 3
BUILD

So it took about 8 support calls to Symantec and finally the second level tech found this workaround. She said someone from Novell came up with it. I don't understand why Symantec is so slow to support this release and quite frankly, it irritates the heck out of me. The workaround is so easy but changing the novell-release file could impact other apps, like databases.
 

 

My best to all....

0
Login to vote
DanPearson's picture

So what exactly does changing the novell-release file do and what else will changing it impact? I tried it and it does seem to allow BE 2012 to back up NSS volumes, but I'm just concerned about it causing problems with other programs/services on the OES server.

0
Login to vote
mcguirwl's picture

The release file is referred to by Backup Exec to determine what kind of client it's backing up. By changing the information in the file you're fooling Backup Exec into supporting the OES server in question. I've been using this workaround for a while now and haven't encountered any issues on our server. (We periodically test the restores and have never had a problem) The only issue that I can think of that arose was when I had to call Novell for support on an unrelated issue, they were curious why their log collection tool was reporting a different OS version than they expected. They accepted my explanation and the call went on as expected. You could always change the file back prior to calling Novell for support if you were worried about them not supporting you in a pinch.

0
Login to vote
DanPearson's picture

I'm wondering at what point the file is read. If it's only read when the remote agent is loaded then we could change the file when starting the agent and then change it back once it's loaded. Or, is it read each time the server is requesting info from the agent?

Thanks for the update. Just wondering how the release file is being checked and when.

0
Login to vote
Mahesh_SSR_PM's picture

Dear all

We are aware of this demand and the requirements evaluation is in progress.

 

Thanks and regards

Mahesh Kumar Gupta

Senior Product Manager - BE Linux Agent

+1
Login to vote
pgtiii's picture

Mahesh,

Its great that you posted that comment, but we need to know when?  Your requirements evaluation should have taken place 6 months ago when OES11 was in Beta, not after the final product was released.  Never in a million years did I think I was going to get screwed by your stupid product locking me out of backing up nss volumes.  Next time I will just go with a forward thinking company like Sesam who has there act together and is supporting OES 11 today. 

Get with the program and GET THIS FIXED, NOW.

Sincertely,

Peter Tomasi III
West Morris Regional HSD

+3
Login to vote
Chris Riley's picture

Update for everyone...

Support for OES11 (NSS volumes only) will be added to Backup Exec 2012 soon. Exact dates are not available yet. I will update here when more details are available.

+2
Login to vote
matiasm74's picture

I need this update tomorrow, is there any "beta" update ?

0
Login to vote
Chris Riley's picture

Not that I am aware of I'm afraid.

0
Login to vote
pgtiii's picture

It would seem that with Symantec its an all or nothing approach.  This is so typical of a large software conglomerate that doesnt actually do any programming in the United States, they use programmers from overseas that dont know how to interface with the software community at large.  

Gone are the days of a software lifecycle that actually includes input from the end users, Symantec is like Microsoft they think and act like they are in a vacum and who cares what the end users say, you get it when we are done with it.

I tell you if Sesam pricing comes down a bit I am going with them at least there you can interface with backline and dont have to go through the "how do I open a support case and actually get support" scenario.  I say this because I did a 30 day trial of Sesam and they gave me free installation support during the whole 30 days.

Symantec needs to get there act together and listen to its customer needs not there inept programming staff.

+1
Login to vote
Jason Whitson's picture

 

This is really sad but the only they will listen is if you punch them in the wallet. I've already done that by purchasing over $8,000 worth of licensing then I immediately returned when I found out NSS wasn't supported. Perhaps I should have looked a little closer but I assumed that when I upgrade a product it would continue to work on the platform I've been using for 12 years.

If you're going to alienate a group of customers, Symantec, you should have the common decency to let them know.

0
Login to vote
Chris Riley's picture

I can confirm that we are adding support for OES11 (NSS only) with the next DDI (device driver installer) for Backup Exec 2012. This should be available next month (Dec 2012).

Hope that helps.

0
Login to vote
Stephen Gardiner's picture

Chris are you saying NSS for 64 bit will only be supported in 2012.  We need to use 2010 as we support Netware 6.5 and can't provision to 2012 due to Netware support being dropped.

 

Thanks

 

0
Login to vote
Chris Riley's picture

I'm pretty sure that support wont be added to BE 2010. Sorry, not what you want to hear.

0
Login to vote
Bsimps's picture

Hey Chris - Any update on the release date?  Its December.  Using a workaround - that is less than optimal.

0
Login to vote
Chris Riley's picture

I don't have a specific date to give you I'm afraid but I know it is targeted for this month. I will update this thread when it is available.

0
Login to vote
John_Cr's picture

Chris, any update on OES11 NSS support?

0
Login to vote
Chris Riley's picture

The documentation for the hotfix that adds support for OES11 is currently being written up. Once this is complete, the hotfix should be published to LiveUpdate and our support site.

I would expect this to be done within the next 2-3 days maximum. I will post back here once it is ready.

0
Login to vote
Lars.A's picture

Hi Chris, we are more people waiting for a update on BE2012 OES11 NSS support any news? And will it also support OES11 SP1?

0
Login to vote
Chris Riley's picture

The hotfix has just been made available:

http://www.symantec.com/docs/TECH199190

Please note that it may take up to 24 hours before this is available via LiveUpdate.

0
Login to vote
Allen.D's picture

And it works Chris..... was able to backup and restore a test VM OES 11 system (NSS files and folders only) this morning.  All file metadata restored without a hitch.  Nicely done.  Good luck to all!

0
Login to vote
Lars.A's picture

Please confirm that it also works on the "new" OES11 SP1?

0
Login to vote
Chris Riley's picture

SP1 is not supported yet. It may work but not officially supported.

0
Login to vote
gdwalker's picture

Any Idea when The hotfix will be made available again?

looks like you cannot download it anymore and I have some servers with SP1 that I really need to try and get backed up using the hotfix even if it is not supported on OES11 SP1.

I need to try or have to go find another solution.

0
Login to vote
Chris Riley's picture

No ETA at this point I'm afraid (please don't shoot the messenger).

I'll post back here when there is an update.

0
Login to vote
kochie's picture

Are they going to support OES11 Sp1?  Man this has been taking a long time to get an agent....

 

+1
Login to vote
DanPearson's picture

I am really disappointed in Symantec. I have been using BackupExec for many years (back since Veritas) and expected that they would continue to support Novell OES even after dropping NetWare. I purchased an upgrade to BE 2012 when I moved my last NetWare box to OES 11 and to my dismay find that OES 11 is not supported and there is no workaround to allow me to back up my NSS volumes. If they can't provide a solution soon I will have to ask for a refund and look for an alternative vendor that supports Novell.

 

+1
Login to vote
Bsimps's picture

Dan,

I have to agree with you.  This thread is now a full year old.  One can only assume that Symantec has corporately decided to make support of Novell OES an extremely low priority going forward.  This leaves us all in a bad position as we progress with Novell to the full maturity of OES.  We can't be held back by Symantec's lack of dedication to the OES product.  It is almost unconscionable that Symantec dropped support for legacy Netware on BE2012 and yet still doesn't support the last 2 versions of OES on BE2012. 

I am part of a consulting group with about 25 of our clients using BE in a Novell environment.  The clients aren't happy about not being able to move forward with their systems development and a few have already said lets go with an alternative. Of course along with Symantec our firm is taking it on the chin for this. (As I am sure a lot of IT professionals are.)

Sesam is pricy but my initial conversations with them were much better than any conversation I have had with BE since the death of Veritas.  The other option I am exploring is CA Arcserve.  Some of my coleagues have commented that CA has their act together again...at least concering Arcserve.  And yes, they do support OES 11.1  NSS. 

Its just sad though that Symantec would disenfranchise so many Novell / loyal BE users in such a cavalier way.  I hope they get this resolved before all our clients switch off.

 

+1
Login to vote
pgtiii's picture

This is what happens when companies get so large and full of themselves.  The other issue is that they probably sent the development pecice for this product elsewhere and that may be whats slowing this down. I say crap or get off the pot.  Release the dam patch already. 

Peter 

0
Login to vote
abeNdorg's picture

I noticed they are way behind the curve with Windows server 2012 & ESXi 5.1 too....it is not just OES11 customers suffering.

 

Current support matrix (which oddly does show support for oes11sp1x64...but none for svr2012/esxi5.1)
http://www.symantec.com/business/support/index?page=content&id=TECH175581&key=15047
 
Windows Server 2012 released on ~September 2012
http://www.symantec.com/business/support/index?page=content&id=TECH196108
 
Vmware ESXi 5.1 released on ~September 2012
https://www-secure.symantec.com/connect/forums/vsphere-51-support-update
 
Novell OES11 released on ~December 2011
http://www.symantec.com/connect/ideas/need-novell-oes11-sles11-support (this thread)
http://www.symantec.com/business/support/index?page=content&id=TECH199190 (mentioned in this thread already)
 
Is backupexec a "dead" product then? It would seem they would rather we all move to netbackup instead? It would seem esxi51/oes11 are supported with netbackup (but not win2012) - http://www.symantec.com/business/support/index?page=content&id=TECH59978

 

+1
Login to vote
Bsimps's picture

abeNdorg,

I just got invited to be part of a feature review team for BE2013.  So they are moving foward while BE2012 is still a piece of relatively unuseable junk in the enterprise.  So they aren't killing BE; just us users, slowly and painfully.

 

+1
Login to vote
Chris Riley's picture

FYI

The DDI is now available again:

http://www.symantec.com/docs/TECH201596

0
Login to vote