When performing a restore I am unable to drill all the way down to the files I need. I get stopped at the folder level. Unable to restore files even from folders a couple levels up. Performed a tape scan and the files are definitely in the folder that I need restored. I merged the session with the same problem. When doing the restore I get error message AE3118...Failed to locate VOL1:\path\path\path. I DO have the correct path specified in the Source for the restore. I am using ARCSERVEIT 6.61 for NT on an NT4.0 platform. The server that was backed up and trying to restore to is Novell 4.11. Any ideas???
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Cannot see files under Session or Tree in Restore Window. 1
- Thread starter wamason
- Start date
-
1
- #2
look in c:\arcserve\temp, are there any *.cat files. If so your database has issues =:-] try running dbmgr.exe. As for AE3118, unselect the restore to original locations option and manually choose a restore directory on the netware server
- Thread starter
- #3
- Thread starter
- #5
Error Message: AE3118 Failed to locate VOL1\USERS\SHARED\CREAMS\GEORGE. This is the exacty error messgae. I tried to do TREE restore this morning and SEARCH for the files..no files found..Problem is SCAN found the the files...FILTER is LAST resort!!. Thanks for quick responses so far.
- Thread starter
- #6
are your normal backups merging properly, i.e can you see the files in the restore screen. Here is a list of things to check:<br>1. Run dbmgr.exe and repair and pack<br>2. Check the nwagent is the current and correct version<br>3. Make sure sp1 is applied to arcserve and nwagent<br>
Have you found a solution to this problem because it is the exact same problem that i'm having at the moment. I'm using the same systems aswell.
I dont have any *cat files in the temp directory and i have run a check and pack and repair just to be safe.
I dont know if it was happening for you but some directories are displaying subdirectories and files but others seem to be blank??????
Any help would be greatly appreciated.......
I dont have any *cat files in the temp directory and i have run a check and pack and repair just to be safe.
I dont know if it was happening for you but some directories are displaying subdirectories and files but others seem to be blank??????
Any help would be greatly appreciated.......
Don't know if this will help, but I've had mixed results using a tree restore. If its a full backup tape, put the tape in you want to restore from, find the session id of the tape under the second pulldown menu, Manager, Device, (highlight the tape--the summary tab-ID is the session ID. Then, drill down to the file using restore by session id, instead of by the tree. [sig][/sig]
Hi,
I've read this thread with great interest, but was hoping to pick your collective brains further. I've "inherited" Arcserve and I've noticed loads of *.CAT files in the \ArcserveIT\temp folder - 2.49Gb worth! Yup, I guess my database has issues and would say housekeeping wasn't top of the agenda before. Same old story, can run a merge OK, but cannot drill down the restore tree. Data is present on the tape as I can select the top level box (i.e. all data within the session) and restore it that way, which on some sessions can be as much as 65Gb - I only need a .PST file. Following advice, I've started a database repair and left it a number of hours, but it doesn't appear to do a great deal at all. I've noticed there is a tab option to initialise the database. I've saved my job scripts away and am considering this option as a last resort but first need to know:
a) how long (v. roughly) would a repair and pack take on 2.49Gb of *.CAT files - I don't know how often people perform maintenance......I've previously read "weekly".
b) am I heading in the right direction with the database initialise idea because repair and pack will take eons? What are the issues with this option?
c) I've downloaded Service Pack 2a and was wondering if it's best to init the database and then apply this or just ignore the init and just apply the S.P. right now.
d) If S.P.2a is applied, I need to apply to all target servers as well I guess (?), which also means rebooting each server, impacting system availability?
If S.P.2a doesn't need a reboot post install, then I'll be sorted and will deploy it everywhere!
If you know answers to parts or all, please let me know. If I'm barking up the wrong tree and being a lamer, also please let me know.
Sparkler.
I've read this thread with great interest, but was hoping to pick your collective brains further. I've "inherited" Arcserve and I've noticed loads of *.CAT files in the \ArcserveIT\temp folder - 2.49Gb worth! Yup, I guess my database has issues and would say housekeeping wasn't top of the agenda before. Same old story, can run a merge OK, but cannot drill down the restore tree. Data is present on the tape as I can select the top level box (i.e. all data within the session) and restore it that way, which on some sessions can be as much as 65Gb - I only need a .PST file. Following advice, I've started a database repair and left it a number of hours, but it doesn't appear to do a great deal at all. I've noticed there is a tab option to initialise the database. I've saved my job scripts away and am considering this option as a last resort but first need to know:
a) how long (v. roughly) would a repair and pack take on 2.49Gb of *.CAT files - I don't know how often people perform maintenance......I've previously read "weekly".
b) am I heading in the right direction with the database initialise idea because repair and pack will take eons? What are the issues with this option?
c) I've downloaded Service Pack 2a and was wondering if it's best to init the database and then apply this or just ignore the init and just apply the S.P. right now.
d) If S.P.2a is applied, I need to apply to all target servers as well I guess (?), which also means rebooting each server, impacting system availability?
If S.P.2a doesn't need a reboot post install, then I'll be sorted and will deploy it everywhere!
If you know answers to parts or all, please let me know. If I'm barking up the wrong tree and being a lamer, also please let me know.
Sparkler.
Hi Sparkler,
In answer to your questions,
a) Pack'n repair should take 5 hours on that size database but if the database is a RAIMA16 database [standard] then it should only reach 1.6gig anyway [16 million records times 10bytes per entry]. Its a good idea to run a pack every month and a check every 2 weeks [just to be sure]. If any of these finds an issue with the database then just repair and pack.
b) With the database you have its not a lost cause. Let the repair do its job and then initalize ONLY IF ALL ELSE FAILS.
c) You can apply sp2a at anytime without a problem but be careful with the VLDB [Very Large Database] update. I have found that a small very healthy database is the only way it works but if the upgrade works then it can reach 350gig [yes, thats right folks].
d) Yes apply the sp2a updates to all servers but only the backup agent updated machines need rebooting.
Hope this helps
In answer to your questions,
a) Pack'n repair should take 5 hours on that size database but if the database is a RAIMA16 database [standard] then it should only reach 1.6gig anyway [16 million records times 10bytes per entry]. Its a good idea to run a pack every month and a check every 2 weeks [just to be sure]. If any of these finds an issue with the database then just repair and pack.
b) With the database you have its not a lost cause. Let the repair do its job and then initalize ONLY IF ALL ELSE FAILS.
c) You can apply sp2a at anytime without a problem but be careful with the VLDB [Very Large Database] update. I have found that a small very healthy database is the only way it works but if the upgrade works then it can reach 350gig [yes, thats right folks].
d) Yes apply the sp2a updates to all servers but only the backup agent updated machines need rebooting.
Hope this helps
Guest_imported
New member
- Jan 1, 1970
- 0
I have two problems : 1) I have data sized 12GB and my astpsdat files 300MB - is it normal? repair and pack actions doesnt make the database smaller(less then 300MB).
Is there a healthy option of compressing the database?
2)I was trying to restore from a lastnight-backup a file that was deleted today and couldnt find the file in any kind of restoration (by tree, by session, by query...) is there a reasonable explanetion for that - I'm desperate - it happens to me almost every couple of days - Thank's
Is there a healthy option of compressing the database?
2)I was trying to restore from a lastnight-backup a file that was deleted today and couldnt find the file in any kind of restoration (by tree, by session, by query...) is there a reasonable explanetion for that - I'm desperate - it happens to me almost every couple of days - Thank's
I have almost the exact same issue Arcserve 6.61 full backup will not merge to the database completely only a few sessions. I recieve invalid file trailer signatures, and catalog file not found. The puzling thing is that I recieve these errors on all sets of backups I try to merge into the db, even after CA sent me afresh db to merge the info into. The errors occur at the same place on all merges.
Any ideas ?
Any ideas ?
- Status
Similar threads
- Locked
- Question