Hi Guys,
We have since a while status 25 (socket write failed errors).
We have a P1 case open with Symantec but they are as clueless as we are.
Environment: 1 Solaris Master, 2 Solaris Media Servers (10Gbit connected), Data
is backed up to DSSU, restores are coming from both tape and disk (same
Then run /usr/openv/netbackup/bin/vltopmenu to generate the reports.
Regards,
Patrick Whelan
VERITAS Certified NetBackup Support Engineer for UNIX.
VERITAS Certified NetBackup Support Engineer for Windows.
netbac...@whelan-consulting.co.uk
From:
Depending on your environment, you can define it in your vm.conf
# cat /usr/openv/volmgr/vm.conf
ACS_UNKNOWN=HCART
ACS_LTO_1_5T=HCART
I have an acsls, so that is how it is defined. I chose hcart, since I was not
using it already.
Apparently there is no hard and fast rule yet about LTO5, so you
Hi
Thx, using LTO4 as hcart so will need to use hcart2 I suppose.
Justin
On Sep 14, 2011, at 1:34 PM, David McMullin
david.mcmul...@cbc-companies.com wrote:
Depending on your environment, you can define it in your vm.conf
# cat /usr/openv/volmgr/vm.conf
ACS_UNKNOWN=HCART
My problem seems to be with the backup part of this. The database portion of
the backup is successful, however the GRT part fails with a status 1 (9/14/2011
12:53:52 PM - Error bpbrm(pid=4380) from client dag1: ERR - Unable to obtain
image list. Confirm this client has access to images on
I think VNX was meant, and not CNX. VNX is just the replacement to the CX
lineup.
RMAN is your best option, you would not backup from the NFS mount, you would
backup to where ever RMAN is configured to spit out the backup files.
During data migration of retention 10 year IMAGES from LTO/3 to LTO/5 I
noticed the old IMAGES (2009), written on the tape expires in 2021 and not
in year 2019.
I use Netbackup Enterprise Server 7.0.1, and in the version 6.0MP7 it
works propertly. I will say I do this migration not the first
