About CHRISTIANMINIBEK
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Home
- :
- About CHRISTIANMINIBEK
About CHRISTIANMINIBEK
CHRISTIANMINIBEK
Contributor
6
Total Posts
1
Total Kudos Received
Nov 17, 2015
Last Visited
Jan 31, 2013
Date Registered
After upgrading from SC 4.1.1P4 to 4.1.2 i have exact the same issue on Windows Server 2008R2 SP1 with Domino 9.0.1FP4 64 bit. Nothing else changed - just upgraded from one SC version to another. I checked the path variable and that all is 64bit. What else can be the problem? SC Server 4.1.2 with SC Agent 4.1.1P4 works fine.
... View more
Hello John! Tried now an u2m-restore with the older snapshot. Is was working on my test server. But had the same issue on productive server. The difference between this two servers is, that the first one is a testserver without user activity, so the transaction log is not archived for a very long time - on this server only an agent is running in one application which creates a document every two minutes (just for restore testing). The other server, where restore is not working is a busy productive machine and logs are archived daily to ChangeInfo\logs folder. I have mailed you the dumps. Thanks!
... View more
Hello! Logging style is set to archived of course. Retention for archived logs in SC is set to 21 days, whis is working well as far I cann see. See information about logging settings at the end of my last message. thanks
... View more
Good Morning John! Thanks for quick reply! I confirm that I was running the SC-Agent in CLI. To be honest, I have never tried u2m-restore. But I did it now: Below the results from agent console and debug-logfile: c:\Program Files\NetApp\Snap_Creator_Framework\scAgent4.0p1>snapcreator.exe -start-agent -verbose [Thu Nov 7 07:07:46 2013] INFO: Starting NetApp Snap Creator Framework 4.0p1 Agent [single-threaded] [Thu Nov 7 07:07:46 2013] DEBUG: Listening on built-in default port: 9090 [Thu Nov 7 07:07:49 2013] INFO: Snap Creator Framework Agent [single-threaded], running with pid 6828, is listening on port 9090 of all configured network interfaces [Thu Nov 7 07:11:01 2013] INFO: Authorized request from [scServer@*] [Thu Nov 7 07:11:01 2013] INFO: Authorized request from [scServer@*] [1AAC:0002-1640] Media Recovery Replay (6142 MB): 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% [1AAC:0002-1640] 07.11.2013 07:14:47 Recovery Manager: Media Recovery complete for D:\IBM\Lotus\Domino\data\restore\archive_it\helpdesk.nsf, last update applied 06.11.2013 22:14:16. [Thu Nov 7 07:14:48 2013] INFO: Restoring databases finished successfully ########## Custom plug-in action ########## [2013-11-07 07:14:48,705] DEBUG: [atsmsvld02.itc.global.mahle:9090 (4.0.0.1)] domino::setENV finished successfully [2013-11-07 07:14:48,705] DEBUG: [atsmsvld02.itc.global.mahle:9090 (4.0.0.1)] Restoring to current time. [2013-11-07 07:14:48,705] DEBUG: [atsmsvld02.itc.global.mahle:9090 (4.0.0.1)] Calling dominocore::postRestoreToTime with arguments(C:\Program Files\IBM\Lotus\Domino\notes.ini,D:\IBM\Lotus\Domino\data\restore,N:\ChangeInfo\ATSMSVLD02-daily_20131105230000,-1,D:\IBM\Lotus\Domino\data\restore\archive_it\helpdesk.nsf,UP-TO-THE-MINUTE,N:\ChangeInfo\logs\) [2013-11-07 07:14:48,705] TRACE: Notes API initialized Applying Change info for:D:\IBM\Lotus\Domino\data\restore\archive_it\helpdesk.nsf NSFRecoverDatabases returned successfully. NSFDbReplicaInfoGet called successfully. NSFDbReplicaInfoSet called successfully. Replication disabled. ERROR_CODE:0 [2013-11-07 07:14:48,705] INFO: [atsmsvld02.itc.global.mahle:9090 (4.0.0.1)] Restoring databases finished successfully ########## Custom handling for plugin domino completed successfully ########## ########## Snap Creator Framework 4.0p1 finished successfully ########## [2013-11-07 07:14:48,721] INFO: INFO: Snap Creator Framework finished successfully (Action: custom) [2013-11-07 07:14:50,297] INFO: STORAGE-05016: Creating OM Event [script:information-event] on [atsmsvfsmgmt01.itc.global.mahle]. [2013-11-07 07:14:50,297] DEBUG: <event-generate> <event-name>script:information-event</event-name> <source>1</source> <event-message>SNAPCREATOR INFO: Snap Creator Framework finished successfully (Action: custom)(Config: ATSMSVLD02 Name: ATSMSVLD02)</event-message> </event-generate> [2013-11-07 07:14:50,297] INFO: STORAGE-05017: OM Event [script:information-event] on [atsmsvfsmgmt01.itc.global.mahle] created successfully. Because this was working well, I tried a su2m-restore with the same snapshot. It was also working. Both cases where the latest existing snapshot of course. After that I tried a su2m-restore from an older snapshot (5 day old snapshot, so that the logs are available) and had the same error as I described yesterday. c:\Program Files\NetApp\Snap_Creator_Framework\scAgent4.0p1>snapcreator.exe -start-agent -verbose [Thu Nov 7 08:06:51 2013] INFO: Starting NetApp Snap Creator Framework 4.0p1 Agent [single-threaded] [Thu Nov 7 08:06:51 2013] DEBUG: Listening on built-in default port: 9090 [Thu Nov 7 08:06:54 2013] INFO: Snap Creator Framework Agent [single-threaded], running with pid 9632, is listening on port 9090 of all configured network interfaces [Thu Nov 7 08:07:38 2013] INFO: Authorized request from [scServer@*] [Thu Nov 7 08:07:38 2013] INFO: Authorized request from [scServer@*] [25A0:0002-2604] comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 co mp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 10 23D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11 , fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D0000 00 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp So from my point of view there are only two options: 1. the older snapshot has a problem => I don't think this is the reason. 2. su2m-restore has a problem with recovering the archived logs from the ChangeInfo path. Logging style from Domino is set to "Archived" in the directory t:\log. Here is some config information regarding the archive-log-settings: ######################################################################################################################## # Archive Options # ######################################################################################################################## ARCHIVE_LOG_RECURSIVE_SEARCH=N ARCHIVE_LOG_DIR=N:\ChangeInfo\logs ARCHIVE_LOG_EXT=TXN ARCHIVE_LOG_RETENTION=28.0 ARCHIVE_LOG_ENABLE=Y ######################################################################################################################## # Plug-In Parameter # ######################################################################################################################## DOMINO_DATA_PATH=D:\IBM\Lotus\Domino\data VALIDATE_DOMINO_DATA_PATH=N Notes_ExecDirectory=C:\Program Files\IBM\Lotus\Domino DOMINO_DATABASE_TYPE=0 DOMINO_CHANGE_INFO_PATH=N:\ChangeInfo DOMINO_INI_PATH=C:\Program Files\IBM\Lotus\Domino\notes.ini DOMINO_RESTORE_DATA_PATH=D:\IBM\Lotus\Domino\data\restore LOTUS=C:\Program Files\IBM\Lotus
... View more
Hello, I am using SnapCreator 4.0p1 for my Domino backup. Environment Facts: - Domino 8.5.3FP4 64bit on Windows Server 2008R2 - SnapCreatorAgent 4.0p1 64bit runs as Service - Domino Data is stored on iSCSI LUN - SnapCreatorServer 4.0p1 installed on Windows Server 2008R2, Running on Port 9080 because DFM is also installed on the same machine I followed this restore operation steps => https://library.netapp.com/ecmdocs/ECMP1149421/html/html/GUID-334E9282-6824-4226-8ABC-A4F92ECA5BA3.html My restore command was on SnapCreatorServer was => c:\Program Files\NetApp\Snap_Creator_Framework\scServer4.0p1>snapcreator.exe --server localhost --port 9080 --user sc_user --passwd xxxxxx --verbose --debug --action custom --profile Domino --config ATSMSVLD02 --params snapname=ATSMSVLD02-weekly_20131102230000 datapath=D:\IBM\Lotus\Domino\data\restore\archive_it\helpdesk.nsf restoretype=su2m restoretime="11/06/2013 14:00:00" disablereplication=Y The only entry in the ATSMSVLD02.debug.20131106150032.log is "########## Custom plug-in action ##########". After a while the Domino Server crashes with an NSD or I have to kill the snapcreator process manually an then the server crashes. Then the debug log has some more infos: ########## Custom plug-in action ########## [2013-11-06 15:15:49,060] ERROR: SCF-00050: Action custom for plugin [domino] failed with error [java.net.ConnectException: ConnectException invoking http://atsmsvld02.itc.global.mahle:9090/SnapCreator/Daemon/Agent: Connection refused: connect] and exit code [-1], Exiting! ########## Snap Creator Framework 4.0p1 failed ########## [2013-11-06 15:15:49,076] INFO: Pre Exit commands are not defined. Skipping ! [2013-11-06 15:15:49,091] INFO: STORAGE-05016: Creating OM Event [script:critical-event] on [atsmsvfsmgmt01.itc.global.mahle]. [2013-11-06 15:15:49,091] DEBUG: <event-generate> <event-name>script:critical-event</event-name> <source>1</source> <event-message>SNAPCREATOR SCF-00050: Action custom for plugin [domino] failed with error [java.net.ConnectException: ConnectException invoking http://atsmsvld02.itc.global.mahle:9090/SnapCreator/Daemon/Agent: Connection refused: connect] and exit code [-1], Exiting!(Config: ATSMSVLD02 Name: ATSMSVLD02)</event-message> </event-generate> [2013-11-06 15:15:49,091] INFO: STORAGE-05017: OM Event [script:critical-event] on [atsmsvfsmgmt01.itc.global.mahle] created successfully. I found this bug report => http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=695053 Tryed it and saw for a few minutes this output on the command window where I started snapcreator.exe -start-agent 0 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D 000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tra cePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, f nc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D000000 comp = 11, fnc = 82, tracePt = 1023D0 This was very fast scolling, after I killes the snapcreator process, domino crashed again. File restore from snapshot allways works perfect, after a fixup of the restored file from snapshot, the database is readable. The problem only exists when working with selectable point in time. On another Domino Server where I have the same configuration the restore works perfect! Has anyone an idea where I have to look to solve the problem? Is additional information needed?
... View more
by
CHRISTIANMINIBEK
in Data Protection
2013-11-06
06:50 AM
View By:
- View By:
-
Snap Creator Framework
7,721 Views
Hello, I tried this for a couple of times. When I am not using the restoretype, then the point-in-time is the snapshot-time - works fine. When I use u2m, the rollback of the logs is don up to now - workls also fine. But when I am using su2m with the restoretime parameter, it will be ignored. Allways a u2m is done, it does not matter which format I am using for the restoretime, seems to be ignored. Snapcreator 3.6.0 SnapDrive 6.5 Domino 8.5.3FP3 64bit on Windows 2008R2 64bit Running on a VM (ESX) with NFS Datastores Here is my log: [Tue Apr 9 10:20:00 2013] INFO: Logfile timestamp: 20130409102000 [Tue Apr 9 10:20:00 2013] DEBUG: GMT - Tue Apr 9 08:20:00 2013 [Tue Apr 9 10:20:00 2013] DEBUG: Version: NetApp Snap Creator Framework 3.6.0 [Tue Apr 9 10:20:00 2013] DEBUG: Profile: Domino [Tue Apr 9 10:20:00 2013] DEBUG: Config Type: STANDARD [Tue Apr 9 10:20:00 2013] DEBUG: Action: custom [Tue Apr 9 10:20:00 2013] DEBUG: Application Plugin: domino [Tue Apr 9 10:20:00 2013] DEBUG: File System Plugin: null [Tue Apr 9 10:20:00 2013] DEBUG: Policy: null [Tue Apr 9 10:20:00 2013] DEBUG: Snapshot Name: null [Tue Apr 9 10:20:00 2013] INFO: Plugin validation for domino completed successfully [Tue Apr 9 10:20:00 2013] INFO: Removing log TLATSMSVLD01.out.20130404144244.log [Tue Apr 9 10:20:00 2013] INFO: Removing log TLATSMSVLD01.debug.20130404144244.log [Tue Apr 9 10:20:00 2013] INFO: Removing log TLATSMSVLD01.stderr.20130404144244.log ########## Parsing Environment Parameters ########## [Tue Apr 9 10:20:00 2013] DEBUG: Parsing VOLUMES - controller: atsm-mc-v01 volume: vm_sas_v01_dominodaos [Tue Apr 9 10:20:00 2013] DEBUG: Parsing VOLUMES - controller: atsm-mc-v01 volume: vm_sas_v01_dominodata [Tue Apr 9 10:20:00 2013] DEBUG: Parsing VOLUMES - controller: atsm-mc-v21 volume: vm_sas_v21_dominotranslog [Tue Apr 9 10:20:00 2013] DEBUG: Parsing NTAP_USERS - controller: atwo-bup-v01 user: root [Tue Apr 9 10:20:00 2013] DEBUG: Parsing NTAP_USERS - controller: atsm-mc-v01 user: root [Tue Apr 9 10:20:00 2013] DEBUG: Parsing NTAP_USERS - controller: atsm-mc-v21 user: root [Tue Apr 9 10:20:00 2013] DEBUG: Parsing NTAP_SNAPSHOT_RETENTIONS - policy: daily retention: 14 [Tue Apr 9 10:20:00 2013] DEBUG: Parsing NTAP_SNAPVAULT_RETENTIONS - sv policy: daily retention: 21 [Tue Apr 9 10:20:00 2013] DEBUG: Parsing SNAPVAULT_VOLUMES - controller: atsm-mc-v01 sv volume: vm_sas_v01_dominodaos [Tue Apr 9 10:20:00 2013] DEBUG: Parsing SNAPVAULT_VOLUMES - controller: atsm-mc-v01 sv volume: vm_sas_v01_dominodata [Tue Apr 9 10:20:00 2013] DEBUG: Parsing SNAPVAULT_VOLUMES - controller: atsm-mc-v21 sv volume: vm_sas_v21_dominotranslog ########## Custom plug-in action ########## [Tue Apr 9 10:20:00 2013] [tlatsmsvld01.itc.global.mahle:9090(3.6.0.1)] DEBUG: Restoring to current time. [Tue Apr 9 10:20:00 2013] [tlatsmsvld01.itc.global.mahle:9090(3.6.0.1)] DEBUG: Calling dominocore::postRestoreToTime with arguments(C:\Program Files\IBM\Lotus\Domino\notes.ini,D:\IBM\Lotus\Domino\data\restore,N:\ChangeInfo\TLATSMSVLD01-daily_20130408082121,-1,D:\IBM\Lotus\Domino\data\restore\test\Test.nsf,UP-TO-THE-MINUTE,N:\ChangeInfo\logs\) [Tue Apr 9 10:20:02 2013] [tlatsmsvld01.itc.global.mahle:9090(3.6.0.1)] TRACE: Notes API initialized Applying Change info for:D:\IBM\Lotus\Domino\data\restore\test\Test.nsf NSFRecoverDatabases returned successfully. ERROR_CODE:0 [Tue Apr 9 10:20:02 2013] [tlatsmsvld01.itc.global.mahle:9090(3.6.0.1)] INFO: Restoring databases finished successfully ########## Custom plug-in action completed successfully ########## [Tue Apr 9 10:20:02 2013] DEBUG: Exiting with error code - 0
... View more
