![]()
BACKUP EXEC 16 SCHEDULED AND OCCURRENCES SOFTWARESo my backup software will only read from or Symantec have not (and will not) released agents for 10d beyond XP or Server 2003. The only backup software I have access to is Backup Exec 10d. The files are there because they need to be backed up on a schedule. To clear the workstation vs server issue. "simon.t" wrote in message Galiher" wrote in message. Looks like you and Kevin are already well into some troubleshooting steps, so I won't interject any tangents.but on a complete aside, have you looked at using the backup utility built into SBS? Is there a reason you need to go 3rd-party? The group was created using the same process as all other security groups on this domain. AllĪttempting to use the Resource Controllers group on other folders on the same machine and other machines produces the same result. I have tried removing and re-adding the group to the folder ACL, deleteing and re-creating the group, using both the SBS console and the Active Directory Users and Computers snap in to create the group and using cacls to add the group to the folder ACL. I then use the "Effective Permissions" tool to check that the group members have the correct permissions. ![]() On the network share I right click -> Properties -> Security tab and add the Resource Controllers group with the "Modify" permission. Using the SBS 2008 console I have created a new security group, lets call it Resource Controllers, and added the relevant users to the group. BACKUP EXEC 16 SCHEDULED AND OCCURRENCES WINDOWSThe share is on a Windows XP SP3 machine. "simon.t" wrote in message have a network share which some users need read, write and delete access to. I've seen odd discrepancies when trying to view or alter NTFS permissions through a share. My second question would be, since this is already an odd need, is the workstation joined to the domain? The client would need access to AD to enumerate the security group.įinally, I'd also recommend logging onto the machine locally (or via remote desktop if necssary) and checking the permissions that way. It is unusual to need to host files on a workstation instead of a server, so my first question would be is this even necessary? The users can do their work as I have added them individually to the folder ACL but I like to do things the "right" way so I'd like to get to the bottom of this. OtherĪs far as I can see nothing is wrong, it just won't work. I have tried removing and re-adding the group to the folder ACL, deleteing and re-creating the group, using both the SBS console and the Active Directory Users and Computers snap in to create the group and using cacls to add the group to the folder ACL.Īttempting to use the Resource Controllers group on other folders on the same machine and other machines produces the same result. If I add their individual user accounts to the folder ACL with the "modify" permission it works as expected. The problem is the group members have no access to the share at all, they cannot even browse it. I then use the "Effective Permissions" tool to check that the group members have the correct permissions. Using the SBS 2008 console I have created a new security group, lets call it Resource Controllers, and added the relevant users to the group. BACKUP EXEC 16 SCHEDULED AND OCCURRENCES FULLThe share is on a Windows XP SP3 machine.įolder is shared and share permissions set to Everybody - Full Control. the above path may be insted 100 write 90 "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\SQLCMD.EXE" -S ADMIN-PC -i "C:\Users\admin\Desktop\DBScript\DBBackUpSQL.I have a network share which some users need read, write and delete access to. īutton Put "C:\Program Files\Microsoft SQL Server\100\Tools\Binn\SQLCMD.EXE" -S ADMIN-PC -i "C:\Users\admin\Desktop\DBScript\DBBackUpSQL.sql" in the program/script text box(make sure Match your files path and Put the double quoted path in start-> search box and if it find then click it and see the backup is there or not) ![]() ![]() If You want daily backup // following sql script store in C:\Users\admin\Desktop\DBScript\DBBackUpSQL.sql DECLARE NVARCHAR(512) SET = 'Databasename' SET = 'C:\DBBackup\DBData\DBBackUp' Convert(varchar(8), GETDATE(), 112) '_' Replace((Convert(varchar(8), GETDATE(), 108)),':','-') '.bak' BACKUP DATABASE TO DISK = WITH NOFORMAT,Ĭreate task-> select Triggers tab Select New. BACKUP EXEC 16 SCHEDULED AND OCCURRENCES UPDATEIF EXISTS(SELECT job_id FROM WHERE (name = Create the job:ĮXEC _add_jobserver Add step to execute SQL:ĮXEC my_stored_procedure - OR ANY SQL Update job to set start step:ĮXEC -YYYYMMDD (this represents no end -HHMMSS See Microsoft help for details on syntax of the individual stored procedures and valid range of parameters. To do this in t-sql, you can use the following system stored procedures to schedule a daily job. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |