Did your exchange admin maybe mount the rsg to check it? It should be
dismounted and not marked as a read only storage group prior to the restore.
Exchange restores are always fun, as it is a connection via ESE, so you won't
get Netbackup telling you about problems with the data movement. Look
Hi,
With NBU 7.0.1/UNIX (Linux):
May 4, 2011 3:45:06 PM - started process bpbrm (pid=8399)
May 4, 2011 3:45:07 PM - connecting
May 4, 2011 3:45:07 PM - mounting X22549
May 4, 2011 3:45:07 PM - connected; connect time: 0:00:00
May 4, 2011 3:45:09 PM - end writing
unexpected message received (43)
Hi Simon,
Thanks, it would be nice if there was an easier rollback, if I find one
I'll update the list.
Justin.
On Wed, 4 May 2011, WEAVER, Simon \(external\) wrote:
Justin
I thought it was a case of:
1) Uninstall
2) Reinstall previous version, ensuring maintenance pack
3) Do inventory
My suggestion for this, is because I felt the 7.1 EMM may be at a
different level to the 7.0.
Simon
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: 05 May 2011 09:32
To: WEAVER, Simon (external)
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE:
bplist -C server1 -t 17 -s 05/04/2011 -e 05/05/2011 -R 99 /*
that should work (obviously dates as you require).
Type it out, though… copying and pasting “-“ into a command prompt is often
misinterpreted. Not sure what the alt character it uses is, because it
definitely still looks like a
You can shutdown NetBackup services an copy the veritas directory.
Do the update and if you want to rollback, uninstall 7.1, install 7.0.1 and
after you shutdown NetBackup copy back the veritas directory.
stefanos
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
Cheers Nick, VERY much appreciated, going back to the test lab now
From: Nic Solomons [mailto:nic.solom...@attenda.net]
Sent: 05 May 2011 10:09
To: WEAVER, Simon (external); veritas-bu@mailman.eng.auburn.edu
Subject: RE: The exact files that were captured by
Hi Uli
Have not seen that particular isssue, but have had a lot with exchange
restores.
I would check the tar log on the exchange server for indication of where
problem lies
One thing I have giving strange problem is if the temporary location is too
small
Hope this helps
Regards
Michael
All
From my History of working with NBU, any upgrades I have done have been
in this order:
Master
Media Servers
SAN Media
Clients
So ... why would Symantec be telling a colleage that its ok to oto
6.5.6 on a client and leave Master at 6.5.4 ?
Client OS is Wink28 R2 SP1 which cant be backed up
We found this out all on our own, without Symantec's blessing.
They came a little late with their 2008 R2 support, so they let this go on
for CYA. We were doing this before we went to 7.0.1.
When you are caught in the dilemma of getting backups or being supported,
well, I choose the former.
Sure I read somewhere this was bad practice, but for life of me cant
find it!
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
scott.geo...@parker.com
Sent: 05 May 2011 15:33
To:
Well, it is not supported but is working.
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WEAVER, Simon
(external)
Sent: Thursday, May 05, 2011 6:04 PM
To: scott.geo...@parker.com; veritas-bu@mailman.eng.auburn.edu
Subject: Re:
If you have the SAN/Server space, what we often do for upgrades and server
lease returns is the following. One thing to keep in mind is that our
/usr/openv dir is its own mount point.
Build an identical server
Shutdown NetBackup
Copy /usr/openv on original server to new server's /usr/openv
Concern I have is that can you really rely on it. There may be
enhancements to the product that the Master knows little about.
If you have support with Symantec, and best practice is to follow what I
have been doing 10+ years, should that be the best course of action?
Of course, That's not to
As it stands, I have put it back to 6.5.4 and will upgrade the Master at the
weekend.
For now, its getting the essential Data we need as is and I am happy with
this.
Thanks for all of the feedback.
S.
From: Valenze, Christopher [mailto:ch...@batechp.com]
Good Afternoon,
It would be nice if Symantec could design the client to master interface to be
more generic, without hurting performance.
Put the smarts for handling client differences in the client and not on the
master.
Then they should be able to handle not only newer client support needs
Re: Sure I read somewhere this was bad practice, but for life of me cant
find it!
Probably saw this in the release notes on mixed-server compatibility
environments. 7.1 release notes page 41. Suspect it id doc’d in other versions
of Release notes also. I didn’t check.
■ In a
Hi All,
We're having a strange problem when the media server (AIX 6.1) is backing
up itself. This problem only occurs when the media server attempts to back
up itself. The media server can back up other clients just fine. Other
media servers can back up this media server just fine.
Here is the
I have few questions:
- What is in the backup selection.
- Follow NFS and cross mount points selected
- Try splitting up the backup selection in multiple streams and pin point
exactly which file or folder is creating problem.
On Fri, May 6, 2011 at 9:15 AM, jim.ca...@mylan.com wrote:
Hi All,
19 matches
Mail list logo
