HP 3PAR Recovery Manager 4.5.0 for Oracle on Solaris, Red Hat Linux, and Oracle Enterprise Linux User's Guide (QL226-97705, May 2014)

NOTE: If the database volumes do not belong to any domain, then the retention time of the
read-only Virtual Copy cannot exceed the VVRetentionTimeMax value of the system. The
VVRetentionTimeMax default value for the system is 14 days. If the database volumes
belong to a domain, then the retention time of the read-only Virtual Copy cannot exceed the
VVRetentionTimeMax value of the domain, if set. The retention time cannot be removed
or reduced once it is set. The retention time can be extended by rmora_set command. The
VVRetentionTimeMax value can be checked via HP 3PAR OS Software CLI commands
showsys -param and showdomain -d.
• Enter Virtual Copy expiration time in days(d|D) or hours(h|H)
[h=help,s=skip,q=quit]? (default=0d) h
There are two ways to maintain the Virtual Copies in the HP 3PAR StoreServ Storage system:
◦ Time-based policy: Enter an expiration time. When Virtual Copies expire, they are
automatically removed from the system.
To enter an expiration time, enter the amount of time, relative to the current time, that all
future Virtual Copies will expire. Valid expiration times range is between 1 to 43,800
hours (1825 days). You can specify the value in days or hours by adding either 'd' or
'D' for day, or 'h' or 'H' for hours after the amount of time. The default value, '0d', means
the Virtual Copy has no expiration time.
◦ Count-based or numeric-based policy: Either skip this question or use the default value
'0' for the expiration date. You will be prompted for the maximum Virtual Copies you
want the system to keep.
NOTE: The numeric-based policy is deprecated and will be removed in a future release.
• Enter maximum number of Virtual Copies allowed [h=help,q=quit]?
You will be prompted with this question if you did not set an expiration for a Virtual Copy in
the previous question. Enter the maximum number of Virtual Copies that can be created for
the specified database. Once the maximum number of Virtual Copies for the database is
reached, Recovery Manager for Oracle removes the oldest Virtual Copy before creating a
new one.
The default maximum number is 500 read-only Virtual Copies for each volume.
• Do you want to remove oldest Virtual Copy when the maximum number
of Virtual Copy is reached [y=yes,n=no,q=quit]?
You will be prompted with this question if you set the maximum number of Virtual Copies in
the previous question. Enter n if you do not want to remove the oldest Virtual Copy when
maximum number of Virtual Copy is reached. Otherwise, enter y.
• Select third-party backup tool
[0=NONE,1=RMAN,2=RMAN_NBU,3=RMAN_DP,h=help,q=quit]?
Recovery Manager for Oracle support Symantec NetBackup, Oracle RMAN with and without
Symantec NetBackup or HP Data Protector.
NOTE: Symantec Netbackup backup method is not supported and does not appear for an
ASM managed database.
Enter 0 if you do not want to perform backup.
If you enter 0, stop here. No further information is required. If you enter 1, 2, 3 ,or 4; you
may be prompted for the following information:
Recovery Manager for Oracle Configuration Files 61