Jump to content

alpha297

Members
  • Content count

    3
  • Joined

  • Last visited

  • Days Won

    1

alpha297 last won the day on November 5 2012

alpha297 had the most liked content!

Community Reputation

1 Neutral

About alpha297

  • Rank
    Newbie
  1. Hi, I'm starting to research below consistent Retrospect error that has popped up in the operations log. I've created a test backup script and confirmed I can recreate below error and is not dependent on a specific script. I suspect it has something to do with the state of the Windows 2003 servers vss (Volume Shadowcopy service) state, but not exactly sure. There were no shadowcopies ever configured on this server (never enabled feature), but I've just created a new shadow copy schedule for the below C drive to see if it might clear up some issue with the specific files quota.md and quota.xml. I was just wondering if anyone might have any input from a Retrospect perspective. Thanks in advance, Mark - 3/9/2011 2:40:47 PM: Copying OS (C:) MapError: unknown Windows error -1,017 xpmlStoreMetadata: couldn't copy file "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\System Volume Information\SRM\quota.md" to the state folder "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0000\comp0001\file0000", osErr -1017, error -1001 MapError: unknown Windows error -1,017 xpmlStoreMetadata: couldn't copy file "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\System Volume Information\SRM\quota.xml" to the state folder "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0000\comp0001\file0001", osErr -1017, error -1001 3/9/2011 2:52:43 PM: Snapshot stored, 135.0 MB 3/9/2011 2:53:44 PM: Execution completed successfully Completed: 790 files, 3.4 GB, with 26% compression Performance: 393.6 MB/minute Duration: 00:12:57 (00:04:12 idle/loading/preparing)
  2. Update: Installed beta retro client 6.2.222 on intel 10.5 xserve and beta mac retro server 6.1.222 on PPC G5 and net retry problem has gone away- have performed problem free backups on this client for two days straight (hasn't ever happen). All other backups working fine as well.
  3. Hi, One client continual has a "net retry" problem: intel xserve os x 10.5.1, retro client 6.1.130. The retrospect server is mac 6.1.138 running on g5 tower os x 10.4.9. -- I have been troubleshooting this even since the os x 10.5.1 server has been put into production (two+ months). This is only os x 10.5 machine we have, and is the only problem client. When we run the normal backup script (backup set type is file), it starts matching files and folders, then the net rety screen starts and will sometimes generate an error 519 after a few minutes. To fix daily, I'll stop script on backup server, toggle problem client off and then back on. Then I'll repopulate permissions via xserve server admin software on the data the backup script generated the net retry screen. There are ACL permissions used on the data. I do not have "use attribute modification date when matching" checked under matching section under the backup script options. This data using same ACL permissions, use to be setup on a g4 xserver running 10.4- never encounter the net retry problem. Does anyone have a similar enviro and similar problems? The problem could be the ACL permissions in conjunction with os x 10.5? I am starting to check the retro client log, but not sure what to look for, I see these error, but not sure if they were generated during net retry issues: 1209697886: PmcOpen: connect() failed with error 61: Connection refused 1209697886: ipludAddMembership: adding membership for 0.0.0.0 1209697886: iplud: bound to address 4.5.23.172 1209697892: IPNSRegister(0): registered: "xserve2"/"88ba0eb491e27887" 1209697898: IPNSRegister(0): registered: "xserve2"/"88ba0eb491e27887" 1209697898: bindToValidBootPort: gServerPID has been initialized to 190 1209697938: Connection established by 13.5.23.172:49238 1209697945: TransWritePipe: write() failed with error 32 1209697957: TransWritePipe: write() failed with error 32 1209697993: ConnWriteData: send() failed with error 32 1209697993: TransReadPipe: read() failed with error 9 1209697993: ConnWriteData: send() failed with error 32 1209697994: ConnWriteData: send() failed with error 32 1209697994: ConnReadData: Connection with 13.5.23.172:49238 was reset 1209697994: ServicePurge: service not found 1209698307: Connection established by 13.5.23.172:49239 1209698555: ConnReadData: Connection with 13.5.23.172:49239 was reset 1209698560: Connection established by 13.5.23.172:49240 1209698560: ConnReadData: Connection with 13.5.23.172:49240 was reset 1209698561: Connection established by 13.5.23.172:49241 1209698561: ConnReadData: Connection with 13.5.23.172:49241 was reset 1209698768: Connection established by 13.5.23.172:49242 1209698807: ConnReadData: Connection with 13.5.23.172:49242 was reset 1209698812: Connection established by 13.5.23.172:49243 1209698818: ConnReadData: Connection with 13.5.23.172:49243 was reset 1209698818: Connection established by 13.5.23.172:49244 1209698823: ConnReadData: Connection with 13.5.23.172:49244 was reset 1209698823: Connection established by 13.5.23.172:49245 1209698826: ConnReadData: Connection with 13.5.23.172:49245 was reset 1209698826: Connection established by 13.5.23.172:49246 1209698828: ConnReadData: Connection with 13.5.23.172:49246 was reset 1209699112: Connection established by 13.5.23.172:49259 1209699117: ConnReadData: Connection with 13.5.23.172:49259 was reset 1209699118: Connection established by 13.5.23.172:49260 1209699122: ConnReadData: Connection with 13.5.23.172:49260 was reset 1209699123: Connection established by 13.5.23.172:49261 1209699128: ConnReadData: Connection with 13.5.23.172:49261 was reset 1209699128: Connection established by 13.5.23.172:49262 1209699133: ConnReadData: Connection with 13.5.23.172:49262 was reset 1209699412: Connection established by 13.5.23.172:49275 1209699418: ConnReadData: Connection with 13.5.23.172:49275 was reset 1209699418: Connection established by 13.5.23.172:49276 1209699424: ConnReadData: Connection with 13.5.23.172:49276 was reset 1209699424: Connection established by 13.5.23.172:49277 1209699430: ConnReadData: Connection with 13.5.23.172:49277 was reset 1209699430: Connection established by 13.5.23.172:49278 1209699436: ConnReadData: Connection with 13.5.23.172:49278 was reset 1209699712: Connection established by 13.5.23.172:49290 1209699718: ConnReadData: Connection with 13.5.23.172:49290 was reset 1209699718: Connection established by 13.5.23.172:49291 1209699723: ConnReadData: Connection with 13.5.23.172:49291 was reset 1209699724: Connection established by 13.5.23.172:49292 1209699725: ConnReadData: Connection with 13.5.23.172:49292 was reset Thanks for any info. Mark Bonne Alphagraphics Seattle mbonne@alphagraphics.com
×