Hi ,

You must deploy 1 VBA for 1 Vcenter

You can create only 2 policies : 1 for daily with 2 actions (bck/clone) and 1 for monthly with 2 actions (bck/clone) with appropriete retention .

You may use only 1 policies with 2 actions (bck/clone) and then using nsrmm in order to change specific ssid retention (for vba backup use mminfo -k ...)

Remember that in order to protect you vba you must create policies for discovery/backup of vba check points.

You can associate VMs with a policies by name,directory,entire esx or entire Vcenter automatically.

You also may decide which vmdks protect or not (DB datafile partition for example)

regards,

-Nicola

HI mrakM

what you describe seems to be by design :

all backup done during a month ,except the last day of the month, will have a retention period of 32days.

All backups made on the last day of the month will have retention period of 190 days.

So in December you can restore only the backup done on  30 Sep (not other days of September i.e. 10th)

-Nicola

Thanks Nicola, yes I did also something similar, but as I already explained, the theory is fine, but using it in production is not so simple.

You can create only 2 policies : 1 for daily with 2 actions (bck/clone) and 1 for monthly with 2 actions (bck/clone) with appropriate retention .

But how to scheduled it properly, with separated admin roles.

Let’s have an example:

P1 is policy for daily backup with schedule Daily Incr and retention 32 days.

P2 is policy for monthly backup with (full on last day in month, skip other days and retention 190 days)

At 3rd Sep, we've got 10 new VMs installed and responsible VMware admin assigned new VMs to both P1 and to P2, so all done.

P1 is scheduled for daily backups, recognized new VM and promoted incr. backup to full but only for 32 days.

AT 5TH Sep additional 5 VMs are installed with similar scenario and later more and more

of VMs are being added to the VDP policies

So now you can imagine how your are data protected.

And the best in this example story:

at 15th Oct. 5 VM were decommissioned, and 2 months later some of data which were backed up at 10th. Sep. should be recovered (but these data were backed up only for 32 days?!?)

.

errata corrige:

mminfo -k -ot -r name,savetime,ssretent

-Nicola

In addicition:

try from backup server cli :

mminfo -k -c -ot -r name,savetime,ssretent

regards,

-Nicola