Jump to content

lmcanada

Members
  • Content count

    7
  • Joined

  • Last visited

Everything posted by lmcanada

  1. lmcanada

    testing backups

    I'm having some problems with the testing of our disaster recovery. Here's My procedure: I do a complete backup of all files and folders, Run's fine, get 3 warnings: File "C:\WINDOWS\Temp\Buf2.tmp": can't read, error -1020 (sharing violation) File "C:\WINDOWS\Temp\VxsvcError.log.tmp": can't read, error -1020 (sharing violation) File "C:\WINDOWS\Temp\hsperfdata_SYSTEM\1320": can't read, error -1020 (sharing violation) Thats all fine, I create a bootable CD using the disaster recovery for the windows 2003 OS. I boot up from the disc on our virtual server (used as a test machine), boots up, loads up the OS fine, restart to install the retrospect client, now I install SP1 (same OS version as the back-up system. ) Now i go into Retrospect, and "restore entire Volume", where I replace files and folders, and having 'restore system state' checked off in the options. I run the restore, get one error: File "C:\Program Files\Citrix\GoToMyPC\g2host.log": appears incomplete looks like a minor issue. The virtual machine displayed the message that the restore was complete, and it went for a restart. It tried booting back up, but to no avail. It would get past the POST, and then only display a black screen. I tried safe mode, also to no avail. What am I doing wrong?
  2. lmcanada

    weird logs

    seems to be backing up fine, I opened up the retrospect client, and get a 3/4/2006 5:12 AM: Script "Toronto Daily Bac..." (LMCTORBACKUP1): First Storage Gro..., Execution completed successfully so i'm assuming the exchange part was backed up. This also happens when backing up from networked drives, however. And also while transferring the disk backup to tape. I tried a test restore of the exchange, which worked fine, so i'm assuming the errors can be ignored? Any way to get rid of them, they make it hard for me to actually check whats ran, and what didn't.
  3. lmcanada

    weird logs

    Hi We recently upgraded to the 7.5 version on both of our backup servers. One the one server, the logs are created normally, with results looking like this: - 3/1/2006 9:04:56 PM: Copying Work on dev on Quants-dev 3/1/2006 9:08:55 PM: Snapshot stored, 1,491 KB 3/1/2006 9:08:56 PM: Execution completed successfully Completed: 5973 files, 2.7 GB Performance: 727.0 MB/minute Duration: 00:03:59 (00:00:16 idle/loading/preparing) On our other backup server, we get really really long logs (850kb) with many random errors that i cannot understand, not know the meaning of. Example: First Storage Group on pertormsx2 T-3: TWDBSqlServerInit: CoCreateInstance() failed [0x80040154]: T-3: TWDBSqlServerGetInstanceInfo: InitDMO failed T-3: TWDBSqlServerGetInstanceInfo: InitDMO failed T-3: TWDBSqlServerInit: CoCreateInstance() failed [0x80040154]: T-3: TWDBSqlServerGetInstanceInfo: InitDMO failed T-3: TWDBSqlServerGetInstanceInfo: InitDMO failed * Resolved container Exchange Server on lmctormsx3 to 1 volumes: and a lot of FEndcEnd errors throughout the document, with other VloRDiskDoFileCreate errors as well. FEncEnd: not started FEncEnd: not started vlocRDiskDoFileCreate: device number = 0x0 FEncEnd: not started Is this a setting that needs to be changed? Is this a bug? Thanks, Willem
  4. yah dude, You cannot upgrade without paying for it, unless you have a ASM (Annual Support Maintenance), if you have an ASM, you can email/call them, else your stuck with 7.0
  5. Hi there We run a nightly process to back up our exchange servers, and im not sure if they are actually being backup up since we do not see a report on the speed of the backup, or any message saying it was backed up successfully. We do not get an error either tho, so im just wondering if anyone else has had better experience with exchange, pertormsx2 is running 2000, while lmctormsx3 is running 2003. Log file: * Resolved container Exchange Server on pertormsx2 to 1 volumes: First Storage Group on pertormsx2 T-3: TWDBSqlServerInit: CoCreateInstance() failed [0x80040154]: T-3: TWDBSqlServerGetInstanceInfo: InitDMO failed T-3: TWDBSqlServerGetInstanceInfo: InitDMO failed T-3: TWDBSqlServerInit: CoCreateInstance() failed [0x80040154]: T-3: TWDBSqlServerGetInstanceInfo: InitDMO failed T-3: TWDBSqlServerGetInstanceInfo: InitDMO failed * Resolved container Exchange Server on lmctormsx3 to 1 volumes: First Storage Group on lmctormsx3 To Backup Set Daily Backup to Disk... vtopCreateHelper: Volume Shadow Copy API disabled in script options. FEncEnd: not started FEncEnd: not started FEncEnd: not started FEncEnd: not started FEncEnd: not started FEncEnd: not started 2/20/2006 7:00:01 PM: Recycle backup: The Backup Set was reset thanks, Willem
  6. lmcanada

    7.5 Scripting error

    Problem solved, I called support, they led me through re-creating the script for the backup to tape, this fixed the error, good future reference tho, --WIllem
  7. As of yesterday, we have the new 7.5 version installed. This caused a huge problem for the overnight backups. While our upgrade from 6.5 to 7.0 went smooth, when the backups to tape ran last night, they copped out with the following error "No destination Backup set specified." This also happens when I try to validate the script. The regular backup to disk (which happens before) worked fine. I tried removing and recreating the destination script to no avail. Any help would be appreciated. Willem Legg Mason Canada IT
×