Hi,
Has anyone here backed up MSSQL databases that are mirrored within a
cluster?
I have several clients who run a sole MSSQL DB that backup without issue
in 6.5.x environments.
However, when the DBs are mirrored, if there are processes
cleaning/migrating data between a mirrored pair, the
Snapshot client? I guess you'd still be 24hrs + time to take the snap
but that should be negligible...
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dean
Sent: 16 July 2010 05:54
To: veritas-bu@mailman.eng.auburn.edu
Subject:
You are quite correct and it is something that I have pointed out several times
to rather puzzled managers. We don't sell a service but for most systems the
RPO is 24 hours. I have pointed out that for many systems where they take a
FULL backup on Friday, and Cumulative Incremental on Mon,
I don't think this problem is a NBU issue. It looks like Solaris has lost the
drives. You need to rescan the devices to make sure that Solaris can see the
drives. I believe you can run devfsadm -c tape to have the system rescan for
devices or issue a touch /reconfigure then reboot the
Check into synthetic fulls...especially optimized synthetic fullsthat way
you are only really doing a differential every night and letting NBU handle the
creation of the full...this should dramatically shrink the time it takes to do
the backups.
From:
On Thu, Jul 15, 2010 at 11:54 PM, Dean dean.de...@gmail.com wrote:
Silver is 24 hours. The large majority of our backup clients fall into this
category. Silver class is all based on tape backup/recovery. It's the
traditional overnight backup to tape (or disk, VTL, whatever) fulls on
the
If the devices are scsi attached, you can take the system down to the OK
prompt and run probe-scsi-all to verify that at the OS level, the drives
are being presented. This page tells you how to do it:
http://www.tech-recipes.com/rx/114/troubleshoot-scsi-devices-with-probe-scsi-all/
This is the only thing I can think of.
Document ID: 327105
http://support.veritas.com/docs/327105
A potential for System State data loss has been discovered in NetBackup Server
/ Enterprise Server 6.5.4. This occur when the System State is selected for
backup and snapshot error control is
Is the reported elapsed time including the time that job spent in queue? If so
that would explain this, as now I have nearly 1,000 jobs queuing at night that
could explain the jump in total elapsed time yet decreased backup times.
Yes,
There are two columns
Elapsed time - includes queued
Active Elapsed - only active time.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Brandon35
Sent: Friday, July 16, 2010 11:25 AM
To:
Thanks for the info. I see Active Elapsed as a selectable column in my
Activity Monitor, but unfortunately, I can't get that column in my Reports for
historical info... I'm thinking command line may be able to pull this info for
me. I am researching, will post my findings :)
Is anyone out there using a Data Domain with the OST plug in for NetBackup?
(Especially if you are running NBU 7) Can someone give me a rough idea what
kind of performance numbers you are gettingjust looking for an average mb/s
per stream on typical backup jobs. Don't need a lot of
Renee,
We're testing OST as I write this !! We've actually been testing OST and the
new dedupe in NBU 7.0. We've been running our exchange backups to an OST
storage unit and have seen higher throughput speeds compared to our regular
CIFS backups in the limited testing we've done (40mb./sec
Thank you all for the responses.
We do already offer a Bronze service class, which is basically best-effort.
But most of the systems fall into this 24 hour Silver category.
Doing daily differential incrementals then synethetic backups wouldn't
really change the fact that in the worst case, our
14 matches
Mail list logo
