Unlike file-based backup (copying documents), True Image 9.1 created a sector-accurate image of a partition or entire hard drive. This included boot sectors, hidden system files, and deleted file remnants. The output was a proprietary .TIB (True Image Backup) file, which could be compressed (normal or high) or split into chunks (e.g., 650MB for CD burning).
| Limitation | Description | |------------|-------------| | | Relied on its own snapshot driver, which could occasionally miss open/locked files in complex databases. | | Large HDD Support | Officially supported up to 2TB, but many users reported issues with 4K sector drives (Advanced Format). | | Network Performance | Backup to SMB shares was slow (≈5-10 MB/s on 100Mbit LAN) due to non-optimized protocol handling. | | Encryption | Password protection was available, but only weak AES-128 (no AES-256). | | No Cloud Support | Cloud backups were not commercially available at the time. |
Unlike file-based backup (copying documents), True Image 9.1 created a sector-accurate image of a partition or entire hard drive. This included boot sectors, hidden system files, and deleted file remnants. The output was a proprietary .TIB (True Image Backup) file, which could be compressed (normal or high) or split into chunks (e.g., 650MB for CD burning).
| Limitation | Description | |------------|-------------| | | Relied on its own snapshot driver, which could occasionally miss open/locked files in complex databases. | | Large HDD Support | Officially supported up to 2TB, but many users reported issues with 4K sector drives (Advanced Format). | | Network Performance | Backup to SMB shares was slow (≈5-10 MB/s on 100Mbit LAN) due to non-optimized protocol handling. | | Encryption | Password protection was available, but only weak AES-128 (no AES-256). | | No Cloud Support | Cloud backups were not commercially available at the time. |
Strictly Necessary
Performance & Analytics
Functional
Marketing