When does a non-full backup automatically get converted to a full backup?
A non-full backup is automatically converted to a full backup in the following situations:
-
First backup of the subclient.
-
Promote a secondary storage policy copy that is not synchronized with a primary copy (for all the subclients of a storage policy).
-
If you switch from a IntelliSnap backup to a traditional backup or vice versa.
-
CommCell Migration operation.
How long is the backup data retained?
Each subclient is associated to a storage policy. How long the backup data will be retained on the backup media is determined by the retention rules set in the Storage Policy Copy Properties dialog box. This will affect media usage, and is an important consideration when planning your backups. A longer retention period, for example, could use more media for securing the data over time.
If a retention period other than infinite is selected, the data will be pruned according to backup cycles in relation to the retention rules you set in the Storage Policy Copy Properties dialog box. Pruned data can be overwritten on the backup media.
The backup data from a subclient will be retained according to the rules set for the storage policy associated with it. The ability to define data in subclients, and then associate them to specific storage policies allows you to prioritize exactly what data is retained and for how long.
For example, a client is being backed up with the Windows File System iDataAgent using the default subclient (which backs up the entire file system). It is associated to a storage policy that regularly ages the data. There is a critical folder on that client that you would like retained longer than the rest of the file system. You could create a new subclient with that critical folder as its content, and associate the new subclient with a storage policy that has the desired retention period.
When a user changes the storage policy association of a subclient, a subclient is deleted, or a client or an agent is deleted, only the retention days must be exceeded for data to be aged. In these cases, retention cycles are set to zero (0). However, when a client or an agent is deconfigured, the associated data will be aged according to the associated storage policy copy’s defined retention time and cycle rules. In this case, retention cycles are honored. If necessary, you can enable the Ignore Cycles Retention on De-Configured Clients option from the Control Panel | Media Management Configuration (Service Configuration) dialog box so that the defined retention cycle rules are ignored for the data associated with deconfigured clients.
See Data Aging for detailed information and advanced concepts on Data Aging and retention.
What permissions does the restored data acquire after the restores?
When performing restore operations (other than in-place restores), the restored data assumes the rights (i.e., permissions) of the parent directory.
How to run parallel backups using subclients?
You can back up an entire instance more quickly by scheduling multiple subclients for simultaneous backup. This way, the backups proceed in parallel and take less time than if the instance were not divided into separate subclients.
Note, however, that in order for the subclient backups to run in parallel, they must be configured to use different storage policies or a storage policy that is configured to have at least as many data streams as the total required for all subclients you want to back up in parallel. If any of the subclients are configured to use the same storage policy, and if that storage policy is not configured for enough data streams, then a media group resource contention will arise, and the competing subclients will back up one after the other in a serial manner. For more information see Storage Policies and Media Groups.
What are the folders or files created and changes done during installation of this agent?
|
Platforms |
Folders Created |
Files Created |
Other changes |
|---|---|---|---|
|
Mac |
/etc/CommVaultRegistry/Galaxy/InstanceXXX /opt/commvault /var/log/.gxsetup /var/log/commvault /Applications/Process Manager.app /Library/StartupItems/Galaxy .gxupdate
|
/usr/local/bin/commvault /usr/local/bin/cvpkgrm /usr/local/bin/cvpkgchg /usr/local/bin/cvpkgcheck /usr/local/bin/detect /usr/local/bin/laptop2startup.$GALAXY_INST.command, where GALAXY_INST = Instance001, Instance002, ... |
For Process Manager.app, symbolic link to: /opt/commvault/Base/Process Manager.app Startup Scripts: /Library/StartupItems/Galaxy/StartupParameters.plist (Mac OS X v10.7.x and Mac OS X v10.8.x only) /Library/StartupItems/Galaxy/Galaxy (Mac OS X v10.7.x and Mac OS X v10.8.x only) /Library/LaunchDaemons/com.commvault.galaxy.plist |
Why do I see a ._filename file when I browse from a backup run on a UNIX client containing NFS volume shared to Mac clients?
The ._filename file is an Apple Double format file created by Mac OS X to store file metadata and other information. This file is created when a Mac OS X file is saved or copied to a non-HFS file system, such as NFS.
When you select the Enable Apple Double Support option, the subclient backs up the file and the associated Apple Double format file as a single file. Such a file can be restored directly to HFS or HFS Plus file system or to the NFS volume itself. Without the option selected, each file and the associated Apple Double format file are backed up as separate files, and they will be restored to any file system as such.