You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "김성민 [넷마블에프앤씨/R&D빌드파트]" <su...@nm-fc.com> on 2023/04/17 05:28:33 UTC
When backing up an svn server, why shouldn't we use copy and move provided by linux and should we use svnadmin dump?
hello. I am sending an e-mail because I have a question during the svn
backup process.
When backing up svn, you are backing up using svnsync or dump.
However, if you try to move and use the copy command or move command
provided by linux os
to change only the location on the same computer (server), normal operation
is impossible.
Could you please explain the reason for this?
--
Netmarble Confidential
*이 메일은 지정된 수취인만을 위해 작성되었으며, 중요한 정보나 저작권을
포함하고 있을 수 있습니다. 어떠한 권한 없이, 본 문서에 포함된 정보의 전부 또는 일부를 무단으로 제3자에게 공개, 배포, 복사 또는
사용하는 것을 엄격히 금지합니다. 만약, 본 메일이 잘못 전송된 경우, 발신인 또는 당사에 알려주시고, 본 메일을 즉시 삭제하여 주시기
바랍니다.
*This
E-mail may contain confidential information and/or copyright
material. This
email is intended for the use of the addressee only. If you
receive this email
by mistake, please either delete it without reproducing,
distributing or
retaining copies thereof or notify the sender immediately.
Re: When backing up an svn server, why shouldn't we use copy and move provided by linux and should we use svnadmin dump?
Posted by "김성민 [넷마블에프앤씨/R&D빌드파트]" <su...@nm-fc.com>.
팁 고마워!
2023년 4월 18일 (화) 오후 12:30, Nico Kadel-Garcia <nk...@gmail.com>님이 작성:
> On Mon, Apr 17, 2023 at 9:44 PM 김성민 [넷마블에프앤씨/R&D빌드파트]
> <su...@nm-fc.com> wrote:
> >
> > 답변 감사합니다.
> >
> > 2023년 4월 18일 (화) 오전 5:14, Daniel Sahlberg <da...@gmail.com>님이
> 작성:
> >>
> >> Den mån 17 apr. 2023 kl 17:44 skrev 김성민 [넷마블에프앤씨/R&D빌드파트] <
> sungmin4036@nm-fc.com>:
> >>>
> >>> hello. I am sending an e-mail because I have a question during the svn
> backup process.
> >>>
> >>> When backing up svn, you are backing up using svnsync or dump.
> >>>
> >>> However, if you try to move and use the copy command or move command
> provided by linux os
> >>>
> >>> to change only the location on the same computer (server), normal
> operation is impossible.
> >>>
> >>> Could you please explain the reason for this?
> >>
> >>
> >> Do I understand it correctly that you have moved the repository using
> mv(1)?
> >>
> >> In that case it depens on how you access your repository. If you are
> using HTTP/mod_dav_svn then you need to update your httpd configuration to
> point to the new location of the repository. If you are using plain
> svnserve you should update your service configuration. If you are accessing
> the repository via the file:// protocol, you can use the svn relocate
> command to point your working copy to the new location.
> >>
> >> Kind regards,
> >> Daniel
>
> *Never* just do an "mv". If the Subversion service is in the midst of
> an atomic operation, especially if you have anything.... exotic in
> your pre and post scripts, it can be especially traumatic.
>
--
Netmarble Confidential
*이 메일은 지정된 수취인만을 위해 작성되었으며, 중요한 정보나 저작권을
포함하고 있을 수 있습니다. 어떠한 권한 없이, 본 문서에 포함된 정보의 전부 또는 일부를 무단으로 제3자에게 공개, 배포, 복사 또는
사용하는 것을 엄격히 금지합니다. 만약, 본 메일이 잘못 전송된 경우, 발신인 또는 당사에 알려주시고, 본 메일을 즉시 삭제하여 주시기
바랍니다.
*This
E-mail may contain confidential information and/or copyright
material. This
email is intended for the use of the addressee only. If you
receive this email
by mistake, please either delete it without reproducing,
distributing or
retaining copies thereof or notify the sender immediately.
Re: When backing up an svn server, why shouldn't we use copy and move provided by linux and should we use svnadmin dump?
Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Mon, Apr 17, 2023 at 9:44 PM 김성민 [넷마블에프앤씨/R&D빌드파트]
<su...@nm-fc.com> wrote:
>
> 답변 감사합니다.
>
> 2023년 4월 18일 (화) 오전 5:14, Daniel Sahlberg <da...@gmail.com>님이 작성:
>>
>> Den mån 17 apr. 2023 kl 17:44 skrev 김성민 [넷마블에프앤씨/R&D빌드파트] <su...@nm-fc.com>:
>>>
>>> hello. I am sending an e-mail because I have a question during the svn backup process.
>>>
>>> When backing up svn, you are backing up using svnsync or dump.
>>>
>>> However, if you try to move and use the copy command or move command provided by linux os
>>>
>>> to change only the location on the same computer (server), normal operation is impossible.
>>>
>>> Could you please explain the reason for this?
>>
>>
>> Do I understand it correctly that you have moved the repository using mv(1)?
>>
>> In that case it depens on how you access your repository. If you are using HTTP/mod_dav_svn then you need to update your httpd configuration to point to the new location of the repository. If you are using plain svnserve you should update your service configuration. If you are accessing the repository via the file:// protocol, you can use the svn relocate command to point your working copy to the new location.
>>
>> Kind regards,
>> Daniel
*Never* just do an "mv". If the Subversion service is in the midst of
an atomic operation, especially if you have anything.... exotic in
your pre and post scripts, it can be especially traumatic.
Re: When backing up an svn server, why shouldn't we use copy and move provided by linux and should we use svnadmin dump?
Posted by "김성민 [넷마블에프앤씨/R&D빌드파트]" <su...@nm-fc.com>.
답변 감사합니다.
2023년 4월 18일 (화) 오전 5:14, Daniel Sahlberg <da...@gmail.com>님이
작성:
> Den mån 17 apr. 2023 kl 17:44 skrev 김성민 [넷마블에프앤씨/R&D빌드파트] <
> sungmin4036@nm-fc.com>:
>
>> hello. I am sending an e-mail because I have a question during the svn
>> backup process.
>>
>> When backing up svn, you are backing up using svnsync or dump.
>>
>> However, if you try to move and use the copy command or move command
>> provided by linux os
>>
>> to change only the location on the same computer (server), normal
>> operation is impossible.
>>
>> Could you please explain the reason for this?
>>
>
> Do I understand it correctly that you have moved the repository using
> mv(1)?
>
> In that case it depens on how you access your repository. If you are using
> HTTP/mod_dav_svn then you need to update your httpd configuration to point
> to the new location of the repository. If you are using plain svnserve you
> should update your service configuration. If you are accessing the
> repository via the file:// protocol, you can use the svn relocate command
> to point your working copy to the new location.
>
> Kind regards,
> Daniel
>
>
--
Netmarble Confidential
*이 메일은 지정된 수취인만을 위해 작성되었으며, 중요한 정보나 저작권을
포함하고 있을 수 있습니다. 어떠한 권한 없이, 본 문서에 포함된 정보의 전부 또는 일부를 무단으로 제3자에게 공개, 배포, 복사 또는
사용하는 것을 엄격히 금지합니다. 만약, 본 메일이 잘못 전송된 경우, 발신인 또는 당사에 알려주시고, 본 메일을 즉시 삭제하여 주시기
바랍니다.
*This
E-mail may contain confidential information and/or copyright
material. This
email is intended for the use of the addressee only. If you
receive this email
by mistake, please either delete it without reproducing,
distributing or
retaining copies thereof or notify the sender immediately.
Re: When backing up an svn server, why shouldn't we use copy and move provided by linux and should we use svnadmin dump?
Posted by Daniel Sahlberg <da...@gmail.com>.
Den mån 17 apr. 2023 kl 17:44 skrev 김성민 [넷마블에프앤씨/R&D빌드파트] <
sungmin4036@nm-fc.com>:
> hello. I am sending an e-mail because I have a question during the svn
> backup process.
>
> When backing up svn, you are backing up using svnsync or dump.
>
> However, if you try to move and use the copy command or move command
> provided by linux os
>
> to change only the location on the same computer (server), normal
> operation is impossible.
>
> Could you please explain the reason for this?
>
Do I understand it correctly that you have moved the repository using mv(1)?
In that case it depens on how you access your repository. If you are using
HTTP/mod_dav_svn then you need to update your httpd configuration to point
to the new location of the repository. If you are using plain svnserve you
should update your service configuration. If you are accessing the
repository via the file:// protocol, you can use the svn relocate command
to point your working copy to the new location.
Kind regards,
Daniel