Beginning with Virtuozzo Containers for Windows 4.5 and VZU400018 update of Virtuozzo Containers for Windows 4.0, you can use third-party backup solutions like Symantec Backup Exec inside Containers to perform file-level/mailbox-level backups/restores.
Using such backup solutions is restricted to additional drives inside containers only. In other words, it is impossible to back up and restore the C: drive inside a Container, due to the fact that by default, all shadow copies of D: (or E: or any other letter) drives are created on drive C.
Thus, if you would like to backup the Exchange server mailboxes, for example, the Exchange server database should be installed on this additional drive D: (E:, etc). When creating a container for such a configuration, it is necessary to enable SCSI and VSS on the container level:
vzctl set _CTID_ --vss yes vzctl set _CTID_ --scsi yes
Do not forget to create a partition on a loopback file, which will act as an additional drive:
vzctl partadd _CTID_ --drive D: --size 20000000 --file D:\vz\private\_CTID_\D-DRIVE.efd --scsi
NOTE: It is possible to perform the above actions only via command-line. Parallels Management Console or Parallels Virtual Automation do not allow to set these options.
As a necessary step before using similar backup solutions, you need also to change the VSS snapshots storage area from disk C: to another disk inside the Container with the following command:
vssadmin add shadowstorage /for=D: /on=D:
/for=D: an option pointing to where files that are going to be backed up are located,
/on=D: an option pointing where Shadow Copy Storage is located.
It is allowed to change the D: drive to another drive of the Container in the command above as long as it is not the C: drive.
When creating a new backup job with Symantec Backup Exec for backing up and restoring Microsoft Exchange, make sure that the Use GRT (Granular Recovery Technology) option in Microsoft Exchange Settings is not selected.
Sometimes Symantec Backup Exec produces the following error:
1213 The database page size does not match the engine
Symantec confirms this problem and provides the hotfixes in this article.
Sometimes new SCSI volumes are created with read-only attributes, so VSS does not work properly. In such cases, adding new shadow storage will result in the following error:
Error: shadow copying on specified volume is not supported.
In such case, clear the read-only attribute manually via command line:
vzctl enter _CTID_ diskpart select disk 0 online disk attributes disk clear readonly select volume 0 attributes volume set shadowcopy
NOTE: Use real disk and volume IDs instead of 0.