- Destination available free space
If your destination does not have sufficient free space, you may consider the following corrective actions:
- Reduce the number of saved recovery points
- Increase the available free space at the backup destination
- Change the backup destination to a larger capacity
- Reduce the size of the backup source (maybe eliminate unnecessary volumes from the backup)
- Increase the Compression setting of the backup
- Ensure you have proper licensing
When using CA ARCserve D2D to perform backups (especially for SQL Server and Exchange Server), it is important to make sure you have the proper licenses.
- Backup disk size
A volume will be skipped from a backup if it is located on a disk larger than 2TB and an uncompressed backup format is used.
- Ensure you are using a supported disk
Different types of disks are supported as CA ARCserve D2D backup source disks and destination disks.
For more information, see Disks Supported by CA ARCserve D2D.
- How changing your backup destination can affect saved recovery points
When you continue performing Incremental backups to the changed destination and the specified number of saved recovery points is reached, CA ARCserve D2D will start merging the earliest backup sessions to the first destination in order to maintain that specified number of recovery points. As this merging process is repeated, the number of recovery points saved to the first destination will decrease, while at the same time the number of recovery points for the changed destination will increase. Eventually, there will be no recovery points for the first destination and all the sessions will be merged to the changed destination.
- How changing backup destinations can affect continued backups
If you configure and perform a Full Backup (and maybe some Incremental Backups) to a destination and then you decide to change your backups to a different destination, you can reconfigure your backup settings and continue performing Incremental Backups to the new destination without any problems.
If you later decide to change your backup destination again, you can simply reconfigure your backup settings again and continue performing Incremental Backups to the new destination without any problems.
For example:
- If you have a machine and it is configured to backup up to Folder A on your local/remote volume, and after you perform a Full Backup and some Incremental backups, your destination is getting full and you want to change to a different destination (Folder B). You can reconfigure the backup settings to the Folder B destination and CA ARCserve D2D will continue performing Incremental backups to that new destination. As a result, you will have your Full Backup and some Incremental Backups on the original Folder A destination, and you will have some Incremental Backups on the new Folder B destination.
- If after performing some Incremental Backups to Folder B, you decide to reconfigure to another new destination (Folder C), CA ARCserve D2D will continue performing Incremental Backups to the Folder C destination because the link to the original Full Backup location (Folder A) has been maintained.
If you configure and perform a Full Backup (and maybe some Incremental Backups) to a destination and then you decide to change your backups to a different destination, you can copy or move the contents from the original destination to the new destination, and then reconfigure your backup settings and continue performing Incremental Backups to the new destination without any problems.
However, if you have Full Backups in one location and Incremental Backups in a second location and then move the contents from the second location to a third location and attempt to continue performing Incremental Backups, then these backups will fail because the link to the first location has been lost.
For example:
- If you have a machine and it is configured to backup up to Folder A on your local/remote volume, and after you perform a Full Backup and some Incremental Backups, your destination is getting full and you want to change to a different destination (Folder B). You can move the contents of Folder A to Folder B and reconfigure the backup settings to the new Folder B destination. CA ARCserve D2D will continue performing Incremental Backups to that new Folder B destination. As a result, you will have your Full Backup and Incremental Backups all on the new Folder B destination.
- However, if your first destination is in Folder A (which now contains a Full Backup and some Incremental Backups) and you change the destination to Folder B using CA ARCserve D2D backup settings and continue to perform Incremental Backups, in this scenario, Folder B will now only contain Incremental Backups. Then, if you move the contents from Folder B to another new destination in Folder C (moving only the Incremental Backups from Folder B without a Full Backup included), in this scenario, if you continue to perform Incremental Backups to Folder C, these Incremental Backups will fail because the link to the original Full Backup location (Folder A) has been lost.
- Restrictions for a Microsoft SQL Server Backup
Due to Microsoft SQL Server VSS writer restrictions, some Microsoft SQL Server databases with a special status will automatically be skipped and not be backed up by CA ARCserve D2D. These databases include:
- Database with 'Restoring' status. This status indicates that the database may be the log shipping secondary database, the mirror database, or the database waiting for more backed-up data to be restored.
- Database with 'Offline' status. This status indicates that the database is not available for general use.
- If your database is configured in one volume and the logs are configured in another volume and you select only one volume to back up, the Microsoft SQL application backup will be skipped for that particular database.
- Any database in a dismounted state will be skipped from Microsoft Exchange application backup.
- Restrictions for a Microsoft Exchange Server Backup
- If your database is configured in one volume and the logs are configured in another volume and you select only one volume to back up, the Microsoft Exchange application backup will be skipped for that particular database.