You want to create an automated test environment that performs a single file SnapRestore time you run the procedure, however, SnapRestore prompts you to confirm your decision to revert the file. How can you automate this step?
Five minutes ago, you performed a single file SnapRestore on a large NFS file. 40% of your NFS users are now complaining about getting "stale file handles" for the file. Which is the most likely cause of this problem, and the best procedure to correct it?
Using the output below, a co-worker determined that these are types Solaris LUNs. What would your destination be?
lun show – m LUN patch mapped to LUN ID -------------------------------------------------------
/vol/vol1/lun0 solaris – igroup0 0 /vol/vol1/lun solaris- igroup1
0 /vol/vol1/qtree1/lun2 solaris – igroup2 0 /vol/vol1/qtree1/lun3 solaris – igroup3 0
In a tape environment after a SnapRestore reversion of a volume, incremental backup and restore operations on the file or volume cannot rely on the timestamps to determine what data needs to be backed up or restored. Which course of action ensures correct incremental backups?