- Notes, cautions, and warnings
- Preface
- Introduction
- Architecture
- Backup
- Restore and recovery
- Concurrent backups and restores
- Password-protected database backups and restores
- Database backup and restore verification
- Database consistency checks
- Preprocessing and postprocessing scripts
- Internationalization (I18N)
- Multi-streaming
- Multi-striping
- Client logs and caches
- Sybase ASE 15.7.x support
- Cumulative dump/load support
- Sybase ASE network password encryption
- Software processes
- Installation and Configuration
- Preparing to install the Avamar Plug-in for Sybase
- Installing, upgrading, and uninstalling the software on HP-UX
- Installing, upgrading, and uninstalling the software on IBM AIX
- Installing, upgrading, and uninstalling the software on Linux
- Installing upgrading, and uninstalling the software on Solaris
- Installing, upgrading, and uninstalling the software on Windows
- Performing post-installation tasks
- Backup
- Restore and Recovery
- Plug-in Options
- Command Line Interface
- Overview of CLI operations
- Command options
- Browse operations with the avsybase command
- On-demand backups with the avsybase command
- Cumulative backups with the avsybase command
- Restore and recovery with the avsybase command
- Troubleshooting
- Logging information
- Configuration checklist
- Determining the Sybase ASE server version
- Bitness of Avamar Plug-in for Sybase ASE and Sybase
- Requirements for libsybase_avamar.so and libsybase_avamar.dll
- Verifying the bitness of the library file
- Avamar client and Avamar Plug-in for Sybase ASE installation
- Avamar client and Avamar Plug-in for Sybase registration
- Disk space for the Avamar var directory
- Common problems and solutions
- Backup or restore failure with Sybase ASE 15.5
- "Cannot open file f_cache.dat" error
- Failure of list-times operation
- Hidden backups
- Failure of point-in-time recovery
- Failure of cumulative backups after enabling incremental dumps on the Sybase server
- Unable to browse databases with Avamar Administrator
- Restore with parallelism greater than one fails
- Using Sybase ASE release 16.0 Service Pack 2 with 32-bit backup servers
- active/active application cluster
- active/passive cluster
- Adaptive Server Enterprise (ASE) server
- administrator
- Avamar Administrator
- Avamar client
- Avamar Plug-in for Sybase
- Avamar server
- back up (verb)
- backup (noun)
- backup browsing
- backup cycle
- backup group
- backup level
- CLI backup
- CLI restore
- client
- client agent
- client registration
- cluster nodes
- Data Domain system
- database
- database administrator (DBA)
- dataset
- DD Boost
- disaster recovery
- DNS
- domain
- full backup
- granular restore
- group
- group policy
- GUI backup
- GUI restore
- high-availability system
- host
- incremental backup
- internationalization (I18N)
- level
- log backup
- MCS
- manual backup
- multiple session backup or restore
- multi-streaming
- on-demand backup
- online backup
- pathname
- physical host
- point-in-time restore
- plug-in
- policy
- recovery
- registration
- relocated restore
- restore
- restore browsing
- retention
- schedule
- scheduled backup
- shared storage
- Sybase plug-in
- Sybase server
- target database
- transaction log
- transaction log backup
- unscheduled backup
- virtual cluster client
Dell EMC Avamar for Sybase ASE 19.7 User Guide
Disk space for the Avamar var directory
The Avamar var directory must have sufficient disk space for log and other files. Backups and restores will fail if the var directory does not have enough space. Check the free space in the Avamar var directory by using the applicable method for the system.
The following example shows output from the df -h command on a Red Hat Linux system:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00 985G 310G 625G 34% /
A minimum of 100 MB of disk space is recommended for avsybase log files and other files.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\