|
ISSUE: [MigrateV6Index.migrateIndex] Failed to migrate v6 index (MS Exchange DAG server backup set upgraded from version 6 to 7)
|
|
1
|
1618
|
24 September 2020
|
|
ISSUE: Incorrect error message 'Another backup job is still running' is displayed (MS Exchange server backup)
|
|
0
|
1564
|
23 February 2018
|
|
ISSUE: Invalid backup source displayed for Exchange 2007 server backup set upgraded from version 6 to 7
|
|
0
|
1484
|
23 February 2018
|
|
ISSUE: MS Exchange DAG server scheduled / continuous backup jobs are not running (Run scheduled backup on computers named setting is incorrect)
|
|
0
|
1486
|
23 February 2018
|
|
ISSUE: MS Exchange server backup job cannot run to completion (for backup set with backup schedule disabled)
|
|
0
|
1466
|
23 February 2018
|
|
ISSUE: Incorrect error message 'Another backup job is still running' is displayed (IBM Lotus Domino / Notes backup)
|
|
0
|
1501
|
23 February 2018
|
|
ISSUE: IBM Lotus Domino / Notes backup job cannot run to completion (for backup set with backup schedule disabled)
|
|
0
|
1507
|
23 February 2018
|
|
ISSUE:"ORA-01078: failure in processing system parameters" error when restoring an Oracle 12c database to an Alternate location on a Windows server
|
|
0
|
1660
|
23 February 2018
|
|
FAQ: How to configure an Oracle database server backup set?
|
|
0
|
1495
|
23 February 2018
|
|
ISSUE: 'JavaSysPriv role not granted. Please execute Grant JavaSysPriv to System' error when creating an Oracle 12c backup set
|
|
0
|
1773
|
23 February 2018
|
|
ISSUE: Incorrect error message 'Another backup job is still running' is displayed (Oracle database backup)
|
|
0
|
1501
|
23 February 2018
|
|
ISSUE: Oracle database backup job cannot run to completion (for backup set with backup schedule disabled)
|
|
0
|
1524
|
23 February 2018
|
|
ISSUE: "No database file found for "%DB_Name%" error on MSSQL Server backups
|
|
0
|
1528
|
23 February 2018
|
|
ISSUE: Incorrect error message 'Another backup job is still running' is displayed (MS SQL database backup)
|
|
0
|
1478
|
23 February 2018
|
|
ISSUE: MS SQL database backup job cannot run to completion (for backup set with backup schedule disabled)
|
|
0
|
1466
|
23 February 2018
|
|
ISSUE: MSSQL Server database backup fails with "Cannot start shadow copy, reason =null" error
|
|
0
|
1558
|
23 February 2018
|
|
ISSUE: MSSQL Server databases are not shown in AhsayOBM backup source if the hostname of the database server is longer than 15 characters
|
|
0
|
1452
|
23 February 2018
|
|
ISSUE: No database file found (MS SQL database backup) for database file name with extension in upper case
|
|
0
|
1499
|
23 February 2018
|
|
ISSUE: No database file found (MS SQL database backup) for database file name with unicode
|
|
0
|
1494
|
23 February 2018
|
|
FAQ: How to create a MS Exchange mail level backup set with AhsayOBM (MS Exchange 2007 / 2010)?
|
|
0
|
1475
|
23 February 2018
|
|
FAQ: How to create a MS Exchange mail level backup set with AhsayOBM (MS Exchange 2013)?
|
|
0
|
1401
|
23 February 2018
|
|
ISSUE: Duplicate databases are displayed under empty DAG group when creating a MS Exchange mail level backup set (MS Exchange mail level backup)
|
|
0
|
1471
|
23 February 2018
|
|
ISSUE: Incorrect error message 'Another backup job is still running' is displayed (MS Exchange mail level backup)
|
|
0
|
1453
|
23 February 2018
|
|
ISSUE: Index migration is performed by every backup jobs (MS Exchange DAG mail level backup set upgraded from version 6 to 7)
|
|
0
|
1411
|
23 February 2018
|
|
ISSUE: MS Exchange mail level backup job cannot run to completion (for backup set with backup schedule disabled)
|
|
0
|
1392
|
23 February 2018
|
|
ISSUE: [MigrateV6Index.migrateMultiHostIndices] Failed to deserialize v6 index (MS Exchange DAG mail level backup set upgraded from version 6 to 7)
|
|
1
|
1425
|
24 September 2020
|
|
ISSUE: Unable to do backup (Failed to download v6 index) when performing backup after upgrading AhsayCBS to 7.5.0.0 or above
|
|
0
|
1496
|
23 February 2018
|
|
ISSUE: When performing a backup job on AhsayOBM/AhsayACB the following error is shown [ChunkedOutputStream.FlushData.execute Failed to flush buffer to this destination Error=com.ahsay.afc.cloud.d Failed to get OutputStream of file"
|
|
0
|
2016
|
23 February 2018
|
|
ISSUE: xhost command not found error when running the RunConfigurator.sh script file
|
|
0
|
1787
|
23 February 2018
|
|
ISSUE: “CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory.” when running a Windows batch file as a pre or post backup command from a network drive
|
|
0
|
2406
|
23 February 2018
|
