• Please be aware that ADSM.ORG will be going through forum software conversion and migration over the next several weeks. The cut-over date and time will be posted as we near the target date. Please visit the following link for more details ADSM News & Announcements
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Prevent missed schedule

smp

ADSM.ORG Member
Joined
Jun 12, 2018
Messages
11
Reaction score
0
Points
0
We are running SPVE 8.1.13.3 and we are using tag based backups. We have one schedule with 4 datamover nodes associated with it. The schedule is using the asnodename option which causes all VMs to be backed up with the same node name.

Our daily backup schedule is defined with the following options:
Options: -VMBACKUPTYPE=FULLVM -ASNODENAME=VCENTER1 -DOMAIN.VMFULL="SCHEDULE-TAG" -MODE=IFINCR

There are about 75 VMs tagged for each datamover.
Occasionally, a VM is being backed up and it takes more than 24 hours to complete. When this happens, the schedule assigned to the datamover for that VM is missed the next night; therefore, 74 VMs miss their backup.

What options do I have to allow the long running backup to complete but ensure the other VMs assigned to that datamover don't miss their scheduled backup the next night?
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,791
Reaction score
626
Points
0
Location
Canada
The only to avoid missing schedules because the previous one is still running is to ensure that each schedule run to completion before the next scheduled time. So you would need to tweak the environment so that backups consistently run in less than 24 hours. Ideally, a lot less than 24 hours.

You can try tuning those parameters to allow more simultaneous backup sessions to help the backups finish sooner: vmmaxparallel, vmmaxbackupsessions, vmlimitperhost and vmlimitperdatastore. More info:

You possibly need additional data movers.

The general idea is that if more work is done in parallel, it can finish quicker. Also, there could be bottlenecks that could impact performance and make the backup run longer.
 
  • Like
Reactions: smp

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 22 19.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 67 59.3%
  • Let's be formal and just say Spectrum Protect

    Votes: 15 13.3%
  • Other (please comement)

    Votes: 9 8.0%

Forum statistics

Threads
31,858
Messages
134,954
Members
21,834
Latest member
wilsocl
Top