bck666 Posted September 2, 2003 Report Share Posted September 2, 2003 I have created a "Windows 2k Server" folder in the Volumes Database; the folder contains W2K server clients. I can see the SQL databases when I expand the "SQL Server" treeview under the machine running the SQL server. So far, so good... I just noticed(unfortunately too late), that two new SQL databases created after the installation of the SQL agent were not backed up!!! So, what's the correct procedure to get the SQL agent to automagically detect / backup new databases ? thanks, alan Link to comment Share on other sites More sharing options...
natew Posted September 8, 2003 Report Share Posted September 8, 2003 Hi I have managed to reproduce this problem as well. It looks like you have to go the volumes database and expand and contract the database container once to get the new DB seen. I'll do some digging and post if I find some more info Nate Link to comment Share on other sites More sharing options...
algilson Posted January 20, 2004 Report Share Posted January 20, 2004 Sorry to bring an old thread back to life, but I was wondering if you discovered any more details on this? I've got the same problem. Version 6.5.336, and when we add new databases or remove databases from the SQL client, Retrospect doesn't see them. Thanks, - Al Link to comment Share on other sites More sharing options...
natew Posted January 21, 2004 Report Share Posted January 21, 2004 Hi This can actually happen with all client volumes not just databases. I'm not sure if it is by design or oversight. When you add a new database or drive to a client you need to go to that client, look at the volumes and make sure the new database is highlighted. It is a pain but Retrospect won't see the new database otherwise. Nate Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.