We have been disk to disk for over a year now. We send all our data to data
domain and replicate to a data domain using the archive tier. We have some
longer retentions, 3 year, 5 year and 7 year. No tape of VTL is awesome.
+--
Runing 7.5.0.6 on windows 2003 x64 host, writing to a data domain. ESIx 5.0.
Our backups and restore of a VMDK works fine, but when we go to power on the
restored server (2008) it blue screens with a 0x7b. I have tested 2003 and 2012
which work fine.
If I power of the 2008 host back it up,
i just tested this senario. NDMP to a DD670 over the network. All I had to do
is have a valid license key for Netbackup. Set up a NDMP user on the VNX5700,
set up the NDMP backup policy in Symantec/Vertias.
Our File share was on a VNX5700
Our master/media was windows 2003 x64 7.0.1
Our Data
We use SLP for our backups and copies. We create our original backups to a
dd670 (2 weeks) and then spin off a copy to our remote dd670 with a different
retention period (5 weeks).
The SLP policy allows you to create a second copy to a different destintation
right after your backups has
We also have our Catalog connected to a LUN on the SAN. That we we can expand
the LUN if needed, as out catalog grows. We also make a catalog backup to our
DR site so that we could retreirve our catalog if the primary data center had
an issue.
We are running nbu 7.0.1 and there is a know issue with the exclude list not
working in cluster nodes. There is a hotfix available to fix this issue.
http://www.symantec.com/business/support/index?page=contentid=TECH150081
+--
I believe using NDMP or Flashbackups the image file will be much larger than a
normal backup. We saw this when some of our backups were using the flashbackup
option, so we had to change them to a DataDump instead of a flashbackup so the
catalog would stop growing so large
Yea, Data Domain want us to upgrade to 5.0.2.3 also but they cannot pinpoint
any reason for the code 84. Right now we are staying at 5.0.1.7 as the media
write errors are very very few now. I even asked datadomain to give the
solution id that specifically addresses the media write error in the
We had the same problem, media write errors. Seems to happen with long running
jobs most of the time. We ugpraded the Data domain code and OST code which
increased the timeouts to 3hrs from data domain. We also noticed are long
running jobs in which most of the 84 errors were coming from were
you can put each volume in serperatly and the job will spawn off a backup for
each volume.
Example:
\\.\D:
\\.\E:
\\.\F:
the job will spawn off three backup jobs one for each volume.
+--
|This was sent by
Currently our SQL team run SQL LiteSpeed with compresson. They really dont want
to turn it off.
We keep 5 weeks of data for our SQL backups and are getting 2.1 to 3.5 dedupe
ratio's even with compression backup on.
+--
|This
We are curretly having a problem with the robot daemon going down. We are
running windows 2003 x64 with an EMC 4406 VTL. We have 168 tape drives
configured but can only have about 50 running at one time. We have had up to 80
jobs running at once but about every 3-4 days the robot daemon goes
We are seeing our robot deamon go down when we have over 80 clients submitted
at the same time. We are running 6.5.3.a, emulating an EMC EDL and when we have
a bunch of clients submitted at one the the library deamon goes offline and we
have to reboot the windows media server.
Has anyone seen
13 matches
Mail list logo
