Hello
Starting in version 7.1.5 ( I think ), we changed so that you can update
the default per week. If it isn't too much trouble, you can change the
default to 7 or 8 weeks. Then you can change the other machines to use a
custom value that we support. This isn't a good option if you have a lot of
clients.
The other option is to use the command builder to update the 4 clients,
this way you don't have to leave OC.
Rob Jose
Spectrum Protect OC UI Developer / L3 Support
-----Original Message-----
From: Stefan Folkerts [mailto:stefan.folkerts AT GMAIL DOT COM]
Sent: Wednesday, June 14, 2017 3:54 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Operations Center at risk setting jumps from 30 to 60
days
@Remco, do you mind sharing? I can only set custom at risk settings for the
defaults, I can't find where I can set (ie) 31 day's for 4 servers using
the GUI.
On Wed, Jun 14, 2017 at 11:15 AM, Remco Post <r.post AT plcs DOT nl> wrote:
> > On 14 Jun 2017, at 11:08, Stefan Folkerts
> > <stefan.folkerts AT GMAIL DOT COM>
> wrote:
> >
> > Thanks Steven, too bad you can't set this in the GUI.
>
> yes you can
>
> > Trying to keep this
> > customer on the OC for as much as possible.
> >
> > On Wed, Jun 14, 2017 at 9:40 AM, Harris, Steven <
> > steven.harris AT btfinancialgroup DOT com> wrote:
> >
> >> Hi Stephan
> >>
> >> Set vmatriskinterval
> >>
> >> Syntax
> >>
> >>>> ---Set VMATRISKINTERVAL--node_name--fsid---------------------->
> >>
> >>> --TYPE--=--+-DEFAULT--+--+--------------------+---------------><
> >> +-BYPASSED-+ '-Interval--=--value-'
> >> '-CUSTOM---'
> >>
> >> Type is custom and interval is in *Hours* between 6 and 8808 (367
> >> days)
> >>
> >> Oh Heck. I had plans to set it much higher, as we have to keep
> monthlies
> >> for 7 years even after decommission. I will have to set to
> >> bypassed instead.
> >>
> >>
> >> Cheers
> >>
> >> Steve
> >>
> >> Steven Harris
> >> TSM Admin/Consultant
> >> Canberra Australia
> >>
> >> -----Original Message-----
> >> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> >> Behalf
> Of
> >> Stefan Folkerts
> >> Sent: Wednesday, 14 June 2017 5:05 PM
> >> To: ADSM-L AT VM.MARIST DOT EDU
> >> Subject: [ADSM-L] Operations Center at risk setting jumps from 30
> >> to 60 days
> >>
> >> Hi all,
> >>
> >> Is there a way to manually set the at risk for a node to, for
> >> example,
> 31
> >> days?
> >> Monthly backups now have to be set to 30 or 60, both isn't what we
> >> want because 30 will cause false positives and 60 is a bit too late.
> >>
> >> The default can be set to 5 weeks for example, I think the best
> >> would be if we have the resolution of the default settings per node
> >> (or
> selection of
> >> nodes) in the OC.
> >>
> >> Regards,
> >> Stefan
> >>
> >>
> >> This message and any attachment is confidential and may be
> >> privileged or otherwise protected from disclosure. You should
> >> immediately delete the message if you are not the intended
> >> recipient. If you have received this email by mistake please delete
> >> it from your system; you should not copy
> the
> >> message or disclose its content to anyone.
> >>
> >> This electronic communication may contain general financial product
> advice
> >> but should not be relied upon or construed as a recommendation of
> >> any financial product. The information has been prepared without
> >> taking into account your objectives, financial situation or needs.
> >> You should
> consider
> >> the Product Disclosure Statement relating to the financial product
> >> and consult your financial adviser before making a decision about
> >> whether to acquire, hold or dispose of a financial product.
> >>
> >> For further details on the financial product please go to
> >> http://www.bt.com.au
> >>
> >> Past performance is not a reliable indicator of future performance.
> >>
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post AT plcs DOT nl
> +31 6 248 21 622
>
|
