We have done this with DD OST plugin, NBU 6.5.4 and Exchange 2007. The
problem is that GRT backups could not be duplicated manually, or with an
SLP. It would do horrible things. Currently not using GRT for exchange.
We are using GRT for sharepoint, but also running non GRT fulls to
duplicate
Morning All,
We have Exchange 2003 on windows 2003 Enterprise servers with SP2.
We were using Netbackup 6.5.5 to backup these servers successfully but
we upgraded to 7.0.1 and since then the mailbox backups have failed with
Status 69.
We do have EV 8.0 SP3 in our environment but as far as I
I think that the problem with the duplication is fixed with a patch and at
7.1
7.1 has a different problem. Some mailboxes are not browseable.
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of David
Stanaway
Sent: Wednesday,
Kevin
Is the client account running as system?
As a test, try running it with a Domain Account that has Exchange rights
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Kevin
O'Connor
Sent:
It’s running as a system account but has never had an issue.
Our test environment was set up the same way and worked.
Kevin O'Connor
Storage Administrator
From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net]
Sent: 13 April
Could be something to do with LSA on the box.
This is why I suggested trying with a Domain Account as a test.
From: Kevin O'Connor [mailto:kevin.ocon...@esbi.ie]
Sent: Wednesday, April 13, 2011 12:51 PM
To: WEAVER, Simon (external);
Hello Geeks,
We take backup of our windows machines using BMR.Using BMR 6.5.4NOw yesterday
one of our machines crashed and so we tried to recover it by BMR.
EVerything was going fine but suddenly we got the below error.
Unable to make Registry modification required to boot the system is
Wish I would have read this yesterday. I'm in the middle of an
upgrade right now and all my window's policies are slowly being
converted right now. I figure it should finish in 10 hours. I'm
very lucky to have the ability to keep this env down this long.
Little upset that this known issue
Sorry thought I would add that you need to determine the target number that
your device(s) are seen thru. I usually connect each drive directly to my
storage switch and then zone it so that I'm not overloading any HBA channels.
(typically 4-5 LTO4 caliber drives per 4gb channel - this depends
This depends on your library and how the LUNs are presented. Some libraries
present each device as a target and not individual LUNs under a target so if
you had 5 devices your st.conf would look like this:
name=st class=scsi target=0 lun=0;
name=st class=scsi target=1 lun=0;
name=st class=scsi
I've heard from a few shops running protectier that they had a lot of problems
after upgrading to 7.0.
Thx for any info,
CC
+--
|This was sent by chuck.car...@gmail.com via Backup Central.
|Forward SPAM to
We are running a RedHat Enterprise Linux (RHEL) 6 master with 7.1.
We've been doing backups for a few days without much trouble.
Today I setup vaulting and kicked it off. It is mainly doing
duplication from Data Domain and Quantum DXi deduplication units to
LTO5.
Shortly after
Hello all,
We have a large NetApp volume (14TB) that we are trying to backup through NDMP.
The job is still running after 71 hours and it is reporting 25TB currently
written. This volume is being deduped with NetApps block-level dedupe, so
maybe I'm not understanding the true size of the
13 matches
Mail list logo
