ato_release_notes.pdf
DESCRIPTION
ato_release_notesTRANSCRIPT
ATO Release Notes Version 2.1.4e November 23, 2010
ATO Release Notes
Page - 2
RELEASE NOTES VERSION 2.14e
Introduction.................................................................................................................................................................................... 3
Getting Help ................................................................................................................................................................................... 3
Web Access to Powerlink.......................................................................................................................................................... 3
Information Required for Prompt Issue Resolution................................................................................................................... 4
Your Comments ........................................................................................................................................................................ 4
End of Life Notification ................................................................................................................................................................. 5
Release Dates ................................................................................................................................................................................. 5
New Features, Improvements or Enhancements ............................................................................................................................ 7
Release 2.1.4e ....................................................................................................................................................................... 7
Release 2.1.4d....................................................................................................................................................................... 7
Release 2.1.4c ....................................................................................................................................................................... 7
Release 2.1.4a ....................................................................................................................................................................... 7
Release 2.1.4......................................................................................................................................................................... 7
Release 2.1.3a - c .................................................................................................................................................................. 7
Release 2.1.3......................................................................................................................................................................... 8
Release 2.1.2......................................................................................................................................................................... 8
Release 2.1.1......................................................................................................................................................................... 8
Release 2.1.0......................................................................................................................................................................... 8
Release 2.0.0h....................................................................................................................................................................... 8
Release 2.0.0g....................................................................................................................................................................... 8
Release 2.0.0f ....................................................................................................................................................................... 8
Release 2.0.0e ....................................................................................................................................................................... 8
Release 2.0.0c ....................................................................................................................................................................... 9
Release 2.0.0......................................................................................................................................................................... 9
Release 1.2.3c ....................................................................................................................................................................... 9
Release 1.2.2......................................................................................................................................................................... 9
Release 1.2.1b....................................................................................................................................................................... 9
Release 1.2.0......................................................................................................................................................................... 9
Release 1.1.10....................................................................................................................................................................... 9
Release 1.1.9......................................................................................................................................................................... 9
Release 1.1.8......................................................................................................................................................................... 9
Release 1.1.7......................................................................................................................................................................... 9
Release 1.1.6....................................................................................................................................................................... 10
Release 1.1.5....................................................................................................................................................................... 10
Release 1.1.2....................................................................................................................................................................... 10
Release 1.1.1....................................................................................................................................................................... 10
Release 1.0.9....................................................................................................................................................................... 10
Release 1.0.8....................................................................................................................................................................... 10
Issues Resolved ............................................................................................................................................................................ 12
Known Issues and Limitations ..................................................................................................................................................... 16
ATO Release Notes
Page - 3
Introduction ATO is a scripted utility used to perform rehydrated tape out operations from an Avamar system. Tape Out refers to a process of first defining the individual clients to act on and selecting specific backups from them which are then recovered to a predefined staging server location. After the recovery or staging phase is complete a tape backup using a traditional tape backup product can be initiated either automatically or on demand to backup the staged data directly to tape.
Getting Help Support for all EMC products is provided by way of Powerlink — EMC’s dedicated customer support and services web site. When you have an issue, EMC Technical Support will work with you to identify and assist with resolving the problem. To ensure secure and reliable support, EMC requires designated customer contacts as the only individuals authorized to contact and communicate with our support representatives. Designated customer contacts will be recorded in forms attached to your EMC Software and Hardware Service Agreement.
Web Access to Powerlink
Before you install the ATO Utility, be sure to read the most recent product release notes or technical notes that are currently available to determine if any identified issues might affect your use of it. If necessary, you can create a service request for support by using the form on the Powerlink Web site to request the latest documentation and script file.
Telephone Support North America (English)
Hotline: +877.534.2867 (option #2)
Hours: 06:00 - 18:00 Pacific Time
ATO Release Notes
Page - 4
Information Required for Prompt Issue Resolution
When contacting EMC Technical Support, please have the following information available so that we can promptly and efficiently process your support request:
1. Current service request number, if a number has already been assigned. 2. Your name and current return phone number. 3. You must be a designated customer contact in order to communicate with EMC Technical Support
representatives. 4. Your master customer number (if you have been issued one). 5. Site address where the issue is occurring. 6. A detailed description of the issue, including all steps for issue replication, if the issue can be replicated. 7. A description of the specific environment, including type of user involved, client operating system and
application type and version. 8. Any related error messages. 9. Recurrence: Whether the issue has occurred before or is a new occurrence. 10. You may be asked to email, fax or upload to Powerlink copies of relevant information such as screen shots,
error messages, and error logs or an ATO -grab.
Your Comments
Your suggestions will help us continue to improve the accuracy, organization and overall quality of the user publications. Please send your opinion of this document to:
Please include the following information: • Product name and version • Document name, part number and revision (for example, A01) • Page numbers • Other details that will help us address the documentation issue
ATO Release Notes
Page - 5
End of Life Notification Implications related with ATO end of life are few however, as enhancements are made or bugs corrected it will be necessary for existing users to upgrade their existing version with the latest as only the most recent version of the ATO code will be maintained. Implications related with updating to a new version of ATO will be documented to ensure a smooth transition but in general there are typically none with the rare exception being when a new variable may be added or modified to the environment file or a new field to the client configuration file. In these cases you may need to manually edit existing files as required but ATO now provides an upgrade option to perform the process for you.
Release Dates Version 2.1.4e – November 23, 2010
Version 2.1.4d – November 18, 2010
Version 2.1.4c – November 1, 2010
Version 2.1.4a – October 29, 2010
Version 2.1.4 – October 20, 2010
Version 2.1.3c – October 3, 2010
Version 2.1.3a – September 24, 2010
Version 2.1.3 – September 18, 2010
Version 2.1.2 – August 29, 2010
Version 2.1.1 – August 10, 2010
Version 2.1.0 – July 31, 2010
Version 2.0.0h – July 17, 2010
Version 2.0.0g – July 9, 2010
Version 2.0.0f – July 2, 2010
Version 2.0.0c – June 14, 2010
Version 2.0.0 – June 2010
Version 1.2.3c – April 23, 2010
Version 1.2.2 – April 8, 2010
Version 1.2.1b – April 6, 2010
Version 1.2.0 – March 20, 2010
Version 1.1.10 – March 06, 2010
Version 1.1.9 – February 28, 2010
Version 1.1.8 – February 18, 2010
Version 1.1.7 – February 12, 2010
ATO Release Notes
Page - 6
Version 1.1.6 – February 8, 2010
Version 1.1.5 – February 2, 2010
Version 1.1.4 - January 05, 2010
Version 1.1.3 - January 02, 2010
Version 1.1.2 - December 21, 2009
Version 1.1.1 - December 19, 2009
Version 1.0.9 - December 15, 2009
Version 1.0.8 - December 06, 2009
Version 1.0.7 - November 10, 2009
Version 1.0.6 – November 09, 2009
Version 1.0.5 - November 04 2009
Version 1.0.4 – October 28, 2009
Version 1.0.3 - October 24, 2009
ATO Release Notes
Page - 7
New Features, Improvements or Enhancements This section introduces new features, improvements or enhancements added since release 1.0.8 of ATO.
Release 2.1.4e
• Enhanced Backup Exec support to provide client initiated tape backups whether they have a predefined job policy or are user defined
• Enhanced –tpolicy option to support multiple arguments
• Added to Batch Manager the ability to edit the CRON directly
Release 2.1.4d
• improved batch job summary
• corrected bug with cancel feature
• improved view with Networker dedup node to display long save set names
Release 2.1.4c
• security enhancements
• Added a job summary to batch and event logs making it easier to determine completion status and
identify failures when running batch jobs
• In configuration Manager, added timestamp to show last discovery time
• Added new environment variable BYDATEPATHEXT to enable or disable an expanded
destination staging folder name with non-incremental TO. When set to Y the destination folder
will now have appended to the default name of yyyy-mm-dd-hh-mm-ss-buid# the retention tag
type and expiry date of the Avamar backup-ids involved. Default setting is N
• Added ability to cancel an active batch job from Batch Manager
• Added ability when executing a batch job from Batch Manager to override its configured
environment-#
• Added a browse function in Batch Manager to review results from the last job execution only
Release 2.1.4a
• Modified how ATO detects Read-Only status
• Modified tape script behavior for HPDP to enable the user to specify the tape backup mode
• Modified Menu selections to consolidate the Environment file functions into one
Release 2.1.4
• Bug fixes related with Backup Exec automated tape support
• Added new environment lock detection mechanism to prevent the potential for batch jobs to
overlap each other
• Added new select filter –rday # enabling backup selections based on a specified day of the month
only
Release 2.1.3a - c
• Bug fixes related with Backup Exec automated tape support
• Bug fixes with discovery of replication systems
• Bug fixes when using the new networker_save definition in the environment file
ATO Release Notes
Page - 8
• Bug fixes with reported run times
Release 2.1.3
• Added new tape backup application definition for Networker named networker_save leveraging
the Networker save command during the tape backup useful for non-incremental to increase tape
backup throughput
• Modified End-of-Year tape policy behavior enabling any valid calendar month to used
• Added new environment file variable allowing defining where backup and grab files are kept
• Added a locking mechanism preventing execution of critical functions from overlapping each
other
Release 2.1.2
• Updated Backup Exec support for auto generated tape script
• Improved email alters subject line now contains Avamar host name, environment number and
group name
• Added filtering support for Exchange VSS –exchvss and Windows VSS (systemstate) –vss
backups providing reporting capability only. Currently there’s no support to tape out these backup
types.
Release 2.1.1
• Updated Backup Exec support
• Added ability for user to choose their preferred editor defined in the ATO environment file
• Updated doc relative to using email alerts and improved parse checks on email address’s
Release 2.1.0
• Updated Backup Exec support
• Bug fixes
Release 2.0.0h
• Enhanced ATO batch profile initiation procedure when using a Networker pnpc script. The new process provides a
consistent configuration method for both single and bulk profiles and each will now reflect their final completion
status within the NMC GUI. Their corresponding logs are still maintained with Batch Manager.
• Administration Guide has been updated with the above procedures
• Bug fixes
Release 2.0.0g
• Bug fixes
Release 2.0.0f
• Bug fixes
Release 2.0.0e
• Bug fixes
ATO Release Notes
Page - 9
Release 2.0.0c
• Improved status reporting when avtar is used to perform the staging process used primarily with
non FS plug-in’s
Release 2.0.0
• Added file system support for Networker dedup node for Windows and Unix clients
• Added status check and display of Avamar maintenance tasks
• Added auto generated tape script support for Backup Exec
Release 1.2.3c
• Added preliminary support for performing file system tape-out from a Networker dedup node
Release 1.2.2
• Added ability preliminary to execute multiple batch profiles as one job. Any number of individual
batch profiles may be included within a bulk batch profile which will run sequentially with no
time delay between each. Monitoring and logging in Batch Manager remains consistent.
Release 1.2.1b
• Added ability to select exchange backups based on database or message level. Refer to limitation
section #10 for details
• Improved parse checks for environment files to better detect invalid syntax in Windows path
definitions
Release 1.2.0
Release 1.1.10
• Added support for vmimage backups available only with Avamar 5.x or higher. Refer to
–vmimage option available on the –select action.
Release 1.1.9
• Added ability to call a user defined pre and/or post script from within the auto generated tape
script. Refer to –upre <pre-script-name> and –upst <post-script-name> options available with the
–tapeout action.
Release 1.1.8
• Added support for interactively updating ATO environment files
• Added support for SCO and Netware clients
Release 1.1.7
• Added a new option –tpolicy <tape-policy-name> available with the –tapeout action. If specified
it will override the tape policy defined within the client configuration file. A use case might be if
weekly and monthly TO’s are required for a set of clients and different tape retention periods are
needed. Rather than establishing another client group with different tape policies defined you can
now use the original client group and pass the desired tape policy to it as needed from the call line.
ATO Release Notes
Page - 10
• Added additional administration functions in menu Opt-12 including a file locator and health
check which parses available environment and client files and captures the last execution status
from each batch log. Grab has been updated to automatically perform and include the health check
results saved in file /tmp/atohealth-check.txt
Release 1.1.6
• Added functionality to manage backing up the ATO environment including the ability to rollback
and for managing ATO grab files. These are available from menu Opt-2-ATO Administration. Or
from command line with –backup –backup rollback and -grab
Release 1.1.5
• Added new ATO menu selection #13 or from command line ato –upgrade to facilitate an
automated upgrade process. This provides the framework to automatically add or configure new
environment file variables or adjust the client configuration file if required. To use, alwys ensure
the latest ATO tar file is placed in /usr/local/Avamar/src on the Utility node or Red Hat client as
applicable.
• Expanded the ATO Grab diagnostic to also include an ATO Backup function. Useful to protect the
ATO configuration files and it will automatically invoked when running the upgrade process.
Release 1.1.2
• Added support to use ATO as a front-end wrapper interface for latest version of AST. In this mode ATO is installed on a Red Hat client as opposed to the Utility node.
Release 1.1.1
• Added support for Arcserv/Brighstore auto generated tape scripts
• Fld-12,13,14 in client configuration file may now contain additional valid parameters to be passed to the tape backup command syntax as required
• Added –server option on –tapeout action to provide the means to initiate the tape backup from the tape backup server versus the default of using the staging client. This will require the manual addition of 2 new variables to any existing environment files established prior to this release in the Tape Backup section. Add new variables TAVAINSTALLPATH and TAVADOMAINNAME using the Environment file update option from the ATO menu.
• Added support for an interactive process to perform -tapeout sessions from ATO menu
• Added support for interactive retry or rerun of a ATO checkpoint directly from Recovery Manager
Release 1.0.9
• Added support for selecting clients from the MC_RETIRED domain in Configuration Manager
Release 1.0.8
• Added an interactive process to perform –select sessions from ATO main menu
• Added an audit log to track changes impacting how a given client would be recovered from tape. Over time a TO environment may change impacting where an operator would locate a backup on tape. The Audit process captures these changes and the date they took effect. To access from the Configuration Manager choose any view where individual clients are displayed then select the T=Audit option.
• Added -gname filter to the -select action to allow selecting backups belonging to a given policy group name only
• Added –rtype filter to the -select action to allow selecting backups having a given retention tag type
• Added ATO grab option available on command line with –grab or from ATO’s menu
ATO Release Notes
Page - 11
• Added support for Lotus Notes plug-in
ATO Release Notes
Page - 12
Issues Resolved The following table lists issues or bugs which have been resolved.
Bug-
ID#
Issue / Resolution Release
75 Corrected bug with batch job summary showing no staging status when a staging item failed
2.1.4e
74 Corrected bug with cancelling a checkpoint session 2.1.4e
73 Ensure by default one upper case –D debug flag is included in newly created batch profiles to ensure tape details are captured to the batch log
2.1.4c
72 Corrected behavior of debug flags in various places 2.1.4c
71 Corrected syntax of generated TSM tape script and eliminated the verbose o/p from TSM at the end of the tape backup from the ATO event and batch logs. To include this o/p include at least 4 upper case –D debug flags
2.1.4c
70 Corrected bug when used with a Networker dedup node whereby the tape backup RC was being interpreted incorrectly
2.1.3e
69 Corrected bug which prevented proper discovery of all possible domains when used on a replication target system.
2.1.3c
68 Corrected bug caused by incorrect syntax when using networker_save as the defined backup product
2.1.3c
67 Improved accuracy of reported runtimes during the staging and tape backup phases 2.1.3c
66 Ensure any blank lines are removed from a Backup Exec input script file 2.1.3c
65 Corrected bug when modifying a client entry in the Configuration Manager there was a potential to corrupt the file when similar client names were involved.
2.1.3.c
64 Modified behavior of tape initiation when using Backup Exec. Client initiated backup now functions correctly utilizing Fld-12 and 13 contents from the client configuration file.
2.1.3a
63 Corrected bug where recent new variables within the environment file were not being established automatically at initialization time.
2.1.3
62 Corrected view where AIX clients were showing up as a undetermined plug-in type with a zero byte size
2.1.3
61 Added support to ensure the mcclimcs.xml file exists
/root/.avamardata/var/mc/cli_data/prefs/mcclimcs.xml
60 Added check to ensure the /clients domain exists 2.1.3
ATO Release Notes
Page - 13
59 Corrected bug when using the –tpolicy option if its corresponding arguments contained leading hyphen characters “-“. They were being interpreted by the ATO syntax checker as an ATO option and detected as being illegal.
2.1.3
58 Corrected handing of duplicate client names in Configuration Manager 2.1.2
57 Corrected bug with email alerts when only one destination address was defined in the environment file
2.1.2
56 Corrected bug where two email alerts were being sent during a –tapeout when an error was detected.
2.1.2
55 Corrected bug with Configuration Manager so that displayed columns align with each other
2.1.2
54 Bug corrected auto generated tape scripts when using Backup Exec. ATO Admin Guide will be updated to document specifics related with using Backup Exec
2.1.0
53 Bug correction with parsing the client config file, it failed to detect when an invalid staging path was defined for a Windows staging server
2.1.0
52 Bug correction when parsing an environment file used for backup Exec it would say it is a non supported application
2.1.0
51 Corrected bug in Configuration Manager induced with correction for bug#50 2.0.0.h
50 Corrected issue in Configuration Manager when more than 1000 clients exist. Display would truncate a portion of the reference number making it impossible to select these clients for configuration.
2.0.0g
49 Corrected issue when using the –path option, if more than one backup was selected only the first would utilize the user defined path
2.0.0.g
48 Corrected problem with determining required Avamar authentication 2.0.0f
47 Corrected issue with the –oracle switch not being accepted 2.0.0e
46 Corrected issues when using Solaris staging server 2.0.0e
45 Corrected behavior when initially establishing environment files. 2.0.0c
44 Corrected problem related with ERROR-11C messages when using Unix based staging servers. Problem was related with path definitions.
2.0.0c
43 Corrected logic error with a batch job initiated by Batch Manager whereby if the client group was not found the batch process would fail with no error message logged.
2.0.0
42 Corrected behavior when called by an external scheduler or script where various calls were unable to authenticate to Avamar
2.0.0
41 Corrected bug with auto generated tape scripts for Unix & Linux where the final results of the tape backup were not being captured properly resulting in a false error status being reported.
1.2.3c
40 Corrected bug when using -server option to initiate tape backup from a windows based tape backup server. Problem symptom was the tape phase would loop displaying a failed awk command.
1.2.3c
39 Corrected bug in Recovery Manager where the selected backups were accurate but the displayed group name was not. If the checkpoint was rerun it would use the incorrect group name.
1.2.3c
38 Corrected bugs with the health check when parsing available environment files. Only the first was being processed correctly.
1.2.2
ATO Release Notes
Page - 14
37 Corrected bug where ERROR-06G was displayed in error when environment file variables TAVAINSTALLPATH and TAVADOMAINNAME were set to not-used preventing a TO session from progressing.
1.2.1b
36 Corrected bug when using avtar mode used for non standard plug-ins such as –lotus or –ndmp etc. The problem manifested itself as an error-code 10007 reported in Activity Monitor and by ATO
1.2.1b
35 Corrected bug in health check which prevented the environment files from being verified properly.
1.2.1
34 Corrected bug during the -tapeout process if multiple backups are selected for a given client and file inclusion or exclusions are being used. The first backup staged applied these correctly but subsequent ones did not resulting in message Status=Failed Error-Code=10002
1.2.0
33 Corrected bug during the -select process where it would hang if Fld-8 in the client configuration file specified multiple file exclusions with spaces in file names
1.2.0
32 Corrected bug during staging of selected folders only using avtar mode. Only first level folders were being staged as opposed to including their underlying files.
1.1.9
31 Improved and expanded on ATO health check and administration tools grab and backup
1.1.8
30 Corrected incorrect description text displayed when creating a batch profile 1.1.8
29 Corrected behavior of a batch job in a scenario where some staging items succeeded while others did not and the tape backup was successful. The batch completion status in this case resulted in a success status but will now register this as failure.
1.1.7
28 Corrected bug related with using client sub groups within a batch profile. When creating a batch profile and you intended to use sub groups the prompt for the base-name required a complete name to already exist preventing you from completing the configuration interactively.
1.1.7
27 Modified ATO grab function to use a more granular and unique zip file name when more than one grab is run per day. It is now based on date and time down to the second.
1.1.5
26 Modified the –data and –xdata filters to provide more consistent behavior regardless of whether a mccli or avtar based recovery session is being used. This change also applies to client configuration file Fld-8 and Fld-17 which are used for this purpose as well. Added a check to detect when these two fields are both defined for a given client entry as this will result in undefined behavior. See limitation section below Ref#-4.
1.1.5
25 When running a long ATO tape backup session or when using the –avtar switch during a –tapeout session which is the default for non FS backups, there was a potential for a timeout to occur with the following error message “avtar Info <7023>: Timeout on
script run-at-end” resulting in a failed ATO session. This timeout by default is 1 Hr and has been increased to a default of 10 Hr’s. The addition of variable SCRIPT_TIMEOUT=<#secs> to the environment file allows you to set the timeout value to use.
1.1.5
24 removed the E option from Batch Manager monitor mode menu which was inadvertently added at version 1.1.1
1.1.4
23 corrected bug when using -avtar switch during a –tapeout action for non-standard FS plugins where -data and -xdata filters were not being recognized
1.1.3
22 corrected bug with –tapeout which manifests itself during the month of January displaying error message ERROR-10A requesting you add the –sdate option to expand the search range date
1.1.3
ATO Release Notes
Page - 15
21 corrected bug with using Fld-16 in client configuration file where the user defined path
suffix if specified was not being inserted properly 1.1.2
20 corrected bugs with user input syntax checks related when using –data and –xdata switches to either include or exclude folders from the staging process
1.1.2
19 Corrected behavior of the timers TIMEDELAYSTAGE and TIMEDELAYTAPE in the environment file to permit much longer values being specified without it imposing a delay on the completion time of a given activity. This reduces the quantity of progress messages logged considerably especially in batch logs for long TO sessions.
1.1.1
18 corrected several bugs with batch status reporting 1.1.1
17 corrected several behavioral issues in Batch Manager related with question prompts and no input was specified
1.0.9
16 Removed the need to specify the plug-in type during a -tapeout session of NDMP, Oracle, SharePoint or Lotus Notes
1.0.8
15 Confirmed -ndmp works with Celerra 1.0.8
14 Corrected bug with –week filter resulting in a hang when used during the month of December
1.0.8
13 Corrected bug with auto generated tape script when using Unix/Linux staging servers for server initiated tape backup controlled by Fld-14 of client configuration file
1.0.7
12 added additional event information when using ATO as a wrapper around Avamar Perl scripts to provide more detailed tape error information in the case of a failure
1.0.7
11 Corrected problem with a batch profile which uses sub-groups where the generated batch script would lose its ability to determine the active status after the first sub group completed
1.0.6
10 Improved user interface used to create a new batch profile providing ability to accept, reject or modify a newly created profile and added help text to the various prompts.
1.0.6
9 Added the –avtar option to –tapeout action used when staging Lotus Notes, Oracle, NDMP or SharePoint backups. Refer to help text for restrictions when using these plug-in types
1.0.6
8 Added –but option as an alternative to using –butype during the selection process 1.0.6
7 Added technical support contact info 1.0.6
6 Provided support for running and managing ATO from a Red Hat client requires Avamar 4.1 or higher
1.0.6
5 Added support for FreeBSD staging server and client 1.0.6
4 Corrected bug with the selection process where no backups were being selected on the first day of the month or missed a backup from the last day of the month
1.0.5
3 Improved environment file layout by adding comments and grouping variables into related sections. Will only pertain to new files created, existing files would need to be manually edited to benefit from this
1.0.5
2 Corrected problem with the batch manger when a long profile name >26 characters existed which by design was truncated to fit the display width. The truncated value was being referenced when adding it to the CRON or when viewing its related log file. New behavior verifies if the truncated name is in fact complete, if not it will then detect and use the correct full file name. If more than one profile name matches the first 26 characters then all matching names are displayed and the user must choose the desired one.
1.0.4
1 Corrected bug where the recovery manager was establishing a checkpoint containing the last staged backup even when the staging activity completed successfully
1.0.3
ATO Release Notes
Page - 16
Known Issues and Limitations The following table documents known issues and/or limitations and temporary workarounds if available. The status field value determines the current status of the limitation where Current=Currently-Applicable, Closed=No-Longer-Applicable
Ref# Limitations or Behavioral Considerations Status
1 When staging non standard FS Plug-In’s including NDMP, Oracle and Lotus Notes the progress messages will display as n/a. This is due to these Plug-in types relying on avtar being initiated remotely. Recovery sessions are registered in the Activity Monitor but report only the final completion status.
Current
2 When performing TO of NDMP data original file permissions are not guaranteed and may vary based on the type of the original source file share involved CIFS or NFS and their compatibility with the staging server type being used.
Current
3 With non standard FS Plug-IN’s including NDMP, Oracle, Exchange Message level or Lotus Notes it’s the user’s responsibility to determine whether recovered data is in a usable format. Lotus Notes and NDMP have been confirmed to be usable and Oracle although not confirmed is recovered in a format which should be able to be imported to an RMAN catalog using the “catalog” command after which a normal RMAN recovery should be possible. The Oracle backup would also have to be performed initially using an RMAN catalog.
Current
4 When using Fld-8 and 17 in the client configuration file to include or exclude specified folders, ensure only one field is defined for a given client. Behavior is considered undefined if both fields are used together and recovery results may not be as expected. When using the command line –data and –xdata are mutually exclusive and fields in the client configuration file are ignored.
Current
5 When running ATO version 1.1.5 the –upgrade function will not work correctly. In this case you will need to run tar Pxf ato-1-1-6.tar to perform an upgrade to 1.1.6
Resolved
1.1.6
6 –vmimage client names displayed in Configuration Manager or a View display may be truncated if their names exceed the available display width. The correct name will be used if referenced.
Current
7 For –vmimage clients it’s recommended not to establish host names containing spaces or special characters as these will impact ATO’s ability to handle them correctly.
Current
8 For –vmimage clients their full name discovery is dependent on the availability of the axionfs service being active. If it’s not, you can edit the client name entries in the client configuration file manually if you know what they are.
Current
9 Three options are provided to filter Exchange BU’s, –exch includes both database and message level BU’s and is provided for past compatibility only, -exchdb limits selection to the storage group only and –exchmsg limits selection to message level BU’s. Message level BU’s have not been proven with ATO therefore these switches are primarily to exclude message level BU’s from the selection process. If message level staging is proven to function satisfactorily this restriction will be removed.
Current
10 When administering ATO from a RH client as opposed to the norm on the Utility Node, ATO’s enhanced security and the maintenance task verification are not supported.
Current
11 Removed SharePoint plug-in –shpt support as it does not work 2.0.0d
12 When using the –ndmp plug-in the displayed backup size is not as expected. The value shown is supplied by avtar but suspected to represent the ndmp incremental size rather than the original full backup size.
Current
ATO Release Notes
Page - 17
Ref# Limitations or Behavioral Considerations Status
13 In some situations when staging to a Windows server some files usually under windows or program files directory may not delete afterwards and special privileges or procedures may be needed to remove them. This is especially prevalent with Vista and later Windows OS versions including W2K8 which incorporate enhanced security. Files in these folders have limited value on tape as they belong to the OS or software application and could not be used in a system recovery scenario. OS and application software files would need to be reinstalled from their original media or other bare metal approach. Some suggestions on how to possibly overcome this condition are as follows; - Exclude the problem folders from the TO process using Fld-8 in client cfg file or
with the –xdata switch on command line - Ensure the Avamar service is started with an account that has sufficient
administration privileges perhaps including domain privilege as opposed to using the default local account
- Invoke your own script using the –upst script call from ATO or execute it outside the ATO process to delete the problem files.
- Invoke your own script using –upst script call from ATO or execute it outside the ATO process to reformat the staging disk involved
- Perform incremental staging rather than non-incremental as no delete is used. Incremental could be limited to the problem folders only if necessary to conserve staging disk capacity
- Use a non Windows staging server with the understanding Windows specific ACL’s will be lost
Current
14 ATO does not currently support tape out of backups performed using Exchange VSS or Windows VSS plug-in. Selection options have been added allowing for these to be selected and viewed –exchvss and –vss but you cannot perform a TO of these backups. These filters also prevent these BU types from being included within the normal Exchange or Windows FS backup selections. This restriction also pertains to SharePoint –shpt backups.
2.1.2
15 When configuring ATO email alerts if the destination address string contains more than one address the first address specified must be entered twice and the complete string must be quoted. When a single email address is defined it must not be in a quoted string. The supported mail program must be set to /bin/mail
2.1.2