The Question is: How Do You Restore Data to the Aggregator? The Documentation states two different methods and Technical Support states a third; none of the three methods work.
Below is what I have tried. All of the Data for November 2012 exists on a external FTP server that shares the shared secret.
1. Central Management--Data Management--Data Restore--Data Restore Criteria
From 2012-11-01 00:00:00
To 2012-11-30 23:59:00
Host Name <Blank>
Result: 7 files are listed each of which is a different date in November, even though all 30 days archived files exist
Data Restore Search Results
Don't purge restored data for at least (days)
Select Host Name From Date
xxxxxxxxxxx01b 2012-11-03 00:00:00.0
xxxxxxxxxxx01b 2012-11-04 00:00:00.0
xxxxxxxxxxx01b 2012-11-17 00:00:00.0
xxxxxxxxxxx01b 2012-11-18 00:00:00.0
xxxxxxxxxxx01b 2012-11-22 00:00:00.0
xxxxxxxxxxx01b 2012-11-23 00:00:00.0
xxxxxxxxxxx01b 2012-11-25 00:00:00.0
2. Using the following instructions from Technical Support:
1. Only on a collector, Run "stop inspection-core" to stop the sniffer.
2. GUI - choose Administration Console -> Data Management -> Catalog Archive, put the date range requested in the GUI and IP address of a server the data is located at, and click "Add"
3. Add the "EMC Centera" info and click "Save" ( if you have several files, just put name of one of the files in the file name box, it will still point to the right location)
4. GUI - choose "Catalog Archive" again, then click "Search". It should show you the file(s), check mark them and click "Done".
5. GUI - choose "Data Restore". You should see the file(s) under this section. Check mark the file(s) interested and click "Restore".
Data Management--Catalog Archive--Catalog Archive Search Criteria
From 2012-11-01 00:00:00
To 2012-11-30 23:59:00
Host Name <Blank>, click Search,
Select All (66 files 2 each for each day of month as well as backed-up CONFIG and DATA.tgz files and those files were not selected),
Entry Type Results Archive
Process Description Nov 2012 Restore
File Name <this is where the error occurs>
Host Name IP of FTP server that the Archived Files are On
Path /<directory name>
Storage System FTP
The problem is with what to put as the FILE NAME. Since I want to Restore 30 days of data, I assumed you can truncate the file name of the archived file. For example
735173-xxxxxxxxxxx01b.com-w20121102.051941-d?2-11-01.agg.82.tar.gz.enc is truncated as 735*-xxxxxxxxxxx01b.com-w2012*.agg.82.tar.gz.enc
That does not work nor does putting the full file name; the error is Wrong file name format for archived result: -<myHostname>-d<res_process_id>_<run_no>_<execution_date>.res.<sql-ver>.tar.gz
3. From the Guardiumv82_Aggregation_Central_Management pages 11-12
As described previously, archives are written to an SCP or FTP host, or to a Centera or TSM storage system (see Archiving Data, above). To restore archives, you must copy the appropriate file(s) back to the Guardium unit on which the data is to be restored. There is a separate file for each day of data. Depending on how your archive/purge operation is configured, you may have multiple copies of data archived for the same day. Archive and export data file names have the same format: <daysequence>-<hostname.domain>-w<run_datestamp>-d<data_date>.dbdump/TAR file. For example: 732423-g1.guardium.com-w20050425.040042-d2009-04-22.dbdump/TAR file.
Unless you are restoring data from the first archive created during the month, you will need to restore multiple days of data. That is because when restoring data, Guardium needs to have all of the information that it had when the data being restored was archived. After the archive was created, some of that information may have been purged due to a lack of use. All information needed for a restore operation is archived automatically, the first time that data is archived each month. So, when restoring data, you have two options:
Restore the first day of the month and all the following days until the desired day or
Restore the desired day and then the first day of the following month
For example, to restore June 28th, either restore June 1st through June 28th, or restore June 28th and July 1st.
To restore archives:
1. From the CLI, use a separate import file command to copy each archived data file to be restored to the Guardium unit. The archive and restore operations depend on the file names generated during the archiving process. DO NOT change the names of archived files. If a generated file name is changed, the restore operation will not work.
xxxxxxxxxxx01b.com> import file
Please enter the number of your choice: (q to quit) 2
Enter the backup host: <FTP IP>
Enter the backup host username:
Enter the remote directory:
Enter the remote file name (file name may use wildcard ): 735173-xxxxxxxx.xxxx.com-w.enc
Enter the password for backup host username@backup host IP ? ********
Enter the FTP port if you need to use a special port.
Enter "0" or press "Enter key" to use the default port:
Attempting to retrieve file. It may take time. Please wait.
During the transfer, please do not enter the password or answer any questions.
Connected to <FTP IP>
Login successful as user envision
Proceeding to download our file, this might take a few minutes...
However, neither of these files are listed under Data Restore
Thanks in Advance
This topic has been locked.
1 reply Latest Post - 2013-03-28T15:50:15Z by ol1
Pinned topic Confusing Documentation about How to Restore Data to a 8.2 Aggregator?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-28T15:50:15Z at 2013-03-28T15:50:15Z by ol1
ol1 2700054BRF4 PostsACCEPTED ANSWER
Re: Confusing Documentation about How to Restore Data to a 8.2 Aggregator?2013-03-28T15:50:15Z in response to SystemAdminHello Magda,
the reason you do not see imported files in the drop down list might be in fact that these days were previously imported/restored.
You can check your Aggregation/Archive Log for messages or to run some report with dates range of Nov 01 (for your case) and check if data already exists in DB.