Thanks guys
Our Netbackup verision is 6.5.4.
There should be open for port 13724 in the firewall.
This seems to be confirmed by the fact that file backup restore works when
initiated from the master server.
Bplist also gives status 23 and bpclntcmd only say expecting response from
server master
Dear milisers,
Is it possible to backup using Backup Exec (version 12) and then restore it
using NetBackup (version 6.5)?
Is it just a matter of doing inventory catalog at the NetBackup side?
Thank you for helping.
--
Best Regards,
Adrian Soetanto
On Mon, Jun 14, 2010 at 5:00 AM, Adrian Soetanto
adrian.soeta...@bentoel.co.id wrote:
Is it possible to backup using Backup Exec (version 12) and then restore it
using NetBackup (version 6.5)?
http://seer.entsupport.symantec.com/docs/295433.htm
.../Ed
It turned out that my suspicion about the name resolving was correct
After removing an wrong dns entry and making sure the client name was in the
same case on both the client the master,
boty bplist and the oracle backup work
Regards
Michael
2010/6/14 Michael Graff Andersen mia...@gmail.com
Hello,
We are running NBU 6.5.5 in combination with a Fujitsu VTL, configured in ACS
emulation mode. I am getting recurrent Operator/EMM drive DOWN'ED messages for
some tape operations, and they are always occuring EXACTLY 25 minutes after the
mount request.
I was wondering if there are
Does anyone happen to know if there's a way of determining the date media was
frozen?
Thanks
Mike
blocked::http://www.justgiving.com/CoastCakesCastles2010
**
This e-mail (including any attachments) is
bperror -l -media -X -d 169200 -e 127652 | grep -i freez
that the large number in the first column:
bpdbm -ctime large number
and that will tell you the date.
Regards,
Patrick Whelan
NetBackup Specialist
Wholesale Markets and Treasury Trading
Lloyds Banking Group
Desk: +44 (0)
Could me like what I go through
My normaly is mydomain.mycompany.com
But we have service networks so some servers get mydomainservice.mycompany.com
Which they do not always set dns setup right. They use to make two entries,
one for each domain.
I had to talk to them to make true aliais so
Look in the all logs, it shows when it freezes tapes.
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
michael.ket...@orange-ftgroup.com
Sent: Monday, June 14, 2010 8:50 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu]
Please note this potential issue with OpsCenter!
From the manual:
If you have NOM you need to upgrade to Ops Center, but if you do that and your
master server is still on 6.5.x you will need to install and config an agent to
monitor the 6.5.x server. But if you upgrade right away you don't
I was very fluent with NBU versions 3.x-5.1. I've been a CommVault user since
6.1, we're running 8.0, right now. Can anyone on the list compare their
experiences with both products? I'm especially interesting in hearing from
folks who like the current version of NBU over CV v.8.
Thanks ,
Steve
I have Netbackup 6.5.5, windows master server, windows 2003 client.
Here is the set up
2 cluster nodes we will call a b.
A has a SAN share of F
B has 2 SAN Shares labeled drive E and G.
E:\blah\ and G:\blah2\ are set up as shares in the clusters.
For some reason when I do backups I'm getting
What do your client list and backup selections look like? Why did you
select cross mount points, are you using NTFS mount points?
-Jonathan
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of zimmy00
Sent:
Are you sure they're clustered drives on the virtual host rather than
local drives that just happen to be mounted on the active physical node
of the cluster?
Perhaps it stopped working due to a failover 6 months ago when somehow
they got remounted on the physical node rather than the virtual
I am backing them up based on the root drive letter and the host as the virtual
host the drive is assigned to.
+--
|This was sent by steve.s...@compucom.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
I used the Cross mount points in an attempt to fix this based on a symantec
article.
Martin, Jonathan wrote:
What do your client list and backup selections look like? Why did you
select cross mount points, are you using NTFS mount points?
-Jonathan
-Original Message-
From:
Right - my point was it may be empty directories because its not
really on the virtual but rather on the underlying physical node.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of zimmy00
Sent: Monday, June
Ugh...ok I forgot that this isn't on a san anymore. They are physical drives
now. But that has been that way for a while and the problem just started 6
months ago.
Also, sometimes if I mess around with the client (failover / reboot clusters) I
can get it to do 1 good backup.
Lightner,
I just changed employers and am now managing an existing NBU 6.5 deployment
which I will be upgrading to NBU 7. I had built the backup solution at my
previous employer on CommVault 5.0 and upgraded it to Simpana v7. Had I not
switched employers, I would have upgraded to version 8.
As far as I
I tried using the physical node name instead of the virtual and it has the same
problems. It also seems that the only problem directories are the larger ones
that are shared out via the clusters. I don't know if that is relavent.
Lightner, Jeff wrote:
Right - my point was it may be empty
The question comes down to just how are you backing up the cluster.
There are 4 server names involved here.
A is a physical server - with physical drive C
B is a physical server - with physical drive C
Then you have VA - a virtual server - you have some resources assigned to this
virtual
Can you please run mountvol /L and post the output?
-Jonathan
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of zimmy00
Sent: Monday, June 14, 2010 3:43 PM
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject:
That is exactly correct and also exactly how it is configured already.
:\
Note that the other virtual server has other resources assigned to it that have
no problems what so ever.
+--
|This was sent by steve.s...@compucom.com
We have a NetApp filer that has a few TB of data made up largely of
millions of small files (about 30 million or so) and we are using several
NDMP policies to back up this data. The two main problems are length of
time it takes to backup (we usually have 2-3 backups running all day every
day)
We’ve been testing backup methods for millions of small files on NAS and DAS
storage for YEARS here. Without exception, the best backup method has been NFS
mount via a “proxy” client. I don’t manage the NetApp Storage, but we saw an
increase from 10MB/sec to 17-19MB/sec when switching from NDMP
Rusty,
If you have a way to use Snapvault to backup to another location, I
would use it. We have a number of file systems like what you have. I
tried NDMP over TCP and NFS backups using dedicated snapshots mounted
on a client. Both used a dedicated 10G network. We basically overran
our 6030
26 matches
Mail list logo
