Before you perform a CA ARCserve D2D backup, review the following backup considerations:
If your destination does not have sufficient free space, you can consider the following corrective actions:
A volume is skipped from a backup if it is on a disk larger than 2 TB and the compression option is disabled. However, there is no size limitation if compression is enabled (which is the default setting). As a result, if you want to back up source volumes larger than 2 TB, you must keep the compression option enabled.
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.
If your scheduled backups are occurring more frequently than the amount of time it takes to generate a file system catalog for previous backup jobs, your recovery point retention count may be exceeded before the file system catalog being generated for the oldest session is completed. If this happens there may be no catalog generated for the backup sessions. To avoid this problem, you can either increase the schedule interval time for your incremental backups or increase the retention count.
Manual operations (such as copy, cut, paste, or drag-and-drop) for the backup destination folder are not successful if a job is active or a user is browsing recovery points using the ARCserve D2D View. Verify that no active jobs are running or browsing of recovery points (using ARCserve D2D View) is being performed before attempting any of these manual operations.
Verify that you have latest drivers/firmware installed for all the devices.
Even when backup jobs are not running, CA ARCserve D2D is constantly monitoring changes that are related to the operating system and data. Any detected changes are then compiled and saved in a list to include as an Incremental Backup after the next machine start-up. If your machine was not properly shut down and all of the changed information was not saved, CA ARCserve D2D may perform a more lengthy Verify Backup for the next backup, even if a Verify Backup was not scheduled.
When the CA ARCserve D2D backup job runs on a Hyper-V server, the status of the VMs is "Backing up" and the following tasks cannot be performed:
When you enter a backup path, CA ARCserve D2D appends the host name to that path to use as the destination and this host name is also displayed in the settings dialog. When the name of the machine is changed, you must also change the destination path (backup, file copy, copy recovery point) by removing the old host name from the path before you attempt to save the settings.
For example: If your host name is "Host_A" and your backup destination is X:\ and you change your host name to "Host_B", any changes that are made to your backup settings are not saved unless you first change the backup destination from x:\Host_A to x:\ again.
If you do not change the backup destination host name and attempt to save the settings, CA ARCserve D2D thinks the backup destination "x:\Host_A" is already in use by Host_A and that Host_A is another machine and does not accept any changes to the settings.
When you continue performing Incremental Backups to the changed destination and the specified number of saved recovery points is reached, CA ARCserve D2D merges the earliest backup sessions to the first destination to maintain the specified number of recovery points. As this merging process repeats, the number of recovery points that are saved to the first destination decreases, and at the same time the number of recovery points for the changed destination increases. Eventually, there are no recovery points for the first destination and all of the sessions are merged to the changed destination.
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 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 fail because the link to the first location has been lost.
For example:
Previously the CA ARCserve D2D merge process took a long time to complete and while the merge job was running, you could not submit any other jobs. The merge happened inside the backup job (at the end) and in a catalog job (in the beginning).
For example, if each incremental backup generates about 100 GB of data. Merging the 100 GB of data to the full session takes more than 15 hours to complete and during this time nothing can be done.
CA ARCserve D2D now allows the merge job to merge multiple sessions at the same time. In addition, the merge job can be started/stopped and paused/resumed on demand and does not affect any other jobs. This merge process avoids multiple reads and writes because it only merges the latest change for each block. The merge process ignores all the changes that have occurred to the same block during any intermediate incremental backups. Merging multiple sessions at the same time is faster than merging them individually.
Slow merge performance is generally caused by the following reasons:
To resolve this slow merge issue, consider retaining Recovery Sets instead of Recovery Points. You can configure how many recovery sets to retain, starting with a full backup, and when the number of recovery sets exceeds the user-specified one, the oldest recovery set will be deleted, instead of merged. For more information, see Merge Job Guidelines and Specify Retention Settings.
Volume defragmentation by Windows native tool affects the size of the block-level backups because CA ARCserve D2D will continue to incrementally back up all changed blocks. This means that blocks that shifted during defragmentation will also be included in the backup, even if no data has changed in the files. As a result, the backup size may increase. This is expected behavior. If you do not want the increased backup size and the added backup time is a problem, you can exclude volumes from defragmentation or stop any schedules for defragmentation.
If you are backing up volumes that were replicated using CA ARCserve Replication and High Availability, you should verify that the spool has been created on a separate volume and configure your backup settings to exclude the spool volume. This helps to avoid the backing up of unnecessary temp spool data.
Due to Microsoft SQL Server VSS writer restrictions, some Microsoft SQL Server databases with a special status are automatically skipped and not backed up. These databases include:
CA ARCserve D2D uses all the VSS writers during backup to ensure consistent backups. The only exceptions are Microsoft SQL Server, Microsoft Exchange, and Hyper-V writers which are only included when they are properly licensed.
If both compression and encryption are disabled, then CA ARCserve D2D can only back up the files in .VHD format. CA ARCserve D2D cannot back up the files in .VHDX format.
|
Copyright © 2012 CA.
All rights reserved.
|
|