Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-77-1019715.1
Update Date:2010-08-11
Keywords:

Solution Type  Sun Alert Sure

Solution  1019715.1 :   Restart of VTL Services May be Required After Daylight Saving Time (DST) Change  


Related Items
  • Sun StorageTek VTL Plus Storage Appliance
  •  
Related Categories
  • GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
  •  
  • GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
  •  

PreviouslyPublishedAs
244446


Bug Id
<SUNBUG: 6763139>

Product
Sun StorageTek Virtual Tape Library Plus Storage Appliance 1.0
Sun StorageTek Virtual Tape Library Plus Storage Appliance 2.0

Date of Workaround Release
27-Oct-2008

Date of Resolved Release
27-Oct-2008

Restart of VTL Services May be Required After Daylight Saving Time (DST) Change

1. Impact

Any Sun StorageTek Virtual Tape Library (VTL) system that has “time based” policies configured (i.e., Automated Tape Caching, Replication) will need to restart the VTL services after the time change for Daylight Saving Time (DST). Failure to restart VTL services may cause the schedule for the time based VTL jobs to be off one hour after the time change, until the next restart of VTL services.

2. Contributing Factors

This issue can occur on the following platforms:
  • Sun StorageTek Virtual Tape Library (VTL) 1000/2000/3000 Software (for Solaris or Linux)
VTL time based policy schedules do not pick up any server time changes, except when services are restarted.  This includes if using NTP or if the server time is changed via the VTL Console GUI.

3. Symptoms

After the server time changes, the VTL time based policy scheduled jobs (i.e., ATC migration jobs) may happen plus/minus the difference from the actual time. The schedule for the time based VTL jobs will be off until the next restart of VTL services.

4. Workaround

To work around this issue, stop/suspend backup/migration jobs and restart VTL services.
 
VTL services can be restarted via VTL Console (right click server name -> System Maintenance -> Restart VTL) or from a command line:

# vtl restart

Notes:

1. For HA configurations, either first initiate manual failover of one node prior to restarting VTL services (then repeat for other node), OR suspend failover on both nodes, then restart VTL services on both nodes and resume failover on both nodes when done.

2. Backup jobs directed at VTL are handled by the Backup Application/Server and do not require VTL restart.  If no time based policies are configured in VTL the restart of VTL is not necessary.

5. Resolution

Please see the Work Around section above.

Modification History
11-Aug-2010: No further updates. Republished Resolved.

Internal Comments
Please send technical questions to the following email:
sunalert-tech-questions@sun.com
and CC the following persons:
Internal Eng Responsible Engineer
Internal Services Knowledge Engineer
VTL patch is targeted for 1QCY2009, so that the restart of VTL services
will not be needed for server time changes.

Internal Contributor/submitter
Dan.Spratt@Sun.COM

Internal Services Knowledge Engineer
Dan.Spratt@Sun.COM
Internal Services Knowledge Engineer
david.mariotto@sun.com
Internal Eng Business Unit Group
NWS (Network Storage)
Internal Sun Alert & FAB Admin Info
24-Oct-2008, david m: Originally drafted as FAB, now SA - Completed draft and sent to Review
27-Oct-2008, david m: review completed, send to publish


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback