I would say firstly: disregard shares... NDMP is performed at the volume level,
so that is what I would be looking at (vol status or df)
For me, we track the backups using change control (so our documentation
required for creating a new volume also highlights the requirement for a backup
Hi folks,
My customer has implemented an offsite strategy that calls for tapes from the
previous night's backups to be suspended after the backup cycle so that they
can be completely replicated offsite from the production VTL. A job is run
every day at 14:30 pm that suspends the tapes
Suspend prevents new jobs from selecting the tape. Although I've not seen
this myself it makes sense to me that a suspend done after the tape was
assigned would have no effect on that existing assignment. To have a backup
release a tape the best way to do it would be to suspend the backup
Hello,
You cannot change the attributes of a tape when the tape is in use.
I had the same problem with you and my solution was to make the script to
track the tapes that ware in use and exclude them from any action or report.
We had to be sour that the tape was exported or duplicated with the
Thanks smpt1,
I think we will integrate the script with VTL reporting to get a list of the
tapes that are in the VTL when the suspend job is run, then we can run the
suspend script against that list later (either manually or automatically).
Thanks,
Mark
From: smpt
In a previous life where we had weak change control and this scenario was a
problem, I wrote a script to dump and sort the policy (bppllist -l... | grep
^Include: | sed…| sort…), and compare that list to a similarly transformed
list of ls /net/$filer/ on the (Solaris) NetApp management host,
Hi,
I have solved this problem by gathering (every morning) a list of all the
netapp volumes in my estate (vol status), and a list of all my netbackup
policies (bppllist), and effectively doing a difference between them..
No difference = No volumes being missed by netbackup
Differences =
Hi,
For those using OpsCenter-- is it very slow for anyone, does it run
quickly for any customers using it?
Been using it with several master servers, its so slow (5-10+ min to
load).
Any optimization tips/etc?
One ops center server per master maybe?
Justin.
My VM that had our test OpsCenter vapourised but it was fine while it was
available, certainly not obviously worse than NOM. What we did do was the
tuning documented in the NOM guides to set the DB cache a bit bigger - there is
a section that is basically Sybase tuning.
I admit that it was
